From owner-freebsd-drivers@FreeBSD.ORG Tue Nov 7 00:01:41 2006 Return-Path: X-Original-To: freebsd-drivers@freebsd.org Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2ED6216A407 for ; Tue, 7 Nov 2006 00:01:41 +0000 (UTC) (envelope-from wes@uia.net) Received: from smtp2.uia.net (smtp2.uia.net [66.146.0.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id DEAB743D46 for ; Tue, 7 Nov 2006 00:01:40 +0000 (GMT) (envelope-from wes@uia.net) Received: from [10.50.0.123] (fw1.uia.net [66.146.1.4]) by smtp2.uia.net (8.13.6/8.11.6/2.1) with ESMTP id kA701a4X021412 for ; Mon, 6 Nov 2006 16:01:40 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v752.2) To: freebsd-drivers@freebsd.org Message-Id: <9EA29BB6-C492-40AA-A750-04841670EBCA@uia.net> From: Wes Zuber Date: Mon, 6 Nov 2006 16:01:33 -0800 X-Mailer: Apple Mail (2.752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Dell SC440 and Broadcom 5787 X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Nov 2006 00:01:41 -0000 Hi there, We are experiencing kernel panics for FreeBSD 6.1 release. cvsup to the latest. I recompiled the kernel with the latest bge drivers but I still get the same error. bge0 X-Original-To: freebsd-drivers@freebsd.org Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4C4A916A40F for ; Tue, 7 Nov 2006 01:15:11 +0000 (UTC) (envelope-from davidch@broadcom.com) Received: from mms2.broadcom.com (mms2.broadcom.com [216.31.210.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id C89DD43D58 for ; Tue, 7 Nov 2006 01:15:10 +0000 (GMT) (envelope-from davidch@broadcom.com) Received: from 10.10.64.154 by mms2.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.0)); Mon, 06 Nov 2006 17:14:58 -0800 X-Server-Uuid: 05DA3F36-9AA8-4766-A7E5-53B43A7C42E6 Received: by mail-irva-10.broadcom.com (Postfix, from userid 47) id 909A92B2; Mon, 6 Nov 2006 17:14:58 -0800 (PST) Received: from mail-irva-8.broadcom.com (mail-irva-8 [10.10.64.221]) by mail-irva-10.broadcom.com (Postfix) with ESMTP id 6C17B2B0; Mon, 6 Nov 2006 17:14:58 -0800 (PST) Received: from mail-irva-12.broadcom.com (mail-irva-12.broadcom.com [10.10.64.146]) by mail-irva-8.broadcom.com (MOS 3.7.5a-GA) with ESMTP id EKH41729; Mon, 6 Nov 2006 17:14:58 -0800 (PST) Received: from NT-IRVA-0750.brcm.ad.broadcom.com (nt-irva-0750 [10.8.194.64]) by mail-irva-12.broadcom.com (Postfix) with ESMTP id 10C5669CA4; Mon, 6 Nov 2006 17:14:58 -0800 (PST) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Mon, 6 Nov 2006 17:14:57 -0800 Message-ID: <09BFF2FA5EAB4A45B6655E151BBDD90302433A1B@NT-IRVA-0750.brcm.ad.broadcom.com> In-Reply-To: <9EA29BB6-C492-40AA-A750-04841670EBCA@uia.net> Thread-Topic: Dell SC440 and Broadcom 5787 thread-index: AccCAMlP7jpbZ4N+Tey/KCh9btXcrwACPoaQ From: "David Christensen" To: "Wes Zuber" , freebsd-drivers@freebsd.org X-WSS-ID: 6951019839O2115053-01-01 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Cc: Subject: RE: Dell SC440 and Broadcom 5787 X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Nov 2006 01:15:11 -0000 > Hi there, >=20 > We are experiencing kernel panics for FreeBSD 6.1 release. cvsup to =20 > the latest. >=20 > I recompiled the kernel with the latest bge drivers but I still get =20 > the same error. >=20 > bge0 mem 0xefcf000-0xefcfffff > irq 17 at device 0.0 on pci4 >=20 > kernel trap 19 with interrupts disabled >=20 > NMI ISA a0 Eisa ff >=20 > Ram Parity error, likely Hardware failure > Fatal trap 19: non-maskeble interrupt trap while in kernel mode >=20 > Instuction pointer =3D 0x20:oxc0817f10 > stack pointer =3D 0x28:0xc0c20880 > frame pointer =3D 0x29:0xc0c208a4 > code segment =3D base 0x0 > limit 0xfffff, tpe ox1b =3D dpl 0, pres 1, def 32, granl > processor eflags =3D IPOL =3D 0 > current Process =3D 0 (swapper) > trap number =3D19 > panic: non-maskeble interrupt trap > uptime 1ms Looks like the OS is reporting a memory parity error. Does the OS run with the LOM disabled? Does the LOM work correctly under another OS? Did you run memtest86+ on the system to verify the memory? Dave From owner-freebsd-drivers@FreeBSD.ORG Tue Nov 7 01:30:33 2006 Return-Path: X-Original-To: freebsd-drivers@freebsd.org Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9E12016A40F for ; Tue, 7 Nov 2006 01:30:33 +0000 (UTC) (envelope-from wes@uia.net) Received: from smtp2.uia.net (smtp2.uia.net [66.146.0.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 68C3043D45 for ; Tue, 7 Nov 2006 01:30:33 +0000 (GMT) (envelope-from wes@uia.net) Received: from [10.50.0.123] (fw1.uia.net [66.146.1.4]) by smtp2.uia.net (8.13.6/8.11.6/2.1) with ESMTP id kA71UWFG020227; Mon, 6 Nov 2006 17:30:32 -0800 (PST) In-Reply-To: <09BFF2FA5EAB4A45B6655E151BBDD90302433A1B@NT-IRVA-0750.brcm.ad.broadcom.com> References: <09BFF2FA5EAB4A45B6655E151BBDD90302433A1B@NT-IRVA-0750.brcm.ad.broadcom.com> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <1331D139-46F8-49B6-A1DA-57F248F70845@uia.net> Content-Transfer-Encoding: 7bit From: Wes Zuber Date: Mon, 6 Nov 2006 17:30:25 -0800 To: David Christensen X-Mailer: Apple Mail (2.752.2) Cc: freebsd-drivers@freebsd.org Subject: Re: Dell SC440 and Broadcom 5787 X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Nov 2006 01:30:33 -0000 If we disable the NIC then everything loads as it should. We have several of these boxes from Dell. We tried it on another to make sure, but got the same results. We did not run memitest86 as disabling the NIC seemed to make everything work, plus it seemed to crash right after the the NIC driver load. This is our first try with an SC440. We have been using SC400, SC420 and SC430. Thanks, --Wes On Nov 6, 2006, at 5:14 PM, David Christensen wrote: >> Hi there, >> >> We are experiencing kernel panics for FreeBSD 6.1 release. cvsup to >> the latest. >> >> I recompiled the kernel with the latest bge drivers but I still get >> the same error. >> >> bge0 > mem 0xefcf000-0xefcfffff >> irq 17 at device 0.0 on pci4 >> >> kernel trap 19 with interrupts disabled >> >> NMI ISA a0 Eisa ff >> >> Ram Parity error, likely Hardware failure >> Fatal trap 19: non-maskeble interrupt trap while in kernel mode >> >> Instuction pointer = 0x20:oxc0817f10 >> stack pointer = 0x28:0xc0c20880 >> frame pointer = 0x29:0xc0c208a4 >> code segment = base 0x0 >> limit 0xfffff, tpe ox1b = dpl 0, pres 1, def 32, granl >> processor eflags = IPOL = 0 >> current Process = 0 (swapper) >> trap number =19 >> panic: non-maskeble interrupt trap >> uptime 1ms > > Looks like the OS is reporting a memory parity error. Does the > OS run with the LOM disabled? Does the LOM work correctly under > another OS? Did you run memtest86+ on the system to verify the > memory? > > Dave > > > From owner-freebsd-drivers@FreeBSD.ORG Tue Nov 7 15:16:53 2006 Return-Path: X-Original-To: freebsd-drivers@freebsd.org Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 311FA16A417 for ; Tue, 7 Nov 2006 15:16:53 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 945E343DF0 for ; Tue, 7 Nov 2006 15:15:45 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.6/8.13.6) with ESMTP id kA7FFVGf058066; Tue, 7 Nov 2006 10:15:33 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-drivers@freebsd.org Date: Tue, 7 Nov 2006 10:03:53 -0500 User-Agent: KMail/1.9.1 References: <09BFF2FA5EAB4A45B6655E151BBDD90302433A1B@NT-IRVA-0750.brcm.ad.broadcom.com> <1331D139-46F8-49B6-A1DA-57F248F70845@uia.net> In-Reply-To: <1331D139-46F8-49B6-A1DA-57F248F70845@uia.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200611071003.53651.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [192.168.0.1]); Tue, 07 Nov 2006 10:15:36 -0500 (EST) X-Virus-Scanned: ClamAV 0.88.3/2172/Tue Nov 7 09:04:48 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: Subject: Re: Dell SC440 and Broadcom 5787 X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Nov 2006 15:16:53 -0000 On Monday 06 November 2006 20:30, Wes Zuber wrote: > If we disable the NIC then everything loads as it should. We have > several of these boxes from Dell. We tried it on another to make > sure, but got the same results. > > We did not run memitest86 as disabling the NIC seemed to make > everything work, plus it seemed to crash right after the the NIC > driver load. This is our first try with an SC440. We have been using > SC400, SC420 and SC430. David, could this be related to the IPMI fixes in 6.2 and HEAD? Wes, try a kernel from RELENG_6 instead perhaps. > Thanks, > > --Wes > > On Nov 6, 2006, at 5:14 PM, David Christensen wrote: > > >> Hi there, > >> > >> We are experiencing kernel panics for FreeBSD 6.1 release. cvsup to > >> the latest. > >> > >> I recompiled the kernel with the latest bge drivers but I still get > >> the same error. > >> > >> bge0 >> mem 0xefcf000-0xefcfffff > >> irq 17 at device 0.0 on pci4 > >> > >> kernel trap 19 with interrupts disabled > >> > >> NMI ISA a0 Eisa ff > >> > >> Ram Parity error, likely Hardware failure > >> Fatal trap 19: non-maskeble interrupt trap while in kernel mode > >> > >> Instuction pointer = 0x20:oxc0817f10 > >> stack pointer = 0x28:0xc0c20880 > >> frame pointer = 0x29:0xc0c208a4 > >> code segment = base 0x0 > >> limit 0xfffff, tpe ox1b = dpl 0, pres 1, def 32, granl > >> processor eflags = IPOL = 0 > >> current Process = 0 (swapper) > >> trap number =19 > >> panic: non-maskeble interrupt trap > >> uptime 1ms > > > > Looks like the OS is reporting a memory parity error. Does the > > OS run with the LOM disabled? Does the LOM work correctly under > > another OS? Did you run memtest86+ on the system to verify the > > memory? > > > > Dave > > > > > > > > _______________________________________________ > freebsd-drivers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-drivers > To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@freebsd.org" > -- John Baldwin From owner-freebsd-drivers@FreeBSD.ORG Tue Nov 7 20:31:15 2006 Return-Path: X-Original-To: freebsd-drivers@freebsd.org Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C232A16A4D0; Tue, 7 Nov 2006 20:31:15 +0000 (UTC) (envelope-from wes@uia.net) Received: from smtp3.uia.net (smtp3.uia.net [66.146.0.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C1F343DA2; Tue, 7 Nov 2006 20:30:52 +0000 (GMT) (envelope-from wes@uia.net) Received: from [10.50.0.123] (fw1.uia.net [66.146.1.4]) by smtp3.uia.net (8.13.6/8.11.6/2.1) with ESMTP id kA7KUqYc053249; Tue, 7 Nov 2006 12:30:52 -0800 (PST) In-Reply-To: <200611071003.53651.jhb@freebsd.org> References: <09BFF2FA5EAB4A45B6655E151BBDD90302433A1B@NT-IRVA-0750.brcm.ad.broadcom.com> <1331D139-46F8-49B6-A1DA-57F248F70845@uia.net> <200611071003.53651.jhb@freebsd.org> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <5BE0205D-0ED0-45A7-B2E0-C1335769E92C@uia.net> Content-Transfer-Encoding: 7bit From: Wes Zuber Date: Tue, 7 Nov 2006 12:30:28 -0800 To: John Baldwin X-Mailer: Apple Mail (2.752.2) Cc: freebsd-drivers@freebsd.org Subject: Re: Dell SC440 and Broadcom 5787 X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Nov 2006 20:31:15 -0000 Hi John, We did run the mem test and it checks out so far. I will try RLENG_6 --Wes On Nov 7, 2006, at 7:03 AM, John Baldwin wrote: > On Monday 06 November 2006 20:30, Wes Zuber wrote: >> If we disable the NIC then everything loads as it should. We have >> several of these boxes from Dell. We tried it on another to make >> sure, but got the same results. >> >> We did not run memitest86 as disabling the NIC seemed to make >> everything work, plus it seemed to crash right after the the NIC >> driver load. This is our first try with an SC440. We have been using >> SC400, SC420 and SC430. > > David, could this be related to the IPMI fixes in 6.2 and HEAD? Wes, > try a kernel from RELENG_6 instead perhaps. > >> Thanks, >> >> --Wes >> >> On Nov 6, 2006, at 5:14 PM, David Christensen wrote: >> >>>> Hi there, >>>> >>>> We are experiencing kernel panics for FreeBSD 6.1 release. cvsup to >>>> the latest. >>>> >>>> I recompiled the kernel with the latest bge drivers but I still get >>>> the same error. >>>> >>>> bge0 >>> mem 0xefcf000-0xefcfffff >>>> irq 17 at device 0.0 on pci4 >>>> >>>> kernel trap 19 with interrupts disabled >>>> >>>> NMI ISA a0 Eisa ff >>>> >>>> Ram Parity error, likely Hardware failure >>>> Fatal trap 19: non-maskeble interrupt trap while in kernel mode >>>> >>>> Instuction pointer = 0x20:oxc0817f10 >>>> stack pointer = 0x28:0xc0c20880 >>>> frame pointer = 0x29:0xc0c208a4 >>>> code segment = base 0x0 >>>> limit 0xfffff, tpe ox1b = dpl 0, pres 1, def 32, granl >>>> processor eflags = IPOL = 0 >>>> current Process = 0 (swapper) >>>> trap number =19 >>>> panic: non-maskeble interrupt trap >>>> uptime 1ms >>> >>> Looks like the OS is reporting a memory parity error. Does the >>> OS run with the LOM disabled? Does the LOM work correctly under >>> another OS? Did you run memtest86+ on the system to verify the >>> memory? >>> >>> Dave >>> >>> >>> >> >> _______________________________________________ >> freebsd-drivers@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-drivers >> To unsubscribe, send any mail to "freebsd-drivers- >> unsubscribe@freebsd.org" >> > > -- > John Baldwin > > From owner-freebsd-drivers@FreeBSD.ORG Wed Nov 8 10:34:32 2006 Return-Path: X-Original-To: freebsd-drivers@freebsd.org Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6117F16A416 for ; Wed, 8 Nov 2006 10:34:32 +0000 (UTC) (envelope-from jackie7691@yahoo.com.mx) Received: from web56014.mail.re3.yahoo.com (web56014.mail.re3.yahoo.com [216.252.110.193]) by mx1.FreeBSD.org (Postfix) with SMTP id 9564443D5D for ; Wed, 8 Nov 2006 10:34:29 +0000 (GMT) (envelope-from jackie7691@yahoo.com.mx) Received: (qmail 24498 invoked by uid 60001); 8 Nov 2006 10:34:29 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com.mx; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=g89MPvcfWm6bkEuoiUSZrzrVfLBEfLgDo/U3hVMEd5EtaEGVII0xSmIKx+eFdGj+e0W48UCE7J+X8jL9GNphgOYxFEK66bIcmxoj85fC/yrje72taq7iJrGwCY89CyEuSu7Unv2n4OfJfc/Ocu6UPX2F2I7nSdbe8YdXx0PDeIU= ; Message-ID: <20061108103429.24496.qmail@web56014.mail.re3.yahoo.com> Received: from [83.64.77.210] by web56014.mail.re3.yahoo.com via HTTP; Wed, 08 Nov 2006 04:34:29 CST Date: Wed, 8 Nov 2006 04:34:29 -0600 (CST) From: Jacqueline P To: Freebsd driverlist MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: PCCARD - interruptible sleep X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Nov 2006 10:34:32 -0000 Hi all how can I implement an interruptible sleep within my pccard smart card reader driver like ? For Linux I do this the following way // interruptible_pause() static inline void ipause(unsigned long amount) { set_current_state(TASK_INTERRUPTIBLE); schedule_timeout(amount); } and within my driver I use the function DELAY which does a busy wait. The problem is, that the driver does not recognize when the pccard is detached during a read / write operation. Does the kernel update the struct device_t, so that the driver can use the function device_is_attached() to determine that the device is detached ? Thanks, Jacqueline --------------------------------- Do You Yahoo!? La mejor conexión a Internet y 2GB extra a tu correo por $100 al mes. http://net.yahoo.com.mx From owner-freebsd-drivers@FreeBSD.ORG Wed Nov 8 13:44:02 2006 Return-Path: X-Original-To: freebsd-drivers@freebsd.org Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E111F16A407 for ; Wed, 8 Nov 2006 13:44:02 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id 47F3643D5F for ; Wed, 8 Nov 2006 13:44:00 +0000 (GMT) (envelope-from asmrookie@gmail.com) Received: by wx-out-0506.google.com with SMTP id i27so1606660wxd for ; Wed, 08 Nov 2006 05:43:59 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=LdDg4+g+RqmifMMacSQZAVAorwdu+HRUkDwBK87132kZpGQ94jz9A8zpZoAldKSgC1ItswYrX+6GaLblLcbyXe+OZ+N2y5bNkOGGLCe0z1qkEJX74w1sbgMGexU6bkJJ6E5npYu/Rt2QepYHfAhxUCjZiwmt8kxDzT4iDwc0JEw= Received: by 10.70.91.11 with SMTP id o11mr9489638wxb.1162993439662; Wed, 08 Nov 2006 05:43:59 -0800 (PST) Received: by 10.70.12.2 with HTTP; Wed, 8 Nov 2006 05:43:59 -0800 (PST) Message-ID: <3bbf2fe10611080543y61511b96nd49f71985e7cf6d1@mail.gmail.com> Date: Wed, 8 Nov 2006 14:43:59 +0100 From: "Attilio Rao" Sender: asmrookie@gmail.com To: "Jacqueline P" , freebsd-drivers@freebsd.org In-Reply-To: <20061108103429.24496.qmail@web56014.mail.re3.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20061108103429.24496.qmail@web56014.mail.re3.yahoo.com> X-Google-Sender-Auth: ae155cad57c2dd32 Cc: Subject: Re: PCCARD - interruptible sleep X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Nov 2006 13:44:03 -0000 2006/11/8, Jacqueline P : > Hi all > > how can I implement an interruptible sleep within my pccard smart card reader driver like ? > For Linux I do this the following way > > // interruptible_pause() > static inline void ipause(unsigned long amount) { > set_current_state(TASK_INTERRUPTIBLE); > schedule_timeout(amount); > } > > and within my driver I use the function DELAY which does a busy wait. > > The problem is, that the driver does not recognize when the pccard is detached during a read / write operation. > > Does the kernel update the struct device_t, so that the driver can use the function device_is_attached() to determine that the device is detached ? You can implement a 'dying' flag in your softc structure (and subsequent macro in order to handle). Attilio -- Peace can only be achieved by understanding - A. Einstein From owner-freebsd-drivers@FreeBSD.ORG Wed Nov 8 17:00:07 2006 Return-Path: X-Original-To: freebsd-drivers@freebsd.org Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9ED9E16A403 for ; Wed, 8 Nov 2006 17:00:07 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 12B9343D45 for ; Wed, 8 Nov 2006 17:00:06 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id kA8Gxvqf091395; Wed, 8 Nov 2006 09:59:57 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Wed, 08 Nov 2006 09:59:57 -0700 (MST) Message-Id: <20061108.095957.41708696.imp@bsdimp.com> To: jackie7691@yahoo.com.mx From: Warner Losh In-Reply-To: <20061108103429.24496.qmail@web56014.mail.re3.yahoo.com> References: <20061108103429.24496.qmail@web56014.mail.re3.yahoo.com> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Wed, 08 Nov 2006 09:59:58 -0700 (MST) Cc: freebsd-drivers@freebsd.org Subject: Re: PCCARD - interruptible sleep X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Nov 2006 17:00:07 -0000 From: Jacqueline P Subject: PCCARD - interruptible sleep Date: Wed, 8 Nov 2006 04:34:29 -0600 (CST) > Hi all > > how can I implement an interruptible sleep within my pccard smart card reader driver like ? > For Linux I do this the following way > > // interruptible_pause() > static inline void ipause(unsigned long amount) { > set_current_state(TASK_INTERRUPTIBLE); > schedule_timeout(amount); > } > > and within my driver I use the function DELAY which does a busy wait. Use msleep instead to do the busy waiting, or limit the amount you spin. Alternatively, you can do these things in a task. > The problem is, that the driver does not recognize when the pccard is detached during a read / write operation. > > Does the kernel update the struct device_t, so that the driver can use the function device_is_attached() to determine that the device is detached ? No, because the device is still attached, even if the hardware is gone. However, you can ask "bus_child_present(your_devt)" and the bridge will determine if the hardware is still there. Warner From owner-freebsd-drivers@FreeBSD.ORG Wed Nov 8 17:03:16 2006 Return-Path: X-Original-To: freebsd-drivers@FreeBSD.org Delivered-To: freebsd-drivers@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9274B16A417; Wed, 8 Nov 2006 17:03:16 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 281E843D55; Wed, 8 Nov 2006 17:03:16 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id kA8H1PRC091431; Wed, 8 Nov 2006 10:01:25 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Wed, 08 Nov 2006 10:01:25 -0700 (MST) Message-Id: <20061108.100125.104107782.imp@bsdimp.com> To: attilio@FreeBSD.org From: Warner Losh In-Reply-To: <3bbf2fe10611080543y61511b96nd49f71985e7cf6d1@mail.gmail.com> References: <20061108103429.24496.qmail@web56014.mail.re3.yahoo.com> <3bbf2fe10611080543y61511b96nd49f71985e7cf6d1@mail.gmail.com> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Wed, 08 Nov 2006 10:01:25 -0700 (MST) Cc: freebsd-drivers@FreeBSD.org, jackie7691@yahoo.com.mx Subject: Re: PCCARD - interruptible sleep X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Nov 2006 17:03:16 -0000 From: "Attilio Rao" Subject: Re: PCCARD - interruptible sleep Date: Wed, 8 Nov 2006 14:43:59 +0100 > 2006/11/8, Jacqueline P : > > Hi all > > > > how can I implement an interruptible sleep within my pccard smart card reader driver like ? > > For Linux I do this the following way > > > > // interruptible_pause() > > static inline void ipause(unsigned long amount) { > > set_current_state(TASK_INTERRUPTIBLE); > > schedule_timeout(amount); > > } > > > > and within my driver I use the function DELAY which does a busy wait. > > > > The problem is, that the driver does not recognize when the pccard is detached during a read / write operation. > > > > Does the kernel update the struct device_t, so that the driver can use the function device_is_attached() to determine that the device is detached ? > > You can implement a 'dying' flag in your softc structure (and > subsequent macro in order to handle). But that won't tell you if the hardware has disappeared. Experience has shown that dying isn't such a good idea in many cases and tends to cause more races than it solves. Warner From owner-freebsd-drivers@FreeBSD.ORG Wed Nov 8 18:04:34 2006 Return-Path: X-Original-To: freebsd-drivers@freebsd.org Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EF3E116A403 for ; Wed, 8 Nov 2006 18:04:34 +0000 (UTC) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 931F643D49 for ; Wed, 8 Nov 2006 18:04:24 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (e67no9x875jmbvad@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.6/8.13.3) with ESMTP id kA8I4Msi040845; Wed, 8 Nov 2006 10:04:23 -0800 (PST) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.6/8.13.3/Submit) id kA8I4MW9040844; Wed, 8 Nov 2006 10:04:22 -0800 (PST) (envelope-from jmg) Date: Wed, 8 Nov 2006 10:04:22 -0800 From: John-Mark Gurney To: Jacqueline P Message-ID: <20061108180422.GA9291@funkthat.com> Mail-Followup-To: Jacqueline P , Freebsd driverlist References: <20061108103429.24496.qmail@web56014.mail.re3.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20061108103429.24496.qmail@web56014.mail.re3.yahoo.com> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: Freebsd driverlist Subject: Re: PCCARD - interruptible sleep X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Nov 2006 18:04:35 -0000 Jacqueline P wrote this message on Wed, Nov 08, 2006 at 04:34 -0600: > how can I implement an interruptible sleep within my pccard smart card reader driver like ? look at tsleep(9) -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-drivers@FreeBSD.ORG Wed Nov 8 19:31:41 2006 Return-Path: X-Original-To: freebsd-drivers@freebsd.org Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4A39316A4C2 for ; Wed, 8 Nov 2006 19:31:41 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.233]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9731743D45 for ; Wed, 8 Nov 2006 19:30:01 +0000 (GMT) (envelope-from asmrookie@gmail.com) Received: by wx-out-0506.google.com with SMTP id i27so1701248wxd for ; Wed, 08 Nov 2006 11:30:01 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=HH+vYCf5JJPwYL6lHqRt0OJvnuNZuuPZy3c4sSFGeWl7v4Y7hjqgtxcTg38PGB29AHOqOOJW7YmUWRUSkURGjW4Ob8tE3qN2U8qxmDVS/PH+rMD+b6faB7ZOXEtg/nlbD/Fw1ggclTyxdd2ZmMtmzXm4nGKpR2aFUeaTdzvGGC4= Received: by 10.70.89.19 with SMTP id m19mr10027852wxb.1163014200809; Wed, 08 Nov 2006 11:30:00 -0800 (PST) Received: by 10.70.12.2 with HTTP; Wed, 8 Nov 2006 11:30:00 -0800 (PST) Message-ID: <3bbf2fe10611081130i1e34ab2end66bf238117cfcf8@mail.gmail.com> Date: Wed, 8 Nov 2006 20:30:00 +0100 From: "Attilio Rao" Sender: asmrookie@gmail.com To: "Warner Losh" In-Reply-To: <20061108.100125.104107782.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20061108103429.24496.qmail@web56014.mail.re3.yahoo.com> <3bbf2fe10611080543y61511b96nd49f71985e7cf6d1@mail.gmail.com> <20061108.100125.104107782.imp@bsdimp.com> X-Google-Sender-Auth: b2a9781cfa31283d Cc: freebsd-drivers@freebsd.org, jackie7691@yahoo.com.mx Subject: Re: PCCARD - interruptible sleep X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Nov 2006 19:31:41 -0000 2006/11/8, Warner Losh : > From: "Attilio Rao" > Subject: Re: PCCARD - interruptible sleep > Date: Wed, 8 Nov 2006 14:43:59 +0100 > > > 2006/11/8, Jacqueline P : > > > Hi all > > > > > > how can I implement an interruptible sleep within my pccard smart card reader driver like ? > > > For Linux I do this the following way > > > > > > // interruptible_pause() > > > static inline void ipause(unsigned long amount) { > > > set_current_state(TASK_INTERRUPTIBLE); > > > schedule_timeout(amount); > > > } > > > > > > and within my driver I use the function DELAY which does a busy wait. > > > > > > The problem is, that the driver does not recognize when the pccard is detached during a read / write operation. > > > > > > Does the kernel update the struct device_t, so that the driver can use the function device_is_attached() to determine that the device is detached ? > > > > You can implement a 'dying' flag in your softc structure (and > > subsequent macro in order to handle). > > But that won't tell you if the hardware has disappeared. Experience > has shown that dying isn't such a good idea in many cases and tends to > cause more races than it solves. Nothing that can't be solved with a softc lock? Give an example please. Attilio -- Peace can only be achieved by understanding - A. Einstein From owner-freebsd-drivers@FreeBSD.ORG Wed Nov 8 23:03:50 2006 Return-Path: X-Original-To: freebsd-drivers@freebsd.org Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E397716A407; Wed, 8 Nov 2006 23:03:50 +0000 (UTC) (envelope-from wes@uia.net) Received: from smtp2.uia.net (smtp2.uia.net [66.146.0.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id B366C43D7B; Wed, 8 Nov 2006 23:03:42 +0000 (GMT) (envelope-from wes@uia.net) Received: from [10.50.0.123] (fw1.uia.net [66.146.1.4]) by smtp2.uia.net (8.13.6/8.11.6/2.1) with ESMTP id kA8N3cuP061500; Wed, 8 Nov 2006 15:03:38 -0800 (PST) In-Reply-To: <200611071003.53651.jhb@freebsd.org> References: <09BFF2FA5EAB4A45B6655E151BBDD90302433A1B@NT-IRVA-0750.brcm.ad.broadcom.com> <1331D139-46F8-49B6-A1DA-57F248F70845@uia.net> <200611071003.53651.jhb@freebsd.org> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <0C337453-25B7-46B2-915D-11572D781881@uia.net> Content-Transfer-Encoding: 7bit From: Wes Zuber Date: Wed, 8 Nov 2006 15:03:33 -0800 To: John Baldwin X-Mailer: Apple Mail (2.752.2) Cc: freebsd-drivers@freebsd.org Subject: Re: Dell SC440 and Broadcom 5787 X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Nov 2006 23:03:51 -0000 Brought it up to RLENG_6 and it crashed again, so same issue apparently. We would be happy to send the 440 to someone if that would help. thanks, --Wes On Nov 7, 2006, at 7:03 AM, John Baldwin wrote: > On Monday 06 November 2006 20:30, Wes Zuber wrote: >> If we disable the NIC then everything loads as it should. We have >> several of these boxes from Dell. We tried it on another to make >> sure, but got the same results. >> >> We did not run memitest86 as disabling the NIC seemed to make >> everything work, plus it seemed to crash right after the the NIC >> driver load. This is our first try with an SC440. We have been using >> SC400, SC420 and SC430. > > David, could this be related to the IPMI fixes in 6.2 and HEAD? Wes, > try a kernel from RELENG_6 instead perhaps. > >> Thanks, >> >> --Wes >> >> On Nov 6, 2006, at 5:14 PM, David Christensen wrote: >> >>>> Hi there, >>>> >>>> We are experiencing kernel panics for FreeBSD 6.1 release. cvsup to >>>> the latest. >>>> >>>> I recompiled the kernel with the latest bge drivers but I still get >>>> the same error. >>>> >>>> bge0 >>> mem 0xefcf000-0xefcfffff >>>> irq 17 at device 0.0 on pci4 >>>> >>>> kernel trap 19 with interrupts disabled >>>> >>>> NMI ISA a0 Eisa ff >>>> >>>> Ram Parity error, likely Hardware failure >>>> Fatal trap 19: non-maskeble interrupt trap while in kernel mode >>>> >>>> Instuction pointer = 0x20:oxc0817f10 >>>> stack pointer = 0x28:0xc0c20880 >>>> frame pointer = 0x29:0xc0c208a4 >>>> code segment = base 0x0 >>>> limit 0xfffff, tpe ox1b = dpl 0, pres 1, def 32, granl >>>> processor eflags = IPOL = 0 >>>> current Process = 0 (swapper) >>>> trap number =19 >>>> panic: non-maskeble interrupt trap >>>> uptime 1ms >>> >>> Looks like the OS is reporting a memory parity error. Does the >>> OS run with the LOM disabled? Does the LOM work correctly under >>> another OS? Did you run memtest86+ on the system to verify the >>> memory? >>> >>> Dave >>> >>> >>> >> >> _______________________________________________ >> freebsd-drivers@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-drivers >> To unsubscribe, send any mail to "freebsd-drivers- >> unsubscribe@freebsd.org" >> > > -- > John Baldwin > > From owner-freebsd-drivers@FreeBSD.ORG Thu Nov 9 14:09:10 2006 Return-Path: X-Original-To: freebsd-drivers@freebsd.org Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BD03A16A494; Thu, 9 Nov 2006 14:09:10 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id CCBDA43D49; Thu, 9 Nov 2006 14:09:09 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id kA9E7Z9P010683; Thu, 9 Nov 2006 07:07:35 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Thu, 09 Nov 2006 07:08:08 -0700 (MST) Message-Id: <20061109.070808.-1975970075.imp@bsdimp.com> To: attilio@freebsd.org From: "M. Warner Losh" In-Reply-To: <3bbf2fe10611081130i1e34ab2end66bf238117cfcf8@mail.gmail.com> References: <3bbf2fe10611080543y61511b96nd49f71985e7cf6d1@mail.gmail.com> <20061108.100125.104107782.imp@bsdimp.com> <3bbf2fe10611081130i1e34ab2end66bf238117cfcf8@mail.gmail.com> X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Thu, 09 Nov 2006 07:07:35 -0700 (MST) Cc: freebsd-drivers@freebsd.org, jackie7691@yahoo.com.mx Subject: Re: PCCARD - interruptible sleep X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Nov 2006 14:09:10 -0000 In message: <3bbf2fe10611081130i1e34ab2end66bf238117cfcf8@mail.gmail.com> "Attilio Rao" writes: : 2006/11/8, Warner Losh : : > From: "Attilio Rao" : > Subject: Re: PCCARD - interruptible sleep : > Date: Wed, 8 Nov 2006 14:43:59 +0100 : > : > > 2006/11/8, Jacqueline P : : > > > Hi all : > > > : > > > how can I implement an interruptible sleep within my pccard smart card reader driver like ? : > > > For Linux I do this the following way : > > > : > > > // interruptible_pause() : > > > static inline void ipause(unsigned long amount) { : > > > set_current_state(TASK_INTERRUPTIBLE); : > > > schedule_timeout(amount); : > > > } : > > > : > > > and within my driver I use the function DELAY which does a busy wait. : > > > : > > > The problem is, that the driver does not recognize when the pccard is detached during a read / write operation. : > > > : > > > Does the kernel update the struct device_t, so that the driver can use the function device_is_attached() to determine that the device is detached ? : > > : > > You can implement a 'dying' flag in your softc structure (and : > > subsequent macro in order to handle). : > : > But that won't tell you if the hardware has disappeared. Experience : > has shown that dying isn't such a good idea in many cases and tends to : > cause more races than it solves. : : Nothing that can't be solved with a softc lock? : Give an example please. You are in your ISR with a loop: while(sr() & INTR) do_interrupt(); if the card is ejected, then sr (the status register) will go all ones. This will loop forever. Since the interrupt for the card management and for the card isr are shared, so the management interrupt will be blocked until the ISR returns. So the detach() routine never runs, and you never set the 'dying' flag. There are many other examples. The real solution is to check to make sure the hardware is still present by asking the bridge from time to time and limiting what you do. A dying flag can be useful in some cases, but it is naive to think it solves all the problems. In the past it was used as such when in fact the drivers that used it were full of detach races... Warner From owner-freebsd-drivers@FreeBSD.ORG Fri Nov 10 01:30:32 2006 Return-Path: X-Original-To: freebsd-drivers@freebsd.org Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 20EA016A4A7; Fri, 10 Nov 2006 01:30:32 +0000 (UTC) (envelope-from wes@uia.net) Received: from smtp2.uia.net (smtp2.uia.net [66.146.0.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id E8C5343D53; Fri, 10 Nov 2006 01:30:28 +0000 (GMT) (envelope-from wes@uia.net) Received: from [10.50.0.123] (fw1.uia.net [66.146.1.4]) by smtp2.uia.net (8.13.6/8.11.6/2.1) with ESMTP id kAA1UOAA041482; Thu, 9 Nov 2006 17:30:28 -0800 (PST) In-Reply-To: <5BE0205D-0ED0-45A7-B2E0-C1335769E92C@uia.net> References: <09BFF2FA5EAB4A45B6655E151BBDD90302433A1B@NT-IRVA-0750.brcm.ad.broadcom.com> <1331D139-46F8-49B6-A1DA-57F248F70845@uia.net> <200611071003.53651.jhb@freebsd.org> <5BE0205D-0ED0-45A7-B2E0-C1335769E92C@uia.net> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <45237F52-0EAE-4B83-B012-87E9A3F838BB@uia.net> Content-Transfer-Encoding: 7bit From: Wes Zuber Date: Thu, 9 Nov 2006 17:30:23 -0800 To: John Baldwin X-Mailer: Apple Mail (2.752.2) Cc: freebsd-drivers@freebsd.org Subject: Re: Dell SC440 and Broadcom 5787 X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Nov 2006 01:30:32 -0000 Is there anything else I can try? Thanks, --Wes On Nov 7, 2006, at 12:30 PM, Wes Zuber wrote: > Hi John, > > We did run the mem test and it checks out so far. > > I will try RLENG_6 > > --Wes > > On Nov 7, 2006, at 7:03 AM, John Baldwin wrote: > >> On Monday 06 November 2006 20:30, Wes Zuber wrote: >>> If we disable the NIC then everything loads as it should. We have >>> several of these boxes from Dell. We tried it on another to make >>> sure, but got the same results. >>> >>> We did not run memitest86 as disabling the NIC seemed to make >>> everything work, plus it seemed to crash right after the the NIC >>> driver load. This is our first try with an SC440. We have been using >>> SC400, SC420 and SC430. >> >> David, could this be related to the IPMI fixes in 6.2 and HEAD? Wes, >> try a kernel from RELENG_6 instead perhaps. >> >>> Thanks, >>> >>> --Wes >>> >>> On Nov 6, 2006, at 5:14 PM, David Christensen wrote: >>> >>>>> Hi there, >>>>> >>>>> We are experiencing kernel panics for FreeBSD 6.1 release. >>>>> cvsup to >>>>> the latest. >>>>> >>>>> I recompiled the kernel with the latest bge drivers but I still >>>>> get >>>>> the same error. >>>>> >>>>> bge0 >>>> mem 0xefcf000-0xefcfffff >>>>> irq 17 at device 0.0 on pci4 >>>>> >>>>> kernel trap 19 with interrupts disabled >>>>> >>>>> NMI ISA a0 Eisa ff >>>>> >>>>> Ram Parity error, likely Hardware failure >>>>> Fatal trap 19: non-maskeble interrupt trap while in kernel mode >>>>> >>>>> Instuction pointer = 0x20:oxc0817f10 >>>>> stack pointer = 0x28:0xc0c20880 >>>>> frame pointer = 0x29:0xc0c208a4 >>>>> code segment = base 0x0 >>>>> limit 0xfffff, tpe ox1b = dpl 0, pres 1, def 32, granl >>>>> processor eflags = IPOL = 0 >>>>> current Process = 0 (swapper) >>>>> trap number =19 >>>>> panic: non-maskeble interrupt trap >>>>> uptime 1ms >>>> >>>> Looks like the OS is reporting a memory parity error. Does the >>>> OS run with the LOM disabled? Does the LOM work correctly under >>>> another OS? Did you run memtest86+ on the system to verify the >>>> memory? >>>> >>>> Dave >>>> >>>> >>>> >>> >>> _______________________________________________ >>> freebsd-drivers@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-drivers >>> To unsubscribe, send any mail to "freebsd-drivers- >>> unsubscribe@freebsd.org" >>> >> >> -- >> John Baldwin >> >> > > _______________________________________________ > freebsd-drivers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-drivers > To unsubscribe, send any mail to "freebsd-drivers- > unsubscribe@freebsd.org" > >