public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
* Fw: [Bugme-new] [Bug 4929] New: problem with aic7xxx driver on 2.6.x
@ 2005-07-23  0:05 Andrew Morton
  2005-07-23 18:51 ` Christoph Hellwig
  0 siblings, 1 reply; 6+ messages in thread
From: Andrew Morton @ 2005-07-23  0:05 UTC (permalink / raw)
  To: linux-scsi



Begin forwarded message:

Date: Fri, 22 Jul 2005 13:43:26 -0700
From: bugme-daemon@kernel-bugs.osdl.org
To: bugme-new@lists.osdl.org
Subject: [Bugme-new] [Bug 4929] New: problem with aic7xxx driver on 2.6.x


http://bugzilla.kernel.org/show_bug.cgi?id=4929

            Summary: problem with aic7xxx driver on 2.6.x

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Fw: [Bugme-new] [Bug 4929] New: problem with aic7xxx driver on 2.6.x
  2005-07-23  0:05 Fw: [Bugme-new] [Bug 4929] New: problem with aic7xxx driver on 2.6.x Andrew Morton
@ 2005-07-23 18:51 ` Christoph Hellwig
  2005-07-24  0:42   ` Andrew Morton
  2005-07-24 12:50   ` James Bottomley
  0 siblings, 2 replies; 6+ messages in thread
From: Christoph Hellwig @ 2005-07-23 18:51 UTC (permalink / raw)
  To: Andrew Morton; +Cc: linux-scsi

On Sat, Jul 23, 2005 at 10:05:22AM +1000, Andrew Morton wrote:
> 
> 
> Begin forwarded message:
> 
> Date: Fri, 22 Jul 2005 13:43:26 -0700
> From: bugme-daemon@kernel-bugs.osdl.org
> To: bugme-new@lists.osdl.org
> Subject: [Bugme-new] [Bug 4929] New: problem with aic7xxx driver on 2.6.x
> 
> 
> http://bugzilla.kernel.org/show_bug.cgi?id=4929
> 
>             Summary: problem with aic7xxx driver on 2.6.x

This message is totally useless.  If you want to forward bugzilla reports
please include all relevant information.


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Fw: [Bugme-new] [Bug 4929] New: problem with aic7xxx driver on 2.6.x
  2005-07-23 18:51 ` Christoph Hellwig
@ 2005-07-24  0:42   ` Andrew Morton
  2005-07-24 10:10     ` Stefan Richter
  2005-07-24 18:38     ` Christoph Hellwig
  2005-07-24 12:50   ` James Bottomley
  1 sibling, 2 replies; 6+ messages in thread
From: Andrew Morton @ 2005-07-24  0:42 UTC (permalink / raw)
  To: Christoph Hellwig; +Cc: linux-scsi

Christoph Hellwig <hch@infradead.org> wrote:
>
> On Sat, Jul 23, 2005 at 10:05:22AM +1000, Andrew Morton wrote:
> > 
> > 
> > Begin forwarded message:
> > 
> > Date: Fri, 22 Jul 2005 13:43:26 -0700
> > From: bugme-daemon@kernel-bugs.osdl.org
> > To: bugme-new@lists.osdl.org
> > Subject: [Bugme-new] [Bug 4929] New: problem with aic7xxx driver on 2.6.x
> > 
> > 
> > http://bugzilla.kernel.org/show_bug.cgi?id=4929
> > 
> >             Summary: problem with aic7xxx driver on 2.6.x
> 
> This message is totally useless.  If you want to forward bugzilla reports
> please include all relevant information.

Absolutely not.  Please use bugzilla.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Fw: [Bugme-new] [Bug 4929] New: problem with aic7xxx driver on 2.6.x
  2005-07-24  0:42   ` Andrew Morton
@ 2005-07-24 10:10     ` Stefan Richter
  2005-07-24 18:38     ` Christoph Hellwig
  1 sibling, 0 replies; 6+ messages in thread
From: Stefan Richter @ 2005-07-24 10:10 UTC (permalink / raw)
  To: linux-scsi; +Cc: Andrew Morton

Andrew Morton wrote:
> Christoph Hellwig <hch@infradead.org> wrote:
>> This message is totally useless.  If you want to forward bugzilla reports
>> please include all relevant information.
> 
> Absolutely not.  Please use bugzilla.

