Re: 2.3.43 failed

Re: 2.3.43 failed

[Paul Mackerras]

On Sat, 12 Feb 2000, ramp@oddjob.uchicago.edu wrote:

> 2.3.43 failed as well on my iMac. Anyone have better luck?
> It didn't get past softirq.h.

My rsync tree at linuxcare.com.au::linux-pmac-devel is at 2.3.44-pre8, it
should compile and run just fine on an iMac.

--
Paul Mackerras, Senior Open Source Researcher, Linuxcare, Inc.
+61 2 6262 8990 tel, +61 2 6262 8991 fax
paulus@linuxcare.com.au, http://www.linuxcare.com.au/
Linuxcare.  Support for the revolution.

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

Re: 2.3.43 failed

[Michael R. Zucca]

At 12:07 PM -0500 2/12/00, Catherine & Andreas wrote:

>> > My rsync tree at linuxcare.com.au::linux-pmac-devel is at 2.3.44-pre8, it
>> > should compile and run just fine on an iMac.
>>
>> it compiles fine on a B&W G3 but doesn't run : it stops after the
>>"Booting..."
>> message.

This is the same problem I had with 2.2.14 on my PowerCenter 132. I just
compiled a recent rsync of the linux-pmac-devel tree and had the same hang.

I think it has something to do with the boot environment. When I boot under
MacOS 9 with the BootX application, the boot will only get as far as
"Booting..." and then some registers (i.e. never get to Tux and the linux
boot info). However, if I boot using the BootX extension instead, the
kernel will get to boot and run the kernel but then it crashes with a
machine check. I think the crash is happening in the serial driver, or the
sound driver. I can't tell which for sure yet. I'd like to try booting
right out of OF to see if that changes anything.

Did we change something about the way we setup memory early in the boot
process after 2.2.12 because the 2.2.12 kernel that came with my Yellowdog
distribution works just great out of BootX.

Thanks!

____________________________________________________________________
 Michael Zucca - mrz5149@acm.org - http://www.mdc.net/~mrz5149/
 "I will choose a path that's clear. I will choose Freewill. "
  --Rush, Freewill
____________________________________________________________________


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

Re: 2.3.43 failed

[ramp]

Paul -
Thanks for the 2.3.44. The compile went smoothly and the machine booted
fine as well but I still continue to have USB keyboard/mouse problems.
>From the USB debug I can see that my keyboard and mouse are being
recognized. But nothing happens when I type or move the mouse. I have
had the same problems with other dev kernels as well. I have tried
unplugging and plugging back the kbd/mouse. Everything works fine
in 2.2.14.

What should my /etc/sysconfig/keyboard and /etc/sysconfig/mouse be?
My current files are
[ramp@localhost ~]$ cat /etc/sysconfig/keyboard
KEYTABLE=
KEYBOARDTYPE="usb"
[ramp@localhost ~]$ cat /etc/sysconfig/mouse
MOUSETYPE="Busmouse"
XMOUSETYPE="BusMouse"
FULLNAME="Universal Serial Bus 3+ Button Mouse (USB)"
XEMU3=yes

In /dev should I have /dev/usbmouse or /dev/usb/mouse? Currently i have
[ramp@localhost ~]$ ls -l /dev/usbmouse
lrwxrwxrwx   1 root     root           11 Dec 17 18:56 /dev/usbmouse ->
hidbp-mse-0
[ramp@localhost ~]$ ls -l /dev/hidbp-mse-0
crw-r--r--   1 root     root      10,  32 Apr 30  1999 /dev/hidbp-mse-0
Should there be a /dev/keyboard or some such?

Help please. This is killing me - Ram

PS: I just used the default pmac_config on my Rev D iMac. In the linux-usb
site the howto says that one should not set HIDBP. But the defaults in the
.config are set to HIDBP?


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

Re: 2.3.43 failed

[Nelson Abramson]

ramp@oddjob.uchicago.edu wrote:

