View Single Post
Old 10-16-06, 02:09 PM   #18
Hannibal
#356906
 
Hannibal's Avatar
 
Join Date: Feb 2004
Location: Lodz, Poland
Posts: 24
Default Re: geforce 6600 random system lock

I try to invastigate what is a problem, but I was unsucessful. But maybe my tries help someone...

I've add some printk to handle_IRQ_event function in kernel/irq/handle.c file.
It prits data something like that:
Code:
Oct 16 19:06:30 hannibal kernel: DATA: dff23448 2 dff234ec 1 2 2
Oct 16 19:06:30 hannibal kernel: DATA: 31687465 0 0 0 0 c0441048
Oct 16 19:06:30 hannibal kernel: DATA: e104c000 e19bb640 1 1 1 f210de
Oct 16 19:06:30 hannibal kernel:     SUBDATA1 d9b48000
Oct 16 19:06:30 hannibal kernel:     SUBDATA2 e104c000
Oct 16 19:06:30 hannibal kernel: IRQ: 16 - Device: e19bb640 Handler:  nv_kern_isr+0x0/0x72 [nvidia]
Oct 16 19:06:30 hannibal kernel: DATA: dff23448 2 dff234ec 1 2 2
Oct 16 19:06:30 hannibal kernel: DATA: 31687465 0 0 0 0 c0441048
Oct 16 19:06:30 hannibal kernel: DATA: e104c000 e19bb640 1 1 1 f210de
Oct 16 19:06:30 hannibal kernel:     SUBDATA1 d9b48000
Oct 16 19:06:30 hannibal kernel:     SUBDATA2 e104c000
Oct 16 19:06:30 hannibal kernel: IRQ: 16 - Device: e19bb640 Handler:  nv_kern_isr+0x0/0x72 [nvidia]
Oct 16 19:06:30 hannibal kernel: DATA: dff23448 2 dff234ec 1 2 2
Oct 16 19:06:30 hannibal kernel: DATA: 31687465 0 0 0 0 c0441048
Oct 16 19:06:30 hannibal kernel: DATA: e104c000 e19bb640 1 1 1 f210de
Oct 16 19:06:30 hannibal kernel:     SUBDATA1 d9b48000
Oct 16 19:06:30 hannibal kernel:     SUBDATA2 e104c000
Oct 16 19:06:30 hannibal kernel: IRQ: 16 - Device: e19bb640 Handler:  nv_kern_isr+0x0/0x72 [nvidia]
DATA means action->handle and first 5 dwords from action->dev_id
SUBDATAX id data from NVIDIA board (2 first dwords used as pointers )
Last line tells which handler takes interrupt.

From time to time appear this log:
Code:
Oct 16 19:06:30 hannibal kernel: DATA:  2 dff234ec 1 2 2
Oct 16 19:06:30 hannibal kernel: DATA: 31687465 0 0 0 0 c0441048
Oct 16 19:06:30 hannibal kernel: DATA: e104c000 e19bb640 1 1 1 f210de
Oct 16 19:06:30 hannibal kernel:     SUBDATA1 d9b48000
Oct 16 19:06:30 hannibal kernel:     SUBDATA2 e104c000
Oct 16 19:06:30 hannibal kernel: IRQ: 16 - Device: 00000000 Handler: NULL
I think this is not detected properly nvidia interrupt. Almost for sure this aren't USB (0xdff23448) and Realtek (0x31687465) ints. Because the not run at that moment (and I have lockups even when I disable usb in BIOS and remove realtek).

For sure this NULL apperar when I swich from X to console. Second time this appear is just before lockup. Then apperar losts of this NULLS and also somethin like that:
Code:
Oct 16 19:06:34 hannibal kernel: DATA: e104c000 e31687465 0 0 0 0 c0441048
Oct 16 19:06:34 hannibal kernel: DATA: e104c000 31687465 0 0 0 0 c0441048
Oct 16 19:06:34 hannibal kernel: DATA: e104c000 e131687465 0 0 0 0 c0441048
Oct 16 19:06:34 hannibal kernel: DATA: e104c000 e19b31687465 0 0 0 0 c0441048
Oct 16 19:06:34 hannibal kernel: DATA: e104c000 e131687465 0 0 0 0 c0441048
Oct 16 19:06:34 hannibal kernel: DATA: e104c000 e1931687465 0 0 0 0 c0441048
Oct 16 19:06:34 hannibal last message repeated 2 times
Oct 16 19:06:34 hannibal kernel: DA31687465 0 0 0 0 c0441048
Oct 16 19:06:34 hannibal kernel: DATA: e104c000 31687465 0 0 0 0 c0441048
Oct 16 19:06:34 hannibal kernel: DATA: e104c000 e31687465 0 0 0 0 c0441048
Oct 16 19:06:34 hannibal kernel: DATA: e104c000 e1931687465 0 0 0 0 c0441048
Oct 16 19:06:34 hannibal kernel: DATA: e104c000 e131687465 0 0 0 0 c0441048
Oct 16 19:06:34 hannibal kernel: DATA: e1031687465 0 0 0 0 31687465 0 0 0 0 c0441048
Oct 16 19:06:34 hannibal kernel: DATA: e104c000 31687465 0 0 0 0 c0441048
Oct 16 19:06:34 hannibal kernel: DATA: e104c000 e31687465 0 0 0 0 c0441048
Oct 16 19:06:34 hannibal kernel: DATA: e104c000 e19b31687465 0 0 0 0 c0441048
Oct 16 19:06:34 hannibal kernel: DATA: e104c000 e131687465 0 0 0 0 c0441048
Oct 16 19:06:34 hannibal kernel: DATA: e104c000 e19b31687465 0 0 0 0 c0441048
Oct 16 19:06:34 hannibal kernel: DATA: e104c000 e19bb31687465 0 0 0 0 c0441048
Oct 16 19:06:34 hannibal kernel: DATA: e104c031687465 0 0 0 0 c0441048
Oct 16 19:06:34 hannibal kernel: DATA: e104c00031687465 0 0 0 0 c0441048
Oct 16 19:06:34 hannibal kernel: DATA: e104c000 e31687465 0 0 0 0 c0441048
Oct 16 19:06:34 hannibal last message repeated 2 times
Oct 16 19:06:34 hannibal kernel: DATA: e104c000 31687465 0 0 0 0 c0441048
It looks like so many interrupts are commning, that printk doesn't have enough time to print whole message. This ints are probably those NULLS because 9900 unahandled ints is requied to disable IRQ, but not all are listed explictly in log.

Code that detect nv interrupt will probably help, but unfortunatlyin this is in binary part...

I hope it was understandable and helpful ;-)
__________________
Hannibal@Slackware-current
Hannibal is offline   Reply With Quote