All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stuart Longland <redhatter@gentoo.org>
To: linux-mips@linux-mips.org
Subject: IP22 (Indy) Breakage
Date: Sat, 04 Feb 2006 01:07:58 +1000	[thread overview]
Message-ID: <43E371CE.2080302@gentoo.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1025 bytes --]

Hi all,
	I've just done a checkout of git HEAD (as of 23rd January), and struck
this little gem whilst trying to boot a kernel on my Indy.

	http://dev.gentoo.org/~redhatter/misc/ip22-r4k6-2615.png

	I figured WD33C93 SCSI was the culprit, so I modularised that (with the
intention of modprobing it later), and set up a kernel with IP Level
AutoConfiguration (via DHCP) and Root-over-NFS support, to try and
isolate the SCSI problem.  That yeilded the following crash.

	http://dev.gentoo.org/~redhatter/misc/ip22-r4k6-2615-nfs.png

	I've heard this affects both R4600 and R5000 Indys.  It would seem
there's some breakage of the sgiseeq and wd33c93 drivers due to changes
in the surrounding API, but this is an uneducated guess. :-)  Would
someone have some pointers as to where I should look for problems?

Regards,
-- 
Stuart Longland (aka Redhatter)              .'''.
Gentoo Linux/MIPS Cobalt and Docs Developer  '.'` :
. . . . . . . . . . . . . . . . . . . . . .   .'.'
http://dev.gentoo.org/~redhatter             :.'

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]

             reply	other threads:[~2006-02-03 15:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-03 15:07 Stuart Longland [this message]
2006-02-03 15:12 ` IP22 (Indy) Breakage Stuart Longland

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=43E371CE.2080302@gentoo.org \
    --to=redhatter@gentoo.org \
    --cc=linux-mips@linux-mips.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.