From: Finn Thain <fthain@telegraphics.com.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "Christian T. Steigies" <cts@debian.org>,
Thorsten Glaser <tg@mirbsd.de>,
linux-m68k@vger.kernel.org
Subject: Re: Debian kernel 2.6.38-5
Date: Tue, 10 May 2011 21:57:07 +1000 (EST) [thread overview]
Message-ID: <alpine.OSX.2.00.1105102031140.446@ibook.intranet> (raw)
In-Reply-To: <BANLkTin-bsA6KYbCawtrnUdQ-PhqGrTyOA@mail.gmail.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 2008 bytes --]
On Tue, 10 May 2011, Geert Uytterhoeven wrote:
> On Mon, May 9, 2011 at 01:14, Finn Thain <fthain@telegraphics.com.au>
> wrote:
> > On Sun, 8 May 2011, Christian T. Steigies wrote:
> >>
> >> PS 2.6.28 did not boot: kernel too old. When was TLS introduced? I'll
> >> try to apply the patch you mentioned in your other message.
> >
> > I sometimes test network cards with busybox. It can be built without
> > linking in glibc and doesn't need TLS.
> >
> >
> >> [ 130.870000] eth0: trigger_send() called with the transmitter busy.
> >> [ 132.240000] ------------[ cut here ]------------
> >> [ 132.240000] WARNING: at net/sched/sch_generic.c:256 dev_watchdog+0x1ac/0x1cc()
> >> [ 132.250000] NETDEV WATCHDOG: eth0 (): transmit queue 0 timed out
> >
> > Looks a lot like this problem:
> >
> > http://patchwork.ozlabs.org/patch/27774/
>
> Finn, could it also work if you remove the "#include "lib8390.c" from
> *8390.c? That would reduce code size for distro kernels, which would
> have too many copies of lib8390.c (for zorro8390, mac8390, hydra)?
ISTR that I tried the approach you suggest back when I fixed mac8390 but
couldn't make it fly but I don't recall why not.
I see that ax88796.c and ne-h8300.c also #include <lib8390.c>. In
ax88796.c I find this:
#define __ei_open ax_ei_open
#define __ei_close ax_ei_close
...
#include "lib8390.c"
which would have been better than my patch for mac8390; without this
renaming you may not be able to link a sane multi-sub-arch m68k kernel.
OTOH, I don't know if it is possible to build a single 8390.o that can
work for multiple drivers either.
BTW, ne-h8300 appears to lack the fixes in your patch and mine and so it
probably doesn't work properly either.
I'm not really sure how to tackle this; I'd like to think that we could
use 8390.o for the m68k drivers at least but I need to investigate
further.
Finn
>
> Gr{oetje,eeting}s,
>
> Geert
next prev parent reply other threads:[~2011-05-10 11:56 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-23 18:00 Debian kernel v2.6.38 (was: Re: Fix for SLUB?) Geert Uytterhoeven
2011-04-23 18:13 ` Debian kernel v2.6.38 Thorsten Glaser
2011-04-23 19:19 ` Geert Uytterhoeven
2011-04-23 19:58 ` Thorsten Glaser
2011-04-23 22:12 ` Michael Schmitz
2011-04-24 8:18 ` Geert Uytterhoeven
2011-04-24 11:37 ` Thorsten Glaser
2011-04-25 2:36 ` Michael Schmitz
2011-04-25 14:19 ` Thorsten Glaser
2011-04-25 1:33 ` Thorsten Glaser
2011-04-24 16:18 ` Finn Thain
2011-04-25 2:48 ` Michael Schmitz
2011-04-25 3:53 ` Finn Thain
2011-04-29 23:44 ` Michael Schmitz
2011-05-08 12:58 ` Debian kernel 2.6.38-5 Thorsten Glaser
2011-05-08 16:59 ` Christian T. Steigies
2011-05-08 18:00 ` Geert Uytterhoeven
2011-05-08 18:49 ` Thorsten Glaser
2011-05-08 19:26 ` Geert Uytterhoeven
2011-05-08 18:40 ` Thorsten Glaser
2011-05-08 20:08 ` Christian T. Steigies
2011-05-08 20:22 ` Geert Uytterhoeven
2011-05-08 20:58 ` Michael Schmitz
2011-05-08 21:45 ` Christian T. Steigies
2011-05-08 21:30 ` Thorsten Glaser
2011-05-08 23:14 ` Finn Thain
2011-05-09 7:16 ` Geert Uytterhoeven
2011-05-09 20:25 ` Christian T. Steigies
2011-05-09 22:49 ` Michael Schmitz
2011-05-10 7:00 ` Christian T. Steigies
2011-05-10 7:38 ` Michael Schmitz
2011-05-09 20:28 ` zorro8390 (was: Re: Debian kernel 2.6.38-5) Geert Uytterhoeven
2011-05-10 9:01 ` Debian kernel 2.6.38-5 Geert Uytterhoeven
2011-05-10 11:57 ` Finn Thain [this message]
2011-05-10 12:06 ` Geert Uytterhoeven
2011-05-08 20:53 ` Michael Schmitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.OSX.2.00.1105102031140.446@ibook.intranet \
--to=fthain@telegraphics.com.au \
--cc=cts@debian.org \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@vger.kernel.org \
--cc=tg@mirbsd.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox