From: Giacomo Catenazzi <cate@cateee.net>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: regression: disk error loop (panic?) ide_do_rw_disk-bad:
Date: Tue, 17 Jul 2007 21:49:50 +0200 [thread overview]
Message-ID: <469D1D5E.8050609@cateee.net> (raw)
Hello,
last git changes to git give me the following error (repead very quickly):
sector 14657019, nr/cmr 0/0
bio f7b59280, biotail f7b59280, buffer 0000000, date 0000000, len 36
ide_do_rw_disk-bad command: dev hda: type 2, flags 104c8
[note: manually copied]
I tried bisect:
cate@catee:~/kernel/6,v2.6/linux-2.6$ git bisect log
# bad: [a5fcaa210626a79465321e344c91a6a7dc3881fa] Merge branch
'drm-patches' of
ssh://master.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2.6
# good: [8f41958bdd577731f7411c9605cfaa9db6766809] Merge
git://git.infradead.org/battery-2.6
git-bisect start 'a5fcaa21' '8f41958b'
# good: [02b2318e07f98a7cdf7089a4457a8d62424aa824] Merge branch 'master'
of master.kernel.org:/pub/scm/linux/kernel/git/davem/sparc-2.6
git-bisect good 02b2318e07f98a7cdf7089a4457a8d62424aa824
# good: [f716a425c15ebadf60286cd4fb60d1d6f46e3cf9] [POWERPC] VIOTAPE:
Use designated initializers for fops member structures.
git-bisect good f716a425c15ebadf60286cd4fb60d1d6f46e3cf9
# good: [14dc5249728ff699b1ca4dac01ad416a350a147a] Merge branch
'for-linus' of git://git.kernel.dk/data/git/linux-2.6-block
git-bisect good 14dc5249728ff699b1ca4dac01ad416a350a147a
# good: [c2dc1ad582196208a2f990eb0230eb922046c684] Merge branch
'drm-patches' of
ssh://master.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2.6
git-bisect good c2dc1ad582196208a2f990eb0230eb922046c684
# good: [c5e3ae8823693b260ce1f217adca8add1bc0b3de] forcedeth bug fix:
realtek phy
git-bisect good c5e3ae8823693b260ce1f217adca8add1bc0b3de
# good: [70584578ab3e940ac9d7820f268f9adc9884e407] [POWERPC] Check for
NULL ppc_md.init_IRQ() before calling
git-bisect good 70584578ab3e940ac9d7820f268f9adc9884e407
# good: [bf22f6fe2d72b4d7e9035be8ceb340414cf490e3] Merge branch
'for-2.6.23' into merge
git-bisect good bf22f6fe2d72b4d7e9035be8ceb340414cf490e3
# bad: [f798634d806615bee27d1b83479034087a02aa0f] [SERIAL] SUNHV: Fix
jerky console on LDOM guests.
git-bisect bad f798634d806615bee27d1b83479034087a02aa0f
# bad: [29417b899a77aaba1c060f5e123db4f50006f58a] Make BLK_DEV_BSG
depend strictly on SCSI=y
git-bisect bad 29417b899a77aaba1c060f5e123db4f50006f58a
but last changeset don't compile (and it doesn't seem relevant).
ciao
cate
next reply other threads:[~2007-07-17 19:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-17 19:49 Giacomo Catenazzi [this message]
2007-07-17 20:47 ` regression: disk error loop (panic?) ide_do_rw_disk-bad: Michal Piotrowski
2007-07-17 21:20 ` Bartlomiej Zolnierkiewicz
2007-07-17 21:24 ` Linus Torvalds
2007-07-17 22:45 ` Bartlomiej Zolnierkiewicz
2007-07-17 22:38 ` Linus Torvalds
2007-07-17 23:14 ` Bartlomiej Zolnierkiewicz
2007-07-17 23:18 ` Jeff Garzik
2007-07-18 8:09 ` Jens Axboe
2007-07-17 22:57 ` Linus Torvalds
2007-07-18 6:31 ` Giacomo Catenazzi
2007-07-18 19:57 ` Linus Torvalds
2007-07-18 20:08 ` Jens Axboe
2007-07-18 20:11 ` Jens Axboe
2007-07-18 20:14 ` Linus Torvalds
2007-07-18 20:27 ` Jens Axboe
2007-07-18 22:53 ` Bartlomiej Zolnierkiewicz
2007-07-18 23:20 ` Linus Torvalds
2007-07-19 6:13 ` Jens Axboe
2007-07-19 6:40 ` Giacomo Catenazzi
2007-07-19 6:47 ` Jens Axboe
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=469D1D5E.8050609@cateee.net \
--to=cate@cateee.net \
--cc=linux-kernel@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.