Bug 142524 - Blinking the keybleds after a panic causes a warning to be emitted, which in turn causes the reason for the panic to scroll of the screen
Summary: Blinking the keybleds after a panic causes a warning to be emitted, which in ...
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 3
Hardware: i686
OS: Linux
medium
low
Target Milestone: ---
Assignee: Dave Jones
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-12-10 09:51 UTC by Hans de Goede
Modified: 2015-01-04 22:13 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-08-31 07:35:20 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Hans de Goede 2004-12-10 09:51:24 UTC
Version: 2.6.9-1.681_FC3

I recompiled my kernel with the default .config, all I did was add an
additional vendor/product id pair to the usb-ff.c file to try to get
forcefeedback to work on my logitech rumblepad. But I forgot to set
extra version to: 2.6.9-1.681_FC3, and did install the bzImage over  
vmlinuz-2.6.9-1.681_FC3, so I got a well deserved panic, because the
modules in my ramdisk refused to work (I think).

I say I think because I couldn't read the exact error message(s)
because the kernel started emmitting:
"atkbd.c: Spurious %s on %s. Some program, "
"like XFree86, might be trying access hardware directly.\n"

From line 369 of drivers/input/keyboard/atkbd.c, which is very annoying.

Comment 1 Dave Jones 2005-07-15 19:03:14 UTC
An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which
may contain a fix for your problem.   Please update to this new kernel, and
report whether or not it fixes your problem.

If you have updated to Fedora Core 4 since this bug was opened, and the problem
still occurs with the latest updates for that release, please change the version
field of this bug to 'fc4'.

Thank you.

Comment 2 Hans de Goede 2005-08-31 07:35:20 UTC
I can't reproduce this anymore, so either it is fixed, or I need my old hardware
(gone) to reproduce. Closing.


Note You need to log in before you can comment on or make changes to this bug.