Jim Harris wrote this message on Fri, Oct 26, 2012 at 13:24 -0700:
> On Fri, Oct 26, 2012 at 1:18 PM, John-Mark Gurney wrote:
> >
> > I'm seeing similar stuff on the hpt27xx driver:
> > (probe18:hpt27xx0:0:18:0): INQUIRY. CDB: 12 0 0 0 24 0
> > (probe18:hpt27xx0:0:18:0): CAM status: Invalid Target
On Fri, Oct 26, 2012 at 1:18 PM, John-Mark Gurney wrote:
>
> I'm seeing similar stuff on the hpt27xx driver:
> (probe18:hpt27xx0:0:18:0): INQUIRY. CDB: 12 0 0 0 24 0
> (probe18:hpt27xx0:0:18:0): CAM status: Invalid Target ID
> (probe18:hpt27xx0:0:18:0): Error 22, Unretryable error
>
> Should I mak
Jim Harris wrote this message on Fri, Sep 21, 2012 at 20:17 -0700:
> On Fri, Sep 21, 2012 at 5:37 PM, Mike Tancsa wrote:
> > On 9/21/2012 8:03 PM, Jim Harris wrote:
> >>> .
> >>> then a lot of
> >>> .
> >>> (probe65:tws0:0:65:0): INQUIRY. CDB: 12 0 0 0 24 0
> >>> (probe65:tws0:0:65:0): CAM status:
On Sat, Sep 22, 2012 at 1:32 AM, Thomas Mueller wrote:
>
> The specific subject of this thread is not my issue, but I did notice
> problems apparently related to CAM on a SATA hard drive.
>
I would suggest starting a new thread if you have a different issue.
> I use one UFS partition, with FreeB
On 9/21/2012 11:17 PM, Jim Harris wrote:
>> What about a change similar to what Alexander Motin did in
>>
>> http://lists.freebsd.org/pipermail/svn-src-head/2012-June/038196.html
>
> Ah, yes. I was thinking you had CAM_DEBUG enabled which is why you
> were seeing this spew - but that's not the ca
On Fri, Sep 21, 2012 at 5:37 PM, Mike Tancsa wrote:
> On 9/21/2012 8:03 PM, Jim Harris wrote:
>>> .
>>> then a lot of
>>> .
>>> (probe65:tws0:0:65:0): INQUIRY. CDB: 12 0 0 0 24 0
>>> (probe65:tws0:0:65:0): CAM status: Invalid Target ID
>>> (probe65:tws0:0:65:0): Error 22, Unretryable error
>>> (pr
On Fri, Sep 21, 2012 at 5:37 PM, Mike Tancsa wrote:
> On 9/21/2012 8:03 PM, Jim Harris wrote:
>>> .
>>> then a lot of
>>> .
>>> (probe65:tws0:0:65:0): INQUIRY. CDB: 12 0 0 0 24 0
>>> (probe65:tws0:0:65:0): CAM status: Invalid Target ID
>>> (probe65:tws0:0:65:0): Error 22, Unretryable error
>>> (pr
On 9/21/2012 8:03 PM, Jim Harris wrote:
>> .
>> then a lot of
>> .
>> (probe65:tws0:0:65:0): INQUIRY. CDB: 12 0 0 0 24 0
>> (probe65:tws0:0:65:0): CAM status: Invalid Target ID
>> (probe65:tws0:0:65:0): Error 22, Unretryable error
>> (probe1:tws0:0:1:0): INQUIRY. CDB: 12 0 0 0 24 0
>> (probe1:tws0:
On Fri, Sep 21, 2012 at 3:11 PM, Mike Tancsa wrote:
> On 9/21/2012 4:59 PM, Jim Harris wrote:
> Thanks, that allows it to boot up now!
>
> pci2: on pcib2
> LSI 3ware device driver for SAS/SATA storage controllers, version:
> 10.80.00.003
> tws0: port 0x4000-0x40ff mem
> 0xc246-0xc2463fff,
On 9/21/2012 4:59 PM, Jim Harris wrote:
>> boot. Anyone know whats up ? Is this something that should be sent
>> directly to LSI ?
>
> Through a code inspection, this mutex is being recursed whether or not
> debugging is enabled. There is no code path here specific to
> INVARIANTS. And the main
On Fri, Sep 21, 2012 at 1:07 PM, Mike Tancsa wrote:
> Hi,
> I have been trying out a nice new tws controller and decided to enable
> debugging in the kernel and run some stress tests. With a regular
> GENERIC kernel, it boots up fine. But with debugging, it panics on
> boot. Anyone know whats up
Hi,
I have been trying out a nice new tws controller and decided to enable
debugging in the kernel and run some stress tests. With a regular
GENERIC kernel, it boots up fine. But with debugging, it panics on
boot. Anyone know whats up ? Is this something that should be sent
directly to LSI ?
pc
12 matches
Mail list logo
