Skip to contentSkip to conversation

Probable PCIE prob

DISCUSSION Syren Baran 3 participants 6 messages Apr 28, 2007 – May 9, 2007

lore
Share & tools
lore
#0 lore raw

Hi,

i got a problem with the combination of an Asrock AM2NF4G-SATA2 mainboard with a Radeon X1900 (chip 1002,724b) graphics card. /i386/pci/mmconfig.c reports a buggy bios (e0000000 is not E820-reserved). System crashes only happen when viewing films (neither xine nor mplayer run with root privileges) and independent of video drivers (framebuffer, vesa and fglrx). Logs dont show any anomalies before crashing. Anybody got a clue?

Thanks,
Syren

#1 lore raw
Quoted 4 lines · Syren Baran

i got a problem with the combination of an Asrock AM2NF4G-SATA2 mainboard with a Radeon X1900 (chip 1002,724b) graphics card. /i386/pci/mmconfig.c reports a buggy bios (e0000000 is not E820-reserved).

This message is harmless and likely unrelated.

System crashes only happen when viewing films (neither

Quoted 3 lines

xine nor mplayer run with root privileges) and independent of video drivers (framebuffer, vesa and fglrx). Logs dont show any anomalies before crashing. Anybody got a clue?

Sounds like some sort of hardware problem. Maybe the power supply is not up to the task? Or the board could be broken. Also always worth updating the BIOS.

-Andi

#2 lore raw

Am Sonntag, den 29.04.2007, 13:54 +0200 schrieb Andi Kleen:

Quoted 8 lines
Quoted 4 lines · Syren Baran

i got a problem with the combination of an Asrock AM2NF4G-SATA2 mainboard with a Radeon X1900 (chip 1002,724b) graphics card. /i386/pci/mmconfig.c reports a buggy bios (e0000000 is not E820-reserved).

This message is harmless and likely unrelated.

Maybe, but thats the only clue i can get from the kernel.

Quoted 8 lines

System crashes only happen when viewing films (neither

Quoted 3 lines

xine nor mplayer run with root privileges) and independent of video drivers (framebuffer, vesa and fglrx). Logs dont show any anomalies before crashing. Anybody got a clue?

Sounds like some sort of hardware problem. Maybe the power supply is not up to the task?

Definatly not, already replaced that with a 550W power supply.

Quoted 1 line

Or the board could be broken.

Most likely not. I recently actually installed Windows XP to check. Granted, just watching one film may not have been long enough to trigger this effect (the crashes usually take place after 1/2 an hour, though times can vary largely).

Quoted 2 lines

Also always
worth updating the BIOS.

Did that long before posting. Changing the PCIE frequency in the BIOS didnt help either.

Quoted 2 lines

-Andi

Syren

#3 lore raw
In reply to Syren Baran
Quoted 9 lines · On Saturday 28 April 2007 20:53:37 Syren Baran wrote:

Hi,

i got a problem with the combination of an Asrock AM2NF4G-SATA2 mainboard with a Radeon X1900 (chip 1002,724b) graphics card. /i386/pci/mmconfig.c reports a buggy bios (e0000000 is not E820-reserved). System crashes only happen when viewing films (neither xine nor mplayer run with root privileges) and independent of video drivers (framebuffer, vesa and fglrx). Logs dont show any anomalies before crashing. Anybody got a clue?

This is a pretty bizarre crash. It might be a hardware problem. Try running a load intensive task, something that heats your CPU up, for a long period. See if it lasts longer than 30 minutes..

Another thing you could try doing was eliminating X completely, by using mplayer on a vesafb console..

Signature · 5 lines
Cheers,
Alistair.

Final year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.
#4 lore raw

Am Sonntag, den 29.04.2007, 15:21 +0100 schrieb Alistair John Strachan:

Quoted 9 lines · On Saturday 28 April 2007 20:53:37 Syren Baran wrote:
Quoted 4 lines

System crashes only happen when viewing films (neither xine nor mplayer run with root privileges) and independent of video drivers (framebuffer, vesa and fglrx). Logs dont show any anomalies before crashing. Anybody got a clue?

