All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 14159] AIC79xx is not working properly with an attached scsi tape since 2.6.29
Date: Fri, 11 Sep 2009 23:27:55 GMT	[thread overview]
Message-ID: <200909112327.n8BNRtDF032672@demeter.kernel.org> (raw)
In-Reply-To: <bug-14159-11613@http.bugzilla.kernel.org/>

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





--- Comment #2 from Anonymous Emailer <anonymous@kernel-bugs.osdl.org>  2009-09-11 23:27:53 ---
Reply-To: James.Bottomley@suse.de

On Fri, 2009-09-11 at 09:18 +0000, bugzilla-daemon@bugzilla.kernel.org
wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=14159
> 
>            Summary: AIC79xx is not working properly with an attached scsi
>                     tape since 2.6.29
>            Product: SCSI Drivers
>            Version: 2.5
>     Kernel Version: 2.6.27 (working), 2.6.30 (not working)
>           Platform: All
>         OS/Version: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: normal
>           Priority: P1
>          Component: Other
>         AssignedTo: scsi_drivers-other@kernel-bugs.osdl.org
>         ReportedBy: g.giorgetti@teamsystem.com
>                 CC: g.giorgetti@teamsystem.com
>         Regression: Yes
> 
> 
> Both kernels 2.6.27 and 2.6.28 are working correctly.
> Since Linux 2.6.29 till 2.6.31rc8 the regression(?) is out there.
> 
> Please let me know if I can provide any further details.
> 
> Best regards,
>  Gabriele
> 
> =================
> Here is the messages part for Linux 2.6.27:
> 
> aic79xx 0000:41:01.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19   
> scsi5 : Adaptec AIC79XX PCI-X SCSI HBA DRIVER, Rev 3.0
>         <Adaptec 29320ALP PCIx Ultra320 SCSI adapter>
>         aic7901: Ultra320 Wide Channel A, SCSI Id=7, PCI-X 101-133Mhz, 512 SCBs
>  target5:0:3: asynchronous
> scsi 5:0:3:0: Sequential-Access IBM      HH LTO Gen 2     0376 PQ: 0 ANSI: 3
>  target5:0:3: Beginning Domain Validation
>  target5:0:3: wide asynchronous
>  target5:0:3: FAST-80 WIDE SCSI 160.0 MB/s DT (12.5 ns, offset 126)
>  target5:0:3: Ending Domain Validation
> scsi 5:0:3:0: Attached scsi generic sg7 type 1
> st: Version 20080504, fixed bufsize 32768, s/g segs 256
> Driver 'st' needs updating - please use bus_type methods
> st 5:0:3:0: Attached scsi tape st0
> st 5:0:3:0: st0: try direct i/o: yes (alignment 4 B)
> osst :I: Tape driver with OnStream support version 0.99.4
> osst :I: $Id: osst.c,v 1.73 2005/01/01 21:13:34 wriede Exp $
> Driver 'osst' needs updating - please use bus_type methods
> st0: Block limits 256 - 524288 bytes.
> =================
> 
> =================
> Here is Linux 2.6.30:
> 
> Aug  3 06:25:04 svil kernel: aic79xx 0000:41:01.0: PCI INT A -> GSI 19 (level,
> low) -> IRQ 19
> Aug  3 06:25:04 svil kernel: scsi5 : Adaptec AIC79XX PCI-X SCSI HBA DRIVER, Rev
> 3.0
> Aug  3 06:25:04 svil kernel:         <Adaptec 29320ALP PCIx Ultra320 SCSI
> adapter>
> Aug  3 06:25:04 svil kernel:         aic7901: Ultra320 Wide Channel A, SCSI
> Id=7, PCI-X 101-1
> Aug  3 06:25:04 svil kernel: scsi 5:0:0:0: Attempting to queue an ABORT
> message:CDB: 0x12 0x0

That's an inquiry to a non-existent target.  It should have returned a
DID_NO_CONNECT timeout within 250ms.  The fact that it didn't is
suggestive of interrupt routing problems.  After all these messages have
completed, what does /proc/interrupts say?

James

-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

  parent reply	other threads:[~2009-09-11 23:27 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-11  9:18 [Bug 14159] New: AIC79xx is not working properly with an attached scsi tape since 2.6.29 bugzilla-daemon
2009-09-11  9:23 ` [Bug 14159] " bugzilla-daemon
2009-09-11 23:27 ` [Bug 14159] New: " James Bottomley
2009-09-11 23:27 ` bugzilla-daemon [this message]
2009-09-14  7:18 ` [Bug 14159] " bugzilla-daemon
2009-09-14 14:25   ` James Bottomley
2009-09-14 17:24     ` Bjorn Helgaas
2009-09-14  7:19 ` bugzilla-daemon
2009-09-14 14:25 ` bugzilla-daemon
2009-09-14 17:24 ` bugzilla-daemon
2009-09-15  7:05 ` bugzilla-daemon
2009-09-15 13:53   ` James Bottomley
2009-09-15 13:07 ` bugzilla-daemon
2009-09-15 13:55   ` James Bottomley
2009-09-15 15:08     ` Bjorn Helgaas
2009-09-15 13:53 ` bugzilla-daemon
2009-09-15 13:55 ` bugzilla-daemon
2009-09-15 15:08 ` bugzilla-daemon
2009-09-15 15:14 ` bugzilla-daemon
2009-09-15 15:20 ` bugzilla-daemon
2009-09-16  9:16 ` bugzilla-daemon
2009-09-16 13:42 ` bugzilla-daemon
2009-09-17  6:45 ` bugzilla-daemon
2009-09-17 14:14 ` bugzilla-daemon
     [not found] <bug-14159-11613@https.bugzilla.kernel.org/>
2012-06-13 16:55 ` bugzilla-daemon
2012-06-13 16:56 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200909112327.n8BNRtDF032672@demeter.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.