Hide Forgot
Description of problem: Kernel panic - not syncing : map_single : buffer is not DMA'able PID 1100, comm: NetworkManager Not tainted 2.6.37-2.fc15.x86_64 #1 Call Trace ff...81475925 panic+0x91/0x1a4 8123bbba ?swtiotlb_map_page+0x8/0xcc 8123bcc7a swiotllb_map_page+0x8/oxcc a020dbc7 dma_map_single_attrs.close.36+06x/0x83 [b44] a020dad0 b44_alloc_rx_skb+0x7f/0x251 [b44] a020d0f0 b44_init_rings=0x93/0xa8 [b44] a020eb0c b44_open+ox263/0327 [b44] 813ce7b8 __dev_change_flags+0xad/ox131 813ce8bd dev_change_flags+0x21/0x57 Additional info: (Sorry, copied off the screen) The panic has been in all the 2.6.37 rawhide kernels I've tried, including the previous rc's. I also grepped the kernel mailing list for the last several weeks, but haven't seen a mention of a b44 problem.
I confirm this. As soon as /sbin/ifconfig puts eth0 up, the kernel panics. Dell Vostro laptop with broadcom ethernet card (b44 module) and vanilla 2.6.37 kernel.
Please attach the complete logs from booting the system with the failing kernel. You don't have to bring up the interface.
It panics and the boot log doesn't show anything. (I did try several times, and looked but no luck. That's why I resorted to copying and typing the panic message)
It doesn't panic when the module is loaded. I double-checked that booting single user. Modprobe-ing b44 is fine; it panics just when I issue "ifconfig eth0 up" (second time let some reasonable time after modprobe before bringing it up).
Same message as the original poster's: Kernel panic - not syncing : map_single : buffer is not DMA'able PID XXX, comm: ifconfig Not tainted 2.6.37-pf2 #2 x86_64 Call Trace [...] I know it's not fedora, but I couldn't find a bug report elsewhere and had it both with vanilla and stock archlinux kernel.
Please post the boot log from a successful boot without bringing up the interface. We need to see the messages printed during early boot when the software iommu loads.
Created attachment 473422 [details] dmesg from boot Dump of initial startup. Was obtained by booting single user and doing a dmesg. Didn't load b44 or ifup the interface.
PCI-DMA: Using software bounce buffering for IO (SWIOTLB) Placing 64MB software IO TLB between ffff8800db400000 - ffff8800df400000 software IO TLB at phys 0xdb400000 - 0xdf400000 So, the iotlb is above 1GB, but the b44 can only DMA to addresses below that. Does adding "iommu=soft" to the boot options make any difference?
I have almost the same dmesg (except for the address ranges starting at db600000). Appending "iommu=soft" doesn't help, it still panics on "ifconfig eth0 up".
Same result for me. Still panics.
Can someone try a 2.6.36 kernel to try and narrow down when this started happening? I tested 2.6.34 and 2.6.35 by forcibly enabling swiotlb and they were both OK. There's a 2.6.36 kernel for F15 here: http://koji.fedoraproject.org/koji/buildinfo?buildID=208434
That's the last kernel that worked for me. The problem started with the very first 2.6.37 kernel.
(In reply to comment #12) > That's the last kernel that worked for me. The problem started with the very > first 2.6.37 kernel. Can you find the lines like the ones in comment #8 from the 2.6.36 boot messages and post them here?
2.6.36 is fine, here's my relevant boot messages: PCI-DMA: Using software bounce buffering for IO (SWIOTLB) Placing 64MB software IO TLB between ffff880005c00000 - ffff880009c00000 software IO TLB at phys 0x5c00000 - 0x9c00000
I applied the patch proposed at http://groups.google.com/group/linux.kernel/browse_thread/thread/184c7cd190ae7b5a?pli=1 and it works. PCI-DMA: Using software bounce buffering for IO (SWIOTLB) Placing 64MB software IO TLB between ffff8800db600000 - ffff8800df600000 software IO TLB at phys 0xdb600000 - 0xdf600000
Package kernel-2.6.38-0.rc6.git6.1.fc15: * should fix your issue, * was pushed to the Fedora 15 updates-testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing kernel-2.6.38-0.rc6.git6.1.fc15' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/kernel-2.6.38-0.rc6.git6.1.fc15 then log in and leave karma (feedback).
This fixes the problem for me. Modprobing b44 doesn't cause a panic any more.
kernel-2.6.38-0.rc6.git6.1.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 695370 has been marked as a duplicate of this bug. ***