L4Linux and USB mass storage
Adam Lackorzynski
adam at os.inf.tu-dresden.de
Tue Sep 26 19:00:05 CEST 2006
On Tue Sep 26, 2006 at 17:54:54 +0200, Andreas Niederl wrote:
> I'm having problems using a USB connected mass storage device with
> L4Linux. On device detection an out of memory error happens when the
> cache is allocated:
>
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> Waiting 15sec before mounting root device...
> l4lx | l4lx_thread_create: Created thread 0e.0c (IRQ1)
> input: AT Translated Set 2 keyboard as /class/input/input0
> logips2pp: Detected unknown logitech mouse model 1
> input: PS/2 Logitech Mouse as /class/input/input1
> Vendor: ST325082 Model: 3AS Rev:
> Type: Direct-Access ANSI SCSI revision: 02
> oom-killer: gfp_mask=0xd1, order=0
> <0040a605> show_trace+0x15/0x20 <0040a6f7> dump_stack+0x17/0x20
> <0043227b> out_of_memory+0x6b/0x90 <0043336c> __alloc_pages+0x26c/0x2a0
> <004469d4> kmem_getpages+0x34/0xa0 <00447689> cache_grow+0x99/0x180
> <004478ed> cache_alloc_refill+0x17d/0x1c0 <00447af8>
> kmem_cache_alloc+0x48/0x5
> 0
> <00571fbc> sd_revalidate_disk+0x2c/0x100 <005722ad> sd_probe+0x21d/0x310
> <00512244> driver_probe_device+0x54/0xb0 <005122b0>
> __device_attach+0x10/0x20
> <005118db> bus_for_each_drv+0x4b/0x70 <00512314> device_attach+0x54/0x60
> <00511a05> bus_add_device+0x25/0x90 <00510a5a> device_add+0xda/0x160
> <0056da33> scsi_sysfs_add_sdev+0x33/0x180 <0056bef9>
> scsi_add_lun+0x199/0x360
> <0056c1db> scsi_probe_and_add_lun+0x11b/0x200 <0056c9b1>
> __scsi_scan_target+0xa1/0xe0
> <0056caec> scsi_scan_channel+0x6c/0x90 <0056cb76>
> scsi_scan_host_selected+0x66/0xb0
> <0056cbd4> scsi_scan_host+0x14/0x20 <00594dee>
> usb_stor_scan_thread+0x4e/0x150
> <00424994> kthread+0x94/0xc0 <00407619> kernel_thread_start+0x29/0x30
> <004075ee> ret_kernel_thread_start+0x6/0x8
>
> I'm using L4Linux-2.6.17 and tried it on a machine with 512MB memory
> with 256MB reserved for L4Linux as well as on a machine with 1GB memory
> and 768MB for L4Linux. Delaying the device detection by booting into a
> Ramdisk and then loading the respective modules and udev resulted in the
> same behaviour.
>
> Has anybody else experienced such problems when using USB disks with
> L4Linux?
I guess this one also applies for USB storage.
http://os.inf.tu-dresden.de/L4/LinuxOnL4/faq.shtml#gfpdmamemory
Adam
--
Adam adam at os.inf.tu-dresden.de
Lackorzynski http://os.inf.tu-dresden.de/~adam/
More information about the l4-hackers
mailing list