linux-kernel - Re: I2O block driver broken in kernel 2.6.19?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20070224030924.e2b0fcce.akpm@linux-foundation.org>
Date:	Sat, 24 Feb 2007 03:09:24 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Mark Gray <mvg001@...kvgray.com>
Cc:	linux-kernel@...r.kernel.org, Sam Hokin <sam@....net>,
	Chuck Ebbert <cebbert@...hat.com>,
	Markus Lidel <Markus.Lidel@...dowconnect.com>
Subject: Re: I2O block driver broken in kernel 2.6.19?


(cc's restored.  Please, always do reply-to-all)

> On Fri, 23 Feb 2007 22:57:27 +0000 (UTC) Mark Gray <mvg001@...kvgray.com> wrote:
> >  i2o/hda:<3>Buffer I/O error on device i2o/hda, logical block 0
> > Buffer I/O error on device i2o/hda, logical block 0
> 
> Same error here. Both 2.6.19 and 2.6.20 kernels, using Adaptec 2400A RAID.

Is Adaptec 2400 controlled by drivers/message/i2o? I assume so...

If so, thats's at least three people reporting breakage in 2.6.19 and later.

Is anyone able perform a git-bisect to identify the offending commit?  It
would really help.

Thanks.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/