linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Jeglinski <jeglin@4pi.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: whacked out 2.2.18pre21?
Date: Fri, 17 Nov 2000 22:12:31 -0500	[thread overview]
Message-ID: <p04330100b63b9e07574a@[192.168.0.1]> (raw)
In-Reply-To: <200011060712.IAA00775@piglet.grunz.lu>


Last week I called this "whacked out 2.2.18pre17?"

I'm the one with the 6 cards in the PowerTowerPro, who can compile
2.2.18preX (linux-pmac-stable from penguinppc.org or
ppc.linuxcare.com or ppc.samba.org) but not boot it without a kernel
panic. I know that some think I should remove cards, but I've been
able to narrow things down a bit, and no longer do I think I have a
BootX problem, and I'm not so sure this is a PCI issue (although
maybe still).

Upgrading to BootX 1.2.2 didn't make a difference in any boot issues.

Always compiling the kernel for both video cards (imstt and matrox)
finally allowed BootX to pay attn to its no-video checkbox. Problem
solved.

Compiling without the "early BootX text" switch (or whatever that is)
eliminated all my freezes at "booting..." Problem solved.

Next I will start removing cards :-(, but I am highly suspicious of
the code involving the 2940UW card in the box. The -only- drives I
have are 2 9G atlases connected to the 2940. All 2.2.17 kernels I've
tried work fine. OTOH, every linux-pmac-stable 2.2.18preX kernel
panics just as it is beginning to register (poll? discover?) the SCSI
devices, at the same place where 2.2.17 properly recognizes the 2
drives and the 2940.

I have the pertinent debug info (backtrace, other registers,
System.map). Can I just post them here? I've never tried analyzing
one of these things. From what little sense I can make of it, it sure
looks like the panic has something to do with the aic7xxx code, or
related code. Roughly speaking, just after the fd0 (floppy) message
appears in the boot, I get :

Machine check in kernel mode
Caused by (from srr1): Unknown values in srr1
<debug info>
[kernel panic]

I'm compiling the kernel with default settings, other than including
the matrox driver. How might I compile the kernel differently w.r.t.
aic7xxx to try to nail this one down, if at all?

Once during the 2.2.17 linux-pmac-stable series, I got exactly this
srr1 error. I waited a couple of days and rsynced again and it was
gone. I always assumed that was due to some obscure bug creeping in
and then back out again. I feel in my bones this is the same
situation. I've written to Paul a couple of times about this, but I'm
sure to be low on his radar. Meanwhile, I rsync and try again each
day, without luck. BTW, I've tried this same troublesome 2.2.18
kernel on similar PowerTowerPro that I use and it works fine. That
PTP doesn't have a 2940 card in it, but it doesn't have all the PCI
slots filled either.

Any and all ideas welcome.


Stefan Jeglinski

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-11-18  3:12 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
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               ` Stefan Jeglinski [this message]
2000-11-18 20:03                 ` whacked out 2.2.18pre21? 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='p04330100b63b9e07574a@[192.168.0.1]' \
    --to=jeglin@4pi.com \
    --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).