On 2/8/06, linux-os (Dick Johnson) <[email protected]> wrote:
>
> On Wed, 8 Feb 2006, thomas wrote:
>
> > Hello,
> > I'm running Debian GNU/Linux Etch on an Acer Aspire 1682 laptop with
> > kernel 2.6.12-1-686. So far the system was rock solid but I'm now
> > experiencing a boot freeze:
> >
> > ... Setting up ICE socket directory /tmp/ICE-Unix... done
> > INIT: Entering runlevel: 2
> > Starting system log daemon: syslogd
> >
> > Then, nothing. However I can boot in "recover mode" (that is, single
> > user & root login). There does not seem to be any hardware failure,
> > the partitions are properly mounted, and there is engough free space
> > on any of them. When I shut down the box, hundreds of lines of errors
> > messages are outputted. I cannot read them all but here are the last
> > ones:
> >
> > EIP is at do_page_fault+0xd6/0x6bf
> > eax: dfa40000 ebx:00000000 ecx:0000007b edx:ffffff7b esi:00030001
> > edi:0000000d ebp:0000000b esp: dfa417c8
> > ds: 007b es:007b ss:0008 (snip)
> ^^^^^^^^^^^____ These are not correct segments!
>
> Something is corrupting the GDT or setting incorrect segments directly.
> Perhaps a driver? Or maybe your CPU is way too hot and is corrupting
> segments itself?
You may be right (but I did not install any new piece of hardware
recently). Maybe the following will help to understand the problem:
Booting for the tenth time worked surprisingly. As I shutdown the
system, this line was outputted without end:
inode hda2: 96697 at df6aa440: mode 120777, nlink 1, next 0
hda2 is my / partition. What does that mean? When I re-booted, then
re-shut down my computer, this worked flawlessly. Now everything seems
to work; however /var/log/boot contains a few errors:
Wed Feb 8 23:58:23 2006: Starting internet superserver:
inetdstart-stop-daemon: open pidfile /var/run/inetd.pid: Input/output
error (Input/output error)
Wed Feb 8 23:58:24 2006: Starting periodic command scheduler:
cronstart-stop-daemon: open pidfile /var/run/crond.pid: Input/output
error (Input/output error)
I don't want ask you to spend time for an
approximatively-self-solved-issue, but if you have an idee what
happened to my comp, I would be glad to hear it.
Thanks
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