> What should my /etc/sysconfig/keyboard and /etc/sysconfig/mouse be?
> My current files are
> [ramp@localhost ~]$ cat /etc/sysconfig/keyboard
> KEYTABLE=
> KEYBOARDTYPE="usb"
> [ramp@localhost ~]$ cat /etc/sysconfig/mouse
> MOUSETYPE="Busmouse"
> XMOUSETYPE="BusMouse"
> FULLNAME="Universal Serial Bus 3+ Button Mouse (USB)"
> XEMU3=yes

You want to set your mouse type to ps2 (this is well documented in the
install guides...)

HTH
--Nelson Abramson

--
Shouldn't people be arrested and persecuted for engaging in their
constitutional rights?  http://www.opendvd.org


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

Sucess with 2.3.44pre !!

[ramp]

OK _ Lots more progress. Kernel 2.3.44pre compiles and boots. Turns out
that I should *not* select HIDBP for mouse/keyboard in the dot config.
Keyboard and mouse do register as well as the USBZip drive. Now I have to
figure out how to mount and read/write from it.

Ramprasad


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

Re: 2.3.43 failed

[Paul Mackerras]

On Sat, 12 Feb 2000, Eric Benard wrote:

> it compiles fine on a B&W G3 but doesn't run : it stops after the "Booting..."
> message.

I just updated linuxcare.com.au::linux-pmac-devel to 2.3.44 final.  I
fixed a couple of problems where it would hang during boot if you booted
from OF (or with quik or yaboot) and it couldn't find the screen.  Try it
now.  If it doesn't work, let me know (and tell me how you are booting it).

--
Paul Mackerras, Senior Open Source Researcher, Linuxcare, Inc.
+61 2 6262 8990 tel, +61 2 6262 8991 fax
paulus@linuxcare.com.au, http://www.linuxcare.com.au/
Linuxcare.  Support for the revolution.

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

Re: 2.3.43 failed

[Andreas Tobler]

Paul Mackerras wrote:
> I just updated linuxcare.com.au::linux-pmac-devel to 2.3.44 final.  I
> fixed a couple of problems where it would hang during boot if you booted
> from OF (or with quik or yaboot) and it couldn't find the screen.  Try it
> now.  If it doesn't work, let me know (and tell me how you are booting it).

Updated to 2.3.44 this morning.
Compiles but doesn't boot, hangs on the message booting.....
PM7200, booting via BootX ext & app (BootX V: 1.2b1)
I try to get the latest BootX.

Andreas
--
| Andreas Tobler
| CH-8004 Zuerich
| E-Mail:   a.tobler@schweiz.ch
-----------------------------------------------


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

Re: 2.3.43 failed

[Paul Mackerras]

On Sun, 13 Feb 2000, Andreas Tobler wrote:

> Updated to 2.3.44 this morning.
> Compiles but doesn't boot, hangs on the message booting.....
> PM7200, booting via BootX ext & app (BootX V: 1.2b1)

