Date: Mon, 3 Apr 2000 10:57:46 +0100 (BST) From: Nick Hibma <n_hibma@calcaphon.com> To: Paul Haddad <paul@pth.com> Cc: Christopher Masto <chris@netmonger.net>, FreeBSD CURRENT Mailing List <current@freebsd.org> Subject: Re: Another current crash (cvs-cur.6183 Message-ID: <Pine.BSF.4.20.0004031057070.9381-100000@localhost> In-Reply-To: <008501bf9b84$ad365270$0bac2ac0@pth.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Where are you guys now as far as USB drives are concerned? I've been
looking a lot at the driver lately and would like to hear about any
problems you have.
Nick
On Fri, 31 Mar 2000, Paul Haddad wrote:
> Hi,
>
> Boy I wish I had read this message before I went out and bought a USB zip
> drive... I'm in the exact same situation IOPENER with 4.0 installed and
> screwed up to a point where I can boot but not mount the sandisk drive. I
> figured that I would get a zip drive and mount it instead.
>
> Anyways if you found some way around this please let me know, otherwise I've
> got to make another trip out and get a SuperDisk instead...
>
> BTW What state are you in? Mine will boot, but gets to the point where it
> tries to mount the sandisk and panics with a ffs_write panic. Booting in
> single user doesn't help.
> ---
> Paul Haddad (paul@pth.com)
> Imagine that Cray computer decides to make a personal computer. It has
> a 150 MHz processor, 200 megabytes of RAM, 1500 megabytes of disk
> storage, a screen resolution of 4096 x 4096 pixels, relies entirely on
> voice recognition for input, fits in your shirt pocket and costs $300.
> What's the first question that the computer community asks?
>
> "Is it PC compatible?"
>
> ----- Original Message -----
> From: "Christopher Masto" <chris@netmonger.net>
> To: "Paul Richards" <paul@originative.co.uk>; "Stephen Hocking-Senior
> Programmer PGS SPS Perth" <shocking@prth.pgs.com>
> Cc: <current@FreeBSD.ORG>; <poul@FreeBSD.ORG>
> Sent: Wednesday, March 22, 2000 12:16 AM
> Subject: Re: Another current crash (cvs-cur.6183
>
>
> > On Wed, Mar 22, 2000 at 03:02:02AM +0000, Paul Richards wrote:
> > > I've got a different but I think related panic.
> > >
> > > #9 0xc0143280 in panic (fmt=0xc0250460 "vm_page_wakeup: page not
> > > busy!!!")
> > > at ../../kern/kern_shutdown.c:552
> > > #10 0xc01df583 in swp_pager_async_iodone (bp=0xc3236250)
> > > at ../../vm/vm_page.h:346
> >
> > I've been playing around with one of those iopener things and got
> > myself into a state I thought I could get out of with the help of a
> > USB Zip drive. Unfortunately, upon purchasing and connecting one,
> > I discovered that I can't access it without a panic, which I
> > point out here on the chance it's also related.
> >
> > #7 0xc024ac2c in trap (frame={tf_fs = 16, tf_es = 16, tf_ds = 16,
> > tf_edi = -1018879976, tf_esi = 256, tf_ebp = -919618472, tf_isp
> = -919618500,
> > tf_ebx = -1071201278, tf_edx = 0, tf_ecx = -1070746656, tf_eax = 18,
> > tf_trapno = 3, tf_err = 0, tf_eip = -1071396739, tf_cs = 8,
> tf_eflags = 582,
> > tf_esp = -1071099905, tf_ss = -1071212893}) at
> ../../i386/i386/trap.c:549
> > #8 0xc023c87d in Debugger (msg=0xc02696a3 "panic") at
> machine/cpufunc.h:64
> > #9 0xc01549e8 in panic (fmt=0xc026c402 "allocbuf: buffer too small")
> > at ../../kern/kern_shutdown.c:552
> > #10 0xc0178f5a in allocbuf (bp=0xc3452018, size=83886080) at
> ../../kern/vfs_bio.c:2346
> > #11 0xc0178f01 in geteblk (size=83886080) at ../../kern/vfs_bio.c:2315
> > #12 0xc025cb57 in dsinit (dev=0xc0be1e00, lp=0xc0c490f4, sspp=0xc0c490f0)
> > at ../../kern/subr_diskmbr.c:186
> > #13 0xc015eec6 in dsopen (dev=0xc0be1e00, mode=8192, flags=0,
> sspp=0xc0c490f0,
> > lp=0xc0c490f4) at ../../kern/subr_diskslice.c:683
> > #14 0xc015dfbf in diskopen (dev=0xc0be1e00, oflags=1, devtype=8192,
> p=0xc88be860)
> > at ../../kern/subr_disk.c:146
> > #15 0xc018ae65 in spec_open (ap=0xc92fbe10) at
> ../../miscfs/specfs/spec_vnops.c:191
> > #16 0xc018ad65 in spec_vnoperate (ap=0xc92fbe10)
> > at ../../miscfs/specfs/spec_vnops.c:117
> > #17 0xc01ff2e9 in ufs_vnoperatespec (ap=0xc92fbe10) at
> ../../ufs/ufs/ufs_vnops.c:2301
> > #18 0xc018595f in vn_open (ndp=0xc92fbedc, fmode=1, cmode=0) at
> vnode_if.h:189
> > #19 0xc0181951 in open (p=0xc88be860, uap=0xc92fbf80) at
> ../../kern/vfs_syscalls.c:994
> > #20 0xc024b4ce in syscall (frame={tf_fs = 47, tf_es = 47, tf_ds = 47,
> > tf_edi = -1077937212, tf_esi = 134894800, tf_ebp = -1077937132,
> > tf_isp = -919617580, tf_ebx = 0, tf_edx = 8, tf_ecx = 134894828,
> tf_eax = 5,
> > tf_trapno = 12, tf_err = 2, tf_eip = 672026540, tf_cs = 31,
> tf_eflags = 642,
> > tf_esp = -1077937316, tf_ss = 47}) at ../../i386/i386/trap.c:1073
> > #21 0xc023cf26 in Xint0x80_syscall ()
> >
> > I'm not intimately familiar with the function involved, and I'm out of
> > time tonight, so I'm backing up a few days to see if it goes away.
> > --
> > 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
> >
> >
>
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
--
n_hibma@webweaving.org
n_hibma@freebsd.org USB project
http://www.etla.net/~n_hibma/
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?Pine.BSF.4.20.0004031057070.9381-100000>