From: Stefan Jeglinski <jeglin@4pi.com>
To: Benjamin Herrenschmidt <bh40@calva.net>,
<linuxppc-dev@lists.linuxppc.org>
Subject: Re: whacked out 2.2.18pre17?
Date: Sat, 4 Nov 2000 01:03:01 -0500 [thread overview]
Message-ID: <p04330100b629527c3036@[192.168.0.1]> (raw)
In-Reply-To: <19340928092828.1670@192.168.1.2>
> >I am aware that this kernel is being worked on daily (that's why I
>>try to rebuild it each night), but I'm a little surprised that I am
>>having so much trouble with a pre17 kernel. Anybody know what's up?
>>Is this thing going through such big changes that I should let it go
>>for a while instead of trying each night?
>
>Well, first try with a more recent bootx.. that may help.
After a long evening of playing with this, I stand by my original assertion :-)
I did update to BootX 1.2.2, and started from scratch by playing with
several settings. I also scrounged several 2.2.18 versions, newly
rsynced from penguinppc.org::linux-pmac-stable and
ppc.linuxcare.com::linux-pmac-stable, and also earlier 2.2.18 rsyncs
that were stored on different computers available to me.
The two things that are constant on my hardware (PowerTowerPro +
PowerLogix G3, 6 PCI cards, most of which are not seen anyway,
2940UW):
1. Full boot is impossible, always with one of the following circumstances:
a) freeze at "booting..."
b) can't find MAC address for MACE device -> kernel panic
c) "machine check in kernel mode" -> "unknown values in srr1" ->
kernel panic
2. no video checkbox is ignored, on or off. There is no way to force
OFfb, regardless of kernel args or video checkboxes. The imstt card
is -always- found and the driver -always- loaded. Most odd, I've
never seen this one before.
Reverting to 2.2.17-linux-pmac-stable fixes everything. Looks to me
like 2.2.18-linux-pmac-stable is undergoing serious under-the-hood
changes, at least for my hardware. It makes me pretty nervous. I
don't think I have the expertise to sleuth this, I just wanted to
post to the list in case the info helped anyone.
Stefan Jeglinski
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-11-04 6:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-03 5:53 whacked out 2.2.18pre17? Stefan Jeglinski
2000-11-03 15:56 ` Benjamin Herrenschmidt
2000-11-04 6:03 ` Stefan Jeglinski [this message]
2000-11-04 12:47 ` Benjamin Herrenschmidt
2000-11-04 15:55 ` Stefan Jeglinski
2000-11-05 9:36 ` Michel Lanners
2000-11-05 22:59 ` Stefan Jeglinski
2000-11-06 7:12 ` Michel Lanners
2000-11-18 3:12 ` whacked out 2.2.18pre21? Stefan Jeglinski
2000-11-18 20:03 ` Stefan Jeglinski
2000-11-18 20:09 ` aic7xxx panic in 2.2.18pre21 Hollis R Blanchard
2000-11-18 21:33 ` Stefan Jeglinski
2000-11-10 6:58 ` whacked out 2.2.18pre17? [partly solved] Stefan Jeglinski
2000-11-03 23:52 ` whacked out 2.2.18pre17? Tony Mantler
2000-11-04 1:15 ` Stefan Jeglinski
2000-11-04 2:01 ` Tony Mantler
2000-11-04 12:35 ` Simon Piette
2000-11-04 15:32 ` Tony Mantler
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='p04330100b629527c3036@[192.168.0.1]' \
--to=jeglin@4pi.com \
--cc=bh40@calva.net \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).