On Fri, Mar 31, 2017 at 02:32:50AM +1100, Joel Sing wrote:
> On Monday 20 February 2017 18:52:18 multiplex d wrote:
> > > Synopsis: Removing CardBus USB expansion card causes panic on IBM T22
> > > Thinkpad Category: kernel
> > 
> > > Environment:
> >     System : OpenBSD 6.0
> >     Details : OpenBSD 6.0 (GENERIC) #1: Sat Feb 11 17:41:40 GMT 2017
> >     [email protected]:/usr/src/sys/arch/i386/compile/GENERIC
> > 
> >     Architecture: OpenBSD.i386
> >     Machine : i386
> > 
> > > Description:
> > I am using OpenBSD 6.0-stable on an IBM T22 Thinkpad. This machine only has
> > a single USB 1.0 slot at the rear, so I use a CardBus expansion card which
> > attaches to one of the side PCMCIA slots and provides two extra USB ports.
> > However, if the card is removed, the kernel deregisters the USB bus from
> > the expansion card, panics and then drops to a ddb prompt.
> > 
> > The other operating system that has been used on this hardware (Debian 8.7,
> > with a 3.16-series kernel) does not show any problems from hotplugging this
> > expansion card.
> > 
> > The information generated by sendbug(1) below was created from the immediate
> > subsequent boot, where the offending CardBus adaptor was plugged in after
> > the system had booted.
> > 
> > I have already attempted to send this message to [email protected] on Sunday
> > 12th February with some images of information from ddb, however the message
> > was 17 MB in size so I think it got dropped. I can send the images one at a
> > time to the mailing list if required.
> > > How-To-Repeat:
> >    (1) Plug a CardBus USB expansion card into one of the side PCMCIA slots
> > of an IBM T22 Thinkpad (I don't know if other sufficiently old and similar
> > Thinkpads such as the T20, T21 or T23 exhibit this behaviour).
> >    (2) Remove the card.
> >    (3) The kernel should panic and drop to a ddb prompt.
> > 
> > > Fix:
> > Unknown, other than refraining from hotplugging the expansion card.
> 
> This should be fixed by sys/dev/usb/ehci.c r1.198.
> 

Fixed with OpenBSD 6.1.

Reply via email to