Have a box with P4, 1G RAM, 60 Gig HDD dual booting Linux Mint and Debian
Etch 4.0 with GRUB.
Have had a major crash.
Computer worked fine in the morning but later in the day I powered up and
got the GRUB screen showing Mint and Etch selection menu as per normal.
Tried to boot into Etch, which I use normally and after some scrolling text
in a console the system froze with a kernel panic indication.
I did a soft reboot using the computer reset button into Mint and got the
same frozen kernel panic warning.
Inserted a Knoppix Live Distro Disc into the DVD tray and tried a reboot.
The computer recognised the live distro and then froze with the same kernel
panic message whilst trying to boot.
Any thoughts please ...maybe HDD or motherboard ...thanks in advance.
Klang
Why would it be HDD if a Live CD does the same? Sounds like RAM or Mobo
or some other HW to me.
>Collegues
It is a hardware problem. Almost certainly motherboard-- maybe memory.
Now if you actually told us what that kernel panic message was....
> "Klang" <gcl...@ozemail.com.au> writes:
>> Have a box with P4, 1G RAM, 60 Gig HDD dual booting Linux Mint and Debian
>> Etch 4.0 with GRUB.
>> Have had a major crash.
>> Computer worked fine in the morning but later in the day I powered up and
>> got the GRUB screen showing Mint and Etch selection menu as per normal.
>> Tried to boot into Etch, which I use normally and after some scrolling
>> text in a console the system froze with a kernel panic indication.
[snip; repeatable, even when booting from CD]
> It is a hardware problem. Almost certainly motherboard-- maybe memory. Now
> if you actually told us what that kernel panic message was....
Include whatever triggered the panic; chances are that it's an "oops" message
with a register dump and stack backtrace. If you can possibly capture the
kernel log on another computer, you should...
http://www.mjmwired.net/kernel/Documentation/networking/netconsole.txt
http://www.mjmwired.net/kernel/Documentation/serial-console.txt
--
| Darren Salt | linux or ds at | nr. Ashington, | Toon
| RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army
| + At least 4000 million too many people. POPULATION LEVEL IS UNSUSTAINABLE.
Look at all the Indians! - General Custer
Check your RAM. I had the same exact problem a month ago on my old box.
I fiddled with my two RAM pieces. One went bad. I RMA'ed it and waiting
to get it returned.
--
"Since the world began, we have never exterminated. We probably shall
never exterminate as much as one single insect species. If there was
ever an example of an insect we cannot destroy, the fire ant is it."
--an entomologist quote mentioned by Leonard Nimoy on In The Search Of:
Deadly Ants (1978)
/\___/\
/ /\ /\ \ Phil/Ant @ http://antfarm.home.dhs.org (Personal Web Site)
| |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
\ _ / Remove ANT from e-mail address: phi...@earthlink.netANT
( ) or ANT...@zimage.com
Ant is currently not listening to any songs on his home computer.
I second the RAM suggestion, I had a similar story.
i
My story was that I had two hard random lockups for no reasons within
two days. After that, my machine refused to boot up so I thought maybe
my PSU, video card, or motherboard went dead. My friend and I didn't
think it was RAM when we changed them (except motherboard). Then, he
tried RAM with different combinations and in various slots (three).
Either Kernel would panic at Linux boot up or not. They were random. As
you can see the lockup problem went to worse. :)
I don't know what caused the RAM to go bad. Maybe old age?
--
"I look at an ant and I see myself: a native South African, endowed by
nature with a strength much greater than my size so I might cope with
the weight of a racism that crushes my spirit." --Miriam Makeba
In the absence of knowledge of the real reason why memory gates appear
to spontaneously fail, I evenly attribute these kind of failures to bad
luck, neutrinos, and divine providence, depending on my mood.
--
Regards,
Sheridan Hutchinson
Sher...@Shezza.org
> Ant wrote:
>> I don't know what caused the RAM to go bad. Maybe old age?
>
> In the absence of knowledge of the real reason why memory gates appear
> to spontaneously fail, I evenly attribute these kind of failures to bad
> luck, neutrinos, and divine providence, depending on my mood.
Bad computer luck for me then. Computers hate me. I break them too
easily, but then that is why I am a software quality assurance tester. :D
--
"Yo mama is so poor, I saw her fighting an ant for food." --unknown