From owner-freebsd-hardware@FreeBSD.ORG Mon Jun 21 04:58:14 2004 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BC1E716A4CE; Mon, 21 Jun 2004 04:58:14 +0000 (GMT) Received: from www.reppep.com (www.reppep.com [66.92.104.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 780AC43D5D; Mon, 21 Jun 2004 04:58:14 +0000 (GMT) (envelope-from pepper@reppep.com) Received: from [10.0.1.102] (airport.reppep.com [66.92.104.202]) by www.reppep.com (Postfix) with ESMTP id A84A6FDAF; Mon, 21 Jun 2004 00:58:12 -0400 (EDT) Mime-Version: 1.0 X-Sender: pepper@mail.reppep.com Message-Id: Date: Mon, 21 Jun 2004 00:57:56 -0400 To: freebsd-hardware@freebsd.org From: Chris Pepper Content-Type: text/plain; charset="us-ascii" ; format="flowed" cc: Bill Paul Subject: re(4) hang at bootup under CURRENT X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jun 2004 04:58:14 -0000 I've had a couple hangs bringing up re(4) at boot time. A reboot cleared both, but since it's happened twice in a couple weeks, here's a report. I'm not sure if this merits a PR. This all applies to an HP Pavilion 7915 w/ 3.04 BIOS and FreeBSD 5.2.1 (now running -CURRENT from a few days ago). I'm working on upgrading it to 3.07 BIOS to see if this lets me run with ACPI, but haven't gotten there yet. "pciconf -lv", dmesg, and my REPPEP5 kernel configuration are all at . The card itself is an 8169, sold by Asante as a FriendlyNet GigaNIX : >re0@pci1:10:0: class=0x020000 card=0x816910ec chip=0x816910ec >rev=0x10 hdr=0x00 > vendor = 'Realtek Semiconductor' > device = 'RTL8169 Gigabit Ethernet Adapter' > class = network > subclass = ethernet After installing 5.2.1 from CD, the system hung during its first boot -- apparently while configuring the re driver. Since an immediate reboot cleared the problem, and it didn't recur within a week, I no longer have notes on that hang. I have a 6gb partition with Windows XP Pro SP1 on the disk. SP1 (which I installed after 5.2.1), does not come with a driver for the RealTek card; it does detect the 3Com 10/100 card, but I only got the RealTek driver from Windows Update a day or two ago, and Windows hadn't recognized for the 8169 before this evening. When I finished futzing with the (failed) HP UIUD BIOS update and booted back into FreeBSD, I got the second hang. I don't know if Windows configured the card problematically for FreeBSD, but mention it for completeness. If I have any further hangs, I'll report them here, and/or file a PR. For convenience, here's tonight's hang from : >xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0x2080-0x20ff mem >0xf4104000-0xf410407f irq 9 at device 9.0 on pci1 >xl0: Ethernet address: 00:04:76:df:f2:82 >miibus0: on xl0 >xlphy0: <3c905C 10/100 internal PHY> on miibus0 >xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto >re0: port 0x2400-0x24ff >mem 0xf4104400-0xf41044ff irq 10 at device 10.0 on pci1 >re0: Ethernet address: 00:0e:2e:06:ea:82 >miibus1: on re0 >rgephy0: on miibus1 >rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, >1000baseTX, 1000baseTX-FDX, auto >re0: diagnostic failed, failed to receive packet in loopback mode >re0: attach aborted due to hardware diag failure > > >Fatal trap 12: page fault while in kernel mode >fault virtual address = 0x98 >fault code = supervisor write, page not present >instruction pointer = 0x8:0xc05914c5 >stack pointer = 0x10:0xc0c21998 >frame pointer = 0x10:0xc0c219a8 >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 = 0 (swapper) >trap number = 12 >panic: page fault >Uptime: 1s >Automatic reboot in 15 seconds - press a key on the console to abort >Rebooting... Regards, Chris Pepper -- Chris Pepper: Rockefeller University: