From owner-freebsd-current Sun Feb 9 13:29:53 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8604D37B401 for ; Sun, 9 Feb 2003 13:29:50 -0800 (PST) Received: from warez.scriptkiddie.org (uswest-dsl-142-38.cortland.com [209.162.142.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id C1A8543FAF for ; Sun, 9 Feb 2003 13:29:49 -0800 (PST) (envelope-from lamont@scriptkiddie.org) Received: from [192.168.69.11] (unknown [192.168.69.11]) by warez.scriptkiddie.org (Postfix) with ESMTP id CE5B062D1A for ; Sun, 9 Feb 2003 13:29:48 -0800 (PST) Date: Sun, 9 Feb 2003 13:29:48 -0800 (PST) From: Lamont Granquist To: freebsd-current@freebsd.org Subject: panic with hp psc 2210xi usb printer Message-ID: <20030209132056.W1044-100000@coredump.scriptkiddie.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG My USB PCI hub is: ohci0: mem 0xec000000-0xec000fff irq 5 at device 5.0 on pci2 usb0: OHCI version 1.0 usb0: on ohci0 usb0: USB revision 1.0 uhub0: NEC OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1: mem 0xeb800000-0xeb800fff irq 6 at device 5.1 on pci2 usb1: OHCI version 1.0 usb1: on ohci1 usb1: USB revision 1.0 uhub1: NEC OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered pci2: at device 5.2 (no driver attached) Here's what happened when I plugged it the printer (all i did was plug it in): ulpt0: Hewlett-Packard PSC 2200 Series, rev 2.00/1.00, addr 2, iclass 7/1 ulpt0: using bi-directional mode umass0: Hewlett-Packard PSC 2200 Series, rev 2.00/1.00, addr 2 umass0: Residue incorrect, was 255, should've been 0 umass0: BBB reset failed, TIMEOUT umass0: Residue incorrect, was 255, should've been 0 umass0: BBB reset failed, TIMEOUT umass0: Residue incorrect, was 255, should've been 0 umass0: BBB reset failed, TIMEOUT umass0: Residue incorrect, was 255, should've been 0 umass0: BBB reset failed, TIMEOUT umass0: Residue incorrect, was 255, should've been 0 umass0: BBB reset failed, TIMEOUT umass0: Residue incorrect, was 14, should've been 0 umass0: BBB reset failed, TIMEOUT umass0: Residue incorrect, was 8, should've been 0 umass0: BBB reset failed, TIMEOUT umass0: Residue incorrect, was 8, should've been 0 umass0: BBB reset failed, TIMEOUT umass0: Residue incorrect, was 8, should've been 0 umass0: BBB reset failed, TIMEOUT umass0: Residue incorrect, was 8, should've been 0 umass0: BBB reset failed, TIMEOUT umass0: Residue incorrect, was 8, should've been 0 umass0: BBB reset failed, TIMEOUT (da1:umass-sim0:0:0:0): got CAM status 0x4 (da1:umass-sim0:0:0:0): fatal error, failed to attach to device (da1:umass-sim0:0:0:0): lost device umass0: Residue incorrect, was 8, should've been 0 umass0: BBB reset failed, TIMEOUT umass0: Residue incorrect, was 8, should've been 0 umass0: BBB reset failed, TIMEOUT umass0: Residue incorrect, was 8, should've been 0 umass0: BBB reset failed, TIMEOUT umass0: Residue incorrect, was 8, should've been 0 umass0: BBB reset failed, TIMEOUT umass0: Residue incorrect, was 8, should've been 0 umass0: BBB reset failed, TIMEOUT (da1:umass-sim0:0:0:0): removing device entry Opened disk da1 -> 5 Feb 9 13:08:45 coredump syslogd: kernel boot file is /boot/kernel/kernel Fatal trap 12: page fault while in kernel mode cpuid = 1; lapic.id = 01000000 fault virtual address = 0x68 fault code = supervisor read, pawe not present instruction pointer = 0x8:0xc02f1d41 stack pointer ( < 0x10:0xd7a37c0c frame pointer = 0x10:0xd7a37c2c code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 502 (tcsh) This is from -current as of around: 5.0-CURRENT #2: Thu Feb 6 18:59:11 PST 2003 And I've deleted my kernel.debug (and sources, and object tree), so debugging the panic I got out of it is unfortunately not going to be too useful... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message