All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Hourihane <alanh@fairlite.co.uk>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Finn Thain <fthain@telegraphics.com.au>,
	Thorsten Glaser <tg@mirbsd.de>,
	debian-68k@lists.debian.org,
	Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: Atari TT
Date: Thu, 05 Jan 2012 17:04:18 +0000	[thread overview]
Message-ID: <4F05D812.6020109@fairlite.co.uk> (raw)
In-Reply-To: <CAMuHMdUK=2tkFtxQjua6LLGDJuEkrbK0W+mMVQ6PLBB9MfqPSw@mail.gmail.com>

On 05/01/12 14:42, Geert Uytterhoeven wrote:
> On Thu, Jan 5, 2012 at 13:55, Alan Hourihane <alanh@fairlite.co.uk> wrote:
>> Linux version 3.1.0-atari-00246-gbff0dc7 (root@server) (gcc version
> bff0dc7 = m68k-v3.1. That kernel still has the SCC driver, but it depends on
> BROKEN, so you cannot select it.
> If you revert 173808aa9203cf752518acd80fde3c9c910ddd0f ("m68k/atari: SCC
> - Mark Atari serial driver BROKEN") you can select CONFIG_ATARI_SCC again,
> and get a real serial console.
>
> But first the interrupt storm must be fixed.
>
>> unexpected interrupt from 112
> That's the vector number, so the actual IRQ number is 112 / 4 = 28, which is
> IRQ_TT_MFP_TIMD. Sorry, no clues.

It's worth enhancing that message then as the NR_IRQs reported was 72.
And it really confused me that 112 appeared.

Maybe...

"unexpected interrupt from 28, vector 112" ?

> Can you please try a pristine v3.1? The only relevant differences are the
> conversion to the genirq framework and the Atari SCC driver.

Will do.

> If that works, I guess it's a regression introduced by the genirq conversion.
> Then you can bisect between v3.1 and m68k-v3.1.
>
> BTW, in between 9fa434585e5f6cfeae685505b4cd8465dbab1dff ("m68k/irq:
> Add genirq support") and 971ae31663e817a5e5b673d30c7652d9160145f0
> ("m68k/irq: Remove obsolete m68k irq framework"), genirq support is a config
> option that can be turned on or off.
>

O.k. thanks.

Alan.

  parent reply	other threads:[~2012-01-05 17:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4F0488A9.5030100@fairlite.co.uk>
     [not found] ` <Pine.BSM.4.64L.1201041911580.19192@herc.mirbsd.org>
     [not found]   ` <alpine.LNX.2.00.1201052128060.6601@nippy.intranet>
     [not found]     ` <4F059460.5040305@fairlite.co.uk>
     [not found]       ` <CAMuHMdUxQq_29g7yeaS2Ktz193CcHNX5FaP8PR9ijU0htnKbZg@mail.gmail.com>
     [not found]         ` <4F059AE1.6070707@fairlite.co.uk>
     [not found]           ` <4F059DB9.1050209@fairlite.co.uk>
2012-01-05 14:42             ` Atari TT Geert Uytterhoeven
2012-01-05 15:49               ` Andreas Schwab
2012-01-05 19:40                 ` Alan Hourihane
2012-01-05 23:35                   ` Andreas Schwab
2012-01-05 17:04               ` Alan Hourihane [this message]
2012-01-05 19:02               ` Alan Hourihane
2012-01-05 20:35                 ` Geert Uytterhoeven
2013-01-20 16:52                   ` Thorsten Glaser
     [not found] <20130120205231.GC32291@mail.biophys.uni-duesseldorf.de>
     [not found] ` <Pine.BSM.4.64L.1301202117270.27441@herc.mirbsd.org>
     [not found]   ` <20130120225718.GA1459@mail.biophys.uni-duesseldorf.de>
     [not found]     ` <Pine.BSM.4.64L.1301232011550.14843@herc.mirbsd.org>
     [not found]       ` <20130123212251.GA14282@mail.biophys.uni-duesseldorf.de>
     [not found]         ` <Pine.BSM.4.64L.1301232213380.14843@herc.mirbsd.org>
     [not found]           ` <20130124000856.GA15759@mail.biophys.uni-duesseldorf.de>
     [not found]             ` <Pine.BSM.4.64L.1301241759530.6423@herc.mirbsd.org>
     [not found]               ` <20130124185341.GA27701@mail.biophys.uni-duesseldorf.de>
     [not found]                 ` <Pine.BSM.4.64L.1301241946080.6423@herc.mirbsd.org>
2013-01-24 20:20                   ` Michael Schmitz
2013-01-24 20:41                     ` Geert Uytterhoeven
2013-01-24 21:48                       ` Michael Schmitz
2013-01-25  7:30                         ` Geert Uytterhoeven
2013-01-25  8:14                           ` Michael Schmitz
2013-01-24 20:50                     ` Thorsten Glaser
2013-01-25  7:33                       ` Geert Uytterhoeven

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=4F05D812.6020109@fairlite.co.uk \
    --to=alanh@fairlite.co.uk \
    --cc=debian-68k@lists.debian.org \
    --cc=fthain@telegraphics.com.au \
    --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 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.