From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ide@vger.kernel.org
Subject: [Bug 12874] Seagate STT20000A no longer works
Date: Thu, 20 Aug 2009 06:41:11 GMT [thread overview]
Message-ID: <200908200641.n7K6fBVF008669@demeter.kernel.org> (raw)
In-Reply-To: <bug-12874-11633@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=12874
--- Comment #37 from Borislav Petkov <bbpetkov@yahoo.de> 2009-08-20 06:41:10 ---
Hi Mark,
ok, we have to wheel out the heavy guns. In ide-next I've got an
ide-tape debugging patch for the whole driver. Get the tree at
git://git.kernel.org/pub/scm/linux/kernel/git/davem/ide-next-2.6.git and
apply the patch at http://bugzilla.kernel.org/attachment.cgi?id=22782
and catch the _whole_ output while doing only one filesize, let's say:
cat /tmp/32 >/dev/ht0
cat /dev/ht0 > /tmp/32.copy
Try setting log_buf_len=10M kernel parameter in case the output gets
truncated since it is quite a lot.
Thanks.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2009-08-20 6:41 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-15 8:23 [Bug 12874] New: Seagate STT20000A no longer works bugme-daemon
2009-03-15 8:25 ` [Bug 12874] " 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 [this message]
2009-08-31 18:22 ` bugzilla-daemon
2010-01-25 14:56 ` bugzilla-daemon
-- strict thread matches above, loose matches on Subject: below --
2009-04-10 17:42 [bug#12874] " Borislav Petkov
2009-04-14 21:34 ` Mark de Wever
2009-04-14 21:41 ` Mark de Wever
2009-04-20 9:30 ` Borislav Petkov
2009-05-05 21:12 ` Mark de Wever
2009-05-06 6:11 ` Borislav Petkov
2009-05-16 8:25 ` Mark de Wever
[not found] <bug-12874-11633@https.bugzilla.kernel.org/>
2012-01-12 0:58 ` [Bug 12874] " bugzilla-daemon
2012-05-30 14:38 ` bugzilla-daemon
2012-05-30 14:38 ` 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=200908200641.n7K6fBVF008669@demeter.kernel.org \
--to=bugzilla-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.