Alan Stern wrote:
Yes, "could be". That'd be a case of DMA writing into some unexpectedOn Thu, 16 Jan 2003, Stephen Harker wrote:Trace; c013f258 <try_to_free_buffers+88/f0> Trace; c0133a67 <shrink_cache+217/300> Trace; c0133c95 <shrink_caches+55/90> Trace; c0133d03 <try_to_free_pages_zone+33/60> Trace; c0134c10 <balance_classzone+60/200> Trace; c0134e89 <__alloc_pages+d9/170> Trace; c012fcde <generic_file_write+32e/6d0> Trace; d080ec81 <[jbd].text.lock.journal+5ea5/14284> Trace; c013b314 <sys_write+84/100> Trace; c0108f03 <system_call+33/40>All that stuff about try_to_free_pages_zone, alloc_pages, and so on belongs to memory management. generic_file_write and text.lock.journal are part of ext3 (I think). However, it certainly could be that the ehci driver is causing a problem that doesn't show up until later.
location, which isn't at the top of my list of things I think would
be happening, but I'll check later.
- Dave
-------------------------------------------------------
This SF.NET email is sponsored by: Thawte.com
Understand how to protect your customers personal information by implementing
SSL on your Apache Web Server. Click here to get our FREE Thawte Apache Guide: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0029en
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
