All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugme-daemon@bugzilla.kernel.org
To: linux-ide@vger.kernel.org
Subject: [Bug 12874] New: Seagate STT20000A no longer works
Date: Sun, 15 Mar 2009 01:23:45 -0700 (PDT)	[thread overview]
Message-ID: <bug-12874-11633@http.bugzilla.kernel.org/> (raw)

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

           Summary: Seagate STT20000A no longer works
           Product: IO/Storage
           Version: 2.5
     KernelVersion: 2.6.29-rc7
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: IDE
        AssignedTo: io_ide@kernel-bugs.osdl.org
        ReportedBy: koraq@xs4all.nl


Latest working kernel version: 2.6.25
Earliest failing kernel version: 2.6.26
Distribution: Debian Lenny (tested with vanilla kernel)
Hardware Environment: i386
Problem Description: 
The Seagate STT20000A tapestreamer is no longer usable 
when modprobing the ide_tape module there's kernel BUG.

It was reported on the lkml[1][2], I tested with 2.6.29-rc7
and the problem still remains. Attached the boot dmesg and
the kernel BUG dmesg. Please let me know if more information
is needed. 

[1]http://marc.info/?l=linux-kernel&m=122203193728465&w=2
[2]http://marc.info/?l=linux-kernel&m=122202406417545&w=2


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

             reply	other threads:[~2009-03-15  8:24 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-15  8:23 bugme-daemon [this message]
2009-03-15  8:25 ` [Bug 12874] Seagate STT20000A no longer works bugme-daemon
2009-03-15  8:26 ` bugme-daemon
2009-03-15  8:26 ` bugme-daemon
2009-03-15 10:18 ` bugme-daemon
2009-03-15 10:37 ` bugme-daemon
2009-03-15 10:38 ` bugme-daemon
2009-03-15 10:40 ` bugme-daemon
2009-03-16  6:20 ` bugme-daemon
2009-03-18 23:04 ` bugme-daemon
2009-03-18 23:04 ` bugme-daemon
2009-03-25  8:40 ` bugzilla-daemon
2009-03-25  8:42 ` bugzilla-daemon
2009-03-30 20:20 ` bugzilla-daemon
2009-03-31  8:08 ` bugzilla-daemon
2009-03-31  8:11 ` bugzilla-daemon
2009-04-05 10:42 ` bugzilla-daemon
2009-04-05 16:23 ` bugzilla-daemon
2009-04-05 16:24 ` bugzilla-daemon
2009-04-05 20:45 ` bugzilla-daemon
2009-04-08  5:45 ` bugzilla-daemon
2009-04-08  5:47 ` bugzilla-daemon
2009-04-08 22:21 ` bugzilla-daemon
2009-04-08 22:23 ` bugzilla-daemon
2009-04-10 10:06 ` bugzilla-daemon
2009-04-10 10:06 ` bugzilla-daemon
2009-04-10 10:14 ` bugzilla-daemon
2009-04-10 10:15 ` bugzilla-daemon
2009-04-10 10:16 ` bugzilla-daemon
2009-04-10 12:48 ` bugzilla-daemon
2009-06-15  8:18 ` bugzilla-daemon
2009-06-18 18:02 ` bugzilla-daemon
2009-06-18 21:15 ` bugzilla-daemon
2009-07-14 21:01 ` bugzilla-daemon
2009-07-19 13:21 ` bugzilla-daemon
2009-07-19 13:22 ` bugzilla-daemon
2009-07-19 14:27 ` bugzilla-daemon
2009-07-19 14:30 ` bugzilla-daemon
2009-08-15  8:02 ` bugzilla-daemon
2009-08-15  8:04 ` bugzilla-daemon
2009-08-19 20:46 ` bugzilla-daemon
2009-08-20  6:36 ` bugzilla-daemon
2009-08-20  6:41 ` bugzilla-daemon
2009-08-31 18:22 ` bugzilla-daemon
2010-01-25 14: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=bug-12874-11633@http.bugzilla.kernel.org/ \
    --to=bugme-daemon@bugzilla.kernel.org \
    --cc=linux-ide@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.