System constantly crashing suse11.3

hgallo · December 9, 2010, 4:47am

Hello all I’m having an issue my suse 11.3 just freezes out of no where several times during the day. this is the out put of /var/log/messages right before it freezes I have many of this:

Dec 8 21:48:03 linux-md1h kernel: 30.889715] [drm:drm_edid_is_valid] ERROR EDID checksum is invalid, remainder is 1
Dec 8 21:48:03 linux-md1h kernel: 30.889716] [drm:drm_edid_is_valid] ERROR Raw EDID:
Dec 8 21:48:03 linux-md1h kernel: 30.889718] <3>00 ff ff ff ff ff ff 00 40 12 21 00 01 01 01 00 …@.!..
Dec 8 21:48:03 linux-md1h kernel: 30.889719] <3>08 00 01 03 08 00 14 10 e8 60 41 a0 51 42 9c 25 …A.QB.% Dec 8 21:48:03 linux-md1h kernel: 30.889721] <3>0e 47 40 a5 ce 00 01 00 01 00 01 00 01 00 01 01 .G@............. Dec 8 21:48:03 linux-md1h kernel: 30.889722] <3>01 01 01 01 01 01 20 20 00 90 51 00 0a 00 00 00 ...... ..Q..... Dec 8 21:48:03 linux-md1h kernel: 30.889723] <3>02 00 08 00 10 00 00 1a 00 00 00 fd 00 32 00 16 .............2.. Dec 8 21:48:03 linux-md1h kernel: 30.889724] <3>00 00 00 00 20 20 00 20 20 20 00 00 00 fc 00 40 .... . .....@ Dec 8 21:48:03 linux-md1h kernel: 30.889726] <3>40 01 00 03 02 00 20 20 20 20 20 20 00 00 00 fc @..... .... Dec 8 21:48:03 linux-md1h kernel: 30.889727] <3>00 14 43 12 10 0c 00 08 00 00 00 20 20 00 00 79 ..C........ ..y Dec 8 21:48:03 linux-md1h kernel: 30.889728] Dec 8 21:48:03 linux-md1h kernel: 30.987688] [drm:drm_edid_is_valid] *ERROR* EDID checksum is invalid, remainder is 1 Dec 8 21:48:03 linux-md1h kernel: 30.987689] [drm:drm_edid_is_valid] *ERROR* Raw EDID: Dec 8 21:48:03 linux-md1h kernel: 30.987691] <3>00 ff ff ff ff ff ff 00 40 12 21 00 01 01 01 00 ........@.!..... Dec 8 21:48:03 linux-md1h kernel: 30.987692] <3>08 00 01 03 08 00 14 10 e8 60 41 a0 51 42 9c 25 .........A.QB.%
Dec 8 21:48:03 linux-md1h kernel: 30.987693] <3>0e 47 40 a5 ce 00 01 00 01 00 01 00 01 00 01 01 .G@…
Dec 8 21:48:03 linux-md1h kernel: 30.987695] <3>01 01 01 01 01 01 20 20 00 90 51 00 0a 00 00 00 … …Q…
Dec 8 21:48:03 linux-md1h kernel: 30.987696] <3>02 00 08 00 10 00 00 1a 00 00 00 fd 00 32 00 16 …2…
Dec 8 21:48:03 linux-md1h kernel: 30.987697] <3>00 00 00 00 20 20 00 20 20 20 00 00 00 fc 00 40 … . …@
Dec 8 21:48:03 linux-md1h kernel: 30.987699] <3>40 01 00 03 02 00 20 20 20 20 20 20 00 00 00 fc @… …
Dec 8 21:48:03 linux-md1h kernel: 30.987700] <3>00 14 43 12 10 0c 00 08 00 00 00 20 20 00 00 79 …C… …y
Dec 8 21:48:03 linux-md1h kernel: 30.987701]
Dec 8 21:48:03 linux-md1h kernel: 31.011998] e1000e 0000:00:19.0: irq 29 for MSI/MSI-X
Dec 8 21:48:03 linux-md1h kernel: 31.062459] e1000e 0000:00:19.0: irq 29 for MSI/MSI-X
Dec 8 21:48:03 linux-md1h kernel: 31.063057] ADDRCONF(NETDEV_UP): eth0: link is not ready
Dec 8 21:48:03 linux-md1h ifup-dhcp: eth0 Starting DHCP4 client
Dec 8 21:48:03 linux-md1h kernel: 31.085561] [drm:drm_edid_is_valid] ERROR EDID checksum is invalid, remainder is 1
Dec 8 21:48:03 linux-md1h kernel: 31.085562] [drm:drm_edid_is_valid] ERROR Raw EDID:

It happens more often when Im in XEN mode. Any ideas its getting very frustrating.

caf4926 · December 9, 2010, 5:52am

Google: ERROR* EDID checksum is invalid

