search for: __wait_on_buffer

...e > > case of virtio-scsi-pci, the device may still try to send interupts, > > which will be on IRQ lines seeing MSI-X disabled. Those interrupts will > > be unhandled, and may cause flood. Here is the problem I want to solve - file system driver hang: If a fs code happen to hit __wait_on_buffer right after pci pci_device_shutdown disabled msix, it will never make progress because the requests it waits for will never be completed. So the system hangs. In other words we will want to reset virtio device before pci_device_shutdown AND wake up all waiters. Unfortunately, neither your patch n...

...e > > case of virtio-scsi-pci, the device may still try to send interupts, > > which will be on IRQ lines seeing MSI-X disabled. Those interrupts will > > be unhandled, and may cause flood. Here is the problem I want to solve - file system driver hang: If a fs code happen to hit __wait_on_buffer right after pci pci_device_shutdown disabled msix, it will never make progress because the requests it waits for will never be completed. So the system hangs. In other words we will want to reset virtio device before pci_device_shutdown AND wake up all waiters. Unfortunately, neither your patch n...

...0 [kjournald] 3016 1 1 102168f27f0 UN 0.0 0 0 [kjournald] 3017 1 1 1021837b030 IN 0.0 0 0 [kjournald] 3018 1 7 10216fd0030 UN 0.0 0 0 [kjournald] 2 are in the UNITERRUPTIBLE state. But only PID 3018 shows __wait_on_buffer in its stack: crash> bt -f 3018 PID: 3018 TASK: 10216fd0030 CPU: 7 COMMAND: "kjournald" -----snip----- #2 [10215a83b30] __wait_on_buffer at ffffffff8017d504 10215a83b38: 000001005fa12ce8 0000000000000000 10215a83b48: 0000010216fd0030 ffffffff8017d38a 10215a83b...

...y to send interupts, > > > > which will be on IRQ lines seeing MSI-X disabled. Those interrupts will > > > > be unhandled, and may cause flood. > > > > Here is the problem I want to solve - file system driver hang: > > > > If a fs code happen to hit __wait_on_buffer right after pci pci_device_shutdown > > disabled msix, it will never make progress because the requests it waits for > > will never be completed. So the system hangs. > > Paolo says that pci reset of virtio scsi device guarantees > that all outstanding requests complete. >...

...y to send interupts, > > > > which will be on IRQ lines seeing MSI-X disabled. Those interrupts will > > > > be unhandled, and may cause flood. > > > > Here is the problem I want to solve - file system driver hang: > > > > If a fs code happen to hit __wait_on_buffer right after pci pci_device_shutdown > > disabled msix, it will never make progress because the requests it waits for > > will never be completed. So the system hangs. > > Paolo says that pci reset of virtio scsi device guarantees > that all outstanding requests complete. >...

http://www.sample.banga.lt/crash.gif System - fully (except kernel) updated RedHat 7.3. Filesystems - ext3 in default ordered mode. What could be the cause of the crash? Kernel update will solve the problem? Thanks, Mindaugas

...i-pci, the device may still try to send interupts, > > > which will be on IRQ lines seeing MSI-X disabled. Those interrupts will > > > be unhandled, and may cause flood. > > Here is the problem I want to solve - file system driver hang: > > If a fs code happen to hit __wait_on_buffer right after pci pci_device_shutdown > disabled msix, it will never make progress because the requests it waits for > will never be completed. So the system hangs. Paolo says that pci reset of virtio scsi device guarantees that all outstanding requests complete. If true and implemented corre...

...i-pci, the device may still try to send interupts, > > > which will be on IRQ lines seeing MSI-X disabled. Those interrupts will > > > be unhandled, and may cause flood. > > Here is the problem I want to solve - file system driver hang: > > If a fs code happen to hit __wait_on_buffer right after pci pci_device_shutdown > disabled msix, it will never make progress because the requests it waits for > will never be completed. So the system hangs. Paolo says that pci reset of virtio scsi device guarantees that all outstanding requests complete. If true and implemented corre...

Currently shutdown is nop for virtio devices, but the core code could remove things behind us such as MSI-X handler etc. For example in the case of virtio-scsi-pci, the device may still try to send interupts, which will be on IRQ lines seeing MSI-X disabled. Those interrupts will be unhandled, and may cause flood. Remove the device in "shutdown" callback to allow device drivers clean up

Currently shutdown is nop for virtio devices, but the core code could remove things behind us such as MSI-X handler etc. For example in the case of virtio-scsi-pci, the device may still try to send interupts, which will be on IRQ lines seeing MSI-X disabled. Those interrupts will be unhandled, and may cause flood. Remove the device in "shutdown" callback to allow device drivers clean up

