From: Wilfried Weissmann <Wilfried.Weissmann@gmx.at>
To: alex-n@ua.fm
Cc: linux-kernel@vger.kernel.org
Subject: Re: BUG?
Date: Tue, 21 May 2002 12:14:00 +0200 [thread overview]
Message-ID: <3CEA1DE8.6080201@gmx.at> (raw)
In-Reply-To: <web-10136453@ua.fm>
alex-n@ua.fm wrote:
> Dear Sirs,
> this can be lamer's question (I'm sorry rite now!), but...
>
> The report itself is:
>
> ################################################################################
>
> [1.] Linux crashes at the 'interactive startup' boot stage.
>
> [2.] Once the system is trying to boot, first stage (which is
> *before* msg 'Interactive startup') it is all O.K. Once the
> 'Interactive startup' stage begins, the bootstrap process
> fails with diffirent msgs; all of them begins with "Unable
> to handle kernel paging request at address..." or "Unable
> to handle kernel dereference at address..." (first 'reason'
> is in the majority of cases, the second is quite unusual).
>
> It seems to me that this is a trouble with initrd.img,
> because once I've recompiled kernel with ALL OPTIONS (not
> suitable to my hardware, i.e. SCSI adapters) turned OFF,
> the problem remains.
[snip]
2.4.7 does not have some VIA chipset workarounds that caused oopses when
the kernel was compiled with K7 optimization. So set the optimization to
AMD K6 or use a more recent kernel version. I think 2.4.16 and later
versions have fixed this problem.
hope this helps,
Wilfried
next prev parent reply other threads:[~2002-05-21 10:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-21 9:48 BUG? alex-n
2002-05-21 10:14 ` Wilfried Weissmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-04-01 13:39 Bug? Sascha Curth
2007-04-01 13:54 ` Bug? Michal Piotrowski
2001-12-31 18:09 bug ? Klaus Zerwes
2001-12-31 18:51 ` Stephan von Krawczynski
2002-01-05 11:44 ` Klaus Zerwes
2002-01-05 15:37 ` Stephan von Krawczynski
2002-01-02 14:03 ` Simon Richter
2001-12-08 0:31 bug?? wolvie_cobain
2001-12-07 10:33 Bug? Ian Molton
2001-12-07 10:56 ` Bug? DevilKin
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=3CEA1DE8.6080201@gmx.at \
--to=wilfried.weissmann@gmx.at \
--cc=alex-n@ua.fm \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox