FS#22709 - [kernel26] 2.6.37-5 Kernel panic on boot -

Attached to Project: Arch Linux
Opened by Pafrapé (Pafrapé) - Tuesday, 01 February 2011, 22:52 GMT
Last edited by Vesa Kaihlavirta (vegai) - Sunday, 13 March 2011, 11:27 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture All
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

After updating the kernel that is passed to version 2.6.37-5, a kernel panic appears at startup.
This problem is due to an incompatibility between some NICs (Broadcom,...) and the new kernel.

Here is the message kernel panic:

kernel panic - not syncing: map_single: bounce buffer is not DMA'ble
Pid: 1347, comm: ifconfig Not tainted 2.6.37-ARCH #1
Call trace:
...
panic occured, switching back tot text console
This task depends upon

Closed by  Vesa Kaihlavirta (vegai)
Sunday, 13 March 2011, 11:27 GMT
Reason for closing:  Fixed
Comment by Dashkal (Dashkal) - Thursday, 03 February 2011, 20:49 GMT
I have this as well. The actual kernel panic for me is when wicd starts and engages the network card.
Comment by Al (epikal) - Friday, 04 February 2011, 00:56 GMT
I can confirm same issue with b43 for Broadcom BCM4306/3 14e4:4320.
Comment by Thomas Dziedzic (tomd123) - Saturday, 05 February 2011, 02:18 GMT
I know this is broadcom, but it would be nice if everyone posted the device descriptions also
Comment by Thomas Dziedzic (tomd123) - Saturday, 05 February 2011, 02:25 GMT
Never mind...

Please try the patch proposed in one of the links. It will most likely fix your issue.

Relevant upstream bug report: https://bugzilla.kernel.org/show_bug.cgi?id=25402

Links on the kernel bug:
Redhat bug link: https://bugzilla.redhat.com/show_bug.cgi?id=668088
Google group link: http://groups.google.com/group/linux.kernel/browse_thread/thread/184c7cd190ae7b5a?pli=1
Comment by Thomas Dziedzic (tomd123) - Saturday, 05 February 2011, 02:25 GMT
Also, please comment upstream about your experience, as the bug report seems to have lost some steam.
Comment by Al (epikal) - Sunday, 06 February 2011, 18:27 GMT
Patch resolves issue for b43, updated upstream bug report.
Comment by Pafrapé (Pafrapé) - Friday, 11 February 2011, 21:04 GMT
It seems that the problem can be solved by applying the following patch:

https://bugzilla.kernel.org/show_bug.cgi?id=25402

Comment by Ajibola (okubax) - Wednesday, 09 March 2011, 14:37 GMT
The kernel update 'kernel26 2.6.37.3-1' seems to have solved this issue. I applied the latest update and re-installed 'broadcom-wl' from AUR, now my wireless works as normal with no kernel panic.

Mark as solved

Loading...