Here is an Eg: [ubuntu] ERROR EDID checksum is invalid, remainder is 87 - Ubuntu Forums](http://ubuntuforums.org/showthread.php?t=1486066)

hgallo · December 9, 2010, 3:49pm

Thanks caf4926 based on the information on that link my issue isnt related to those dumps, I do have a 1024MB nVidia GeForce GT220 with dual head. maybe its not the right driver.
Now the question is what is causing my frezing, could it be possible that the system does not have time to log what happends ???

caf4926 · December 9, 2010, 5:01pm

You mention the XEN kernel
You need this for what exactly?

If you use kernel-desktop, is there an issue?
Have you tried any failsafe boot arguments:?

hgallo · December 10, 2010, 2:17am

Yes caf4926 I bought a new system with a powerfull enough processor and enough memory with the intentions of running xen virtual machines, unfortunateny so far it has been a total failure, cant get the network to work on them.
and yes if I use my kernel desktop it will also freze just not as fast as the xen. I haven’t tried any fail safe arguments since the computer works for a while and then it frezes I have no problem booting up. Is there any arguments you have in mind that maybe could help me find the root of the problem?

deano_ferrari · December 10, 2010, 2:52am

IMHO, it would be worthwhile booting up in failsafe mode, as at least it will help eliminate the graphics driver as a possible source of your problem.

LewsTherinTelemon · December 10, 2010, 3:36am

You might try adding the nomodeset kernel boot argument. And try safemode as the previous poster suggested.

Which Nvidia driver are you using? (Last I knew, the Nvidia binary driver didn’t work under Xen without modifying the driver or a kernel patch.)

As an alternative you could go with VirtualBox - though that has nothing to do with fixing your issue or course.

Cheers,
Lews Therin

caf4926 · December 10, 2010, 4:46am

Agreed
I assume ‘nomodeset’ is already in the default by virtue of your graphics. But x11-failsafe with all the other arguments in Failsafe- should give us a base to work from

hgallo · December 10, 2010, 6:29pm

To Deano Ferrari ,caf4926 and Lews Therin Telemon
The nomodeset didn’t help at all also, I Downloaded the latest driver from the nVidia website last night I haven’t had a chance to try it yet and Lews you are right it does not support the xen kernel, I will give Virtual Box a try.
Also on another note it seems that I am not the only one experiencing this issue, in fact there are a few people with the same exact problem e.g
freezing Opensuse 11.3 -kernel 2.6.34.4-0.1-default i686

caf4926 · December 10, 2010, 7:04pm

Virtual Box (Sun Version) Install HowTo

hgallo · December 11, 2010, 3:32am

OK Guys I have great news I went ahead and tested out the latest driver from nVidia and it seem to have worked I’ve been on the system for about two hours and no freezing yet or crazy dumps on my /var/log/messages

Just a note: after installing the driver I lost my Dual Head then I ran :

nvidia-xconfig –separate-x-screens

Restarted my x and I was back to Dual Screen. But guess what the mouse goes from one to the other but I cant drag windows across screens, also they each have their own menu bar. Isn’t that crazy…

Any way thanks to all… I hope this helps everybody els

caf4926 · December 11, 2010, 6:13am

Sounds like progress :-0

hgallo · December 20, 2010, 12:12am

I haven’t had any problems since the above so I’m posting a copy of my xorg.conf file plus a couple of steps I did to get it running.

xorg.conf file:

# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings:  version 260.19.21  (buildmeister@builder101)  Thu Nov  4 21:47:06 PDT 2010

Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 0 0
    Screen      1  "Screen1" RightOf "Screen0"
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
    Option         "Xinerama" "1"    #added this line to enable xinerama
EndSection

Section "Files"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"
    # HorizSync source: edid, VertRefresh source: edid
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "NUL 19''"
    HorizSync       24.0 - 80.0
    VertRefresh     50.0 - 75.0
    Option         "DPMS"
EndSection

Section "Monitor"
    # HorizSync source: builtin, VertRefresh source: builtin
    Identifier     "Monitor1"
    VendorName     "Unknown"
    ModelName      "CRT-1"
    HorizSync       28.0 - 55.0
    VertRefresh     43.0 - 72.0
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"		#added a 0 to device to differ devices
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce GT 220"
    BusID          "PCI:4:0:0"
    Screen          0
EndSection

Section "Device"
    Identifier     "Device1"		#added a 0 to device to differ devices
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce GT 220"
    BusID          "PCI:4:0:0"
    Screen          1
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "TwinView" "0"	#This was added by nvidia control center
    Option         "metamodes" "DFP: nvidia-auto-select +0+0"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen1"
    Device         "Device1"
    Monitor        "Monitor1"
    DefaultDepth    24
    Option         "TwinView" "0"	#This was added by nvidia control center
    Option         "metamodes" "CRT: nvidia-auto-select +0+0"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

note: please make a copy of this file before you make any changes to enable dual head.

After the changes open nvidia control center
under x server display configuration
press tab X Screen and if it says disabled just check the box to enable it
Also enable xinerama

	If you opened it as root you could press save to x configuration file which is located in 
	/etc/X11/xorg.conf

If you ran it as a non root it gives you the option of preview it, just copy and paste into a new file
any where in your system name it xorg.conf and then just drop it in /etc/X11/xorg
restart your x server and you should be ok.