NetBSD Problem Report #10440
Received: (qmail 3284 invoked from network); 25 Jun 2000 16:06:43 -0000
Message-Id: <Pine.SOL.4.21.0006251647410.13958-100000@libra.cus.cam.ac.uk>
Date: Sun, 25 Jun 2000 17:06:35 +0100 (BST)
From: Ben Harris <bjh21@cam.ac.uk>
Sender: Ben Harris <bjh21@cus.cam.ac.uk>
To: gnats-bugs@gnats.netbsd.org
Subject: Occasional panics from kue
>Number: 10440
>Category: kern
>Synopsis: Occasional panics from kue
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: kern-bug-people
>State: closed
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Sun Jun 25 16:07:02 +0000 2000
>Closed-Date: Sun Nov 22 20:41:16 +0000 2009
>Last-Modified: Sun Nov 22 20:41:16 +0000 2009
>Originator: Ben Harris
>Release: 1.4X
>Organization:
University of Cambridge
>Environment:
NetBSD cromarty 1.4X NetBSD 1.4X (CROMARTY) #9: Wed May 3 23:49:51 BST 2000
bjh21@cromarty:/usr/src/sys/arch/macppc/compile/CROMARTY macppc
>Description:
Occasionally, usually under load, the "kue" driver seems to cause a
panic. This doesn't happen to me very often, and I've only just set up my
system to automatically core-dump and reboot on panics, so I don't have a
core from it yet. I do have a bunch of log messages from just before a
panic though:
Jun 18 13:57:05 cromarty /netbsd: kue0: watchdog timeout
Jun 18 13:57:05 cromarty /netbsd: usb_block_allocmem: in interrupt context, size=4096
Jun 18 13:57:05 cromarty /netbsd: usb_block_allocmem: in interrupt context, size=4096
Jun 18 13:57:05 cromarty /netbsd: usbd_transfer_cb: pipe==0, xfer=0xe007b980
Jun 18 13:57:05 cromarty last message repeated 2 times
Jun 18 13:57:05 cromarty /netbsd: usb_transfer_complete: bad dequeue 0xe0091400 != 0x0
[...]
Jun 18 14:53:49 cromarty uservd[29370]: user ceb28 -> root : prod-kue0
[...]
Jun 18 16:31:03 cromarty /netbsd: kue0: watchdog timeout
Jun 18 16:31:04 cromarty /netbsd: usbd_transfer_cb: pipe==0, xfer=0xe007b980
Jun 18 16:31:04 cromarty last message repeated 2 times
Jun 18 16:31:04 cromarty /netbsd: usb_transfer_complete: bad dequeue 0xe0091400 != 0x0
Jun 18 16:35:35 cromarty /netbsd: kue0: watchdog timeout
Jun 18 16:35:35 cromarty /netbsd: usbd_transfer_cb: pipe==0, xfer=0xe007b980
Jun 18 16:35:35 cromarty last message repeated 2 times
Jun 18 16:35:35 cromarty /netbsd: usb_transfer_complete: bad dequeue 0xe0091400 != 0x0
At this point, I think the system panicked, though problems with the
console make it hard to be sure.
The "uservd" message indicates a user running the script which does
"ifconfig kue0 down; ifconfig kue0 up", in order to deal with kue0 hanging
up as described in PR#10337.
I'll append more information if I manage to get a more useful panic.
>How-To-Repeat:
Not known. Perhaps just repeatedly ifconfigging a kue down and up again
will do it.
--
Ben Harris
Unix Support, University of Cambridge Computing Service.
E-mail: bjh21@cam.ac.uk Tel: +44 (0)1223 334728 Fax: +44 (0)1223 334679
>Fix:
>Release-Note:
>Audit-Trail:
From: Ben Harris <bjh21@cam.ac.uk>
To: gnats-bugs@netbsd.org
Cc:
Subject: Re: kern/10440: Occasional panics from kue
Date: Sun, 16 Jul 2000 11:38:38 +0100 (BST)
My system just panicked with the console terminal turned on, so I could
ten-finger the messages off it before rebooting it. Here's what it had to
say:
--------8<--------
usb_transfer_complete: bad dequeue 0xe00c2080 != 0
kue0: watchdog timeout
panic: ohci_add_done: addr 0x00542530 not found
syncing disks... ohci_intr: ignored interrupt while polling
panic: lockmgr: no context
dumpsys: TBD
rebooting
trap type 700 at ff8237f4
Stopped at cpu_Debugger+0x10: lwz r0, r1, 0x14,
db>
-------->8--------
Hope this is of use.
--
Ben Harris
Unix Support, University of Cambridge Computing Service.
State-Changed-From-To: open->closed
State-Changed-By: dsl@NetBSD.org
State-Changed-When: Sun, 22 Nov 2009 20:41:16 +0000
State-Changed-Why:
Can't help feeling this PR is well past its 'fix by' date.
>Unformatted:
(Contact us)
$NetBSD: query-full-pr,v 1.51 2026/08/10 02:28:17 riastradh Exp $
$NetBSD: gnats_config.sh,v 1.10 2026/05/13 22:00:09 riastradh Exp $
Copyright © 1994-2026
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.