2.4.1ac17 hang on mounting loopback fs

Nate Eldredge (neldredge@hmc.edu)
Sat, 17 Feb 2001 01:52:53 -0800


This one should be easy to track down, it's reproducible (2 for 2 so
far).

Kernel 2.4.1ac17 compiled by gcc 2.95.2.

Scenario: In single-user mode; only user process running is /bin/bash
(pid 1). Only fs'es mounted are / (ro), /spare (rw) (both ext2),
/proc.

# mount -t ext2 -o loop /spare/i486-linuxaout.img /spare/mnt
loop: enabling 8 loop devices

then it hangs. No ctrl-C etc.

I did Ctrl+ScrollLock. The entry for mount had the following (copied
manually):

mount D C7E33E78 5012 23 1 (NOTLB)
Call trace: c012f17a c0130167 c0151dc1 c01267af c0133102 c013331c
c0108e84 c0133e65 c0133c9c [maybe 3cac] c013401c c0108d43

Appropriate lines of System.map, in order:

c012f110 T __wait_on_buffer
c0130124 T bread
c0151d0c T ext2_read_super
c0126740 T kmalloc
c0132ffc t read_super
c01331d0 t get_sb_bdev
c0108e50 t error_code
c0133cec T do_mount
c0133c4c t copy_mount_options [in either case]
c0133fa0 T sys_mount
c0108d10 T system_call

The image file in question is ext2, about 20 MB, 1K blocksize. loop.o
is compiled as a module.

Incidentally this also happened under more normal circumstances, when
it tried to mount the fs from fstab. I haven't yet booted without
mounting that fs.

Btw, this machine has a FIC PA-2013 motherboard with VIA chipset, and
I have CONFIG_IDEDMA_PCI_AUTO enabled. But this doesn't seem like the
other trouble such machines were having.

I'm happy to provide more info, test patches, etc. Please CC me
directly if convenient as I can only read the list through a web
gateway, which is slow.

-- 

Nate Eldredge neldredge@hmc.edu - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/