Am Montag 18 April 2011 schrieb Ionuț Bîru:

On 04/17/2011 09:34 PM, Tobias Powalowski wrote:

...

Hi guys, please signoff 2.6.38.3 series for both arches.

greetings tpowa

now the booting messages from initrd and dmesg are more verbose.

Is it intended? yes, i think this is because i enabled printk_time option. That was a feature request on bug tracker.

greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa@archlinux.org

Am Mon, 18 Apr 2011 07:29:20 +0200 schrieb Tobias Powalowski :

Am Montag 18 April 2011 schrieb Ionuț Bîru:

...

On 04/17/2011 09:34 PM, Tobias Powalowski wrote:

...

Hi guys, please signoff 2.6.38.3 series for both arches.

greetings tpowa

now the booting messages from initrd and dmesg are more verbose.

Is it intended? yes, i think this is because i enabled printk_time option. That was a feature request on bug tracker.

greetings tpowa

Once again somebody request something and we don't think about it and enable it without any need... arch/x86/Kconfig.debug The configuration item CONFIG_EARLY_PRINTK: prompt: Early printk type: tristate depends on: CONFIG_EMBEDDED defined in arch/x86/Kconfig.debug found in Linux Kernels: from 2.6.0 release still available on 2.6.38 release Help text Write kernel log output directly into the VGA buffer or to a serial port. This is useful for kernel debugging when your machine crashes very early before the console code is initialized. For normal operation it is not recommended because it looks ugly and doesn't cooperate with klogd/syslogd or the X server. You should normally N here, unless you want to debug such a crash. I suggest to revert this for the next build. PS: Just had another full freeze without any log entries. I blame nouveau drm kernel module. Even without nouveau-dri my nv44 seems a bit unstable since .38 series :( I'm probably forced to use the closed driver from now on and I don't expect upstream devs to care much about my old card. -Andy

Am Donnerstag 21 April 2011 schrieb Tom Gundersen:

On Thu, Apr 21, 2011 at 7:16 AM, Andreas Radke wrote:

...

Am Mon, 18 Apr 2011 07:29:20 +0200

schrieb Tobias Powalowski :

...

yes, i think this is because i enabled printk_time option.

Once again somebody request something and we don't think about it and enable it without any need...

...

The configuration item CONFIG_EARLY_PRINTK: CONFIG_PRINTK_TIME is not the same as CONFIG_EARLY_PRINTK. The former is very useful to make sense of dmesg (otherwise you dont know what messages "belong together") and it should not have any negative side effects (I have been using it for years). The latter might be, as you say, annoying and should perhaps be removed, it is not new in this release though (it is from before the start of the packages repo)...

Cheers,

Tom All major distros have it enabled. This is can be turned off by printk_time=0 on boot line greetings tpowa

-- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa@archlinux.org

On Mon, Apr 18, 2011 at 4:15 PM, Tom Gundersen wrote:

On Mon, Apr 18, 2011 at 2:34 AM, Tobias Powalowski wrote:

...

Hi guys, please signoff 2.6.38.3 series for both arches.

signoff i686

It seems I spoke to soon. I'm seeing a minor issue with my iwl3945 wireless nic. The problem is described here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=623290, but I have not found a kernel bug report yet. As far as I can see the only problem is that dmesg/console is spammed with error messages every few seconds. There probably is an impact on performance, but not big enough for me to notice during day-to-day use. I will follow up upstream and report back when/if I find a fix. Cheers, Tom