|
Bugzilla – Full Text Bug Listing |
| Summary: | b43 drive works in default kernel but crashes desktop kernel | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.3 | Reporter: | Clark Tompsett <clarkt> |
| Component: | Kernel | Assignee: | E-mail List <kernel-maintainers> |
| Status: | RESOLVED DUPLICATE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | forgotten_CHC7OcAR44, jeffm, jslaby |
| Version: | Factory | ||
| Target Milestone: | --- | ||
| Hardware: | x86 | ||
| OS: | openSUSE 11.3 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
upstart + default kernel
infor from b43 kernel hang |
||
|
Description
Clark Tompsett
2010-05-20 13:18:03 UTC
Hrm. I'm unable to reproduce this on my system with 2.6.34-8-desktop. You can blacklist the module by adding a file, /etc/modprobe.d/b43-blacklist.conf that contains "blacklist b43" I'd like to try to capture the crash, though. Once you've blacklisted the module, boot into the desktop kernel. Then drop to console, run "klogconsole -r 0 -l 8" and then "modprobe b43". A digital photo is an easy way to capture it. Created attachment 366260 [details]
upstart + default kernel
upstart + default kernel output -- success
Created attachment 366261 [details]
infor from b43 kernel hang
message found from --
upstart + desktop kernel
sysvinit + default
sysvinit + desktop
With the update to sysvinit from today, default will load b43 but desktop still fails with b43. Additional information. If you boot to level 3 in default kernel, you can modprobe b43 and it will load. If you remove b43 and ssb from the blacklist then system hangs during boot. If you boot to level 5 and attempt to modprobe in a terminal window system locks. Problem appears to be the ssb driver that hangs system. Since I reported this bug, what do you want me to do? This seems to be a duplicate of bug 617912 *** This bug has been marked as a duplicate of bug 617912 *** |