This is a pretty bizarre crash. It might be a hardware problem. Try running a load intensive task, something that heats your CPU up, for a long period. See if it lasts longer than 30 minutes..

Think were getting in the right direction. Running "mencoder -ovc lavc -oac lavc -of mpeg -o /dev/null somefilm" causes crashes consistantly after a couple of minutes (using different kernels, some problem on XP). Exchanging the CPU with an identical chip (Sempron 2800+, family 15, model 79) caused the same behavior. On the other hand a highly sophisticated, quick test for several hours (4-12, probably closer to
12) produced this crash:

EFLAGS: 00010093 (2.6.20-1.2944-fc6 #1)
EIP is at dump_trace+0x5c/0x93
eax: 75715ffd ebx: 75715f65 ecx: 0178d206 edx: 01236180
esi: 5f6f626f edi: 75715000 ebp: c06a645e esp: dead4d95
ds: 007b es: 007b ss:0068
Process a.out (pid 3499, ti=dead4000, task=eb64cbb0, task.ti=ea872000)

Stack: c06a645e c06a645e 00000018 00000000 c06a645e c0405001 c06fdc40
c06a645e
dead4f38 c04050b0 c06a645e c06a645e dead4e9d dead4ed5 00000002 00010046
dead4e9d dead4ed5 c0405246 c06a645e 00000010 eb64cd44 00000dab dead4000
Call Trace:
[<c0405001>] show_trace_log_lvl+0x18/0x2c
[<c04050b0>] show_trace_log_lvl+0x9b/0xa3
[<c0405246>] show_registers+018e/0x25d
[<c0621fcf>] notifier_call_chain+0x19/0x29
[<c0405443>] die+0x12e/0x240
[<c0621ee3>] do_page_fault+0x407/0x4da
[<c0621adc>] do_page_fault+0x0/0x4da
[<c0620744>] error_code+0x7c/0x84
BUG: unable to handle kernel paging request at virtual address 75715f65

printing eip:
c0404fb2
*pde=00000000
Recursive die() failure, output suppressed <O>Kernel panic-not syncing: Fatal exception in interrupt

This is probable due to overheating (didnt have any thermal paste when swapping the CPU´s). After waking up after 12 hours and noting the error the CPU was still at 82 degrees celsius.
Unlike the crashes from mencoder, cpu temperatur below 40 degrees. The only meaningfull error i could get when running mencoder (sometimes system freezes, sometimes reboots, once got this message+freeze) "double fault, gdt at c17c8000".

Quoted 2 lines

Another thing you could try doing was eliminating X completely, by using mplayer on a vesafb console..

Did the above tests in runlevel 3, thus eliminating X as a possible cause. Also removed the gfx card to exclude electromagnetical interference (onboard nv4 is sufficient).
Doesnt seem like a kernel bug, but (usermode-) mencoder causing a crash on different kernels and OS´s is wierd.

Quoted 1 line

Syren

PS: the source code for the sophisticated a.out

int main(char *argv[], int argc){
        int i;
        while (1){
                i++;
        }
} 
#5 lore raw

Resolved (was: Re: Probable PCIE prob)

In reply to Alistair John Strachan

Am Sonntag, den 29.04.2007, 15:21 +0100 schrieb Alistair John Strachan:

Quoted 11 lines
Quoted 7 lines

i got a problem with the combination of an Asrock AM2NF4G-SATA2 mainboard with a Radeon X1900 (chip 1002,724b) graphics card. /i386/pci/mmconfig.c reports a buggy bios (e0000000 is not E820-reserved). System crashes only happen when viewing films (neither xine nor mplayer run with root privileges) and independent of video drivers (framebuffer, vesa and fglrx). Logs dont show any anomalies before crashing. Anybody got a clue?

This is a pretty bizarre crash. It might be a hardware problem. Try running a load intensive task, something that heats your CPU up, for a long period. See if it lasts longer than 30 minutes..

It turned out this problem only occors when the DDR2 modules (of the mainboard) run in dual channel mode (two different modules, identical specs). Weird and annoying, but no softwareproblem.

Syren