Re: 2.6.22.6: kernel BUG at fs/locks.c:171 - Kernel

This is a discussion on Re: 2.6.22.6: kernel BUG at fs/locks.c:171 - Kernel ; Soeren Sonnenburg wrote: >> Fixing recursive fault but reboot is needed! > > Hmmhh, so now I rebooted and again tried to > > $ make > > the new kernel which again triggered this(?) BUG: I had a similar ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: Re: 2.6.22.6: kernel BUG at fs/locks.c:171

  1. Re: 2.6.22.6: kernel BUG at fs/locks.c:171

    Soeren Sonnenburg wrote:

    >> Fixing recursive fault but reboot is needed!

    >
    > Hmmhh, so now I rebooted and again tried to
    >
    > $ make
    >
    > the new kernel which again triggered this(?) BUG:


    I had a similar issue with 2.6.22.9, but as I had a proprietary nvidia
    module loaded, I didn't report it. X was not enabled, though.

    At this moment, the machine was spawning quite a bit of bash / awk etc.
    processes with large variables (50 MB or so), and used memory and CPU a lot.

    Normally, it's my desktop machine, and it's rarely on for more than ~12
    hours, but this time, I left it on for a couple of days.

    After this happened, these bash / awk processes died. After I restarted
    the script again, I lost ssh access to the machine, and I saw no more
    entries in the syslog. The machine was pingable though, and had it's
    network sockets still open (I could telnet to ssh port).
    I used SysRq to reboot the machine.



    Oct 3 10:14:09 tomek kernel: Eeek! page_mapcount(page) went negative! (-1)
    Oct 3 10:14:09 tomek kernel: page pfn = 13aa
    Oct 3 10:14:10 tomek kernel: page->flags = 40000400
    Oct 3 10:14:10 tomek kernel: page->count = 1
    Oct 3 10:14:10 tomek kernel: page->mapping = 00000000
    Oct 3 10:14:10 tomek kernel: vma->vm_ops = 0x0
    Oct 3 10:14:10 tomek kernel: ------------[ cut here ]------------
    Oct 3 10:14:10 tomek syslogd: /dev/tty12: Interrupted system call
    Oct 3 10:14:10 tomek kernel: kernel BUG at mm/rmap.c:628!
    Oct 3 10:14:10 tomek kernel: invalid opcode: 0000 [#1]
    Oct 3 10:14:10 tomek kernel: PREEMPT
    Oct 3 10:14:10 tomek kernel: Modules linked in: nvidia(P) iptable_nat
    nf_nat ipt_ULOG ipt_recent af_packet nf_conntrack_ipv4 xt_state
    nf_conntrack nfnetli
    nk ipt_REJECT xt_tcpudp iptable_filter ip_tables snd_seq_dummy x_tables
    snd_seq_oss snd_seq_midi_event snd_seq usblp loop dm_mod video thermal
    sbs fan cont
    ainer dock battery ac floppy cpufreq_conservative cpufreq_powersave
    processor snd_pcm_oss snd_mixer_oss snd_via82xx snd_ac97_codec ac97_bus
    snd_pcm snd_tim
    er snd_page_alloc snd_mpu401_uart snd_rawmidi snd_seq_device snd
    soundcore ehci_hcd i2c_viapro i2c_core via_rhine uhci_hcd tsdev evdev
    usbcore via_agp agpg
    art 8139cp 8139too mii sg
    Oct 3 10:14:10 tomek kernel: CPU: 0
    Oct 3 10:14:10 tomek kernel: EIP: 0060:[] Tainted: P
    VLI
    Oct 3 10:14:10 tomek kernel: EFLAGS: 00010246 (2.6.22.9-3 #1)
    Oct 3 10:14:10 tomek kernel: EIP is at page_remove_rmap+0xd7/0x105
    Oct 3 10:14:10 tomek kernel: eax: 00000000 ebx: c1027540 ecx:
    e8a2e000 edx: 00000002
    Oct 3 10:14:10 tomek kernel: esi: c4226f20 edi: c3ab828c ebp:
    e8a2fea4 esp: e8a2fe94
    Oct 3 10:14:10 tomek kernel: ds: 007b es: 007b fs: 0000 gs: 0000
    ss: 0068
    Oct 3 10:14:10 tomek kernel: Process bash (pid: 28682, ti=e8a2e000
    task=db280000 task.ti=e8a2e000)
    Oct 3 10:14:10 tomek kernel: Stack: c0346d1d 00000000 c1027540 0b4a3000
    e8a2ff00 c0154edc e8a2e000 28b98fff
    Oct 3 10:14:10 tomek kernel: 013aaa80 00000000 c4226f20 e8a2ff18
    00000001 00000000 00000000 0b800000
    Oct 3 10:14:10 tomek kernel: c21330b4 c21330b4 d896d780 c03f2200
    00000000 ffffffff 28b99000 00000000
    Oct 3 10:14:10 tomek kernel: Call Trace:
    Oct 3 10:14:10 tomek kernel: [] show_trace_log_lvl+0x1a/0x2f
    Oct 3 10:14:10 tomek kernel: [] show_stack_log_lvl+0x9b/0xa3
    Oct 3 10:14:10 tomek kernel: [] show_registers+0x1d7/0x30c
    Oct 3 10:14:10 tomek kernel: [] die+0xfe/0x1d6
    Oct 3 10:14:10 tomek kernel: [] do_trap+0x89/0xa2
    Oct 3 10:14:10 tomek kernel: [] do_invalid_op+0x88/0x92
    Oct 3 10:14:10 tomek kernel: [] error_code+0x6a/0x70
    Oct 3 10:14:10 tomek kernel: [] unmap_vmas+0x236/0x425
    Oct 3 10:14:10 tomek kernel: [] exit_mmap+0x68/0xf0
    Oct 3 10:14:10 tomek kernel: [] mmput+0x1e/0x88
    Oct 3 10:14:10 tomek kernel: [] exit_mm+0xbb/0xc1
    Oct 3 10:14:10 tomek kernel: [] do_exit+0x1f0/0x720
    Oct 3 10:14:12 tomek kernel: [] sys_exit_group+0x0/0x11
    Oct 3 10:14:12 tomek kernel: [] sys_exit_group+0xf/0x11
    Oct 3 10:14:12 tomek kernel: [] sysenter_past_esp+0x5f/0x99
    Oct 3 10:14:12 tomek kernel: =======================
    Oct 3 10:14:12 tomek kernel: Code: c0 74 0d 8b 50 08 b8 4d 6d 34 c0 e8
    ea 0f fe ff 8b 46 48 85 c0 74 14 8b 40 10 85 c0 74 0d 8b 50 2c b8 6c 6d
    34 c0 e8 cf
    0f fe ff <0f> 0b eb fe 8b 53 10 8b 03 83 e2 01 c1 e8 1e f7 da 83 c2 04 69
    Oct 3 10:14:12 tomek kernel: EIP: []
    page_remove_rmap+0xd7/0x105 SS:ESP 0068:e8a2fe94
    Oct 3 10:14:12 tomek kernel: Fixing recursive fault but reboot is needed!
    Oct 3 10:14:12 tomek kernel: BUG: scheduling while atomic:
    bash/0x00000002/28682
    Oct 3 10:14:12 tomek kernel: INFO: lockdep is turned off.
    Oct 3 10:14:12 tomek kernel: [] show_trace_log_lvl+0x1a/0x2f
    Oct 3 10:14:12 tomek kernel: [] show_trace+0x12/0x14
    Oct 3 10:14:12 tomek kernel: [] dump_stack+0x15/0x17
    Oct 3 10:14:12 tomek kernel: [] __sched_text_start+0x6e/0x5d5
    Oct 3 10:14:12 tomek kernel: [] do_exit+0xf1/0x720
    Oct 3 10:14:12 tomek kernel: [] die+0x1ce/0x1d6
    Oct 3 10:14:12 tomek kernel: [] do_trap+0x89/0xa2
    Oct 3 10:14:12 tomek kernel: [] do_invalid_op+0x88/0x92
    Oct 3 10:14:12 tomek kernel: [] error_code+0x6a/0x70
    Oct 3 10:14:12 tomek kernel: [] unmap_vmas+0x236/0x425
    Oct 3 10:14:12 tomek kernel: [] exit_mmap+0x68/0xf0
    Oct 3 10:14:12 tomek kernel: [] mmput+0x1e/0x88
    Oct 3 10:14:12 tomek kernel: [] exit_mm+0xbb/0xc1
    Oct 3 10:14:12 tomek kernel: [] do_exit+0x1f0/0x720
    Oct 3 10:14:12 tomek kernel: [] sys_exit_group+0x0/0x11
    Oct 3 10:14:12 tomek kernel: [] sys_exit_group+0xf/0x11
    Oct 3 10:14:12 tomek kernel: [] sysenter_past_esp+0x5f/0x99
    Oct 3 10:14:12 tomek kernel: =======================



    --
    Tomasz Chmielewski
    http://blog.wpkg.org
    -
    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/

  2. Re: 2.6.22.6: kernel BUG at fs/locks.c:171


    On Tue, 2007-10-09 at 15:09 +0200, Tomasz Chmielewski wrote:
    > Soeren Sonnenburg wrote:
    >
    > >> Fixing recursive fault but reboot is needed!

    > >
    > > Hmmhh, so now I rebooted and again tried to
    > >
    > > $ make
    > >
    > > the new kernel which again triggered this(?) BUG:

    >
    > I had a similar issue with 2.6.22.9, but as I had a proprietary nvidia
    > module loaded, I didn't report it. X was not enabled, though.
    >
    > At this moment, the machine was spawning quite a bit of bash / awk etc.
    > processes with large variables (50 MB or so), and used memory and CPU a lot.
    >
    > Normally, it's my desktop machine, and it's rarely on for more than ~12
    > hours, but this time, I left it on for a couple of days.
    >
    > After this happened, these bash / awk processes died. After I restarted
    > the script again, I lost ssh access to the machine, and I saw no more


    I am afraid you are seeing some kind of hardware failure/bad driver
    behavior, just the symptom is the same.

    I am saying this as I have an uptime of 22 days with that very same
    machine now. And all I changed was unloading the asus p7131 dvb-t driver
    (saa71xx).

    Soeren
    -
    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/

  3. Re: 2.6.22.6: kernel BUG at fs/locks.c:171

    On Tue, 9 Oct 2007, Tomasz Chmielewski wrote:
    >
    > I had a similar issue with 2.6.22.9, but as I had a proprietary nvidia module
    > loaded, I didn't report it. X was not enabled, though.


    There is indeed a strong likelihood that yours is
    related to that nvidia(P): please take it to them.

    Hugh

    > Oct 3 10:14:09 tomek kernel: Eeek! page_mapcount(page) went negative! (-1)
    > Oct 3 10:14:09 tomek kernel: page pfn = 13aa
    > Oct 3 10:14:10 tomek kernel: page->flags = 40000400
    > Oct 3 10:14:10 tomek kernel: page->count = 1
    > Oct 3 10:14:10 tomek kernel: page->mapping = 00000000
    > Oct 3 10:14:10 tomek kernel: vma->vm_ops = 0x0
    > Oct 3 10:14:10 tomek kernel: ------------[ cut here ]------------
    > Oct 3 10:14:10 tomek syslogd: /dev/tty12: Interrupted system call
    > Oct 3 10:14:10 tomek kernel: kernel BUG at mm/rmap.c:628!
    > Oct 3 10:14:10 tomek kernel: invalid opcode: 0000 [#1]
    > Oct 3 10:14:10 tomek kernel: PREEMPT
    > Oct 3 10:14:10 tomek kernel: Modules linked in: nvidia(P) ...
    > Oct 3 10:14:10 tomek kernel: CPU: 0
    > Oct 3 10:14:10 tomek kernel: EIP: 0060:[] Tainted: P VLI
    > Oct 3 10:14:10 tomek kernel: EFLAGS: 00010246 (2.6.22.9-3 #1)
    > Oct 3 10:14:10 tomek kernel: EIP is at page_remove_rmap+0xd7/0x105

    -
    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/

+ Reply to Thread