Re: 6.0-CURRENT SNAP004 hangs on amr (patch)

From: Eric Anderson (anderson_at_centtech.com)
Date: 09/04/05

  • Next message: Bjoern A. Zeeb: "Re: LOR route vr0" 
    Date: Sun, 04 Sep 2005 10:25:06 -0500
To: joao.barros@gmail.com

    Joao Barros wrote:
    > On 9/4/05, Eric Anderson <anderson@centtech.com> wrote:
    >
    >>Joao Barros wrote:
    >>
    >>>On 8/8/05, John Baldwin <jhb@freebsd.org> wrote:
    >>>
    >>>
    >>>>Ok, so I'm assuming that 5.4 works but RELENG_6 does not? Do you have verbose
    >>>>dmesg's from both cases so that I can compare them?
    >>>
    >>>
    >>>Ok, review:
    >>>FreeBSD5.4: kernel boots with amr installed
    >>>FreeBSD6.0: kernel doesn't boot with amr installed
    >>>As I think some commit in time between 5.4 and CURRENT(6.0) changed
    >>>something that prevents the kernel to boot with an amr installed, I'm
    >>>trying to pinpoint that change.
    >>>So far I've tested 5.4-STABLE-SNAP006-i386 which boots and back till
    >>>6.0-CURRENT-SNAP001 which does not boot.
    >>>My next step will be to cvsup to specific times and start testing kernels :)
    >>>More feedback to come!
    >>
    >>If you verbose boot, do you see it attempting to probe (?) lots of scsi
    >>id's that don't exist? I have an issue with a QLogic fiber channel
    >>card doing this on 6.0-B3 but not on the most recent 5.4-STABLE. It's
    >>definitely something in CAM that isn't right. If anyone wants more
    >>info, I'd be happy to provide it.
    >>
    >>Eric
    >
    >
    >>From my verbose boots this is common between kernels:
    >
    > Waiting 5 seconds for SCSI devices to settle
    > amrd0: <LSILogic MegaRAID logical drive> on amr0
    > amrd0: 104040MB (213073920 sectors) RAID 5 (optimal)
    > GEOM: new disk amrd0
    >
    > This only happens on 5.x after the last common part:
    >
    > GEOM: Configure amrd0s1, start 32256 length 72727893504 end 72727925759
    > [0] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0
    > [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0
    > [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0
    > [3] f:80 typ:165 s(CHS):0/0/1 e(CHS):1023/254/63 s:0 l:50000
    > GEOM: Configure amrd0s1a, start 0 length 268435456 end 268435455
    > GEOM: Configure amrd0s1b, start 268435456 length 239804416 end 508239871
    > GEOM: Configure amrd0s1c, start 0 length 72727893504 end 72727893503
    > GEOM: Configure amrd0s1d, start 508239872 length 268435456 end 776675327
    > GEOM: Configure amrd0s1e, start 776675328 length 268435456 end 1045110783
    > GEOM: Configure amrd0s1f, start 1045110784 length 71682782720 end 72727893503
    > [0] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0
    > [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0
    > [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0
    > [3] f:80 typ:165 s(CHS):0/0/1 e(CHS):1023/254/63 s:0 l:50000
    > [0] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0
    > [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0
    > [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0
    > [3] f:80 typ:165 s(CHS):0/0/1 e(CHS):1023/254/63 s:0 l:50000
    > (probe2:amr0:0:2:0): error 22
    > (probe2:amr0:0:2:0): Unretryable Error
    > (probe17:amr0:1:2:0): error 22
    > (probe17:amr0:1:2:0): Unretryable Error
    > (probe3:amr0:0:3:0): error 22
    > (probe3:amr0:0:3:0): Unretryable Error
    > (probe18:amr0:1:3:0): error 22
    > (probe18:amr0:1:3:0): Unretryable Error
    > (probe4:amr0:0:4:0): error 22
    > (probe4:amr0:0:4:0): Unretryable Error
    > (probe22:amr0:1:8:0): error 22
    > (probe22:amr0:1:8:0): Unretryable Error
    > (probe5:amr0:0:5:0): error 22
    > (probe5:amr0:0:5:0): Unretryable Error
    > (probe23:amr0:1:9:0): error 22
    > (probe23:amr0:1:9:0): Unretryable Error
    > (probe9:amr0:0:10:0): error 22
    > (probe9:amr0:0:10:0): Unretryable Error
    > (probe24:amr0:1:10:0): error 22
    > (probe24:amr0:1:10:0): Unretryable Error
    > (probe10:amr0:0:11:0): error 22
    > (probe10:amr0:0:11:0): Unretryable Error
    > (probe25:amr0:1:11:0): error 22
    > (probe25:amr0:1:11:0): Unretryable Error
    > (probe11:amr0:0:12:0): error 22
    > (probe11:amr0:0:12:0): Unretryable Error
    > (probe26:amr0:1:12:0): error 22
    > (probe26:amr0:1:12:0): Unretryable Error
    > (probe12:amr0:0:13:0): error 22
    > (probe12:amr0:0:13:0): Unretryable Error
    > (probe27:amr0:1:13:0): error 22
    > (probe27:amr0:1:13:0): Unretryable Error
    > (probe13:amr0:0:14:0): error 22
    > (probe13:amr0:0:14:0): Unretryable Error
    > (probe28:amr0:1:14:0): error 22
    > (probe28:amr0:1:14:0): Unretryable Error
    > (probe14:amr0:0:15:0): error 22
    > (probe14:amr0:0:15:0): Unretryable Error
    > (probe29:amr0:1:15:0): error 22
    > (probe29:amr0:1:15:0): Unretryable Error
    > (probe6:amr0:0:6:0): error 22
    > (probe6:amr0:0:6:0): Unretryable Error
    > (probe19:amr0:1:4:0): error 22
    > (probe19:amr0:1:4:0): Unretryable Error
    > (probe7:amr0:0:8:0): error 22
    > (probe7:amr0:0:8:0): Unretryable Error
    > (probe20:amr0:1:5:0): error 22
    > (probe20:amr0:1:5:0): Unretryable Error
    > (probe8:amr0:0:9:0): error 22
    > (probe8:amr0:0:9:0): Unretryable Error
    > (probe0:amr0:0:0:0): error 22
    > (probe0:amr0:0:0:0): Unretryable Error
    > (probe21:amr0:1:6:0): error 22
    > (probe21:amr0:1:6:0): Unretryable Error
    > (probe1:amr0:0:1:0): error 22
    > (probe1:amr0:0:1:0): Unretryable Error
    > (probe16:amr0:1:1:0): error 22
    > (probe16:amr0:1:1:0): Unretryable Error
    > (probe15:amr0:1:0:0): error 22
    > (probe15:amr0:1:0:0): Unretryable Error
    >
    > The controller has 2 channels so this looks fine to me.

    Mine probes to 16384 before continuing, and then finds the same devices
    hundreds of times.

    Eric 

    -- 
------------------------------------------------------------------------
Eric Anderson        Sr. Systems Administrator        Centaur Technology
Anything that works is better than anything that doesn't.
------------------------------------------------------------------------
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
  • Next message: Bjoern A. Zeeb: "Re: LOR route vr0"

    Relevant Pages

    • SCSI subsystem supports two modes of data transfer: asynchronous and synchronous
      ... The maximum data-transfer rate across the small computer system interface is five times faster than across the enhanced small device interface bus. ... However, because SCSI devices are independent of the SCSI controller, all devices do not have to transfer data at the same rate. ... For example, as soon as a hard disk drive has received a command from the SCSI controller, it can disconnect from the interface. ...
      (comp.sys.ibm.ps2.hardware)
    • Re: Please revert 5adc55da4a7758021bcc374904b0f8b076508a11 (PCI_MULTITHREAD_PROBE)
      ... A proper dependency system is necessary ... Proper mutual exclusion for shared system resources/registers/etc. ... always probe the subfunctions serially. ... the individual LUN's of many "SCSI" devices concurrently. ...
      (Linux-Kernel)
    • Re: solaris 9 x86 12/03: scsi disk timeout
      ... quantum atlas v 18 wls ... the external box is connected to the server by a less than one meter scsi ... i think i will go to disconnect all the scsi devices and then i will try to ... > external SCSI devices attached? ...
      (comp.unix.solaris)
    • Re: unable to mount usb smartmedia card reader
      ... SCSI device" in the kernel config. ... It looks like your kernel's SCSI modules were compiled without "probe ... all LUNs" support defined. ... then look at the output from dmesg. ...
      (comp.os.linux.hardware)
    • Re: TLZ07-DA box
      ... >your scsi devices ask yourself why that is. ... All of the external SCSI ... I stopped using large SCSI connectors several ... I don't own any HV differential SCSI devices, ...
      (comp.sys.dec)