FS#17551 - [kernel26] Can't mount USB device with DMA

Attached to Project: Arch Linux
Opened by Dan Vratil (progdan) - Saturday, 19 December 2009, 20:41 GMT
Last edited by Tobias Powalowski (tpowa) - Friday, 08 January 2010, 08:09 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No


When USB device with MDA support (mp3 player for example) is plugged in, dmesg outputs:

usb 5-1: new full speed USB device using uhci_hcd and address 4
usb 5-1: configuration #1 chosen from 1 choice
usb_storage: Unknown symbol scsi_add_host_with_dma

Function scsi_add_host_with_dma was introduced in I don't know if it is a bug in upstream or in our package. But better to start down here. Maybe something must be changed in kernel config?

Steps to reproduce:
Take some device with DMA, plug it in and look into dmesg.
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Friday, 08 January 2010, 08:09 GMT
Reason for closing:  Fixed
Comment by Jan de Groot (JGC) - Saturday, 19 December 2009, 20:47 GMT
Did you actually reboot into after updating it, or do you still run 2.6.32?

http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.32.y.git;a=commit;h=d888b1a2d5c7a9fbdc01e7395ea6a8d75cd729f5 changed the scsi module a bit, so isn't compatible with 2.6.32 modules. If you happen to have 2.6.32 loaded and try to load scsi modules, you'll get unresolved symbols.
Comment by Dan Vratil (progdan) - Saturday, 19 December 2009, 20:54 GMT
Yes I did. I updated to already 3 days ago.
Comment by Jan de Groot (JGC) - Saturday, 19 December 2009, 21:00 GMT
But was your system rebooted after that?
Comment by Dan Vratil (progdan) - Saturday, 19 December 2009, 21:07 GMT
Sure it was.
Comment by Tom Killian (tomk) - Friday, 25 December 2009, 17:17 GMT
  • Field changed: Percent Complete (100% → 0%)
Still getting this error with
Comment by Dan Vratil (progdan) - Friday, 25 December 2009, 22:22 GMT
I'm not sure if it is related (and I can't verify it now), but I rebuilt udev from sources. But I rebooted first after updating the kernel to, so I can't say if rebuilding udev did or didn't help, but anyway - you can try :-)
Comment by Tom Killian (tomk) - Sunday, 27 December 2009, 03:37 GMT
I'm running now, still getting the error.

Can this be reassigned? It's nobody's right now.
Comment by Tom Killian (tomk) - Monday, 04 January 2010, 22:29 GMT
Finally got some time to poke at this a bit more, and found that it only happens when I start radeon kms in the initramfs. Disabling kms, or starting it from rc.conf, makes this problem disappear.

A bit more digging revealed that it was the particular "early kms" workaround that I was using that was the problem i.e. the one with the custom radeon hook, as described here: http://bbs.archlinux.org/viewtopic.php?id=86211. Changing to tpowa's workaround ( FS#17461 ) for early kms also made the usb problem go away.

I have no idea why the radeon kms start method would cause an Unknown symbol error in the usb-storage module, but I now have both early radeon kms AND usb storage working again, so I'm happy. :)

As I asked for this to be reopened, I guess I should now say that it can be closed (again) - unless, of course, anyone wants to track down the exact cause of the problem.