All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Richmond <bob@lorez.org>
To: kernel-stuff@comcast.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: Immediate general protection errors on Tyan board
Date: Fri, 30 Sep 2005 08:49:48 -0700	[thread overview]
Message-ID: <433D5E9C.2030708@lorez.org> (raw)
In-Reply-To: <431BE9CE.8080302@comcast.net>

I just got it working over the weekend. The machine had an Adaptec 29320 
64-bit PCI card driving a SCSI HD. It was removed, and the drive 
replaced with a Serial ATA drive, and it came up fine.

There were probably a lot of variables that were changed by removing the 
card, but I'm wondering if anyone has experienced the same symptoms with 
any 64-bit PCI card installed on this board.

Parag Warudkar wrote:

> 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.
> 
> Parag

      parent reply	other threads:[~2005-09-30 15:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-05  6:35 Immediate general protection errors on Tyan board Bob Richmond
2005-09-05  6:46 ` Parag Warudkar
2005-09-06  6:03   ` Sander
2005-09-30 15:49   ` Bob Richmond [this message]

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=433D5E9C.2030708@lorez.org \
    --to=bob@lorez.org \
    --cc=kernel-stuff@comcast.net \
    --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.