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 0000000000000292 > > Jun 22 22:59:20 debian kernel: [ 5392.581993] IP: [<ffffffff812072ca>] 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.
Description: This is a digitally signed message part