Re: uhci on cardbus error blocks shutdown

[David Young <dyoung%pobox.com@localhost>]

On Tue, Jun 24, 2008 at 08:07:22AM +0100, Iain Hibbert wrote:
> On Tue, 24 Jun 2008, David Young wrote:
> 
> > On Sun, Jun 22, 2008 at 08:34:12PM +0100, Iain Hibbert wrote:
> > > Hi,
> > >
> > > Just upgrading from a couple of months ago (4.99.62) to -current as of a
> > > couple of days ago, I notice that the machine won't shutdown/reboot
> > > properly.
> > >
> > > I have a bluetooth cardbus card that contains two UHCI controllers and a
> > > bluetooth dongle all in one, shows up as:
> > >
> > *snip snip*
> > >
> > > when I try to shutdown the system, the disks are dismounted as normal
> > > then I get:
> > >
> > > uhci1: host system error
> > > uhci1: host controller process error
> > > uhci1: host controller halted
> > > uhci2: host system error
> > > uhci2: host controller process error
> > > uhci2: host controller halted
> > >
> > > and the machine just hangs.  I can break into DDB but there seems nothing
> > > interesting in the backtrace (below) but if I eject the card then the halt
> > > or reboot resumes. If this sounds familiar to anybody feel free to speak
> > > up..
> >
> > What does ps/l say during the hang?
> 
> unmounting file systems... done
> uhci1: host system error
> uhci1: host controller process error
> uhci1: host controller halted
> uhci2: host system error
> uhci2: host controller process error
> uhci2: host controller halted
> fatal breakpoint trap in supervisor mode
> trap type 1 code 0 eip c0575ffc cs 8 eflags 202 cr2 bbb3abd4 ilevel 6
> Stopped in pid 0.3 (system) at        netbsd:breakpoint+0x4:  popl    %ebp
> db{0}> ps/l
>  PID         LID S     FLAGS       STRUCT LWP *               NAME WAIT
>  863           1 7         4           cbf8faa0             reboot
>  1             1 3   8020084           ca5b5060               init wait
> >0            41 3       204           cb8d6ca0            physiod physiod
>               40 3       204           cb843a20        vmem_rehash vmem_rehash
>               39 3       204           cb843c80           aiodoned aiodoned
>               38 2       204           ca5b6080            ioflush
>               37 3       204           ca5b62e0           pgdaemon pgdaemon
>               36 3       204           ca5b5c40          cryptoret crypto_wait
>               35 3       204           ca5b59e0          atapibus0 sccomp
>               34 3       204           ca5b5780               usb2 usbevt
>               33 3       204           ca5b3040               usb1 usbevt
>               32 3       204           ca5b5520         usbtask-dr usbtsk
>               31 3       204           ca5b52c0         usbtask-hc usbtsk
>               30 3       204           ca5b6c60               usb0 usbevt
>               29 3       204           ca5b6540            acpitz0 acpitz0
>               28 3       204           ca5b67a0           acpibat1 acpibat1
>               27 3       204           ca5b6a00           acpibat0 acpibat0
>               18 3       204           ca5b32a0          cardslot1 cardslotev
>               17 3       204           ca5b3500          cardslot0 cardslotev
>               16 3       204           ca5b3760               iic0 iicintr
>               15 3       204           ca5b39c0            atabus1 atath
>               14 3       204           ca5b3c20            atabus0 atath
>               13 3       204           ca5a9020               pms0 pmsreset
>               12 3       204           ca5a9280               apm0 apmev
>               11 2       204           ca5a94e0             sysmon
>               10 3       204           ca5a9740           pmfevent pmfevent
>                9 3       204           ca5a99a0            cachegc cachegc
>                8 3       204           ca5a9c00              vrele vrele
>                7 3       204           ca5a7000            xcall/0 xcall
>                6 1       204           ca5a7260          softser/0
>                5 1       204           ca5a74c0          softclk/0
>                4 1       204           ca5a7720          softbio/0
>            >   3 7       204           ca5a7980          softnet/0
>                2 1       205           ca5a7be0             idle/0
>                1 3       204           c0acbde0            swapper schedule
> db{0}>
> 
> which means .. stuck in softnet?

I can only conclude that the breakpoint is in softnet.  Get a backtrace
on the reboot process.

Dave

-- 
David Young             OJC Technologies
dyoung%ojctech.com@localhost      Urbana, IL * (217) 278-3933 ext 24