:-(

It works OK on my 7600.  I'll see if I can get over to ANU and try it on a
7200 there.

--
Paul Mackerras, Senior Open Source Researcher, Linuxcare, Inc.
+61 2 6262 8990 tel, +61 2 6262 8991 fax
paulus@linuxcare.com.au, http://www.linuxcare.com.au/
Linuxcare.  Support for the revolution.

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

Re: 2.3.43 failed

[Martin Costabel]

Paul Mackerras wrote:

> I just updated linuxcare.com.au::linux-pmac-devel to 2.3.44 final.  I
> fixed a couple of problems where it would hang during boot if you booted
> from OF (or with quik or yaboot) and it couldn't find the screen.  Try it
> now.  If it doesn't work, let me know (and tell me how you are booting it).

On my 6400, it compiles and boots OK, but there are some little itches:

- rsync complains about "send_files failed to open
Documentation/kernel-docs.txt: Permission denied"

- rsync copies a spurious file drivers/net/.#ppp_generic.c which is a
dead symlink

- during booting, there is a message
"/proc/sys/net/ipv4/ip_always_defrag is missing - Cannot control IP
fragmentation"

- while using my ethernet card with the de4x5 driver, I get hundreds of
"kernel: Warning: kfree_skb on hard IRQ c010ded8". Seeing that this
address is inside the de4x5 driver, I tried to compile it as a module,
so that I could also compare it to the tulip driver. Didn't work at
first:

- the tulip module loads without problem, but doesn't seem to like my
ethernet card (DEC 21041 chip). It gives me hundreds of "kernel: eth0:
21041 transmit timed out, status fc6800". With 2.2.14 kernels, the tulip
module works OK.

- the de4x5 module complains about missing symbols; and this is in fact
a bug I had mentioned already some days ago. I repeat the patch below.
It seems to be necessary, and it cures the problem. I am now on the net
with de4x5 as a module, but I still get the warnings, now with an
address in the module:
Feb 13 15:06:14 rennes-231 kernel: Warning: kfree_skb on hard IRQ
c7159770
Feb 13 15:07:24 rennes-231 last message repeated 421 times
Feb 13 15:12:01 rennes-231 last message repeated 97 times
and so on.

How can I get rid of the warnings (short of disabling the line that
produces it in net/core/skbuff.c)?

Here is the patch needed by pci driver modules:

--- arch/ppc/kernel/ppc_ksyms.c.ori     Fri Feb  4 10:18:20 2000
+++ arch/ppc/kernel/ppc_ksyms.c Fri Feb  4 10:28:10 2000
@@ -11,6 +11,7 @@
 #include <linux/spinlock.h>
 #include <linux/console.h>
 #include <linux/irq.h>
+#include <linux/pci.h>

 #include <asm/page.h>
 #include <asm/semaphore.h>
@@ -137,6 +138,9 @@
 EXPORT_SYMBOL(__clear_user);
 EXPORT_SYMBOL(__strncpy_from_user);
 EXPORT_SYMBOL(__strnlen_user);
+
+EXPORT_SYMBOL(pci_alloc_consistent);
+EXPORT_SYMBOL(pci_free_consistent);

 /*
 EXPORT_SYMBOL(inb);

--
Martin

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

Re: 2.3.43 failed

[Paul Mackerras]

On Mon, 14 Feb 2000, Martin Costabel wrote:

> On my 6400, it compiles and boots OK, but there are some little itches:
>
> - rsync complains about "send_files failed to open
> Documentation/kernel-docs.txt: Permission denied"

Fixed now.

> - rsync copies a spurious file drivers/net/.#ppp_generic.c which is a
> dead symlink

It was an emacs lock file or something.

> - during booting, there is a message
> "/proc/sys/net/ipv4/ip_always_defrag is missing - Cannot control IP
> fragmentation"

Rusty (Paul Russell) here reckons that he personally ripped that out
(leaving a bleeding stump :-) early in the 2.3 series, because it isn't
needed any more.

> - while using my ethernet card with the de4x5 driver, I get hundreds of
> "kernel: Warning: kfree_skb on hard IRQ c010ded8". Seeing that this
> address is inside the de4x5 driver, I tried to compile it as a module,
> so that I could also compare it to the tulip driver. Didn't work at
> first:

Apparently you now have to use dev_kfree_skb_irq instead of dev_kfree_skb
in hardware interrupt routines.  Presumably the de4x5 driver hasn't been
converted yet.

> - the tulip module loads without problem, but doesn't seem to like my
> ethernet card (DEC 21041 chip). It gives me hundreds of "kernel: eth0:
> 21041 transmit timed out, status fc6800". With 2.2.14 kernels, the tulip
> module works OK.
>
> - the de4x5 module complains about missing symbols; and this is in fact
> a bug I had mentioned already some days ago. I repeat the patch below.
> It seems to be necessary, and it cures the problem. I am now on the net
> with de4x5 as a module, but I still get the warnings, now with an
> address in the module:
> Feb 13 15:06:14 rennes-231 kernel: Warning: kfree_skb on hard IRQ
> c7159770
> Feb 13 15:07:24 rennes-231 last message repeated 421 times
> Feb 13 15:12:01 rennes-231 last message repeated 97 times
> and so on.
>
> How can I get rid of the warnings (short of disabling the line that
> produces it in net/core/skbuff.c)?

Find the places where dev_kfree_skb is called from interrupt context and
change them to dev_kfree_skb_irq.  If you aren't sure you can say

	if (in_irq())
		dev_kfree_skb_irq(skb);
	else
		dev_kfree_skb(skb);

> Here is the patch needed by pci driver modules:

Thanks, I've applied that to my sources.

I just tried 2.3.44 on the powerbook 3400 and it fell over during boot.
Oh well.

--
Paul Mackerras, Senior Open Source Researcher, Linuxcare, Inc.
+61 2 6262 8990 tel, +61 2 6262 8991 fax
paulus@linuxcare.com.au, http://www.linuxcare.com.au/
Linuxcare.  Support for the revolution.

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

Re: 2.3.43 failed

[Martin Costabel]

Paul Mackerras wrote:
>
> On Mon, 14 Feb 2000, Martin Costabel wrote:
[]
> > Feb 13 15:06:14 rennes-231 kernel: Warning: kfree_skb on hard IRQ
> > c7159770
> > Feb 13 15:07:24 rennes-231 last message repeated 421 times
> > Feb 13 15:12:01 rennes-231 last message repeated 97 times
> > and so on.
> >
> > How can I get rid of the warnings (short of disabling the line that
> > produces it in net/core/skbuff.c)?
>
> Find the places where dev_kfree_skb is called from interrupt context and
> change them to dev_kfree_skb_irq.  If you aren't sure you can say
>
>         if (in_irq())
>                 dev_kfree_skb_irq(skb);
>         else
>                 dev_kfree_skb(skb);

Thanks. Your new version in 2.3.45pre works correctly (shows me once
more why I'm not a kernel developer: I replaced all 3 occurrences of
dev_kfree_skb by if (in_irq()) ... else ..., which worked, too; you
replaced just one of them by dev_kfree_skb_irq; I had tried this before,
but always got the wrong one :-( ).

--
Martin

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

Re: 2.3.43 failed

[Paul Mackerras]

On Mon, 14 Feb 2000, Martin Costabel wrote:

> Thanks. Your new version in 2.3.45pre works correctly (shows me once
> more why I'm not a kernel developer: I replaced all 3 occurrences of
> dev_kfree_skb by if (in_irq()) ... else ..., which worked, too; you
> replaced just one of them by dev_kfree_skb_irq; I had tried this before,
> but always got the wrong one :-( ).

Actually, I can't take the credit, the fix was in the official 2.3.45-pre2.

--
Paul Mackerras, Senior Open Source Researcher, Linuxcare, Inc.
+61 2 6262 8990 tel, +61 2 6262 8991 fax
paulus@linuxcare.com.au, http://www.linuxcare.com.au/
Linuxcare.  Support for the revolution.

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

Re: 2.3.43 failed

[Eric Benard]

Le dim, 13 fév 2000, Paul Mackerras a écrit :
> On Sat, 12 Feb 2000, Eric Benard wrote:
>
> > it compiles fine on a B&W G3 but doesn't run : it stops after the "Booting..."
> > message.
>
> I just updated linuxcare.com.au::linux-pmac-devel to 2.3.44 final.  I
> fixed a couple of problems where it would hang during boot if you booted
> from OF (or with quik or yaboot) and it couldn't find the screen.  Try it
> now.  If it doesn't work, let me know (and tell me how you are booting it).
>
I just tried with the 2.3.45 from linux-pmac-devel and it makes exctlly the
same thing.
I'm using BootX 1.2b1 with MacOS 8.6 to boot.

My root partition is on an external SCSI HD connected to an Adaptec 2906 scsi
card.


Eric

______________________________________________________________________________
Si votre email etait sur iFrance vous pourriez ecouter ce message au tel !
http://www.ifrance.com : ne laissez plus vos emails loin de vous ...
gratuit sur iFrance :  emails (20 MO, POP, FAX), Agenda, Site perso

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

Re: 2.3.43 failed

[Jeremy Knope]

ditto... any 2.3.x kernel i've tried... 42,44,45 hault
at Booting... message on my BlueG3 400 DVD (rev2)
 any clue anybody out there? this being the
linuxcare.com.au kernel i've tried. i would like to
find a 2.3.x kernel for BlueG3.
  -jeremy



=====
/---------------------------------\
|        Jeremy T. Knope          |
|      swttiggr2@yahoo.com        |
|---------------------------------|
| jerome@knopej1.umeres.maine.edu |

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