Bug#632678: linux-image-2.6.32-5-amd64: el sistema se cuelga de forma aleatoria
Ben was right, I used memtest86+ and found many RAM errors. After correcting this problem, the system seems to work well even in high load situations. Thank you.
Bug#632678: linux-image-2.6.32-5-amd64: el sistema se cuelga de forma aleatoria
Package: linux-2.6 Version: 2.6.32-35 Severity: important De vez en cuando el sistema emite un pitido corto por el altavoz interno del ordenador y la pantalla se apaga. Se puede reiniciar con la combinación ALT+SysRQ+REISUB. El momento del cuelgue es aleatorio, pero la probabilidad aumenta con la ejecución de más aplicaciones o de aplicaciones que consumen más recursos. En el momento del cuelgue el archivo kernel.log indica que se produjo una referencia a puntero nulo: Jun 22 22:59:20 debian kernel: [ 5392.581979] BUG: unable to handle kernel NULL pointer dereference at 0292 Jun 22 22:59:20 debian kernel: [ 5392.581993] IP: [812072ca] vt_console_device+0x14/0x1e Jun 22 22:59:20 debian kernel: [ 5392.582010] PGD 6cc24067 PUD 376d0067 PMD 0 Jun 22 22:59:20 debian kernel: [ 5392.582020] Oops: 0002 [#1] SMP Jun 22 22:59:20 debian kernel: [ 5392.582026] last sysfs file: /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq Jun 22 22:59:20 debian kernel: [ 5392.582034] CPU 1 Jun 22 22:59:20 debian kernel: [ 5392.582037] Modules linked in: powernow_k8 cpufreq_powersave cpufreq_conservative cpufreq_userspace cpufreq_stats ppdev lp sco bridge stp bnep rfcomm l2cap bluetooth rfkill binfmt_misc fuse loop firewire_sbp2 snd_hda_codec_via snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_midi snd_rawmidi snd_seq_midi_event radeon snd_seq ttm drm_kms_helper snd_timer snd_seq_device snd drm soundcore snd_page_alloc i2c_piix4 i2c_algo_bit shpchp parport_pc i2c_core pci_hotplug parport edac_core k10temp edac_mce_amd asus_atk0110 psmouse processor button joydev evdev serio_raw pcspkr ext4 mbcache jbd2 crc16 usbhid hid sd_mod crc_t10dif ata_generic ohci_hcd firewire_ohci firewire_core pata_atiixp crc_itu_t ahci libata r8169 ehci_hcd mii scsi_mod thermal thermal_sys usbcore nls_base [last unloaded: scsi_wait_scan] Jun 22 22:59:20 debian kernel: [ 5392.582162] Pid: 1356, comm: Xorg Not tainted 2.6.32-5-amd64 #1 System Product Name Jun 22 22:59:20 debian kernel: [ 5392.582168] RIP: 0010:[812072ca] [812072ca] vt_console_device+0x14/0x1e Jun 22 22:59:20 debian kernel: [ 5392.582181] RSP: 0018:88006cf659b0 EFLAGS: 00010282 Jun 22 22:59:20 debian kernel: [ 5392.582186] RAX: 0006 RBX: RCX: Jun 22 22:59:20 debian kernel: [ 5392.582192] RDX: 88006ef9a3c0 RSI: 0292 RDI: 88006ea73000 Jun 22 22:59:20 debian kernel: [ 5392.582197] RBP: 88006ea73000 R08: 88006cc73790 R09: 88006ea73000 Jun 22 22:59:20 debian kernel: [ 5392.582203] R10: 0300 R11: 812072c4 R12: 88006efa7c01 Jun 22 22:59:20 debian kernel: [ 5392.582209] R13: 88006efa7cc0 R14: 88006cf65ad8 R15: 0005 Jun 22 22:59:20 debian kernel: [ 5392.582216] FS: 7f5effcc8700() GS:88000184() knlGS: Jun 22 22:59:20 debian kernel: [ 5392.58] CS: 0010 DS: ES: CR0: 80050033 Jun 22 22:59:20 debian kernel: [ 5392.582227] CR2: 0292 CR3: 6efee000 CR4: 06e0 Jun 22 22:59:20 debian kernel: [ 5392.582233] DR0: DR1: DR2: Jun 22 22:59:20 debian kernel: [ 5392.582239] DR3: DR6: 0ff0 DR7: 0400 Jun 22 22:59:20 debian kernel: [ 5392.582246] Process Xorg (pid: 1356, threadinfo 88006cf64000, task 88006da09c40) Jun 22 22:59:20 debian kernel: [ 5392.582250] Stack: Jun 22 22:59:20 debian kernel: [ 5392.582254] 811fbc22 88006ea73000 Jun 22 22:59:20 debian kernel: [ 5392.582263] 0 88006efa7cc0 88006d90c9b0 811f854a 0020 Jun 22 22:59:20 debian kernel: [ 5392.582272] 0 0300 88006efa7cc0 88006cf65ad8 Jun 22 22:59:20 debian kernel: [ 5392.582282] Call Trace: Jun 22 22:59:20 debian kernel: [ 5392.582292] [811fbc22] ? n_tty_poll+0x124/0x138 Jun 22 22:59:20 debian kernel: [ 5392.582300] [811f854a] ? tty_poll+0x56/0x6d Jun 22 22:59:20 debian kernel: [ 5392.582311] [810fc436] ? do_select+0x37b/0x57a Jun 22 22:59:20 debian kernel: [ 5392.582320] [810fcaaf] ? __pollwait+0x0/0xd6 Jun 22 22:59:20 debian kernel: [ 5392.582328] [810fcb85] ? pollwake+0x0/0x5b Jun 22 22:59:20 debian kernel: [ 5392.582336] [810fcb85] ? pollwake+0x0/0x5b Jun 22 22:59:20 debian kernel: [ 5392.582344] [810fcb85] ? pollwake+0x0/0x5b Jun 22 22:59:20 debian kernel: [ 5392.582352] [810fcb85] ? pollwake+0x0/0x5b Jun 22 22:59:20 debian kernel: [ 5392.582362] [810c2c71] ? shmem_delete_inode+0x0/0xf8 Jun 22 22:59:20 debian kernel: [ 5392.582371] [81064e3b] ? bit_waitqueue+0x10/0xa0 Jun 22 22:59:20 debian kernel: [ 5392.582379] [81116dbe] ? fsnotify_clear_marks_by_inode+0x20/0xcd Jun 22 22:59:20 debian kernel: [ 5392.582390] [810e5bbd] ? virt_to_head_page+0x9/0x2a Jun
Bug#632678: linux-image-2.6.32-5-amd64: el sistema se cuelga de forma aleatoria
retitle 632678 [radeon] NULL pointer dereference in vt_console_device, beep, screen goes black tags 632678 + moreinfo quit Hi, Simón C. A. wrote: De vez en cuando el sistema emite un pitido corto [...] translate.google.com comes to the rescue: | Occasionally the system emits a short beep through the internal PC speaker | and the display turns off. It's possible to reboot using the combination | ALT+SysRQ+REISUB. | | The time of the crash is random, but the probability increases with | more applications running or applications consuming more resources. | At the time of the crash, the kernel.log file indicates that there | was a null pointer reference: Jun 22 22:59:20 debian kernel: [ 5392.581979] BUG: unable to handle kernel NULL pointer dereference at 0292 Jun 22 22:59:20 debian kernel: [ 5392.581993] IP: [812072ca] vt_console_device+0x14/0x1e So, the .device method of vt_console_driver was called with one of its arguments equal to NULL. The only caller I know of is kernel/printk.c::console_device, which suggests that the latter was called with its argument NULL... [...] Jun 22 22:59:20 debian kernel: [ 5392.582282] Call Trace: Jun 22 22:59:20 debian kernel: [ 5392.582292] [811fbc22] ? n_tty_poll+0x124/0x138 Jun 22 22:59:20 debian kernel: [ 5392.582300] [811f854a] ? tty_poll+0x56/0x6d Jun 22 22:59:20 debian kernel: [ 5392.582311] [810fc436] ? do_select+0x37b/0x57a Jun 22 22:59:20 debian kernel: [ 5392.582320] [810fcaaf] ? __pollwait+0x0/0xd6 Jun 22 22:59:20 debian kernel: [ 5392.582328] [810fcb85] ? pollwake+0x0/0x5b Jun 22 22:59:20 debian kernel: [ 5392.582336] [810fcb85] ? pollwake+0x0/0x5b Jun 22 22:59:20 debian kernel: [ 5392.582344] [810fcb85] ? pollwake+0x0/0x5b Jun 22 22:59:20 debian kernel: [ 5392.582352] [810fcb85] ? pollwake+0x0/0x5b Jun 22 22:59:20 debian kernel: [ 5392.582362] [810c2c71] ? shmem_delete_inode+0x0/0xf8 Jun 22 22:59:20 debian kernel: [ 5392.582371] [81064e3b] ? bit_waitqueue+0x10/0xa0 Jun 22 22:59:20 debian kernel: [ 5392.582379] [81116dbe] ? fsnotify_clear_marks_by_inode+0x20/0xcd Jun 22 22:59:20 debian kernel: [ 5392.582390] [810e5bbd] ? virt_to_head_page+0x9/0x2a Jun 22 22:59:20 debian kernel: [ 5392.582398] [8103fa3a] ? __wake_up+0x30/0x44 Jun 22 22:59:20 debian kernel: [ 5392.582441] [a0388d3f] ? radeon_bo_wait+0xb1/0xbd [radeon] Jun 22 22:59:20 debian kernel: [ 5392.582451] [812fbab6] ? mutex_lock+0xd/0x31 Jun 22 22:59:20 debian kernel: [ 5392.582460] [810fc7b9] ? core_sys_select+0x184/0x21e ... but it is not in the backtrace. So much for that guess. Could you try a kernel from unstable or experimental and let us know how it goes? Thanks for reporting, Jonathan Jun 22 22:59:20 debian kernel: [ 5392.582471] [8101657d] ? read_tsc+0xa/0x20 Jun 22 22:59:20 debian kernel: [ 5392.582479] [8106c48f] ? ktime_get_ts+0x68/0xb2 Jun 22 22:59:20 debian kernel: [ 5392.582487] [810fca86] ? sys_select+0x92/0xbb Jun 22 22:59:20 debian kernel: [ 5392.582495] [81010b42] ? system_call_fastpath+0x16/0x1b Jun 22 22:59:20 debian kernel: [ 5392.582500] Code: 48 6b c0 28 48 8b 80 70 c3 67 81 8a 80 23 01 00 00 d0 e8 83 e0 03 c3 66 8b 47 42 66 85 c0 74 05 98 ff c8 eb 06 8b 05 7e 5a 47 00 89 06 48 8b 05 8d 6a 47 00 c3 8a 87 ec 00 00 00 83 e0 01 3c 01 Jun 22 22:59:20 debian kernel: [ 5392.582563] RIP [812072ca] vt_console_device+0x14/0x1e Jun 22 22:59:20 debian kernel: [ 5392.582572] RSP 88006cf659b0 Jun 22 22:59:20 debian kernel: [ 5392.582576] CR2: 0292 Jun 22 22:59:20 debian kernel: [ 5392.582581] ---[ end trace 1d363e716392f765 ]--- -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110704204341.GA6660@elie
Bug#632678: linux-image-2.6.32-5-amd64: el sistema se cuelga de forma aleatoria
On Mon, 2011-07-04 at 15:43 -0500, Jonathan Nieder wrote: Simón C. A. wrote: De vez en cuando el sistema emite un pitido corto [...] translate.google.com comes to the rescue: | Occasionally the system emits a short beep through the internal PC speaker | and the display turns off. It's possible to reboot using the combination | ALT+SysRQ+REISUB. | | The time of the crash is random, but the probability increases with | more applications running or applications consuming more resources. | At the time of the crash, the kernel.log file indicates that there | was a null pointer reference: Jun 22 22:59:20 debian kernel: [ 5392.581979] BUG: unable to handle kernel NULL pointer dereference at 0292 Jun 22 22:59:20 debian kernel: [ 5392.581993] IP: [812072ca] vt_console_device+0x14/0x1e So, the .device method of vt_console_driver was called with one of its arguments equal to NULL. The only caller I know of is kernel/printk.c::console_device, which suggests that the latter was called with its argument NULL... [...] ... but it is not in the backtrace. [...] I think this is likely due to faulty RAM resulting in a jump to the wrong address. Simón, please use the memtest86+ package to test the RAM on this computer. Ben. -- Ben Hutchings This sentence contradicts itself - no actually it doesn't. signature.asc Description: This is a digitally signed message part