On Monday 07 May 2007 22:04, M Harris wrote:

        I can hardly believe that this is an xorg problem... no way. You have a memory or HD issue there... I suspect. Back up your home dir and then reload suse 10.

Does it still have same issue? -- Kind regards, M Harris <>< -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 5/7/07, M Harris wrote:

On Monday 07 May 2007 21:25, Sunny wrote:

...

After the latest xorg updates my 10.0 x86_64 machine started to freeze after an hour or so work. I have tested the memory and other components, and everything looks OK. If I leave the machine in runlevel 3, it does not freeze. Does the machine lock? --tight loop --?

When it "freezes" can you ctl-alt-F1 and get to a console?

When if freezes can you ping it? can you ssh to it?

I can hardly believe that this is an xorg problem... no way. You have a memory or HD issue there... I suspect.

Hardlock - no console, no net, no ssh, nothing. Completely dead. Memory tested for 24 hours with memtest - OK. HDDs tested with their manufacturers diagnostic tools (full test) - OK. After the problems started, I updated the nvidia driver, no change. And ... it happens only in init 5, it does not happen in init 3. And I made it to reencode a couple of movies in init 3, so i have something to keep it busy. A reload of the OS is not so very good option. If I go there I'd better upgrade the OS, and I do not want it for now. -- Svetoslav Milenov (Sunny) Even the most advanced equipment in the hands of the ignorant is just a pile of scrap. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 5/8/07, Luciano Mannucci wrote:

On Tue, 8 May 2007 07:27:06 -0500 Sunny wrote:

...

After the problems started, I updated the nvidia driver, no change.

And ... it happens only in init 5, it does not happen in init 3. And I made it to reencode a couple of movies in init 3, so i have something to keep it busy. Are your fan coolers ok? (CPU and nvidia chip)

luciano.

I'm running gkrelm, when it freezes, the temperature shown for the cpu and gpu are ok, same as when it works. One other finding: If I log in runlevel 5, i.e. kde running, etc., but I switch to terminal console (ctrl-alt-F1) and leave the machine that way, it does not freeze. If I leave it in a graphical mode, it freezes. So, now maybe Matthias suggestion starts to make sense a little bit. The problem is that all this started after the xorg upgrade a week or 2 ago. It does not exclude the videocard going south just at the same time. I'll look for a replacement card, just to see if this is going to solve the problem. At least that way we'll know if this is software or hardware problem. Thanks for all the suggestions. -- Svetoslav Milenov (Sunny) Even the most advanced equipment in the hands of the ignorant is just a pile of scrap. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

* Sunny [05-08-07 11:32]: [...]

I'm running gkrelm, when it freezes, the temperature shown for the cpu and gpu are ok, same as when it works.

One other finding: If I log in runlevel 5, i.e. kde running, etc., but I switch to terminal console (ctrl-alt-F1) and leave the machine that way, it does not freeze. If I leave it in a graphical mode, it freezes.

So, now maybe Matthias suggestion starts to make sense a little bit. The problem is that all this started after the xorg upgrade a week or 2 ago. It does not exclude the videocard going south just at the same time. I'll look for a replacement card, just to see if this is going to solve the problem. At least that way we'll know if this is software or hardware problem.

Before swaping hardware, you might try a live-boot cd/dvd such as Knoppix and see if you still get the freeze. Might give you a better basis to determine hardware vs software failure. -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 OpenSUSE Linux http://en.opensuse.org/ Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

* Sunny [05-08-07 16:16]: [...]

I was thinking about this, but live distro will not use the proprietary nvidia drivers, which will not help me to investigate if this is a software or hardware problem, or both.

this is good as it would indicate that the nvidia drivers were causing you a problem.

Maybe I'll go first with downgrading xorg, then with replacing the hardware.

Just that the quick boot of a live-.... would give a quick indication. -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 OpenSUSE Linux http://en.opensuse.org/ Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Tuesday 08 May 2007 07:27, Sunny wrote:

Hardlock - no console, no net, no ssh, nothing. Completely dead. Memory tested for 24 hours with memtest - OK. HDDs tested with their manufacturers diagnostic tools (full test) - OK.

After the problems started, I updated the nvidia driver, no change.

And ... it happens only in init 5, it does not happen in init 3. And I made it to reencode a couple of movies in init 3, so i have something to keep it busy. I have a couple of ideas for you, and some comment...

... first, almost all intermittent problems are hardware--- like 99.9% of them. At this point I would be suspecting the video card--- memory or chip. The nvidia geforce chips are famous for crapping out... because they are usually surface mounted, and when they get hot they break free from their mounting. (one possibility) The other possibility is that there is a memory problem on the card... can cause the same kinds of flaky lock-ups that memory problems cause on the bus. Bottom line, try another card. The other thing you might want to look at is your xorg.conf file. I have been experimenting with my ATI setup and have been able to force my system to "lock" (and I do mean locked... kernel is dead not even a panic), by changing some of the settings (mouse, monitor, device) in xorg.conf. This is a disturbing revelation for me... because in the unix environment *nothing* should be able to bring the system down --- especially X... thats sounding like Windoze. In other words, there may be problems with X and the server may not be stable, or may not start, or my lock... but the system should *never* go down because of it... so some serious breaches are occurring somewhere (something is rotten in Denmark!). Obviously the the xserver code is too closely linked to the hardware/kernel lately. Unrelated to your problem... at the moment my ATI machine has two(2) copies of X running ... only after updating xorg and installing the ATI fglrx driver for 3D support?? Well, it may be normal... but I can't prove it. It probably is a problem... but I'm not finding much to help me figure it out. Isn't X fun these days? -- Kind regards, M Harris <>< -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org