All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Michael Schmitz <schmitzmic@googlemail.com>
Cc: "Christian T. Steigies" <cts@debian.org>,
	Tuomas Vainikka <tuomas.vainikka@aalto.fi>,
	Finn Thain <fthain@telegraphics.com.au>,
	Linux/m68k <linux-m68k@lists.linux-m68k.org>
Subject: Re: watchdog (?) on linux 3.0.0 and 2.6.39.3
Date: Sun, 14 Aug 2011 10:29:42 +0200	[thread overview]
Message-ID: <CAMuHMdWf4wnto0Y5u01XDPpSfJeHDPCRV06w1ZWejNHpFs2sAQ@mail.gmail.com> (raw)
In-Reply-To: <4E474E7D.2000405@gmail.com>

On Sun, Aug 14, 2011 at 06:26, Michael Schmitz
<schmitzmic@googlemail.com> wrote:
>>> Christian - can you remember which 2.6 kernel that last had ethernet
>>> working for you?
>>>
>>
>> I haven't been testing kernels a lot recently... from the logfiles it
>> would
>> seem the last kernel that was running on kullervo was this one:
>>
>> Linux version 2.6.24-1-amiga (Debian 2.6.24-4) (waldi@debian.org) (gcc
>> version 3.3.6) #1 Tue Feb 12 10:05:37 CET 2008
>>
>
> Plain 2.6.24 from Geert's tree does show TX timeouts again - no watchdog
> firing this time because IDE wasn't even built as module (something cause
> make oldconfig to drop all IDE stuff when starting from Tuomas' .config).
>
> Speaking of which - I cannot even build IDE at all in that release:
>
>  CC [M]  drivers/ide/ide-lib.o
> drivers/ide/ide-lib.c: In function `ide_dump_atapi_status':
> drivers/ide/ide-lib.c:601: internal compiler error: in
> verify_local_live_at_start, at flow.c:600
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <URL:http://gcc.gnu.org/bugs.html> for instructions.
>
> I'm sure we've seen that before and it did eventually get fixed.

You can probably work around that by building with "make V=1" to show
the compile command,
and manually executing it with a lower optimization level.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  reply	other threads:[~2011-08-14  8:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-01 12:12 watchdog (?) on linux 3.0.0 and 2.6.39.3 Tuomas Vainikka
2011-08-01 19:03 ` Geert Uytterhoeven
2011-08-02  5:33 ` Finn Thain
2011-08-04 16:59   ` Tuomas Vainikka
2011-08-04 20:45     ` Michael Schmitz
2011-08-05  2:44       ` Finn Thain
2011-08-05 11:53       ` Tuomas Vainikka
2011-08-05 22:32         ` Michael Schmitz
2011-08-06  9:56           ` Geert Uytterhoeven
2011-08-07 20:01             ` Michael Schmitz
2011-08-07 22:07               ` Christian T. Steigies
2011-08-08  0:23                 ` Michael Schmitz
2011-08-08 10:52                   ` Tuomas Vainikka
2011-08-14  4:26                 ` Michael Schmitz
2011-08-14  8:29                   ` Geert Uytterhoeven [this message]
2011-08-14 20:40                     ` 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=CAMuHMdWf4wnto0Y5u01XDPpSfJeHDPCRV06w1ZWejNHpFs2sAQ@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=cts@debian.org \
    --cc=fthain@telegraphics.com.au \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=schmitzmic@googlemail.com \
    --cc=tuomas.vainikka@aalto.fi \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.