I am sure it has been discussed elsewhere multiple times. Here are my 2
cents anyway: A tool for bug management is extremely valuable. But there
are comfort drawbacks (e.g. sometimes high latency of bugzilla.kernel.org)
and a severe conceptional drawback compared to mailinglists: Any list
subscriber may join a discussion with an additional test case or even with
a new approach to solve a problem. The bug database lacks this kind of
input which is vital for a non-corporate project like Linux.
-- 
Stefan Richter
-=====-=-=-= -=== ==---
http://arcgraph.de/sr/

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Fw: [Bugme-new] [Bug 4929] New: problem with aic7xxx driver on 2.6.x
  2005-07-23 18:51 ` Christoph Hellwig
  2005-07-24  0:42   ` Andrew Morton
@ 2005-07-24 12:50   ` James Bottomley
  1 sibling, 0 replies; 6+ messages in thread
From: James Bottomley @ 2005-07-24 12:50 UTC (permalink / raw)
  To: Christoph Hellwig; +Cc: Andrew Morton, SCSI Mailing List, mbligh

On Sat, 2005-07-23 at 19:51 +0100, Christoph Hellwig wrote:
> This message is totally useless.  If you want to forward bugzilla reports
> please include all relevant information.

OK, let me try.

The format I'd like is for the text of the bug report to go over the
list with a cc to the bugzilla so that it captures any email
conversation about it.  Martin has already set this up, I just can't
figure out what the bugzilla email address is for this report.

Anyway, this is what looks to be the issue in the trace

>  target2:0:1: Ending Domain Validation
> SCSI device sdc: 2788016128 512-byte hdwr sectors (1427464 MB)
> (scsi2:A:1:0): Handled Residual of 4 bytes
> SCSI device sdc: drive cache: write back
> SCSI device sdc: 2788016128 512-byte hdwr sectors (1427464 MB)
> (scsi2:A:1:0): Handled Residual of 4 bytes
> SCSI device sdc: drive cache: write back
>  sdc: sdc1 sdc2 sdc3 sdc4
> Attached scsi disk sdc at scsi2, channel 0, id 1, lun 0
> (scsi2:A:1:0): Handled Residual of 3960 bytes
> scsi: host 2 channel 0 id 1 lun 0x00000200080c0400 has a LUN larger than
> currently supported.
> scsi: host 2 channel 0 id 1 lun 0xff010000ffffffff has a LUN larger than
> currently supported.
> scsi: host 2 channel 0 id 1 lun 0x0002202020202020 has a LUN larger than
> currently supported.
> scsi: host 2 channel 0 id 1 lun808529923 has a LUN larger than allowed by the
> host adapter
> (scsi2:A:1:4): Handled Residual of 4 bytes
> (scsi2:A:1:5): Handled Residual of 4 bytes
> scsi: host 2 channel 0 id 1 lun3078 has a LUN larger than allowed by the host
> adapter

So I think it's not an aic7xxx error (it seems the new DV actually works
whereas the old DV failed).  It seems to be a bug in REPORT LUNS.
Either in the device or in the kernel code.

The curious thing is why after the report luns failure, we apparently
jump to sequential LUN scanning, but choose to begin at LUN 4.

I think as a work around, a simple

echo scsi add-single-device 2 0 1 1 > /proc/scsi/scsi

should bring the missing LUN back again

James



^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Fw: [Bugme-new] [Bug 4929] New: problem with aic7xxx driver on 2.6.x
  2005-07-24  0:42   ` Andrew Morton
  2005-07-24 10:10     ` Stefan Richter
@ 2005-07-24 18:38     ` Christoph Hellwig
  1 sibling, 0 replies; 6+ messages in thread
From: Christoph Hellwig @ 2005-07-24 18:38 UTC (permalink / raw)
  To: Andrew Morton; +Cc: Christoph Hellwig, linux-scsi

On Sun, Jul 24, 2005 at 10:42:38AM +1000, Andrew Morton wrote:
> > This message is totally useless.  If you want to forward bugzilla reports
> > please include all relevant information.
> 
> Absolutely not.  Please use bugzilla.

No way as long as it doesn't have a really usable email interface.


^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2005-07-24 18:38 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-07-23  0:05 Fw: [Bugme-new] [Bug 4929] New: problem with aic7xxx driver on 2.6.x Andrew Morton
2005-07-23 18:51 ` Christoph Hellwig
2005-07-24  0:42   ` Andrew Morton
2005-07-24 10:10     ` Stefan Richter
2005-07-24 18:38     ` Christoph Hellwig
2005-07-24 12:50   ` James Bottomley

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox