From owner-freebsd-scsi@FreeBSD.ORG Mon Mar 27 11:03:07 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D13A916A420 for ; Mon, 27 Mar 2006 11:03:07 +0000 (UTC) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 99A9743D45 for ; Mon, 27 Mar 2006 11:03:07 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k2RB375g062369 for ; Mon, 27 Mar 2006 11:03:07 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k2RB36fH062363 for freebsd-scsi@freebsd.org; Mon, 27 Mar 2006 11:03:06 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 27 Mar 2006 11:03:06 GMT Message-Id: <200603271103.k2RB36fH062363@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-scsi@FreeBSD.org Cc: Subject: Current problem reports assigned to you X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Mar 2006 11:03:07 -0000 Current FreeBSD problem reports Critical problems Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2001/05/03] kern/27059 scsi [sym] SCSI subsystem hangs under heavy lo o [2001/06/29] kern/28508 scsi problems with backup to Tandberg SLR40 st o [2002/06/17] kern/39388 scsi ncr/sym drivers fail with 53c810 and more o [2002/07/22] kern/40895 scsi wierd kernel / device driver bug o [2003/05/24] kern/52638 scsi [panic] SCSI U320 on SMP server won't run s [2003/09/30] kern/57398 scsi [mly] Current fails to install on mly(4) o [2003/12/26] kern/60598 scsi wire down of scsi devices conflicts with o [2003/12/27] kern/60641 scsi [sym] Sporadic SCSI bus resets with 53C81 s [2004/01/10] kern/61165 scsi [panic] kernel page fault after calling c o [2004/12/02] kern/74627 scsi [ahc] [hang] Adaptec 2940U2W Can't boot 5 o [2005/06/04] kern/81887 scsi [aac] Adaptec SCSI 2130S aac0: GetDeviceP o [2005/12/12] kern/90282 scsi [sym] SCSI bus resets cause loss of ch de o [2006/02/04] kern/92798 scsi [ahc] SCSI problem with timeouts o [2006/02/10] kern/93128 scsi [sym] FreeBSD 6.1 BETA 1 has problems wit o [2006/03/22] kern/94838 scsi Kernel panic while mounting SD card with 15 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2000/12/06] kern/23314 scsi aic driver fails to detect Adaptec 1520B o [2002/02/23] kern/35234 scsi World access to /dev/pass? (for scanner) o [2002/06/02] kern/38828 scsi [feature request] DPT PM2012B/90 doesn't o [2002/10/29] kern/44587 scsi dev/dpt/dpt.h is missing defines required o [2005/01/12] kern/76178 scsi [ahd] Problem with ahd and large SCSI Rai 5 problems total. From owner-freebsd-scsi@FreeBSD.ORG Mon Mar 27 20:10:34 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6355016A422; Mon, 27 Mar 2006 20:10:34 +0000 (UTC) (envelope-from os@rsu.ru) Received: from mail.r61.net (mail.r61.net [195.208.245.235]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E1E543D62; Mon, 27 Mar 2006 20:10:32 +0000 (GMT) (envelope-from os@rsu.ru) Received: from wolf.os.rsu.ru (os@os.adsl.r61.net [195.208.243.95]) (authenticated bits=0) by mail.r61.net (8.13.4/8.13.4) with ESMTP id k2RKAJcB077460 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 28 Mar 2006 00:10:22 +0400 (MSD) (envelope-from os@rsu.ru) Date: Tue, 28 Mar 2006 00:10:21 +0400 (MSD) From: Oleg Sharoiko To: John Baldwin In-Reply-To: <200603241718.49362.jhb@freebsd.org> Message-ID: <20060327234908.K831@wolf.os.rsu.ru> References: <20060215102749.D58480@brain.cc.rsu.ru> <200603241607.55075.jhb@freebsd.org> <20060325003610.J11600@brain.cc.rsu.ru> <200603241718.49362.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: ClamAV version 0.86.2, clamav-milter version 0.86 on asterix.r61.net X-Virus-Status: Clean Cc: freebsd-scsi@freebsd.org, Andrey Beresovsky Subject: Re: Boot hangs on ips0: resetting adapter, this may take up to 5 minutes X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Mar 2006 20:10:34 -0000 On Fri, 24 Mar 2006, John Baldwin wrote: JB>> I've found an interesting thread on netbsd mailing list. JB>> http://mail-index.netbsd.org/port-amd64/2006/03/ JB>> With subject "Re: Bug in x86 ioapic interrupt code for devices with shared JB>> interrupts?". May this relate to my problems? JB>Well, there is one possibly interesting patch for bge in there, (the JB>one from the linux driver) but I'm not sure if it would really help or JB>not. John, can it be possible that interrupts are incorrectly delivered to bge_intr? Is it possible that these interrupts are generated by some different device? I've added simple debug out to the bge_intr. This is from the normal interrupts: statusword: 0001 bge0: BGE_PCI_PCISTATE: 1210 And this is from interrupt storm: bge0: statusword: 0000 bge0: BGE_PCI_PCISTATE: 1212 According to linux driver bit 0x02 (called PCISTATE_INT_NOT_ACTIVE) of BGE_PCI_PCISTATE register means that device is not generating interrups. Here is an extract from linux driver (distributed by broadcom - manufacturer of bge cards): /* In INTx mode, it is possible for the interrupt to arrive at * the CPU before the status block posted prior to the interrupt. * Reading the PCI State register will confirm whether the * interrupt is ours and will flush the status block. */ if ((sblk->status & SD_STATUS_UPDATED) || !(tr32(TG3PCI_PCISTATE) & PCISTATE_INT_NOT_ACTIVE)) { ... } else { /* shared interrupt */ handled = 0; } out: return IRQ_RETVAL(handled); As I understand in Linux when driver interrupt routine returns 0 it means that this interrupt was not for this driver and kernel should handle this case. I don't know how to implement this in FreeBSD. -- Oleg Sharoiko. Software and Network Engineer Computer Center of Rostov State University. From owner-freebsd-scsi@FreeBSD.ORG Mon Mar 27 20:20:30 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 77FB516A401; Mon, 27 Mar 2006 20:20:30 +0000 (UTC) (envelope-from os@rsu.ru) Received: from mail.r61.net (mail.r61.net [195.208.245.235]) by mx1.FreeBSD.org (Postfix) with ESMTP id 95F8943D45; Mon, 27 Mar 2006 20:20:29 +0000 (GMT) (envelope-from os@rsu.ru) Received: from wolf.os.rsu.ru (os@os.adsl.r61.net [195.208.243.95]) (authenticated bits=0) by mail.r61.net (8.13.4/8.13.4) with ESMTP id k2RKKQQI078900 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 28 Mar 2006 00:20:27 +0400 (MSD) (envelope-from os@rsu.ru) Date: Tue, 28 Mar 2006 00:20:27 +0400 (MSD) From: Oleg Sharoiko To: John Baldwin In-Reply-To: <20060327234908.K831@wolf.os.rsu.ru> Message-ID: <20060328001603.B831@wolf.os.rsu.ru> References: <20060215102749.D58480@brain.cc.rsu.ru> <200603241607.55075.jhb@freebsd.org> <20060325003610.J11600@brain.cc.rsu.ru> <200603241718.49362.jhb@freebsd.org> <20060327234908.K831@wolf.os.rsu.ru> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: ClamAV version 0.86.2, clamav-milter version 0.86 on asterix.r61.net X-Virus-Status: Clean Cc: freebsd-scsi@freebsd.org, Andrey Beresovsky Subject: Re: Boot hangs on ips0: resetting adapter, this may take up to 5 minutes X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Mar 2006 20:20:30 -0000 On Tue, 28 Mar 2006, Oleg Sharoiko wrote: OS>According to linux driver bit 0x02 (called PCISTATE_INT_NOT_ACTIVE) of OS>BGE_PCI_PCISTATE register means that device is not generating interrups. And one more thing I've noted: this interrupt storms only happen when I install additional PCI-X device into expansion slot. And this device doesn't necessary has to have a driver in the kernel. -- Oleg Sharoiko. Software and Network Engineer Computer Center of Rostov State University. From owner-freebsd-scsi@FreeBSD.ORG Mon Mar 27 21:08:15 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3081516A423 for ; Mon, 27 Mar 2006 21:08:15 +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 E878043D72 for ; Mon, 27 Mar 2006 21:08:07 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k2RL83jf063796; Mon, 27 Mar 2006 16:08:03 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: Oleg Sharoiko Date: Mon, 27 Mar 2006 16:07:07 -0500 User-Agent: KMail/1.9.1 References: <20060215102749.D58480@brain.cc.rsu.ru> <200603241718.49362.jhb@freebsd.org> <20060327234908.K831@wolf.os.rsu.ru> In-Reply-To: <20060327234908.K831@wolf.os.rsu.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200603271607.09550.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1358/Mon Mar 27 11:12:27 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-3.8 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: freebsd-scsi@freebsd.org, Andrey Beresovsky Subject: Re: Boot hangs on ips0: resetting adapter, this may take up to 5 minutes X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Mar 2006 21:08:15 -0000 On Monday 27 March 2006 15:10, Oleg Sharoiko wrote: > > On Fri, 24 Mar 2006, John Baldwin wrote: > > JB>> I've found an interesting thread on netbsd mailing list. > JB>> http://mail-index.netbsd.org/port-amd64/2006/03/ > JB>> With subject "Re: Bug in x86 ioapic interrupt code for devices with shared > JB>> interrupts?". May this relate to my problems? > JB>Well, there is one possibly interesting patch for bge in there, (the > JB>one from the linux driver) but I'm not sure if it would really help or > JB>not. > > John, can it be possible that interrupts are incorrectly delivered to > bge_intr? Is it possible that these interrupts are generated by some > different device? Yes, if the interrupt for another device is mis-routed. That is, if another device is really sharing the IRQ with bge0, but we think it is using some other interrupt pin (because that's what the BIOS _told us_) then this would happen. I misspoke earlier because I thought kldloading bge brought on the storm rather than a disk access once bge was loaded. Which device is not getting interrupts and hanging? You said all your SCSI cards work fine with bge0 (IRQ16) is not in the kernel, yes? What if you disable just the devices on IRQ16 (bge and usb) do all of your various SCSI cards work fine in that case? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-scsi@FreeBSD.ORG Tue Mar 28 15:45:35 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BE46316A401; Tue, 28 Mar 2006 15:45:35 +0000 (UTC) (envelope-from os@rsu.ru) Received: from mail.r61.net (mail.r61.net [195.208.245.235]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2AB4643D45; Tue, 28 Mar 2006 15:45:34 +0000 (GMT) (envelope-from os@rsu.ru) Received: from brain.cc.rsu.ru (brain.cc.rsu.ru [195.208.252.154]) (authenticated bits=0) by mail.r61.net (8.13.4/8.13.4) with ESMTP id k2SFjTQM002736 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 28 Mar 2006 19:45:29 +0400 (MSD) (envelope-from os@rsu.ru) Date: Tue, 28 Mar 2006 19:45:29 +0400 (MSD) From: Oleg Sharoiko To: John Baldwin In-Reply-To: <200603271607.09550.jhb@freebsd.org> Message-ID: <20060328185449.F763@brain.cc.rsu.ru> References: <20060215102749.D58480@brain.cc.rsu.ru> <200603241718.49362.jhb@freebsd.org> <20060327234908.K831@wolf.os.rsu.ru> <200603271607.09550.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: ClamAV version 0.86.2, clamav-milter version 0.86 on asterix.r61.net X-Virus-Status: Clean Cc: freebsd-scsi@freebsd.org, Andrey Beresovsky Subject: Re: Boot hangs on ips0: resetting adapter, this may take up to 5 minutes X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Mar 2006 15:45:35 -0000 On Mon, 27 Mar 2006, John Baldwin wrote: JB>Which device is not getting interrupts and hanging? You said all your JB>SCSI cards work fine with bge0 (IRQ16) is not in the kernel, yes? What JB>if you disable just the devices on IRQ16 (bge and usb) do all of your JB>various SCSI cards work fine in that case? Yes, as soon as I remove bge from kernel all other devices work fine. I couldn't figure out which particular device is mis-routed, because when interrupt storm happens the system becomes unresponsive and it's impossible to tell which devices work and which not. I tried to track this with KTR, but I only made a trace for good case. When I enabled KTR for interrupt storm case the behaviour changed and I only get repeated clock interrupts - no storm on bge. And interrupt storm only happens on single CPU when PREEMPTION is in effect. Without PREEMPTION kernel with bge works. With SMP kernel I can kldload if_bge when 2nd CPU has been already initialized, though I haven't run many tests and this last setup is probably unstable. By the way, shouldn't ithread_execute_handlers detect interrupt storm condition? As I can see it has corresponding code, but in my case storm is not detected. BIOS has a page "PCI interrupt routing" which currently contains: Planar USB IRQ [Auto Configure] Current Interrupt Assigned 10 SCSI INTA IRQ [Auto Configure] Current Interrupt Assigned 11 SCSI INTB IRQ [Auto Configure] Current Interrupt Assigned 10 Planar Video IRQ [Auto Configure] Current Interrupt Assigned 11 Planar Ethernet IRQ [Auto Configure] Current Interrupt Assigned 11 Slot1 INTA IRQ [No IRQ reqested] Current Interrupt Assigned No IRQ reqested Slot2 INTA IRQ [No IRQ reqested] Current Interrupt Assigned No IRQ reqested Slot3 INTA IRQ [No IRQ reqested] Current Interrupt Assigned No IRQ reqested Slot4 INTA IRQ [Auto Configure] Current Interrupt Assigned 11 Slot5 INTA IRQ [No IRQ reqested] Current Interrupt Assigned No IRQ reqested Slot6 INTA IRQ [No IRQ reqested] Current Interrupt Assigned No IRQ reqested In this menu SLOT4 INTA is linked with Ethernet and they change together whenever I alter one of them. I suppose, this values correspond to 'irq=' from dmesg output: found-> vendor=0x14e4, dev=0x1659, revid=0x11 bus=1, slot=0, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0146, statreg=0x0010, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 powerspec 2 supports D0 D3 current D0 MSI supports 8 messages, 64 bit map[10]: type 1, range 64, base d0100000, size 16, enabled pcib1: (null) requested memory range 0xd0100000-0xd010ffff: good Dut I don't understand the next lines pcib0: matched entry for 0.2.INTA pcib0: slot 2 INTA hardwired to IRQ 16 pcib1: slot 0 INTA is routed to irq 16 What does 'hardwired' mean and why irq number is different. I'm probably asking dumb questions, that's because I only know for sure two things about interrupts: there 4 interrupt lines on PCI bus (A-D) which devices use to trigger interrupts and there are interrupt handlers. How signals from these lines are delivered to proper handlers, what is the role of APICs and how these things work together - all this is covered by darkness for me. -- Oleg Sharoiko. Software and Network Engineer Computer Center of Rostov State University. From owner-freebsd-scsi@FreeBSD.ORG Tue Mar 28 16:08:37 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CA8DD16A41F for ; Tue, 28 Mar 2006 16:08:37 +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 BC6D643DFA for ; Tue, 28 Mar 2006 16:07:40 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k2SG7Yk2070474; Tue, 28 Mar 2006 11:07:34 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: Oleg Sharoiko Date: Tue, 28 Mar 2006 11:08:23 -0500 User-Agent: KMail/1.9.1 References: <20060215102749.D58480@brain.cc.rsu.ru> <200603271607.09550.jhb@freebsd.org> <20060328185449.F763@brain.cc.rsu.ru> In-Reply-To: <20060328185449.F763@brain.cc.rsu.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200603281108.25548.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1359/Tue Mar 28 06:49:08 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-3.8 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: freebsd-scsi@freebsd.org, Andrey Beresovsky Subject: Re: Boot hangs on ips0: resetting adapter, this may take up to 5 minutes X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Mar 2006 16:08:37 -0000 On Tuesday 28 March 2006 10:45, Oleg Sharoiko wrote: > > On Mon, 27 Mar 2006, John Baldwin wrote: > > JB>Which device is not getting interrupts and hanging? You said all your > JB>SCSI cards work fine with bge0 (IRQ16) is not in the kernel, yes? What > JB>if you disable just the devices on IRQ16 (bge and usb) do all of your > JB>various SCSI cards work fine in that case? > > Yes, as soon as I remove bge from kernel all other devices work fine. I > couldn't figure out which particular device is mis-routed, because when > interrupt storm happens the system becomes unresponsive and it's > impossible to tell which devices work and which not. Is this an Intel box? > And interrupt storm only happens on single CPU when PREEMPTION is in > effect. Without PREEMPTION kernel with bge works. With SMP kernel I can > kldload if_bge when 2nd CPU has been already initialized, though I haven't > run many tests and this last setup is probably unstable. > > By the way, shouldn't ithread_execute_handlers detect interrupt storm > condition? As I can see it has corresponding code, but in my case storm is > not detected. It only detects it if the interrupt line is constantly on. If the interrupt line goes off for a little bit and then back on often enough the istorm logic won't kick in. You can try lowering the threshold via the tunable to see if you can get it to kick in perhaps. > BIOS has a page "PCI interrupt routing" which currently contains: > > Planar USB IRQ [Auto Configure] > Current Interrupt Assigned 10 > SCSI INTA IRQ [Auto Configure] > Current Interrupt Assigned 11 > SCSI INTB IRQ [Auto Configure] > Current Interrupt Assigned 10 > Planar Video IRQ [Auto Configure] > Current Interrupt Assigned 11 > Planar Ethernet IRQ [Auto Configure] > Current Interrupt Assigned 11 > Slot1 INTA IRQ [No IRQ reqested] > Current Interrupt Assigned No IRQ reqested > Slot2 INTA IRQ [No IRQ reqested] > Current Interrupt Assigned No IRQ reqested > Slot3 INTA IRQ [No IRQ reqested] > Current Interrupt Assigned No IRQ reqested > Slot4 INTA IRQ [Auto Configure] > Current Interrupt Assigned 11 > Slot5 INTA IRQ [No IRQ reqested] > Current Interrupt Assigned No IRQ reqested > Slot6 INTA IRQ [No IRQ reqested] > Current Interrupt Assigned No IRQ reqested > > In this menu SLOT4 INTA is linked with Ethernet and they change together > whenever I alter one of them. > > I suppose, this values correspond to 'irq=' from dmesg output: > > found-> vendor=0x14e4, dev=0x1659, revid=0x11 > bus=1, slot=0, func=0 > class=02-00-00, hdrtype=0x00, mfdev=0 > cmdreg=0x0146, statreg=0x0010, cachelnsz=8 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > intpin=a, irq=11 > powerspec 2 supports D0 D3 current D0 > MSI supports 8 messages, 64 bit > map[10]: type 1, range 64, base d0100000, size 16, enabled > pcib1: (null) requested memory range 0xd0100000-0xd010ffff: good > > Dut I don't understand the next lines > > pcib0: matched entry for 0.2.INTA > pcib0: slot 2 INTA hardwired to IRQ 16 > pcib1: slot 0 INTA is routed to irq 16 > > What does 'hardwired' mean and why irq number is different. Because on x86 there are two completely different sets of interrupt controllers. The AT-compatible 8259A pair of PICs provides ISA IRQs 0-15, and when using the 8259As, PCI interrupts are routed to a PCI interrupt router that forwards the PCI interrupts onto the ISA IRQs. The second set of interrupt contollers are called APICs. A system can have 1 or more I/O APICs, each of which can have anywhere from 16 to 32 individual interrupt pins (usually 16, 24, or 32). Each PCI interrupt usually gets its own private interrupt pin that it doesn't have to share with any other interrupts, and any ISA interrupts are routed to pins 0-15 on the first I/O APIC. The OS is required to use APICs in SMP mode for several reasons (you have to use APICs to do IPIs for example). The messages above show that your device's interrupt line is connected to pin 16 on the first I/O APIC (thus, IRQ 16). -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-scsi@FreeBSD.ORG Tue Mar 28 16:37:18 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8979C16A401; Tue, 28 Mar 2006 16:37:18 +0000 (UTC) (envelope-from os@rsu.ru) Received: from mail.r61.net (mail.r61.net [195.208.245.235]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9AC4E44ADC; Tue, 28 Mar 2006 16:37:17 +0000 (GMT) (envelope-from os@rsu.ru) Received: from brain.cc.rsu.ru (brain.cc.rsu.ru [195.208.252.154]) (authenticated bits=0) by mail.r61.net (8.13.4/8.13.4) with ESMTP id k2SGbEf3007334 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 28 Mar 2006 20:37:15 +0400 (MSD) (envelope-from os@rsu.ru) Date: Tue, 28 Mar 2006 20:37:14 +0400 (MSD) From: Oleg Sharoiko To: John Baldwin In-Reply-To: <200603281108.25548.jhb@freebsd.org> Message-ID: <20060328201134.S763@brain.cc.rsu.ru> References: <20060215102749.D58480@brain.cc.rsu.ru> <200603271607.09550.jhb@freebsd.org> <20060328185449.F763@brain.cc.rsu.ru> <200603281108.25548.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: ClamAV version 0.86.2, clamav-milter version 0.86 on asterix.r61.net X-Virus-Status: Clean Cc: freebsd-scsi@freebsd.org, Andrey Beresovsky Subject: Re: Boot hangs on ips0: resetting adapter, this may take up to 5 minutes X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Mar 2006 16:37:18 -0000 On Tue, 28 Mar 2006, John Baldwin wrote: JB>Is this an Intel box? This is IBM xSeries 226. Motherboard is labeled 'MS 9151 Ver.1'. It appears to be MSI E7525 Master-S2 or a modification of it. I couldn't find information about it in the net. Just few short notes and nothing else. I suppose it's based on Intel's E7525 chipset. JB>It only detects it if the interrupt line is constantly on. If the interrupt JB>line goes off for a little bit and then back on often enough the istorm logic JB>won't kick in. You can try lowering the threshold via the tunable to see if JB>you can get it to kick in perhaps. No luck here. -- Oleg Sharoiko. Software and Network Engineer Computer Center of Rostov State University. From owner-freebsd-scsi@FreeBSD.ORG Wed Mar 29 13:49:51 2006 Return-Path: X-Original-To: freebsd-scsi@FreeBSD.ORG Delivered-To: freebsd-scsi@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E1A2C16A4AC for ; Wed, 29 Mar 2006 13:49:51 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A40C43D45 for ; Wed, 29 Mar 2006 13:49:50 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (fgjajc@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k2TDnhw5006002 for ; Wed, 29 Mar 2006 15:49:49 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k2TDnhZ0006001; Wed, 29 Mar 2006 15:49:43 +0200 (CEST) (envelope-from olli) Date: Wed, 29 Mar 2006 15:49:43 +0200 (CEST) Message-Id: <200603291349.k2TDnhZ0006001@lurza.secnetix.de> From: Oliver Fromme To: freebsd-scsi@FreeBSD.ORG X-Newsgroups: list.freebsd-scsi User-Agent: tin/1.8.0-20051224 ("Ronay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Wed, 29 Mar 2006 15:49:49 +0200 (CEST) Cc: Subject: Temperature sensor on SCSI disks (IBM / Hitachi) X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-scsi@FreeBSD.ORG List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Mar 2006 13:49:52 -0000 Hi, I have the following SCSI disks in a server: at scbus0 target 0 lun 0 (pass0,da0) at scbus0 target 1 lun 0 (pass1,da1) Searching the mailing lists revealed that IBM SCSI disks (Hitachi nowadays) have a temperature sensor that can be queried with a special (prioprietary) command like this: camcontrol cmd -n da -u 0 -c "4D 0 76 0 0 0 0 0 20 0" -i 32 "s9 i1" However, I get: "camcontrol: error sending command". Any advice? (I'm using 4-stable, BTW.) Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. cat man du : where Unix geeks go when they die From owner-freebsd-scsi@FreeBSD.ORG Wed Mar 29 14:57:42 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A7DC616A401 for ; Wed, 29 Mar 2006 14:57:42 +0000 (UTC) (envelope-from rob@hudson-trading.com) Received: from ms-smtp-02.rdc-nyc.rr.com (ms-smtp-02-smtplb.rdc-nyc.rr.com [24.29.109.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B06A43D5F for ; Wed, 29 Mar 2006 14:57:38 +0000 (GMT) (envelope-from rob@hudson-trading.com) Received: from cpe-72-225-255-159.nyc.res.rr.com (cpe-72-225-255-159.nyc.res.rr.com [72.225.255.159]) by ms-smtp-02.rdc-nyc.rr.com (8.13.4/8.13.4) with ESMTP id k2TEntb8004273; Wed, 29 Mar 2006 09:49:56 -0500 (EST) Date: Wed, 29 Mar 2006 09:57:36 -0500 (EST) From: Rob Watt X-X-Sender: rob@daemon.mistermishap.net To: freebsd-scsi@freebsd.org In-Reply-To: <713A93E978A4D7E09863191F@[10.0.0.90]> Message-ID: <20060329095115.V4048@daemon.mistermishap.net> References: <20060308093407.H20947@daemon.mistermishap.net> <713A93E978A4D7E09863191F@[10.0.0.90]> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: Symantec AntiVirus Scan Engine Cc: Rob Watt Subject: Re: SCB timeout and other errors + system hang with adaptec/seagate X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Mar 2006 14:57:42 -0000 So, These error are still cropping up on some of my machines. After upgrading the drive firmware and disabling SMART, some of my machines are stable (and no longer generate the SCB timeout error). I am still having problems on a few of the machines though, and I have a new piece of data. It seems that when they hang they are generating 'swap_pager: indefinite wait buffer: device ...' messages. I noticed that fixing swap_pager warnings are on the to-do list for 6.1 release. I have not seen any bug reports that give more detail on what exactly the problem is. Does anyone have any more info on this? Is there an experimental patch I can try? I suspect that the swap_pager problem is not the _only_ problem, but it might be what is causing the remaining machines to hang. Thanks. - Rob Watt On Wed, 8 Mar 2006, Justin T. Gibbs wrote: > The termination looks correct. I'll review your other logs > to see why we're failing during recovery. > > -- > Justin > > --On Wednesday, March 08, 2006 9:35 AM -0500 Rob Watt > wrote: > >> ---------- Forwarded message ---------- >> Date: Tue, 7 Mar 2006 10:06:53 -0500 (EST) >> From: Rob Watt >> To: Justin T. Gibbs >> Cc: Rob Watt >> Subject: Re: SCB timeout and other errors + system hang with >> adaptec/seagate >> >> On Mon, 6 Mar 2006, Justin T. Gibbs wrote: >> >>> Can you send me a dmesg from a boot -v? Perhaps we're not >>> getting the termination settings correct on the SCSI controller. >>> The verbose dmesg should tell. >> >> attached is the verbose dmesg. >> >> thanks >> >> - >> Rob Watt > > > > > From owner-freebsd-scsi@FreeBSD.ORG Wed Mar 29 15:15:20 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DBE2316A401 for ; Wed, 29 Mar 2006 15:15:20 +0000 (UTC) (envelope-from asstec@matik.com.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7010143D5E for ; Wed, 29 Mar 2006 15:15:00 +0000 (GMT) (envelope-from asstec@matik.com.br) Received: from anb (anb.matik.com.br [200.152.83.34]) by msrv.matik.com.br (8.13.4/8.13.1) with ESMTP id k2TFEvAV067127; Wed, 29 Mar 2006 12:14:58 -0300 (BRT) (envelope-from asstec@matik.com.br) From: AT Matik Organization: Infomatik To: freebsd-scsi@freebsd.org Date: Wed, 29 Mar 2006 12:14:56 -0300 User-Agent: KMail/1.9.1 References: <20060308093407.H20947@daemon.mistermishap.net> <713A93E978A4D7E09863191F@[10.0.0.90]> <20060329095115.V4048@daemon.mistermishap.net> In-Reply-To: <20060329095115.V4048@daemon.mistermishap.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200603291214.56623.asstec@matik.com.br> X-Filter-Version: 1.11a (msrv.matik.com.br) X-Virus-Scanned: ClamAV version 0.88, clamav-milter version 0.87 on msrv.matik.com.br X-Virus-Status: Clean Cc: Rob Watt Subject: Re: SCB timeout and other errors + system hang with adaptec/seagate X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Mar 2006 15:15:20 -0000 On Wednesday 29 March 2006 11:57, Rob Watt wrote: > So, > > These error are still cropping up on some of my machines. After upgrading > the drive firmware and disabling SMART, some of my machines are stable > (and no longer generate the SCB timeout error). > > I am still having problems on a few of the machines though, and I have a I got SCB erros on my SCSI servers recently I changed the adapter (Adaptec) cable and terminator and no change I need to say that I have not seen this problem on releng_6 before a month = ago=20 but on early 6.0-Stable in beginning of december So I changed the slot of the adapter card and it worked for more or less ti= me=20 before getting the error, since I had polling enabled I didn't saw the NIC= =20 IRQs, so I disabled polling to see I disabled polling by not compiling it in and the effexted machines are=20 running stable since two weeks now strange that there is no HW IRQ conflict disabling polling on a 4.11-STABLE machine resolved the same problem jo=E3o A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br From owner-freebsd-scsi@FreeBSD.ORG Wed Mar 29 16:01:35 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9F2A916A420 for ; Wed, 29 Mar 2006 16:01:35 +0000 (UTC) (envelope-from ken@nargothrond.kdm.org) Received: from nargothrond.kdm.org (nargothrond.kdm.org [70.56.43.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id A04F343D5D for ; Wed, 29 Mar 2006 16:01:30 +0000 (GMT) (envelope-from ken@nargothrond.kdm.org) Received: from nargothrond.kdm.org (localhost [127.0.0.1]) by nargothrond.kdm.org (8.13.4/8.12.11) with ESMTP id k2TG1T3j095134 for ; Wed, 29 Mar 2006 09:01:29 -0700 (MST) (envelope-from ken@nargothrond.kdm.org) Received: (from ken@localhost) by nargothrond.kdm.org (8.13.4/8.12.5/Submit) id k2TG1T0q095133 for freebsd-scsi@freebsd.org; Wed, 29 Mar 2006 09:01:29 -0700 (MST) (envelope-from ken) Date: Wed, 29 Mar 2006 09:01:29 -0700 From: "Kenneth D. Merry" To: freebsd-scsi@freebsd.org Message-ID: <20060329160129.GA95084@nargothrond.kdm.org> References: <200603291349.k2TDnhZ0006001@lurza.secnetix.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200603291349.k2TDnhZ0006001@lurza.secnetix.de> User-Agent: Mutt/1.4.2i X-Virus-Scanned: ClamAV 0.87.1/1361/Tue Mar 28 23:50:38 2006 on nargothrond.kdm.org X-Virus-Status: Clean Subject: Re: Temperature sensor on SCSI disks (IBM / Hitachi) X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Mar 2006 16:01:35 -0000 On Wed, Mar 29, 2006 at 15:49:43 +0200, Oliver Fromme wrote: > Hi, > > I have the following SCSI disks in a server: > > at scbus0 target 0 lun 0 (pass0,da0) > at scbus0 target 1 lun 0 (pass1,da1) > > Searching the mailing lists revealed that IBM SCSI disks > (Hitachi nowadays) have a temperature sensor that can be > queried with a special (prioprietary) command like this: > > camcontrol cmd -n da -u 0 -c "4D 0 76 0 0 0 0 0 20 0" -i 32 "s9 i1" > > However, I get: "camcontrol: error sending command". > > Any advice? (I'm using 4-stable, BTW.) Use the -v flag for camcontrol to print sense information. That should tell you what the drive is complaining about. With some more recent IBM drives (possibly including DDYS drives, can't remember), you can get the temperature like this: camcontrol cmd da0 -v -u $i -c "4D 0 6F 0 0 0 0 0 20 0" -i 32 "s10 i1"` Ken -- Kenneth Merry ken@FreeBSD.ORG From owner-freebsd-scsi@FreeBSD.ORG Wed Mar 29 21:30:27 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CA55D16A400; Wed, 29 Mar 2006 21:30:27 +0000 (UTC) (envelope-from ticso@cicely12.cicely.de) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9CFB643D46; Wed, 29 Mar 2006 21:30:26 +0000 (GMT) (envelope-from ticso@cicely12.cicely.de) Received: from cicely5.cicely.de ([10.1.1.7]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id k2TLUMdA018705; Wed, 29 Mar 2006 23:30:22 +0200 (CEST) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (cicely12.cicely.de [10.1.1.14]) by cicely5.cicely.de (8.13.4/8.13.4) with ESMTP id k2TLUGoq070029 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 29 Mar 2006 23:30:17 +0200 (CEST) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (localhost [127.0.0.1]) by cicely12.cicely.de (8.13.4/8.13.3) with ESMTP id k2TLUGc8090401; Wed, 29 Mar 2006 23:30:16 +0200 (CEST) (envelope-from ticso@cicely12.cicely.de) Received: (from ticso@localhost) by cicely12.cicely.de (8.13.4/8.13.3/Submit) id k2TLUGG5090400; Wed, 29 Mar 2006 23:30:16 +0200 (CEST) (envelope-from ticso) Date: Wed, 29 Mar 2006 23:30:16 +0200 From: Bernd Walter To: "Kenneth D. Merry" Message-ID: <20060329213015.GI86354@cicely12.cicely.de> References: <200603291349.k2TDnhZ0006001@lurza.secnetix.de> <20060329160129.GA95084@nargothrond.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060329160129.GA95084@nargothrond.kdm.org> X-Operating-System: FreeBSD cicely12.cicely.de 5.4-STABLE alpha User-Agent: Mutt/1.5.9i X-Spam-Status: No, score=-5.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.4 X-Spam-Report: * -3.3 ALL_TRUSTED Did not pass through any untrusted hosts * -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% * [score: 0.0000] X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on cicely12.cicely.de Cc: freebsd-scsi@freebsd.org Subject: Re: Temperature sensor on SCSI disks (IBM / Hitachi) X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ticso@cicely.de List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Mar 2006 21:30:27 -0000 On Wed, Mar 29, 2006 at 09:01:29AM -0700, Kenneth D. Merry wrote: > On Wed, Mar 29, 2006 at 15:49:43 +0200, Oliver Fromme wrote: > > Hi, > > > > I have the following SCSI disks in a server: > > > > at scbus0 target 0 lun 0 (pass0,da0) > > at scbus0 target 1 lun 0 (pass1,da1) > > > > Searching the mailing lists revealed that IBM SCSI disks > > (Hitachi nowadays) have a temperature sensor that can be > > queried with a special (prioprietary) command like this: > > > > camcontrol cmd -n da -u 0 -c "4D 0 76 0 0 0 0 0 20 0" -i 32 "s9 i1" > > > > However, I get: "camcontrol: error sending command". > > > > Any advice? (I'm using 4-stable, BTW.) > > Use the -v flag for camcontrol to print sense information. That should > tell you what the drive is complaining about. So far I'm only aware of DGHS drives to support reading temperatures. -- B.Walter http://www.bwct.de http://www.fizon.de bernd@bwct.de info@bwct.de support@fizon.de From owner-freebsd-scsi@FreeBSD.ORG Wed Mar 29 21:36:31 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 97C0216A401 for ; Wed, 29 Mar 2006 21:36:31 +0000 (UTC) (envelope-from ken@nargothrond.kdm.org) Received: from nargothrond.kdm.org (nargothrond.kdm.org [70.56.43.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id EBCA643D69 for ; Wed, 29 Mar 2006 21:36:30 +0000 (GMT) (envelope-from ken@nargothrond.kdm.org) Received: from nargothrond.kdm.org (localhost [127.0.0.1]) by nargothrond.kdm.org (8.13.4/8.12.11) with ESMTP id k2TLaRuF097421; Wed, 29 Mar 2006 14:36:27 -0700 (MST) (envelope-from ken@nargothrond.kdm.org) Received: (from ken@localhost) by nargothrond.kdm.org (8.13.4/8.12.5/Submit) id k2TLaRFj097420; Wed, 29 Mar 2006 14:36:27 -0700 (MST) (envelope-from ken) Date: Wed, 29 Mar 2006 14:36:27 -0700 From: "Kenneth D. Merry" To: ticso@cicely.de Message-ID: <20060329213627.GA97376@nargothrond.kdm.org> References: <200603291349.k2TDnhZ0006001@lurza.secnetix.de> <20060329160129.GA95084@nargothrond.kdm.org> <20060329213015.GI86354@cicely12.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060329213015.GI86354@cicely12.cicely.de> User-Agent: Mutt/1.4.2i X-Virus-Scanned: ClamAV 0.87.1/1363/Wed Mar 29 13:38:37 2006 on nargothrond.kdm.org X-Virus-Status: Clean Cc: freebsd-scsi@freebsd.org Subject: Re: Temperature sensor on SCSI disks (IBM / Hitachi) X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Mar 2006 21:36:31 -0000 On Wed, Mar 29, 2006 at 23:30:16 +0200, Bernd Walter wrote: > On Wed, Mar 29, 2006 at 09:01:29AM -0700, Kenneth D. Merry wrote: > > On Wed, Mar 29, 2006 at 15:49:43 +0200, Oliver Fromme wrote: > > > Hi, > > > > > > I have the following SCSI disks in a server: > > > > > > at scbus0 target 0 lun 0 (pass0,da0) > > > at scbus0 target 1 lun 0 (pass1,da1) > > > > > > Searching the mailing lists revealed that IBM SCSI disks > > > (Hitachi nowadays) have a temperature sensor that can be > > > queried with a special (prioprietary) command like this: > > > > > > camcontrol cmd -n da -u 0 -c "4D 0 76 0 0 0 0 0 20 0" -i 32 "s9 i1" > > > > > > However, I get: "camcontrol: error sending command". > > > > > > Any advice? (I'm using 4-stable, BTW.) > > > > Use the -v flag for camcontrol to print sense information. That should > > tell you what the drive is complaining about. > > So far I'm only aware of DGHS drives to support reading temperatures. # camcontrol devlist at scbus0 target 0 lun 0 (pass0,da0) at scbus0 target 1 lun 0 (pass1,da1) at scbus0 target 2 lun 0 (pass2,da2) at scbus1 target 4 lun 0 (pass3,cd0) at scbus1 target 5 lun 0 (pass4,cd1) at scbus2 target 0 lun 0 (pass5,cd2) # camcontrol cmd da0 -v -c "4D 0 6F 0 0 0 0 0 20 0" -i 32 "s10 i1" 30 # camcontrol cmd da1 -v -c "4D 0 6F 0 0 0 0 0 20 0" -i 32 "s10 i1" 31 Ken -- Kenneth Merry ken@FreeBSD.ORG From owner-freebsd-scsi@FreeBSD.ORG Thu Mar 30 00:09:17 2006 Return-Path: X-Original-To: scsi@freebsd.org Delivered-To: freebsd-scsi@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3663116A422 for ; Thu, 30 Mar 2006 00:09:17 +0000 (UTC) (envelope-from ottavio@utta.com) Received: from utta.com (p4142-ipad206sapodori.hokkaido.ocn.ne.jp [60.39.3.142]) by mx1.FreeBSD.org (Postfix) with SMTP id 52A8D43D49 for ; Thu, 30 Mar 2006 00:09:16 +0000 (GMT) (envelope-from ottavio@utta.com) Message-ID: <000001c6538e$1edd2a30$52d6a8c0@unw55> From: "Ottavio Housley" To: scsi@freebsd.org Date: Wed, 29 Mar 2006 19:08:49 -0500 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: news good X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Ottavio Housley List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Mar 2006 00:09:17 -0000 De h ar Home Ow g ner ,=20 =20 Your c o redit doesn't matter to us ! If you OW E N real e P st 4 at 3 e and want IMMED f IA N TE ca 1 sh to spe Y nd ANY way you like, or simply wish=20 to L 6 OWER your monthly p i ayments by a third or more, here are the de H als=20 we have T y OD w AY :=20 =20 $4 X 88,000.00 at a 3. F 67% fi o xed-ra E te=20 $37 h 2,000.00 at a 3 Y .90% variabl k e-rat V e=20 $4 Y 92,000.00 at a 3.2 y 1% i o ntere Y st-only=20 $24 9 8,000.00 at a 3. h 36% fix a ed-rat g e=20 $19 R 8,000.00 at a 3 q .55% var o iable-ra T te=20 =20 Hur Q ry, when these d 4 eaIs are gone, they are gone ! =20 Don't worry about approv C al, your credi X t will not d B isqualify you !=20 =20 Visi R t our sit 7 e =20 =20 Sincerely, Ottavio Housley =20 Appro B val Manager From owner-freebsd-scsi@FreeBSD.ORG Thu Mar 30 12:43:34 2006 Return-Path: X-Original-To: freebsd-scsi@FreeBSD.ORG Delivered-To: freebsd-scsi@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4D9F116A424 for ; Thu, 30 Mar 2006 12:43:34 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id E583443D6D for ; Thu, 30 Mar 2006 12:43:24 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (nmbcnc@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k2UChHQf054251 for ; Thu, 30 Mar 2006 14:43:23 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k2UChHSp054250; Thu, 30 Mar 2006 14:43:17 +0200 (CEST) (envelope-from olli) Date: Thu, 30 Mar 2006 14:43:17 +0200 (CEST) Message-Id: <200603301243.k2UChHSp054250@lurza.secnetix.de> From: Oliver Fromme To: freebsd-scsi@FreeBSD.ORG In-Reply-To: <20060329160129.GA95084@nargothrond.kdm.org> X-Newsgroups: list.freebsd-scsi User-Agent: tin/1.8.0-20051224 ("Ronay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Thu, 30 Mar 2006 14:43:23 +0200 (CEST) Cc: Subject: Re: Temperature sensor on SCSI disks (IBM / Hitachi) X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Mar 2006 12:43:34 -0000 Kenneth D. Merry wrote: > Oliver Fromme wrote: > > I have the following SCSI disks in a server: > > > > at scbus0 target 0 lun 0 (pass0,da0) > > at scbus0 target 1 lun 0 (pass1,da1) > > > > Searching the mailing lists revealed that IBM SCSI disks > > (Hitachi nowadays) have a temperature sensor that can be > > queried with a special (prioprietary) command like this: > > [...] > With some more recent IBM drives (possibly including DDYS drives, can't > remember), you can get the temperature like this: > > camcontrol cmd da0 -v -u $i -c "4D 0 6F 0 0 0 0 0 20 0" -i 32 "s10 i1"` Cool, that one works. # camcontrol cmd da0 -v -c "4D 0 6F 0 0 0 0 0 20 0" -i 32 "s10 i1" 33 # camcontrol cmd da1 -v -c "4D 0 6F 0 0 0 0 0 20 0" -i 32 "s10 i1" 36 Thanks very much! Do such commands exist for other drives or vendors, too? Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things." -- Doug Gwyn From owner-freebsd-scsi@FreeBSD.ORG Thu Mar 30 18:21:05 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 48CC816A423 for ; Thu, 30 Mar 2006 18:21:05 +0000 (UTC) (envelope-from bmiele@ipnstock.com) Received: from shanty.ipnstock.com (static-71-241-222-63.port.east.verizon.net [71.241.222.63]) by mx1.FreeBSD.org (Postfix) with ESMTP id BFAD043D4C for ; Thu, 30 Mar 2006 18:21:04 +0000 (GMT) (envelope-from bmiele@ipnstock.com) Received: from shanty.ipnstock.com (localhost [127.0.0.1]) by shanty.ipnstock.com (8.13.4/8.13.4) with ESMTP id k2UIL3CV092547 for ; Thu, 30 Mar 2006 13:21:03 -0500 (EST) (envelope-from bmiele@ipnstock.com) Received: from localhost (brad@localhost) by shanty.ipnstock.com (8.13.4/8.13.3/Submit) with ESMTP id k2UIL2Ko092544 for ; Thu, 30 Mar 2006 13:21:03 -0500 (EST) (envelope-from bmiele@ipnstock.com) X-Authentication-Warning: shanty.ipnstock.com: brad owned process doing -bs Date: Thu, 30 Mar 2006 13:21:02 -0500 (EST) From: brad miele X-X-Sender: brad@shanty.ipnstock.com To: freebsd-scsi@freebsd.org Message-ID: <20060330131105.A73721@shanty.ipnstock.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: test utilities X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Mar 2006 18:21:05 -0000 Hi, I have been fighting with msa1500/msa20/qlogic/freebsd5 issues for a while now, and am trying to nail down where things are going bad. I have mentioned this before, my setup is an msa1500 controller with 2 of the msa(30?) SCSI shelves and two of the msa20 sata shelves. the sata shelves are ADG (i have also used raid5), one lun per shelf, 10 drives w/2 spares. My msa1500s and msa20s all have the most recent firmware and the qlogic card(isp0: ) with the ispfw module dynamically loaded. the issues are usually that drives and luns will just take themselves offline, mark disks bad, and pannic my freebsd box. the luns are invariably fine when brought back up, and after fsck can be used for random amount of time before this happens again. syslog shows occasional timeouts and resets. what i want is a tool or tools to help me test the setup from the freebsd box through to the san and help me pinpoint the problem area. does such a thing exist? thanks, Brad --------------------- Brad Miele IPNStock.com bmiele@ipnstock.com From owner-freebsd-scsi@FreeBSD.ORG Thu Mar 30 18:47:13 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7681216A41F for ; Thu, 30 Mar 2006 18:47:13 +0000 (UTC) (envelope-from christias@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.238]) by mx1.FreeBSD.org (Postfix) with ESMTP id 08BF443D46 for ; Thu, 30 Mar 2006 18:47:12 +0000 (GMT) (envelope-from christias@gmail.com) Received: by wproxy.gmail.com with SMTP id i21so528199wra for ; Thu, 30 Mar 2006 10:47:12 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Hp2QP/HUGd737h6qxS8+ceBIc3GtK58dUDufgtGdCS3cSQHP8Ufsla22XPC6rV3HDUbisDiFssuZa+wYRTA07FdaVaTufQKKD8pEXBW7CYV1OM9v5VCE8HhtnLDVn38Do4EnccjhR8UUuPgcLz/3ax69P3yWOrMfIRB3ej6P85s= Received: by 10.64.10.5 with SMTP id 5mr1466256qbj; Thu, 30 Mar 2006 10:47:11 -0800 (PST) Received: by 10.64.196.6 with HTTP; Thu, 30 Mar 2006 10:47:11 -0800 (PST) Message-ID: Date: Thu, 30 Mar 2006 21:47:11 +0300 From: "Panagiotis Christias" To: freebsd-scsi@freebsd.org In-Reply-To: <200603301243.k2UChHSp054250@lurza.secnetix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20060329160129.GA95084@nargothrond.kdm.org> <200603301243.k2UChHSp054250@lurza.secnetix.de> Subject: Re: Temperature sensor on SCSI disks (IBM / Hitachi) X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Mar 2006 18:47:13 -0000 On 3/30/06, Oliver Fromme wrote: > Kenneth D. Merry wrote: > > Oliver Fromme wrote: > > > I have the following SCSI disks in a server: > > > > > > at scbus0 target 0 lun 0 (pass0,da0) > > > at scbus0 target 1 lun 0 (pass1,da1) > > > > > > Searching the mailing lists revealed that IBM SCSI disks > > > (Hitachi nowadays) have a temperature sensor that can be > > > queried with a special (prioprietary) command like this: > > > [...] > > With some more recent IBM drives (possibly including DDYS drives, can'= t > > remember), you can get the temperature like this: > > > > camcontrol cmd da0 -v -u $i -c "4D 0 6F 0 0 0 0 0 20 0" -i 32 "s10 i1"= ` > > Cool, that one works. > > # camcontrol cmd da0 -v -c "4D 0 6F 0 0 0 0 0 20 0" -i 32 "s10 i1" > 33 > # camcontrol cmd da1 -v -c "4D 0 6F 0 0 0 0 0 20 0" -i 32 "s10 i1" > 36 > > Thanks very much! > > Do such commands exist for other drives or vendors, too? > > Best regards > Oliver Very interesting! I am wondering if it would be possible to get that kind of information if the disks are part of a hardware RAID. Our systems have IBM/Hitachi disks connected on RAID controllers (accessible using the amr driver). Any ideas? Thank you in advance, Panagiotis From owner-freebsd-scsi@FreeBSD.ORG Fri Mar 31 03:34:20 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A65EF16A420 for ; Fri, 31 Mar 2006 03:34:20 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id EC99443D6B for ; Fri, 31 Mar 2006 03:34:15 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k2V3YETH011818; Thu, 30 Mar 2006 20:34:14 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <442CA330.4090904@samsco.org> Date: Thu, 30 Mar 2006 20:34:08 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051230 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Panagiotis Christias References: <20060329160129.GA95084@nargothrond.kdm.org> <200603301243.k2UChHSp054250@lurza.secnetix.de> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: freebsd-scsi@freebsd.org Subject: Re: Temperature sensor on SCSI disks (IBM / Hitachi) X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Mar 2006 03:34:20 -0000 Panagiotis Christias wrote: > On 3/30/06, Oliver Fromme wrote: > >>Kenneth D. Merry wrote: >> > Oliver Fromme wrote: >> > > I have the following SCSI disks in a server: >> > > >> > > at scbus0 target 0 lun 0 (pass0,da0) >> > > at scbus0 target 1 lun 0 (pass1,da1) >> > > >> > > Searching the mailing lists revealed that IBM SCSI disks >> > > (Hitachi nowadays) have a temperature sensor that can be >> > > queried with a special (prioprietary) command like this: >> > > [...] >> > With some more recent IBM drives (possibly including DDYS drives, can't >> > remember), you can get the temperature like this: >> > >> > camcontrol cmd da0 -v -u $i -c "4D 0 6F 0 0 0 0 0 20 0" -i 32 "s10 i1"` >> >>Cool, that one works. >> >># camcontrol cmd da0 -v -c "4D 0 6F 0 0 0 0 0 20 0" -i 32 "s10 i1" >>33 >># camcontrol cmd da1 -v -c "4D 0 6F 0 0 0 0 0 20 0" -i 32 "s10 i1" >>36 >> >>Thanks very much! >> >>Do such commands exist for other drives or vendors, too? >> >>Best regards >> Oliver > > > Very interesting! I am wondering if it would be possible to get that > kind of information if the disks are part of a hardware RAID. Our > systems have IBM/Hitachi disks connected on RAID controllers > (accessible using the amr driver). Any ideas? > > Thank you in advance, > Panagiotis The amr driver has a SCSI passthrough mechanism for talking to the underlying disks (assuming that the disks are SCSI and not SATA), but it's been broken for several months. Since such a mechanism has such limited use, I haven't bothered to fix it. I definitely don't have time to fix it now, but I can give pointers to anyone who does want to look at it. Scott From owner-freebsd-scsi@FreeBSD.ORG Sat Apr 1 05:46:01 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4CF0116A510 for ; Sat, 1 Apr 2006 05:46:01 +0000 (UTC) (envelope-from ehrhard.herbst@sz-online.de) Received: from smtp.sz-online.de (smtp.sz-online.de [193.98.117.121]) by mx1.FreeBSD.org (Postfix) with SMTP id 74A1C43D46 for ; Sat, 1 Apr 2006 05:46:00 +0000 (GMT) (envelope-from ehrhard.herbst@sz-online.de) Received: (qmail 12420 invoked from network); 1 Apr 2006 05:41:25 -0000 Received: from smtp.sz-online.de (HELO webmail.sz-online.de) (193.98.117.121) by smtp.sz-online.de with SMTP; 1 Apr 2006 05:41:25 -0000 Received: from 212.144.2.231 (SquirrelMail authenticated user ehrhard.herbst) by webmail.sz-online.de with HTTP; Sat, 1 Apr 2006 07:41:25 +0200 (CEST) Message-ID: <52821.212.144.2.231.1143870085.squirrel@webmail.sz-online.de> Date: Sat, 1 Apr 2006 07:41:25 +0200 (CEST) From: ehrhard.herbst@sz-online.de To: freebsd-scsi@freebsd.org User-Agent: SquirrelMail/1.4.2 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 Importance: Normal Subject: Problem with FreeBSD Installation X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Apr 2006 05:46:01 -0000 Hello again, may I ask you for help with the following Problem: When I try to install FreeBsd6.0, there is the following error during the boot process occurs: ahc0: probe1:ahc0:0:1:0: SCB 6: immediate reset Flags 0x620 ahc0: probe1:ahc0:0:1:0: No longer in timeout, status=25b ahc0: Issued channel A bus reset, SCBs 6 aborted. ... ... ... ahc0: Timedout SCBs complete. Interrupts may not be functioning ... ... ... There are variants of the messages with different SCB, flags and status. After a long time (spent probing SCSI devices?) the sysinstall menu appears. Continuing the installation, the install program does not find any disk. Adapter firmware and BIOS are up to date. BUT, FreeBSD5.2 is running on that machine and dmesg produces the following output: Copyright (c) 1992-2004 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 5.2.1-RELEASE #0: Mon Feb 23 20:45:55 GMT 2004 root@wv1u.btc.adaptec.com:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel "/boot/kernel/kernel" at 0xc0a35000. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc0a351f4. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel Pentium III (797.97-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x686 Stepping = 6 Features=0x383f9ff real memory = 268369920 (255 MB) avail memory = 251047936 (239 MB) Pentium Pro MTRR support enabled npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard pcibios: BIOS version 2.10 Using $PIR table, 6 entries at 0xc00fdee0 acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 acpi_cpu0: on acpi0 acpi_button0: on acpi0 acpi_button1: on acpi0 pcib0: port 0x5000-0x500f,0x4080-0x40ff,0x4000-0x407f,0xcf8-0xcff on acpi0 pci0: on pcib0 pcib0: slot 9 INTA is routed to irq 10 pcib0: slot 10 INTA is routed to irq 12 pcib0: slot 11 INTA is routed to irq 5 agp0: mem 0xd8000000-0xdbffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pcib0: slot 1 INTA is routed to irq 11 pcib1: slot 0 INTA is routed to irq 11 pci1: at device 0.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xd000-0xd00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: at 0x170 irq 15 on atapci0 ata1: [MPSAFE] pci0: at device 7.3 (no driver attached) rl0: port 0xd800-0xd8ff mem 0xe3001000-0xe30010ff irq 10 at device 9.0 on pci0 rl0: Ethernet address: 00:40:33:ab:df:66 miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pci0: at device 10.0 (no driver attached) ahc0: port 0xe000-0xe0ff mem 0xe3000000-0xe3000fff irq 5 at device 11.0 on pci0 aic7870: Single Channel A, SCSI Id=7, 16/253 SCBs fdc0: port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ppc0 port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 orm0: