2007/2/15, Andrew Morton <[email protected]>:
Temporarily at http://userweb.kernel.org/~akpm/2.6.20-mm1/ Will appear later at Changes since 2.6.20-rc6-mm3: -minix-v3-support.patch
Hi Daniel,
On 2.6.20-rc6-mm3 and 2.6.20-mm1, i get an OOPS when using the minix 3
file system. I enclose the dmesg and the .config to that mail.
Here are the steps to reproduce this oops (they involve using qemu to
run Minix 3)
- First create a 2GB image using
qemu-img create minix.img 2G
(Please note that this seem to be producing an eroneous image)
- Then launch Minix inside qemu to make a minix partition on this
image using mkfs on the corresponding device.
- Mount the image on loopback using
mount -t minix -o loop minix.img /mnt/qemu/
- issue a "df" command on /mnt/qemu
This oops occurs everytime i use df on this directory. However, this
does not occur if the image was for a 1MB partition. And it does not
occur if the partition on which we created minix.img was the same as
the partition on which qemu stands. Sounds like qemu has an issue and
creates an erroneous partition which linux does not handle correctly.
Regards, and thanks for your patch by the way !
Cédric
Attachment:
configOOPS-20-mm1
Description: Binary data
Attachment:
dmesgOOPS-20-mm1
Description: Binary data
- Follow-Ups:
- Re: 2.6.20-mm1 - Oops using Minix 3 file system
- From: Bill Davidsen <[email protected]>
- Re: 2.6.20-mm1 - Oops using Minix 3 file system
- From: "Daniel Aragonés" <[email protected]>
- Re: 2.6.20-mm1 - Oops using Minix 3 file system
- Prev by Date: Re: Using sched_clock for mmio-trace
- Next by Date: Re: GPL vs non-GPL device drivers
- Previous by thread: MediaGX/GeodeGX1 requires X86_OOSTORE. (Was: Re: Strange connection slowdown on pcnet32)
- Next by thread: Re: 2.6.20-mm1 - Oops using Minix 3 file system
- Index(es):
 |