Hello,
I just installed opensuse 11.2 and I have random hard lock freezes (where I have to hold the power button down). I have tried several different Linux distros and they all freeze randomly (or so it seems) throughout different tasks. I have tried Sabayon, kubuntu, ubuntu, puppy, and opensuse (opensuse is what I want installed).
It freezes sometimes about 1 minute after bootup others up to 20-30 minutes. I have had it freeze while doing updates, connecting to the wifi, and adding in my music collection when I am using amarok. I orginally thought it was a problem accessing my ntfs drives but I do not think that is the case since I tested and didn't access them and it still froze.
I am using an ASUS N70SV laptop with a 2.66ghz duo core cpu, 4gb ram, nvidia 130M card. No effects are turned on other than default on these installs. Anyone have an ideas on things I can test?
Have you check your memory? Run the memory check from the installer disk. Run it over night or at least a couple of hours.
I will do that when I get home tonight, I have ran it about a week ago right after it first started freezing and it was fine (after 8 hours). Never hurts to be thorough though so I will report results after they have finished.
Edit: also I had ubuntu installed on this laptop right after I got it (June of 09) and it ran fine. I updated the bios to 206 because express gate had wireless off and this was the only fix. I never checked linux after the bios update however I have rolled back to 205 (original) and the problem remains.
An 8-hour memory test may not be enough. I always do a 24-hour test.
Is your system freezing, or are you having a kernel panic? The difference is
that the caps and numeric lock LEDs flash at a one Hz rate with the latter.
If it will fail when you are not doing anything, switch to the logging console
(ctrl+alt+F10) to see if anything gets logged when it fails. You must be viewing
this screen when it fails. You will have to write the info down by hand, or take
a picture of the screen.
I will try to do a 24 hour test, but I may not be able to let it go that long. I do not have an LED for caps and num lock on this laptop so I have no way of knowing if it is flashing, I will try the logging console and report back.
You could try plugging in an external keyboard to see if the lights flash.
On 02/13/2010 11:16 AM, darkbobby wrote:
>
> [image: http://img39.imageshack.us/img39/4079/img0154hpx.jpg]
>
> thats the screen on hard lock…
The lights won’t flash. Your eth0 device is stuck in some sort of
auto-negotiation loop. Unplugging the cable should allow it to proceed.
What is your Ethernet device? You can determine this with
hwinfo --network
it returns…
26: None 00.0: 10700 Loopback
[Created at net.124]
Unique ID: ZsBS.GQNx7L4uPNA
SysFS ID: /class/net/lo
Hardware Class: network interface
Model: "Loopback network interface"
Device File: lo
Link detected: yes
Config Status: cfg=new, avail=yes, need=no, active=unknown
27: None 00.0: 10701 Ethernet
[Created at net.124]
Unique ID: usDW.ndpeucax6V1
Parent ID: rBUF.CThQ1fwbBOC
SysFS ID: /class/net/eth0
SysFS Device Link: /devices/pci0000:00/0000:00:04.0
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "sis190"
Driver Modules: "sis190"
Device File: eth0
HW Address: 00:24:8c:95:41:fe
Link detected: no
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #8 (Ethernet controller)
28: None 00.0: 10780 Network Interface
[Created at net.124]
Unique ID: agy+.GSopYcFr9cF
Parent ID: y9sn.V_ktNTOK2k0
SysFS ID: /class/net/wmaster0
SysFS Device Link: /devices/pci0000:00/0000:00:06.0/0000:02:00.0
Hardware Class: network interface
Model: "Network Interface"
Driver: "ath9k"
Driver Modules: "ath9k"
Device File: wmaster0
HW Address: 00:22:43:8e:24:d0
Link detected: yes
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #14 (Network controller)
29: None 00.0: 1070a WLAN
[Created at net.124]
Unique ID: AYEt.QXn1l67RSa1
Parent ID: y9sn.V_ktNTOK2k0
SysFS ID: /class/net/wlan0
SysFS Device Link: /devices/pci0000:00/0000:00:06.0/0000:02:00.0
Hardware Class: network interface
Model: "WLAN network interface"
Driver: "ath9k"
Driver Modules: "ath9k"
Device File: wlan0
HW Address: 00:22:43:8e:24:d0
Link detected: yes
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #14 (Network controller)
30: None 00.0: 10701 Ethernet
[Created at net.124]
Unique ID: fLK9.ndpeucax6V1
SysFS ID: /class/net/pan0
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "bridge"
Device File: pan0
HW Address: 8e:c8:50:62:02:48
Link detected: yes
Config Status: cfg=new, avail=yes, need=no, active=unknown
on a side note i noticed that while it is booting up, it says something about network loopback then it lists “skipping… missing” any ideas?
On 02/15/2010 10:56 AM, darkbobby wrote:
>
>
> on a side note i noticed that while it is booting up, it says something
> about network loopback then it lists “skipping… missing” any ideas?
You should be able to see that message from either dmesg output or from
/var/log/boot.msg. It probably is not significant.
Your wired network card uses sis190 as its driver. Your wireless driver is
ath9k. What are you doing that you have a bridge setup? That is not normal.
Do you get the system hanging if the Ethernet cable is unplugged? When
unplugged, do you have a chance for a wireless connection?
i only use the wireless connection, i never have a ethernet cable plugged in. The bridge set itself up… i did nothing to do that. Is there a way to remove all that and just use the wireless?
On 02/15/2010 02:46 PM, darkbobby wrote:
>
> i only use the wireless connection, i never have a ethernet cable
> plugged in. The bridge set itself up… i did nothing to do that. Is
> there a way to remove all that and just use the wireless?
You can blacklist sis190. To do that edit (as root)
/etc/modprobe.d/50-blacklist.conf
and add the line “blacklist sis190” to the end of the file. As I’m not sure what
is causing the bridge, this may not remove it.
after blacklisting, It still freezes for no apparent reason, any other suggestions?
bump
is there anything else I can try? I really want to get this running so I can switch from win7 over completely
darkbobby <darkbobby@no-mx.forums.opensuse.org> writes:
Hi,
> bump
>
> is there anything else I can try? I really want to get this running so
> I can switch from win7 over completely
Maybe you mentioned this before, but I couldn’t find it.
Do you have any idea why/when it freezes?
I have two ideas, but I haven’t been following your entire thread, I
just scanned through the posts quickly:
Have you cleaned out the fan to make sure it isn’t due to overheating?
Have you tried using vesa graphics driver to ensure it isn’t that, that
is causing it?
–
Regards,
Barry Nichols
I have checked the fans after you mentioned looking, they are fine. I have not tried any other graphics other than default install and it freezes at random intervals. The image I linked on the first page shows the log. would you like me to do a new one now that i blacklisted the driver?
Hi,
I didn’t see that image before you mentioned it.
You could try disabling auto-negotiation, I don’t know about it, but a
brief search online returned this:
http://www.cyberciti.biz/faq/linux-change-the-speed-and-duplex-settings-of-an-ethernet-card/
It may be worth a try.
–
Regards,
Barry Nichols
