This is a problem that did not exist in 2.4.0test1-ac22-riel:
On boot, I insert modules in this sequnce:
ramfs
floppy
minix
ext2
fat
msdos
When trying to mount the floppy immediately after, I get a string of errors,
including the following (sorry - no way to cut and paste, and I don't have
all day):
=============================================
Trying to lock fdc while usage count = 0
warning: usage count=0, CURRENT=c3dd38c0 exiting
sect=0 cmd=0
floppy0: fractionary current count b=0 s=0
addr=0 length=0
=============================================
Hope that's enough to be of some use.
The reason I can't cut and paste is related to the following Oops, as the
machine bursts into flames as I try insmoding in different orders (worked
once, but I can't replicate it now):
=============================================
echo -e "EIP: 0010:[<c0121e4d>]\nCall Trace: <c010f2a8> <c011e66b> <c011e5b8> <c011e4a1> <c010c4b4> <c01115c0> <c0108af0> <c010b154> <c01115c0> <c0108af0> <c01117da> <c01115c0> <c0108af0> <c0108b62> <c0105000> <c010018d>\nCode: 8b 71 10 8b 59 0c 8b 11 85 d2 74 08 0b 41 04 89 42 04 89 10" | ksymoops -o ~/skel/boot/modules -K -L -m /home/root/skel/boot/System.map-2.4.0test2\:athlon
ksymoops 2.3.4 on i686 2.3.99-pre9. Options used
-V (default)
-K (specified)
-L (specified)
-o /home/root/skel/boot/modules (specified)
-m /home/root/skel/boot/System.map-2.4.0test2:athlon (specified)
No modules in ksyms, skipping objects
EIP: 0010:[<c0121e4d>]
Using defaults from ksymoops -t elf32-i386 -a i386
Call Trace: <c010f2a8> <c011e66b> <c011e5b8> <c011e4a1> <c010c4b4> <c01115c0> <c0108af0> <c010b154> <c01115c0> <c0108af0> <c01117da> <c01115c0> <c0108af0> <c0108b62> <c0105000> <c010018d>
Code: 8b 71 10 8b 59 0c 8b 11 85 d2 74 08 0b 41 04 89 42 04 89 10
>>EIP; c0121e4d <timer_bh+24d/2b0> <=====
Trace; c010f2a8 <timer_interrupt+88/100>
Trace; c011e66b <bh_action+1b/70>
Trace; c011e5b8 <tasklet_hi_action+38/60>
Trace; c011e4a1 <do_softirq+51/80>
Trace; c010c4b4 <do_IRQ+a4/c0>
Trace; c01115c0 <acpi_idle+0/230>
Trace; c0108af0 <default_idle+0/30>
Trace; c010b154 <ret_from_intr+0/20>
Trace; c01115c0 <acpi_idle+0/230>
Trace; c0108af0 <default_idle+0/30>
Trace; c01117da <acpi_idle+21a/230>
Trace; c01115c0 <acpi_idle+0/230>
Trace; c0108af0 <default_idle+0/30>
Trace; c0108b62 <cpu_idle+42/60>
Trace; c0105000 <empty_bad_page+0/1000>
Trace; c010018d <L6+0/2>
Code; c0121e4d <timer_bh+24d/2b0>
00000000 <_EIP>:
Code; c0121e4d <timer_bh+24d/2b0> <=====
0: 8b 71 10 mov 0x10(%ecx),%esi <=====
Code; c0121e50 <timer_bh+250/2b0>
3: 8b 59 0c mov 0xc(%ecx),%ebx
Code; c0121e53 <timer_bh+253/2b0>
6: 8b 11 mov (%ecx),%edx
Code; c0121e55 <timer_bh+255/2b0>
8: 85 d2 test %edx,%edx
Code; c0121e57 <timer_bh+257/2b0>
a: 74 08 je 14 <_EIP+0x14> c0121e61 <timer_bh+261/2b0>
Code; c0121e59 <timer_bh+259/2b0>
c: 0b 41 04 or 0x4(%ecx),%eax
Code; c0121e5c <timer_bh+25c/2b0>
f: 89 42 04 mov %eax,0x4(%edx)
Code; c0121e5f <timer_bh+25f/2b0>
12: 89 10 mov %edx,(%eax)
===============================================
I'm also getting reliable Oopsen from umounting ramfs, but that was in
previous kernels, too. Can't say if it's relevant.
-Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Jun 26 2000 - 21:00:09 EST