From: Florian Lohoff <flo@rfc822.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [2.6.7] kernel BUG at fs/jbd/transaction.c:1227!
Date: Thu, 14 Oct 2004 17:43:19 +0200 [thread overview]
Message-ID: <20041014154319.GH21334@paradigm.rfc822.org> (raw)
In-Reply-To: <1094502324.4531.12.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1248 bytes --]
On Mon, Sep 06, 2004 at 09:25:26PM +0100, Alan Cox wrote:
> On Llu, 2004-09-06 at 21:41, Florian Lohoff wrote:
> > Sep 6 20:22:03 source kernel: attempt to access beyond end of device
> > Sep 6 20:22:03 source kernel: sdb1: rw=0, want=1803231528, limit=976784067
> > Sep 6 20:22:03 source kernel: attempt to access beyond end of device
> > Sep 6 20:22:03 source kernel: sdb1: rw=0, want=1080256520, limit=976784067
> > Sep 6 20:22:03 source kernel: attempt to access beyond end of device
> > Sep 6 20:22:03 source kernel: sdb1: rw=0, want=1121190792, limit=976784067
> > Sep 6 20:22:03 source kernel: attempt to access beyond end of devic
>
> All of these seem to be sensible block numbers if the top bit is flipped
> back. How much do you trust the hardware ?
Too much - It seems there is a 3Ware HW bug notice saying that for
64Bit 3Ware Controllers on specific Board and or Chipsets (My case
I7501) there are some unwanted noises on the PCI lines which is fixed in
newer Board revisions of the Controllers.
After replacing the 8506 with a newer revision the bug is gone.
Flo
--
Florian Lohoff flo@rfc822.org +49-171-2280134
Heisenberg may have been here.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-10-14 16:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-06 20:41 Florian Lohoff
2004-09-06 20:25 ` Alan Cox
2004-10-14 15:43 ` Florian Lohoff [this message]
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=20041014154319.GH21334@paradigm.rfc822.org \
--to=flo@rfc822.org \
--cc=alan@lxorguk.ukuu.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®