Date: Wed, 5 Apr 2000 03:57:18 -0400 From: Christopher Masto <chris@netmonger.net> To: Nick Hibma <n_hibma@calcaphon.com>, Paul Haddad <paul@pth.com> Cc: FreeBSD CURRENT Mailing List <current@FreeBSD.ORG> Subject: Re: USB/Orb/kue/iopener/filesystem corruption Message-ID: <20000405035718.A9789@netmonger.net> In-Reply-To: <20000404184022.A15164@netmonger.net>; from Christopher Masto on Tue, Apr 04, 2000 at 06:40:22PM -0400 References: <008501bf9b84$ad365270$0bac2ac0@pth.com> <Pine.BSF.4.20.0004031057070.9381-100000@localhost> <20000403132725.B8685@netmonger.net> <20000404184022.A15164@netmonger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
For those following along, it's definately kue-related. On Tue, Apr 04, 2000 at 06:40:22PM -0400, Christopher Masto wrote: > Next time I get a chance, I'll try: > > Filesystem-intensive activity without using kue at all, then a > reboot and fsck. Tested, absolutely no problems. In fact, I'm writing this from the i-opener (running ppp). > Loading kue as a module. Same disaster. Instant filesystem damage if I use the maching at all with kue up. > Simulating the i-opener situation with my laptop. Haven't tried yet.. it's nearly 4AM. > Getting more details on the kernel panic. Haven't managed a panic this time around. I'm still stumped as to what exactly is going on.. whether kue is corrupting random memory, or umass's buffers.. I may just try to find an aue-based adapter to try. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000405035718.A9789>