Hi, I have problem with my OS, sometimes it hangs during boot (after I pick suse, I share it with windows, in systems table it shows the loading bar and stops,i can’t switch to tty, alt+sys rq doesn’t work too, and i have to push the restard button). I have this problem for a long time but todays 10 times restarting pissed me off. So I’ asking for some help. cat /etc/SuSE=release
openSUSE 11.3 (x86_64)
VERSION = 11.3 uname -r
2.6.34-12-desktop
Hardware:
ASRock P43DE
VGA compatible controller: ATI Technologies Inc RV770 [Radeon HD 4850]
Intel E5200
I’ve already done -> "you can run yast in text mode with root permissions if X window not available) and navigate to yast > System > /etc/sysconfig Editor > System > Kernel > NO_KMS_IN_INITRD and change it to “yes”. This takes a minute or two to save once changed is submitted. "
Distribution tried, where the same problem appeared : Ubuntu 5,7; Fedora 13, Knoppix 5, OpenSUSE 11.3 32bit
I think that this is hardware problem (because in Debian,Novell,Red Hat branch the same error occured) but i don’t know how to check what’s wrong. I’ve also tried to search some info in /var/log/messages but there’re error’s like:
mcelog: failed to prefill DIMM database from DMI data
mcelog: HARDWARE ERROR. This is NOT a software problem!
SuSEfirewall2: Warning: no default firewall zone defined, assuming ‘ext’
gdm-simple-greeter[3106]: WARNING: Failed to send buffer
WARNING: could not read /etc/xdg/autostart/ksmolt-autostart.desktop
So can someone tell me where i can find information what stops system ?
On 2011-02-28 14:06, cavetroll wrote:
> Hi, I have problem with my OS, sometimes it hangs during boot (after I
> pick suse, I share it with windows, in systems table it shows the
> loading bar and stops,
Change to verbose booting mode.
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
any chance of you finding a deterministic pattern instead of ‘sometimes’ ?
I know of PCs with hardware which will NOT reboot from Windows to Linux, and one must 1st switch off the PC. Unplug the PC electrical cable from the wall, and then plug the PC cable back in to the wall and then switch ON the PC and boot to Linux. But going from Linux to Windows does not have the problems.
So if you could find a pattern to this ‘sometimes’ it might help you a bit in determining the problem.
Usually it stops while ‘loading modules’,but still it doesn’t tell me what should be fixed.
That’s the problem it happens ‘sometimes’, once it boots up normally and the other I have to restart it twice or more. There’s no schedule or regular frequency.
When it fails to start, you could boot from a liveCD, and take a look at the /var/log/messages and boot.log on the hard drive (from the failed boot) and see if it offers any hints.
mcelog says: HARDWARE ERROR. This is NOT a software problem!
I suggest you install and run memtest, at least for 24 hours. It should report no errors at all, if it does report errors, test the RAM modules one by one, to find out which is broken.
On 2011-02-28 21:36, cavetroll wrote:
>
> robin_listas;2296403 Wrote:
>>
>> Change to verbose booting mode.
>>
> Usually it stops while ‘loading modules’,but still it doesn’t tell me
> what should be fixed.
Always there?
> oldcpu;2296424 Wrote:
>> any chance of you finding a deterministic pattern instead of ‘sometimes’
>> ?
> That’s the problem it happens ‘sometimes’, once it boots up normally
> and the other I have to restart it twice or more. There’s no schedule or
> regular frequency.
I’m starting to suspect disk problems. Test them, using smartctl (long
test) or the manufacturer test disk. Test memory too.
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
Am 2011-02-28 23:36, schrieb Knurpht:
>
> mcelog says: HARDWARE ERROR. This is NOT a software problem!
>
> I suggest you install and run memtest, at least for 24 hours. It should
> report no errors at all, if it does report errors, test the RAM modules
> one by one, to find out which is broken.
> …
not necessarily one broken. I once had a MB, two RAM modules
and this situation: Each of the modules alone tested ok, but the
two together failed! More likely a MB problem.