FS#10399 - Crash after upgrade to kernel 2.6.25.3-1

Attached to Project: Arch Linux
Opened by Mårten Olsson (maos) - Monday, 12 May 2008, 19:33 GMT
Last edited by Thomas Bächler (brain0) - Tuesday, 13 May 2008, 11:28 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture x86_64
Severity Low
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
After upgrading to kernel 2.6.25.3-1 I get a crash when login into X (XFCE4, compiz-fusion, emerald)

Additional info:
* package version(s)
kernel26-2.6.25.3-1

mesa 7.0.3-1
nvidia 169.12-3
nvidia-utils 169.12-1

* config and/or log files etc.
May 12 20:50:49 rincewind BUG: unable to handle kernel NULL pointer dereference at 0000000000000248
May 12 20:50:49 rincewind IP: [<ffffffff885cc337>] :nvidia:os_set_mlock_capability+0x17/0x40
May 12 20:50:49 rincewind PGD b0679067 PUD b0678067 PMD 0
May 12 20:50:49 rincewind Oops: 0002 [1] PREEMPT SMP
May 12 20:50:49 rincewind CPU 1
May 12 20:50:49 rincewind Modules linked in: uhci_hcd amd74xx ide_core nf_conntrack_ipv4 xt_state xt_tcpudp iptable_filter ip_tables x_tables ns558 parport_pc snd_mpu401 snd_mpu401_uart snd_seq_oss snd_seq_midi_event snd_intel8x0 snd_ac97_codec snd_seq ppdev snd_rawmidi snd_seq_device snd_pcm_oss snd_mixer_oss psmouse analog ac97_bus snd_pcm nvidia(P) snd_timer snd gameport lp ppp_generic slhc parport pcspkr serio_raw soundcore snd_page_alloc sg joydev thermal battery ac nf_conntrack_ftp nf_conntrack video output fan button evdev cpufreq_ondemand cpufreq_userspace cpufreq_conservative powernow_k8 freq_table processor fuse k8temp it87 hwmon_vid eeprom i2c_nforce2 i2c_core forcedeth rtc_cmos rtc_core rtc_lib ext3 jbd mbcache sr_mod cdrom sd_mod ata_generic usbhid hid ff_memless sata_nv pata_amd ehci_hcd pata_acpi libata ohci_hcd scsi_mod dock usbcore
May 12 20:50:49 rincewind Pid: 5759, comm: glxinfo Tainted: P 2.6.25-ARCH #1
May 12 20:50:49 rincewind RIP: 0010:[<ffffffff885cc337>] [<ffffffff885cc337>] :nvidia:os_set_mlock_capability+0x17/0x40
May 12 20:50:49 rincewind RSP: 0018:ffff8100a888de00 EFLAGS: 00010296
May 12 20:50:49 rincewind RAX: 0000000000000000 RBX: 0000000000000000 RCX: 000000000000000a
May 12 20:50:49 rincewind RDX: 0000000000000001 RSI: 0000000000000296 RDI: 0000000000000296
May 12 20:50:49 rincewind RBP: ffff8100b0636fd8 R08: 0000000000000002 R09: ffff8100a888dd1c
May 12 20:50:49 rincewind R10: 0000000000000000 R11: ffffffff803be7a0 R12: ffff8100bed26000
May 12 20:50:49 rincewind R13: ffff8100be66b800 R14: ffff8100bee5ed40 R15: 000000000000000c
May 12 20:50:49 rincewind FS: 00007fec74c9a740(0000) GS:ffff8100bf80e480(0000) knlGS:0000000000000000
May 12 20:50:49 rincewind CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
May 12 20:50:49 rincewind CR2: 0000000000000248 CR3: 00000000b0762000 CR4: 00000000000006e0
May 12 20:50:49 rincewind DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
May 12 20:50:49 rincewind DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
May 12 20:50:49 rincewind Process glxinfo (pid: 5759, threadinfo ffff8100a888c000, task ffff8100b07d0000)
May 12 20:50:49 rincewind Stack: ffffffff8851ae3a ffffffff8851d516 000000000000005b ffffffff88a5eee0
May 12 20:50:49 rincewind ffff8100b0686c00 ffffffff8835222d ffff8100b0634000 ffffffff88a5eee0
May 12 20:50:49 rincewind ffff8100bee5ed40 ffff8100b0634000 ffffffff8851bd4d 000000000000005b
May 12 20:50:49 rincewind Call Trace:
May 12 20:50:49 rincewind [<ffffffff8851ae3a>] ? :nvidia:_nv002788rm+0x9/0x18
May 12 20:50:49 rincewind [<ffffffff8851d516>] ? :nvidia:rm_write_watch_init+0x65/0x87
May 12 20:50:49 rincewind [<ffffffff8835222d>] ? :nvidia:_nv002878rm+0x51d/0x6f9
May 12 20:50:49 rincewind [<ffffffff8851bd4d>] ? :nvidia:rm_ioctl+0x2f/0x67
May 12 20:50:49 rincewind [<ffffffff885c906f>] ? :nvidia:nv_kern_ioctl+0x12f/0x3e0
May 12 20:50:49 rincewind [<ffffffff885c936c>] ? :nvidia:nv_kern_unlocked_ioctl+0x1c/0x30
May 12 20:50:49 rincewind [<ffffffff802b2a6f>] ? vfs_ioctl+0x2f/0xb0
May 12 20:50:49 rincewind [<ffffffff802b2d73>] ? do_vfs_ioctl+0x283/0x2f0
May 12 20:50:49 rincewind [<ffffffff803333b1>] ? __up_write+0x21/0x150
May 12 20:50:49 rincewind [<ffffffff802b2e81>] ? sys_ioctl+0xa1/0xb0
May 12 20:50:49 rincewind [<ffffffff8020c59a>] ? system_call_after_swapgs+0x8a/0x8f
May 12 20:50:49 rincewind
May 12 20:50:49 rincewind
May 12 20:50:49 rincewind Code: 00 00 00 00 f3 c3 66 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 48 c7 c2 01 00 00 00 65 48 8b 04 25 00 00 00 00 48 8b 80 48 06 00 00 <48> c7 80 48 02 00 00 ff ff ff ff 65 48 8b 04 25 00 00 00 00 81
May 12 20:50:49 rincewind RIP [<ffffffff885cc337>] :nvidia:os_set_mlock_capability+0x17/0x40
May 12 20:50:49 rincewind RSP <ffff8100a888de00>
May 12 20:50:49 rincewind CR2: 0000000000000248
May 12 20:50:49 rincewind ---[ end trace 4a3b1d118cb9ba8c ]---

