[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20070521150409.e1ef7701.akpm@linux-foundation.org>
Date: Mon, 21 May 2007 15:04:09 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Uwe Bugla <uwe.bugla@....de>
Cc: "Ken Chen" <kenchen@...gle.com>,
"Linus Torvalds" <torvalds@...ux-foundation.org>,
"Kay Sievers" <kay.sievers@...y.org>,
"Ray Lee" <ray-lk@...rabbit.org>,
"Al Viro" <viro@....linux.org.uk>,
"Andrey Borzenkov" <arvidjaar@...l.ru>,
"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
"Michal Piotrowski" <michal.k.k.piotrowski@...il.com>
Subject: Re: bug in 2.6.22-rc2: loop mount limited to one single iso image
On Mon, 21 May 2007 23:20:54 +0200
Uwe Bugla <uwe.bugla@....de> wrote:
> I meanwhile tried to find out why my AMD K7 machine oopses with 2.6.21.1.
> I first suspected sis5513 ide module, reverted all its dependencies, even
> changed a Makefile, but the Oops is still there after 10 modules reverted. I
> am standing in the dark, although I really would like to help to close down
> 2.6.21.x "cleanly".
>
> On Intel P 4 machines this Oops does not happen at all, only on the AMD K7
> machine.
> Already planned to start a new thread but instead of wild guessing around I do
> not have any idea wht the reason for the kernel Oops could be.
Yes, please send out a fresh bug report for this.
-
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/
Powered by blists - more mailing lists