From owner-freebsd-hardware@FreeBSD.ORG Mon Jun 28 13:39:55 2010 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B97EA106566C for ; Mon, 28 Jun 2010 13:39:55 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 8B75F8FC1E for ; Mon, 28 Jun 2010 13:39:55 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 22A4646B03; Mon, 28 Jun 2010 09:39:55 -0400 (EDT) Received: from jhbbsd.localnet (smtp.hudson-trading.com [209.249.190.9]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id E25268A03C; Mon, 28 Jun 2010 09:39:53 -0400 (EDT) From: John Baldwin To: Ireneusz Pluta Date: Mon, 28 Jun 2010 09:37:56 -0400 User-Agent: KMail/1.12.1 (FreeBSD/7.3-CBSD-20100217; KDE/4.3.1; amd64; ; ) References: <4C2499B5.3030404@wp.pl> <201006251303.41457.jhb@freebsd.org> <4C2518CD.1020900@wp.pl> In-Reply-To: <4C2518CD.1020900@wp.pl> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201006280937.56174.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Mon, 28 Jun 2010 09:39:53 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=4.2 tests=AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: freebsd-hardware@freebsd.org Subject: Re: System hangs during heavy sequential write to mfi device X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jun 2010 13:39:55 -0000 On Friday 25 June 2010 4:59:57 pm Ireneusz Pluta wrote: > John Baldwin pisze: > > > > Hmmm. You might have a hardware issue. OTOH, you can try seeing if you have > > a BIOS option to disable PCIE error logging. > is it one of them?: > > Assert NMI on SERR > Assert NMI on PERR > > (pdf page 109 of: -> > http://download.intel.com/support/motherboards/server/s5520hc/sb/e39529013_s5520hc_s5500hcv_s5520hct_tps_r1_9.pdf) Well, that will turn off the NMIs. Not sure if it will affect the event logging, but it is worth a shot. -- John Baldwin From owner-freebsd-hardware@FreeBSD.ORG Mon Jun 28 16:00:23 2010 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B22CB106566C for ; Mon, 28 Jun 2010 16:00:23 +0000 (UTC) (envelope-from ipluta@wp.pl) Received: from mx3.wp.pl (mx3.wp.pl [212.77.101.7]) by mx1.freebsd.org (Postfix) with ESMTP id 3D84B8FC15 for ; Mon, 28 Jun 2010 16:00:22 +0000 (UTC) Received: (wp-smtpd smtp.wp.pl 15054 invoked from network); 28 Jun 2010 18:00:08 +0200 Received: from 121-20-N1.aster.pl (HELO [127.0.0.1]) (ipluta@[94.75.121.20]) (envelope-sender ) by smtp.wp.pl (WP-SMTPD) with AES256-SHA encrypted SMTP for ; 28 Jun 2010 18:00:08 +0200 Message-ID: <4C28C706.80309@wp.pl> Date: Mon, 28 Jun 2010 18:00:06 +0200 From: Ireneusz Pluta User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: John Baldwin References: <4C2499B5.3030404@wp.pl> <201006251303.41457.jhb@freebsd.org> <4C2518CD.1020900@wp.pl> <201006280937.56174.jhb@freebsd.org> In-Reply-To: <201006280937.56174.jhb@freebsd.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-WP-AV: skaner antywirusowy poczty Wirtualnej Polski S. A. X-WP-SPAM: NO 0000000 [4eP0] Cc: freebsd-hardware@freebsd.org Subject: Re: System hangs during heavy sequential write to mfi device X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jun 2010 16:00:23 -0000 John Baldwin pisze: > On Friday 25 June 2010 4:59:57 pm Ireneusz Pluta wrote: > >> John Baldwin pisze: >> >>> Hmmm. You might have a hardware issue. OTOH, you can try seeing if you have >>> a BIOS option to disable PCIE error logging. >>> >> is it one of them?: >> >> Assert NMI on SERR >> Assert NMI on PERR >> >> (pdf page 109 of: -> >> http://download.intel.com/support/motherboards/server/s5520hc/sb/e39529013_s5520hc_s5500hcv_s5520hct_tps_r1_9.pdf) >> > > Well, that will turn off the NMIs. Not sure if it will affect the event > logging, but it is worth a shot. > Per BIOS setup documentation: On SERR, generate an NMI and log an error. Note: [Enabled] must be selected for the Assert NMI on PERR setup option to be visible. and: On PERR, generate an NMI and log an error. Note: This option is only active if the Assert NMI on SERR option is [Enabled] selected. However, disabling them did not change anything. From owner-freebsd-hardware@FreeBSD.ORG Mon Jun 28 17:26:20 2010 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6974D106564A for ; Mon, 28 Jun 2010 17:26:20 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 3CC428FC1A for ; Mon, 28 Jun 2010 17:26:20 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 73D6F46B09; Mon, 28 Jun 2010 13:26:19 -0400 (EDT) Received: from jhbbsd.localnet (smtp.hudson-trading.com [209.249.190.9]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id A663C8A03C; Mon, 28 Jun 2010 13:26:13 -0400 (EDT) From: John Baldwin To: Ireneusz Pluta Date: Mon, 28 Jun 2010 13:26:08 -0400 User-Agent: KMail/1.12.1 (FreeBSD/7.3-CBSD-20100217; KDE/4.3.1; amd64; ; ) References: <4C2499B5.3030404@wp.pl> <201006280937.56174.jhb@freebsd.org> <4C28C706.80309@wp.pl> In-Reply-To: <4C28C706.80309@wp.pl> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201006281326.08896.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Mon, 28 Jun 2010 13:26:13 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=4.2 tests=AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: freebsd-hardware@freebsd.org Subject: Re: System hangs during heavy sequential write to mfi device X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jun 2010 17:26:20 -0000 On Monday 28 June 2010 12:00:06 pm Ireneusz Pluta wrote: > > John Baldwin pisze: > > On Friday 25 June 2010 4:59:57 pm Ireneusz Pluta wrote: > > > >> John Baldwin pisze: > >> > >>> Hmmm. You might have a hardware issue. OTOH, you can try seeing if you have > >>> a BIOS option to disable PCIE error logging. > >>> > >> is it one of them?: > >> > >> Assert NMI on SERR > >> Assert NMI on PERR > >> > >> (pdf page 109 of: -> > >> http://download.intel.com/support/motherboards/server/s5520hc/sb/e39529013_s5520hc_s5500hcv_s5520hct_tps_r1_9.pdf) > >> > > > > Well, that will turn off the NMIs. Not sure if it will affect the event > > logging, but it is worth a shot. > > > Per BIOS setup documentation: > > On SERR, generate an NMI and log an error. > Note: [Enabled] must be selected for the Assert NMI > on PERR setup option to be visible. > > and: > > On PERR, generate an NMI and log an error. > Note: This option is only active if the Assert NMI on > SERR option is [Enabled] selected. > > However, disabling them did not change anything. Is it still logging errors and sending NMIs with them disabled? -- John Baldwin From owner-freebsd-hardware@FreeBSD.ORG Mon Jun 28 17:57:30 2010 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C1EFC106566B for ; Mon, 28 Jun 2010 17:57:30 +0000 (UTC) (envelope-from ipluta@wp.pl) Received: from mx3.wp.pl (mx3.wp.pl [212.77.101.7]) by mx1.freebsd.org (Postfix) with ESMTP id 4D0D98FC1A for ; Mon, 28 Jun 2010 17:57:29 +0000 (UTC) Received: (wp-smtpd smtp.wp.pl 20170 invoked from network); 28 Jun 2010 19:57:28 +0200 Received: from aayh18.neoplus.adsl.tpnet.pl (HELO [127.0.0.1]) (ipluta@[83.6.119.18]) (envelope-sender ) by smtp.wp.pl (WP-SMTPD) with AES256-SHA encrypted SMTP for ; 28 Jun 2010 19:57:28 +0200 Message-ID: <4C28E287.5010103@wp.pl> Date: Mon, 28 Jun 2010 19:57:27 +0200 From: Ireneusz Pluta User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: John Baldwin References: <4C2499B5.3030404@wp.pl> <201006280937.56174.jhb@freebsd.org> <4C28C706.80309@wp.pl> <201006281326.08896.jhb@freebsd.org> In-Reply-To: <201006281326.08896.jhb@freebsd.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-WP-AV: skaner antywirusowy poczty Wirtualnej Polski S. A. X-WP-SPAM: NO 0000000 [kfPk] Cc: freebsd-hardware@freebsd.org Subject: Re: System hangs during heavy sequential write to mfi device X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jun 2010 17:57:30 -0000 John Baldwin pisze: > On Monday 28 June 2010 12:00:06 pm Ireneusz Pluta wrote: > >> John Baldwin pisze: >> >>> On Friday 25 June 2010 4:59:57 pm Ireneusz Pluta wrote: >>> >>> >>>> John Baldwin pisze: >>>> >>>> >>>>> Hmmm. You might have a hardware issue. OTOH, you can try seeing if you >>>>> > have > >>>>> a BIOS option to disable PCIE error logging. >>>>> >>>>> >>>> is it one of them?: >>>> >>>> Assert NMI on SERR >>>> Assert NMI on PERR >>>> >>>> (pdf page 109 of: -> >>>> >>>> > http://download.intel.com/support/motherboards/server/s5520hc/sb/e39529013_s5520hc_s5500hcv_s5520hct_tps_r1_9.pdf) > >>>> >>>> >>> Well, that will turn off the NMIs. Not sure if it will affect the event >>> logging, but it is worth a shot. >>> >>> >> Per BIOS setup documentation: >> >> On SERR, generate an NMI and log an error. >> Note: [Enabled] must be selected for the Assert NMI >> on PERR setup option to be visible. >> >> and: >> >> On PERR, generate an NMI and log an error. >> Note: This option is only active if the Assert NMI on >> SERR option is [Enabled] selected. >> >> However, disabling them did not change anything. >> > > Is it still logging errors and sending NMIs with them disabled? > with the options I mentioned disabled. They do not have to be the only sources of NMIs, do they? From owner-freebsd-hardware@FreeBSD.ORG Mon Jun 28 18:18:48 2010 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 585501065672 for ; Mon, 28 Jun 2010 18:18:48 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 2CE9F8FC1F for ; Mon, 28 Jun 2010 18:18:48 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id DAE4046B23; Mon, 28 Jun 2010 14:18:47 -0400 (EDT) Received: from jhbbsd.localnet (smtp.hudson-trading.com [209.249.190.9]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id C64038A050; Mon, 28 Jun 2010 14:18:46 -0400 (EDT) From: John Baldwin To: Ireneusz Pluta Date: Mon, 28 Jun 2010 14:09:23 -0400 User-Agent: KMail/1.12.1 (FreeBSD/7.3-CBSD-20100217; KDE/4.3.1; amd64; ; ) References: <4C2499B5.3030404@wp.pl> <201006281326.08896.jhb@freebsd.org> <4C28E287.5010103@wp.pl> In-Reply-To: <4C28E287.5010103@wp.pl> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201006281409.23546.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Mon, 28 Jun 2010 14:18:46 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=4.2 tests=AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: freebsd-hardware@freebsd.org Subject: Re: System hangs during heavy sequential write to mfi device X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jun 2010 18:18:48 -0000 On Monday 28 June 2010 1:57:27 pm Ireneusz Pluta wrote: > John Baldwin pisze: > > On Monday 28 June 2010 12:00:06 pm Ireneusz Pluta wrote: > > > >> John Baldwin pisze: > >> > >>> On Friday 25 June 2010 4:59:57 pm Ireneusz Pluta wrote: > >>> > >>> > >>>> John Baldwin pisze: > >>>> > >>>> > >>>>> Hmmm. You might have a hardware issue. OTOH, you can try seeing if you > >>>>> > > have > > > >>>>> a BIOS option to disable PCIE error logging. > >>>>> > >>>>> > >>>> is it one of them?: > >>>> > >>>> Assert NMI on SERR > >>>> Assert NMI on PERR > >>>> > >>>> (pdf page 109 of: -> > >>>> > >>>> > > http://download.intel.com/support/motherboards/server/s5520hc/sb/e39529013_s5520hc_s5500hcv_s5520hct_tps_r1_9.pdf) > > > >>>> > >>>> > >>> Well, that will turn off the NMIs. Not sure if it will affect the event > >>> logging, but it is worth a shot. > >>> > >>> > >> Per BIOS setup documentation: > >> > >> On SERR, generate an NMI and log an error. > >> Note: [Enabled] must be selected for the Assert NMI > >> on PERR setup option to be visible. > >> > >> and: > >> > >> On PERR, generate an NMI and log an error. > >> Note: This option is only active if the Assert NMI on > >> SERR option is [Enabled] selected. > >> > >> However, disabling them did not change anything. > >> > > > > Is it still logging errors and sending NMIs with them disabled? > > > with the options I mentioned disabled. They do not have to be the only > sources of NMIs, do they? Well, they should be the sources of the log messages you found in your system event log. There is a good chance that you have some broken hardware somewhere, I'm not sure how easy it is for you to debug that via swapping out components, but the RAID controller is the first thing I would try. -- John Baldwin From owner-freebsd-hardware@FreeBSD.ORG Mon Jun 28 23:47:14 2010 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CA3FA106566B; Mon, 28 Jun 2010 23:47:14 +0000 (UTC) (envelope-from lists@mawer.org) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 7027E8FC13; Mon, 28 Jun 2010 23:47:14 +0000 (UTC) Received: by vws13 with SMTP id 13so8453316vws.13 for ; Mon, 28 Jun 2010 16:47:05 -0700 (PDT) MIME-Version: 1.0 Received: by 10.220.162.148 with SMTP id v20mr3000060vcx.176.1277767186454; Mon, 28 Jun 2010 16:19:46 -0700 (PDT) Received: by 10.220.194.5 with HTTP; Mon, 28 Jun 2010 16:19:46 -0700 (PDT) In-Reply-To: <201006281409.23546.jhb@freebsd.org> References: <4C2499B5.3030404@wp.pl> <201006281326.08896.jhb@freebsd.org> <4C28E287.5010103@wp.pl> <201006281409.23546.jhb@freebsd.org> Date: Tue, 29 Jun 2010 09:19:46 +1000 Message-ID: From: Antony Mawer To: John Baldwin Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Ireneusz Pluta , freebsd-hardware@freebsd.org Subject: Re: System hangs during heavy sequential write to mfi device X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jun 2010 23:47:14 -0000 On Tue, Jun 29, 2010 at 4:09 AM, John Baldwin wrote: > On Monday 28 June 2010 1:57:27 pm Ireneusz Pluta wrote: >> John Baldwin pisze: >> > On Monday 28 June 2010 12:00:06 pm Ireneusz Pluta wrote: >> > >> >> John Baldwin pisze: >> >> >> >>> On Friday 25 June 2010 4:59:57 pm Ireneusz Pluta wrote: >> >>> >> >>> >> >>>> John Baldwin pisze: >> >>>> >> >>>> >> >>>>> Hmmm. =A0You might have a hardware issue. =A0OTOH, you can try see= ing if > you >> >>>>> >> > have >> > >> >>>>> a BIOS option to disable PCIE error logging. >> >>>>> >> >>>>> >> >>>> is it one of them?: >> >>>> >> >>>> Assert NMI on SERR >> >>>> Assert NMI on PERR >> >>>> >> >>>> (pdf page 109 of: -> >> >>>> >> >>>> >> > > http://download.intel.com/support/motherboards/server/s5520hc/sb/e3952901= 3_s5520hc_s5500hcv_s5520hct_tps_r1_9.pdf) >> > >> >>>> >> >>>> >> >>> Well, that will turn off the NMIs. =A0Not sure if it will affect the= event >> >>> logging, but it is worth a shot. >> >>> >> >>> >> >> Per BIOS setup documentation: >> >> >> >> On SERR, generate an NMI and log an error. >> >> Note: [Enabled] must be selected for the Assert NMI >> >> on PERR setup option to be visible. >> >> >> >> and: >> >> >> >> On PERR, generate an NMI and log an error. >> >> Note: This option is only active if the Assert NMI on >> >> SERR option is [Enabled] selected. >> >> >> >> However, disabling them did not change anything. >> >> >> > >> > Is it still logging errors and sending NMIs with them disabled? >> > >> with the options I mentioned disabled. They do not have to be the only >> sources of NMIs, do they? > > Well, they should be the sources of the log messages you found in your sy= stem > event log. =A0There is a good chance that you have some broken hardware > somewhere, I'm not sure how easy it is for you to debug that via swapping= out > components, but the RAID controller is the first thing I would try. You might want to try a BIOS update to see if it resolves these problems ... I seem to remember some mention of these sorts of errors in the change log of one of the recent Intel server board BIOSes. -- Antony From owner-freebsd-hardware@FreeBSD.ORG Tue Jun 29 05:36:30 2010 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 31808106564A for ; Tue, 29 Jun 2010 05:36:30 +0000 (UTC) (envelope-from ocrow@skymind.com) Received: from skink.simplexity.net (skink.simplexity.net [209.209.9.228]) by mx1.freebsd.org (Postfix) with ESMTP id 1BE3A8FC14 for ; Tue, 29 Jun 2010 05:36:29 +0000 (UTC) Received: from [10.25.2.100] (adsl-69-226-234-190.dsl.pltn13.pacbell.net [69.226.234.190]) (authenticated bits=0) by skink.simplexity.net (8.14.3/8.14.3) with ESMTP id o5T5aS1G062528 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT) for ; Mon, 28 Jun 2010 22:36:29 -0700 (PDT) (envelope-from ocrow@skymind.com) Message-ID: <4C29864F.1070609@skymind.com> Date: Mon, 28 Jun 2010 22:36:15 -0700 From: Oliver Crow User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.10) Gecko/20100512 Thunderbird/3.0.5 MIME-Version: 1.0 To: freebsd-hardware@freebsd.org References: <4C23E2CB.1070008@skymind.com> In-Reply-To: <4C23E2CB.1070008@skymind.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: JMicron JMC250 jme interface not receiving X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jun 2010 05:36:30 -0000 After getting stuck on this I left it for a couple of days while I tried to install Ubuntu on the same machine. Then I came back to try FreeBSD again, and it was working fine, as if by magic. I don't know what to make of this, whether somehow the Ubuntu fiddling had an effect, or for some other reason it settled down into a working condition. Perhaps I had some odd problem with incorrect arp cache entries that finally timed out. I can't really understand it. In any event, I now see the jme driver working fine on the Eee Box B202 under both FreeBSD 7.2-RELEASE and 8.0-RELEASE. Oliver On 6/24/2010 3:57 PM, Oliver Crow wrote: > > I'm asking for help getting a JMicron JMC250 network interface working > under FreeBSD. It appears that the jme driver is not functioning > correctly on this hardware. The machine is an Asus Eee Box B202 with a > JMicron JMC250 ethernet chip on the motherboard. I'm running the > 8.0-RELEASE Generic kernel. The machine boots fine, recognizing the > interface as jme0, but I can't connect to any hosts on the network. > When I ping the router or another host on the subnet, I see the packet > lights flash on the router, but I get no ping responses. The arp cache > remains empty. > > I know that it's not a hardware problem, because the machine can > connect to the network fine under Windows XP, using the same NIC, > cable and router port. Under FreeBSD I can assign an IP address, take > the interface down and up, and can see the link light on the router > turn off and on again when the interface comes up, but I can't ping > any hosts. > > When I ping the EeeBox from another host the EeeBox MAC address is > added to the other hosts' arp cache, but no ping response packets are > received. On the EeeBox the arp cache remains empty. Perhaps the > EeeBox can transmit packets, but somehow not receive? > > I have tried booting with MSI and MSI-X disabled (in loader.conf: > hw.jme.msi_disable="1", hw.jme.msix_disable="1"). The interface came > up without MSI, but I was still unable to connect to any hosts. I > tried disabling the following interface options using ifconfig, also > without result: -rxcsum, -txcsum, -tso, -wol, -vlanhwtag. > > # pciconf -vlbc > ... > jme0@pci0:1:0:0: class=0x020000 card=0x839c1043 chip=0x0250197b > rev=0x11 hdr=0x00 > vendor = 'JMicron Technology Corp.' > class = network > subclass = ethernet > bar [10] = type Memory, range 32, base 0xfbefc000, size 16384, > enabled > bar [18] = type I/O Port, range 32, base 0xec80, size 128, enabled > bar [1c] = type I/O Port, range 32, base 0xe800, size 256, enabled > cap 01[68] = powerspec 3 supports D0 D3 current D0 > cap 10[50] = PCI-Express 1 legacy endpoint max data 128(128) link > x1(x1) > cap 11[40] = MSI-X supports 8 messages in map 0x10 enabled > cap 05[70] = MSI supports 8 messages, 64 bit, vector masks > > # ifconfig jme0 > > jme0: flags=8843 metric 0 mtu > 1500 > > options=219b > > ether e0:cb:4e:08:37:f5 > inet 10.25.2.49 netmask 0xffffff00 broadcast 10.25.2.255 > media: Ethernet autoselect (100baseTX ) > status: active > > # netstat -nr > > Routing tables > > Internet: > Destination Gateway Flags Refs Use Netif > Expire > 10.25.2.0/24 link#1 U 0 15 jme0 > 10.25.2.49 link#1 UHS 0 0 lo0 > 127.0.0.1 link#2 UH 0 4 lo0 > > # arp -a > > # ping 10.25.2.1 > > PING 10.25.2.1 (10.25.2.1): 56 data bytes > ping: sendto: Host is down > ping: sendto: Host is down > ping: sendto: Host is down > ping: sendto: Host is down > ^C > --- 10.25.2.1 ping statistics --- > 9 packets transmitted, 0 packets received, 100.0% packet loss > > # uname -a > > FreeBSD 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21 15:48:17 UTC > 2009 root@almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 > > > # dmesg > > Copyright (c) 1992-2009 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 8.0-RELEASE #0: Sat Nov 21 15:48:17 UTC 2009 > root@almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Intel(R) Atom(TM) CPU N270 @ 1.60GHz (1608.02-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x106c2 Stepping = 2 > > Features=0xbfe9fbff > > > Features2=0x40c39d> > AMD Features=0x100000 > AMD Features2=0x1 > TSC: P-state invariant > real memory = 1073741824 (1024 MB) > avail memory = 1027768320 (980 MB) > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > FreeBSD/SMP: 1 package(s) x 1 core(s) x 2 HTT threads > cpu0 (BSP): APIC ID: 0 > cpu1 (AP/HT): APIC ID: 1 > ACPI Warning: Optional field Pm2ControlBlock has zero address or > length: 0 820/0 20090521 tbfadt-655 > ACPI Warning: Invalid length for Pm2ControlBlock: 0, using default 8 > 20090521 tbfadt-707 > ioapic0: Changing APIC ID to 2 > ioapic0 irqs 0-23 on motherboard > kbd1 at kbdmux0 > acpi0: on motherboard > acpi0: [ITHREAD] > acpi0: Power Button (fixed) > acpi0: reservation of 0, a0000 (3) failed > acpi0: reservation of 100000, 3f700000 (3) failed > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 > acpi_hpet0: iomem 0xfed00000-0xfed003ff > on acpi0 > Timecounter "HPET" frequency 14318180 Hz quality 900 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > vgapci0: port 0xdc80-0xdc87 mem > 0xfbd00000-0xfbd7ffff,0xd0000000-0xdfffffff,0xfbcc0000-0xfbcfffff irq > 16 at device 2.0 on pci0 > agp0: on vgapci0 > agp0: detected 7932k stolen memory > agp0: aperture size is 256M > vgapci1: mem 0xfbd80000-0xfbdfffff at device > 2.1 on pci0 > pci0: at device 27.0 (no driver attached) > pcib1: irq 16 at device 28.0 on pci0 > pci3: on pcib1 > pcib2: irq 17 at device 28.1 on pci0 > pci2: on pcib2 > pci2: at device 0.0 (no driver attached) > pcib3: irq 18 at device 28.2 on pci0 > pci1: on pcib3 > jme0: port > 0xec80-0xecff,0xe800-0xe8ff mem 0xfbefc000-0xfbefffff irq 18 at device > 0.0 on pci1 > jme0: Using 8 MSIX messages. > miibus0: on jme0 > jmphy0: PHY 1 on miibus0 > jmphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > 1000baseT-FDX, auto > jme0: Ethernet address: e0:cb:4e:08:37:f5 > jme0: [FILTER] > jme0: [FILTER] > jme0: [FILTER] > jme0: [FILTER] > jme0: [FILTER] > jme0: [FILTER] > jme0: [FILTER] > jme0: [FILTER] > uhci0: port 0xd480-0xd49f > irq 23 at device 29.0 on pci0 > uhci0: [ITHREAD] > uhci0: LegSup = 0x0f30 > usbus0: on uhci0 > ... > > Thanks for any assistance, > Oliver > > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to > "freebsd-hardware-unsubscribe@freebsd.org" > From owner-freebsd-hardware@FreeBSD.ORG Wed Jun 30 10:09:23 2010 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 35899106566C for ; Wed, 30 Jun 2010 10:09:23 +0000 (UTC) (envelope-from ipluta@wp.pl) Received: from mx4.wp.pl (mx4.wp.pl [212.77.101.8]) by mx1.freebsd.org (Postfix) with ESMTP id B24548FC1A for ; Wed, 30 Jun 2010 10:09:22 +0000 (UTC) Received: (wp-smtpd smtp.wp.pl 26657 invoked from network); 30 Jun 2010 12:09:19 +0200 Received: from 121-20-N1.aster.pl (HELO [127.0.0.1]) (ipluta@[94.75.121.20]) (envelope-sender ) by smtp.wp.pl (WP-SMTPD) with AES256-SHA encrypted SMTP for ; 30 Jun 2010 12:09:19 +0200 Message-ID: <4C2B17CE.5060209@wp.pl> Date: Wed, 30 Jun 2010 12:09:18 +0200 From: Ireneusz Pluta User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: Antony Mawer References: <4C2499B5.3030404@wp.pl> <201006281326.08896.jhb@freebsd.org> <4C28E287.5010103@wp.pl> <201006281409.23546.jhb@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-WP-AV: skaner antywirusowy poczty Wirtualnej Polski S. A. X-WP-SPAM: NO 0000000 [UROk] Cc: freebsd-hardware@freebsd.org Subject: Re: System hangs during heavy sequential write to mfi device X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jun 2010 10:09:23 -0000 Antony Mawer pisze: > On Tue, Jun 29, 2010 at 4:09 AM, John Baldwin wrote: > >> On Monday 28 June 2010 1:57:27 pm Ireneusz Pluta wrote: >> >>> John Baldwin pisze: >>> >>>> On Monday 28 June 2010 12:00:06 pm Ireneusz Pluta wrote: >>>> >>>> >>>>> John Baldwin pisze: >>>>> >>>>> >>>>>> On Friday 25 June 2010 4:59:57 pm Ireneusz Pluta wrote: >>>>>> >>>>>> >>>>>> >>>>>>> John Baldwin pisze: >>>>>>> >>>>>>> >>>>>>> >>>>>>>> Hmmm. You might have a hardware issue. OTOH, you can try seeing if >>>>>>>> >> you >> >>>> have >>>> >>>> >>>>>>>> a BIOS option to disable PCIE error logging. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> is it one of them?: >>>>>>> >>>>>>> Assert NMI on SERR >>>>>>> Assert NMI on PERR >>>>>>> >>>>>>> (pdf page 109 of: -> >>>>>>> >>>>>>> >>>>>>> >> http://download.intel.com/support/motherboards/server/s5520hc/sb/e39529013_s5520hc_s5500hcv_s5520hct_tps_r1_9.pdf) >> >>>>>>> >>>>>> Well, that will turn off the NMIs. Not sure if it will affect the event >>>>>> logging, but it is worth a shot. >>>>>> >>>>>> >>>>>> >>>>> Per BIOS setup documentation: >>>>> >>>>> On SERR, generate an NMI and log an error. >>>>> Note: [Enabled] must be selected for the Assert NMI >>>>> on PERR setup option to be visible. >>>>> >>>>> and: >>>>> >>>>> On PERR, generate an NMI and log an error. >>>>> Note: This option is only active if the Assert NMI on >>>>> SERR option is [Enabled] selected. >>>>> >>>>> However, disabling them did not change anything. >>>>> >>>>> >>>> Is it still logging errors and sending NMIs with them disabled? >>>> >>>> >>> with the options I mentioned disabled. They do not have to be the only >>> sources of NMIs, do they? >>> >> Well, they should be the sources of the log messages you found in your system >> event log. There is a good chance that you have some broken hardware >> somewhere, I'm not sure how easy it is for you to debug that via swapping out >> components, but the RAID controller is the first thing I would try. >> > > You might want to try a BIOS update to see if it resolves these > problems ... I seem to remember some mention of these sorts of errors > in the change log of one of the recent Intel server board BIOSes. > Yeah, I tried, and the problem dissappeared. I really could do that initially but none of the entries found in the BIOS changelog from Intel seemed to address my particular issue. From owner-freebsd-hardware@FreeBSD.ORG Thu Jul 1 23:40:25 2010 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 170A2106566C for ; Thu, 1 Jul 2010 23:40:25 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-px0-f182.google.com (mail-px0-f182.google.com [209.85.212.182]) by mx1.freebsd.org (Postfix) with ESMTP id D923B8FC13 for ; Thu, 1 Jul 2010 23:40:24 +0000 (UTC) Received: by pxi3 with SMTP id 3so1151001pxi.13 for ; Thu, 01 Jul 2010 16:40:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:from:date:to:cc :subject:message-id:reply-to:references:mime-version:content-type :content-disposition:in-reply-to:user-agent; bh=iL4JhpEGh/wXgyGuaht+fhSPz40N2u4hNJuzz7RDOhA=; b=nysgZjOBNY9SAs5cmLlHxytiatxRRKTh9RKz75V1rCOnGU3Rap45PhIaioeB7IhHee p6+9oDgQDORYZ4o1T3QMaILnsXFo6ifgE27nWh0Faha/omQ3uDoCLki5OG7ZB7Teyax9 RAOa+56uh8eu1on0HkvqOwEtB8rbZfFElEWSc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=dvUS0aDfTI3fofF/UX1dZILjdWumZqJ63szo0s9168VgIaGxe2XeV/A/ymQuuRR/b4 A09Yan6JownDMggsTuVv5i+zLiSLf/cfjFBIo+3cypAK17vDO1lZB/MwhgrXDBmrF+TF PZZnqAyXj6fTSjChlEXVLcHoW4d+yiuZCbNP8= Received: by 10.142.132.12 with SMTP id f12mr298167wfd.130.1278027617668; Thu, 01 Jul 2010 16:40:17 -0700 (PDT) Received: from pyunyh@gmail.com ([174.35.1.224]) by mx.google.com with ESMTPS id 21sm32260wfi.17.2010.07.01.16.40.16 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 01 Jul 2010 16:40:16 -0700 (PDT) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Thu, 1 Jul 2010 16:39:51 -0700 From: Pyun YongHyeon Date: Thu, 1 Jul 2010 16:39:51 -0700 To: Oliver Crow Message-ID: <20100701233951.GI7090@michelle.cdnetworks.com> References: <4C23E2CB.1070008@skymind.com> <4C29864F.1070609@skymind.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4C29864F.1070609@skymind.com> User-Agent: Mutt/1.4.2.3i Cc: freebsd-hardware@freebsd.org Subject: Re: JMicron JMC250 jme interface not receiving X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2010 23:40:25 -0000 On Mon, Jun 28, 2010 at 10:36:15PM -0700, Oliver Crow wrote: > > After getting stuck on this I left it for a couple of days while I tried > to install Ubuntu on the same machine. Then I came back to try FreeBSD > again, and it was working fine, as if by magic. I don't know what to In previous mail, you mentioned that other host that initiated ping got ethernet address of jme0 which in turn means both TX and RX of jme0 works as expected. The subsequent unresponsive ping indicates jme0 didn't receive unicast ping(ICMP ECHO) request. I'm not sure how this can happen and I never seen this kind of issue with my sample boards that JMicron sent to me. > make of this, whether somehow the Ubuntu fiddling had an effect, or for > some other reason it settled down into a working condition. Perhaps I > had some odd problem with incorrect arp cache entries that finally timed > out. I can't really understand it. > Yeah, it may explain it. If you encounter the same issue again, please compare the ethernet hardware address of jme0 and ethernet address of ARP entry on another host. > In any event, I now see the jme driver working fine on the Eee Box B202 > under both FreeBSD 7.2-RELEASE and 8.0-RELEASE. > Ok, thanks for letting me know. > Oliver > > On 6/24/2010 3:57 PM, Oliver Crow wrote: > > > >I'm asking for help getting a JMicron JMC250 network interface working > >under FreeBSD. It appears that the jme driver is not functioning > >correctly on this hardware. The machine is an Asus Eee Box B202 with a > >JMicron JMC250 ethernet chip on the motherboard. I'm running the > >8.0-RELEASE Generic kernel. The machine boots fine, recognizing the > >interface as jme0, but I can't connect to any hosts on the network. > >When I ping the router or another host on the subnet, I see the packet > >lights flash on the router, but I get no ping responses. The arp cache > >remains empty. > > > >I know that it's not a hardware problem, because the machine can > >connect to the network fine under Windows XP, using the same NIC, > >cable and router port. Under FreeBSD I can assign an IP address, take > >the interface down and up, and can see the link light on the router > >turn off and on again when the interface comes up, but I can't ping > >any hosts. > > > >When I ping the EeeBox from another host the EeeBox MAC address is > >added to the other hosts' arp cache, but no ping response packets are > >received. On the EeeBox the arp cache remains empty. Perhaps the > >EeeBox can transmit packets, but somehow not receive? > > > >I have tried booting with MSI and MSI-X disabled (in loader.conf: > >hw.jme.msi_disable="1", hw.jme.msix_disable="1"). The interface came > >up without MSI, but I was still unable to connect to any hosts. I > >tried disabling the following interface options using ifconfig, also > >without result: -rxcsum, -txcsum, -tso, -wol, -vlanhwtag. > > > ># pciconf -vlbc > >... > >jme0@pci0:1:0:0: class=0x020000 card=0x839c1043 chip=0x0250197b > >rev=0x11 hdr=0x00 > > vendor = 'JMicron Technology Corp.' > > class = network > > subclass = ethernet > > bar [10] = type Memory, range 32, base 0xfbefc000, size 16384, > >enabled > > bar [18] = type I/O Port, range 32, base 0xec80, size 128, enabled > > bar [1c] = type I/O Port, range 32, base 0xe800, size 256, enabled > > cap 01[68] = powerspec 3 supports D0 D3 current D0 > > cap 10[50] = PCI-Express 1 legacy endpoint max data 128(128) link > >x1(x1) > > cap 11[40] = MSI-X supports 8 messages in map 0x10 enabled > > cap 05[70] = MSI supports 8 messages, 64 bit, vector masks > > > ># ifconfig jme0 > > > >jme0: flags=8843 metric 0 mtu > >1500 > > > >options=219b > > > > ether e0:cb:4e:08:37:f5 > > inet 10.25.2.49 netmask 0xffffff00 broadcast 10.25.2.255 > > media: Ethernet autoselect (100baseTX ) > > status: active > > > ># netstat -nr > > > >Routing tables > > > >Internet: > >Destination Gateway Flags Refs Use Netif > >Expire > >10.25.2.0/24 link#1 U 0 15 jme0 > >10.25.2.49 link#1 UHS 0 0 lo0 > >127.0.0.1 link#2 UH 0 4 lo0 > > > ># arp -a > > > ># ping 10.25.2.1 > > > >PING 10.25.2.1 (10.25.2.1): 56 data bytes > >ping: sendto: Host is down > >ping: sendto: Host is down > >ping: sendto: Host is down > >ping: sendto: Host is down > >^C > >--- 10.25.2.1 ping statistics --- > >9 packets transmitted, 0 packets received, 100.0% packet loss > > > ># uname -a > > > >FreeBSD 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21 15:48:17 UTC > >2009 root@almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 > > > > > ># dmesg > > > >Copyright (c) 1992-2009 The FreeBSD Project. > >Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > > The Regents of the University of California. All rights reserved. > >FreeBSD is a registered trademark of The FreeBSD Foundation. > >FreeBSD 8.0-RELEASE #0: Sat Nov 21 15:48:17 UTC 2009 > > root@almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC > >Timecounter "i8254" frequency 1193182 Hz quality 0 > >CPU: Intel(R) Atom(TM) CPU N270 @ 1.60GHz (1608.02-MHz 686-class CPU) > > Origin = "GenuineIntel" Id = 0x106c2 Stepping = 2 > > > >Features=0xbfe9fbff > > > > > >Features2=0x40c39d> > > AMD Features=0x100000 > > AMD Features2=0x1 > > TSC: P-state invariant > >real memory = 1073741824 (1024 MB) > >avail memory = 1027768320 (980 MB) > >ACPI APIC Table: > >FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > >FreeBSD/SMP: 1 package(s) x 1 core(s) x 2 HTT threads > > cpu0 (BSP): APIC ID: 0 > > cpu1 (AP/HT): APIC ID: 1 > >ACPI Warning: Optional field Pm2ControlBlock has zero address or > >length: 0 820/0 20090521 tbfadt-655 > >ACPI Warning: Invalid length for Pm2ControlBlock: 0, using default 8 > >20090521 tbfadt-707 > >ioapic0: Changing APIC ID to 2 > >ioapic0 irqs 0-23 on motherboard > >kbd1 at kbdmux0 > >acpi0: on motherboard > >acpi0: [ITHREAD] > >acpi0: Power Button (fixed) > >acpi0: reservation of 0, a0000 (3) failed > >acpi0: reservation of 100000, 3f700000 (3) failed > >Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > >acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 > >acpi_hpet0: iomem 0xfed00000-0xfed003ff > >on acpi0 > >Timecounter "HPET" frequency 14318180 Hz quality 900 > >pcib0: port 0xcf8-0xcff on acpi0 > >pci0: on pcib0 > >vgapci0: port 0xdc80-0xdc87 mem > >0xfbd00000-0xfbd7ffff,0xd0000000-0xdfffffff,0xfbcc0000-0xfbcfffff irq > >16 at device 2.0 on pci0 > >agp0: on vgapci0 > >agp0: detected 7932k stolen memory > >agp0: aperture size is 256M > >vgapci1: mem 0xfbd80000-0xfbdfffff at device > >2.1 on pci0 > >pci0: at device 27.0 (no driver attached) > >pcib1: irq 16 at device 28.0 on pci0 > >pci3: on pcib1 > >pcib2: irq 17 at device 28.1 on pci0 > >pci2: on pcib2 > >pci2: at device 0.0 (no driver attached) > >pcib3: irq 18 at device 28.2 on pci0 > >pci1: on pcib3 > >jme0: port > >0xec80-0xecff,0xe800-0xe8ff mem 0xfbefc000-0xfbefffff irq 18 at device > >0.0 on pci1 > >jme0: Using 8 MSIX messages. > >miibus0: on jme0 > >jmphy0: PHY 1 on miibus0 > >jmphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > >1000baseT-FDX, auto > >jme0: Ethernet address: e0:cb:4e:08:37:f5 > >jme0: [FILTER] > >jme0: [FILTER] > >jme0: [FILTER] > >jme0: [FILTER] > >jme0: [FILTER] > >jme0: [FILTER] > >jme0: [FILTER] > >jme0: [FILTER] > >uhci0: port 0xd480-0xd49f > >irq 23 at device 29.0 on pci0 > >uhci0: [ITHREAD] > >uhci0: LegSup = 0x0f30 > >usbus0: on uhci0 > >... > > > >Thanks for any assistance, > >Oliver > > > >_______________________________________________ > >freebsd-hardware@freebsd.org mailing list > >http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > >To unsubscribe, send any mail to > >"freebsd-hardware-unsubscribe@freebsd.org" > > > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org"