whacked out 2.2.18preX - last gasp

whacked out 2.2.18preX - last gasp

[Stefan Jeglinski]

[refer to all previous whacked out posts]


In deference to BenH's necessary suggestion, I removed all of the 6
cards I could from my PowerTowerPro. It's now down to the only 2 I
need: a video card (imstt running the OFfb just fine like it always
has) and the 2940UW card, connected to my 2 9Gig atlas drives. I
can't do fewer cards than these, and I've tried them in different
slots.

Thanks to Hollis, I learned how to determine that a kernel panic at
boot occurs in ioremap, called by the aic7xxx driver (backtrace
posted the other day). If I compile without the aic7xxx driver, the
panic does not occur but of course I cannot mount the root device.

The following kernels fail identically:

ppc.samba.org::linux-pmac-stable-2.2.18preX
ppc.linuxcare.com:: linux-pmac-stable-2.2.18preX
penguinppc.org:: linux-pmac-stable-2.2.18preX
bk://bitkeeper.fsmlabs.com:5001 (2.2.18preX)

(yes, every X I've tried for about a month now)

The following kernels work fine:
linux-pmac-stable (2.2.17)
penguinppc.org::linux-pmac-benh (2.2.18pre17)

I want 2.2.18 because it appears to have the full USB backport
(according to linux-usb.org). Also AFAICT, the "backports" on
linux-usb.org are really patches to take 2.2.17 to 2.2.18preX - they
don't really "add USB to 2.2.17."

I don't know why Ben's 2.2.18pre17 alone works, but it appears to be
irrelevant because of Ben's statement that all his rsync trees are
inactive. The only clue I have is both odd and almost totally
irrelevant: the only kernels that work (both 2.2.17 and 2.2.18) are
the ones that create a

	ERROR - Attempting to write value for
	unconfigured variable (CONFIG_SERIAL_CONSOLE).

when using make xconfig. I can't see how this could be related, but it is true.

It's frankly hard at this point to buy that one of my PCI devices is
walking over the kernel. Or if it is, it looks like the end of the
Linux line for my PowerTowerPro with the 2940 card. I think this is
either a bug in the aic7xxx driver that has been exposed by 2.2.18
changes (highly doubtful, there are too many 2940s out there for it
to have been missed), or a linux-pmac bug. I just don't know enough
yet to prove it, much less find it.



c-ya



Stefan Jeglinski

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

Re: whacked out 2.2.18preX - last gasp

[Michael Schmitz]

> The following kernels work fine:
> linux-pmac-stable (2.2.17)
> penguinppc.org::linux-pmac-benh (2.2.18pre17)
>
> I want 2.2.18 because it appears to have the full USB backport
> (according to linux-usb.org). Also AFAICT, the "backports" on

The PPC source trees always had the 'full USB backport' (nothing else
would work on PPC) for all I know.

	Michael


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

Re: whacked out 2.2.18preX - last gasp

[Stefan Jeglinski]

>  > I want 2.2.18 because it appears to have the full USB backport
>>  (according to linux-usb.org). Also AFAICT, the "backports" on
>
>The PPC source trees always had the 'full USB backport' (nothing else
>would work on PPC) for all I know.


Hmm, I've tried compiling in the USB stuff that's in 2.2.17. I have
to turn a lot more off than in 2.2.18 to get it to compile. I've also
been unsuccessful at getting my Logitech USB mouse + Orangelink USB
board to work under 2.2.17, but I can't tell if it's because I had to
turn certain things off. That's why I want 2.2.18 so bad, from what
I've read I'm lead to believe there's a good chance to get it
working. I know it's not a good measure, but the USB config in 2.2.18
seems much more complete (and has filled-in help text!) compared to
2.2.17.

I'll continue my daily compiles. Hopefully it will magically
disappear the same way it appeared.


Stefan Jeglinski

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

Re: whacked out 2.2.18preX - last gasp

[Michael Schmitz]

> >  > I want 2.2.18 because it appears to have the full USB backport
> >>  (according to linux-usb.org). Also AFAICT, the "backports" on
> >
> >The PPC source trees always had the 'full USB backport' (nothing else
> >would work on PPC) for all I know.
>
>
> Hmm, I've tried compiling in the USB stuff that's in 2.2.17. I have

I can safely assume you are talking about BenH's or Paul's 2.2.17 here?
I've only tried with standard PowerMac and USB hardware (as in: mouse,
keyboard), and that worked fine since I forgot when.

	Michael


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

Re: whacked out 2.2.18preX - last gasp

[Tom Rini]

On Mon, Nov 20, 2000 at 11:03:43PM -0500, Stefan Jeglinski wrote:

> 	ERROR - Attempting to write value for
> 	unconfigured variable (CONFIG_SERIAL_CONSOLE).
>
> when using make xconfig. I can't see how this could be related, but it is true.

xconfig is buggy sometimes.  Try make oldconfig afterwards, it'll prompt for
anything which didn't get set by xconfig.

> It's frankly hard at this point to buy that one of my PCI devices is
> walking over the kernel. Or if it is, it looks like the end of the
> Linux line for my PowerTowerPro with the 2940 card. I think this is
> either a bug in the aic7xxx driver that has been exposed by 2.2.18
> changes (highly doubtful, there are too many 2940s out there for it
> to have been missed), or a linux-pmac bug. I just don't know enough
> yet to prove it, much less find it.

Hmm.  2.2.18pre21 from linuxppc_2_2 bk works on my G4/Yikes! with a 2940UW
in it.  What compiler are you using?

--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/

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

Re: whacked out 2.2.18preX - last gasp

[Stefan Jeglinski]

