Summary: | >=sys-fs/udev-103 causes console corruptions and boot failure | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Lincoln A Baxter <lab> |
Component: | [OLD] Core system | Assignee: | Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel> |
Status: | RESOLVED NEEDINFO | ||
Severity: | critical | CC: | base-system, udev-bugs |
Priority: | High | ||
Version: | 2006.1 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge --info output
dmesg output (describes hardware) (after down grading to udev-087 kernel configuration |
Description
Lincoln A Baxter
2006-12-22 14:12:39 UTC
Created attachment 104605 [details]
emerge --info output
*** Bug 158862 has been marked as a duplicate of this bug. *** Created attachment 104606 [details]
dmesg output (describes hardware) (after down grading to udev-087
Created attachment 104607 [details]
kernel configuration
I think your only problem is having the matrox-framebuffer-module in your kernel-config and not loading it. Newer udev-versions with enabled coldplug (/etc/conf.d/rc:RC_COLDPLUG=yes) try to load that module and *bang*. Just delete that module or blacklist it, or disable COLDPLUG. Then please add a comment on this bug. This bug could be related: http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=195761#c9 I think this bug is rather a kernel, and no udev issue. Reading the Redhat-Bug, this adding this to a file in /etc/modules.d/... could solve it: install matrox_w1 /bin/true Please comment if this works. I had this exact problem on a machine with a Matrox G450 card running a single monitor. The solution by Matthias Schwarzott in comment #5 works for me. Fortunately, although the screen was completely scrambled, the boot completed, so I was able to ssh in to the system to change /etc/conf.d/rc, then reboot with the screen intact. Of course, one finds this bug when rebooting, in this case after updating both udev to udev-103 and the kernel to vanilla-sources 2.6.17.13. Not too helpful in finding the source of the bug - sorry. After applying the above workaround, does running "modprobe --ignore-install matrox_w1" cause the bug to appear during standard system operation? This bug report indicates that there is a bug in matroxfb which causes the problems you have seen here. You didn't notice this before, because the driver wasn't loaded before, but newer udev loads it automatically. While there are workarounds above to prevent udev from loading the driver which avoid this problem, if you're interested in solving the actual matroxfb bug then please reopen this with the information requested in comment #9 |