From owner-freebsd-bugs Wed Mar 6 16:10:04 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA12517 for bugs-outgoing; Wed, 6 Mar 1996 16:10:04 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA12511 Wed, 6 Mar 1996 16:10:02 -0800 (PST) Resent-Date: Wed, 6 Mar 1996 16:10:02 -0800 (PST) Resent-Message-Id: <199603070010.QAA12511@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, hsu@clinet.fi Received: from hauki.clinet.fi (root@hauki.clinet.fi [194.100.0.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id QAA12421 for ; Wed, 6 Mar 1996 16:08:14 -0800 (PST) Received: from zetor.clinet.fi (root@zetor.clinet.fi [194.100.0.11]) by hauki.clinet.fi (8.7.3/8.6.4) with ESMTP id CAA04756 for ; Thu, 7 Mar 1996 02:08:05 +0200 (EET) Received: (root@localhost) by zetor.clinet.fi (8.7.3/8.6.4) id CAA28412; Thu, 7 Mar 1996 02:08:04 +0200 (EET) Message-Id: <199603070008.CAA28412@zetor.clinet.fi> Date: Thu, 7 Mar 1996 02:08:04 +0200 (EET) From: Heikki Suonsivu Reply-To: hsu@clinet.fi To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: kern/1066: Arnet driver: panic when ifconfig PPP -> HDLC Sender: owner-bugs@freebsd.org Precedence: bulk >Number: 1066 >Category: kern >Synopsis: Arnet driver: panic when ifconfig PPP -> HDLC >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Mar 6 16:10:01 PST 1996 >Last-Modified: >Originator: Heikki Suonsivu >Organization: Clinet, Espoo, Finland >Release: FreeBSD 2.2-CURRENT i386 >Environment: FreeBSD 2.2-CURRENT #0: Sun Mar 3 12:00:09 EET 1996 hsu@news.clinet.fi:/usr/current/src/sys/compile/CLINETARNET CPU: i486 SX (486-class CPU) Origin = "GenuineIntel" Id = 0x423 Stepping=3 Features=0x2 real memory = 16777216 (16384K bytes) avail memory = 14467072 (14128K bytes) Probing for devices on the ISA bus: vt0 at 0x60-0x6f irq 1 on motherboard vt0: cl-gd5428, 80/132 col, mono, 8 scr, mf2-kbd, [R3.20-b24] ed0 at 0x280-0x29f irq 5 on isa ed0: address 00:4f:56:00:7c:6b, type NE2000 (16 bit) ed3 at 0x240-0x25f irq 9 on isa ed3: address 00:4f:56:00:4b:76, type NE2000 (16 bit) ed4 at 0x340-0x35f irq 15 on isa ed4: address 00:4f:56:00:ad:e0, type NE2000 (16 bit) ed5 not found at 0x220 sio0 not found at 0x3f8 sio0 not found at 0x3f8 sio1 not found at 0x2f8 sio1 not found at 0x2f8 sio2 not found at 0x2a0 sio2 not found at 0x2a0 sio3 not found at 0x2a8 sio3 not found at 0x2a8 sio4 not found at 0x2b0 sio4 not found at 0x2b0 sio5 not found at 0x2b8 sio5 not found at 0x2b8 cy0 not found cy1 not found bt0 not found at 0x330 aha0 not found at 0x330 wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 402MB (824160 sectors), 1010 cyls, 16 heads, 51 S/T, 512 B/S fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 765 fd0: 1.44MB 3.5in arc0 at 0x300-0x30f irq 10 maddr 0xd0000 msize 16384 on isa arc0: 256K RAM, 4 ports, rev 0, EIA-232 or V.35 interface. ar0: Adapter 0, port 0. ar1: Adapter 0, port 1. ar2: Adapter 0, port 2. ar3: Adapter 0, port 3. npx0 on motherboard npx0: 387 emulator new masks: bio c0004040, tty c0038622, net c0038622 <7>arplookup 193.64.6.28 failed: host is not on local network <7>arplookup 193.64.6.27 failed: host is not on local network >Description: When trying to ioctl ar1 from PPP to Cisco HDLC I got this: Fatal trap 12: page fault while in kernel mode fault virtual address = 0x1e fault code = supervisor read, page not present instruction pointer = 0x8:0xf01501b3 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 = 165 (ifconfig) interrupt mask = panic: page fault syncing disks... done dumping to dev 1, offset 0 dump 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 The ar0 device works, but when using ar1 at the same time ar1 fails to work correctly. ar0 is connected to a frame relay box which ignores handshake signals, while ar1 is connected to a pair of modems, with a Cisco 1005 in the other end. I haven't yet fully verified that this is arnet driver problem, as I need to take the setup to lab and try it there. What we see is loss of packets and this: Mar 6 07:09:26 kamppi2-gw /kernel: ar1: down Mar 6 07:09:26 kamppi2-gw /kernel: ar1: up Mar 6 07:32:26 kamppi2-gw /kernel: ar1: down Mar 6 07:32:26 kamppi2-gw /kernel: ar1: up Mar 6 07:47:36 kamppi2-gw /kernel: ar1: down Mar 6 07:47:36 kamppi2-gw /kernel: ar1: up Mar 6 08:10:35 kamppi2-gw /kernel: ar1: down Mar 6 08:10:35 kamppi2-gw /kernel: ar1: up Mar 6 08:33:35 kamppi2-gw /kernel: ar1: down Mar 6 08:33:35 kamppi2-gw /kernel: ar1: up Mar 6 08:48:45 kamppi2-gw /kernel: ar1: down Mar 6 08:48:45 kamppi2-gw /kernel: ar1: up Mar 6 09:11:45 kamppi2-gw /kernel: ar1: down Mar 6 09:11:45 kamppi2-gw /kernel: ar1: up Mar 6 09:47:35 kamppi2-gw /kernel: ar1: down Mar 6 09:47:35 kamppi2-gw /kernel: ar1: up Mar 6 10:15:35 kamppi2-gw /kernel: ar1: down Mar 6 10:15:35 kamppi2-gw /kernel: ar1: up Mar 6 10:31:03 kamppi2-gw /kernel: RX1 So this does happen :), stat a4, ST2 0, cda 4190. Mar 6 10:31:03 kamppi2-gw /kernel: RX1 After reset: ST2 0. Mar 6 10:44:05 kamppi2-gw /kernel: ar1: down Mar 6 10:44:05 kamppi2-gw /kernel: ar1: up Mar 6 10:51:05 kamppi2-gw /kernel: ar1: down Mar 6 10:51:05 kamppi2-gw /kernel: ar1: up Mar 6 11:47:24 kamppi2-gw /kernel: ar1: down Mar 6 11:47:24 kamppi2-gw /kernel: ar1: up Mar 6 11:54:04 kamppi2-gw /kernel: ar1: down Mar 6 11:54:04 kamppi2-gw /kernel: ar1: up Mar 6 12:01:24 kamppi2-gw /kernel: ar1: down Mar 6 12:01:24 kamppi2-gw /kernel: ar1: up Mar 6 12:05:45 kamppi2-gw /kernel: RX1 So this does happen :), stat d4, ST2 0, cda 42b2. Mar 6 12:05:45 kamppi2-gw /kernel: RX1 After reset: ST2 0. Mar 6 12:23:24 kamppi2-gw /kernel: ar1: down Mar 6 12:23:24 kamppi2-gw /kernel: ar1: up Mar 6 12:46:24 kamppi2-gw /kernel: ar1: down Mar 6 12:46:24 kamppi2-gw /kernel: ar1: up Mar 6 13:01:33 kamppi2-gw /kernel: ar1: down Mar 6 13:01:34 kamppi2-gw /kernel: ar1: up Mar 6 13:22:43 kamppi2-gw /kernel: ar1: down Mar 6 13:22:43 kamppi2-gw /kernel: ar1: up Mar 6 14:14:33 kamppi2-gw /kernel: RX1 So this does happen :), stat a4, ST2 0, cda 41ea. Mar 6 14:14:33 kamppi2-gw /kernel: RX1 After reset: ST2 0. Mar 6 14:28:23 kamppi2-gw /kernel: ar1: down Mar 6 14:28:23 kamppi2-gw /kernel: ar1: up Mar 6 14:51:23 kamppi2-gw /kernel: ar1: down Mar 6 14:51:23 kamppi2-gw /kernel: ar1: up Mar 6 15:06:33 kamppi2-gw /kernel: ar1: down Mar 6 15:06:33 kamppi2-gw /kernel: ar1: up Mar 6 15:29:33 kamppi2-gw /kernel: ar1: down Mar 6 15:29:33 kamppi2-gw /kernel: ar1: up Mar 6 15:52:16 kamppi2-gw /kernel: RX1 So this does happen :), stat 84, ST2 0, cda 4104. Mar 6 15:52:16 kamppi2-gw /kernel: RX1 After reset: ST2 0. Mar 6 16:15:52 kamppi2-gw /kernel: ar1: down Mar 6 16:15:52 kamppi2-gw /kernel: ar1: up Mar 6 16:31:02 kamppi2-gw /kernel: ar1: down Mar 6 16:31:02 kamppi2-gw /kernel: ar1: up Mar 6 16:54:02 kamppi2-gw /kernel: ar1: down Mar 6 16:54:02 kamppi2-gw /kernel: ar1: up Mar 6 17:35:02 kamppi2-gw /kernel: ar1: down Mar 6 17:35:02 kamppi2-gw /kernel: ar1: up Mar 6 17:58:02 kamppi2-gw /kernel: ar1: down ftp://ftp.clinet.fi/pub/FreeBSD/crashdumps/kamppi2 Unfortunately there are no symbols in the kernel, the machine was configured with too small root and I had left them out. >How-To-Repeat: I could not repeat the panic, but I didn't want to try it (it is a production link). The packet loss problem I need to verify to work without the telco cable between the modems to make sure it is not their problem (modem error counters do not show anything wrong, and we tried two very different pairs of modems). >Fix: >Audit-Trail: >Unformatted: