Re: 2.3.43 failed

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/

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/

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/

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/

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/

Paul Mackerras wrote:

On Mon, 14 Feb 2000, Martin Costabel wrote:

[]

quoted

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/

Le dim, 13 f�v 2000, Paul Mackerras a �crit :

On Sat, 12 Feb 2000, Eric Benard wrote:

quoted

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/

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/