Date: Tue, 28 Aug 2012 09:07:51 +0700 From: Alexey Dokuchaev <danfe@nsu.ru> To: Hans Petter Selasky <hselasky@c2i.net> Cc: freebsd-stable@freebsd.org, freebsd-usb@freebsd.org, Jung-uk Kim <jkim@freebsd.org> Subject: Re: Resume broken in 8.3-PRERELEASE Message-ID: <20120828020750.GA61543@regency.nsu.ru> In-Reply-To: <201208271734.54814.hselasky@c2i.net> References: <20120227152238.GA2940@regency.nsu.ru> <201203050710.22871.hselasky@c2i.net> <20120827125943.GA68575@regency.nsu.ru> <201208271734.54814.hselasky@c2i.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Aug 27, 2012 at 05:34:54PM +0200, Hans Petter Selasky wrote: > If the USB HC is feeding too many such IRQ's it will be stuck. However, > if you see that "uhub_read_port_status()" is called, the kernel is at least > running, though it might be that some IRQ is stuck, hence the 100% CPU > usage. Could you try to get some IRQ stats? Before zzz'ing: db> show intrcnt irq1: atkbd0 168 irq9: acpi0 8300 irc12: psm0 2 irq14: ata0 6301 irq16: bge0 uhci3 13 irq23: uhci0 ehci0 2 cpu0: timer 7306385 irq256: hdac0 30 After (within a minute after botched resume) db> show intrcnt irq1: atkbd0 479 irq9: cdpi0 8379 irc12: psm0 2 irq14: ata0 6377 irq16: bge0 uhci3 26 irq23: uhci0 ehci0 5 cpu0: timer 7731880 irq256: hdac0 34 Not too much difference. Anything else I might get from DDB? Unfortunately, I am yet unable to save crashdump for later gdb analysis. ./danfe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120828020750.GA61543>