On 18 Feb 2003 21:20:34 -0800, Steve Bangert wrote:

Hi.

> Hi Goran,
> 
>  Your not alone with regards to USB storage problems, You, myself and
> hundreds of other Linux USBers are having problems as well, the only
> thing i can suggest at this point is wait for 2.4.21-pre5 as there are
> some changes/fixes in the works. Good luck.

Ohh I know that - I am subscribed to the list for about two weeks now
and I can see the issues people are having. I wasn't asking fo ra fix or
anything, just an acknowledgement, something like "yeah, we're aware
about it", or "no, we won't fix it", or anything else.

It's not a big deal for me since I have a workaround, heck I would fix
it myself if I had more time and clues about USB internals.

Goran

> Steve
> 
> 
> 
> On Mon, 2003-02-17 at 22:12, Goran Koruga wrote:
> > 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 
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
> The most comprehensive and flexible code editor you can use.
> Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
> www.slickedit.com/sourceforge
> _______________________________________________
> [EMAIL PROTECTED]
> To unsubscribe, use the last form field at:
> https://lists.sourceforge.net/lists/listinfo/linux-usb-users


-- 
Goran Koruga                            [EMAIL PROTECTED]
HERMES Softlab, Litijska 51             phone: +386 1 586 5530
1000 Ljubljana, Slovenia


-------------------------------------------------------
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users

Reply via email to