...<ffffffff8046d720>] io_schedule+0x70/0xd0 [ 244.340438] [<ffffffff8014958e>] sync_buffer+0x4e/0x70 [ 244.340443] [<ffffffff8046ddd7>] __wait_on_bit+0x67/0xb0 [ 244.340448] [<ffffffff8046dea2>] out_of_line_wait_on_bit+0x82/0xb0 [ 244.340452] [<ffffffff80149522>] __wait_on_buffer+0x32/0x50 [ 244.340457] [<ffffffff801a0c27>] __ext3_get_inode_loc+0x2c7/0x350 [ 244.340462] [<ffffffff801a0d35>] ext3_iget+0x85/0x410 [ 244.340467] [<ffffffff801a7d98>] ext3_lookup+0xc8/0x150 [ 244.340472] [<ffffffff801248c2>] real_lookup+0x102/0x180 [ 244.340477]...

...<ffffffff8046d720>] io_schedule+0x70/0xd0 [ 244.340438] [<ffffffff8014958e>] sync_buffer+0x4e/0x70 [ 244.340443] [<ffffffff8046ddd7>] __wait_on_bit+0x67/0xb0 [ 244.340448] [<ffffffff8046dea2>] out_of_line_wait_on_bit+0x82/0xb0 [ 244.340452] [<ffffffff80149522>] __wait_on_buffer+0x32/0x50 [ 244.340457] [<ffffffff801a0c27>] __ext3_get_inode_loc+0x2c7/0x350 [ 244.340462] [<ffffffff801a0d35>] ext3_iget+0x85/0x410 [ 244.340467] [<ffffffff801a7d98>] ext3_lookup+0xc8/0x150 [ 244.340472] [<ffffffff801248c2>] real_lookup+0x102/0x180 [ 244.340477]...

...xt3_do_update_inode+710/848] (0xec1edc00)) Dec 24 13:48:39 10.17.0.2 kernel: [<c0168146>] (0xec1edc00)) Dec 24 13:48:39 10.17.0.2 kernel: [ext3_reserve_inode_write+49/176] (0xec1edc2c)) Dec 24 13:48:39 10.17.0.2 kernel: [<c01684e1>] (0xec1edc2c)) Dec 24 13:48:39 10.17.0.2 kernel: [__wait_on_buffer+142/160] (0xec1edc44)) Dec 24 13:48:39 10.17.0.2 kernel: [<c014104e>] (0xec1edc44)) Thanks, and merry christmas to all. Yuval PS - please CC me for any replies as I'm not subscribed to the list. thanks. -- Yuval Yeret Exanet yuval@exanet.com http://www.exanet.com Tel. 972-9-9717...

...nd subdirectories. Didn't read or copy any files. When I tried umount my rxvt freezed and: root 5471 0.0 0.1 1272 468 ? D 09:41 0:00 umount /mnt/floppy No. D ! Is this an ext3 bug, or loopback is still broken in 2.4.5 ? I had no problems mounting without ext3. WCHAN shows __wait_on_buffer I just rebooted, after trying without success to use SysRq and avoid fsck. I'd wait and build 2.4.6, but my load average... Any umount -> D. Parallelizing fsck version 1.22 (22-Jun-2001) /dev/ide/host0/bus0/target0/lun0/part1 was not cleanly unmounted, check forced. /dev/ide/host0/bus0/ta...

I have ext3 0.0.6b + 2.2.19 and cannot get ext3 to compile as a module. If I try to modularize it, or turn in off completely, the kernel build fails. Is there an easy fix for this, or is there something that I am missing? Thanks. Peter

When trying to build ext3 as a module, I get the follwing errors during the kernel link: /usr/bin/kgcc -D__KERNEL__ -I/home/brian/src/kernel-2.2.19-pre6mvd/linux-2.2.19pre6-kdb-ext3/include -c -o dummy_sym.o dummy_sym.c ld -m elf_i386 -T /home/brian/src/kernel-2.2.19-pre6mvd/linux-2.2.19pre6-kdb-ext3/arch/i386/vmlinux.lds -e stext arch/i386/kernel/head.o arch/i386/kernel/init_t ask.o -Map map

...cfd1710 [<a0000001003cee90>] blk_backing_dev_unplug+0x90/0xa0 sp=e00000003cfd7540 bsp=e00000003cfd16f0 [<a00000010012a020>] sync_buffer+0x100/0x120 sp=e00000003cfd7540 bsp=e00000003cfd16d8 [<a00000010012a480>] __wait_on_buffer+0x1e0/0x200 sp=e00000003cfd7540 bsp=e00000003cfd16b0 [<a00000010012e230>] __bread_slow+0x150/0x1a0 sp=e00000003cfd75a0 bsp=e00000003cfd1690 [<a00000010012eb00>] __bread+0x60/0x80 sp=e0...

Hi, A system running ext3 crashed this afternoon (nothing to do with ext3, bad network driver). Is was saving a file from emacs when it happened. The file system is 0.06b and had ordered data as the mount option. Let me emphasize this was running ext3 pure, not with SnapFS or InterMezzo layered on top of it. strace reveals that Emacs does open("existing file name", O_TRUNC |