Steps to reproduce:
Upgrade kernel packge to 2.6.25.3-1
Reboot
Login thru gdm
Wait...

Don't have better info at this point, unfortunetly
Closed by  Thomas Bächler (brain0)
Tuesday, 13 May 2008, 11:28 GMT
Reason for closing:  Fixed
Comment by dema (maschino) - Monday, 12 May 2008, 20:00 GMT
I have the same bug, but with the catalyst/fglrx driver from the repo. It's catalyst 8.4-1. The system boots normally but when it starts X, the whole system freezes. Here is the xorg log, I don't know which part of it is important so here is the log:

http://zeug.mtdev.de/dupload/Xorg.1.log
Comment by Pierre Schmitz (Pierre) - Monday, 12 May 2008, 20:29 GMT
Did you try the beta driver from nvidia? Afaik the 169.* driver is not meant to be used with kernel 2.6.25
Comment by Mårten Olsson (maos) - Monday, 12 May 2008, 20:49 GMT
No, I haven't done that. Didn't know of this limitation as all updating of kernel and nvidia was done thru pacman.
But good info...
Comment by Mårten Olsson (maos) - Monday, 12 May 2008, 21:32 GMT
Built "nvidia-beta" and "nvidia-utils-beta" from AUR (diver version 173.08) and during a quick test with old kernel showed that it seems to work ok but upgrade tpo new kernel crashes in same way as originaly reported.
Comment by figue (figue) - Tuesday, 13 May 2008, 06:30 GMT
I happen just as maschino, I had to put the driver to operate open ati
Comment by Thomas Bächler (brain0) - Tuesday, 13 May 2008, 07:31 GMT
Just a quick question, which was the last working kernel for you? Was it 2.6.25 or 2.6.24.X?
Comment by figue (figue) - Tuesday, 13 May 2008, 09:29 GMT
My last working kernel was 2.6.25 (I think 2.6.25.0)
Comment by Thomas Bächler (brain0) - Tuesday, 13 May 2008, 10:01 GMT
Okay, then this is the same as  FS#10403 
Comment by figue (figue) - Tuesday, 13 May 2008, 10:08 GMT
Okay, then this is the same as  FS#10403 

Yes ;)
Comment by Thomas Bächler (brain0) - Tuesday, 13 May 2008, 10:31 GMT
Okay, modules are going to testing right now. Can you guys update and test if nvidia/catalyst work again?
Comment by figue (figue) - Tuesday, 13 May 2008, 11:01 GMT
I have to rebuild catalyst and it works again. Thanks

Loading...