View Single Post
Old 11-19-06, 07:50 PM   #4
Tub
Registered User
 
Join Date: Nov 2006
Posts: 95
Default Re: system crashes when upgrading from 6600GT to 7600GT

@netllama:

thanks for the hint with netconsole. Although netcat -u -l -p 6666 didn't capture the messages, wireshark did. After re-assembling, here it is:
Quote:
Unable to handle kernel paging request at ffff81043b952454 RIP:
[<ffffffff8821c887>] :nvidia:_nv006647rm+0x35f/0x45a
PGD 8063 PUD 0
Oops: 0000 [1]
CPU 0
Modules linked in: netconsole nvidia
Pid: 14672, comm: ut2004-bin Tainted: P 2.6.18-gentoo-r2 #4
RIP: 0010:[<ffffffff8821c887>] [<ffffffff8821c887>] :nvidia:_nv006647rm+0x35f/0x45a
RSP: 0000:ffffffff80616be0 EFLAGS: 00010296
RAX: 00000000ffffffff RBX: ffff81003b952000 RCX: ffff81003b952450
RDX: 00000000ffffffff RSI: 0000000000000000 RDI: 0000000000000001
RBP: 0000000000000001 R08: 0000000000000001 R09: 0000000000000030
R10: 0000000000000020 R11: 0000000000000000 R12: 0000000000000006
R13: 0000000000000030 R14: ffff8100309f0000 R15: ffff8100309f0000
FS: 00002b2f6bc9dfd0(0000) GS:ffffffff80654000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: ffff81043b952454 CR3: 0000000039b64000 CR4: 00000000000006e0
Process ut2004-bin (pid: 14672, threadinfo ffff810029e7a000, task ffff81002f26cb20)
Stack: ffffffff80616c50 ffff81003b952000 ffff8100309f0000 0000000000000001
0000000000000030 ffffffff8821bf69 ffff81003ae34bc0 ffffffff80616cd0
ffff81003ae34ac0 0000000000000002 ffff81003ae34000 ffffffff8823f06b
Call Trace:
<IRQ> [<ffffffff8821bf69>] :nvidia:_nv006662rm+0x9d/0xf2
[<ffffffff8823f06b>] :nvidia:_nv001020rm+0xf7/0x184
[<ffffffff8823eec5>] :nvidia:_nv001019rm+0x139/0x1e8
[<ffffffff88238e05>] :nvidia:_nv001149rm+0x4f/0xbc
[<ffffffff8823b27e>] :nvidia:_nv001104rm+0x108/0x2bc
[<ffffffff8823b606>] :nvidia:_nv001215rm+0x3e/0x7e
[<ffffffff8823980a>] :nvidia:_nv001225rm+0x3e/0x52
[<ffffffff88247ea6>] :nvidia:_nv001005rm+0x8e/0xf6
[<ffffffff88248031>] :nvidia:_nv000966rm+0x2d/0x7c
[<ffffffff881eaa62>] :nvidia:_nv003692rm+0x112/0x4fa
[<ffffffff881e132f>] :nvidia:_nv003702rm+0x8b/0xd2
[<ffffffff8802de3c>] :nvidia:_nv001806rm+0x92/0xae
[<ffffffff8803233f>] :nvidia:rm_isr_bh+0x53/0x56
[<ffffffff88279e3f>] :nvidia:nv_kern_isr_bh+0x16/0x18
[<ffffffff8022dd36>] tasklet_action+0x46/0x80
[<ffffffff8022dfff>] __do_softirq+0x4f/0xb0
[<ffffffff8020a7fc>] call_softirq+0x1c/0x30
[<ffffffff8020c22c>] do_softirq+0x2c/0x90
[<ffffffff8020c1e2>] do_IRQ+0x72/0x90
[<ffffffff80209f59>] ret_from_intr+0x0/0xa
<EOI>

Code: 83 7c 81 08 00 75 04 ff ca eb f3 83 fa ff b8 00 00 00 00 0f
RIP [<ffffffff8821c887>] :nvidia:_nv006647rm+0x35f/0x45a
RSP <ffffffff80616be0>
CR2: ffff81043b952454
<0>Kernel panic - not syncing: Aiee, killing interrupt handler!
can you narrow down the problem from that?

I will now try a bios upgrade.

edit: performed the bios upgrade from 1001 to 1014, it didn't help. ut2k4 crashed again with a very similar message. the pid and some adresses were different, but the general message and the call trace were identical.


@whig: no, I don't think it's heat related. It doesn't just crash after x minutes of 3d-action. There are visible patterns when it crashes and when it doesn't, and they don't depend on the time I played. For example, I can usually play ut2k4 for 20 minutes without problems (usually, not always), but there's a high chance it'll freeze during the next map change.

Last edited by Tub; 11-19-06 at 08:40 PM.
Tub is offline   Reply With Quote