On Mon, 17 Dec 2007, James Bottomley wrote:
>
> On Mon, 2007-12-17 at 13:43 -0800, Andrew Morton wrote:
> > On Mon, 17 Dec 2007 16:02:02 -0500
> > "John Stoffel" <[EMAIL PROTECTED]> wrote:
> >
> > >
> > > Just to confirm, the propsed patch to st.c fixes the issue with
> > > 2.6.24-rc5 as well a
> "James" == James Bottomley <[EMAIL PROTECTED]> writes:
James> On Mon, 2007-12-17 at 13:43 -0800, Andrew Morton wrote:
>> On Mon, 17 Dec 2007 16:02:02 -0500
>> "John Stoffel" <[EMAIL PROTECTED]> wrote:
>>
>> >
>> > Just to confirm, the propsed patch to st.c fixes the issue with
>> > 2.6.24-
http://marc.info/?l=linux-scsi&m=119770154127770&w=2
There is the patch for st.c
Andrew Morton schreef:
On Mon, 17 Dec 2007 16:02:02 -0500
"John Stoffel" <[EMAIL PROTECTED]> wrote:
Just to confirm, the propsed patch to st.c fixes the issue with
2.6.24-rc5 as well at 2.6.24-rc5-mm1 with access
On Mon, 2007-12-17 at 13:43 -0800, Andrew Morton wrote:
> On Mon, 17 Dec 2007 16:02:02 -0500
> "John Stoffel" <[EMAIL PROTECTED]> wrote:
>
> >
> > Just to confirm, the propsed patch to st.c fixes the issue with
> > 2.6.24-rc5 as well at 2.6.24-rc5-mm1 with access to my DLT tape
> > drives.
>
>
On Mon, 17 Dec 2007 16:02:02 -0500
"John Stoffel" <[EMAIL PROTECTED]> wrote:
>
> Just to confirm, the propsed patch to st.c fixes the issue with
> 2.6.24-rc5 as well at 2.6.24-rc5-mm1 with access to my DLT tape
> drives.
err, what patch to st.c?
So it seems that 2.6.24 (and presumably 2.6.23?)
Just to confirm, the propsed patch to st.c fixes the issue with
2.6.24-rc5 as well at 2.6.24-rc5-mm1 with access to my DLT tape
drives.
Thanks!
John
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http:/
> "Andrew" == Andrew Morton <[EMAIL PROTECTED]> writes:
Andrew> On Mon, 17 Dec 2007 11:25:51 +0900 FUJITA Tomonori <[EMAIL PROTECTED]>
wrote:
>> On Sun, 16 Dec 2007 20:05:51 -0500
>> "John Stoffel" <[EMAIL PROTECTED]> wrote:
>> >
>> > [ 273.382057] sd 12:0:0:3: Attached scsi generic sg13 ty
> "Andrew" == Andrew Morton <[EMAIL PROTECTED]> writes:
Andrew> On Mon, 17 Dec 2007 11:25:51 +0900 FUJITA Tomonori <[EMAIL PROTECTED]>
wrote:
>> On Sun, 16 Dec 2007 20:05:51 -0500
>> "John Stoffel" <[EMAIL PROTECTED]> wrote:
>>
>> > [ 215.007701] sym1: SCSI parity error detected: SCR1=1 DBC
On Mon, 17 Dec 2007 11:25:51 +0900 FUJITA Tomonori <[EMAIL PROTECTED]> wrote:
> On Sun, 16 Dec 2007 20:05:51 -0500
> "John Stoffel" <[EMAIL PROTECTED]> wrote:
>
> > [ 215.007701] sym1: SCSI parity error detected: SCR1=1 DBC=1128 SBCL=ae
> > [ 215.008145] sym1: SCSI parity error detected: SC
On Sun, 16 Dec 2007 20:05:51 -0500
"John Stoffel" <[EMAIL PROTECTED]> wrote:
> [ 215.007701] sym1: SCSI parity error detected: SCR1=1 DBC=1128 SBCL=ae
> [ 215.008145] sym1: SCSI parity error detected: SCR1=1 DBC=1128 SBCL=ae
> [ 215.008678] sym1: SCSI parity error detected: SCR1=1 DBC=1
Hi,
This looks to be a regression between 2.6.23 and 2.6.24-rc5, I'll try
to bi-sect this and report more on it. Basically, when I bootup, I
get a ton of errors in the dmesg log along the lines of:
[ 215.007701] sym1: SCSI parity error detected: SCR1=1 DBC=1128 SBCL=ae
[ 215.008145] sym1:
11 matches
Mail list logo