Date: Tue, 6 Sep 2005 08:03:46 +0200
From: Sander <sander@humilis.net>
To: Parag Warudkar <kernel-stuff@comcast.net>
Cc: Bob Richmond <bob@lorez.org>, linux-kernel@vger.kernel.org
Subject: Re: Immediate general protection errors on Tyan board
Message-ID: <20050906060346.GA9071@favonius>
Reply-To: sander@humilis.net
References: <431BE71F.2040901@lorez.org> <431BE9CE.8080302@comcast.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <431BE9CE.8080302@comcast.net>
User-Agent: Mutt/1.5.10i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1461
Lines: 37

Parag Warudkar wrote (ao):
> Bob Richmond wrote:
> >Immediately upon boot on this system, most userland programs will 
> >segfault, including mount. This causes the system to come up in a 
> >bizarre state with the root filesystem mounted read-only, and nothing 
> >runs without segfault. There have been numerous similar posts about 
> >this problem, but they also seem to point to an associated kernel 
> >message, "Bad page state" that I don't observe. dmesg (which runs 
> >without segfault) returns many similar messages to:
> >
> >start_udev[576] general protection rip:2aaaaae0fc70 rsp:7fffffb23d90 
> >error:0
> 
> echo 0 > /proc/sys/kernel/randomize_va_space - Seems to fix it for most 
> people.
> 
> See http://bugzilla.kernel.org/show_bug.cgi?id=4851 for more details.

I only had some programs segfault, but this got resolved by doing an
update of the OS (Debian). It also started after an update of Debian.

Both programs installed with Debian packages as self-compiled programs
crashed with the ".. general protection rip: .." and ".. segfault at
..".

This happened on a dual Opteron Tyan system running 2.6.12-rc5.

	Kind regards, Sander

-- 
Humilis IT Services and Solutions
http://www.humilis.net
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/