On Fri, 07 Jul 2006 17:06:09 +0200, john stultz wrote: > Hmmm. Just to make sure I understand the situation: If you log in via > ssh, and run dmesg, you do see your driver's output, but that output > just doesn't get to syslog until you press a key on your keyboard? Exactly. And it's only the system keyboard which does it - neither mouse movements nor network traffic (like hitting keys in the ssh session) or other system activity (like compiling the kernel of the day) will do. FYI, the issue is still present in 2.6.18-rc4 and 2.6.18-rc3-mm2. Please let me know if you need more information or if you want me to test something. Thanks, Tilman -- Tilman Schmidt E-Mail: [email protected] Bonn, Germany Diese Nachricht besteht zu 100% aus wiederverwerteten Bits. Ungeoeffnet mindestens haltbar bis: (siehe Rueckseite)
Attachment:
signature.asc
Description: OpenPGP digital signature
- References:
- Re: Linux v2.6.18-rc1: printk delays
- From: Tilman Schmidt <[email protected]>
- Re: Linux v2.6.18-rc1: printk delays
- From: john stultz <[email protected]>
- Re: Linux v2.6.18-rc1: printk delays
- From: Tilman Schmidt <[email protected]>
- Re: Linux v2.6.18-rc1: printk delays
- From: john stultz <[email protected]>
- Re: Linux v2.6.18-rc1: printk delays
- Prev by Date: [patch] Re: 2.6.18-rc3-mm2 - OOM storm
- Next by Date: Re: Linux v2.6.18-rc1/reiserfs INFO: possible recursive locking detected
- Previous by thread: Re: Linux v2.6.18-rc1: printk delays
- Next by thread: Implement class_device_update_dev() function
- Index(es):
 |