On Tue, Jun 10, 2008 at 02:21:32PM -0600, dann frazier wrote:
On Tue, Jun 10, 2008 at 04:24:16PM +0200, Leo Weppelman wrote:
On Tue, Jun 03, 2008 at 01:01:55AM +0200, maximilian attems wrote:
On Wed, 30 May 2007, Leo Weppelman wrote:
Package: linux-image-2.6.21-1-686
Version:
On Tue, Jun 03, 2008 at 01:01:55AM +0200, maximilian attems wrote:
On Wed, 30 May 2007, Leo Weppelman wrote:
Package: linux-image-2.6.21-1-686
Version: 2.6.21-4
The trace written to the console:
=
kernel BUG at drivers/block/cciss.c:2479!
On Tue, Jun 10, 2008 at 04:24:16PM +0200, Leo Weppelman wrote:
On Tue, Jun 03, 2008 at 01:01:55AM +0200, maximilian attems wrote:
On Wed, 30 May 2007, Leo Weppelman wrote:
Package: linux-image-2.6.21-1-686
Version: 2.6.21-4
The trace written to the console:
On Wed, 30 May 2007, Leo Weppelman wrote:
Package: linux-image-2.6.21-1-686
Version: 2.6.21-4
The trace written to the console:
=
kernel BUG at drivers/block/cciss.c:2479!
invalid opcode: [#1]
SMP
hmm i see.
How to reproduce:
=
I was asked to look at http://bugzilla.kernel.org/show_bug.cgi?id=7763 since
that bug looked to be related.
It looks like the raid1 module is violating the queue limitations of the cciss
module indeed. Since the panic happens that the line:
BUG_ON(creq-nr_phys_segments MAXSGENTRIES);
in
Package: linux-image-2.6.21-1-686
Version: 2.6.21-4
The trace written to the console:
=
kernel BUG at drivers/block/cciss.c:2479!
invalid opcode: [#1]
SMP
Modules linked in: mptctl sg nfsd exportfs lockd nfs_acl sunrpc ipv6 8021q raw
dm_snapshot shpchp
6 matches
Mail list logo
