2.4 problems

2.4 problems

[Michel Dänzer]

Joseph Garcia wrote:

> > A few days ago, I rsynced linux-pmac-devel and tried 2.4.0-test7(-pre?) .
> > I had problems with the network, no TCP connection could be established.
> > Anyone seen this?
>
> When I tried 2.4, it takes forever for a name to resolve.  connections seem
> ok once they are made.

For me, the names got resolved, but no HTTP, IMAP, ... connection could be
established. As ICQ also worked, I conclude that TCP didn't work but UDP did.


> My system also seems to have a fork problem in 2.4.  su hangs for 2-3
> minutes.

Haven't seen that.


Michel


--
Earthling Michel Dänzer (MrCooper)  \  CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \   member of XFree86 and the DRI project

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

Re: 2.4 problems

[Dan Malek]

Michel Dänzer wrote:

> Haven't seen that.

My 7200 won't even boot.....


	-- Dan

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

Re: 2.4 problems

[Martin Costabel]

Dan Malek wrote:
>
> Michel Dänzer wrote:
>
> > Haven't seen that.
>
> My 7200 won't even boot.....

On my 6400, both bk-test8 and pmac-devel-test7 are running nicely. The
one major problem is random sudden freezes that can happen after some
minutes or after 3 days and which have been reported a couple of times
by others, too. It is like the ADB interrupt dies. There are no
messages, the computer is still alive, it goes on compiling or
downloading, and today I even could ssh in over the net, but locally,
keyboard and mouse are dead, even MagicSysRq, the only working key combo
is ctrl-cmd-power :-(

I never saw this with 2.2.X kernels (not recently, in any case).

--
Martin

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

Re: 2.4 problems

[Michel Lanners]

On  31 Aug, this message from Dan Malek echoed through cyberspace:
>
> Michel Dänzer wrote:
>
>> Haven't seen that.
>
> My 7200 won't even boot.....

And my G3-graded 7600 will only boot one out of 10-20 tries. The other
times, it dies at random places somewhere in init/main.c. When it does
boot up, it dies awfully while processing the rc scripts, with the oops
not showing any apparent problem. That crash is evil, since all
partitions except root will appear to be clean when in fact they are
not.

Which means major havoc will start to appear on my disks if I don't
force an immediate clean fsck....

I'd help debug the 2.4 kernels further, if I could get past these two
problems.... I've just now re-rsync'ed Paul's tree, lets see if there's
any difference....

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: 2.4 problems

[Benjamin Herrenschmidt]

>On my 6400, both bk-test8 and pmac-devel-test7 are running nicely. The
>one major problem is random sudden freezes that can happen after some
>minutes or after 3 days and which have been reported a couple of times
>by others, too. It is like the ADB interrupt dies. There are no
>messages, the computer is still alive, it goes on compiling or
>downloading, and today I even could ssh in over the net, but locally,
>keyboard and mouse are dead, even MagicSysRq, the only working key combo
>is ctrl-cmd-power :-(
>
>I never saw this with 2.2.X kernels (not recently, in any case).

Interesting. Do you have the new input layer enabled or are you still
running the old keyboard and mouse drivers ? If you telnet to the box, do
you still see ADB interrupts increasing when typing keys or not ?


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

Re: 2.4 problems

[Martin Costabel]

Benjamin Herrenschmidt wrote:
>
> >On my 6400, both bk-test8 and pmac-devel-test7 are running nicely. The
> >one major problem is random sudden freezes that can happen after some
> >minutes or after 3 days and which have been reported a couple of times
> >by others, too. It is like the ADB interrupt dies. There are no
> >messages, the computer is still alive, it goes on compiling or
> >downloading, and today I even could ssh in over the net, but locally,
> >keyboard and mouse are dead, even MagicSysRq, the only working key combo
> >is ctrl-cmd-power :-(
> >
> >I never saw this with 2.2.X kernels (not recently, in any case).
>
> Interesting. Do you have the new input layer enabled or are you still
> running the old keyboard and mouse drivers ?

I am now running the new input layer (with old keycodes). But I saw
(rather, suffered from) these freezes already before the arrival of the
new input layer. For a while I blamed it on Xpmac, where I seem to
remember having had these even with 2.2.x kernels, but I am using now
XFree-4.0.1-fbdev.

>                                              If you telnet to the box, do
> you still see ADB interrupts increasing when typing keys or not ?

You mean when I type on the local "dead" keyboard? I couldn't test this
yet, because the machine from which I sshed in was 15 km away at work.
And after a while I had the bad idea to type "hwclock -r", upon which
the 6400 was really dead, so I could not test it any further. While I
observed it, the ADB interrupt did not increase.

--
Martin

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

Re: 2.4 problems

[Benjamin Herrenschmidt]

>You mean when I type on the local "dead" keyboard? I couldn't test this
>yet, because the machine from which I sshed in was 15 km away at work.
>And after a while I had the bad idea to type "hwclock -r", upon which
>the 6400 was really dead, so I could not test it any further. While I
>observed it, the ADB interrupt did not increase.

Ok, so it looks like Cuda gets dead.

Iain Sandoe recently did work to improve the robustness of the Cuda state
machine. I didn't yet have time to look at his code, but it may be
interesting for you to test his patch.

Ben.


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

Re: 2.4 problems

[Iain Sandoe]

>>You mean when I type on the local "dead" keyboard? I couldn't test this
>>yet, because the machine from which I sshed in was 15 km away at work.
>>And after a while I had the bad idea to type "hwclock -r", upon which
>>the 6400 was really dead, so I could not test it any further. While I
>>observed it, the ADB interrupt did not increase.
>
> Ok, so it looks like Cuda gets dead.
>
> Iain Sandoe recently did work to improve the robustness of the Cuda state
> machine. I didn't yet have time to look at his code, but it may be
> interesting for you to test his patch.

It's not 2.4.0 (sorry)

- but, you can (a) either wait a few days - and I'll have a go or (b) take a
look at the 2.2.17 one and see (IMHO it shouldn't be difficult - the 2.4.0
via-cuda doesn't look much different from the 2.2.17 one).

Iain.

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