Re: Panic with usb serial
Kostik Belousov wrote: > On Wed, Apr 02, 2008 at 10:50:39AM +0100, Vince Hoffman wrote: >> Kostik Belousov wrote: >>> On Tue, Apr 01, 2008 at 09:55:19AM +0100, Vince Hoffman wrote: Kostik Belousov wrote: > On Mon, Mar 31, 2008 at 12:13:31PM +0100, Vince Hoffman wrote: >> Kostik Belousov wrote: > Compile the ddb into the kernel (instructions are provided at the same > web page) and post the output of the console on the panic I tried this but other than the fact I can drop into ddb and step though stuff I'm not sure what I can do with it. Since I cant (obviously) get a serial console on my laptop I have done it the other way and taken a picture of the console on panic. When I have more time I'll carry on reading up on ddb but I think I have a steep learning curve since my previous looks at programing stopped at 'hello world':) Panic console at: http://unsane.co.uk/~jhary/freebsd/IMAGE_119.jpg >>> Thanks, this is enough. Two chunks were missed from the rev. 1.210. >>> Please, try the patch below. >>> >>> diff --git a/sys/kern/kern_conf.c b/sys/kern/kern_conf.c >>> index 843498e..7e6e048 100644 >>> --- a/sys/kern/kern_conf.c >>> +++ b/sys/kern/kern_conf.c >>> @@ -402,8 +402,7 @@ giant_ioctl(struct cdev *dev, u_long cmd, caddr_t data, >>> int fflag, struct thread >>> if (dsw == NULL) >>> return (ENXIO); >>> mtx_lock(&Giant); >>> - retval = dev->si_devsw->d_gianttrick-> >>> - d_ioctl(dev, cmd, data, fflag, td); >>> + retval = dsw->d_gianttrick->d_ioctl(dev, cmd, data, fflag, td); >>> mtx_unlock(&Giant); >>> dev_relthread(dev); >>> return (retval); >>> @@ -419,8 +418,7 @@ giant_read(struct cdev *dev, struct uio *uio, int >>> ioflag) >>> if (dsw == NULL) >>> return (ENXIO); >>> mtx_lock(&Giant); >>> - retval = dev->si_devsw->d_gianttrick-> >>> - d_read(dev, uio, ioflag); >>> + retval = dsw->d_gianttrick->d_read(dev, uio, ioflag); >>> mtx_unlock(&Giant); >>> dev_relthread(dev); >>> return (retval); >> Hi Kostik, >> Yes this stops the panic. I do still get the console spammed with >> informational messages >> >> Apr 2 10:36:30 prawn kernel: ucom0: > 0/0, rev 1.10/4.00, addr 3> on uhub2 >> Apr 2 10:36:33 prawn login: ROOT LOGIN (toor) ON ttyv0 >> Apr 2 10:36:56 prawn kernel: ucom0: ucomreadcb: IOERROR >> Apr 2 10:36:56 prawn kernel: ucom0: at uhub2 port 1 (addr 3) disconnected >> Apr 2 10:36:57 prawn kernel: Still 4294967295 threads in ttyU0 >> Apr 2 10:37:16 prawn last message repeated 188 times >> Apr 2 10:37:16 prawn login: ROOT LOGIN (toor) ON ttyv1 >> Apr 2 10:37:16 prawn kernel: Still 4294967295 threads in ttyU0 >> Apr 2 10:37:47 prawn last message repeated 303 times >> Apr 2 10:37:55 prawn last message repeated 85 times >> >> >> but I can live with that. >> >> I had opened PR usb/122287 for this, and I have updated this with the >> relevent information from this thread. > > I committed the fix to the HEAD. I tested the patch with the uark(4) > cable, and simply running the tip over the ttyU0 did not produced the > "Still -1 threads in ttyU0" message. Are you running tip, or something > else over the port ? > Just tip. [~](12:30:32) [EMAIL PROTECTED] usb0 /etc/remote usb0:dv=/dev/ttyU0:br#9600:pa=none: then [~](12:31:20) [EMAIL PROTECTED] usb0 connected Router> then unplugged the usb adapter Vince ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Panic with usb serial
On Wed, Apr 02, 2008 at 10:50:39AM +0100, Vince Hoffman wrote: > Kostik Belousov wrote: > > On Tue, Apr 01, 2008 at 09:55:19AM +0100, Vince Hoffman wrote: > >> Kostik Belousov wrote: > >>> On Mon, Mar 31, 2008 at 12:13:31PM +0100, Vince Hoffman wrote: > Kostik Belousov wrote: > >>> Compile the ddb into the kernel (instructions are provided at the same > >>> web page) and post the output of the console on the panic > >> I tried this but other than the fact I can drop into ddb and step though > >> stuff I'm not sure what I can do with it. Since I cant (obviously) get a > >> serial console on my laptop I have done it the other way and taken a > >> picture of the console on panic. When I have more time I'll carry on > >> reading up on ddb but I think I have a steep learning curve since my > >> previous looks at programing stopped at 'hello world':) > >> Panic console at: > >> http://unsane.co.uk/~jhary/freebsd/IMAGE_119.jpg > > > > Thanks, this is enough. Two chunks were missed from the rev. 1.210. > > Please, try the patch below. > > > > diff --git a/sys/kern/kern_conf.c b/sys/kern/kern_conf.c > > index 843498e..7e6e048 100644 > > --- a/sys/kern/kern_conf.c > > +++ b/sys/kern/kern_conf.c > > @@ -402,8 +402,7 @@ giant_ioctl(struct cdev *dev, u_long cmd, caddr_t data, > > int fflag, struct thread > > if (dsw == NULL) > > return (ENXIO); > > mtx_lock(&Giant); > > - retval = dev->si_devsw->d_gianttrick-> > > - d_ioctl(dev, cmd, data, fflag, td); > > + retval = dsw->d_gianttrick->d_ioctl(dev, cmd, data, fflag, td); > > mtx_unlock(&Giant); > > dev_relthread(dev); > > return (retval); > > @@ -419,8 +418,7 @@ giant_read(struct cdev *dev, struct uio *uio, int > > ioflag) > > if (dsw == NULL) > > return (ENXIO); > > mtx_lock(&Giant); > > - retval = dev->si_devsw->d_gianttrick-> > > - d_read(dev, uio, ioflag); > > + retval = dsw->d_gianttrick->d_read(dev, uio, ioflag); > > mtx_unlock(&Giant); > > dev_relthread(dev); > > return (retval); > > Hi Kostik, > Yes this stops the panic. I do still get the console spammed with > informational messages > > Apr 2 10:36:30 prawn kernel: ucom0: 0/0, rev 1.10/4.00, addr 3> on uhub2 > Apr 2 10:36:33 prawn login: ROOT LOGIN (toor) ON ttyv0 > Apr 2 10:36:56 prawn kernel: ucom0: ucomreadcb: IOERROR > Apr 2 10:36:56 prawn kernel: ucom0: at uhub2 port 1 (addr 3) disconnected > Apr 2 10:36:57 prawn kernel: Still 4294967295 threads in ttyU0 > Apr 2 10:37:16 prawn last message repeated 188 times > Apr 2 10:37:16 prawn login: ROOT LOGIN (toor) ON ttyv1 > Apr 2 10:37:16 prawn kernel: Still 4294967295 threads in ttyU0 > Apr 2 10:37:47 prawn last message repeated 303 times > Apr 2 10:37:55 prawn last message repeated 85 times > > > but I can live with that. > > I had opened PR usb/122287 for this, and I have updated this with the > relevent information from this thread. I committed the fix to the HEAD. I tested the patch with the uark(4) cable, and simply running the tip over the ttyU0 did not produced the "Still -1 threads in ttyU0" message. Are you running tip, or something else over the port ? pgpxbBLK5HU4Y.pgp Description: PGP signature
Re: Panic with usb serial
Kostik Belousov wrote: > On Tue, Apr 01, 2008 at 09:55:19AM +0100, Vince Hoffman wrote: >> Kostik Belousov wrote: >>> On Mon, Mar 31, 2008 at 12:13:31PM +0100, Vince Hoffman wrote: Kostik Belousov wrote: >>> Compile the ddb into the kernel (instructions are provided at the same >>> web page) and post the output of the console on the panic >> I tried this but other than the fact I can drop into ddb and step though >> stuff I'm not sure what I can do with it. Since I cant (obviously) get a >> serial console on my laptop I have done it the other way and taken a >> picture of the console on panic. When I have more time I'll carry on >> reading up on ddb but I think I have a steep learning curve since my >> previous looks at programing stopped at 'hello world':) >> Panic console at: >> http://unsane.co.uk/~jhary/freebsd/IMAGE_119.jpg > > Thanks, this is enough. Two chunks were missed from the rev. 1.210. > Please, try the patch below. > > diff --git a/sys/kern/kern_conf.c b/sys/kern/kern_conf.c > index 843498e..7e6e048 100644 > --- a/sys/kern/kern_conf.c > +++ b/sys/kern/kern_conf.c > @@ -402,8 +402,7 @@ giant_ioctl(struct cdev *dev, u_long cmd, caddr_t data, > int fflag, struct thread > if (dsw == NULL) > return (ENXIO); > mtx_lock(&Giant); > - retval = dev->si_devsw->d_gianttrick-> > - d_ioctl(dev, cmd, data, fflag, td); > + retval = dsw->d_gianttrick->d_ioctl(dev, cmd, data, fflag, td); > mtx_unlock(&Giant); > dev_relthread(dev); > return (retval); > @@ -419,8 +418,7 @@ giant_read(struct cdev *dev, struct uio *uio, int ioflag) > if (dsw == NULL) > return (ENXIO); > mtx_lock(&Giant); > - retval = dev->si_devsw->d_gianttrick-> > - d_read(dev, uio, ioflag); > + retval = dsw->d_gianttrick->d_read(dev, uio, ioflag); > mtx_unlock(&Giant); > dev_relthread(dev); > return (retval); Hi Kostik, Yes this stops the panic. I do still get the console spammed with informational messages Apr 2 10:36:30 prawn kernel: ucom0: on uhub2 Apr 2 10:36:33 prawn login: ROOT LOGIN (toor) ON ttyv0 Apr 2 10:36:56 prawn kernel: ucom0: ucomreadcb: IOERROR Apr 2 10:36:56 prawn kernel: ucom0: at uhub2 port 1 (addr 3) disconnected Apr 2 10:36:57 prawn kernel: Still 4294967295 threads in ttyU0 Apr 2 10:37:16 prawn last message repeated 188 times Apr 2 10:37:16 prawn login: ROOT LOGIN (toor) ON ttyv1 Apr 2 10:37:16 prawn kernel: Still 4294967295 threads in ttyU0 Apr 2 10:37:47 prawn last message repeated 303 times Apr 2 10:37:55 prawn last message repeated 85 times but I can live with that. I had opened PR usb/122287 for this, and I have updated this with the relevent information from this thread. Thanks, Vince ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Panic with usb serial
In message: <[EMAIL PROTECTED]> "M. Warner Losh" <[EMAIL PROTECTED]> writes: : In message: <[EMAIL PROTECTED]> : Jeremy Chadwick <[EMAIL PROTECTED]> writes: : : On Sat, Mar 29, 2008 at 10:11:04PM +, Vince wrote: : : > Is it expected that removing a usb serial adapter while you have a : : > connection (eg tip) using it will panic a -stable system? I know it is : : > expected if you remove a mounted umass device so wanted to see if its known : : > behavior for serial before I file a pr. (adapter is converter, class 0/0, rev 1.10/4.00, addr 3>) : : > -stable version as of the 25th march, (may have existed before but the : : > first time I forgot to close tip before removing the device was on this : : > version.) : : : : I would expect that the problem is identical in the sense that with a : : connection established, you have an open file descriptor which is : : associated with a serial device that uses USB. : : : : So, yes, I would expect this behaviour based on the track record. : : Should it happen? The answer is no. File a PR? : : : : Also, I'd like to know what USB serial adapter you're using (brand, : : model, and a website of it if possible), for unrelated reasons. Thanks! : : That's odd, because I use an FTDI based serial device all the time for : hacking on embedded systems. The problem that I have is 100% CPU : usage on a tip process until I kill it. Actually, the reason for this is that I fixed a bug that gave me panics... During the review process, it was pointed out that others had better changes. These have been included in -current, but I don't think have been merged back to RELENG_7 yet. They aren't in 7.0. warner ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Panic with usb serial
On Tue, Apr 01, 2008 at 09:55:19AM +0100, Vince Hoffman wrote: > Kostik Belousov wrote: > > On Mon, Mar 31, 2008 at 12:13:31PM +0100, Vince Hoffman wrote: > >> Kostik Belousov wrote: > > > Compile the ddb into the kernel (instructions are provided at the same > > web page) and post the output of the console on the panic > > I tried this but other than the fact I can drop into ddb and step though > stuff I'm not sure what I can do with it. Since I cant (obviously) get a > serial console on my laptop I have done it the other way and taken a > picture of the console on panic. When I have more time I'll carry on > reading up on ddb but I think I have a steep learning curve since my > previous looks at programing stopped at 'hello world':) > Panic console at: > http://unsane.co.uk/~jhary/freebsd/IMAGE_119.jpg Thanks, this is enough. Two chunks were missed from the rev. 1.210. Please, try the patch below. diff --git a/sys/kern/kern_conf.c b/sys/kern/kern_conf.c index 843498e..7e6e048 100644 --- a/sys/kern/kern_conf.c +++ b/sys/kern/kern_conf.c @@ -402,8 +402,7 @@ giant_ioctl(struct cdev *dev, u_long cmd, caddr_t data, int fflag, struct thread if (dsw == NULL) return (ENXIO); mtx_lock(&Giant); - retval = dev->si_devsw->d_gianttrick-> - d_ioctl(dev, cmd, data, fflag, td); + retval = dsw->d_gianttrick->d_ioctl(dev, cmd, data, fflag, td); mtx_unlock(&Giant); dev_relthread(dev); return (retval); @@ -419,8 +418,7 @@ giant_read(struct cdev *dev, struct uio *uio, int ioflag) if (dsw == NULL) return (ENXIO); mtx_lock(&Giant); - retval = dev->si_devsw->d_gianttrick-> - d_read(dev, uio, ioflag); + retval = dsw->d_gianttrick->d_read(dev, uio, ioflag); mtx_unlock(&Giant); dev_relthread(dev); return (retval); pgpNHUMzsX4dE.pgp Description: PGP signature
Re: Panic with usb serial
Kostik Belousov wrote: > On Mon, Mar 31, 2008 at 12:13:31PM +0100, Vince Hoffman wrote: >> Kostik Belousov wrote: > Compile the ddb into the kernel (instructions are provided at the same > web page) and post the output of the console on the panic I tried this but other than the fact I can drop into ddb and step though stuff I'm not sure what I can do with it. Since I cant (obviously) get a serial console on my laptop I have done it the other way and taken a picture of the console on panic. When I have more time I'll carry on reading up on ddb but I think I have a steep learning curve since my previous looks at programing stopped at 'hello world':) Panic console at: http://unsane.co.uk/~jhary/freebsd/IMAGE_119.jpg Vince ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Panic with usb serial
On Mon, Mar 31, 2008 at 12:13:31PM +0100, Vince Hoffman wrote:
> Kostik Belousov wrote:
> > On Mon, Mar 31, 2008 at 09:48:55AM +0100, Vince Hoffman wrote:
> >> Marcin Cieslak wrote:
> >>> Vince wrote:
> Jeremy Chadwick wrote:
> Regarding the USB serial adapter, I was supplied it though work a while
> back. I believe from my rather fuzzy memory we got it though these guys
> http://www.usbnow.co.uk/Cables-USB_to_RS232_Cables/c1_23/index.html
> Although I wouldn't swear to it. I'll have an ask if anyone remembers on
> monday.
> >>> Can you post a fragment of dmesg output? I am interested whether you
> >>> attach it to the ohci or uhci controller.
> >>>
> >>> --Marcin
> >>>
> >> Sure,
> >> Please not this is now a different usb adapter as I left mine at home :(
> >> but I just tested and it exhibits the same behavior, (only difference I
> >> can see is this says its FIDI while my one says its FTDI, possibly a typo?)
> >>
> >> [EMAIL PROTECTED] | grep uhub
> >> uhub0: on usb0
> >> uhub0: 2 ports with 2 removable, self powered
> >> uhub1: on usb1
> >> uhub1: 2 ports with 2 removable, self powered
> >> uhub2: on usb2
> >> uhub2: 2 ports with 2 removable, self powered
> >> uhub3: on usb3
> >> uhub3: 2 ports with 2 removable, self powered
> >> uhub4: on usb4
> >> uhub4: 8 ports with 8 removable, self powered
> >> umass0: >> 2.00/0.01, addr 2> on uhub4
> >> ums0:
> >> on uhub2
> >> ucom0: on
> >> uhub2
> >>
> >> And for what its worth:
> >> [EMAIL PROTECTED] /var/crash/info.14
> >> Dump header from device /dev/ad0s3b
> >> Architecture: i386
> >> Architecture Version: 2
> >> Dump Length: 154411008B (147 MB)
> >> Blocksize: 512
> >> Dumptime: Mon Mar 31 09:25:54 2008
> >> Hostname: prawn.unsane.co.uk
> >> Magic: FreeBSD Kernel Dump
> >> Version String: FreeBSD 7.0-STABLE #52: Tue Mar 25 13:45:50 GMT 2008
> >> [EMAIL PROTECTED]:/usr/local/obj/usr/src/sys/PRAWN7ULE
> >> Panic String: page fault
> >> Dump Parity: 1302845723
> >> Bounds: 14
> >> Dump Status: good
> >>
> >> Happy to provide more information but I'm not a programmer so you'll
> >> probably have to ask me slowly and in words of one syllable ;)
> >
> > I need two things:
> > 1. The revision of the sys/kern/kern_conf.c file; in particular,
> >I need to know whether you have rev. 1.208.2.1 or 1.208.2.2.
> > 2. Regardless of the outcome of the question 1, please show the output
> >of the "bt full" from the kgdb loaded with your kernel and crash
> >dump. See
> > http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html
> >for details on how to obtain useful information from the crash dump.
>
> 1)
> [EMAIL PROTECTED] kern_conf.c sys/kern/kern_conf.c
> __FBSDID("$FreeBSD: src/sys/kern/kern_conf.c,v 1.208.2.2 2008/03/24
> 13:09:55 kib Exp $");
>
> 2)
> [/usr/obj/usr/src/sys/PRAWN7ULE](11:07:33)
> [EMAIL PROTECTED] kernel.debug /var/crash/vmcore.14
> [GDB will not be able to debug user-mode threads:
> /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"]
> GNU gdb 6.1.1 [FreeBSD]
> Copyright 2004 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain
> conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB. Type "show warranty" for details.
> This GDB was configured as "i386-marcel-freebsd".
> There is no member named pathname.
> (kgdb) bt full
> #0 doadump () at pcpu.h:195
> No locals.
> #1 0xc05ae391 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409
> _giantcnt = Variable "_giantcnt" is not available.
> (kgdb)
>
>
> This isnt what I was expecting from the article referenced. Would it be
> helpful me to update to the latest stable then reproduce (assuming i
> still can.)
Compile the ddb into the kernel (instructions are provided at the same
web page) and post the output of the console on the panic.
pgp0w9dxRUlcL.pgp
Description: PGP signature
Re: Panic with usb serial
Kostik Belousov wrote:
> On Mon, Mar 31, 2008 at 09:48:55AM +0100, Vince Hoffman wrote:
>> Marcin Cieslak wrote:
>>> Vince wrote:
Jeremy Chadwick wrote:
Regarding the USB serial adapter, I was supplied it though work a while
back. I believe from my rather fuzzy memory we got it though these guys
http://www.usbnow.co.uk/Cables-USB_to_RS232_Cables/c1_23/index.html
Although I wouldn't swear to it. I'll have an ask if anyone remembers on
monday.
>>> Can you post a fragment of dmesg output? I am interested whether you
>>> attach it to the ohci or uhci controller.
>>>
>>> --Marcin
>>>
>> Sure,
>> Please not this is now a different usb adapter as I left mine at home :(
>> but I just tested and it exhibits the same behavior, (only difference I
>> can see is this says its FIDI while my one says its FTDI, possibly a typo?)
>>
>> [EMAIL PROTECTED] | grep uhub
>> uhub0: on usb0
>> uhub0: 2 ports with 2 removable, self powered
>> uhub1: on usb1
>> uhub1: 2 ports with 2 removable, self powered
>> uhub2: on usb2
>> uhub2: 2 ports with 2 removable, self powered
>> uhub3: on usb3
>> uhub3: 2 ports with 2 removable, self powered
>> uhub4: on usb4
>> uhub4: 8 ports with 8 removable, self powered
>> umass0: > 2.00/0.01, addr 2> on uhub4
>> ums0:
>> on uhub2
>> ucom0: on
>> uhub2
>>
>> And for what its worth:
>> [EMAIL PROTECTED] /var/crash/info.14
>> Dump header from device /dev/ad0s3b
>> Architecture: i386
>> Architecture Version: 2
>> Dump Length: 154411008B (147 MB)
>> Blocksize: 512
>> Dumptime: Mon Mar 31 09:25:54 2008
>> Hostname: prawn.unsane.co.uk
>> Magic: FreeBSD Kernel Dump
>> Version String: FreeBSD 7.0-STABLE #52: Tue Mar 25 13:45:50 GMT 2008
>> [EMAIL PROTECTED]:/usr/local/obj/usr/src/sys/PRAWN7ULE
>> Panic String: page fault
>> Dump Parity: 1302845723
>> Bounds: 14
>> Dump Status: good
>>
>> Happy to provide more information but I'm not a programmer so you'll
>> probably have to ask me slowly and in words of one syllable ;)
>
> I need two things:
> 1. The revision of the sys/kern/kern_conf.c file; in particular,
>I need to know whether you have rev. 1.208.2.1 or 1.208.2.2.
> 2. Regardless of the outcome of the question 1, please show the output
>of the "bt full" from the kgdb loaded with your kernel and crash
>dump. See
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html
>for details on how to obtain useful information from the crash dump.
1)
[EMAIL PROTECTED] kern_conf.c sys/kern/kern_conf.c
__FBSDID("$FreeBSD: src/sys/kern/kern_conf.c,v 1.208.2.2 2008/03/24
13:09:55 kib Exp $");
2)
[/usr/obj/usr/src/sys/PRAWN7ULE](11:07:33)
[EMAIL PROTECTED] kernel.debug /var/crash/vmcore.14
[GDB will not be able to debug user-mode threads:
/usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"]
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-marcel-freebsd".
There is no member named pathname.
(kgdb) bt full
#0 doadump () at pcpu.h:195
No locals.
#1 0xc05ae391 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409
_giantcnt = Variable "_giantcnt" is not available.
(kgdb)
This isnt what I was expecting from the article referenced. Would it be
helpful me to update to the latest stable then reproduce (assuming i
still can.)
Vince
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Panic with usb serial
On Mon, Mar 31, 2008 at 09:48:55AM +0100, Vince Hoffman wrote: > Marcin Cieslak wrote: > > Vince wrote: > >> Jeremy Chadwick wrote: > > > >> Regarding the USB serial adapter, I was supplied it though work a while > >> back. I believe from my rather fuzzy memory we got it though these guys > >> http://www.usbnow.co.uk/Cables-USB_to_RS232_Cables/c1_23/index.html > >> Although I wouldn't swear to it. I'll have an ask if anyone remembers on > >> monday. > > > > Can you post a fragment of dmesg output? I am interested whether you > > attach it to the ohci or uhci controller. > > > > --Marcin > > > > Sure, > Please not this is now a different usb adapter as I left mine at home :( > but I just tested and it exhibits the same behavior, (only difference I > can see is this says its FIDI while my one says its FTDI, possibly a typo?) > > [EMAIL PROTECTED] | grep uhub > uhub0: on usb0 > uhub0: 2 ports with 2 removable, self powered > uhub1: on usb1 > uhub1: 2 ports with 2 removable, self powered > uhub2: on usb2 > uhub2: 2 ports with 2 removable, self powered > uhub3: on usb3 > uhub3: 2 ports with 2 removable, self powered > uhub4: on usb4 > uhub4: 8 ports with 8 removable, self powered > umass0: 2.00/0.01, addr 2> on uhub4 > ums0: > on uhub2 > ucom0: on > uhub2 > > And for what its worth: > [EMAIL PROTECTED] /var/crash/info.14 > Dump header from device /dev/ad0s3b > Architecture: i386 > Architecture Version: 2 > Dump Length: 154411008B (147 MB) > Blocksize: 512 > Dumptime: Mon Mar 31 09:25:54 2008 > Hostname: prawn.unsane.co.uk > Magic: FreeBSD Kernel Dump > Version String: FreeBSD 7.0-STABLE #52: Tue Mar 25 13:45:50 GMT 2008 > [EMAIL PROTECTED]:/usr/local/obj/usr/src/sys/PRAWN7ULE > Panic String: page fault > Dump Parity: 1302845723 > Bounds: 14 > Dump Status: good > > Happy to provide more information but I'm not a programmer so you'll > probably have to ask me slowly and in words of one syllable ;) I need two things: 1. The revision of the sys/kern/kern_conf.c file; in particular, I need to know whether you have rev. 1.208.2.1 or 1.208.2.2. 2. Regardless of the outcome of the question 1, please show the output of the "bt full" from the kgdb loaded with your kernel and crash dump. See http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html for details on how to obtain useful information from the crash dump. pgpT26sjC6Ilq.pgp Description: PGP signature
Re: Panic with usb serial
Marcin Cieslak wrote: > Vince wrote: >> Jeremy Chadwick wrote: > >> Regarding the USB serial adapter, I was supplied it though work a while >> back. I believe from my rather fuzzy memory we got it though these guys >> http://www.usbnow.co.uk/Cables-USB_to_RS232_Cables/c1_23/index.html >> Although I wouldn't swear to it. I'll have an ask if anyone remembers on >> monday. > > Can you post a fragment of dmesg output? I am interested whether you > attach it to the ohci or uhci controller. > > --Marcin > Sure, Please not this is now a different usb adapter as I left mine at home :( but I just tested and it exhibits the same behavior, (only difference I can see is this says its FIDI while my one says its FTDI, possibly a typo?) [EMAIL PROTECTED] | grep uhub uhub0: on usb0 uhub0: 2 ports with 2 removable, self powered uhub1: on usb1 uhub1: 2 ports with 2 removable, self powered uhub2: on usb2 uhub2: 2 ports with 2 removable, self powered uhub3: on usb3 uhub3: 2 ports with 2 removable, self powered uhub4: on usb4 uhub4: 8 ports with 8 removable, self powered umass0: on uhub4 ums0: on uhub2 ucom0: on uhub2 And for what its worth: [EMAIL PROTECTED] /var/crash/info.14 Dump header from device /dev/ad0s3b Architecture: i386 Architecture Version: 2 Dump Length: 154411008B (147 MB) Blocksize: 512 Dumptime: Mon Mar 31 09:25:54 2008 Hostname: prawn.unsane.co.uk Magic: FreeBSD Kernel Dump Version String: FreeBSD 7.0-STABLE #52: Tue Mar 25 13:45:50 GMT 2008 [EMAIL PROTECTED]:/usr/local/obj/usr/src/sys/PRAWN7ULE Panic String: page fault Dump Parity: 1302845723 Bounds: 14 Dump Status: good Happy to provide more information but I'm not a programmer so you'll probably have to ask me slowly and in words of one syllable ;) Vince > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Panic with usb serial
Vince wrote: > Jeremy Chadwick wrote: > Regarding the USB serial adapter, I was supplied it though work a while > back. I believe from my rather fuzzy memory we got it though these guys > http://www.usbnow.co.uk/Cables-USB_to_RS232_Cables/c1_23/index.html > Although I wouldn't swear to it. I'll have an ask if anyone remembers on > monday. Can you post a fragment of dmesg output? I am interested whether you attach it to the ohci or uhci controller. --Marcin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Panic with usb serial
On Sat, Mar 29, 2008 at 10:11:04PM +, Vince wrote: > Hi all, > Is it expected that removing a usb serial adapter while you have a > connection (eg tip) using it will panic a -stable system? I know it is > expected if you remove a mounted umass device so wanted to see if its > known behavior for serial before I file a pr. (adapter is serial converter, class 0/0, rev 1.10/4.00, addr 3>) > -stable version as of the 25th march, (may have existed before but the > first time I forgot to close tip before removing the device was on this > version.) What is the exact version number of your system ? There are two supported stable branch now. pgpLyLqVJwIJ4.pgp Description: PGP signature
Re: Panic with usb serial
In message: <[EMAIL PROTECTED]> Jeremy Chadwick <[EMAIL PROTECTED]> writes: : On Sat, Mar 29, 2008 at 10:11:04PM +, Vince wrote: : > Is it expected that removing a usb serial adapter while you have a : > connection (eg tip) using it will panic a -stable system? I know it is : > expected if you remove a mounted umass device so wanted to see if its known : > behavior for serial before I file a pr. (adapter is converter, class 0/0, rev 1.10/4.00, addr 3>) : > -stable version as of the 25th march, (may have existed before but the : > first time I forgot to close tip before removing the device was on this : > version.) : : I would expect that the problem is identical in the sense that with a : connection established, you have an open file descriptor which is : associated with a serial device that uses USB. : : So, yes, I would expect this behaviour based on the track record. : Should it happen? The answer is no. File a PR? : : Also, I'd like to know what USB serial adapter you're using (brand, : model, and a website of it if possible), for unrelated reasons. Thanks! That's odd, because I use an FTDI based serial device all the time for hacking on embedded systems. The problem that I have is 100% CPU usage on a tip process until I kill it. Warner ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Panic with usb serial
Jeremy Chadwick wrote: On Sat, Mar 29, 2008 at 10:11:04PM +, Vince wrote: Is it expected that removing a usb serial adapter while you have a connection (eg tip) using it will panic a -stable system? I know it is expected if you remove a mounted umass device so wanted to see if its known behavior for serial before I file a pr. (adapter is converter, class 0/0, rev 1.10/4.00, addr 3>) -stable version as of the 25th march, (may have existed before but the first time I forgot to close tip before removing the device was on this version.) I would expect that the problem is identical in the sense that with a connection established, you have an open file descriptor which is associated with a serial device that uses USB. So, yes, I would expect this behaviour based on the track record. Should it happen? The answer is no. File a PR? Also, I'd like to know what USB serial adapter you're using (brand, model, and a website of it if possible), for unrelated reasons. Thanks! About what I was expecting but just thought I'd check. Will file a PR tomorrow when my wife isnt browsing facebook on that laptop :) Regarding the USB serial adapter, I was supplied it though work a while back. I believe from my rather fuzzy memory we got it though these guys http://www.usbnow.co.uk/Cables-USB_to_RS232_Cables/c1_23/index.html Although I wouldn't swear to it. I'll have an ask if anyone remembers on monday. Vince ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Panic with usb serial
On Sat, Mar 29, 2008 at 10:11:04PM +, Vince wrote: > Is it expected that removing a usb serial adapter while you have a > connection (eg tip) using it will panic a -stable system? I know it is > expected if you remove a mounted umass device so wanted to see if its known > behavior for serial before I file a pr. (adapter is converter, class 0/0, rev 1.10/4.00, addr 3>) > -stable version as of the 25th march, (may have existed before but the > first time I forgot to close tip before removing the device was on this > version.) I would expect that the problem is identical in the sense that with a connection established, you have an open file descriptor which is associated with a serial device that uses USB. So, yes, I would expect this behaviour based on the track record. Should it happen? The answer is no. File a PR? Also, I'd like to know what USB serial adapter you're using (brand, model, and a website of it if possible), for unrelated reasons. Thanks! -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