>  >	ERROR - Attempting to write value for
>>	unconfigured variable (CONFIG_SERIAL_CONSOLE).
>>
>>  when using make xconfig. I can't see how this could be related,
>>but it is true.
>
>xconfig is buggy sometimes.  Try make oldconfig afterwards, it'll prompt for
>anything which didn't get set by xconfig.

Yeah, that's why I don't see that my observations can be related to
this. I also tried make oldconfig and it lead to the same results.


>  > It's frankly hard at this point to buy that one of my PCI devices is
>>  walking over the kernel. Or if it is, it looks like the end of the
>>  Linux line for my PowerTowerPro with the 2940 card. I think this is
>>  either a bug in the aic7xxx driver that has been exposed by 2.2.18
>>  changes (highly doubtful, there are too many 2940s out there for it
>>  to have been missed), or a linux-pmac bug. I just don't know enough
>>  yet to prove it, much less find it.
>
>Hmm.  2.2.18pre21 from linuxppc_2_2 bk works on my G4/Yikes! with a 2940UW
>in it.  What compiler are you using?

dmesg:

	gcc version 2.95.2 19991024 (release/franzo) #1

rpm -qa |grep gcc:

	gcc-2.95.2-1i
	gcc-c++-2.95.2-1i
	gcc-objc-2.95.2-1i


What I'm worried about mainly is the 6 slots and the PCI bridge
structure in the PowerTowerPro (akin to PowerMac 9500). It is more
"complex" than G4, no? From my previous discussion with you and
others, I gather that there are a lot of problems with the PCI stuff,
that may not be cleared up for quite a while?


Stefan Jeglinski

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

Re: whacked out 2.2.18preX - last gasp

[Tom Rini]

On Tue, Nov 21, 2000 at 10:25:45AM -0500, Stefan Jeglinski wrote:

> >  > It's frankly hard at this point to buy that one of my PCI devices is
> >>  walking over the kernel. Or if it is, it looks like the end of the
> >>  Linux line for my PowerTowerPro with the 2940 card. I think this is
> >>  either a bug in the aic7xxx driver that has been exposed by 2.2.18
> >>  changes (highly doubtful, there are too many 2940s out there for it
> >>  to have been missed), or a linux-pmac bug. I just don't know enough
> >>  yet to prove it, much less find it.
> >
> >Hmm.  2.2.18pre21 from linuxppc_2_2 bk works on my G4/Yikes! with a 2940UW
> >in it.  What compiler are you using?
>
> dmesg:
>
> 	gcc version 2.95.2 19991024 (release/franzo) #1
>
> rpm -qa |grep gcc:
>
> 	gcc-2.95.2-1i
> 	gcc-c++-2.95.2-1i
> 	gcc-objc-2.95.2-1i

You might wanna try 2.95.3-2j, which should be in fsirl's dir on dev.  But I
really do doubt this is why.

> What I'm worried about mainly is the 6 slots and the PCI bridge
> structure in the PowerTowerPro (akin to PowerMac 9500). It is more
> "complex" than G4, no? From my previous discussion with you and
> others, I gather that there are a lot of problems with the PCI stuff,
> that may not be cleared up for quite a while?

Actually, the linuxppc_2_5 bitkeeper tree (which is getting merged into
2_3, for inclusing into hopefully 2.4.0-final from linus) has a giant PCI
re-write, so 9500s/et al might actually work happily now.  But yes, from what
I've gathered from trying to work w/ a 9500 and 2.2.18pre21 there just might
be something broken now.  (The video card refuses to work at all, regardless
of slot).

--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/

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

Re: whacked out 2.2.18preX - last gasp

[Benjamin Herrenschmidt]

>
>Actually, the linuxppc_2_5 bitkeeper tree (which is getting merged into
>2_3, for inclusing into hopefully 2.4.0-final from linus) has a giant PCI
>re-write, so 9500s/et al might actually work happily now.  But yes, from what
>I've gathered from trying to work w/ a 9500 and 2.2.18pre21 there just might
>be something broken now.  (The video card refuses to work at all, regardless
>of slot).

_2_5 will help configs with multiple PCI busses except for IO ports which
will still be available on the first bus only. This may get fixed for PCI
IO BARs if we end up mapping virtually all the IO spaces appended together.

Ben.


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

Re: whacked out 2.2.18preX - last gasp

[Michel Lanners]

> _2_5 will help configs with multiple PCI busses except for IO ports which
> will still be available on the first bus only. This may get fixed for PCI
> IO BARs if we end up mapping virtually all the IO spaces appended together.

... which prompts me to ask: have you tried the 2940 in the three upper
    slots _and_ in the three lower slots? Same result both times?

Michel

-------------------------------------------------------------------------
Michel Lanners                 |  " Read Philosophy.  Study Art.
23, Rue Paul Henkes            |    Ask Questions.  Make Mistakes.
L-1710 Luxembourg              |
email   mlan@cpu.lu            |
http://www.cpu.lu/~mlan        |                     Learn Always. "


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

Re: whacked out 2.2.18preX - last gasp

[Stefan Jeglinski]

>  > _2_5 will help configs with multiple PCI busses except for IO ports which
>>  will still be available on the first bus only. This may get fixed for PCI
>>  IO BARs if we end up mapping virtually all the IO spaces appended together.
>
>... which prompts me to ask: have you tried the 2940 in the three upper
>     slots _and_ in the three lower slots? Same result both times?


No, Ben had same Q, I tried the 2940 in only 3 slots last night
(dunno why I didn't, just got tired of it I guess). With renewed
vigor, will do all 6 tonight and let y'all know.



Stefan Jeglinski

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