Seemingly random crashes on a new desktop running 11.3

English Install/Boot/Login
#1

Hi,

I got a new desktop and figured this would be a great oppurtunity to update to 11.3 (from 11.2) while migrating files… However I have had lots of problems with it, right of the bat.

My first installation got messed up right after it was done, so I had to redo everything. Now the system boots up all fine but I am experiencing crashes every once in a while. By crashes I mean nothing works; the system monitor graphs freeze, the clock freezes, system doesnt respond to key strokes. The only remedy is then to “force an unexpected reboot” (ref: IT Crowd). I have a feeling that it has to do with Yast or something related to Yast, as it is the only common denominator between the crashes so far. However the system doesnt crash everytime I start Yast so I cant really say anything conclusively…

I have also realised that when I attach a secondary screen the graphics get kinda screwed as well… if that makes any sense…

Here are my system details:
Dell Vostro Desktop with Core i7 64bit processor
8 x 2.8Ghz
6gig ram
graphics card: GeForce GT220

What could be the problem here? btw let me know if anyone wants to see logs from /var/log/messages

Cheers,

#2

First thing I’d like to know is whether you installed the NVIDIA driver. If not, SDB:Configuring graphics cards - openSUSE

#3

Well, I have double checked and I am currently running the nouveau driver, which was set after the installation; I didnt do anything particular after that… Does it need to be configured thoroughly? (I checked the link and the following links but it appears as the problems refered to there are more severe than what I have here, I mean after all the graphics work fine most of the time… )

Upon installing openSUSE, the X system’s automatic configuration may have failed to properly configure the graphics correctly. Typically this results in either a black screen upon reboot, or the wrong resolution being displayed on the monitor.

#4

I cant seem to find “edit” option so i’m gonna have to go with a second post on this one.

The same crash just happened, very annoying… I can say that I had nothing to do with Yast this time. Pretty much only browsing, mails and spotify… Anyhow here’s the relevant lines from /var/logs/messages:

Sep  9 15:25:45 office2 kernel:  8861.884299] [drm] nouveau 0000:01:00.0: Allocating FIFO number 4
Sep  9 15:25:45 office2 kernel:  8861.897753] [drm] nouveau 0000:01:00.0: nouveau_channel_alloc: initialised FIFO 4
Sep  9 15:25:45 office2 kernel:  8861.899555] [drm] nouveau 0000:01:00.0: nouveau_channel_free: freeing fifo 4
Sep  9 15:25:45 office2 kernel:  8861.942870] [drm] nouveau 0000:01:00.0: Allocating FIFO number 4
Sep  9 15:25:45 office2 kernel:  8861.956393] [drm] nouveau 0000:01:00.0: nouveau_channel_alloc: initialised FIFO 4
Sep  9 15:25:45 office2 kernel:  8861.958287] [drm] nouveau 0000:01:00.0: nouveau_channel_free: freeing fifo 4
Sep  9 15:27:03 office2 dhclient: XMT: Solicit on eth1, interval 126430ms.
Sep  9 15:28:19 office2 dhcpcd[2861]: eth1: renewing lease of 130.235.250.175
Sep  9 15:28:19 office2 dhcpcd[2861]: eth1: leased 130.235.250.175 for 3600 seconds
Sep  9 15:28:19 office2 dhcpcd[2861]: eth1: adding IP address 130.235.250.175/25
Sep  9 15:28:19 office2 dhcpcd[2861]: eth1: adding default route via 130.235.250.134 metric 0
Sep  9 15:28:19 office2 dhcpcd[2861]: eth1: setting hostname to `office2'
Sep  9 15:28:19 office2 ifup:     eth1      device: Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE] (rev 54)
Sep  9 15:28:26 office2 smartd[4665]: Device: /dev/sda [SAT], SMART Usage Attribute: 195 Hardware_ECC_Recovered changed from 35 to 34
Sep  9 15:29:09 office2 dhclient: XMT: Solicit on eth1, interval 111530ms.
Sep  9 15:31:01 office2 dhclient: XMT: Solicit on eth1, interval 129910ms.
Sep  9 15:33:11 office2 dhclient: XMT: Solicit on eth1, interval 117520ms.
Sep  9 15:35:08 office2 dhclient: XMT: Solicit on eth1, interval 128470ms.
Sep  9 15:37:17 office2 dhclient: XMT: Solicit on eth1, interval 111880ms.
Sep  9 15:39:09 office2 dhclient: XMT: Solicit on eth1, interval 119340ms.
Sep  9 15:41:08 office2 dhclient: XMT: Solicit on eth1, interval 121110ms.
Sep  9 15:43:09 office2 dhclient: XMT: Solicit on eth1, interval 123230ms.
Sep  9 15:45:11 office2 unix2_chkpwd: gkr-pam: the password for the login keyring was invalid.
Sep  9 15:45:13 office2 dhclient: XMT: Solicit on eth1, interval 114600ms.
Sep  9 15:47:07 office2 dhclient: XMT: Solicit on eth1, interval 125710ms.
Sep  9 15:49:13 office2 dhclient: XMT: Solicit on eth1, interval 118550ms.
Sep  9 15:51:12 office2 dhclient: XMT: Solicit on eth1, interval 113140ms.
Sep  9 15:53:05 office2 dhclient: XMT: Solicit on eth1, interval 117020ms.
Sep  9 15:55:02 office2 dhclient: XMT: Solicit on eth1, interval 125630ms.
Sep  9 15:57:08 office2 dhclient: XMT: Solicit on eth1, interval 128400ms.
Sep  9 15:58:05 office2 kernel: [10798.143783] SysRq : HELP : loglevel(0-9) reBoot Crash terminate-all-tasks(E) memory-full-oom-kill(F) kill-all-tasks(I) thaw-filesystems(J) saK show-backtrace-all-active-cpus(L) show-memory-usage(M) nice-all-RT-tasks(N) powerOff show-registers(P) show-all-timers(Q) unRaw Sync show-task-states(T) Unmount force-fb(V) show-blocked-tasks(W) dump-ftrace-buffer(Z)

When I realised that the system was frozen, the clock was showing 15:55 so I presume the last entry there is my force reboot, as the next entries are abour renewing lease on the dhcpcd command…

It feels as there’s something wrong with the network but I am not qualified enough to make an educated guess on what or why…

#5

Please try the proprietary nvidia driver as outlined above there are problems with nouveau.

#6

I have now installed the nvidia driver and double checked that it’s in use. So, for now it’s just about waiting to see if the problem happens again? or am I missing something?