Your message dated Mon, 29 Nov 2010 01:03:30 +0100
with message-id <[email protected]>
and subject line Re: Nvidia kernel module 190.42 crashes on Linux AMD64 2.6.31
has caused the Debian Bug report #561497,
regarding Nvidia kernel module 190.42 crashes on Linux AMD64 2.6.31
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
561497: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=561497
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: nvidia-kernel-source
Version: 190.42-3
The module crashes with the following trace:
[ 108.108361] nvidia: module license 'NVIDIA' taints kernel.
[ 108.114152] Disabling lock debugging due to kernel taint
[ 108.389328] ACPI: PCI Interrupt Link [APC3] enabled at IRQ 18
[ 108.392164] nvidia 0000:04:00.0: PCI INT A -> Link[APC3] -> GSI 18 (level,
low) -> IRQ 18
[ 108.401390] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 190.42 Tue Oct
20 20:25:42 PDT 2009
[ 110.101619] BUG: unable to handle kernel NULL pointer dereference at (null)
[ 110.105008] IP: [<(null)>] (null)
[ 110.105008] PGD 33640f067 PUD 33f0d8067 PMD 0
[ 110.105008] Oops: 0010 [#1] SMP
[ 110.105008] last sysfs file:
/sys/devices/pci0000:00/0000:00:0e.0/0000:04:00.0/resource
[ 110.105008] CPU 2
[ 110.105008] Modules linked in: nvidia(P) cpufreq_conservative
cpufreq_powersave cpufreq_userspace cpufreq_stats powernow_k8 vmnet vmblock vmci
vmmon sco bridge bnep rfcomm l2cap bluetooth rfkill vbo
xnetflt vboxnetadp vboxdrv binfmt_misc fuse 8021q garp stp w83792d usblp
snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm_oss snd_mixer_oss snd_mpu401
snd_mpu401_uart snd_pcm snd_seq_midi snd_rawmidi snd_s
eq_midi_event snd_seq i2c_nforce2 parport_pc i2c_core amd64_edac_mod snd_timer
processor ns558 edac_core pcspkr gameport parport k8temp snd_seq_device button
snd snd_page_alloc soundcore evdev ext3 jbd
mbcache raid10 md_mod ide_cd_mod usbhid usb_storage hid cdrom sd_mod crc_t10dif
ide_pci_generic ata_generic ohci_hcd firewire_ohci amd74xx firewire_core
crc_itu_t ide_core sata_sil tg3 libphy sata_nv ehci_hcd libata scsi_mod thermal
fan thermal_sys [last unloaded: scsi_wait_scan]
[ 110.105008] Pid: 3322, comm: Xorg Tainted: P 2.6.31-1-amd64 #1
System Product Name
[ 110.105008] RIP: 0010:[<0000000000000000>] [<(null)>] (null)
[ 110.105008] RSP: 0000:ffffc90000403d08 EFLAGS: 00013282
[ 110.105008] RAX: 00000000001a0a30 RBX: 0000000000000100 RCX: 0000000000000100
[ 110.105008] RDX: ffffc90014680000 RSI: ffff88033f1be000 RDI: ffff88033f1ad000
[ 110.105008] RBP: ffff8803325b2da8 R08: ffff88033f13d000 R09: ffff88033f1be000
[ 110.105008] R10: 0000000000000076 R11: 0000000000000040 R12: 0000000000100000
[ 110.105008] R13: 0000000000000438 R14: ffff88033f1be000 R15: 0000000000000001
[ 110.105008] FS: 00007f0d48b97790(0000) GS:ffffc90000400000(0000)
knlGS:0000000000000000
[ 110.105008] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 110.105008] CR2: 0000000000000000 CR3: 00000003370c5000 CR4: 00000000000006e0
[ 110.105008] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 110.105008] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 110.105008] Process Xorg (pid: 3322, threadinfo ffff8803370a0000, task
ffff88033d4267c0)
[ 110.105008] Stack:
[ 110.105008] ffffffffa06cb0a8 ffff88033f13e000 0000000000000001
ffff88033f088000
[ 110.105008] <0> 0000000000000000 ffff88033f1be000 ffffffffa0649f02
0000000000000000
[ 110.105008] <0> 000000000000035c ffff88033f13e000 000000000773004e
ffff88033f1be000
[ 110.105008] Call Trace:
[ 110.105008] <IRQ>
[ 110.105008] [<ffffffffa06cb0a8>] ? _nv017804rm+0x2646/0x389d [nvidia]
[ 110.105008] [<ffffffffa0649f02>] ? _nv020476rm+0xe3c/0x10c9 [nvidia]
[ 110.105008] [<ffffffffa0630bd7>] ? _nv020315rm+0x5c/0xc5 [nvidia]
[ 110.105008] [<ffffffffa07ea5eb>] ? _nv013629rm+0x58c/0xbb9 [nvidia]
[ 110.105008] [<ffffffffa096321f>] ? _nv008580rm+0x2eb/0x550 [nvidia]
[ 110.105008] [<ffffffffa09483d6>] ? _nv008600rm+0x66/0x90 [nvidia]
[ 110.105008] [<ffffffffa0a06ab0>] ? _nv003826rm+0xa0/0xd3 [nvidia]
[ 110.105008] [<ffffffffa0a0c743>] ? rm_isr_bh+0x5a/0x8d [nvidia]
[ 110.105008] [<ffffffff81061b9c>] ? tasklet_action+0x88/0xf5
[ 110.105008] [<ffffffff810638d6>] ? __do_softirq+0xe2/0x1bc
[ 110.105008] [<ffffffff8101302c>] ? call_softirq+0x1c/0x30
[ 110.105008] [<ffffffff8101530e>] ? do_softirq+0x4e/0xa9
[ 110.105008] [<ffffffff810634e0>] ? irq_exit+0x4f/0xba
[ 110.105008] [<ffffffff8101498f>] ? do_IRQ+0xb0/0xde
[ 110.105008] [<ffffffff8102b1ae>] ? smp_apic_timer_interrupt+0x97/0xbc
[ 110.105008] [<ffffffff81012853>] ? ret_from_intr+0x0/0x11
[ 110.105008] <EOI>
[ 110.105008] Code: Bad RIP value.
[ 110.105008] RIP [<(null)>] (null)
[ 110.105008] RSP <ffffc90000403d08>
[ 110.105008] CR2: 0000000000000000
[ 110.455422] ---[ end trace 18bcbcf56f5fe79b ]---
The same problem exists with Linux 2.6.32-2.
185.18.36-2 works fine with a 2.6.31 kernel, but does not compile with a
2.6.32-2 kernel.
--
Marc Petit-Huguenin
Personal email: [email protected]
Professional email: [email protected]
Blog: http://blog.marc.petit-huguenin.org
--- End Message ---
--- Begin Message ---
On Wednesday, 25. August 2010 05:09:00 Andreas Beckmann wrote:
> On Thursday, 17. December 2009 18:49:39 Marc Petit-Huguenin wrote:
> > Package: nvidia-kernel-source
> > Version: 190.42-3
> >
> > The module crashes with the following trace:
>
> [snip]
>
> > The same problem exists with Linux 2.6.32-2.
> >
> > 185.18.36-2 works fine with a 2.6.31 kernel, but does not compile with a
> > 2.6.32-2 kernel.
>
> Yesterday nvidia-graphics-drivers 195.36.31-2 was uploaded to unstable.
> Does this, in combination with kernel 2.6.32-5 from unstable, fix your
> problems?
This bug was reported against a very old version of the NVIDIA driver.
A few months ago we asked for testing the current driver version, but so far
we haven't got a reply. Therefore I assume the problem does no longer occur
and I'm closing this report now.
If you can still reproduce the problem with the current driver version
(195.36.31-6 in testing/unstable or 260.19.21-1 in experimental) and kernel
and Xorg from testing or unstable, feel free to reopen this bug report.
Andreas
--- End Message ---
