From owner-freebsd-current Sun Jun 6 12: 9: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by hub.freebsd.org (Postfix) with ESMTP id 8D37514BD2 for ; Sun, 6 Jun 1999 12:09:00 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.55.109]) by smtp01.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA4844 for ; Sun, 6 Jun 1999 21:08:56 +0200 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id VAA23400 for current@freebsd.org; Sun, 6 Jun 1999 21:08:56 +0200 (CEST) (envelope-from asmodai) Date: Sun, 6 Jun 1999 21:08:56 +0200 From: Jeroen Ruigrok van der Werven To: FreeBSD Current Subject: weird crash Message-ID: <19990606210856.D16752@daemon.ninth-circle.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.3i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, just today I got this error, never had it before in all those months I have been tracking CURRENT now. Jun 6 17:15:26 daemon /kernel: sio0: 65 more tty-level buffer overflows (total 65) Jun 6 17:15:28 daemon /kernel: sio0: 131 more tty-level buffer overflows (total 196) Jun 6 17:15:29 daemon /kernel: sio0: 38 more tty-level buffer overflows (total 234) until I interrupted it with CTRL-ALT-ESC to drop into DDB. This is some info I got from DDB: [ please bear with me if I didn't get all I need, but it's the first `crash' I intercepted and I think I got all the relevant data, comments appreciated though ] db>trace Debugger(0c255518) at Debugger+0x37 scgetc(c0294020,2,124bca,c0294020,850ff2c) at scgetc+ox5ec sckdbevent(c0294020,0,0,124bca,850ff2c) at sckbdevent+0x1c4 atkbd_intr(c0294020,0,bfbfd4bc,c0211c92,c06773f0) at atkbd_intr+ox1f atkbd_isa_intr(c06773f0,0,2f,2f,2f) at atkbd_isa_intr+0x1b Xresume1() at Xresume+0x2b --- interrupt, eip=0x28078509, esp=0xc5b6dfe0, ebp=0xbfbfd4bc --- I also have results from show registers, print, show page if those are deemed interesting. What I was able to glance from ps what that the 0xc5b6dfe0 range lay in an xterm memory range... I am not 100% sure about this though. some relevant system information: [asmodai@daemon] (81) $ uname -a FreeBSD daemon.ninth-circle.org 4.0-CURRENT FreeBSD 4.0-CURRENT #3: Thu Jun 3 16:59:10 CEST 1999 asmodai@daemon.ninth-circle.org:/work/FreeBSD/src/sys/compile/DAEMON i386 Jun 2 10:57:38 daemon /kernel: isab0: at device 7.0 on pci0 Jun 2 10:57:38 daemon /kernel: atkbdc0: at port 0x60-0x6f on isa0 Jun 2 10:57:38 daemon /kernel: atkbd0: irq 1 on atkbdc0 Jun 2 10:57:38 daemon /kernel: atkbd: the current kbd controller command byte 0047 Jun 2 10:57:38 daemon /kernel: atkbd: keyboard ID 0x41ab (2) Jun 2 10:57:38 daemon /kernel: kbdc: RESET_KBD return code:00fa Jun 2 10:57:38 daemon /kernel: kbdc: RESET_KBD status:00aa Jun 2 10:57:38 daemon /kernel: kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 Jun 2 10:57:38 daemon /kernel: vga0: on isa0 Jun 2 10:57:38 daemon /kernel: fb0: vga0, vga, type:VGA (5), flags:0x7007f Jun 2 10:57:38 daemon /kernel: fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 Jun 2 10:57:38 daemon /kernel: fb0: init mode:24, bios mode:3, current mode:24 Jun 2 10:57:38 daemon /kernel: fb0: window:0xc00b8000 size:32k gran:32k, buf:0x0 size:0k Jun 2 10:57:38 daemon /kernel: VGA parameters upon power-up Jun 2 10:57:38 daemon /kernel: 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 Jun 2 10:57:38 daemon /kernel: bf 1f 00 4f 0e 0f 00 00 07 80 9c 8e 8f 28 1f 96 Jun 2 10:57:38 daemon /kernel: b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c Jun 2 10:57:38 daemon /kernel: 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff Jun 2 10:57:38 daemon /kernel: VGA parameters in BIOS for mode 24 Jun 2 10:57:38 daemon /kernel: 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 Jun 2 10:57:38 daemon /kernel: bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 Jun 2 10:57:38 daemon /kernel: b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c Jun 2 10:57:38 daemon /kernel: 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff Jun 2 10:57:38 daemon /kernel: EGA/VGA parameters to be used for mode 24 Jun 2 10:57:38 daemon /kernel: 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 Jun 2 10:57:38 daemon /kernel: bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 Jun 2 10:57:38 daemon /kernel: b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c Jun 2 10:57:38 daemon /kernel: 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff Jun 2 10:57:38 daemon /kernel: sc0: on isa0 Jun 2 10:57:38 daemon /kernel: sc0: fb0 kbd0 Jun 2 10:57:38 daemon /kernel: sc0: VGA color <16 virtual consoles, flags=0x0> Jun 2 10:57:38 daemon /kernel: sio0: irq maps: 0x41 0x51 0x41 0x41 Jun 2 10:57:38 daemon /kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 Jun 2 10:57:38 daemon /kernel: sio0: type 16550A Jun 2 10:57:38 daemon /kernel: sio1: irq maps: 0x41 0x49 0x41 0x41 Jun 2 10:57:38 daemon /kernel: sio1 at port 0x2f8-0x2ff irq 3 on isa0 Jun 2 10:57:38 daemon /kernel: sio1: type 16550A The system itself is a simple DFI-based motherboard with Intel Pentium 200 MMX and 96 MB RAM. The keyboard is not one of them ps/2's, but a the older type (I don't think that DIN is the correct name though). the device on sio0 is my serial MouseMan: controller isa0 controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device vga0 at isa? port ? conflicts device sc0 at isa? If any more information is required, please tell me and I will see if I can dig it up. 'gards, -- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The FreeBSD Programmer's Documentation Project Network/Security Specialist *BSD: Accept no limitations... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message