From: Felix von Leitner <felix-linuxkernel@fefe.de>
To: linux-kernel@vger.kernel.org
Subject: kernel suddenly fails to boot
Date: Sun, 16 Nov 2008 02:15:37 +0000 [thread overview]
Message-ID: <20081116021537.GA32090@codeblau.de> (raw)
I'm talking about kernel 2.6.27, but I also tried 2.6.27.6.
The stunning thing is that the kernel USED to work until right about
now. I last booted Linux on this box yesterday evening. I have had
intermittend boot problems, but they always go away after a reset or two.
The box would freeze at boot at a message about ACPI. Since it usually
went away after a reset, and the box is stable once it boots, I never
really cared enough to fix it.
This is a Core 2 Duo on an Abit IP35 mainboard. The kernel is a 64-bit
kernel.
The very last line before the current freeze is:
TIMER: vector=0x30 acpi1=0 pin1=2 apic2=-1 pin2=-1
I googled this line and found people suggesting "nolapic_timer",
"noapic" or "nolapic". None of these work. This is a 64-bit SMP
system. I also tried "noacpi". All of these get a little farther, but
still freeze the kernel before it even starts looking for SATA devices.
Windows (32-bit XP) still works on the box.
Any ideas what I could do now?
I tried updating the BIOS after this problem hit, but the BIOS update
utility said I already have the latest BIOS.
I have four gigs of RAM in the box, Windows XP only uses 3.25 of those.
Could this be a problem on the remaining RAM?
I also tried "memtest=1", which paused a little but then booted the same
kernel and also froze just the same.
Felix
next reply other threads:[~2008-11-16 2:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-16 2:15 Felix von Leitner [this message]
2008-11-16 3:03 ` kernel suddenly fails to boot Tamber Krain
2008-11-16 12:19 ` markus reichelt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081116021537.GA32090@codeblau.de \
--to=felix-linuxkernel@fefe.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.