From owner-freebsd-scsi@FreeBSD.ORG Sun May 10 21:27:16 2009 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 62A201065675 for ; Sun, 10 May 2009 21:27:16 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (alchemy.franken.de [194.94.249.214]) by mx1.freebsd.org (Postfix) with ESMTP id D05D58FC1F for ; Sun, 10 May 2009 21:27:15 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (localhost [127.0.0.1]) by alchemy.franken.de (8.14.3/8.14.3/ALCHEMY.FRANKEN.DE) with ESMTP id n4AKnxkV027242 for ; Sun, 10 May 2009 22:49:59 +0200 (CEST) (envelope-from marius@alchemy.franken.de) Received: (from marius@localhost) by alchemy.franken.de (8.14.3/8.14.3/Submit) id n4AKnxlt027241 for freebsd-scsi@freebsd.org; Sun, 10 May 2009 22:49:59 +0200 (CEST) (envelope-from marius) Date: Sun, 10 May 2009 22:49:59 +0200 From: Marius Strobl To: freebsd-scsi@freebsd.org Message-ID: <20090510204959.GA27204@alchemy.franken.de> References: <49A2B464.4020409@kasimir.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49A2B464.4020409@kasimir.com> User-Agent: Mutt/1.4.2.3i Subject: Re: isp panic after printing the uptime 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: Sun, 10 May 2009 21:27:16 -0000 On Mon, Feb 23, 2009 at 03:36:20PM +0100, Florian Smeets wrote: > Hi, > > i have a 100% reproducible panic on sparc64 with an isp controller. > Every time i reboot/shutdown the machine it panics after printing > "Uptime: XXXX". I'm not sure if this is more scsi or sparc64 related but > as the trace includes isp_* functions i went for scsi@. > > The controller used is: > > isp0: port 0x300-0x3ff mem > 0x100000-0x100fff at device 4.0 on pci2 > isp0: [ITHREAD] > isp0: Board Type 2200, Chip Revision 0x5, loaded F/W Revision 2.2.6 > isp0: invalid NVRAM header > isp0: invalid NVRAM header > > The messages prior to the panic and the panic look like this: > > Sayncing diisks, vnotdes remaiining...n2 g (max 60 seconds) for system > process `syncer' to stop...2 1 0 1 0 0 done > All buffers synced. > zfs_umount:969[0]: Force unmount is not supported, removing FORCE flag. > zfs_umount:969[0]: Force unmount is not supported, removing FORCE flag. > zfs_umount:969[0]: Force unmount is not supported, removing FORCE flag. > lock order reversal: > 1st 0xfffff800038394e0 ufs (ufs) @ /usr/src/sys/kern/vfs_mount.c:1202 > 2nd 0xfffff80003839c40 devfs (devfs) @ /usr/src/sys/kern/vfs_subr.c:2092 > KDB: stack backtrace: > _witness_debugger() at _witness_debugger+0x38 > witness_checkorder() at witness_checkorder+0xcf8 > __lockmgr_args() at __lockmgr_args+0x874 > vop_stdlock() at vop_stdlock+0x38 > VOP_LOCK1_APV() at VOP_LOCK1_APV+0x110 > _vn_lock() at _vn_lock+0x80 > vget() at vget+0x120 > devfs_allocv() at devfs_allocv+0x114 > devfs_root() at devfs_root+0x3c > dounmount() at dounmount+0x490 > vfs_unmountall() at vfs_unmountall+0x3c > boot() at boot+0x674 > reboot() at reboot+0x58 > syscall() at syscall+0x2bc > -- syscall (55, FreeBSD ELF64, reboot) %o7=0x102a88 -- > userland() at 0x12b348 > user trace: trap %o7=0x102a88 > pc 0x12b348, sp 0x7fdffffdd91 > pc 0x101778, sp 0x7fdffffdf01 > pc 0x1001d0, sp 0x7fdffffe531 > pc 0, sp 0x7fdffffe5f1 > done > Uptime: 6m9s > panic: trap: fast data access mmu miss > cpuid = 0 > KDB: enter: panic > [thread pid 1 tid 100001 ] > Stopped at kdb_enter+0x80: ta %xcc, 1 > db> where > Tracing pid 1 tid 100001 td 0xfffff80002082000 > panic() at panic+0x20c > trap() at trap+0x570 > -- fast data access mmu miss tar=0x1454156000 %o7=0xc040e7a4 -- > _mtx_lock_spin_flags() at _mtx_lock_spin_flags+0x5c > callout_lock() at callout_lock+0x50 > untimeout() at untimeout+0xc > isp_done() at isp_done+0x140 > isp_intr() at isp_intr+0x3eb8 > isp_poll() at isp_poll+0x38 > xpt_polled_action() at xpt_polled_action+0xf0 > dashutdown() at dashutdown+0x130 > boot() at boot+0x8ac > reboot() at reboot+0x58 > syscall() at syscall+0x2bc > -- syscall (55, FreeBSD ELF64, reboot) %o7=0x102a88 -- > userland() at 0x12b348 > user trace: trap %o7=0x102a88 > pc 0x12b348, sp 0x7fdffffdd91 > pc 0x101778, sp 0x7fdffffdf01 > pc 0x1001d0, sp 0x7fdffffe531 > pc 0, sp 0x7fdffffe5f1 > done > db> > > Anything i can do, aside from not rebooting the machine :-) ? > For the records, this was fixed with r191979. Marius From owner-freebsd-scsi@FreeBSD.ORG Mon May 11 11:07:04 2009 Return-Path: Delivered-To: freebsd-scsi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 435CA1065672 for ; Mon, 11 May 2009 11:07:04 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 262878FC21 for ; Mon, 11 May 2009 11:07:04 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n4BB74s4086096 for ; Mon, 11 May 2009 11:07:04 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n4BB73ip086092 for freebsd-scsi@FreeBSD.org; Mon, 11 May 2009 11:07:03 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 11 May 2009 11:07:03 GMT Message-Id: <200905111107.n4BB73ip086092@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-scsi@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-scsi@FreeBSD.org 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, 11 May 2009 11:07:04 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o amd64/132394 scsi [isp] - bad underruns with QLogic qla2300 and amd64 o kern/132250 scsi [ciss] ciss driver does not support more then 15 drive o kern/132206 scsi [mpt] system panics on boot when mirroring and 2nd dri o kern/131032 scsi [panic] hald causing panic in scsi_sg o kern/130735 scsi [cam] [patch] pass M_NOWAIT to the malloc() call insid o kern/130621 scsi [mpt] tranfer rate is inscrutable slow when use lsi213 o kern/129602 scsi [ahd] ahd(4) gets confused and wedges SCSI bus o kern/128452 scsi [sa] [panic] Accessing SCSI tape drive randomly crashe o kern/128245 scsi [scsi] "inquiry data fails comparison at DV1 step" [re o kern/127927 scsi [isp] isp(4) target driver crashes kernel when set up o kern/126866 scsi [isp] [panic] kernel panic on card initialization o kern/124667 scsi [amd] [panic] FreeBSD-7 kernel page faults at amd-scsi o kern/123674 scsi [ahc] ahc driver dumping o kern/123666 scsi [aac] attach fails with Adaptec SAS RAID 3805 controll o sparc/121676 scsi [iscsi] iscontrol do not connect iscsi-target on sparc o kern/120487 scsi [sg] scsi_sg incompatible with scanners o kern/120247 scsi [mpt] FreeBSD 6.3 and LSI Logic 1030 = only 3.300MB/s o kern/119668 scsi [cam] [patch] certain errors are too verbose comparing o kern/114597 scsi [sym] System hangs at SCSI bus reset with dual HBAs o kern/110847 scsi [ahd] Tyan U320 onboard problem with more than 3 disks o kern/99954 scsi [ahc] reading from DVD failes on 6.x [regression] o kern/94838 scsi Kernel panic while mounting SD card with lock switch o o kern/92798 scsi [ahc] SCSI problem with timeouts o kern/90282 scsi [sym] SCSI bus resets cause loss of ch device o kern/76178 scsi [ahd] Problem with ahd and large SCSI Raid system o kern/74627 scsi [ahc] [hang] Adaptec 2940U2W Can't boot 5.3 s kern/61165 scsi [panic] kernel page fault after calling cam_send_ccb o kern/60641 scsi [sym] Sporadic SCSI bus resets with 53C810 under load o kern/60598 scsi wire down of scsi devices conflicts with config s kern/57398 scsi [mly] Current fails to install on mly(4) based RAID di o kern/52638 scsi [panic] SCSI U320 on SMP server won't run faster than o kern/44587 scsi dev/dpt/dpt.h is missing defines required for DPT_HAND o kern/40895 scsi wierd kernel / device driver bug o kern/39388 scsi ncr/sym drivers fail with 53c810 and more than 256MB m o kern/38828 scsi [dpt] [request] DPT PM2012B/90 doesn't work o kern/35234 scsi World access to /dev/pass? (for scanner) requires acce 36 problems total. From owner-freebsd-scsi@FreeBSD.ORG Tue May 12 19:52:16 2009 Return-Path: Delivered-To: freebsd-scsi@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0BF0E106564A; Tue, 12 May 2009 19:52:16 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id D55608FC0A; Tue, 12 May 2009 19:52:15 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n4CJqFEu097767; Tue, 12 May 2009 19:52:15 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n4CJqFpP097763; Tue, 12 May 2009 19:52:15 GMT (envelope-from linimon) Date: Tue, 12 May 2009 19:52:15 GMT Message-Id: <200905121952.n4CJqFpP097763@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-scsi@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/134488: [mpt] MPT SCSI driver probes max. 8 LUNs per device 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, 12 May 2009 19:52:16 -0000 Old Synopsis: [SCSI] MPT SCSI driver probes max. 8 LUNs per device New Synopsis: [mpt] MPT SCSI driver probes max. 8 LUNs per device Responsible-Changed-From-To: freebsd-bugs->freebsd-scsi Responsible-Changed-By: linimon Responsible-Changed-When: Tue May 12 19:51:36 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=134488 From owner-freebsd-scsi@FreeBSD.ORG Wed May 13 05:10:04 2009 Return-Path: Delivered-To: freebsd-scsi@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6366F10656A3 for ; Wed, 13 May 2009 05:10:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 519228FC21 for ; Wed, 13 May 2009 05:10:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n4D5A4rv042765 for ; Wed, 13 May 2009 05:10:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n4D5A4NT042764; Wed, 13 May 2009 05:10:04 GMT (envelope-from gnats) Date: Wed, 13 May 2009 05:10:04 GMT Message-Id: <200905130510.n4D5A4NT042764@freefall.freebsd.org> To: freebsd-scsi@FreeBSD.org From: Scott Long Cc: Subject: Re: kern/134488: [mpt] MPT SCSI driver probes max. 8 LUNs per device X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Scott Long List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 May 2009 05:10:04 -0000 The following reply was made to PR kern/134488; it has been noted by GNATS. From: Scott Long To: bug-followup@FreeBSD.org, michel.bouissou@bioclinica.com Cc: Subject: Re: kern/134488: [mpt] MPT SCSI driver probes max. 8 LUNs per device Date: Tue, 12 May 2009 22:59:42 -0600 Increasing the max_lun number in the code is not the solution. Which arbitrary number should be chosen? If it's increased to 32, what about those who want 64? What about the problems created for those with older hardware that can't handle high lun scanning? The correct action requires a significant amount of code to be written and tested; if it were trivial it would have been done already. I know this response is unsatisfying and slightly aloof, and I apologize for that, but right now it's easier to ask that admins recompile for this situation than it is to tear up the core SCSI scanning code. Scott From owner-freebsd-scsi@FreeBSD.ORG Wed May 13 15:00:21 2009 Return-Path: Delivered-To: freebsd-scsi@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6FCC310656BC for ; Wed, 13 May 2009 15:00:21 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 430528FC30 for ; Wed, 13 May 2009 15:00:15 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n4DF0FXj079386 for ; Wed, 13 May 2009 15:00:15 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n4DF0F4K079385; Wed, 13 May 2009 15:00:15 GMT (envelope-from gnats) Date: Wed, 13 May 2009 15:00:15 GMT Message-Id: <200905131500.n4DF0F4K079385@freefall.freebsd.org> To: freebsd-scsi@FreeBSD.org From: Michel Bouissou Cc: Subject: Re: kern/134488: [mpt] MPT SCSI driver probes max. 8 LUNs per device X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Michel Bouissou List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 May 2009 15:00:36 -0000 The following reply was made to PR kern/134488; it has been noted by GNATS. From: Michel Bouissou To: Scott Long Cc: bug-followup@FreeBSD.org Subject: Re: kern/134488: [mpt] MPT SCSI driver probes max. 8 LUNs per device Date: Wed, 13 May 2009 16:24:31 +0200 On mar, 2009-05-12 at 22:59 -0600, Scott Long wrote: > Increasing the max_lun number in the code is not the solution. Which > arbitrary number should be chosen? If it's increased to 32, what about > those who want 64? Well, 8 is as much arbitrary than 32 would be, but 32 would cover a wider use spectrum. SCSI disks enclosures holding 16 to 20 disks are quite commonplace, and some show each disk as a LUN on the same SCSI device (i.e. some SCSI to SATA enclosures, or some RAID bays with RAID turned off to use ZFS RAID instead). > What about the problems created for those with older > hardware that can't handle high lun scanning? I'm not sure whether this exists. Possibly. My own SCSI card BIOS (LSILogic 1030 Ultra4 Adapter) only scans LUNs 0-7 when the system boots, *but* that doesn't prevent FreeBSD to use much higher LUN numbers when dev/mpt/mpt_cam.c is patched and recompiled for allowing so. > The correct action requires a significant amount of code to be written > and tested; if it were trivial it would have been done already. Maybe guessing the highest LUN number to scan according to HW type would be difficult, but would it be also very difficult to make this a parameter that could default to 8 and be set to higher values with an entry i.e. in /boot/loader.conf ? Would be easier than having to recompile the kernel...