From owner-freebsd-current@FreeBSD.ORG Mon Sep 10 08:10:46 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1710016A478 for ; Mon, 10 Sep 2007 08:10:46 +0000 (UTC) (envelope-from jmadle@tac-tac.cz) Received: from mail.tac-tac.cz (mail.tac-tac.cz [194.212.102.90]) by mx1.freebsd.org (Postfix) with ESMTP id 6053813C465 for ; Mon, 10 Sep 2007 08:10:45 +0000 (UTC) (envelope-from jmadle@tac-tac.cz) Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.tac-tac.cz (Postfix) with ESMTP id AE46A22EFB; Mon, 10 Sep 2007 09:43:11 +0200 (CEST) Received: from mail.tac-tac.cz ([127.0.0.1]) by localhost (mail [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 21527-10; Mon, 10 Sep 2007 09:43:07 +0200 (CEST) Received: from pcjirka (unknown [1.0.0.10]) by mail.tac-tac.cz (Postfix) with SMTP id CF2B451EE; Mon, 10 Sep 2007 09:43:07 +0200 (CEST) Message-ID: <033201c7f37e$3e69d2e0$0a000001@pcjirka> From: "TAC-TAC computer s.r.o." To: References: <20070908120006.B9E6E16A4EE@hub.freebsd.org> Date: Mon, 10 Sep 2007 09:43:14 +0200 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at tac-tac.cz Cc: remy.nonnenmacher@activnetworks.com Subject: RE: Solid hang with bge interface X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Sep 2007 08:10:46 -0000 Same problem with Supermicro H8SSL-R10. (amd64) If I remember, this bge problem was reported 3-4 month ago first time - but i have not found any idea of solution anywhere. Jiri Madle TAC-TAC computer s.r.o. jmadle@tac-tac.cz >> -----Original Message----- >> From: Remy Nonnenmacher [mailto:remy.nonnenmacher@activnetworks.com] >> Sent: 21 August 2007 10:45 >> To: Lawrence Farr >> Cc: freebsd-current@freebsd.org >> Subject: Re: Solid hang with bge interface >> >> Lawrence Farr wrote: >> > I have a Supermicro H8DAR-T based server, that was happily >> > running 6-stable from last year sometime. I swapped it out and >> > have been trying to get -CURRENT installed on it but it hangs >> > solid as soon as you configure the bge0 interface. The bge1 >> > interface will work occasionally tho. To try and rule out a >> > hardware fault I booted an AMD64-6.0RC1 cd that I had, which >> > had no problems at all with the interface: >> > >> > http://www.epcdirect.com/bootlog/6boot.txt >> > >> > But the current snapshot from June, and from todays source >> > hangs solid as soon as you try to set up the bge0 interface. >> > >> > http://www.epcdirect.com/bootlog/currentboot.txt >> > >> > As you can see, it hangs solid at "Setting hostname". >> > >> > I've also removed the 3ware card "just in case" but it made >> > no difference. Latest BIOS too. I found some references to >> > a similar problem with bge recently too: >> > >> > http://lists.freebsd.org/pipermail/freebsd-current/2007- >> August/075998.html >> > >> > >> > Anyone else seeing this? >> > >> >> Same here with a Supermicro H8SSL-I2 (Serverworks HT1000 based). >> >> bge0 locks the system hard when going up, bge1 OK (but goes down a few >> hours after start). Also, an ifconfig indicates: >> >> bge0: flags=8802 metric 0 mtu 1500 >> options=9b >> ether 00:30:48:5e:6e:56 >> media: Ethernet autoselect (none ) >> ^^^^^^^^^^^^^^^^^^ >> status: no carrier >> bge1: flags=8843 metric 0 mtu >> 1500 >> options=9b >> ether 00:30:48:5e:6e:57 >> inet 192.168.1.49 netmask 0xffffff00 broadcast 192.168.1.255 >> media: Ethernet autoselect (1000baseTX ) >> status: active >> >> An the dmesg shows: (see "^^^^..") >> >> . >> . >> bge0: > 0x2100> mem 0xff4f0000-0xff4fffff irq 24 at device 3.0 on pci2 >> miibus0: on bge0 >> brgphy0: PHY 1 on miibus0 >> brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, >> 1000baseT-FDX, auto >> bge0: Ethernet address: 00:30:48:5e:6e:56 >> bge0: [ITHREAD] >> pci2:3:1: bad VPD cksum, remain 14 >> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >> bge1: > 0x2100> >> mem 0xff4e0000-0xff4effff irq 25 at device 3.1 on pci2 >> miibus1: on bge1 >> brgphy1: PHY 1 on miibus1 >> brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, >> 1000baseT-FDX, auto >> bge1: Ethernet address: 00:30:48:5e:6e:57 >> bge1: [ITHREAD] >> . >> . >> >> (I also have strange problems with the SATA controller and recent >> kernels (that works fine on other machines) that seems to read random >> sectors (at least not those requested) causing core-dumps, compiler >> internal errors, trashed sources and false positives about corrupted >> filesystems.I don't know what is going on on this platform but it >> smells^Gdoesn't looks very sane.) >> >> RN. >> IeM >> >> > > This is still hanging with yesterdays current in i386 and AMD64, is it > worth > opening a PR? > > > > ------------------------------ > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > End of freebsd-current Digest, Vol 212, Issue 7 > *********************************************** >