From: "Christian T. Steigies" <cts@debian.org>
To: Michael Schmitz <schmitzmic@googlemail.com>
Cc: Thorsten Glaser <tg@mirbsd.de>, linux-m68k@vger.kernel.org
Subject: Re: Debian kernel 2.6.38-5
Date: Sun, 8 May 2011 23:45:46 +0200 [thread overview]
Message-ID: <20110508214546.GC16281@chumley.earth.sol> (raw)
In-Reply-To: <BANLkTin7E_Aedv8RAeaAfR_+me3YZgsbjw@mail.gmail.com>
On Mon, May 09, 2011 at 08:58:00AM +1200, Michael Schmitz wrote:
> Christian,
>
> > Yes, but I am not trying to build a debian package, I try to build directly
> > from linux-m68k. This has worked, only the Amiga complained a missing
> > modules.dep (but I built in the network driver):
>
> Run depmod -a after the Amiga has booted.
I guess I did not have the modules on the linux partition yet...
> > make ARCH=m68k CROSS_COMPILE=m68k-linux-gnu-
> > make ARCH=m68k CROSS_COMPILE=m68k-linux-gnu- INSTALL_MOD_PATH=/data/m68k modules_install
> >
> > The kernel boots, it configures the network (static). When I try to ping a
> > host on my network, I get this oops(?). A few seconds later I also get the
> > mismatch message I reported earlier (does not show up in dmesg?).
>
> It should show up - if it's being printed to the console it has to be
> in the kernel log buffer for klogd to pick up.
You are right, I did not wait long enough. In 2.6.32 I see it in dmesg, same
error as before :-(
In addition the network module (and I thought it was built in...) did not
get loaded on boot. After insmoding it (modprobe did not work), the errors
came back. In addition sshd was blocking the kernel, so the system was
fairly unresponsive.
2.6.30 with TLS patch does not boot, I guess I did something wrong (do I
need to activate a kernel option?).
enough for today... but since Geert has found the problem, I hope a patch is
not far away :-)
Christian
next prev parent reply other threads:[~2011-05-08 21:44 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 [this message]
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
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=20110508214546.GC16281@chumley.earth.sol \
--to=cts@debian.org \
--cc=linux-m68k@vger.kernel.org \
--cc=schmitzmic@googlemail.com \
--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