From glen.j.barber at gmail.com Thu Oct 1 22:08:51 2009 From: glen.j.barber at gmail.com (Glen Barber) Date: Thu Oct 1 22:08:57 2009 Subject: asr(4) - camcontrol(8) reports incorrect dev_openings on 7.2-RELEASE-p3 Message-ID: <4ad871310910011448s6140c7efia9de05d5063222d9@mail.gmail.com> Hello list Following up on a post from April [1] regarding a Supermicro server with an Adaptec 2010S raid controller with two mirrored disks, on 7.1-RELEASE, the output of 'camcontrol tags da0' listed: (pass0:asr0:0:0:0): dev_openings 1 Prior to that post, there was a 'HEADS UP' post [2] noting a regression in the CAM subsystem. The 'HEADS UP' post announced the regression was fixed with HEAD (8-CURRENT) r188570 and would be MFC'd to 7-STABLE [3]. Today, I upgraded one of these machines from 7.1-RELEASE-p4 to 7.2-RELEASE-p3, and camcontrol(8) still reports the output above. I found a USENET post [4] from early August reporting the same behavior on 8.0-BETA2. Is this behavior in fact a continued regression? Is manually setting the number of tags with -N the only workaround? Thanks in advance. [1] - http://lists.freebsd.org/pipermail/freebsd-scsi/2009-April/003880.html [2] - http://lists.freebsd.org/pipermail/freebsd-scsi/2009-February/003806.html [3] - http://svn.freebsd.org/viewvc/base?view=revision&revision=188570 [4] - http://groups.google.com/group/comp.unix.bsd.freebsd.misc/msg/40e3b7566a15662b?hl=en -- Glen Barber From scottl at samsco.org Fri Oct 2 05:11:32 2009 From: scottl at samsco.org (Scott Long) Date: Fri Oct 2 05:14:10 2009 Subject: [PATCH] Moving CAM config to private SYSINIT Message-ID: All, I'm working on fixing the boot-from-USB-doesn't-always work problem, which turns out to be a race between several different threads at boot. As a pre-requisite to controlling the race, I'm moving the CAM bus/device scan to its own private SYSINIT so that its execution is ordered. In practice, it should not affect anything, and systems should continue to boot as normal. That's where I need help in testing. If you have any CAM/SCSI devices that are present when you boot, please test this patch and let me know if it changes anything for you, good or bad. http://people.freebsd.org/~scottl/cam_hook.diff Thanks! Scott From bugmaster at FreeBSD.org Mon Oct 5 11:07:00 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Oct 5 11:09:28 2009 Subject: Current problem reports assigned to freebsd-scsi@FreeBSD.org Message-ID: <200910051106.n95B6xSJ088792@freefall.freebsd.org> 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 kern/138789 scsi [cam] [patch] cd(4) patch for drives/discs failing the o kern/138384 scsi [ips] [patch] NULL pointer dereference in ipsd_dump() o kern/138379 scsi [aic7xxx] [patch] Memory leak in output_listing() in f o kern/138376 scsi [cam] [patch] Memory leak in scsi_low_attach_xs() in f o kern/134488 scsi [mpt] MPT SCSI driver probes max. 8 LUNs per device 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 41 problems total. From therion at ninth-art.de Mon Oct 5 11:39:01 2009 From: therion at ninth-art.de (Georg Bege) Date: Mon Oct 5 11:39:12 2009 Subject: LSI SAS 1064E supported by FBSD8? Message-ID: <7d7ab653cecaf04cc8df8df8eb1925dd.squirrel@webmail.coruscant.info> Hello Does anyone know if this card/chip is supported by FBSD 8.1-RC1? LSISAS1064E This is on an Asus Pike Card for the mainboard Asus Z8PE-D18. Im also able to buy a different controller I just have to know if its supported or not. I've found this in the hardware notes: LSI Logic AS1064 (mpt driver). But Im still unsure if this is the same or equal chip... The card I wanted to buy is also called: Asus PIKE 1064E - I hope someone knows. cheers !DSPAM:4ac9dad2651038983666460! From scottl at samsco.org Tue Oct 6 04:17:25 2009 From: scottl at samsco.org (Scott Long) Date: Tue Oct 6 04:17:32 2009 Subject: LSI SAS 1064E supported by FBSD8? In-Reply-To: <7d7ab653cecaf04cc8df8df8eb1925dd.squirrel@webmail.coruscant.info> References: <7d7ab653cecaf04cc8df8df8eb1925dd.squirrel@webmail.coruscant.info> Message-ID: <7D9BCCA9-EF4A-4FBA-BC04-5A361A771974@samsco.org> I believe that all 1064 models will work. Scott On Oct 5, 2009, at 5:38 AM, Georg Bege wrote: > Hello > > Does anyone know if this card/chip is supported by FBSD 8.1-RC1? > LSISAS1064E > > This is on an Asus Pike Card for the mainboard Asus Z8PE-D18. > Im also able to buy a different controller I just have to know if its > supported or not. > I've found this in the hardware notes: LSI Logic AS1064 (mpt driver). > But Im still unsure if this is the same or equal chip... > > The card I wanted to buy is also called: Asus PIKE 1064E - I hope > someone > knows. > > cheers > > > > !DSPAM:4ac9dad2651038983666460! > > > _______________________________________________ > freebsd-scsi@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-scsi > To unsubscribe, send any mail to "freebsd-scsi- > unsubscribe@freebsd.org" From paul+fbsd at it.ca Sat Oct 10 21:30:05 2009 From: paul+fbsd at it.ca (Paul Chvostek) Date: Sat Oct 10 21:30:36 2009 Subject: juke box problem - "chio: /dev/ch0: CHIOMOVE: Device not configured" Message-ID: <20091010211452.GA44208@it.ca> Hi there. I have a tape library, but I can't seem to send it commands. It's recognized on the bus: # grep ch0 /var/run/dmesg.boot ch0 at isp0 bus 0 target 0 lun 1 ch0: Removable Changer SCSI-5 device ch0: 400.000MB/s transfers ch0: Command Queueing Enabled ch0: 48 slots, 2 drives, 1 picker, 0 portals And I can read status and voltags and such from it: # chio status -vS | tail -8 slot 42: voltag: <000026L4:0> source: slot 43: voltag: <000020L4:0> source: slot 44: voltag: <000039L4:0> source: slot 45: voltag: <000040L4:0> source: slot 46: voltag: <000043L4:0> source: slot 47: voltag: <000031L4:0> source: drive 0: voltag: <:0> source: <> drive 1: voltag: <000030L4:0> source: But I can't send commands: # chio move slot 43 drive 0 chio: /dev/ch0: CHIOMOVE: Device not configured # tail -6 /var/log/messages Oct 10 17:13:14 nas kernel: (ch0:isp0:0:0:1): MOVE MEDIUM. CDB: a5 0 0 0 4 14 0 1 0 0 0 0 Oct 10 17:13:14 nas kernel: (ch0:isp0:0:0:1): CAM Status: SCSI Status Error Oct 10 17:13:14 nas kernel: (ch0:isp0:0:0:1): SCSI Status: Check Condition Oct 10 17:13:14 nas kernel: (ch0:isp0:0:0:1): ILLEGAL REQUEST asc:25,0 Oct 10 17:13:14 nas kernel: (ch0:isp0:0:0:1): Logical unit not supported Oct 10 17:13:14 nas kernel: (ch0:isp0:0:0:1): Unretryable error What am I missing? Thanks. :-) p -- Paul Chvostek Operations / Abuse / Whatever it.canada, hosting and development http://www.it.ca/ From sean.bruno at dsl-only.net Sat Oct 10 22:16:01 2009 From: sean.bruno at dsl-only.net (Sean Bruno) Date: Sat Oct 10 22:16:07 2009 Subject: juke box problem - "chio: /dev/ch0: CHIOMOVE: Device not configured" In-Reply-To: <20091010211452.GA44208@it.ca> References: <20091010211452.GA44208@it.ca> Message-ID: <1255211359.2521.15.camel@Lappy> On Sat, 2009-10-10 at 17:14 -0400, Paul Chvostek wrote: > 000031L4 Huh ... have you tried moving the tape by "voltag" ?? e.g. move voltag 000020L4 drive 0 Sean From bugmaster at FreeBSD.org Mon Oct 12 11:07:01 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Oct 12 11:09:18 2009 Subject: Current problem reports assigned to freebsd-scsi@FreeBSD.org Message-ID: <200910121107.n9CB70Sh036539@freefall.freebsd.org> 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 kern/138789 scsi [cam] [patch] cd(4) patch for drives/discs failing the o kern/138384 scsi [ips] [patch] NULL pointer dereference in ipsd_dump() o kern/138379 scsi [aic7xxx] [patch] Memory leak in output_listing() in f o kern/138376 scsi [cam] [patch] Memory leak in scsi_low_attach_xs() in f o kern/134488 scsi [mpt] MPT SCSI driver probes max. 8 LUNs per device 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 41 problems total. From mays at win.net Mon Oct 12 19:21:52 2009 From: mays at win.net (Joseph Mays) Date: Mon Oct 12 19:22:00 2009 Subject: aaccli question Message-ID: <00f901ca4b6e$e337ef60$b92118d8@engineering01> Okay, we had a disk go bad on a raid controller. I replaced the disk with an identical disk, expecting it to rebuild. "disk list" aaccli showed the new disk was not initialized. So I initialized it with "disk initialize 03," but still nothing ever happened in the task list and the array is still running in degraded mode. C:ID:L Device Type Blocks Bytes/Block Usage Shared Rate ------ -------------- --------- ----------- ---------------- ------ ---- 0:01:0 Disk 71775284 512 Initialized NO 320 0:02:0 Disk 71775284 512 Initialized NO 320 0:03:0 Disk 71775284 512 Initialized NO 320 0:04:0 Disk 71775284 512 Initialized NO 320 AAC0> container list Executing: container list Num Total Oth Stripe Scsi Partition Label Type Size Ctr Size Usage C:ID:L Offset:Size ----- ------ ------ --- ------ ------- ------ ------------- 0 RAID-5 68.3GB 256KB Open 0:01:0 64.0KB:34.1GB /dev/aacd0 admin4 0:02:0 64.0KB:34.1GB 0:04:0 64.0KB:34.1GB AAC0> task list Executing: task list Controller Tasks TaskId Function Done% Container State Specific1 Specific2 ------ -------- ------- --------- ----- --------- --------- No tasks currently running on controller AAC0> I assume I need to add the disk to the container as a failover, but both iterations I tried, "container set failover 0,3,0" and "container set failover 3) failed saying "incorrect parameters". What should the syntax of this command be? I would try "container set failover 0 3" were I not afraid of breaking the array. I have it backed up, but I really would rather not restore the entire system from backup. Joe From scottl at samsco.org Tue Oct 13 00:16:53 2009 From: scottl at samsco.org (Scott Long) Date: Tue Oct 13 00:17:00 2009 Subject: aaccli question In-Reply-To: <00f901ca4b6e$e337ef60$b92118d8@engineering01> References: <00f901ca4b6e$e337ef60$b92118d8@engineering01> Message-ID: Set the disk as a global spare, the rebuild should happen immediately once you do that. Scott On Oct 12, 2009, at 1:04 PM, Joseph Mays wrote: > Okay, we had a disk go bad on a raid controller. I replaced the disk > with an identical disk, expecting it to rebuild. "disk list" aaccli > showed the new disk was not initialized. So I initialized it with > "disk initialize 03," but still nothing ever happened in the task > list and the array is still running in degraded mode. > > C:ID:L Device Type Blocks Bytes/Block Usage > Shared Rate > ------ -------------- --------- ----------- ---------------- > ------ ---- > 0:01:0 Disk 71775284 512 Initialized > NO 320 > 0:02:0 Disk 71775284 512 Initialized > NO 320 > 0:03:0 Disk 71775284 512 Initialized > NO 320 > 0:04:0 Disk 71775284 512 Initialized > NO 320 > > AAC0> container list > Executing: container list > Num Total Oth Stripe Scsi Partition > Label Type Size Ctr Size Usage C:ID:L Offset:Size > ----- ------ ------ --- ------ ------- ------ ------------- > 0 RAID-5 68.3GB 256KB Open 0:01:0 64.0KB:34.1GB > /dev/aacd0 admin4 0:02:0 64.0KB:34.1GB > 0:04:0 64.0KB:34.1GB > > > AAC0> task list > Executing: task list > > Controller Tasks > > TaskId Function Done% Container State Specific1 Specific2 > ------ -------- ------- --------- ----- --------- --------- > > No tasks currently running on controller > > AAC0> > > I assume I need to add the disk to the container as a failover, but > both iterations I tried, "container set failover 0,3,0" and > "container set failover 3) failed saying "incorrect parameters". > What should the syntax of this command be? I would try "container > set failover 0 3" were I not afraid of breaking the array. I have it > backed up, but I really would rather not restore the entire system > from backup. > > Joe > _______________________________________________ > freebsd-scsi@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-scsi > To unsubscribe, send any mail to "freebsd-scsi- > unsubscribe@freebsd.org" From mays at win.net Tue Oct 13 16:09:39 2009 From: mays at win.net (Joseph Mays) Date: Tue Oct 13 16:09:45 2009 Subject: aaccli question References: <00f901ca4b6e$e337ef60$b92118d8@engineering01> Message-ID: <011a01ca4c1f$8a98d750$b92118d8@engineering01> > Set the disk as a global spare, the rebuild should happen immediately > once you do that. Tried that now, but no luck. Perhaps I did it wrong. Tried setting the disk specifically as a failover for the container, too. AAC0> container set global_failover 03 Executing: container set global_failover (ID=3) AAC0> disk list Executing: disk list C:ID:L Device Type Blocks Bytes/Block Usage Shared Rate ------ -------------- --------- ----------- ---------------- ------ ---- 0:01:0 Disk 71775284 512 Initialized NO 320 0:02:0 Disk 71775284 512 Initialized NO 320 0:03:0 Disk 71775284 512 Initialized NO 320 0:04:0 Disk 71775284 512 Initialized NO 320 AAC0> container list Executing: container list Num Total Oth Stripe Scsi Partition Label Type Size Ctr Size Usage C:ID:L Offset:Size ----- ------ ------ --- ------ ------- ------ ------------- 0 RAID-5 68.3GB 256KB Open 0:01:0 64.0KB:34.1GB /dev/aacd0 admin4 0:02:0 64.0KB:34.1GB 0:04:0 64.0KB:34.1GB AAC0> task list Executing: task list Controller Tasks TaskId Function Done% Container State Specific1 Specific2 ------ -------- ------- --------- ----- --------- --------- No tasks currently running on controller AAC0> container set failover 0 03 Executing: container set failover 0 (ID=3) AAC0> task list Executing: task list Controller Tasks TaskId Function Done% Container State Specific1 Specific2 ------ -------- ------- --------- ----- --------- --------- No tasks currently running on controller From paul+fbsd at it.ca Wed Oct 14 06:55:35 2009 From: paul+fbsd at it.ca (Paul Chvostek) Date: Wed Oct 14 06:57:12 2009 Subject: juke box problem - "chio: /dev/ch0: CHIOMOVE: Device not configured" In-Reply-To: <1255211359.2521.15.camel@Lappy> References: <20091010211452.GA44208@it.ca> <1255211359.2521.15.camel@Lappy> Message-ID: <20091014065309.GA95320@it.ca> Hi Sean, On Sat, Oct 10, 2009 at 02:49:19PM -0700, Sean Bruno wrote: > > On Sat, 2009-10-10 at 17:14 -0400, Paul Chvostek wrote: > > 000031L4 > > Huh ... have you tried moving the tape by "voltag" ?? > > e.g. > > move voltag 000020L4 drive 0 I have now, but with the same result: # chio status -v | grep drive drive 0: voltag: <000039L4:0> drive 1: voltag: <000030L4:0> # # chio move voltag 000030L4 slot 44 chio: /dev/ch0: CHIOMOVE: Device not configured # # tail -6 /var/log/messages Oct 14 02:48:16 nas kernel: (ch0:isp0:0:0:1): MOVE MEDIUM. CDB: a5 0 0 0 0 2 4 15 0 0 0 0 Oct 14 02:48:16 nas kernel: (ch0:isp0:0:0:1): CAM Status: SCSI Status Error Oct 14 02:48:16 nas kernel: (ch0:isp0:0:0:1): SCSI Status: Check Condition Oct 14 02:48:16 nas kernel: (ch0:isp0:0:0:1): ILLEGAL REQUEST asc:25,0 Oct 14 02:48:16 nas kernel: (ch0:isp0:0:0:1): Logical unit not supported Oct 14 02:48:16 nas kernel: (ch0:isp0:0:0:1): Unretryable error Is there a way to determine whether this problem is with the device or with FreeBSD? Note that I *can* move the tapes around using the juke box's web gui, so it's not a physical problem. For reference: # grep 'at isp0' /var/run/dmesg.boot sa0 at isp0 bus 0 target 0 lun 0 ch0 at isp0 bus 0 target 0 lun 1 Thanks muchly. -- Paul Chvostek Operations / Abuse / Whatever it.canada, hosting and development http://www.it.ca/ From ken at kdm.org Wed Oct 14 15:01:22 2009 From: ken at kdm.org (Kenneth D. Merry) Date: Wed Oct 14 15:01:30 2009 Subject: juke box problem - "chio: /dev/ch0: CHIOMOVE: Device not configured" In-Reply-To: <20091014065309.GA95320@it.ca> References: <20091010211452.GA44208@it.ca> <1255211359.2521.15.camel@Lappy> <20091014065309.GA95320@it.ca> Message-ID: <20091014150111.GA54658@nargothrond.kdm.org> On Wed, Oct 14, 2009 at 02:53:09 -0400, Paul Chvostek wrote: > Hi Sean, > > On Sat, Oct 10, 2009 at 02:49:19PM -0700, Sean Bruno wrote: > > > > On Sat, 2009-10-10 at 17:14 -0400, Paul Chvostek wrote: > > > 000031L4 > > > > Huh ... have you tried moving the tape by "voltag" ?? > > > > e.g. > > > > move voltag 000020L4 drive 0 > > I have now, but with the same result: > > # chio status -v | grep drive > drive 0: voltag: <000039L4:0> > drive 1: voltag: <000030L4:0> > # > # chio move voltag 000030L4 slot 44 > chio: /dev/ch0: CHIOMOVE: Device not configured > # > # tail -6 /var/log/messages > Oct 14 02:48:16 nas kernel: (ch0:isp0:0:0:1): MOVE MEDIUM. CDB: a5 0 0 0 0 2 4 15 0 0 0 0 > Oct 14 02:48:16 nas kernel: (ch0:isp0:0:0:1): CAM Status: SCSI Status Error > Oct 14 02:48:16 nas kernel: (ch0:isp0:0:0:1): SCSI Status: Check Condition > Oct 14 02:48:16 nas kernel: (ch0:isp0:0:0:1): ILLEGAL REQUEST asc:25,0 > Oct 14 02:48:16 nas kernel: (ch0:isp0:0:0:1): Logical unit not supported > Oct 14 02:48:16 nas kernel: (ch0:isp0:0:0:1): Unretryable error Typically a "Logical unit not supported" error means that that particular LUN (in this case LUN 1) isn't supported/doesn't exist. (Which would be strange, given that it does probe.) Could the changer be in autoloader mode? That's the only thing I can think of that would cause an error like that. The only other explanation is that they're misusing that error to say that it doesn't like the particular move you're trying to do. > Is there a way to determine whether this problem is with the device or > with FreeBSD? Note that I *can* move the tapes around using the juke > box's web gui, so it's not a physical problem. > > For reference: > > # grep 'at isp0' /var/run/dmesg.boot > sa0 at isp0 bus 0 target 0 lun 0 > ch0 at isp0 bus 0 target 0 lun 1 Ken -- Kenneth Merry ken@kdm.org From pluknet at gmail.com Thu Oct 15 10:16:24 2009 From: pluknet at gmail.com (pluknet) Date: Thu Oct 15 10:16:31 2009 Subject: mfi(4) endless loop kernel output on attach Message-ID: Hi. This is 7.2-R. Seen on IBM x3650M2. During the boot I get those endless looping kernel messages while on mfi(4) attach phase. It's getting more odd since 7.2 booted and worked fine on exactly this server model months ago (on different box though).. Any hints? mfi0: 5428 (boot + 3s/0x0020/info) - Firmware initialization started (PCI ID 0060/1000/0364/1014) mfi0: 5429 (boot + 3s/0x0020/info) - Firmware version 1.40.62-0691 mfi0: 5430 (boot + 3s/0x0020/info) - Firmware initialization started (PCI ID 0060/1000/0364/1014) mfi0: 5431 (boot + 3s/0x0020/info) - Firmware version 1.40.62-0691 mfi0: 5432 (boot + 64s/0x0008/info) - Battery Present mfi0: 5433 (boot + 64s/0x0020/info) - BBU FRU is mfi0: 5434 (boot + 64s/0x0020/info) - Board Revision mfi0: 5435 (boot + 89s/0x0002/info) - Inserted: PD 08(e0xff/s8) mfi0: 5436 (boot + 89s/0x0002/info) - Inserted: PD 08(e0xff/s8) Info: enclPd=ffff, scsiType=0, portMap=00, sasAddr=5000c500138d46b5,0000000000000000 mfi0: 5437 (boot + 89s/0x0002/info) - PD 08(e0xff/s8) FRU is 42D0422 mfi0: 5438 (boot + 89s/0x0002/info) - Inserted: PD 09(e0xff/s9) mfi0: 5439 (boot + 89s/0x0002/info) - Inserted: PD 09(e0xff/s9) Info: enclPd=ffff, scsiType=0, portMap=01, sasAddr=5000c500138d842d,0000000000000000 mfi0: 5440 (boot + 89s/0x0002/info) - PD 09(e0xff/s9) FRU is 42D0422 mfi0: 5441 (boot + 89s/0x0002/info) - Inserted: PD 0a(e0xff/s10) mfi0: 5442 (boot + 89s/0x0002/info) - Inserted: PD 0a(e0xff/s10) Info: enclPd=ffff, scsiType=0, portMap=04, sasAddr=5000c500138d7d75,0000000000000000 mfi0: 5443 (boot + 89s/0x0002/info) - PD 0a(e0xff/s10) FRU is 42D0422 mfi0: 5444 (boot + 89s/0x0002/info) - Inserted: PD 0b(e0xff/s11) mfi0: 5445 (boot + 89s/0x0002/info) - Inserted: PD 0b(e0xff/s11) Info: enclPd=ffff, scsiType=0, portMap=05, sasAddr=5000c500138d7835,0000000000000000 mfi0: 5446 (boot + 89s/0x0002/info) - PD 0b(e0xff/s11) FRU is 42D0422 mfi0: 5447 (boot + 89s/0x0002/info) - Inserted: PD 0c(e0xff/s12) mfi0: 5448 (boot + 89s/0x0002/info) - Inserted: PD 0c(e0xff/s12) Info: enclPd=ffff, scsiType=0, portMap=02, sasAddr=5000c500138d60b5,0000000000000000 mfi0: 5449 (boot + 89s/0x0002/info) - PD 0c(e0xff/s12) FRU is 42D0422 mfi0: 5450 (boot + 89s/0x0002/info) - Inserted: PD 0d(e0xff/s13) mfi0: 5451 (boot + 89s/0x0002/info) - Inserted: PD 0d(e0xff/s13) Info: enclPd=ffff, scsiType=0, portMap=03, sasAddr=5000c500138d7bdd,0000000000000000 mfi0: 5452 (boot + 89s/0x0002/info) - PD 0d(e0xff/s13) FRU is 42D0422 mfi0: 5453 (boot + 89s/0x0002/info) - Inserted: PD 0e(e0xff/s14) mfi0: 5454 (boot + 89s/0x0002/info) - Inserted: PD 0e(e0xff/s14) Info: enclPd=ffff, scsiType=0, portMap=06, sasAddr=5000c500138d6839,0000000000000000 mfi0: 5455 (boot + 89s/0x0002/info) - PD 0e(e0xff/s14) FRU is 42D0422 mfi0: 5456 (boot + 89s/0x0002/info) - Inserted: PD 0f(e0xff/s15) mfi0: 5457 (boot + 89s/0x0002/info) - Inserted: PD 0f(e0xff/s15) Info: enclPd=ffff, scsiType=0, portMap=07, sasAddr=5000c500138d5e8d,0000000000000000 mfi0: 5458 (boot + 89s/0x0002/info) - PD 0f(e0xff/s15) FRU is 42D0422 mfi0: 5459 (boot + 144s/0x0008/info) - Battery temperature is normal mfi0: 5460 (308390540s/0x0020/info) - Time established as 10/09/09 8:02:20; (256 seconds since power on) mfi0: 5461 (boot + 3s/0x0020/info) - Firmware initialization started (PCI ID 0060/1000/0364/1014) mfi0: 5462 (boot + 3s/0x0020/info) - Firmware version 1.40.62-0691 mfi0: 5463 (boot + 3s/0x0020/info) - Firmware initialization started (PCI ID 0060/1000/0364/1014) mfi0: 5464 (boot + 3s/0x0020/info) - Firmware version 1.40.62-0691 mfi0: 5465 (boot + 64s/0x0008/info) - Battery Present mfi0: 5466 (boot + 64s/0x0020/info) - BBU FRU is mfi0: 5467 (boot + 64s/0x0020/info) - Board Revision mfi0: 5468 (boot + 89s/0x0002/info) - Inserted: PD 08(e0xff/s8) mfi0: 5469 (boot + 89s/0x0002/info) - Inserted: PD 08(e0xff/s8) Info: enclPd=ffff, scsiType=0, portMap=00, sasAddr=5000c500138d46b5,0000000000000000 mfi0: 5470 (boot + 89s/0x0002/info) - PD 08(e0xff/s8) FRU is 42D0422 mfi0: 5471 (boot + 89s/0x0002/info) - Inserted: PD 09(e0xff/s9) mfi0: 5472 (boot + 89s/0x0002/info) - Inserted: PD 09(e0xff/s9) Info: enclPd=ffff, scsiType=0, portMap=01, sasAddr=5000c500138d842d,0000000000000000 mfi0: 5473 (boot + 89s/0x0002/info) - PD 09(e0xff/s9) FRU is 42D0422 mfi0: 5474 (boot + 89s/0x0002/info) - Inserted: PD 0a(e0xff/s10) mfi0: 5475 (boot + 89s/0x0002/info) - Inserted: PD 0a(e0xff/s10) Info: enclPd=ffff, scsiType=0, portMap=04, sasAddr=5000c500138d7d75,0000000000000000 mfi0: 5476 (boot + 89s/0x0002/info) - PD 0a(e0xff/s10) FRU is 42D0422 mfi0: 5477 (boot + 89s/0x0002/info) - Inserted: PD 0b(e0xff/s11) mfi0: 5478 (boot + 89s/0x0002/info) - Inserted: PD 0b(e0xff/s11) Info: enclPd=ffff, scsiType=0, portMap=05, sasAddr=5000c500138d7835,0000000000000000 mfi0: 5479 (boot + 89s/0x0002/info) - PD 0b(e0xff/s11) FRU is 42D0422 mfi0: 5480 (boot + 89s/0x0002/info) - Inserted: PD 0c(e0xff/s12) mfi0: 5481 (boot + 89s/0x0002/info) - Inserted: PD 0c(e0xff/s12) Info: enclPd=ffff, scsiType=0, portMap=02, sasAddr=5000c500138d60b5,0000000000000000 mfi0: 5482 (boot + 89s/0x0002/info) - PD 0c(e0xff/s12) FRU is 42D0422 mfi0: 5483 (boot + 89s/0x0002/info) - Inserted: PD 0d(e0xff/s13) mfi0: 5484 (boot + 89s/0x0002/info) - Inserted: PD 0d(e0xff/s13) Info: enclPd=ffff, scsiType=0, portMap=03, sasAddr=5000c500138d7bdd,0000000000000000 mfi0: 5485 (boot + 89s/0x0002/info) - PD 0d(e0xff/s13) FRU is 42D0422 mfi0: 5486 (boot + 89s/0x0002/info) - Inserted: PD 0e(e0xff/s14) mfi0: 5487 (boot + 89s/0x0002/info) - Inserted: PD 0e(e0xff/s14) Info: enclPd=ffff, scsiType=0, portMap=06, sasAddr=5000c500138d6839,0000000000000000 mfi0: 5488 (boot + 89s/0x0002/info) - PD 0e(e0xff/s14) FRU is 42D0422 mfi0: 5489 (boot + 89s/0x0002/info) - Inserted: PD 0f(e0xff/s15) mfi0: 5490 (boot + 89s/0x0002/info) - Inserted: PD 0f(e0xff/s15) Info: enclPd=ffff, scsiType=0, portMap=07, sasAddr=5000c500138d5e8d,0000000000000000 mfi0: 5491 (boot + 89s/0x0002/info) - PD 0f(e0xff/s15) FRU is 42D0422 mfi0: 5492 (boot + 144s/0x0008/info) - Battery temperature is normal mfi0: 5493 (308391152s/0x0020/info) - Time established as 10/09/09 8:12:32; (256 seconds since power on) mfi0: 5494 (boot + 3s/0x0020/info) - Firmware initialization started (PCI ID 0060/1000/0364/1014) mfi0: 5495 (boot + 3s/0x0020/info) - Firmware version 1.40.62-0691 mfi0: 5496 (boot + 3s/0x0020/info) - Firmware initialization started (PCI ID 0060/1000/0364/1014) mfi0: 5497 (boot + 3s/0x0020/info) - Firmware version 1.40.62-0691 mfi0: 5498 (boot + 64s/0x0008/info) - Battery Present mfi0: 5499 (boot + 64s/0x0020/info) - BBU FRU is mfi0: 5500 (boot + 64s/0x0020/info) - Board Revision mfi0: 5501 (boot + 89s/0x0002/info) - Inserted: PD 08(e0xff/s8) mfi0: 5502 (boot + 89s/0x0002/info) - Inserted: PD 08(e0xff/s8) Info: enclPd=ffff, scsiType=0, portMap=00, sasAddr=5000c500138d46b5,0000000000000000 mfi0: 5503 (boot + 89s/0x0002/info) - PD 08(e0xff/s8) FRU is 42D0422 mfi0: 5504 (boot + 89s/0x0002/info) - Inserted: PD 09(e0xff/s9) mfi0: 5505 (boot + 89s/0x0002/info) - Inserted: PD 09(e0xff/s9) Info: enclPd=ffff, scsiType=0, portMap=01, sasAddr=5000c500138d842d,0000000000000000 mfi0: 5506 (boot + 89s/0x0002/info) - PD 09(e0xff/s9) FRU is 42D0422 mfi0: 5507 (boot + 89s/0x0002/info) - Inserted: PD 0a(e0xff/s10) mfi0: 5508 (boot + 89s/0x0002/info) - Inserted: PD 0a(e0xff/s10) Info: enclPd=ffff, scsiType=0, portMap=04, sasAddr=5000c500138d7d75,0000000000000000 mfi0: 5509 (boot + 89s/0x0002/info) - PD 0a(e0xff/s10) FRU is 42D0422 mfi0: 5510 (boot + 89s/0x0002/info) - Inserted: PD 0b(e0xff/s11) mfi0: 5511 (boot + 89s/0x0002/info) - Inserted: PD 0b(e0xff/s11) Info: enclPd=ffff, scsiType=0, portMap=05, sasAddr=5000c500138d7835,0000000000000000 mfi0: 5512 (boot + 89s/0x0002/info) - PD 0b(e0xff/s11) FRU is 42D0422 mfi0: 5513 (boot + 89s/0x0002/info) - Inserted: PD 0c(e0xff/s12) mfi0: 5514 (boot + 89s/0x0002/info) - Inserted: PD 0c(e0xff/s12) Info: enclPd=ffff, scsiType=0, portMap=02, sasAddr=5000c500138d60b5,0000000000000000 mfi0: 5515 (boot + 89s/0x0002/info) - PD 0c(e0xff/s12) FRU is 42D0422 mfi0: 5516 (boot + 89s/0x0002/info) - Inserted: PD 0d(e0xff/s13) mfi0: 5517 (boot + 89s/0x0002/info) - Inserted: PD 0d(e0xff/s13) Info: enclPd=ffff, scsiType=0, portMap=03, sasAddr=5000c500138d7bdd,0000000000000000 mfi0: 5518 (boot + 89s/0x0002/info) - PD 0d(e0xff/s13) FRU is 42D0422 mfi0: 5519 (boot + 89s/0x0002/info) - Inserted: PD 0e(e0xff/s14) mfi0: 5520 (boot + 89s/0x0002/info) - Inserted: PD 0e(e0xff/s14) Info: enclPd=ffff, scsiType=0, portMap=06, sasAddr=5000c500138d6839,0000000000000000 mfi0: 5521 (boot + 89s/0x0002/info) - PD 0e(e0xff/s14) FRU is 42D0422 mfi0: 5522 (boot + 89s/0x0002/info) - Inserted: PD 0f(e0xff/s15) mfi0: 5523 (boot + 89s/0x0002/info) - Inserted: PD 0f(e0xff/s15) Info: enclPd=ffff, scsiType=0, portMap=07, sasAddr=5000c500138d5e8d,0000000000000000 mfi0: 5524 (boot + 89s/0x0002/info) - PD 0f(e0xff/s15) FRU is 42D0422 mfi0: 5525 (boot + 144s/0x0008/info) - Battery temperature is normal mfi0: 5526 (308391765s/0x0020/info) - Time established as 10/09/09 8:22:45; (257 seconds since power on) mfi0: 5527 (boot + 3s/0x0020/info) - Firmware initialization started (PCI ID 0060/1000/0364/1014) mfi0: 5528 (boot + 3s/0x0020/info) - Firmware version 1.40.62-0691 mfi0: 5529 (boot + 3s/0x0020/info) - Firmware initialization started (PCI ID 0060/1000/0364/1014) mfi0: 5530 (boot + 3s/0x0020/info) - Firmware version 1.40.62-0691 mfi0: 5531 (boot + 64s/0x0008/info) - Battery Present mfi0: 5532 (boot + 64s/0x0020/info) - BBU FRU is mfi0: 5533 (boot + 64s/0x0020/info) - Board Revision mfi0: 5534 (boot + 89s/0x0002/info) - Inserted: PD 08(e0xff/s8) mfi0: 5535 (boot + 89s/0x0002/info) - Inserted: PD 08(e0xff/s8) Info: enclPd=ffff, scsiType=0, portMap=00, sasAddr=5000c500138d46b5,0000000000000000 mfi0: 5536 (boot + 89s/0x0002/info) - PD 08(e0xff/s8) FRU is 42D0422 mfi0: 5537 (boot + 89s/0x0002/info) - Inserted: PD 09(e0xff/s9) mfi0: 5538 (boot + 89s/0x0002/info) - Inserted: PD 09(e0xff/s9) Info: enclPd=ffff, scsiType=0, portMap=01, sasAddr=5000c500138d842d,0000000000000000 mfi0: 5539 (boot + 89s/0x0002/info) - PD 09(e0xff/s9) FRU is 42D0422 mfi0: 5540 (boot + 89s/0x0002/info) - Inserted: PD 0a(e0xff/s10) mfi0: 5541 (boot + 89s/0x0002/info) - Inserted: PD 0a(e0xff/s10) Info: enclPd=ffff, scsiType=0, portMap=04, sasAddr=5000c500138d7d75,0000000000000000 mfi0: 5542 (boot + 89s/0x0002/info) - PD 0a(e0xff/s10) FRU is 42D0422 mfi0: 5543 (boot + 89s/0x0002/info) - Inserted: PD 0b(e0xff/s11) mfi0: 5544 (boot + 89s/0x0002/info) - Inserted: PD 0b(e0xff/s11) Info: enclPd=ffff, scsiType=0, portMap=05, sasAddr=5000c500138d7835,0000000000000000 mfi0: 5545 (boot + 89s/0x0002/info) - PD 0b(e0xff/s11) FRU is 42D0422 mfi0: 5546 (boot + 89s/0x0002/info) - Inserted: PD 0c(e0xff/s12) mfi0: 5547 (boot + 89s/0x0002/info) - Inserted: PD 0c(e0xff/s12) Info: enclPd=ffff, scsiType=0, portMap=02, sasAddr=5000c500138d60b5,0000000000000000 mfi0: 5548 (boot + 89s/0x0002/info) - PD 0c(e0xff/s12) FRU is 42D0422 mfi0: 5549 (boot + 89s/0x0002/info) - Inserted: PD 0d(e0xff/s13) mfi0: 5550 (boot + 89s/0x0002/info) - Inserted: PD 0d(e0xff/s13) Info: enclPd=ffff, scsiType=0, portMap=03, sasAddr=5000c500138d7bdd,0000000000000000 mfi0: 5551 (boot + 89s/0x0002/info) - PD 0d(e0xff/s13) FRU is 42D0422 mfi0: 5552 (boot + 89s/0x0002/info) - Inserted: PD 0e(e0xff/s14) mfi0: 5553 (boot + 89s/0x0002/info) - Inserted: PD 0e(e0xff/s14) Info: enclPd=ffff, scsiType=0, portMap=06, sasAddr=5000c500138d6839,0000000000000000 mfi0: 5554 (boot + 89s/0x0002/info) - PD 0e(e0xff/s14) FRU is 42D0422 mfi0: 5555 (boot + 89s/0x0002/info) - Inserted: PD 0f(e0xff/s15) mfi0: 5556 (boot + 89s/0x0002/info) - Inserted: PD 0f(e0xff/s15) Info: enclPd=ffff, scsiType=0, portMap=07, sasAddr=5000c500138d5e8d,0000000000000000 mfi0: 5557 (boot + 89s/0x0002/info) - PD 0f(e0xff/s15) FRU is 42D0422 mfi0: 5558 (boot + 144s/0x0008/info) - Battery temperature is normal mfi0: 5559 (308392379s/0x0020/info) - Time established as 10/09/09 8:32:59; (258 seconds since power on) mfi0: 5560 (boot + 3s/0x0020/info) - Firmware initialization started (PCI ID 0060/1000/0364/1014) mfi0: 5561 (boot + 3s/0x0020/info) - Firmware version 1.40.62-0691 mfi0: 5562 (boot + 3s/0x0020/info) - Firmware initialization started (PCI ID 006 0/1000/0364/1014) mfi0: 5563 (boot + 3s/0x0020/info) - Firmware version 1.40.62-0691 mfi0: 5564 (boot + 64s/0x0008/info) - Battery Present mfi0: 5565 (boot + 64s/0x0020/info) - BBU FRU is mfi0: 5566 (boot + 64s/0x0020/info) - Board Revision mfi0: 5567 (boot + 89s/0x0002/info) - Inserted: PD 08(e0xff/s8) mfi0: 5568 (boot + 89s/0x0002/info) - Inserted: PD 08(e0xff/s8) Info: enclPd=ffff, scsiType=0, portMap=00, sasAddr=5000c500138d46b5,0000000000000000 mfi0: 5569 (boot + 89s/0x0002/info) - PD 08(e0xff/s8) FRU is 42D0422 mfi0: 5570 (boot + 89s/0x0002/info) - Inserted: PD 09(e0xff/s9) mfi0: 5571 (boot + 89s/0x0002/info) - Inserted: PD 09(e0xff/s9) Info: enclPd=ffff, scsiType=0, portMap=01, sasAddr=5000c500138d842d,0000000000000000 mfi0: 5572 (boot + 89s/0x0002/info) - PD 09(e0xff/s9) FRU is 42D0422 mfi0: 5573 (boot + 89s/0x0002/info) - Inserted: PD 0a(e0xff/s10) mfi0: 5574 (boot + 89s/0x0002/info) - Inserted: PD 0a(e0xff/s10) Info: enclPd=ffff, scsiType=0, portMap=04, sasAddr=5000c500138d7d75,0000000000000000 mfi0: 5575 (boot + 89s/0x0002/info) - PD 0a(e0xff/s10) FRU is 42D0422 mfi0: 5576 (boot + 89s/0x0002/info) - Inserted: PD 0b(e0xff/s11) mfi0: 5577 (boot + 89s/0x0002/info) - Inserted: PD 0b(e0xff/s11) Info: enclPd=ffff, scsiType=0, portMap=05, sasAddr=5000c500138d7835,0000000000000000 mfi0: 5578 (boot + 89s/0x0002/info) - PD 0b(e0xff/s11) FRU is 42D0422 mfi0: 5579 (boot + 89s/0x0002/info) - Inserted: PD 0c(e0xff/s12) mfi0: 5580 (boot + 89s/0x0002/info) - Inserted: PD 0c(e0xff/s12) Info: enclPd=ffff, scsiType=0, portMap=02, sasAddr=5000c500138d60b5,0000000000000000 mfi0: 5581 (boot + 89s/0x0002/info) - PD 0c(e0xff/s12) FRU is 42D0422 mfi0: 5582 (boot + 89s/0x0002/info) - Inserted: PD 0d(e0xff/s13) mfi0: 5583 (boot + 89s/0x0002/info) - Inserted: PD 0d(e0xff/s13) Info: enclPd=ffff, scsiType=0, portMap=03, sasAddr=5000c500138d7bdd,0000000000000000 mfi0: 5584 (boot + 89s/0x0002/info) - PD 0d(e0xff/s13) FRU is 42D0422 mfi0: 5585 (boot + 89s/0x0002/info) - Inserted: PD 0e(e0xff/s14) mfi0: 5586 (boot + 89s/0x0002/info) - Inserted: PD 0e(e0xff/s14) Info: enclPd=ffff, scsiType=0, portMap=06, sasAddr=5000c500138d6839,0000000000000000 mfi0: 5587 (boot + 89s/0x0002/info) - PD 0e(e0xff/s14) FRU is 42D0422 mfi0: 5588 (boot + 89s/0x0002/info) - Inserted: PD 0f(e0xff/s15) mfi0: 5589 (boot + 89s/0x0002/info) - Inserted: PD 0f(e0xff/s15) Info: enclPd=ffff, scsiType=0, portMap=07, sasAddr=5000c500138d5e8d,0000000000000000 mfi0: 5590 (boot + 89s/0x0002/info) - PD 0f(e0xff/s15) FRU is 42D0422 mfi0: 5591 (boot + 144s/0x0008/info) - Battery temperature is normal mfi0: 5592 (308392995s/0x0020/info) - Time established as 10/09/09 8:43:15; (259 seconds since power on) mfi0: 5593 (boot + 3s/0x0020/info) - Firmware initialization started (PCI ID 0060/1000/0364/1014) mfi0: 5594 (boot + 3s/0x0020/info) - Firmware version 1.40.62-0691 mfi0: 5595 (boot + 3s/0x0020/info) - Firmware initialization started (PCI ID 0060/1000/0364/1014) mfi0: 5596 (boot + 3s/0x0020/info) - Firmware version 1.40.62-0691 mfi0: 5597 (boot + 64s/0x0008/info) - Battery Present mfi0: 5598 (boot + 64s/0x0020/info) - BBU FRU is mfi0: 5599 (boot + 64s/0x0020/info) - Board Revision mfi0: 5600 (boot + 89s/0x0002/info) - Inserted: PD 08(e0xff/s8) mfi0: 5601 (boot + 89s/0x0002/info) - Inserted: PD 08(e0xff/s8) Info: enclPd=ffff, scsiType=0, portMap=00, sasAddr=5000c500138d46b5,0000000000000000 mfi0: 5602 (boot + 89s/0x0002/info) - PD 08(e0xff/s8) FRU is 42D0422 mfi0: 5603 (boot + 89s/0x0002/info) - Inserted: PD 09(e0xff/s9) mfi0: 5604 (boot + 89s/0x0002/info) - Inserted: PD 09(e0xff/s9) Info: enclPd=ffff, scsiType=0, portMap=01, sasAddr=5000c500138d842d,0000000000000000 mfi0: 5605 (boot + 89s/0x0002/info) - PD 09(e0xff/s9) FRU is 42D0422 mfi0: 5606 (boot + 89s/0x0002/info) - Inserted: PD 0a(e0xff/s10) mfi0: 5607 (boot + 89s/0x0002/info) - Inserted: PD 0a(e0xff/s10) Info: enclPd=ffff, scsiType=0, portMap=04, sasAddr=5000c500138d7d75,0000000000000000 mfi0: 5608 (boot + 89s/0x0002/info) - PD 0a(e0xff/s10) FRU is 42D0422 mfi0: 5609 (boot + 89s/0x0002/info) - Inserted: PD 0b(e0xff/s11) mfi0: 5610 (boot + 89s/0x0002/info) - Inserted: PD 0b(e0xff/s11) Info: enclPd=ffff, scsiType=0, portMap=05, sasAddr=5000c500138d7835,0000000000000000 mfi0: 5611 (boot + 89s/0x0002/info) - PD 0b(e0xff/s11) FRU is 42D0422 mfi0: 5612 (boot + 89s/0x0002/info) - Inserted: PD 0c(e0xff/s12) mfi0: 5613 (boot + 89s/0x0002/info) - Inserted: PD 0c(e0xff/s12) Info: enclPd=ffff, scsiType=0, portMap=02, sasAddr=5000c500138d60b5,0000000000000000 mfi0: 5614 (boot + 89s/0x0002/info) - PD 0c(e0xff/s12) FRU is 42D0422 mfi0: 5615 (boot + 89s/0x0002/info) - Inserted: PD 0d(e0xff/s13) mfi0: 5616 (boot + 89s/0x0002/info) - Inserted: PD 0d(e0xff/s13) Info: enclPd=ffff, scsiType=0, portMap=03, sasAddr=5000c500138d7bdd,0000000000000000 mfi0: 5617 (boot + 89s/0x0002/info) - PD 0d(e0xff/s13) FRU is 42D0422 mfi0: 5618 (boot + 89s/0x0002/info) - Inserted: PD 0e(e0xff/s14) mfi0: 5619 (boot + 89s/0x0002/info) - Inserted: PD 0e(e0xff/s14) Info: enclPd=ffff, scsiType=0, portMap=06, sasAddr=5000c500138d6839,0000000000000000 mfi0: 5620 (boot + 89s/0x0002/info) - PD 0e(e0xff/s14) FRU is 42D0422 mfi0: 5621 (boot + 89s/0x0002/info) - Inserted: PD 0f(e0xff/s15) mfi0: 5622 (boot + 89s/0x0002/info) - Inserted: PD 0f(e0xff/s15) Info: enclPd=ffff, scsiType=0, portMap=07, sasAddr=5000c500138d5e8d,0000000000000000 mfi0: 5623 (boot + 89s/0x0002/info) - PD 0f(e0xff/s15) FRU is 42D0422 mfi0: 5624 (boot + 144s/0x0008/info) - Battery temperature is normal mfi0: 5625 (308393612s/0x0020/info) - Time established as 10/09/09 8:53:32; (261 seconds since power on) mfi0: 5626 (boot + 3s/0x0020/info) - Firmware initialization started (PCI ID 0060/1000/0364/1014) mfi0: 5627 (boot + 3s/0x0020/info) - Firmware version 1.40.62-0691 mfi0: 5628 (boot + 3s/0x0020/info) - Firmware initialization started (PCI ID 0060/1000/0364/1014) mfi0: 5629 (boot + 3s/0x0020/info) - Firmware version 1.40.62-0691 mfi0: 5630 (boot + 64s/0x0008/info) - Battery Present mfi0: 5631 (boot + 64s/0x0020/info) - BBU FRU is mfi0: 5632 (boot + 64s/0x0020/info) - Board Revision mfi0: 5633 (boot + 89s/0x0002/info) - Inserted: PD 08(e0xff/s8) mfi0: 5634 (boot + 89s/0x0002/info) - Inserted: PD 08(e0xff/s8) Info: enclPd=ffff, scsiType=0, portMap=00, sasAddr=5000c500138d46b5,0000000000000000 mfi0: 5635 (boot + 89s/0x0002/info) - PD 08(e0xff/s8) FRU is 42D0422 mfi0: 5636 (boot + 89s/0x0002/info) - Inserted: PD 09(e0xff/s9) mfi0: 5637 (boot + 89s/0x0002/info) - Inserted: PD 09(e0xff/s9) Info: enclPd=ffff, scsiType=0, portMap=01, sasAddr=5000c500138d842d,0000000000000000 mfi0: 5638 (boot + 89s/0x0002/info) - PD 09(e0xff/s9) FRU is 42D0422 mfi0: 5639 (boot + 89s/0x0002/info) - Inserted: PD 0a(e0xff/s10) mfi0: 5640 (boot + 89s/0x0002/info) - Inserted: PD 0a(e0xff/s10) Info: enclPd=ffff, scsiType=0, portMap=04, sasAddr=5000c500138d7d75,0000000000000000 mfi0: 5641 (boot + 89s/0x0002/info) - PD 0a(e0xff/s10) FRU is 42D0422 mfi0: 5642 (boot + 89s/0x0002/info) - Inserted: PD 0b(e0xff/s11) mfi0: 5643 (boot + 89s/0x0002/info) - Inserted: PD 0b(e0xff/s11) Info: enclPd=ffff, scsiType=0, portMap=05, sasAddr=5000c500138d7835,0000000000000000 mfi0: 5644 (boot + 89s/0x0002/info) - PD 0b(e0xff/s11) FRU is 42D0422 mfi0: 5645 (boot + 89s/0x0002/info) - Inserted: PD 0c(e0xff/s12) mfi0: 5646 (boot + 89s/0x0002/info) - Inserted: PD 0c(e0xff/s12) Info: enclPd=ffff, scsiType=0, portMap=02, sasAddr=5000c500138d60b5,0000000000000000 mfi0: 5647 (boot + 89s/0x0002/info) - PD 0c(e0xff/s12) FRU is 42D0422 mfi0: 5648 (boot + 89s/0x0002/info) - Inserted: PD 0d(e0xff/s13) mfi0: 5649 (boot + 89s/0x0002/info) - Inserted: PD 0d(e0xff/s13) Info: enclPd=ffff, scsiType=0, portMap=03, sasAddr=5000c500138d7bdd,0000000000000000 mfi0: 5650 (boot + 89s/0x0002/info) - PD 0d(e0xff/s13) FRU is 42D0422 mfi0: 5651 (boot + 89s/0x0002/info) - Inserted: PD 0e(e0xff/s14) mfi0: 5652 (boot + 89s/0x0002/info) - Inserted: PD 0e(e0xff/s14) Info: enclPd=ffff, scsiType=0, portMap=06, sasAddr=5000c500138d6839,0000000000000000 mfi0: 5653 (boot + 89s/0x0002/info) - PD 0e(e0xff/s14) FRU is 42D0422 mfi0: 5654 (boot + 89s/0x0002/info) - Inserted: PD 0f(e0xff/s15) mfi0: 5655 (boot + 89s/0x0002/info) - Inserted: PD 0f(e0xff/s15) Info: enclPd=ffff, scsiType=0, portMap=07, sasAddr=5000c500138d5e8d,0000000000000000 mfi0: 5656 (boot + 89s/0x0002/info) - PD 0f(e0xff/s15) FRU is 42D0422 mfi0: 5657 (boot + 144s/0x0008/info) - Battery temperature is normal mfi0: 5658 (308394231s/0x0020/info) - Time established as 10/09/09 9:03:51; (262 seconds since power on) mfi0: 5659 (boot + 3s/0x0020/info) - Firmware initialization started (PCI ID 0060/1000/0364/1014) mfi0: 5660 (boot + 3s/0x0020/info) - Firmware version 1.40.62-0691 mfi0: 5661 (boot + 3s/0x0020/info) - Firmware initialization started (PCI ID 0060/1000/0364/1014) mfi0: 5662 (boot + 3s/0x0020/info) - Firmware version 1.40.62-0691 mfi0: 5663 (boot + 64s/0x0008/info) - Battery Present mfi0: 5664 (boot + 64s/0x0020/info) - BBU FRU is mfi0: 5665 (boot + 64s/0x0020/info) - Board Revision mfi0: 5666 (boot + 89s/0x0002/info) - Inserted: PD 08(e0xff/s8) mfi0: 5667 (boot + 89s/0x0002/info) - Inserted: PD 08(e0xff/s8) Info: enclPd=ffff, scsiType=0, portMap=00, sasAddr=5000c500138d46b5,0000000000000000 So on. -- wbr, pluknet From pluknet at gmail.com Thu Oct 15 10:38:11 2009 From: pluknet at gmail.com (pluknet) Date: Thu Oct 15 10:38:26 2009 Subject: mfi(4) endless loop kernel output on attach In-Reply-To: References: Message-ID: 2009/10/15 pluknet : > Hi. > > This is 7.2-R. Seen on IBM x3650M2. > > During the boot I get those endless looping kernel messages while on > mfi(4) attach phase. > It's getting more odd since 7.2 booted and worked fine on exactly this > server model > months ago (on different box though).. Any hints? > After the looked endless loop the kernel eventually finished the mfi(4) initialization and continued its booting. Is it expected to do so long initialization? Almost at the end of kernel boot / near to multiuser start it panicked with: panic: invalid ife->ifm_data (0xa) in mii_phy_setmedia Though that's offtopic here. >From last part of dmesg: mfi0: 29365 (boot + 3s/0x0020/info) - Firmware initialization started (PCI ID 0060/1000/0364/1014) mfi0: 29366 (boot + 3s/0x0020/info) - Firmware version 1.40.62-0691 mfi0: 29367 (boot + 64s/0x0008/info) - Battery Present mfi0: 29368 (boot + 64s/0x0020/info) - BBU FRU is mfi0: 29369 (boot + 64s/0x0020/info) - Board Revision mfi0: 29370 (boot + 89s/0x0002/info) - Inserted: PD 08(e0xff/s8) mfi0: 29371 (boot + 89s/0x0002/info) - Inserted: PD 08(e0xff/s8) Info: enclPd=ffff, scsiType=0, portMap=00, sasAddr=5000c500138d46b5,0000000000000000 mfi0: 29372 (boot + 89s/0x0002/info) - PD 08(e0xff/s8) FRU is 42D0422 mfi0: 29373 (boot + 89s/0x0002/info) - Inserted: PD 09(e0xff/s9) mfi0: 29374 (boot + 89s/0x0002/info) - Inserted: PD 09(e0xff/s9) Info: enclPd=ffff, scsiType=0, portMap=01, sasAddr=5000c500138d842d,0000000000000000 mfi0: 29375 (boot + 89s/0x0002/info) - PD 09(e0xff/s9) FRU is 42D0422 mfi0: 29376 (boot + 89s/0x0002/info) - Inserted: PD 0a(e0xff/s10) mfi0: 29377 (boot + 89s/0x0002/info) - Inserted: PD 0a(e0xff/s10) Info: enclPd=ffff, scsiType=0, portMap=04, sasAddr=5000c500138d7d75,0000000000000000 mfi0: 29378 (boot + 89s/0x0002/info) - PD 0a(e0xff/s10) FRU is 42D0422 mfi0: 29379 (boot + 89s/0x0002/info) - Inserted: PD 0b(e0xff/s11) mfi0: 29380 (boot + 89s/0x0002/info) - Inserted: PD 0b(e0xff/s11) Info: enclPd=ffff, scsiType=0, portMap=05, sasAddr=5000c500138d7835,0000000000000000 mfi0: 29381 (boot + 89s/0x0002/info) - PD 0b(e0xff/s11) FRU is 42D0422 mfi0: 29382 (boot + 89s/0x0002/info) - Inserted: PD 0c(e0xff/s12) mfi0: 29383 (boot + 89s/0x0002/info) - Inserted: PD 0c(e0xff/s12) Info: enclPd=ffff, scsiType=0, portMap=02, sasAddr=5000c500138d60b5,0000000000000000 mfi0: 29384 (boot + 89s/0x0002/info) - PD 0c(e0xff/s12) FRU is 42D0422 mfi0: 29385 (boot + 89s/0x0002/info) - Inserted: PD 0d(e0xff/s13) mfi0: 29386 (boot + 89s/0x0002/info) - Inserted: PD 0d(e0xff/s13) Info: enclPd=ffff, scsiType=0, portMap=03, sasAddr=5000c500138d7bdd,0000000000000000 mfi0: 29387 (boot + 89s/0x0002/info) - PD 0d(e0xff/s13) FRU is 42D0422 mfi0: 29388 (boot + 89s/0x0002/info) - Inserted: PD 0e(e0xff/s14) mfi0: 29389 (boot + 89s/0x0002/info) - Inserted: PD 0e(e0xff/s14) Info: enclPd=ffff, scsiType=0, portMap=06, sasAddr=5000c500138d6839,0000000000000000 mfi0: 29390 (boot + 89s/0x0002/info) - PD 0e(e0xff/s14) FRU is 42D0422 mfi0: 29391 (boot + 89s/0x0002/info) - Inserted: PD 0f(e0xff/s15) mfi0: 29392 (boot + 89s/0x0002/info) - Inserted: PD 0f(e0xff/s15) Info: enclPd=ffff, scsiType=0, portMap=07, sasAddr=5000c500138d5e8d,0000000000000000 mfi0: 29393 (boot + 89s/0x0002/info) - PD 0f(e0xff/s15) FRU is 42D0422 mfi0: 29394 (boot + 144s/0x0008/info) - Battery temperature is normal ioapic0: routing intpin 16 (PCI IRQ 16) to vector 52 mfi0: [MPSAFE] mfi0: [ITHREAD] pcib8: irq 16 at device 28.4 on pci0 pcib8: domain 0 pcib8: secondary bus 6 pcib8: subordinate bus 10 pcib8: I/O decode 0xf000-0xfff pcib8: memory decode 0x97000000-0x978fffff pcib8: prefetched decode 0x96000000-0x96ffffff pci6: on pcib8 pci6: domain=0, physical bus=6 found-> vendor=0x101b, dev=0x0452, revid=0x01 domain=0, bus=6, slot=0, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0047, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x0b (2750 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 powerspec 3 supports D0 D3 current D0 MSI supports 2 messages, 64 bit pcib0: matched entry for 0.28.INTA pcib0: slot 28 INTA hardwired to IRQ 16 pcib8: slot 0 INTA is routed to irq 16 pcib9: irq 16 at device 0.0 on pci6 pcib9: domain 0 pcib9: secondary bus 7 pcib9: subordinate bus 7 pcib9: I/O decode 0xf000-0xfff pcib9: memory decode 0x97000000-0x978fffff pcib9: prefetched decode 0x96000000-0x96ffffff pci7: on pcib9 pci7: domain=0, physical bus=7 found-> vendor=0x102b, dev=0x0530, revid=0x00 domain=0, bus=7, slot=0, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0290, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x10 (4000 ns), maxlat=0x20 (8000 ns) intpin=a, irq=11 powerspec 1 supports D0 D3 current D0 map[10]: type Prefetchable Memory, range 32, base 0x96000000, size 24, enabled pcib9: requested memory range 0x96000000-0x96ffffff: good pcib8: requested memory range 0x96000000-0x96ffffff: good map[14]: type Memory, range 32, base 0x97800000, size 14, enabled pcib9: requested memory range 0x97800000-0x97803fff: good pcib8: requested memory range 0x97800000-0x97803fff: good map[18]: type Memory, range 32, base 0x97000000, size 23, enabled pcib9: requested memory range 0x97000000-0x977fffff: good pcib8: requested memory range 0x97000000-0x977fffff: good pcib0: matched entry for 0.28.INTA pcib0: slot 28 INTA hardwired to IRQ 16 pcib8: slot 0 INTA is routed to irq 16 pcib9: slot 0 INTA is routed to irq 16 vgapci0: mem 0x96000000-0x96ffffff,0x97800000-0x97803fff,0x97000000-0x977fffff irq 16 at device 0.0 on pci7 uhci2: port 0x2060-0x207f irq 17 at device 29.0 on pci0 uhci2: Reserved 0x20 bytes for rid 0x20 type 4 at 0x2060 uhci2: [GIANT-LOCKED] uhci2: [ITHREAD] usb3: on uhci2 usb3: USB revision 1.0 uhub3: on usb3 uhub3: 2 ports with 2 removable, self powered uhci3: port 0x2040-0x205f irq 18 at device 29.1 on pci0 uhci3: Reserved 0x20 bytes for rid 0x20 type 4 at 0x2040 uhci3: [GIANT-LOCKED] uhci3: [ITHREAD] usb4: on uhci3 usb4: USB revision 1.0 uhub4: on usb4 uhub4: 2 ports with 2 removable, self powered uhci4: port 0x2020-0x203f irq 19 at device 29.2 on pci0 uhci4: Reserved 0x20 bytes for rid 0x20 type 4 at 0x2020 uhci4: [GIANT-LOCKED] uhci4: [ITHREAD] usb5: on uhci4 usb5: USB revision 1.0 uhub5: on usb5 uhub5: 2 ports with 2 removable, self powered ehci1: mem 0x97a21000-0x97a213ff irq 17 at device 29.7 on pci0 ehci1: Reserved 0x400 bytes for rid 0x10 type 3 at 0x97a21000 ehci1: [GIANT-LOCKED] ehci1: [ITHREAD] usb6: EHCI version 1.0 usb6: companion controllers, 2 ports each: usb3 usb4 usb5 usb6: on ehci1 usb6: USB revision 2.0 uhub6: on usb6 uhub6: 6 ports with 6 removable, self powered usb6: handing over full speed device on port 2 to usb3 uhub6: port 2, device disappeared after reset pcib10: at device 30.0 on pci0 pcib10: domain 0 pcib10: secondary bus 41 pcib10: subordinate bus 45 pcib10: I/O decode 0x0-0x0 pcib10: no prefetched decode pcib10: Subtractively decoded bridge. pci41: on pcib10 pci41: domain=0, physical bus=41 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x20f0-0x20ff,0x20e0-0x20ef irq 16 at device 31.2 on pci0 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0x20f0 atapci0: Reserved 0x10 bytes for rid 0x24 type 4 at 0x20e0 ata0: on atapci0 atapci0: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0 atapci0: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6 ata0: reset tp1 mask=03 ostat0=00 ostat1=00 ata0: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata0: stat1=0x00 err=0x01 lsb=0x14 msb=0xeb ata0: reset tp2 stat0=00 stat1=00 devices=0xc ioapic0: routing intpin 14 (ISA IRQ 14) to vector 53 ata0: [MPSAFE] ata0: [ITHREAD] ata1: on atapci0 atapci0: Reserved 0x8 bytes for rid 0x18 type 4 at 0x170 atapci0: Reserved 0x1 bytes for rid 0x1c type 4 at 0x376 ata1: reset tp1 mask=03 ostat0=7f ostat1=7f ata1: stat0=0x7f err=0xff lsb=0xff msb=0xff ata1: stat0=0x7f err=0xff lsb=0xff msb=0xff ata1: stat0=0x7f err=0xff lsb=0xff msb=0xff ata1: stat0=0x7f err=0xff lsb=0xff msb=0xff ata1: stat0=0x7f err=0xff lsb=0xff msb=0xff ata1: stat0=0x7f err=0xff lsb=0xff msb=0xff ata1: stat0=0x7f err=0xff lsb=0xff msb=0xff ata1: stat0=0x7f err=0xff lsb=0xff msb=0xff ata1: stat0=0x7f err=0xff lsb=0xff msb=0xff ata1: stat0=0x7f err=0xff lsb=0xff msb=0xff ata1: stat0=0x7f err=0xff lsb=0xff msb=0xff ata1: stat0=0x7f err=0xff lsb=0xff msb=0xff ata1: stat0=0x7f err=0xff lsb=0xff msb=0xff ata1: stat0=0x7f err=0xff lsb=0xff msb=0xff ata1: stat0=0x7f err=0xff lsb=0xff msb=0xff ata1: stat0=0x7f err=0xff lsb=0xff msb=0xff ata1: stat0=0x7f err=0xff lsb=0xff msb=0xff ata1: stat0=0x7f err=0xff lsb=0xff msb=0xff ata1: stat0=0x7f err=0xff lsb=0xff msb=0xff ata1: stat0=0x7f err=0xff lsb=0xff msb=0xff ata1: stat0=0x7f err=0xff lsb=0xff msb=0xff ata1: stat0=0x7f err=0xff lsb=0xff msb=0xff ata1: stat1=0x7f err=0xff lsb=0xff msb=0xff ata1: reset tp2 stat0=ff stat1=ff devices=0x0 ioapic0: routing intpin 15 (ISA IRQ 15) to vector 54 ata1: [MPSAFE] ata1: [ITHREAD] pci0: at device 31.3 (no driver attached) atapci1: port 0x2108-0x210f,0x2124-0x2127,0x2100-0x2107,0x2120-0x2123,0x20d0-0x20df,0x20c0-0x20cf irq 21 at device 31.5 on pci0 atapci1: Reserved 0x10 bytes for rid 0x20 type 4 at 0x20d0 ioapic0: routing intpin 21 (PCI IRQ 21) to vector 55 atapci1: [MPSAFE] atapci1: [ITHREAD] atapci1: Reserved 0x10 bytes for rid 0x24 type 4 at 0x20c0 ata2: on atapci1 atapci1: Reserved 0x8 bytes for rid 0x10 type 4 at 0x2108 atapci1: Reserved 0x4 bytes for rid 0x14 type 4 at 0x2124 ata2: reset tp1 mask=03 ostat0=7f ostat1=7f ata2: stat0=0x7f err=0xff lsb=0xff msb=0xff ata2: stat0=0x7f err=0xff lsb=0xff msb=0xff ata2: stat0=0x7f err=0xff lsb=0xff msb=0xff ata2: stat0=0x7f err=0xff lsb=0xff msb=0xff ata2: stat0=0x7f err=0xff lsb=0xff msb=0xff ata2: stat0=0x7f err=0xff lsb=0xff msb=0xff ata2: stat0=0x7f err=0xff lsb=0xff msb=0xff ata2: stat0=0x7f err=0xff lsb=0xff msb=0xff ata2: stat0=0x7f err=0xff lsb=0xff msb=0xff ata2: stat0=0x7f err=0xff lsb=0xff msb=0xff ata2: stat0=0x7f err=0xff lsb=0xff msb=0xff ata2: stat0=0x7f err=0xff lsb=0xff msb=0xff ata2: stat0=0x7f err=0xff lsb=0xff msb=0xff ata2: stat0=0x7f err=0xff lsb=0xff msb=0xff ata2: stat0=0x7f err=0xff lsb=0xff msb=0xff ata2: stat0=0x7f err=0xff lsb=0xff msb=0xff ata2: stat0=0x7f err=0xff lsb=0xff msb=0xff ata2: stat0=0x7f err=0xff lsb=0xff msb=0xff ata2: stat0=0x7f err=0xff lsb=0xff msb=0xff ata2: stat0=0x7f err=0xff lsb=0xff msb=0xff ata2: stat0=0x7f err=0xff lsb=0xff msb=0xff ata2: stat0=0x7f err=0xff lsb=0xff msb=0xff ata2: stat1=0x7f err=0xff lsb=0xff msb=0xff ata2: reset tp2 stat0=ff stat1=ff devices=0x0 ata2: [MPSAFE] ata2: [ITHREAD] ata3: on atapci1 atapci1: Reserved 0x8 bytes for rid 0x18 type 4 at 0x2100 atapci1: Reserved 0x4 bytes for rid 0x1c type 4 at 0x2120 ata3: reset tp1 mask=03 ostat0=7f ostat1=7f ata3: stat0=0x7f err=0xff lsb=0xff msb=0xff ata3: stat0=0x7f err=0xff lsb=0xff msb=0xff ata3: stat0=0x7f err=0xff lsb=0xff msb=0xff ata3: stat0=0x7f err=0xff lsb=0xff msb=0xff ata3: stat0=0x7f err=0xff lsb=0xff msb=0xff ata3: stat0=0x7f err=0xff lsb=0xff msb=0xff ata3: stat0=0x7f err=0xff lsb=0xff msb=0xff ata3: stat0=0x7f err=0xff lsb=0xff msb=0xff ata3: stat0=0x7f err=0xff lsb=0xff msb=0xff ata3: stat0=0x7f err=0xff lsb=0xff msb=0xff ata3: stat0=0x7f err=0xff lsb=0xff msb=0xff ata3: stat0=0x7f err=0xff lsb=0xff msb=0xff ata3: stat0=0x7f err=0xff lsb=0xff msb=0xff ata3: stat0=0x7f err=0xff lsb=0xff msb=0xff ata3: stat0=0x7f err=0xff lsb=0xff msb=0xff ata3: stat0=0x7f err=0xff lsb=0xff msb=0xff ata3: stat0=0x7f err=0xff lsb=0xff msb=0xff ata3: stat0=0x7f err=0xff lsb=0xff msb=0xff ata3: stat0=0x7f err=0xff lsb=0xff msb=0xff ata3: stat0=0x7f err=0xff lsb=0xff msb=0xff ata3: stat0=0x7f err=0xff lsb=0xff msb=0xff ata3: stat0=0x7f err=0xff lsb=0xff msb=0xff ata3: stat1=0x7f err=0xff lsb=0xff msb=0xff ata3: reset tp2 stat0=ff stat1=ff devices=0x0 ata3: [MPSAFE] ata3: [ITHREAD] sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: irq maps: 0 0 0 0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: irq maps: 0 0 0 0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A, console ioapic0: routing intpin 4 (ISA IRQ 4) to vector 56 sio0: [FILTER] sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled sio1: irq maps: 0 0 0 0 sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled sio1: irq maps: 0 0 0 0 sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ioapic0: routing intpin 3 (ISA IRQ 3) to vector 57 sio1: [FILTER] cpu0: on acpi0 cpu0: switching to generic Cx mode est0: on cpu0 est0: Invalid id16 (set, cur) = (16, 17) est0: Invalid freq 2128, ignored. est0: Invalid id16 (set, cur) = (15, 17) est0: Invalid freq 1995, ignored. est0: Invalid id16 (set, cur) = (14, 17) est0: Invalid freq 1862, ignored. est0: Invalid id16 (set, cur) = (13, 17) est0: Invalid freq 1729, ignored. est0: Invalid id16 (set, cur) = (12, 17) est0: Invalid freq 1596, ignored. p4tcc0: on cpu0 cpu1: on acpi0 est1: on cpu1 est1: Invalid id16 (set, cur) = (16, 17) est1: Invalid freq 2128, ignored. est1: Invalid id16 (set, cur) = (15, 17) est1: Invalid freq 1995, ignored. est1: Invalid id16 (set, cur) = (14, 17) est1: Invalid freq 1862, ignored. est1: Invalid id16 (set, cur) = (13, 17) est1: Invalid freq 1729, ignored. est1: Invalid id16 (set, cur) = (12, 17) est1: Invalid freq 1596, ignored. p4tcc1: on cpu1 cpu2: on acpi0 est2: on cpu2 est2: Invalid id16 (set, cur) = (16, 17) est2: Invalid freq 2128, ignored. est2: Invalid id16 (set, cur) = (15, 17) est2: Invalid freq 1995, ignored. est2: Invalid id16 (set, cur) = (14, 17) est2: Invalid freq 1862, ignored. est2: Invalid id16 (set, cur) = (13, 17) est2: Invalid freq 1729, ignored. est2: Invalid id16 (set, cur) = (12, 17) est2: Invalid freq 1596, ignored. p4tcc2: on cpu2 cpu3: on acpi0 est3: on cpu3 est3: Invalid id16 (set, cur) = (16, 17) est3: Invalid freq 2128, ignored. est3: Invalid id16 (set, cur) = (15, 17) est3: Invalid freq 1995, ignored. est3: Invalid id16 (set, cur) = (14, 17) est3: Invalid freq 1862, ignored. est3: Invalid id16 (set, cur) = (13, 17) est3: Invalid freq 1729, ignored. est3: Invalid id16 (set, cur) = (12, 17) est3: Invalid freq 1596, ignored. p4tcc3: on cpu3 cpu4: on acpi0 est4: on cpu4 est4: Invalid id16 (set, cur) = (16, 17) est4: Invalid freq 2128, ignored. est4: Invalid id16 (set, cur) = (15, 17) est4: Invalid freq 1995, ignored. est4: Invalid id16 (set, cur) = (14, 17) est4: Invalid freq 1862, ignored. est4: Invalid id16 (set, cur) = (13, 17) est4: Invalid freq 1729, ignored. est4: Invalid id16 (set, cur) = (12, 17) est4: Invalid freq 1596, ignored. p4tcc4: on cpu4 cpu5: on acpi0 est5: on cpu5 est5: Invalid id16 (set, cur) = (16, 17) est5: Invalid freq 2128, ignored. est5: Invalid id16 (set, cur) = (15, 17) est5: Invalid freq 1995, ignored. est5: Invalid id16 (set, cur) = (14, 17) est5: Invalid freq 1862, ignored. est5: Invalid id16 (set, cur) = (13, 17) est5: Invalid freq 1729, ignored. est5: Invalid id16 (set, cur) = (12, 17) est5: Invalid freq 1596, ignored. p4tcc5: on cpu5 cpu6: on acpi0 est6: on cpu6 est6: Invalid id16 (set, cur) = (16, 17) est6: Invalid freq 2128, ignored. est6: Invalid id16 (set, cur) = (15, 17) est6: Invalid freq 1995, ignored. est6: Invalid id16 (set, cur) = (14, 17) est6: Invalid freq 1862, ignored. est6: Invalid id16 (set, cur) = (13, 17) est6: Invalid freq 1729, ignored. est6: Invalid id16 (set, cur) = (12, 17) est6: Invalid freq 1596, ignored. p4tcc6: on cpu6 cpu7: on acpi0 est7: on cpu7 est7: Invalid id16 (set, cur) = (16, 17) est7: Invalid freq 2128, ignored. est7: Invalid id16 (set, cur) = (15, 17) est7: Invalid freq 1995, ignored. est7: Invalid id16 (set, cur) = (14, 17) est7: Invalid freq 1862, ignored. est7: Invalid id16 (set, cur) = (13, 17) est7: Invalid freq 1729, ignored. est7: Invalid id16 (set, cur) = (12, 17) est7: Invalid freq 1596, ignored. p4tcc7: on cpu7 cpu8: on acpi0 est8: on cpu8 est8: Invalid id16 (set, cur) = (16, 17) est8: Invalid freq 2128, ignored. est8: Invalid id16 (set, cur) = (15, 17) est8: Invalid freq 1995, ignored. est8: Invalid id16 (set, cur) = (14, 17) est8: Invalid freq 1862, ignored. est8: Invalid id16 (set, cur) = (13, 17) est8: Invalid freq 1729, ignored. est8: Invalid id16 (set, cur) = (12, 17) est8: Invalid freq 1596, ignored. p4tcc8: on cpu8 cpu9: on acpi0 est9: on cpu9 est9: Invalid id16 (set, cur) = (16, 17) est9: Invalid freq 2128, ignored. est9: Invalid id16 (set, cur) = (15, 17) est9: Invalid freq 1995, ignored. est9: Invalid id16 (set, cur) = (14, 17) est9: Invalid freq 1862, ignored. est9: Invalid id16 (set, cur) = (13, 17) est9: Invalid freq 1729, ignored. est9: Invalid id16 (set, cur) = (12, 17) est9: Invalid freq 1596, ignored. p4tcc9: on cpu9 cpu10: on acpi0 est10: on cpu10 est10: Invalid id16 (set, cur) = (16, 17) est10: Invalid freq 2128, ignored. est10: Invalid id16 (set, cur) = (15, 17) est10: Invalid freq 1995, ignored. est10: Invalid id16 (set, cur) = (14, 17) est10: Invalid freq 1862, ignored. est10: Invalid id16 (set, cur) = (13, 17) est10: Invalid freq 1729, ignored. est10: Invalid id16 (set, cur) = (12, 17) est10: Invalid freq 1596, ignored. p4tcc10: on cpu10 cpu11: on acpi0 est11: on cpu11 est11: Invalid id16 (set, cur) = (16, 17) est11: Invalid freq 2128, ignored. est11: Invalid id16 (set, cur) = (15, 17) est11: Invalid freq 1995, ignored. est11: Invalid id16 (set, cur) = (14, 17) est11: Invalid freq 1862, ignored. est11: Invalid id16 (set, cur) = (13, 17) est11: Invalid freq 1729, ignored. est11: Invalid id16 (set, cur) = (12, 17) est11: Invalid freq 1596, ignored. p4tcc11: on cpu11 cpu12: on acpi0 est12: on cpu12 est12: Invalid id16 (set, cur) = (16, 17) est12: Invalid freq 2128, ignored. est12: Invalid id16 (set, cur) = (15, 17) est12: Invalid freq 1995, ignored. est12: Invalid id16 (set, cur) = (14, 17) est12: Invalid freq 1862, ignored. est12: Invalid id16 (set, cur) = (13, 17) est12: Invalid freq 1729, ignored. est12: Invalid id16 (set, cur) = (12, 17) est12: Invalid freq 1596, ignored. p4tcc12: on cpu12 cpu13: on acpi0 est13: on cpu13 est13: Invalid id16 (set, cur) = (16, 17) est13: Invalid freq 2128, ignored. est13: Invalid id16 (set, cur) = (15, 17) est13: Invalid freq 1995, ignored. est13: Invalid id16 (set, cur) = (14, 17) est13: Invalid freq 1862, ignored. est13: Invalid id16 (set, cur) = (13, 17) est13: Invalid freq 1729, ignored. est13: Invalid id16 (set, cur) = (12, 17) est13: Invalid freq 1596, ignored. p4tcc13: on cpu13 cpu14: on acpi0 est14: on cpu14 est14: Invalid id16 (set, cur) = (16, 17) est14: Invalid freq 2128, ignored. est14: Invalid id16 (set, cur) = (15, 17) est14: Invalid freq 1995, ignored. est14: Invalid id16 (set, cur) = (14, 17) est14: Invalid freq 1862, ignored. est14: Invalid id16 (set, cur) = (13, 17) est14: Invalid freq 1729, ignored. est14: Invalid id16 (set, cur) = (12, 17) est14: Invalid freq 1596, ignored. p4tcc14: on cpu14 cpu15: on acpi0 est15: on cpu15 est15: Invalid id16 (set, cur) = (16, 17) est15: Invalid freq 2128, ignored. est15: Invalid id16 (set, cur) = (15, 17) est15: Invalid freq 1995, ignored. est15: Invalid id16 (set, cur) = (14, 17) est15: Invalid freq 1862, ignored. est15: Invalid id16 (set, cur) = (13, 17) est15: Invalid freq 1729, ignored. est15: Invalid id16 (set, cur) = (12, 17) est15: Invalid freq 1596, ignored. p4tcc15: on cpu15 ex_isa_identify() sio: sio0 already exists; skipping it sio: sio1 already exists; skipping it ahc_isa_probe 0: ioport 0xc00 alloc failed sc: sc0 already exists; skipping it vga: vga0 already exists; skipping it isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices orm0: at iomem 0xc0000-0xc7fff,0xca800-0xd8fff on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 004d atkbd: keyboard ID 0xffffffff (1) kbdc: RESET_KBD return code:ffffffff kbdc: RESET_KBD return code:ffffffff kbdc: RESET_KBD return code:ffffffff kbdc: DIAGNOSE status:0055 kbdc: TEST_KBD_PORT status:0000 atkbd: failed to reset the keyboard. kbd0 at atkbd0 kbd0: atkbd0, AT 84 (1), config:0x0, flags:0x3d0000 ioapic0: routing intpin 1 (ISA IRQ 1) to vector 58 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] psm0: current command byte:004d kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:ffffffff kbdc: RESET_AUX return code:ffffffff kbdc: RESET_AUX return code:ffffffff kbdc: DIAGNOSE status:0055 kbdc: TEST_KBD_PORT status:0000 psm0: failed to reset the aux device. fdc0 failed to probe at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 ppc0: cannot reserve I/O port range ppc0: failed to probe at irq 7 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sc0: fb0, kbd1, terminal emulator: sc (syscons terminal) sio2: not probed (disabled) sio3: not probed (disabled) vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 isa_probe_children: probing PnP devices cdce0: on uhub3 cdce0: faking MAC address cdce0: WARNING: using obsoleted IFF_NEEDSGIANT flag cdce0: bpf attached cdce0: Ethernet address: 2a:00:00:00:00:00 Device configuration finished. Reducing kern.maxvnodes 382450 -> 100000 procfs registered lapic: Divisor 2, Frequency 66669284 hz Timecounter "TSC" frequency 2266755720 Hz quality -100 Timecounters tick every 1.000 msec ipfw2 (+ipv6) initialized, divert loadable, nat loadable, rule-based forwarding enabled, default to accept, logging limited to 500 packets/entry by default lo0: bpf attached hptrr: no controller detected. bce0: link state changed to DOWN bce1: link state changed to DOWN ata0: reiniting channel .. ata0: reset tp1 mask=03 ostat0=00 ostat1=00 ata0: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata0: stat1=0x00 err=0x01 lsb=0x14 msb=0xeb ata0: reset tp2 stat0=00 stat1=00 devices=0xc ata0: reinit done .. Expensive timeout(9) function: 0xffffffff80267220(0xffffff000414c000) 1.400657904 s ata0: reiniting channel .. ata0: reset tp1 mask=03 ostat0=00 ostat1=00 ata0: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata0: stat1=0x00 err=0x01 lsb=0x14 msb=0xeb ata0: reset tp2 stat0=00 stat1=00 devices=0xc ata0: reinit done .. ata0-master: pio=PIO4 wdma=WDMA2 udma=UDMA33 cable=40 wire acd0: CDRW drive at ata0 as master acd0: read 4134KB/s (4134KB/s) write 4134KB/s (4134KB/s), 2048KB buffer, SATA150 acd0: Reads: CDR, CDRW, CDDA stream, DVDROM, DVDR, DVDRAM, packet acd0: Writes: CDR, CDRW, test write, burnproof acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray, unlocked acd0: Medium: no/blank disc mfi0: 29395 (308927984s/0x0020/info) - Time established as 10/15/09 13:19:44; (210 seconds since power on) ATA PseudoRAID loaded SMP: AP CPU #1 Launched! cpu1 AP: ID: 0x01000000 VER: 0x00060015 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000200ef therm: 0x00010000 err: 0x00010000 pcm: 0x00010000 SMP: AP CPU #4 Launched! cpu4 AP: ID: 0x04000000 VER: 0x00060015 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000200ef therm: 0x00010000 err: 0x00010000 pcm: 0x00010000 SMP: AP CPU #10 Launched! cpu10 AP: ID: 0x12000000 VER: 0x00060015 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000200ef therm: 0x00010000 err: 0x00010000 pcm: 0x00010000 SMP: AP CPU #13 Launched! cpu13 AP: ID: 0x15000000 VER: 0x00060015 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000200ef therm: 0x00010000 err: 0x00010000 pcm: 0x00010000 SMP: AP CPU #5 Launched! cpu5 AP: ID: 0x05000000 VER: 0x00060015 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000200ef therm: 0x00010000 err: 0x00010000 pcm: 0x00010000 SMP: AP CPU #7 Launched! cpu7 AP: ID: 0x07000000 VER: 0x00060015 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000200ef therm: 0x00010000 err: 0x00010000 pcm: 0x00010000 SMP: AP CPU #15 Launched! cpu15 AP: ID: 0x17000000 VER: 0x00060015 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000200ef therm: 0x00010000 err: 0x00010000 pcm: 0x00010000 SMP: AP CPU #14 Launched! cpu14 AP: ID: 0x16000000 VER: 0x00060015 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000200ef therm: 0x00010000 err: 0x00010000 pcm: 0x00010000 SMP: AP CPU #6 Launched! cpu6 AP: ID: 0x06000000 VER: 0x00060015 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000200ef therm: 0x00010000 err: 0x00010000 pcm: 0x00010000 SMP: AP CPU #2 Launched! cpu2 AP: ID: 0x02000000 VER: 0x00060015 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000200ef therm: 0x00010000 err: 0x00010000 pcm: 0x00010000 SMP: AP CPU #9 Launched! cpu9 AP: ID: 0x11000000 VER: 0x00060015 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000200ef therm: 0x00010000 err: 0x00010000 pcm: 0x00010000 SMP: AP CPU #12 Launched! cpu12 AP: ID: 0x14000000 VER: 0x00060015 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000200ef therm: 0x00010000 err: 0x00010000 pcm: 0x00010000 SMP: AP CPU #3 Launched! cpu3 AP: ID: 0x03000000 VER: 0x00060015 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000200ef therm: 0x00010000 err: 0x00010000 pcm: 0x00010000 SMP: AP CPU #8 Launched! cpu8 AP: ID: 0x10000000 VER: 0x00060015 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000200ef therm: 0x00010000 err: 0x00010000 pcm: 0x00010000 SMP: AP CPU #11 Launched! cpu11 AP: ID: 0x13000000 VER: 0x00060015 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000200ef therm: 0x00010000 err: 0x00010000 pcm: 0x00010000 ioapic0: Assigning ISA IRQ 1 to local APIC 0 ioapic0: Assigning ISA IRQ 3 to local APIC 2 ioapic0: Assigning ISA IRQ 4 to local APIC 4 ioapic0: Assigning ISA IRQ 9 to local APIC 6 ioapic0: Assigning ISA IRQ 14 to local APIC 16 ioapic0: Assigning ISA IRQ 15 to local APIC 18 ioapic0: Assigning PCI IRQ 16 to local APIC 20 ioapic0: Assigning PCI IRQ 17 to local APIC 22 ioapic0: Assigning PCI IRQ 18 to local APIC 0 ioapic0: Assigning PCI IRQ 19 to local APIC 2 ioapic0: Assigning PCI IRQ 21 to local APIC 4 msi: Assigning MSI IRQ 256 to local APIC 6 msi: Assigning MSI IRQ 257 to local APIC 16 WARNING: WITNESS option enabled, expect reduced performance. WARNING: DIAGNOSTIC option enabled, expect reduced performance. Trying to mount root from nfs:194.190.130.130:/home/jails/freebsd7.2 panic: invalid ife->ifm_data (0xa) in mii_phy_setmedia cpuid = 15 KDB: enter: panic [thread pid 1 tid 100001 ] Stopped at kdb_enter_why+0x3d: movq $0,0x649838(%rip) > mfi0: 5428 (boot + 3s/0x0020/info) - Firmware initialization started > (PCI ID 0060/1000/0364/1014) > mfi0: 5429 (boot + 3s/0x0020/info) - Firmware version 1.40.62-0691 > mfi0: 5430 (boot + 3s/0x0020/info) - Firmware initialization started > (PCI ID 0060/1000/0364/1014) > mfi0: 5431 (boot + 3s/0x0020/info) - Firmware version 1.40.62-0691 > mfi0: 5432 (boot + 64s/0x0008/info) - Battery Present > mfi0: 5433 (boot + 64s/0x0020/info) - BBU FRU is > mfi0: 5434 (boot + 64s/0x0020/info) - Board Revision > mfi0: 5435 (boot + 89s/0x0002/info) - Inserted: PD 08(e0xff/s8) > mfi0: 5436 (boot + 89s/0x0002/info) - Inserted: PD 08(e0xff/s8) Info: > enclPd=ffff, scsiType=0, portMap=00, > sasAddr=5000c500138d46b5,0000000000000000 > mfi0: 5437 (boot + 89s/0x0002/info) - PD 08(e0xff/s8) FRU is 42D0422 > mfi0: 5438 (boot + 89s/0x0002/info) - Inserted: PD 09(e0xff/s9) > mfi0: 5439 (boot + 89s/0x0002/info) - Inserted: PD 09(e0xff/s9) Info: > enclPd=ffff, scsiType=0, portMap=01, > sasAddr=5000c500138d842d,0000000000000000 > mfi0: 5440 (boot + 89s/0x0002/info) - PD 09(e0xff/s9) FRU is 42D0422 > mfi0: 5441 (boot + 89s/0x0002/info) - Inserted: PD 0a(e0xff/s10) > mfi0: 5442 (boot + 89s/0x0002/info) - Inserted: PD 0a(e0xff/s10) Info: > enclPd=ffff, scsiType=0, portMap=04, > sasAddr=5000c500138d7d75,0000000000000000 > mfi0: 5443 (boot + 89s/0x0002/info) - PD 0a(e0xff/s10) FRU is 42D0422 > mfi0: 5444 (boot + 89s/0x0002/info) - Inserted: PD 0b(e0xff/s11) > mfi0: 5445 (boot + 89s/0x0002/info) - Inserted: PD 0b(e0xff/s11) Info: > enclPd=ffff, scsiType=0, portMap=05, > sasAddr=5000c500138d7835,0000000000000000 > mfi0: 5446 (boot + 89s/0x0002/info) - PD 0b(e0xff/s11) FRU is 42D0422 > mfi0: 5447 (boot + 89s/0x0002/info) - Inserted: PD 0c(e0xff/s12) > mfi0: 5448 (boot + 89s/0x0002/info) - Inserted: PD 0c(e0xff/s12) Info: > enclPd=ffff, scsiType=0, portMap=02, > sasAddr=5000c500138d60b5,0000000000000000 > mfi0: 5449 (boot + 89s/0x0002/info) - PD 0c(e0xff/s12) FRU is 42D0422 > mfi0: 5450 (boot + 89s/0x0002/info) - Inserted: PD 0d(e0xff/s13) > mfi0: 5451 (boot + 89s/0x0002/info) - Inserted: PD 0d(e0xff/s13) Info: > enclPd=ffff, scsiType=0, portMap=03, > sasAddr=5000c500138d7bdd,0000000000000000 > mfi0: 5452 (boot + 89s/0x0002/info) - PD 0d(e0xff/s13) FRU is 42D0422 > mfi0: 5453 (boot + 89s/0x0002/info) - Inserted: PD 0e(e0xff/s14) > mfi0: 5454 (boot + 89s/0x0002/info) - Inserted: PD 0e(e0xff/s14) Info: > enclPd=ffff, scsiType=0, portMap=06, > sasAddr=5000c500138d6839,0000000000000000 > mfi0: 5455 (boot + 89s/0x0002/info) - PD 0e(e0xff/s14) FRU is 42D0422 > mfi0: 5456 (boot + 89s/0x0002/info) - Inserted: PD 0f(e0xff/s15) > mfi0: 5457 (boot + 89s/0x0002/info) - Inserted: PD 0f(e0xff/s15) Info: > enclPd=ffff, scsiType=0, portMap=07, > sasAddr=5000c500138d5e8d,0000000000000000 > mfi0: 5458 (boot + 89s/0x0002/info) - PD 0f(e0xff/s15) FRU is 42D0422 > mfi0: 5459 (boot + 144s/0x0008/info) - Battery temperature is normal > mfi0: 5460 (308390540s/0x0020/info) - Time established as 10/09/09 > 8:02:20; (256 seconds since power on) > mfi0: 5461 (boot + 3s/0x0020/info) - Firmware initialization started > (PCI ID 0060/1000/0364/1014) > mfi0: 5462 (boot + 3s/0x0020/info) - Firmware version 1.40.62-0691 > mfi0: 5463 (boot + 3s/0x0020/info) - Firmware initialization started > (PCI ID 0060/1000/0364/1014) > mfi0: 5464 (boot + 3s/0x0020/info) - Firmware version 1.40.62-0691 > mfi0: 5465 (boot + 64s/0x0008/info) - Battery Present > mfi0: 5466 (boot + 64s/0x0020/info) - BBU FRU is > mfi0: 5467 (boot + 64s/0x0020/info) - Board Revision > mfi0: 5468 (boot + 89s/0x0002/info) - Inserted: PD 08(e0xff/s8) > mfi0: 5469 (boot + 89s/0x0002/info) - Inserted: PD 08(e0xff/s8) Info: > enclPd=ffff, scsiType=0, portMap=00, > sasAddr=5000c500138d46b5,0000000000000000 > mfi0: 5470 (boot + 89s/0x0002/info) - PD 08(e0xff/s8) FRU is 42D0422 > mfi0: 5471 (boot + 89s/0x0002/info) - Inserted: PD 09(e0xff/s9) > mfi0: 5472 (boot + 89s/0x0002/info) - Inserted: PD 09(e0xff/s9) Info: > enclPd=ffff, scsiType=0, portMap=01, > sasAddr=5000c500138d842d,0000000000000000 > mfi0: 5473 (boot + 89s/0x0002/info) - PD 09(e0xff/s9) FRU is 42D0422 > mfi0: 5474 (boot + 89s/0x0002/info) - Inserted: PD 0a(e0xff/s10) > mfi0: 5475 (boot + 89s/0x0002/info) - Inserted: PD 0a(e0xff/s10) Info: > enclPd=ffff, scsiType=0, portMap=04, > sasAddr=5000c500138d7d75,0000000000000000 > mfi0: 5476 (boot + 89s/0x0002/info) - PD 0a(e0xff/s10) FRU is 42D0422 > mfi0: 5477 (boot + 89s/0x0002/info) - Inserted: PD 0b(e0xff/s11) > mfi0: 5478 (boot + 89s/0x0002/info) - Inserted: PD 0b(e0xff/s11) Info: > enclPd=ffff, scsiType=0, portMap=05, > sasAddr=5000c500138d7835,0000000000000000 > mfi0: 5479 (boot + 89s/0x0002/info) - PD 0b(e0xff/s11) FRU is 42D0422 > mfi0: 5480 (boot + 89s/0x0002/info) - Inserted: PD 0c(e0xff/s12) > mfi0: 5481 (boot + 89s/0x0002/info) - Inserted: PD 0c(e0xff/s12) Info: > enclPd=ffff, scsiType=0, portMap=02, > sasAddr=5000c500138d60b5,0000000000000000 > mfi0: 5482 (boot + 89s/0x0002/info) - PD 0c(e0xff/s12) FRU is 42D0422 > mfi0: 5483 (boot + 89s/0x0002/info) - Inserted: PD 0d(e0xff/s13) > mfi0: 5484 (boot + 89s/0x0002/info) - Inserted: PD 0d(e0xff/s13) Info: > enclPd=ffff, scsiType=0, portMap=03, > sasAddr=5000c500138d7bdd,0000000000000000 > mfi0: 5485 (boot + 89s/0x0002/info) - PD 0d(e0xff/s13) FRU is 42D0422 > mfi0: 5486 (boot + 89s/0x0002/info) - Inserted: PD 0e(e0xff/s14) > mfi0: 5487 (boot + 89s/0x0002/info) - Inserted: PD 0e(e0xff/s14) Info: > enclPd=ffff, scsiType=0, portMap=06, > sasAddr=5000c500138d6839,0000000000000000 > mfi0: 5488 (boot + 89s/0x0002/info) - PD 0e(e0xff/s14) FRU is 42D0422 > mfi0: 5489 (boot + 89s/0x0002/info) - Inserted: PD 0f(e0xff/s15) > mfi0: 5490 (boot + 89s/0x0002/info) - Inserted: PD 0f(e0xff/s15) Info: > enclPd=ffff, scsiType=0, portMap=07, > sasAddr=5000c500138d5e8d,0000000000000000 > mfi0: 5491 (boot + 89s/0x0002/info) - PD 0f(e0xff/s15) FRU is 42D0422 > mfi0: 5492 (boot + 144s/0x0008/info) - Battery temperature is normal > mfi0: 5493 (308391152s/0x0020/info) - Time established as 10/09/09 > 8:12:32; (256 seconds since power on) > mfi0: 5494 (boot + 3s/0x0020/info) - Firmware initialization started > (PCI ID 0060/1000/0364/1014) > mfi0: 5495 (boot + 3s/0x0020/info) - Firmware version 1.40.62-0691 > mfi0: 5496 (boot + 3s/0x0020/info) - Firmware initialization started > (PCI ID 0060/1000/0364/1014) > mfi0: 5497 (boot + 3s/0x0020/info) - Firmware version 1.40.62-0691 > mfi0: 5498 (boot + 64s/0x0008/info) - Battery Present > mfi0: 5499 (boot + 64s/0x0020/info) - BBU FRU is > mfi0: 5500 (boot + 64s/0x0020/info) - Board Revision > mfi0: 5501 (boot + 89s/0x0002/info) - Inserted: PD 08(e0xff/s8) > mfi0: 5502 (boot + 89s/0x0002/info) - Inserted: PD 08(e0xff/s8) Info: > enclPd=ffff, scsiType=0, portMap=00, > sasAddr=5000c500138d46b5,0000000000000000 > mfi0: 5503 (boot + 89s/0x0002/info) - PD 08(e0xff/s8) FRU is 42D0422 > mfi0: 5504 (boot + 89s/0x0002/info) - Inserted: PD 09(e0xff/s9) > mfi0: 5505 (boot + 89s/0x0002/info) - Inserted: PD 09(e0xff/s9) Info: > enclPd=ffff, scsiType=0, portMap=01, > sasAddr=5000c500138d842d,0000000000000000 > mfi0: 5506 (boot + 89s/0x0002/info) - PD 09(e0xff/s9) FRU is 42D0422 > mfi0: 5507 (boot + 89s/0x0002/info) - Inserted: PD 0a(e0xff/s10) > mfi0: 5508 (boot + 89s/0x0002/info) - Inserted: PD 0a(e0xff/s10) Info: > enclPd=ffff, scsiType=0, portMap=04, > sasAddr=5000c500138d7d75,0000000000000000 > mfi0: 5509 (boot + 89s/0x0002/info) - PD 0a(e0xff/s10) FRU is 42D0422 > mfi0: 5510 (boot + 89s/0x0002/info) - Inserted: PD 0b(e0xff/s11) > mfi0: 5511 (boot + 89s/0x0002/info) - Inserted: PD 0b(e0xff/s11) Info: > enclPd=ffff, scsiType=0, portMap=05, > sasAddr=5000c500138d7835,0000000000000000 > mfi0: 5512 (boot + 89s/0x0002/info) - PD 0b(e0xff/s11) FRU is 42D0422 > mfi0: 5513 (boot + 89s/0x0002/info) - Inserted: PD 0c(e0xff/s12) > mfi0: 5514 (boot + 89s/0x0002/info) - Inserted: PD 0c(e0xff/s12) Info: > enclPd=ffff, scsiType=0, portMap=02, > sasAddr=5000c500138d60b5,0000000000000000 > mfi0: 5515 (boot + 89s/0x0002/info) - PD 0c(e0xff/s12) FRU is 42D0422 > mfi0: 5516 (boot + 89s/0x0002/info) - Inserted: PD 0d(e0xff/s13) > mfi0: 5517 (boot + 89s/0x0002/info) - Inserted: PD 0d(e0xff/s13) Info: > enclPd=ffff, scsiType=0, portMap=03, > sasAddr=5000c500138d7bdd,0000000000000000 > mfi0: 5518 (boot + 89s/0x0002/info) - PD 0d(e0xff/s13) FRU is 42D0422 > mfi0: 5519 (boot + 89s/0x0002/info) - Inserted: PD 0e(e0xff/s14) > mfi0: 5520 (boot + 89s/0x0002/info) - Inserted: PD 0e(e0xff/s14) Info: > enclPd=ffff, scsiType=0, portMap=06, > sasAddr=5000c500138d6839,0000000000000000 > mfi0: 5521 (boot + 89s/0x0002/info) - PD 0e(e0xff/s14) FRU is 42D0422 > mfi0: 5522 (boot + 89s/0x0002/info) - Inserted: PD 0f(e0xff/s15) > mfi0: 5523 (boot + 89s/0x0002/info) - Inserted: PD 0f(e0xff/s15) Info: > enclPd=ffff, scsiType=0, portMap=07, > sasAddr=5000c500138d5e8d,0000000000000000 > mfi0: 5524 (boot + 89s/0x0002/info) - PD 0f(e0xff/s15) FRU is 42D0422 > mfi0: 5525 (boot + 144s/0x0008/info) - Battery temperature is normal > mfi0: 5526 (308391765s/0x0020/info) - Time established as 10/09/09 > 8:22:45; (257 seconds since power on) > mfi0: 5527 (boot + 3s/0x0020/info) - Firmware initialization started > (PCI ID 0060/1000/0364/1014) > mfi0: 5528 (boot + 3s/0x0020/info) - Firmware version 1.40.62-0691 > mfi0: 5529 (boot + 3s/0x0020/info) - Firmware initialization started > (PCI ID 0060/1000/0364/1014) > mfi0: 5530 (boot + 3s/0x0020/info) - Firmware version 1.40.62-0691 > mfi0: 5531 (boot + 64s/0x0008/info) - Battery Present > mfi0: 5532 (boot + 64s/0x0020/info) - BBU FRU is > mfi0: 5533 (boot + 64s/0x0020/info) - Board Revision > mfi0: 5534 (boot + 89s/0x0002/info) - Inserted: PD 08(e0xff/s8) > mfi0: 5535 (boot + 89s/0x0002/info) - Inserted: PD 08(e0xff/s8) Info: > enclPd=ffff, scsiType=0, portMap=00, > sasAddr=5000c500138d46b5,0000000000000000 > mfi0: 5536 (boot + 89s/0x0002/info) - PD 08(e0xff/s8) FRU is 42D0422 > mfi0: 5537 (boot + 89s/0x0002/info) - Inserted: PD 09(e0xff/s9) > mfi0: 5538 (boot + 89s/0x0002/info) - Inserted: PD 09(e0xff/s9) Info: > enclPd=ffff, scsiType=0, portMap=01, > sasAddr=5000c500138d842d,0000000000000000 > mfi0: 5539 (boot + 89s/0x0002/info) - PD 09(e0xff/s9) FRU is 42D0422 > mfi0: 5540 (boot + 89s/0x0002/info) - Inserted: PD 0a(e0xff/s10) > mfi0: 5541 (boot + 89s/0x0002/info) - Inserted: PD 0a(e0xff/s10) Info: > enclPd=ffff, scsiType=0, portMap=04, > sasAddr=5000c500138d7d75,0000000000000000 > mfi0: 5542 (boot + 89s/0x0002/info) - PD 0a(e0xff/s10) FRU is 42D0422 > mfi0: 5543 (boot + 89s/0x0002/info) - Inserted: PD 0b(e0xff/s11) > mfi0: 5544 (boot + 89s/0x0002/info) - Inserted: PD 0b(e0xff/s11) Info: > enclPd=ffff, scsiType=0, portMap=05, > sasAddr=5000c500138d7835,0000000000000000 > mfi0: 5545 (boot + 89s/0x0002/info) - PD 0b(e0xff/s11) FRU is 42D0422 > mfi0: 5546 (boot + 89s/0x0002/info) - Inserted: PD 0c(e0xff/s12) > mfi0: 5547 (boot + 89s/0x0002/info) - Inserted: PD 0c(e0xff/s12) Info: > enclPd=ffff, scsiType=0, portMap=02, > sasAddr=5000c500138d60b5,0000000000000000 > mfi0: 5548 (boot + 89s/0x0002/info) - PD 0c(e0xff/s12) FRU is 42D0422 > mfi0: 5549 (boot + 89s/0x0002/info) - Inserted: PD 0d(e0xff/s13) > mfi0: 5550 (boot + 89s/0x0002/info) - Inserted: PD 0d(e0xff/s13) Info: > enclPd=ffff, scsiType=0, portMap=03, > sasAddr=5000c500138d7bdd,0000000000000000 > mfi0: 5551 (boot + 89s/0x0002/info) - PD 0d(e0xff/s13) FRU is 42D0422 > mfi0: 5552 (boot + 89s/0x0002/info) - Inserted: PD 0e(e0xff/s14) > mfi0: 5553 (boot + 89s/0x0002/info) - Inserted: PD 0e(e0xff/s14) Info: > enclPd=ffff, scsiType=0, portMap=06, > sasAddr=5000c500138d6839,0000000000000000 > mfi0: 5554 (boot + 89s/0x0002/info) - PD 0e(e0xff/s14) FRU is 42D0422 > mfi0: 5555 (boot + 89s/0x0002/info) - Inserted: PD 0f(e0xff/s15) > mfi0: 5556 (boot + 89s/0x0002/info) - Inserted: PD 0f(e0xff/s15) Info: > enclPd=ffff, scsiType=0, portMap=07, > sasAddr=5000c500138d5e8d,0000000000000000 > mfi0: 5557 (boot + 89s/0x0002/info) - PD 0f(e0xff/s15) FRU is 42D0422 > mfi0: 5558 (boot + 144s/0x0008/info) - Battery temperature is normal > mfi0: 5559 (308392379s/0x0020/info) - Time established as 10/09/09 > 8:32:59; (258 seconds since power on) > mfi0: 5560 (boot + 3s/0x0020/info) - Firmware initialization started > (PCI ID 0060/1000/0364/1014) > mfi0: 5561 (boot + 3s/0x0020/info) - Firmware version 1.40.62-0691 > mfi0: 5562 (boot + 3s/0x0020/info) - Firmware initialization started (PCI ID 006 > 0/1000/0364/1014) > mfi0: 5563 (boot + 3s/0x0020/info) - Firmware version 1.40.62-0691 > mfi0: 5564 (boot + 64s/0x0008/info) - Battery Present > mfi0: 5565 (boot + 64s/0x0020/info) - BBU FRU is > mfi0: 5566 (boot + 64s/0x0020/info) - Board Revision > mfi0: 5567 (boot + 89s/0x0002/info) - Inserted: PD 08(e0xff/s8) > mfi0: 5568 (boot + 89s/0x0002/info) - Inserted: PD 08(e0xff/s8) Info: > enclPd=ffff, scsiType=0, portMap=00, > sasAddr=5000c500138d46b5,0000000000000000 > mfi0: 5569 (boot + 89s/0x0002/info) - PD 08(e0xff/s8) FRU is 42D0422 > mfi0: 5570 (boot + 89s/0x0002/info) - Inserted: PD 09(e0xff/s9) > mfi0: 5571 (boot + 89s/0x0002/info) - Inserted: PD 09(e0xff/s9) Info: > enclPd=ffff, scsiType=0, portMap=01, > sasAddr=5000c500138d842d,0000000000000000 > mfi0: 5572 (boot + 89s/0x0002/info) - PD 09(e0xff/s9) FRU is 42D0422 > mfi0: 5573 (boot + 89s/0x0002/info) - Inserted: PD 0a(e0xff/s10) > mfi0: 5574 (boot + 89s/0x0002/info) - Inserted: PD 0a(e0xff/s10) Info: > enclPd=ffff, scsiType=0, portMap=04, > sasAddr=5000c500138d7d75,0000000000000000 > mfi0: 5575 (boot + 89s/0x0002/info) - PD 0a(e0xff/s10) FRU is 42D0422 > mfi0: 5576 (boot + 89s/0x0002/info) - Inserted: PD 0b(e0xff/s11) > mfi0: 5577 (boot + 89s/0x0002/info) - Inserted: PD 0b(e0xff/s11) Info: > enclPd=ffff, scsiType=0, portMap=05, > sasAddr=5000c500138d7835,0000000000000000 > mfi0: 5578 (boot + 89s/0x0002/info) - PD 0b(e0xff/s11) FRU is 42D0422 > mfi0: 5579 (boot + 89s/0x0002/info) - Inserted: PD 0c(e0xff/s12) > mfi0: 5580 (boot + 89s/0x0002/info) - Inserted: PD 0c(e0xff/s12) Info: > enclPd=ffff, scsiType=0, portMap=02, > sasAddr=5000c500138d60b5,0000000000000000 > mfi0: 5581 (boot + 89s/0x0002/info) - PD 0c(e0xff/s12) FRU is 42D0422 > mfi0: 5582 (boot + 89s/0x0002/info) - Inserted: PD 0d(e0xff/s13) > mfi0: 5583 (boot + 89s/0x0002/info) - Inserted: PD 0d(e0xff/s13) Info: > enclPd=ffff, scsiType=0, portMap=03, > sasAddr=5000c500138d7bdd,0000000000000000 > mfi0: 5584 (boot + 89s/0x0002/info) - PD 0d(e0xff/s13) FRU is 42D0422 > mfi0: 5585 (boot + 89s/0x0002/info) - Inserted: PD 0e(e0xff/s14) > mfi0: 5586 (boot + 89s/0x0002/info) - Inserted: PD 0e(e0xff/s14) Info: > enclPd=ffff, scsiType=0, portMap=06, > sasAddr=5000c500138d6839,0000000000000000 > mfi0: 5587 (boot + 89s/0x0002/info) - PD 0e(e0xff/s14) FRU is 42D0422 > mfi0: 5588 (boot + 89s/0x0002/info) - Inserted: PD 0f(e0xff/s15) > mfi0: 5589 (boot + 89s/0x0002/info) - Inserted: PD 0f(e0xff/s15) Info: > enclPd=ffff, scsiType=0, portMap=07, > sasAddr=5000c500138d5e8d,0000000000000000 > mfi0: 5590 (boot + 89s/0x0002/info) - PD 0f(e0xff/s15) FRU is 42D0422 > mfi0: 5591 (boot + 144s/0x0008/info) - Battery temperature is normal > mfi0: 5592 (308392995s/0x0020/info) - Time established as 10/09/09 > 8:43:15; (259 seconds since power on) > mfi0: 5593 (boot + 3s/0x0020/info) - Firmware initialization started > (PCI ID 0060/1000/0364/1014) > mfi0: 5594 (boot + 3s/0x0020/info) - Firmware version 1.40.62-0691 > mfi0: 5595 (boot + 3s/0x0020/info) - Firmware initialization started > (PCI ID 0060/1000/0364/1014) > mfi0: 5596 (boot + 3s/0x0020/info) - Firmware version 1.40.62-0691 > mfi0: 5597 (boot + 64s/0x0008/info) - Battery Present > mfi0: 5598 (boot + 64s/0x0020/info) - BBU FRU is > mfi0: 5599 (boot + 64s/0x0020/info) - Board Revision > mfi0: 5600 (boot + 89s/0x0002/info) - Inserted: PD 08(e0xff/s8) > mfi0: 5601 (boot + 89s/0x0002/info) - Inserted: PD 08(e0xff/s8) Info: > enclPd=ffff, scsiType=0, portMap=00, > sasAddr=5000c500138d46b5,0000000000000000 > mfi0: 5602 (boot + 89s/0x0002/info) - PD 08(e0xff/s8) FRU is 42D0422 > mfi0: 5603 (boot + 89s/0x0002/info) - Inserted: PD 09(e0xff/s9) > mfi0: 5604 (boot + 89s/0x0002/info) - Inserted: PD 09(e0xff/s9) Info: > enclPd=ffff, scsiType=0, portMap=01, > sasAddr=5000c500138d842d,0000000000000000 > mfi0: 5605 (boot + 89s/0x0002/info) - PD 09(e0xff/s9) FRU is 42D0422 > mfi0: 5606 (boot + 89s/0x0002/info) - Inserted: PD 0a(e0xff/s10) > mfi0: 5607 (boot + 89s/0x0002/info) - Inserted: PD 0a(e0xff/s10) Info: > enclPd=ffff, scsiType=0, portMap=04, > sasAddr=5000c500138d7d75,0000000000000000 > mfi0: 5608 (boot + 89s/0x0002/info) - PD 0a(e0xff/s10) FRU is 42D0422 > mfi0: 5609 (boot + 89s/0x0002/info) - Inserted: PD 0b(e0xff/s11) > mfi0: 5610 (boot + 89s/0x0002/info) - Inserted: PD 0b(e0xff/s11) Info: > enclPd=ffff, scsiType=0, portMap=05, > sasAddr=5000c500138d7835,0000000000000000 > mfi0: 5611 (boot + 89s/0x0002/info) - PD 0b(e0xff/s11) FRU is 42D0422 > mfi0: 5612 (boot + 89s/0x0002/info) - Inserted: PD 0c(e0xff/s12) > mfi0: 5613 (boot + 89s/0x0002/info) - Inserted: PD 0c(e0xff/s12) Info: > enclPd=ffff, scsiType=0, portMap=02, > sasAddr=5000c500138d60b5,0000000000000000 > mfi0: 5614 (boot + 89s/0x0002/info) - PD 0c(e0xff/s12) FRU is 42D0422 > mfi0: 5615 (boot + 89s/0x0002/info) - Inserted: PD 0d(e0xff/s13) > mfi0: 5616 (boot + 89s/0x0002/info) - Inserted: PD 0d(e0xff/s13) Info: > enclPd=ffff, scsiType=0, portMap=03, > sasAddr=5000c500138d7bdd,0000000000000000 > mfi0: 5617 (boot + 89s/0x0002/info) - PD 0d(e0xff/s13) FRU is 42D0422 > mfi0: 5618 (boot + 89s/0x0002/info) - Inserted: PD 0e(e0xff/s14) > mfi0: 5619 (boot + 89s/0x0002/info) - Inserted: PD 0e(e0xff/s14) Info: > enclPd=ffff, scsiType=0, portMap=06, > sasAddr=5000c500138d6839,0000000000000000 > mfi0: 5620 (boot + 89s/0x0002/info) - PD 0e(e0xff/s14) FRU is 42D0422 > mfi0: 5621 (boot + 89s/0x0002/info) - Inserted: PD 0f(e0xff/s15) > mfi0: 5622 (boot + 89s/0x0002/info) - Inserted: PD 0f(e0xff/s15) Info: > enclPd=ffff, scsiType=0, portMap=07, > sasAddr=5000c500138d5e8d,0000000000000000 > mfi0: 5623 (boot + 89s/0x0002/info) - PD 0f(e0xff/s15) FRU is 42D0422 > mfi0: 5624 (boot + 144s/0x0008/info) - Battery temperature is normal > mfi0: 5625 (308393612s/0x0020/info) - Time established as 10/09/09 > 8:53:32; (261 seconds since power on) > mfi0: 5626 (boot + 3s/0x0020/info) - Firmware initialization started > (PCI ID 0060/1000/0364/1014) > mfi0: 5627 (boot + 3s/0x0020/info) - Firmware version 1.40.62-0691 > mfi0: 5628 (boot + 3s/0x0020/info) - Firmware initialization started > (PCI ID 0060/1000/0364/1014) > mfi0: 5629 (boot + 3s/0x0020/info) - Firmware version 1.40.62-0691 > mfi0: 5630 (boot + 64s/0x0008/info) - Battery Present > mfi0: 5631 (boot + 64s/0x0020/info) - BBU FRU is > mfi0: 5632 (boot + 64s/0x0020/info) - Board Revision > mfi0: 5633 (boot + 89s/0x0002/info) - Inserted: PD 08(e0xff/s8) > mfi0: 5634 (boot + 89s/0x0002/info) - Inserted: PD 08(e0xff/s8) Info: > enclPd=ffff, scsiType=0, portMap=00, > sasAddr=5000c500138d46b5,0000000000000000 > mfi0: 5635 (boot + 89s/0x0002/info) - PD 08(e0xff/s8) FRU is 42D0422 > mfi0: 5636 (boot + 89s/0x0002/info) - Inserted: PD 09(e0xff/s9) > mfi0: 5637 (boot + 89s/0x0002/info) - Inserted: PD 09(e0xff/s9) Info: > enclPd=ffff, scsiType=0, portMap=01, > sasAddr=5000c500138d842d,0000000000000000 > mfi0: 5638 (boot + 89s/0x0002/info) - PD 09(e0xff/s9) FRU is 42D0422 > mfi0: 5639 (boot + 89s/0x0002/info) - Inserted: PD 0a(e0xff/s10) > mfi0: 5640 (boot + 89s/0x0002/info) - Inserted: PD 0a(e0xff/s10) Info: > enclPd=ffff, scsiType=0, portMap=04, > sasAddr=5000c500138d7d75,0000000000000000 > mfi0: 5641 (boot + 89s/0x0002/info) - PD 0a(e0xff/s10) FRU is 42D0422 > mfi0: 5642 (boot + 89s/0x0002/info) - Inserted: PD 0b(e0xff/s11) > mfi0: 5643 (boot + 89s/0x0002/info) - Inserted: PD 0b(e0xff/s11) Info: > enclPd=ffff, scsiType=0, portMap=05, > sasAddr=5000c500138d7835,0000000000000000 > mfi0: 5644 (boot + 89s/0x0002/info) - PD 0b(e0xff/s11) FRU is 42D0422 > mfi0: 5645 (boot + 89s/0x0002/info) - Inserted: PD 0c(e0xff/s12) > mfi0: 5646 (boot + 89s/0x0002/info) - Inserted: PD 0c(e0xff/s12) Info: > enclPd=ffff, scsiType=0, portMap=02, > sasAddr=5000c500138d60b5,0000000000000000 > mfi0: 5647 (boot + 89s/0x0002/info) - PD 0c(e0xff/s12) FRU is 42D0422 > mfi0: 5648 (boot + 89s/0x0002/info) - Inserted: PD 0d(e0xff/s13) > mfi0: 5649 (boot + 89s/0x0002/info) - Inserted: PD 0d(e0xff/s13) Info: > enclPd=ffff, scsiType=0, portMap=03, > sasAddr=5000c500138d7bdd,0000000000000000 > mfi0: 5650 (boot + 89s/0x0002/info) - PD 0d(e0xff/s13) FRU is 42D0422 > mfi0: 5651 (boot + 89s/0x0002/info) - Inserted: PD 0e(e0xff/s14) > mfi0: 5652 (boot + 89s/0x0002/info) - Inserted: PD 0e(e0xff/s14) Info: > enclPd=ffff, scsiType=0, portMap=06, > sasAddr=5000c500138d6839,0000000000000000 > mfi0: 5653 (boot + 89s/0x0002/info) - PD 0e(e0xff/s14) FRU is 42D0422 > mfi0: 5654 (boot + 89s/0x0002/info) - Inserted: PD 0f(e0xff/s15) > mfi0: 5655 (boot + 89s/0x0002/info) - Inserted: PD 0f(e0xff/s15) Info: > enclPd=ffff, scsiType=0, portMap=07, > sasAddr=5000c500138d5e8d,0000000000000000 > mfi0: 5656 (boot + 89s/0x0002/info) - PD 0f(e0xff/s15) FRU is 42D0422 > mfi0: 5657 (boot + 144s/0x0008/info) - Battery temperature is normal > mfi0: 5658 (308394231s/0x0020/info) - Time established as 10/09/09 > 9:03:51; (262 seconds since power on) > mfi0: 5659 (boot + 3s/0x0020/info) - Firmware initialization started > (PCI ID 0060/1000/0364/1014) > mfi0: 5660 (boot + 3s/0x0020/info) - Firmware version 1.40.62-0691 > mfi0: 5661 (boot + 3s/0x0020/info) - Firmware initialization started > (PCI ID 0060/1000/0364/1014) > mfi0: 5662 (boot + 3s/0x0020/info) - Firmware version 1.40.62-0691 > mfi0: 5663 (boot + 64s/0x0008/info) - Battery Present > mfi0: 5664 (boot + 64s/0x0020/info) - BBU FRU is > mfi0: 5665 (boot + 64s/0x0020/info) - Board Revision > mfi0: 5666 (boot + 89s/0x0002/info) - Inserted: PD 08(e0xff/s8) > mfi0: 5667 (boot + 89s/0x0002/info) - Inserted: PD 08(e0xff/s8) Info: > enclPd=ffff, scsiType=0, portMap=00, > sasAddr=5000c500138d46b5,0000000000000000 > > So on. > -- wbr, pluknet From pluknet at gmail.com Thu Oct 15 12:53:08 2009 From: pluknet at gmail.com (pluknet) Date: Thu Oct 15 12:53:20 2009 Subject: mfi(4) endless loop kernel output on attach In-Reply-To: References: Message-ID: >> >> This is 7.2-R. Seen on IBM x3650M2. >> >> During the boot I get those endless looping kernel messages while on >> mfi(4) attach phase. >> It's getting more odd since 7.2 booted and worked fine on exactly this >> server model >> months ago (on different box though).. Any hints? >> > > After the looked endless loop the kernel eventually finished > the mfi(4) initialization and continued its booting. > Is it expected to do so long initialization? > Replying to myself. As someone pointed out in the private email, that's due to the large log contained on non-volatile memory in the controller. MegaCli -AdpEventLog -GetEventLogInfo -aAll cleaned up 'em all. Sorry for noise. -- wbr, pluknet From jhb at freebsd.org Thu Oct 15 13:32:48 2009 From: jhb at freebsd.org (John Baldwin) Date: Thu Oct 15 13:32:54 2009 Subject: mfi(4) endless loop kernel output on attach In-Reply-To: References: Message-ID: <200910150853.49850.jhb@freebsd.org> On Thursday 15 October 2009 5:51:19 am pluknet wrote: > Hi. > > This is 7.2-R. Seen on IBM x3650M2. > > During the boot I get those endless looping kernel messages while on > mfi(4) attach phase. > It's getting more odd since 7.2 booted and worked fine on exactly this > server model > months ago (on different box though).. Any hints? We just had some boxes die like this (but spewing a different loop of messages on boot related to continuously scheduling patrol reads and consistency checks that finished immediately) at work. We fixed them by swapping out the controller. We might try stick them in a different box and reflashing them using mfiutil(8) to see if it's some sort of corrupted state that flashing the adapter fixes. In your case it looks lik the firmware keeps crashing and restarting. -- John Baldwin From pluknet at gmail.com Thu Oct 15 15:16:25 2009 From: pluknet at gmail.com (pluknet) Date: Thu Oct 15 15:16:37 2009 Subject: mfi(4) endless loop kernel output on attach In-Reply-To: <200910150853.49850.jhb@freebsd.org> References: <200910150853.49850.jhb@freebsd.org> Message-ID: 2009/10/15 John Baldwin : > On Thursday 15 October 2009 5:51:19 am pluknet wrote: >> Hi. >> >> This is 7.2-R. Seen on IBM x3650M2. >> >> During the boot I get those endless looping kernel messages while on >> mfi(4) attach phase. >> It's getting more odd since 7.2 booted and worked fine on exactly this >> server model >> months ago (on different box though).. Any hints? > > We just had some boxes die like this (but spewing a different loop of messages > on boot related to continuously scheduling patrol reads and consistency > checks that finished immediately) at work. ?We fixed them by swapping out the > controller. ?We might try stick them in a different box and reflashing them > using mfiutil(8) to see if it's some sort of corrupted state that flashing > the adapter fixes. > > In your case it looks lik the firmware keeps crashing and restarting. Probably it is. Though clearing logs helped me. -- wbr, pluknet From jhb at freebsd.org Thu Oct 15 19:18:27 2009 From: jhb at freebsd.org (John Baldwin) Date: Thu Oct 15 19:18:33 2009 Subject: mfi(4) endless loop kernel output on attach In-Reply-To: References: <200910150853.49850.jhb@freebsd.org> Message-ID: <200910151135.04382.jhb@freebsd.org> On Thursday 15 October 2009 11:16:23 am pluknet wrote: > 2009/10/15 John Baldwin : > > On Thursday 15 October 2009 5:51:19 am pluknet wrote: > >> Hi. > >> > >> This is 7.2-R. Seen on IBM x3650M2. > >> > >> During the boot I get those endless looping kernel messages while on > >> mfi(4) attach phase. > >> It's getting more odd since 7.2 booted and worked fine on exactly this > >> server model > >> months ago (on different box though).. Any hints? > > > > We just had some boxes die like this (but spewing a different loop of messages > > on boot related to continuously scheduling patrol reads and consistency > > checks that finished immediately) at work. ?We fixed them by swapping out the > > controller. ?We might try stick them in a different box and reflashing them > > using mfiutil(8) to see if it's some sort of corrupted state that flashing > > the adapter fixes. > > > > In your case it looks lik the firmware keeps crashing and restarting. > > Probably it is. Though clearing logs helped me. Well, from your other e-mail it seems it was just dumping lots of old logs since the previous clean shutdown. (I almost mentioned that case in my original e-mail). In that case you can simply let it finish walking through all the logs or you can set loader tunables to raise the minimum class of message so it skips all the lower priority info messages when walking the log. -- John Baldwin From bugmaster at FreeBSD.org Mon Oct 19 11:07:01 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Oct 19 11:09:30 2009 Subject: Current problem reports assigned to freebsd-scsi@FreeBSD.org Message-ID: <200910191107.n9JB7018063561@freefall.freebsd.org> 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 kern/138789 scsi [cam] [patch] cd(4) patch for drives/discs failing the o kern/138384 scsi [ips] [patch] NULL pointer dereference in ipsd_dump() o kern/138379 scsi [aic7xxx] [patch] Memory leak in output_listing() in f o kern/138376 scsi [cam] [patch] Memory leak in scsi_low_attach_xs() in f o kern/134488 scsi [mpt] MPT SCSI driver probes max. 8 LUNs per device 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 41 problems total. From therion at ninth-art.de Mon Oct 19 21:12:01 2009 From: therion at ninth-art.de (Georg Bege) Date: Mon Oct 19 21:12:17 2009 Subject: LSI Logic SAS3442E or SAS3041E supported by FBSD8 Message-ID: <8f17fd2b7344832857543f5dc96dc2c7.squirrel@webmail.coruscant.info> Hello guys Does anyone know if this two controllers (or either one) are supported by FBSD8? It's LSI's SAS3442E and SAS3041E... if someone knows it would be great. cheers -- Georg 'Therion' Bege http://coruscant.info http://www.ninth-art.de therion@ninth-art.de GnuPG-Key-ID: 0x5717E214 FingerPrint: A8EC B4B2 C9A9 483B CC87 56EE 07A1 C78E 5717 E214 !DSPAM:4adcd61d651039587040467! From damianm at esi.com.au Mon Oct 19 21:36:11 2009 From: damianm at esi.com.au (Damian McGuckin) Date: Mon Oct 19 21:36:18 2009 Subject: LSI Logic SAS3442E or SAS3041E supported by FBSD8 In-Reply-To: <8f17fd2b7344832857543f5dc96dc2c7.squirrel@webmail.coruscant.info> References: <8f17fd2b7344832857543f5dc96dc2c7.squirrel@webmail.coruscant.info> Message-ID: On Mon, 19 Oct 2009, Georg Bege wrote: > Does anyone know if this two controllers (or either one) are supported by > FBSD8? > It's LSI's SAS3442E and SAS3041E... if someone knows it would be great. The second for has been working with at least 7. No experience with the first. - Damian Pacific Engineering Systems International, 277-279 Broadway, Broadway NSW 2007 Ph:+61-2-8571-0847 .. Fx:+61-2-9692-9623 | unsolicited email not wanted here ! Views and opinions here are mine and not those of any past or present employer From brueffer at FreeBSD.org Wed Oct 21 14:10:10 2009 From: brueffer at FreeBSD.org (brueffer@FreeBSD.org) Date: Wed Oct 21 14:10:16 2009 Subject: kern/138379: [aic7xxx] [patch] Memory leak in output_listing() in file sys/dev/aic7xxx/aicasm/aicasm.c Message-ID: <200910211410.n9LEA8OG005664@freefall.freebsd.org> Synopsis: [aic7xxx] [patch] Memory leak in output_listing() in file sys/dev/aic7xxx/aicasm/aicasm.c State-Changed-From-To: open->patched State-Changed-By: brueffer State-Changed-When: Wed Oct 21 16:09:21 CEST 2009 State-Changed-Why: Leak plugged, thanks for the report! Responsible-Changed-From-To: freebsd-scsi->brueffer Responsible-Changed-By: brueffer Responsible-Changed-When: Wed Oct 21 16:09:21 CEST 2009 Responsible-Changed-Why: MFC reminder. http://www.freebsd.org/cgi/query-pr.cgi?pr=138379 From brueffer at FreeBSD.org Wed Oct 21 15:06:08 2009 From: brueffer at FreeBSD.org (brueffer@FreeBSD.org) Date: Wed Oct 21 15:06:17 2009 Subject: kern/138384: [ips] [patch] NULL pointer dereference in ipsd_dump() in file sys/dev/ips/ips_disk.c Message-ID: <200910211506.n9LF67Zm056912@freefall.freebsd.org> Synopsis: [ips] [patch] NULL pointer dereference in ipsd_dump() in file sys/dev/ips/ips_disk.c State-Changed-From-To: open->patched State-Changed-By: brueffer State-Changed-When: Wed Oct 21 17:05:02 CEST 2009 State-Changed-Why: Committed, thanks! Responsible-Changed-From-To: freebsd-scsi->brueffer Responsible-Changed-By: brueffer Responsible-Changed-When: Wed Oct 21 17:05:02 CEST 2009 Responsible-Changed-Why: MFC reminder. http://www.freebsd.org/cgi/query-pr.cgi?pr=138384 From brueffer at FreeBSD.org Thu Oct 22 06:13:48 2009 From: brueffer at FreeBSD.org (brueffer@FreeBSD.org) Date: Thu Oct 22 06:13:55 2009 Subject: kern/138376: [cam] [patch] Memory leak in scsi_low_attach_xs() in file sys/cam/scsi/scsi_low.c Message-ID: <200910220613.n9M6DlpP043828@freefall.freebsd.org> Synopsis: [cam] [patch] Memory leak in scsi_low_attach_xs() in file sys/cam/scsi/scsi_low.c State-Changed-From-To: open->patched State-Changed-By: brueffer State-Changed-When: Thu Oct 22 08:13:19 CEST 2009 State-Changed-Why: Committed, thanks! Responsible-Changed-From-To: freebsd-scsi->brueffer Responsible-Changed-By: brueffer Responsible-Changed-When: Thu Oct 22 08:13:19 CEST 2009 Responsible-Changed-Why: MFC reminder. http://www.freebsd.org/cgi/query-pr.cgi?pr=138376 From pluknet at gmail.com Thu Oct 22 14:30:25 2009 From: pluknet at gmail.com (pluknet) Date: Thu Oct 22 14:30:32 2009 Subject: mfi(4) endless loop kernel output on attach In-Reply-To: <200910150853.49850.jhb@freebsd.org> References: <200910150853.49850.jhb@freebsd.org> Message-ID: 2009/10/15 John Baldwin : > On Thursday 15 October 2009 5:51:19 am pluknet wrote: >> Hi. >> >> This is 7.2-R. Seen on IBM x3650M2. >> >> During the boot I get those endless looping kernel messages while on >> mfi(4) attach phase. >> It's getting more odd since 7.2 booted and worked fine on exactly this >> server model >> months ago (on different box though).. Any hints? > > We just had some boxes die like this (but spewing a different loop of messages > on boot related to continuously scheduling patrol reads and consistency > checks that finished immediately) at work. ?We fixed them by swapping out the > controller. ?We might try stick them in a different box and reflashing them > using mfiutil(8) to see if it's some sort of corrupted state that flashing > the adapter fixes. > > In your case it looks lik the firmware keeps crashing and restarting. > Some more thoughts.. There was a problem I got with 'MegaCli -AdpBbuCmd -BbuLearn -aall' command. On 6.2-R process slept on mfiwait wchan: db> bt 14734 Tracing pid 14734 tid 100135 td 0xc93f8190 sched_switch(c93f8190,0,1) at sched_switch+0x143 mi_switch(1,0,c93f8190,f9a32acc,c06a43a4,...) at mi_switch+0x1ba sleepq_switch(c8c6b0d0) at sleepq_switch+0x87 sleepq_wait(c8c6b0d0,0,c93f8190,c8c6b0d0,c8c25800,...) at sleepq_wait+0x5c msleep(c8c6b0d0,c8c25954,4c,c090acbc,0) at msleep+0x269 mfi_wait_command(c8c25800,c8c6b0d0,0,0,cc382460,...) at mfi_wait_command+0xa8 mfi_ioctl(c8c31300,c1144d01,cc870a00,1,c93f8190,...) at mfi_ioctl+0x485 devfs_ioctl_f(c90a2750,c1144d01,cc870a00,c9048000,c93f8190) at devfs_ioctl_f+0xaf ioctl(c93f8190,f9a32d04) at ioctl+0x445 syscall(3b,3b,3b,0,bfbfedc0,...) at syscall+0x2bf Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (54, FreeBSD ELF32, ioctl), eip = 0x8177207, esp = 0xbfbfe88c, ebp = 0xbfbfe8b8 --- Then: mfi0: COMMAND 0xc8c6b0d0 TIMEOUT AFTER 51 SECONDS mfi0: COMMAND 0xc8c61d50 TIMEOUT AFTER 49 SECONDS mfi0: COMMAND 0xc8c61850 TIMEOUT AFTER 49 SECONDS On 6.4-R MegaCli throws a page fault due to NULL deref in mfi_data_cb():cm->cm_sg (see below). There was past 6.4 backport mentioning "fix some bugs in the API for the management ioctl." With this patch I have no longer panic and/or locks. Thanks to LSI now on 7.2-R (and on patched 6.4-R) it returns an error: # ./MegaCli -AdpBbuCmd -BbuLearn -aall Adapter 0: BBU Learn Failed Exit Code: 0x32 db> bt Tracing pid 43059 tid 101363 td 0xcf46e680 mfi_data_cb(c9cfae00,c9cc3e00,1,0) at mfi_data_cb+0x5e bus_dmamap_load(c9cd7c80,0,caf86270,0,c0597240,c9cfae00,0) at bus_dmamap_load+0x4a1 mfi_mapcmd(c9cc3800,c9cfae00) at mfi_mapcmd+0x31 mfi_startio(c9cc3800) at mfi_startio+0x9b mfi_wait_command(c9cc3800,c9cfae00,0,0,caf86270,...) at mfi_wait_command+0x89 mfi_ioctl(c9cf7200,c1144d01,d3fb6200,1,cf46e680,...) at mfi_ioctl+0x52a devfs_ioctl_f(d1a551b0,c1144d01,d3fb6200,cbf52c80,cf46e680) at devfs_ioctl_f+0xaf ioctl(cf46e680,fbd91d04) at ioctl+0x445 syscall(3b,3b,3b,0,bfbfedc0,...) at syscall+0x2bf Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (54, FreeBSD ELF32, ioctl), eip = 0x8177207, esp = 0xbfbfe88c, ebp = 0xbfbfe8b8 #9 0xc08cbb1a in calltrap () at /usr/src/sys/i386/i386/exception.s:139 #10 0xc059729e in mfi_data_cb (arg=0xc8a744b0, segs=0xc8a49e00, nsegs=1, ---Type to continue, or q to quit--- error=0) at /usr/src/sys/dev/mfi/mfi.c:1488 #11 0xc08c7afd in bus_dmamap_load (dmat=0xc8a6f100, map=0xac89e000, buf=0xc8a5ac60, buflen=0, callback=0xc0597240 , callback_arg=0xc8a744b0, flags=0) at /usr/src/sys/i386/i386/busdma_machdep.c:733 #12 0xc059721d in mfi_mapcmd (sc=0xc8a49800, cm=0xc8a49e00) at /usr/src/sys/dev/mfi/mfi.c:1452 #13 0xc0597177 in mfi_startio (sc=0xc8a49800) at /usr/src/sys/dev/mfi/mfi.c:1436 #14 0xc0595f09 in mfi_wait_command (sc=0xc8a49800, cm=0xc8a744b0) at /usr/src/sys/dev/mfi/mfi.c:822 #15 0xc059840a in mfi_ioctl (dev=0xac89e000, cmd=0, arg=0xc8de8800 "", flag=1, td=0xc8a5ac60) at /usr/src/sys/dev/mfi/mfi.c:2061 #16 0xc06598b7 in devfs_ioctl_f (fp=0xc902dc18, com=3239333121, data=0xc8de8800, cred=0xc9052980, td=0xc8e2dd00) at /usr/src/sys/fs/devfs/devfs_vnops.c:480 #17 0xc06d3a11 in ioctl (td=0xc8e2dd00, uap=0xeb37bd04) at file.h:265 (kgdb) f 10 #10 0xc059729e in mfi_data_cb (arg=0xc8a744b0, segs=0xc8a49e00, nsegs=1, error=0) at /usr/src/sys/dev/mfi/mfi.c:1488 1488 sgl->sg32[i].addr = segs[i].ds_addr; (kgdb) list 1483 return; 1484 } 1485 1486 if ((sc->mfi_flags & MFI_FLAGS_SG64) == 0) { 1487 for (i = 0; i < nsegs; i++) { 1488 sgl->sg32[i].addr = segs[i].ds_addr; 1489 sgl->sg32[i].len = segs[i].ds_len; 1490 } 1491 } else { 1492 for (i = 0; i < nsegs; i++) { (kgdb) p i $1 = 0 (kgdb) p *segs $3 = {ds_addr = 2457600, ds_len = 65536} (kgdb) p sgl $4 = (union mfi_sgl *) 0x0 (kgdb) p *cm $6 = {cm_link = {tqe_next = 0x0, tqe_prev = 0xc8a49814}, cm_timestamp = 0, cm_sc = 0xc8a49800, cm_frame = 0xe8fee680, cm_frame_busaddr = 3748513408, cm_sense = 0xe904c780, cm_sense_busaddr = 3749103488, cm_dmamap = 0x0, cm_sg = 0x0, cm_data = 0xc8a5ac60, cm_len = 0, cm_total_frame_size = 0, cm_extra_frames = 0, cm_flags = 6, cm_aen_abort = 0, cm_complete = 0, cm_private = 0x0, cm_index = 15, cm_error = 0} -- wbr, pluknet From areilly at bigpond.net.au Sat Oct 24 03:58:17 2009 From: areilly at bigpond.net.au (Andrew Reilly) Date: Sat Oct 24 03:58:23 2009 Subject: Some questions about da0 on USB2 (recent bad behaviour) Message-ID: <20091024022238.GA9296@duncan.reilly.home> Hi there, I have a system with a couple of Western Digital "MyBook" USB2 drives connected to it, and have started seeing some odd behaviour that I am not sure how to identify the cause of. Perhaps someone could offer a suggestion or two? The behaviour that I've noticed (and I can't remember any particular event precipitating this, but I do track 8-STABLE approximately weekly, so things do change from time to time...) is that the drive will just stop for a couple of minutes, and then continue what it was doing. For a while that's all I could see: no error messages at all. The last time I booted, I turned on verbose booting and now I see that these periods of inactivity result in streams of syslog messages like: Oct 24 12:48:55 duncan kernel: (da0:umass-sim0:0:0:0): Request completed with CAM_REQ_CMP_ERR Oct 24 12:48:55 duncan kernel: (da0:umass-sim0:0:0:0): Retrying Command Oct 24 12:50:24 duncan kernel: (da0:umass-sim0:0:0:0): Request completed with CAM_REQ_CMP_ERR Oct 24 12:50:24 duncan kernel: (da0:umass-sim0:0:0:0): Retrying Command The retry seems to be successful, because I'm not getting any hard error messages anywhere, and the disk activity does seem to proceed afterwards. The disk drive isn't making any bad/broken noises, either. That drive is, according to dmesg.boot: ugen1.2: at usbus1 umass0: on usbus1 umass0: SCSI over Bulk-Only; quirks = 0x0000 Root mount waiting for: usbus1 umass0:1:0:-1: Attached to scbus1 (probe0:umass-sim0:0:0:0): Down reving Protocol Version from 2 to 0? pass0 at umass-sim0 bus 0 target 0 lun 0 pass0: Fixed Direct Access SCSI-0 device pass0: 40.000MB/s transfers GEOM: new disk da0 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 715404MB (1465149168 512 byte sectors: 255H 63S/T 91201C) What is the likelihood that these pauses and command retries are a sign that this specific drive is in the process of dying, physically? If that were the case, are there any diagnostic tools that I could run against it to show, say, internal error logs? What is the significance of the "sim" part of the device designation umass-sim0? I've looked in all of the manual pages I can think of, but that clearly isn't enough. usbdevs -v says "no USB controllers found", which I thought a bit unuseful. I assume it is *supposed* to work, is there a trick? usbconfig shows my connected USB devices and hubs: ugen0.1: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen1.1: at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen1.2: at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen1.3: at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen0.2: at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen0.3: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON At this rate the dump/restore backup that I'm running to get the data off it will take a little over a day to finish (according to dump), even though systat shows the drive doing about 8MB/s while it's working, which would allow the dump to finish in about eight hours. These modern, large drives are all very well, but they make doing any kind of system reconfiguration or backup really time consuming... Cheers, -- Andrew From areilly at bigpond.net.au Sat Oct 24 09:29:01 2009 From: areilly at bigpond.net.au (Andrew Reilly) Date: Sat Oct 24 09:29:14 2009 Subject: Some questions about da0 on USB2 (recent bad behaviour) In-Reply-To: <20091024022238.GA9296@duncan.reilly.home> References: <20091024022238.GA9296@duncan.reilly.home> Message-ID: <20091024092846.GA68657@duncan.reilly.home> Just a follow-up with some more information: I now doubt that the problem that I reported in the original message is the drive dying: I've just done some read tests (cat largefile >/dev/null) on the other USB2-attached drive (also a Western Digital MyBook, but this one is a USB2+Firewire one with 1TB, while the other one was just USB2 with 750G.) I'm seeing essentially the same behaviour on that drive, too. That is: it seems to work fine for some fraction of a minute (doesn't seem to be longer than a minute, anyway), and then stops completely for several minutes (processes reading or writing sit in "D" state in ps) and then starts again, after logging "Request completed with CAM_REQ_CMP_ERR\nRetrying Command". I reckon that the duty cycle of useful behaviour is is a bit less than a third. Any chance this is some new badness in the USB+umass stack? Anything that I can poke or prod to make it behave better? Any way that I can find out where it's going awry? I don't have kdb in my kernel, but everything not directly connected to these USB devices seem to be behaving themselves completely. Oh: stoppage on the two drives doesn't seem to be chronologically correllated. Cheers, -- Andrew From rea-fbsd at codelabs.ru Sat Oct 24 19:50:03 2009 From: rea-fbsd at codelabs.ru (Eygene Ryabinkin) Date: Sat Oct 24 19:50:09 2009 Subject: kern/130735: [patch] pass M_NOWAIT to the malloc() call inside cdreaddvdstructure() Message-ID: <200910241950.n9OJo3lA007687@freefall.freebsd.org> The following reply was made to PR kern/130735; it has been noted by GNATS. From: Eygene Ryabinkin To: bug-followup@FreeBSD.org Cc: mav@freebsd.org, scottl@freebsd.org Subject: Re: kern/130735: [patch] pass M_NOWAIT to the malloc() call inside cdreaddvdstructure() Date: Sat, 24 Oct 2009 23:40:43 +0400 Gentlemen, good day. I am feeling myself lucky today -- may be someone will be able to look at this PR and fix the bad malloc() invocation? Thanks! -- Eygene _ ___ _.--. # \`.|\..----...-'` `-._.-'_.-'` # Remember that it is hard / ' ` , __.--' # to read the on-line manual )/' _/ \ `-_, / # while single-stepping the kernel. `-'" `"\_ ,_.-;_.-\_ ', fsc/as # _.-'_./ {_.' ; / # -- FreeBSD Developers handbook {_.-``-' {_/ # From dan at langille.org Mon Oct 26 02:40:16 2009 From: dan at langille.org (Dan Langille) Date: Mon Oct 26 02:40:30 2009 Subject: tape library and a stand-alone tape Message-ID: <4AE50853.4000603@langille.org> I'm trying to add a tape library to an existing system. And I've run into a problem. I think it is related to having two tape drives in the same system, but I'm not sure. I *think* the problem is device numbering. e.g. sa0 versus sa1. What should I be reading to tie a given physical SCSI device to a particular /dev/ entry? If you're curious: http://www.freebsddiary.org/tape-library.php Thank you. From jh at FreeBSD.org Mon Oct 26 09:20:05 2009 From: jh at FreeBSD.org (Jaakko Heinonen) Date: Mon Oct 26 09:20:19 2009 Subject: kern/130735: [patch] pass M_NOWAIT to the malloc() call inside cdreaddvdstructure() Message-ID: <200910260920.n9Q9K5uR048430@freefall.freebsd.org> The following reply was made to PR kern/130735; it has been noted by GNATS. From: Jaakko Heinonen To: Eygene Ryabinkin Cc: bug-followup@FreeBSD.org Subject: Re: kern/130735: [patch] pass M_NOWAIT to the malloc() call inside cdreaddvdstructure() Date: Mon, 26 Oct 2009 11:19:20 +0200 Hi, On 2009-10-24, Eygene Ryabinkin wrote: > I am feeling myself lucky today -- may be someone will be able > to look at this PR and fix the bad malloc() invocation? I have been looking at this. The same problem also exists in cdreportkey() and cdsendkey(). I think that it's better to drop periph lock while doing M_WAITOK malloc instead of using M_NOWAIT. Could you test and look at this patch: http://www.saunalahti.fi/~jh3/patches/scsi_cd-M_WAITOK-fixes.diff -- Jaakko From bugmaster at FreeBSD.org Mon Oct 26 11:07:07 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Oct 26 11:09:50 2009 Subject: Current problem reports assigned to freebsd-scsi@FreeBSD.org Message-ID: <200910261107.n9QB76GJ043878@freefall.freebsd.org> 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 kern/138789 scsi [cam] [patch] cd(4) patch for drives/discs failing the o kern/134488 scsi [mpt] MPT SCSI driver probes max. 8 LUNs per device 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 38 problems total. From dan at langille.org Wed Oct 28 01:39:09 2009 From: dan at langille.org (Dan Langille) Date: Wed Oct 28 01:39:15 2009 Subject: tape changer, but not tape drive Message-ID: <4AE7A0BB.8020402@langille.org> I first encountered this problem in April, now I'm back to it: http://lists.freebsd.org/pipermail/freebsd-scsi/2008-April/003452.html In short, the system has tape library. The library has worked in the past (http://www.freebsddiary.org/digital-tl891.php) but now it does not. I can see either the tape library or the tape drive. Which I see depends upon the cable configuration. http://www.freebsddiary.org/images/tape-libraries-cables.jpg As shown above, that's how I would expect things to work normally. However, in that configuration, I do not see the tape drive. The cable going down, goes to the computer. If I reconnect that cable to the plug to the left of the terminator, the system can see the DLT drive, but not the tape library. Under 6.3-STABLE FreeBSD, I can see either one device or the other. ch0 at ahc0 bus 0 target 0 lun 0 ch0: Removable Changer SCSI-2 device ch0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit) ch0: 10 slots, 1 drive, 1 picker, 0 portals or sa0 at ahc0 bus 0 target 1 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit) acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x40 0x00 0x01 Any ideas? Full dmesg output here: http://www.langille.org/tmp/dmesg.boot TIA. From mcdouga9 at egr.msu.edu Wed Oct 28 02:44:30 2009 From: mcdouga9 at egr.msu.edu (Adam McDougall) Date: Wed Oct 28 02:44:36 2009 Subject: tape changer, but not tape drive In-Reply-To: <4AE7A0BB.8020402@langille.org> References: <4AE7A0BB.8020402@langille.org> Message-ID: <20091028021932.GL62972@egr.msu.edu> On Tue, Oct 27, 2009 at 09:39:07PM -0400, Dan Langille wrote: I first encountered this problem in April, now I'm back to it: http://lists.freebsd.org/pipermail/freebsd-scsi/2008-April/003452.html In short, the system has tape library. The library has worked in the past (http://www.freebsddiary.org/digital-tl891.php) but now it does not. I can see either the tape library or the tape drive. Which I see depends upon the cable configuration. http://www.freebsddiary.org/images/tape-libraries-cables.jpg As shown above, that's how I would expect things to work normally. However, in that configuration, I do not see the tape drive. The cable going down, goes to the computer. If I reconnect that cable to the plug to the left of the terminator, the system can see the DLT drive, but not the tape library. Under 6.3-STABLE FreeBSD, I can see either one device or the other. ch0 at ahc0 bus 0 target 0 lun 0 ch0: Removable Changer SCSI-2 device ch0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit) ch0: 10 slots, 1 drive, 1 picker, 0 portals or sa0 at ahc0 bus 0 target 1 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit) acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x40 0x00 0x01 Any ideas? Full dmesg output here: http://www.langille.org/tmp/dmesg.boot TIA. Is it possible the middle cable is broken in some way? Perhaps you could swap it with another cable to try to find out, such as with the cable going from the library to the 2944 card. Might be intermittant and start working if bent or moved. Also can you see the connectors inside the library (on the back side of the external plate) to check if they are well seated or damaged? You could also try swapping the first and second connection or the third and fourth, or both, if it is hooked up like I think it is, those should have an equal chance of working and might reveal a bad port or partially bad port. Also try leaving off the terminator or one/both ends of the middle cable just to see if the system can tell the difference especially while booting, just to confirm if it makes any negative difference at all. From dan at langille.org Wed Oct 28 09:42:36 2009 From: dan at langille.org (Dan Langille) Date: Wed Oct 28 09:42:43 2009 Subject: tape changer, but not tape drive In-Reply-To: <20091028021932.GL62972@egr.msu.edu> References: <4AE7A0BB.8020402@langille.org> <20091028021932.GL62972@egr.msu.edu> Message-ID: <4AE8120A.70608@langille.org> Adam McDougall wrote: > On Tue, Oct 27, 2009 at 09:39:07PM -0400, Dan Langille wrote: > > I first encountered this problem in April, now I'm back to it: > > http://lists.freebsd.org/pipermail/freebsd-scsi/2008-April/003452.html > > In short, the system has tape library. The library has worked in the > past (http://www.freebsddiary.org/digital-tl891.php) but now it does > not. I can see either the tape library or the tape drive. Which I see > depends upon the cable configuration. > > http://www.freebsddiary.org/images/tape-libraries-cables.jpg > > As shown above, that's how I would expect things to work normally. > However, in that configuration, I do not see the tape drive. The cable > going down, goes to the computer. If I reconnect that cable to the plug > to the left of the terminator, the system can see the DLT drive, but not > the tape library. > > Under 6.3-STABLE FreeBSD, I can see either one device or the other. > > ch0 at ahc0 bus 0 target 0 lun 0 > ch0: Removable Changer SCSI-2 device > ch0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit) > ch0: 10 slots, 1 drive, 1 picker, 0 portals > > or > > sa0 at ahc0 bus 0 target 1 lun 0 > sa0: Removable Sequential Access SCSI-2 device > sa0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit) > acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x40 0x00 > 0x01 > > Any ideas? > > Full dmesg output here: http://www.langille.org/tmp/dmesg.boot > > TIA. > > Is it possible the middle cable is broken in some way? Perhaps you > could swap it with another cable to try to find out, such as with > the cable going from the library to the 2944 card. Might be intermittant > and start working if bent or moved. I did try that. I used the cable from my stand-alone DLT drive, which has been used before (and after) and is known to be good. > Also can you see the connectors > inside the library (on the back side of the external plate) to check > if they are well seated or damaged? I'll pull the unit apart and have a look. I have been in there before. Since it last worked, the unit has gone through two moves. > You could also try swapping the > first and second connection or the third and fourth, or both, if it is > hooked up like I think it is, those should have an equal chance of working > and might reveal a bad port or partially bad port. I did try moving the looped cable to plugs 1&2 and connecting my computer to plug 3. > Also try leaving off > the terminator or one/both ends of the middle cable just to see if the > system can tell the difference especially while booting, just to confirm > if it makes any negative difference at all. OK, I will try that. Thank you. From mcdouga9 at egr.msu.edu Wed Oct 28 13:08:19 2009 From: mcdouga9 at egr.msu.edu (Adam McDougall) Date: Wed Oct 28 13:08:26 2009 Subject: tape changer, but not tape drive In-Reply-To: <4AE8120A.70608@langille.org> References: <4AE7A0BB.8020402@langille.org> <20091028021932.GL62972@egr.msu.edu> <4AE8120A.70608@langille.org> Message-ID: <4AE84250.8020409@egr.msu.edu> Dan Langille wrote: > Adam McDougall wrote: >> On Tue, Oct 27, 2009 at 09:39:07PM -0400, Dan Langille wrote: >> >> I first encountered this problem in April, now I'm back to it: >> >> http://lists.freebsd.org/pipermail/freebsd-scsi/2008-April/003452.html >> In short, the system has tape library. The library has worked in >> the past (http://www.freebsddiary.org/digital-tl891.php) but now it >> does not. I can see either the tape library or the tape drive. >> Which I see depends upon the cable configuration. >> http://www.freebsddiary.org/images/tape-libraries-cables.jpg >> As shown above, that's how I would expect things to work >> normally. However, in that configuration, I do not see the tape >> drive. The cable going down, goes to the computer. If I reconnect >> that cable to the plug to the left of the terminator, the system >> can see the DLT drive, but not the tape library. >> Under 6.3-STABLE FreeBSD, I can see either one device or the other. >> ch0 at ahc0 bus 0 target 0 lun 0 >> ch0: Removable Changer SCSI-2 device >> ch0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit) >> ch0: 10 slots, 1 drive, 1 picker, 0 portals >> or >> sa0 at ahc0 bus 0 target 1 lun 0 >> sa0: Removable Sequential Access SCSI-2 device >> sa0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit) >> acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x40 >> 0x00 0x01 >> Any ideas? >> Full dmesg output here: http://www.langille.org/tmp/dmesg.boot >> TIA. >> Is it possible the middle cable is broken in some way? Perhaps you >> could swap it with another cable to try to find out, such as with >> the cable going from the library to the 2944 card. Might be >> intermittant >> and start working if bent or moved. > > I did try that. I used the cable from my stand-alone DLT drive, which > has been used before (and after) and is known to be good. > >> Also can you see the connectors >> inside the library (on the back side of the external plate) to check >> if they are well seated or damaged? > > I'll pull the unit apart and have a look. I have been in there > before. Since it last worked, the unit has gone through two moves. > > > You could also try swapping the >> first and second connection or the third and fourth, or both, if it is >> hooked up like I think it is, those should have an equal chance of >> working >> and might reveal a bad port or partially bad port. > > I did try moving the looped cable to plugs 1&2 and connecting my > computer to plug 3. The two plugs for each device (library, tape1, tape2) are probably tied directly together in a Y shape to the internal device so you can use them as an In/Out, so putting the looped cable on plugs 1 and 2 probably does nothing and isolates that device from the rest. As long as the looped cable is not between 1&2 or 3&4, you can probably use any other order although the manufacturer may have recommendations. I see nothing wrong with the way you appear to have cabled it but variations may reveal something. > >> Also try leaving off >> the terminator or one/both ends of the middle cable just to see if the >> system can tell the difference especially while booting, just to confirm >> if it makes any negative difference at all. > > OK, I will try that. > > Thank you. > From dan at langille.org Wed Oct 28 23:13:32 2009 From: dan at langille.org (Dan Langille) Date: Wed Oct 28 23:13:39 2009 Subject: tape changer, but not tape drive In-Reply-To: <4AE84250.8020409@egr.msu.edu> References: <4AE7A0BB.8020402@langille.org> <20091028021932.GL62972@egr.msu.edu> <4AE8120A.70608@langille.org> <4AE84250.8020409@egr.msu.edu> Message-ID: <4AE8D01A.9020707@langille.org> Adam McDougall wrote: > Dan Langille wrote: >> Adam McDougall wrote: >>> On Tue, Oct 27, 2009 at 09:39:07PM -0400, Dan Langille wrote: >>> >>> I first encountered this problem in April, now I'm back to it: >>> >>> http://lists.freebsd.org/pipermail/freebsd-scsi/2008-April/003452.html >>> In short, the system has tape library. The library has worked in >>> the past (http://www.freebsddiary.org/digital-tl891.php) but now it >>> does not. I can see either the tape library or the tape drive. >>> Which I see depends upon the cable configuration. >>> http://www.freebsddiary.org/images/tape-libraries-cables.jpg >>> As shown above, that's how I would expect things to work >>> normally. However, in that configuration, I do not see the tape >>> drive. The cable going down, goes to the computer. If I reconnect >>> that cable to the plug to the left of the terminator, the system >>> can see the DLT drive, but not the tape library. >>> Under 6.3-STABLE FreeBSD, I can see either one device or the other. >>> ch0 at ahc0 bus 0 target 0 lun 0 >>> ch0: Removable Changer SCSI-2 device >>> ch0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit) >>> ch0: 10 slots, 1 drive, 1 picker, 0 portals >>> or >>> sa0 at ahc0 bus 0 target 1 lun 0 >>> sa0: Removable Sequential Access SCSI-2 device >>> sa0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit) >>> acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x40 >>> 0x00 0x01 >>> Any ideas? >>> Full dmesg output here: http://www.langille.org/tmp/dmesg.boot >>> TIA. >>> Is it possible the middle cable is broken in some way? Perhaps you >>> could swap it with another cable to try to find out, such as with >>> the cable going from the library to the 2944 card. Might be >>> intermittant >>> and start working if bent or moved. >> >> I did try that. I used the cable from my stand-alone DLT drive, which >> has been used before (and after) and is known to be good. >> >>> Also can you see the connectors >>> inside the library (on the back side of the external plate) to check >>> if they are well seated or damaged? >> >> I'll pull the unit apart and have a look. I have been in there >> before. Since it last worked, the unit has gone through two moves. >> >> > You could also try swapping the >>> first and second connection or the third and fourth, or both, if it is >>> hooked up like I think it is, those should have an equal chance of >>> working >>> and might reveal a bad port or partially bad port. >> >> I did try moving the looped cable to plugs 1&2 and connecting my >> computer to plug 3. > The two plugs for each device (library, tape1, tape2) are probably tied > directly together in a Y > shape to the internal device so you can use them as an In/Out, so > putting the looped cable on > plugs 1 and 2 probably does nothing and isolates that device from the > rest. As long as the looped > cable is not between 1&2 or 3&4, you can probably use any other order > although the manufacturer > may have recommendations. I see nothing wrong with the way you appear > to have cabled it but > variations may reveal something. I looked inside. Nothing obviously disconnected etc. I tried connecting the computer into plug 1, leaving 2 and 3 empty. Regardless of whether or not the terminator is in plug 4, FreeBSD does not see the tape drive. FWIW, I went into the SCSI utility for the SCSI card during boot. ahc0: port 0x9400-0x94ff mem 0xfb400000-0xfb400fff irq 16 at device 9.0 on pci0 ahc0: [GIANT-LOCKED] The card itself sees only the library, not the drive. Thus, I conclude this is something outside FreeBSD (so far). >> >>> Also try leaving off >>> the terminator or one/both ends of the middle cable just to see if the >>> system can tell the difference especially while booting, just to confirm >>> if it makes any negative difference at all. >> >> OK, I will try that. >> >> Thank you. No difference. From dan at langille.org Thu Oct 29 00:32:44 2009 From: dan at langille.org (Dan Langille) Date: Thu Oct 29 00:32:51 2009 Subject: tape changer, but not tape drive In-Reply-To: <4AE8D01A.9020707@langille.org> References: <4AE7A0BB.8020402@langille.org> <20091028021932.GL62972@egr.msu.edu> <4AE8120A.70608@langille.org> <4AE84250.8020409@egr.msu.edu> <4AE8D01A.9020707@langille.org> Message-ID: <4AE8E2AA.7020901@langille.org> Dan Langille wrote: > Adam McDougall wrote: >> Dan Langille wrote: >>> Adam McDougall wrote: >>>> On Tue, Oct 27, 2009 at 09:39:07PM -0400, Dan Langille wrote: >>>> >>>> I first encountered this problem in April, now I'm back to it: >>>> >>>> http://lists.freebsd.org/pipermail/freebsd-scsi/2008-April/003452.html >>>> In short, the system has tape library. The library has worked >>>> in the past (http://www.freebsddiary.org/digital-tl891.php) but >>>> now it does not. I can see either the tape library or the tape >>>> drive. Which I see depends upon the cable configuration. >>>> http://www.freebsddiary.org/images/tape-libraries-cables.jpg >>>> As shown above, that's how I would expect things to work >>>> normally. However, in that configuration, I do not see the tape >>>> drive. The cable going down, goes to the computer. If I >>>> reconnect that cable to the plug to the left of the terminator, >>>> the system can see the DLT drive, but not the tape library. >>>> Under 6.3-STABLE FreeBSD, I can see either one device or the other. >>>> ch0 at ahc0 bus 0 target 0 lun 0 >>>> ch0: Removable Changer SCSI-2 device >>>> ch0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit) >>>> ch0: 10 slots, 1 drive, 1 picker, 0 portals >>>> or >>>> sa0 at ahc0 bus 0 target 1 lun 0 >>>> sa0: Removable Sequential Access SCSI-2 device >>>> sa0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit) >>>> acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 >>>> sks=0x40 0x00 0x01 >>>> Any ideas? >>>> Full dmesg output here: http://www.langille.org/tmp/dmesg.boot >>>> TIA. >>>> Is it possible the middle cable is broken in some way? Perhaps you >>>> could swap it with another cable to try to find out, such as with >>>> the cable going from the library to the 2944 card. Might be >>>> intermittant >>>> and start working if bent or moved. >>> >>> I did try that. I used the cable from my stand-alone DLT drive, >>> which has been used before (and after) and is known to be good. >>> >>>> Also can you see the connectors >>>> inside the library (on the back side of the external plate) to check >>>> if they are well seated or damaged? >>> >>> I'll pull the unit apart and have a look. I have been in there >>> before. Since it last worked, the unit has gone through two moves. >>> >>> > You could also try swapping the >>>> first and second connection or the third and fourth, or both, if it is >>>> hooked up like I think it is, those should have an equal chance of >>>> working >>>> and might reveal a bad port or partially bad port. >>> >>> I did try moving the looped cable to plugs 1&2 and connecting my >>> computer to plug 3. >> The two plugs for each device (library, tape1, tape2) are probably >> tied directly together in a Y >> shape to the internal device so you can use them as an In/Out, so >> putting the looped cable on >> plugs 1 and 2 probably does nothing and isolates that device from the >> rest. As long as the looped >> cable is not between 1&2 or 3&4, you can probably use any other order >> although the manufacturer >> may have recommendations. I see nothing wrong with the way you appear >> to have cabled it but >> variations may reveal something. > > I looked inside. Nothing obviously disconnected etc. > > I tried connecting the computer into plug 1, leaving 2 and 3 empty. > Regardless of whether or not the terminator is in plug 4, FreeBSD does > not see the tape drive. > > FWIW, I went into the SCSI utility for the SCSI card during boot. > > ahc0: port 0x9400-0x94ff mem > 0xfb400000-0xfb400fff irq 16 at device 9.0 on pci0 > ahc0: [GIANT-LOCKED] Is this the appropriate card to be using with this device? There is a label on the back of the library saying: SCSI DIFF I know the unit is configured to use SCSI-2 > The card itself sees only the library, not the drive. Thus, I conclude > this is something outside FreeBSD (so far). > >>> >>>> Also try leaving off >>>> the terminator or one/both ends of the middle cable just to see if the >>>> system can tell the difference especially while booting, just to >>>> confirm >>>> if it makes any negative difference at all. >>> >>> OK, I will try that. >>> >>> Thank you. > > No difference. > _______________________________________________ > freebsd-scsi@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-scsi > To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org" From dan at langille.org Thu Oct 29 02:18:38 2009 From: dan at langille.org (Dan Langille) Date: Thu Oct 29 02:18:44 2009 Subject: tape changer, but not tape drive In-Reply-To: <4AE84250.8020409@egr.msu.edu> References: <4AE7A0BB.8020402@langille.org> <20091028021932.GL62972@egr.msu.edu> <4AE8120A.70608@langille.org> <4AE84250.8020409@egr.msu.edu> Message-ID: <4AE8FB7B.5060305@langille.org> Good news: Adam McDougall wrote: > Dan Langille wrote: >> Adam McDougall wrote: >> > You could also try swapping the >>> first and second connection or the third and fourth, or both, if it is >>> hooked up like I think it is, those should have an equal chance of >>> working >>> and might reveal a bad port or partially bad port. >> $ sudo camcontrol devlist Password: at scbus0 target 0 lun 0 (pass0,ch0) at scbus0 target 5 lun 0 (sa0,pass1) at scbus1 target 5 lun 0 (sa1,pass2) at scbus3 target 0 lun 0 (pass3,cd0) Witness: http://www.langille.org/tmp/library-good-cables.jpg It seems putting the cables in the 'right' order helps. FWIW, I have since put that terminator into that empty slot and rebooted. Everything is there. Done a backup/restore/diff. All fine. :) Thank you. From rea-fbsd at codelabs.ru Thu Oct 29 07:50:04 2009 From: rea-fbsd at codelabs.ru (Eygene Ryabinkin) Date: Thu Oct 29 07:50:11 2009 Subject: kern/130735: [patch] pass M_NOWAIT to the malloc() call inside cdreaddvdstructure() Message-ID: <200910290750.n9T7o28e011964@freefall.freebsd.org> The following reply was made to PR kern/130735; it has been noted by GNATS. From: Eygene Ryabinkin To: Jaakko Heinonen Cc: bug-followup@FreeBSD.org Subject: Re: kern/130735: [patch] pass M_NOWAIT to the malloc() call inside cdreaddvdstructure() Date: Thu, 29 Oct 2009 10:40:27 +0300 Jaakko, good day. Mon, Oct 26, 2009 at 11:19:20AM +0200, Jaakko Heinonen wrote: > I have been looking at this. The same problem also exists in > cdreportkey() and cdsendkey(). I think that it's better to drop periph > lock while doing M_WAITOK malloc instead of using M_NOWAIT. Could you > test and look at this patch: > > http://www.saunalahti.fi/~jh3/patches/scsi_cd-M_WAITOK-fixes.diff It works fine for me. Alhough I am no completely familiar with the CAM locking (and that't why I had patched with M_NOWAIT rather than with dropping the locks), so I can't fully judge if dropping the lock inside the helper is good. As I understand, locking is done to prevent races with other requests on the same device. Most probably, dropping the lock inside cdreportkey(), cdsendkey() and cdreaddvdstructure(), is OK, since all three calls are wrapped by the lock/unlock in the ioctl handler like this: ----- cam_periph_lock(periph); error = cdXXX(ARGS); cam_periph_unlock(periph); ----- so dropping the lock at the entry and restoring it after the malloc call is just equivalent to the moving the lock acquisition/release to the functions themselves. I mean that these three functions can be called unlocked and will have the following structure: ----- int cdXXX(...) { check for sanity grab the memory cam_periph_lock(periph); do the stuff cam_periph_unlock(periph); } ----- It looks a bit cleaner from the design point of view (and that is what happens in practice, because the situation when the caller locks us and we unlock the stuff readily upon the entry to the function, just leads to the two locking calls that essentially do nothing): one won't think "heck, why we're dropping the lock here, will it be good?". But this contradicts with the general stratedy of scsi_cd.c to call all helper functions that do the actual work locked. Perhaps, the comment on the top of the cdioctl() that explains that everything, but the ioctl helpers that need malloc(M_WAIT), will be called locked and the said functions should grab the locks by themselves. -- Eygene _ ___ _.--. # \`.|\..----...-'` `-._.-'_.-'` # Remember that it is hard / ' ` , __.--' # to read the on-line manual )/' _/ \ `-_, / # while single-stepping the kernel. `-'" `"\_ ,_.-;_.-\_ ', fsc/as # _.-'_./ {_.' ; / # -- FreeBSD Developers handbook {_.-``-' {_/ # From emaste at FreeBSD.org Thu Oct 29 13:53:09 2009 From: emaste at FreeBSD.org (emaste@FreeBSD.org) Date: Thu Oct 29 13:53:15 2009 Subject: kern/123666: [aac] attach fails with Adaptec SAS RAID 3805 controller and MSI RC410-M2 rev. 1.0 motherboard Message-ID: <200910291353.n9TDr8w8041148@freefall.freebsd.org> Synopsis: [aac] attach fails with Adaptec SAS RAID 3805 controller and MSI RC410-M2 rev. 1.0 motherboard State-Changed-From-To: open->feedback State-Changed-By: emaste State-Changed-When: Thu Oct 29 13:51:13 UTC 2009 State-Changed-Why: A followup suggested contacting Adaptec support and I agree that this is the best course of action since this appears to be a hardware incompatibility with a specific motherboard. Please let us know if Adaptec's able to provide any assistance. http://www.freebsd.org/cgi/query-pr.cgi?pr=123666 From linimon at FreeBSD.org Thu Oct 29 23:55:25 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Thu Oct 29 23:55:31 2009 Subject: kern/140091: [da] [patch] allow for da(4) large block transfer than DFLTPHYS Message-ID: <200910292355.n9TNtOKB061109@freefall.freebsd.org> Old Synopsis: [PATCH] allow for da(4) large block transfer than DFLTPHYS New Synopsis: [da] [patch] allow for da(4) large block transfer than DFLTPHYS Responsible-Changed-From-To: freebsd-bugs->freebsd-scsi Responsible-Changed-By: linimon Responsible-Changed-When: Thu Oct 29 23:54:55 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=140091