From: Andrew Morton <akpm@linux-foundation.org>
To: Uwe Bugla <uwe.bugla@gmx.de>
Cc: "Ken Chen" <kenchen@google.com>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Kay Sievers" <kay.sievers@vrfy.org>,
"Ray Lee" <ray-lk@madrabbit.org>,
"Al Viro" <viro@ftp.linux.org.uk>,
"Andrey Borzenkov" <arvidjaar@mail.ru>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>
Subject: Re: bug in 2.6.22-rc2: loop mount limited to one single iso image
Date: Mon, 21 May 2007 15:04:09 -0700 [thread overview]
Message-ID: <20070521150409.e1ef7701.akpm@linux-foundation.org> (raw)
In-Reply-To: <200705212320.55270.uwe.bugla@gmx.de>
On Mon, 21 May 2007 23:20:54 +0200
Uwe Bugla <uwe.bugla@gmx.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.
next prev parent reply other threads:[~2007-05-21 22:09 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-19 18:33 bug in 2.6.22-rc2: loop mount limited to one single iso image Ray Lee
2007-05-19 19:17 ` Andrey Borzenkov
[not found] ` <200705200124.13026.uwe.bugla@gmx.de>
2007-05-20 4:45 ` Andrey Borzenkov
2007-05-20 6:16 ` Ray Lee
2007-05-20 6:28 ` Al Viro
2007-05-20 6:58 ` Andrey Borzenkov
2007-05-20 14:52 ` Uwe Bugla
2007-05-20 15:26 ` Ray Lee
2007-05-20 15:22 ` Ray Lee
2007-05-20 15:54 ` Kay Sievers
2007-05-20 16:02 ` Andrey Borzenkov
2007-05-20 16:23 ` Andreas Schwab
2007-05-20 16:10 ` Ray Lee
2007-05-20 16:16 ` Kay Sievers
2007-05-20 16:29 ` Uwe Bugla
2007-05-20 19:53 ` Michael Mauch
2007-05-21 16:11 ` Linus Torvalds
2007-05-21 16:27 ` Ken Chen
2007-05-21 16:35 ` Ray Lee
2007-05-21 16:37 ` Ken Chen
2007-05-21 16:50 ` Uwe Bugla
2007-05-21 17:11 ` Kay Sievers
2007-05-21 17:51 ` Andrey Borzenkov
2007-05-21 17:04 ` Linus Torvalds
2007-05-21 20:48 ` Ken Chen
2007-05-21 21:20 ` Uwe Bugla
2007-05-21 22:04 ` Andrew Morton [this message]
2007-05-22 0:10 ` Al Viro
2007-05-22 0:13 ` Al Viro
2007-05-20 16:09 ` Andrey Borzenkov
2007-05-20 16:14 ` Ray Lee
2007-05-22 20:18 ` Jan Engelhardt
2007-05-22 21:35 ` Uwe Bugla
2007-05-21 6:08 ` Ken Chen
2007-05-21 6:40 ` Ray Lee
2007-05-21 7:59 ` Uwe Bugla
-- strict thread matches above, loose matches on Subject: below --
2007-05-19 13:53 Uwe Bugla
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=20070521150409.e1ef7701.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=arvidjaar@mail.ru \
--cc=kay.sievers@vrfy.org \
--cc=kenchen@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=ray-lk@madrabbit.org \
--cc=torvalds@linux-foundation.org \
--cc=uwe.bugla@gmx.de \
--cc=viro@ftp.linux.org.uk \
/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.