Re: m68k und ipv6?
- To: Kilian Krause <firstname.lastname@example.org>
- Cc: Debian GNU/Linux m68k <email@example.com>
- Subject: Re: m68k und ipv6?
- From: Brad Boyer <firstname.lastname@example.org>
- Date: Tue, 7 Sep 2004 09:07:48 -0700
- Message-id: <20040907160748.GB16724@pants.nu>
- In-reply-to: <1094462669.4312.19.camel@localhost>
- References: <email@example.com> <20040814103107.GA29683@grep.be> <firstname.lastname@example.org> <Pine.LNX.email@example.com> <firstname.lastname@example.org> <Pine.LNX.email@example.com> <Pine.LNX.firstname.lastname@example.org> <email@example.com> <Pine.GSO.firstname.lastname@example.org> <1094462669.4312.19.camel@localhost>
On Mon, Sep 06, 2004 at 11:24:29AM +0200, Kilian Krause wrote:
> However my own kernel has a few shortcomings still. While booting the
> scsi system seems to encounter a timeout which however is recovered from
> . This is only a matter of my latest wildly trying changes to get
> things working. The first images i had tried worked quite ok in that
> sense (yet either the NIC wouldn't be a module, or other things that
> didn't get the whole thing flying).
> Nevertheless, the much larger problem is a kernel oops that does occur
> with the ADB keyboard or whatever  would like to tell me.
I'm inclined to say that this oops is still in the scsi code. However,
it doesn't seem to be where I would expect it. I'll have to dig my 650
out of the pile and try it out.
The function scsi_register_driver is only called in 4 places in the
entire kernel, and not a one of them is in a hardware or architecture
specific place. I suppose the oops could be wrong, but it is just after
some of the scsi messages.