Bug 10796
| Summary: | PS/2 keyboard becomes dead/non-responsive on boot with kernel > 2.6.24.3-50.fc8 | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | J (buggy) |
| Component: | IEEE1394 | Assignee: | Stefan Richter (stefanr) |
| Status: | CLOSED CODE_FIX | ||
| Severity: | high | CC: | devzero, naveed, stefanr |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | > 2.6.24.3-50.fc8 | Subsystem: | |
| Regression: | Yes | Bisected commit-id: | |
| Bug Depends on: | |||
| Bug Blocks: | 10492 | ||
| Attachments: | Diff -y on config-2.4.26.7 and config-2.4.26.7-92.fc8 | ||
|
Description
J
2008-05-25 12:36:01 UTC
Building kernel 2.6.24.4 directly from the .kernel.org website using the make instructions from the readme and the config info inherited from 2.4.6.24.3-50 - not altering anything in the menuconfig stage, gave me a kernel which I could boot with no keyboard issues and make nvidia drivers for - a usable kernel. I will try kernel 2.4.6.24.7 from the website and if that works it must be down to a fedora related patch/mod. I have now built the 2.6.24.7 kernel and booted successfully. This would therefore point the problem at one of the fedora patches added to the 2.6.24.7 kernel. I'll now go through their patches and remove them from the rpm src until I can find the one at fault. nice find ;) if this turns out to be a fedora issue - can't this be closed then ? I would suspect the answer is yes. Although I've found that you can't do make binrpm-pkg using the O option to specify an alternate path. If you do it fails to find the .config file. Instead you need to do make then make binrpm-pkg in the same src directory. It is also annoying that make install and make install_modules will create the *img file but the rpm doesn't. I don't suppose any of these comments really need to be in this bug? Before closing the bug would it be ok if I try and post the patch which is causing the fedora issue? There are 160 patches it may take me a while. Plus following the changelog comments makes it no easier a task. Before starting out on the patches I thought it would be worth comparing the 2.6.24.7 and 2.6.24.7-92 config files. (attached). Comparing this with the changelogs could activating I2C_PIIX4 be the culprit? Kernel.org Fedora # CONFIG_I2C_PIIX4 is not set | CONFIG_I2C_PIIX4=m I'll try the stock kernel with this turned on to see. Created attachment 16293 [details]
Diff -y on config-2.4.26.7 and config-2.4.26.7-92.fc8
Diff command run on the two config files used to make the kernel. The non-fedora one works while the fedora one kills the keyboard at boot.
I am having a similar issue, however I cannot even Ctrl-Alt-Del as the PS/2 keyboard is completely unresponsive after "Enabling /etc/fstab swaps: OK" and can only hard reset the box. See https://bugzilla.redhat.com/show_bug.cgi?id=444694 This may have been resolved. A patch has been put forward by the redhat/fedora guys it is suspected that the git firewire modules are to blame when coupled to a ALi firewire/usb combi card. adding blacklist firewire-ohci to /etc/modprobe.conf/blacklist allows the stock fedora kernel to boot. Likewise compiling the stock fedora kernel without the git firewire patches allows for a stable kernel. I think you can now close this. It is a regression in mainline too, post 2.6.25. Fix posted and verified with a newly acquired ALi based card: http://marc.info/?l=linux1394-devel&m=121380606431945 I will try to get it into mainline by the end of this week. Related: bug 10935 "fw-ohci: ALi M52xx unsupported" bug 10936 actually #-| no, 10935 Fix merged into upstream 2.6.26-rc7. J and Naveed, thanks for locating the source of the bug. Fixing it was easy after you did all the debugging work. |