I have problems using USB to RS232 converter under FreeBSD 6.3-STABLE when connecting to any Cisco gear over serial link. I connect my adapter to notebook and dmesg output looks like this one:
And terminal stalls- nothing happens- it ignores keyboard completely- sometimes it works but then suddenly lost keyboard interactivity. I tried from KDE Konsole, from plain tcsh command line, sometimes I am able to gain Cisco command line but 90% of times it just hangs. I got two usb2serial adapters: Trendnet TU-S9 and Manhattan 205146. Same converters works just fine under Windows and Linux (drivers cd even got RedHat 7, 8 and 9 versions source code drivers- http://www.manhattan-products.com/driver-usb-rs232.shtml).
> On Sat, 5 Apr 2008, Andrei Kolu wrote: > > I have problems using USB to RS232 converter under FreeBSD 6.3-STABLE > > when connecting to any Cisco gear over serial link. I connect my adapter > > to notebook and dmesg output looks like this one:
There is no difference if I connect through /dev/ttyU0 or /dev/cuaU0 and even through ttyU1 or cuaU1 (when second serial converter is connected)- same problem. I tried on other computer with FreeBSD 6.1 and 7.0-STABLE snapshot from march- same results.
Something is broken on FreeBSD side- strange thing is that when I turn power down on cisco box and turn in on again then I see scrolling text from cisco gear but there is no feedback to keyboard activity. How to debug this issue?
On Sat, 5 Apr 2008, Andrei Kolu wrote: > I have problems using USB to RS232 converter under FreeBSD 6.3-STABLE when > connecting to any Cisco gear over serial link. I connect my adapter to > notebook and dmesg output looks like this one:
-Warren Block * Rapid City, South Dakota USA _______________________________________________ freebsd-sta...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
> On Saturday 05 April 2008 23:48:59 you wrote: > > On Sat, 5 Apr 2008, Andrei Kolu wrote: > > > I have problems using USB to RS232 converter under FreeBSD 6.3-STABLE > > > when connecting to any Cisco gear over serial link. I connect my > > > adapter to notebook and dmesg output looks like this one:
> There is no difference if I connect through /dev/ttyU0 or /dev/cuaU0 and > even through ttyU1 or cuaU1 (when second serial converter is connected)- > same problem. I tried on other computer with FreeBSD 6.1 and 7.0-STABLE > snapshot from march- same results.
> Something is broken on FreeBSD side- strange thing is that when I turn > power down on cisco box and turn in on again then I see scrolling text from > cisco gear but there is no feedback to keyboard activity. How to debug this > issue?
Some progress on debugging! Just kiddin...
I removed converter from USB and FreeBSD 7.0 kernel dumped following information:
ucom0: ucomreadcb: IOERROR ucom0: at uhub1 port 1 (addr 2) disconnected ucom0: uplcom_set_line_status: STALLED
Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0xb0 fault code = supervisor read data, page not present instruction pointer = 0x8:0xffffffff80446f72 stack pointer = 0x10:0xffffffffae796a00 frame pointer = 0x10:0xffffff000172b400 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 876 (cu) trap number = 12 panic: page fault cpuid: 1 Uptime: 8m41s Physical memory: 2802 MB Dumping 126 MB: 111 95 79 63 47 31 15 Dump complete _______________________________________________ freebsd-sta...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
On Sun, Apr 06, 2008 at 12:33:50AM +0300, Andrei Kolu wrote: > On Sunday 06 April 2008 00:24:38 Andrei Kolu wrote: > > On Saturday 05 April 2008 23:48:59 you wrote: > > > On Sat, 5 Apr 2008, Andrei Kolu wrote: > > > > I have problems using USB to RS232 converter under FreeBSD 6.3-STABLE > > > > when connecting to any Cisco gear over serial link. I connect my > > > > adapter to notebook and dmesg output looks like this one:
> > > -Warren Block * Rapid City, South Dakota USA
> > There is no difference if I connect through /dev/ttyU0 or /dev/cuaU0 and > > even through ttyU1 or cuaU1 (when second serial converter is connected)- > > same problem. I tried on other computer with FreeBSD 6.1 and 7.0-STABLE > > snapshot from march- same results.
> > Something is broken on FreeBSD side- strange thing is that when I turn > > power down on cisco box and turn in on again then I see scrolling text from > > cisco gear but there is no feedback to keyboard activity. How to debug this > > issue?
> Some progress on debugging! Just kiddin...
> I removed converter from USB and FreeBSD 7.0 kernel dumped following > information:
> ucom0: ucomreadcb: IOERROR > ucom0: at uhub1 port 1 (addr 2) disconnected > ucom0: uplcom_set_line_status: STALLED
This is a known problem, and even more so if you still had tip or cu connected to the tty. Others have reported similar, with other USB drivers.
Bottom line: the current FreeBSD USB stack is very fragile and unreliable. You may want to try the usb4bsd kernel patches (I think that's what it's called), some have had better luck with those. Search the web.
-- | Jeremy Chadwick jdc 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 |
In message: <20080405215838.GA27...@eos.sc1.parodius.com> Jeremy Chadwick <koi...@freebsd.org> writes: : Bottom line: the current FreeBSD USB stack is very fragile and : unreliable. You may want to try the usb4bsd kernel patches (I think : that's what it's called), some have had better luck with those. Search : the web.
This crash has nothing to do with the usb stack. The root cause is the device deletion code nulls out a pointer. There's a routine that is sleeping which is woken up and the null pointer gets dereferenced leading to the crash.
The current usb stack isn't as fragile as it was in the 5.x days. While there are problems, this one isn't due to that. The same thing happens when you eject a PC Card 16550 COM device, due to the same bug.
While we're at it: can everybody tell me the magic keystroke to end a cu session? man says ~^Z or something, i think this is a combination of keys to pressed?
In message: <200804060121.56127.an...@bsd.ee> Andrei Kolu <an...@bsd.ee> writes: : On Sunday 06 April 2008 01:12:53 Andrei Kolu wrote: : > On Sunday 06 April 2008 00:32:17 Alec Kloss wrote: : > > The the attached patch, also available at : > > : > > http://setfilepointer.com/pub/src:sys:dev:usb:uplcom.c.patch : > > : > > might help. I've needed it to make uplcom stuff work. : > : > This patch works just fine (tested on 6.3). Thank you! : > Why it is not submitted into base tree for more than a year?
Maybe because it wasn't in the PR database when I did my massive cleanup last summer? Would you like to volunteer to help move patches posted to random places into FreeBSD or the PR database? There's plenty of opportunity for advancement into the project for people willing to do these sorts of things.
On Sat, Apr 05, 2008 at 04:10:10PM -0600, M. Warner Losh wrote: > In message: <20080405215838.GA27...@eos.sc1.parodius.com> > Jeremy Chadwick <koi...@freebsd.org> writes: > : Bottom line: the current FreeBSD USB stack is very fragile and > : unreliable. You may want to try the usb4bsd kernel patches (I think > : that's what it's called), some have had better luck with those. Search > : the web. >=20 > This crash has nothing to do with the usb stack. The root cause is > the device deletion code nulls out a pointer. There's a routine that > is sleeping which is woken up and the null pointer gets dereferenced > leading to the crash.
I believe that I fixed this in the HEAD and RELENG_7.
MFC to the RELENG_6 is possible, but I have no facilities to test.
>=20 > The current usb stack isn't as fragile as it was in the 5.x days. > While there are problems, this one isn't due to that. The same thing > happens when you eject a PC Card 16550 COM device, due to the same > bug. >=20 > Warner > _______________________________________________ > freebsd-sta...@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
> While we're at it: can everybody tell me the magic keystroke to end a cu > session? man says ~^Z or something, i think this is a combination of keys > to pressed?
<Enter><Tilde><Period><Enter> will end a cu session.
-- | Jeremy Chadwick jdc 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 |
> > might help. I've needed it to make uplcom stuff work. >=20 > This patch works just fine (tested on 6.3). Thank you!=20 > Why it is not submitted into base tree for more than a year? >=20
It's been on my todo list forever, but so are a lot of other things. I have a hard enough time keeping up with Arla. :)
