On Fri, 2010-07-30 at 13:23 +0200, Victor Gomes Do Vale wrote:
[...]
Well, I tested the memory with memtest86, it gave me nothing (2 pass clear).
I booted and set the X with vesa mode and nvidia unloaded yesterday, the
machine was dead this morning.
Do you have other ideas ?
Please test the
Ben Hutchings wrote:
On Wed, 2010-07-28 at 09:42 +0200, ulysse31 wrote:
[...]
kernel:[63659.784275] invalid opcode: [#1] SMP
[...]
kernel:[63659.784275] [c017b969] kmem_cache_alloc+0x47/0x87
[...]
kernel:[63659.784275] Code: 8b 75 00 39 ee 75 15 8b 75 10 8d 45 10
Package: linux-2.6
Version: 2.6.26-24
Severity: critical
Justification: breaks the whole system
I have a desktop machine running debian lenny, with nfs4/kerberos for home
directory accounting, which works great on my own machine.
But on a specific machine, it kernel panics all nights, when the
severity 590658 important
thanks
On Wed, Jul 28, 2010 at 09:42:13AM +0200, ulysse31 wrote:
Who?
Package: linux-2.6
Version: 2.6.26-24
Severity: critical
Justification: breaks the whole system
No, the kernel is the system.
** Tainted: P (1)
* Proprietary module has been loaded.
This
Processing commands for cont...@bugs.debian.org:
severity 590658 important
Bug #590658 [linux-2.6] linux-image-2.6.26-2-686-bigmem: 2.6.26-2 bigmem nfs4
kerberos kernel panic
Severity set to 'important' from 'critical'
thanks
Stopping processing here.
Please contact me if you need
Bastian Blank wrote:
severity 590658 important
thanks
On Wed, Jul 28, 2010 at 09:42:13AM +0200, ulysse31 wrote:
Who?
Package: linux-2.6
Version: 2.6.26-24
Severity: critical
Justification: breaks the whole system
No, the kernel is the system.
** Tainted: P (1)
* Proprietary
On Wed, 2010-07-28 at 09:42 +0200, ulysse31 wrote:
[...]
kernel:[63659.784275] invalid opcode: [#1] SMP
[...]
kernel:[63659.784275] [c017b969] kmem_cache_alloc+0x47/0x87
[...]
kernel:[63659.784275] Code: 8b 75 00 39 ee 75 15 8b 75 10 8d 45 10 c7 45 34
01 00 00 00 39 c6 0f 84 a5 00 00
7 matches
Mail list logo
