Hi. I have already posted this before but received no replies. I can't believe no-one cares about this issue, although it's not quite as bad as it could be.
----------------------------------------------------------- I have a major issue with USB mass storage support on my system. I am able to reproduce the problem with 2.4.20 and 2.4.21-pre4 kernels. I have tried -pre4 kernel because it has quite a few USB mass storage fixes mentioned in the changelog. First I will described the hardware. I am using Chaintech 7VJL Apogee motherboard with VIA KT333 chipset (more info here : http://www.chaintech.com.tw/eng/products/SOCKA/7vjl.asp). The USB mass storage device involved is CoolDisk 64M (http://www.z-cyber.net). I have attached the oops message as printed by the kernel (I had to type it by hand since it happens in interrupt handler and it doesn't get written to disk). I have also attached ksymoops report for this message as well as my kernel config. The oops occurs after the modules get loaded and I don't even have to do anything, it just happens. I am loading the following modules (in this order) : sd_mod usb-uhci usb-storage What's weird is, that the kernel oops-es only if my USB mass storage device is connected at boot. If I disconnect the device, boot the system and wait a while and then connect it, kernel works OK. Is this a known problem ? Are there any fixes already available that are not in official kernels ? I hope I have included enough info for someone to depict the problem (I tried to take a look at the code but it's not some trivial issue so I gave up - I would have to study too much code to understand how it works). Thank you and kind regards, Goran PS. Sorry for the URL spam - I have included that to avoid any confusion. -- Writing about music is like dancing about architecture. -- Frank Zappa
oops.debug-2.4.21
Description: Binary data
usboops.log-2.4.21
Description: Binary data
config-2.4.21
Description: Binary data
