From: "Rafael J. Wysocki" <rjw-KKrjLPT3xs0@public.gmane.org>
To: Linux Kernel Mailing List
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Cc: Kernel Testers List
<kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
alexs <alex.shi-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
James Bottomley
<James.Bottomley-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org>,
Linux SCSI list
<linux-scsi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Mike Christie <michaelc-hcNo3dDEHLuVc3sceRu5cw@public.gmane.org>,
Yanmin Zhang
<yanmin_zhang-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
Subject: [Bug #11898] mke2fs hang on AIC79 device.
Date: Sun, 7 Dec 2008 21:32:52 +0100 (CET) [thread overview]
Message-ID: <07Xes05z25M.A.QoG.XuEPJB@chimera> (raw)
In-Reply-To: <6VnlupFpCsN.A.2rE.MsEPJB@chimera>
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.27. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11898
Subject : mke2fs hang on AIC79 device.
Submitter : alexs <alex.shi-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Date : 2008-10-30 01:17 (39 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=f0c0a376d0fcd4c5579ecf5e95f88387cba85211
Handled-By : James Bottomley <James.Bottomley-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org>
Mike Christie <michaelc-hcNo3dDEHLuVc3sceRu5cw@public.gmane.org>
Patch : http://bugzilla.kernel.org/show_bug.cgi?id=11898#c28
http://bugzilla.kernel.org/show_bug.cgi?id=11898#c36
next prev parent reply other threads:[~2008-12-07 20:32 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-07 20:27 2.6.28-rc8-git5: Reported regressions from 2.6.27 Rafael J. Wysocki
2008-12-07 20:32 ` Rafael J. Wysocki [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-10-30 8:17 [Bug 11898] New: mke2fs hang on AIC79 device bugme-daemon
2008-10-30 8:53 ` [Bug 11898] " bugme-daemon
2008-10-30 8:54 ` bugme-daemon
2008-10-30 10:23 ` bugme-daemon
2008-10-30 12:37 ` bugme-daemon
2008-10-30 14:06 ` bugme-daemon
2008-10-31 3:12 ` bugme-daemon
2008-11-03 8:02 ` bugme-daemon
2008-11-04 7:37 ` bugme-daemon
2008-11-04 7:41 ` bugme-daemon
2008-11-04 9:05 ` bugme-daemon
2008-11-05 1:32 ` bugme-daemon
2008-11-05 1:55 ` Mike Christie
2008-11-05 2:10 ` James Bottomley
2008-11-05 1:56 ` bugme-daemon
2008-11-05 2:11 ` bugme-daemon
2008-11-05 2:43 ` bugme-daemon
2008-11-05 2:56 ` bugme-daemon
2008-11-05 3:19 ` bugme-daemon
2008-11-05 4:01 ` bugme-daemon
2008-11-05 15:24 ` James Bottomley
2008-11-05 17:25 ` Mike Christie
2008-11-05 18:46 ` James Bottomley
2008-11-09 15:47 ` James Bottomley
2008-11-11 18:22 ` Mike Christie
2008-11-11 19:42 ` Mike Christie
2008-11-05 4:26 ` bugme-daemon
2008-11-05 10:48 ` bugme-daemon
2008-11-05 14:32 ` bugme-daemon
2008-11-05 15:25 ` bugme-daemon
2008-11-05 17:25 ` bugme-daemon
2008-11-05 18:47 ` bugme-daemon
2008-11-06 1:44 ` bugme-daemon
2008-11-06 1:59 ` bugme-daemon
2008-11-06 2:06 ` bugme-daemon
2008-11-06 2:19 ` bugme-daemon
2008-11-06 14:57 ` James Bottomley
2008-11-06 14:58 ` bugme-daemon
2008-11-07 1:04 ` bugme-daemon
2008-11-09 15:47 ` bugme-daemon
2008-11-09 17:54 ` bugme-daemon
2008-11-09 19:01 ` bugme-daemon
2008-11-09 19:15 ` bugme-daemon
2008-11-10 2:15 ` bugme-daemon
2008-11-11 11:23 ` bugme-daemon
2008-11-11 11:28 ` bugme-daemon
2008-11-11 18:23 ` bugme-daemon
2008-11-11 19:43 ` bugme-daemon
2008-11-12 10:47 ` bugme-daemon
2008-11-14 15:40 ` James Bottomley
2008-11-14 15:41 ` bugme-daemon
2008-11-16 17:17 ` bugme-daemon
2008-11-19 1:49 ` bugme-daemon
2008-12-02 7:20 ` bugme-daemon
2008-12-07 21:52 ` bugme-daemon
2008-12-13 18:23 ` bugme-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=07Xes05z25M.A.QoG.XuEPJB@chimera \
--to=rjw-kkrjlpt3xs0@public.gmane.org \
--cc=James.Bottomley-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org \
--cc=alex.shi-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-scsi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=michaelc-hcNo3dDEHLuVc3sceRu5cw@public.gmane.org \
--cc=yanmin_zhang-VuQAYsv1563Yd54FQh9/CA@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox