Skip to contentSkip to conversation

Atari TT

DISCUSSION Geert Uytterhoeven 4 participants 8 messages Jan 5, 2012 – Jan 20, 2013 7 messages not in the archive

lore
Share & tools
lore
#7 lore raw
In reply to a message not in the archive
Quoted 1 line · Alan Hourihane

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.

Quoted 1 line

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.

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

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.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]

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

#8 lore raw
Quoted 9 lines · Geert Uytterhoeven
Quoted 1 line · Alan Hourihane

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.

Quoted 6 lines

But first the interrupt storm must be fixed.

Quoted 1 line

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.

This irq is used for the timer that generates the clock for the MFP serial port. It should really stay disabled.

Andreas.

Signature · 3 lines
Andreas Schwab, [email protected]
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."
#11 lore raw
In reply to Geert Uytterhoeven
Quoted 8 lines · Geert Uytterhoeven
Quoted 1 line · Alan Hourihane

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.

Quoted 5 lines

But first the interrupt storm must be fixed.

Quoted 1 line

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" ?

Quoted 2 lines

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.

Quoted 8 lines

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.

#12 lore raw
In reply to Geert Uytterhoeven
Quoted 11 lines · Geert Uytterhoeven
Quoted 1 line · Alan Hourihane

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.

Quoted 1 line

unexpected interrupt from 112

Quoted 9 lines

That's the vector number, so the actual IRQ number is 112 / 4 = 28, which is IRQ_TT_MFP_TIMD. Sorry, no clues.

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

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.

No it didn't work. Same problem.

Linux version 3.1.7-atari (root@server) (gcc version 4.5.3 (Gentoo 4.5.3-r1 p1.0, pie-0.4.5) ) #1 Thu Jan 5 18:57:55 GMT 2012 console [debug0] enabled
Atari hardware found: TT_SHIFTER ST_MFP TT_MFP TT_SCSI_DMA TT_SCSI YM2149 PCM SCC_DMA SCC VME SCU MICROWIRE TT_CLK FDC_SPEED ACSI Ignoring memory chunk at 0x0:0x400000 before the first chunk
Fix your bootloader or use a memfile to make use of this area! On node 0 totalpages: 32768
free_area_init_node: node 0, pgdat 003159a8, node_mem_map 0034e000
DMA zone: 288 pages used for memmap
DMA zone: 0 pages reserved
DMA zone: 32480 pages, LIFO batch:7
pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
pcpu-alloc: [0] 0
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32480 Kernel command line: console=tty fb=false video=atafb:ttmid debug=ser2 BOOT_IMAGE=vmlinux.gz
PID hash table entries: 512 (order: -1, 2048 bytes)
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 125372k/125372k available (2476k kernel code, 3112k data, 112k init) unexpected interrupt from 112
unexpected interrupt from 112
unexpected interrupt from 112
unexpected interrupt from 112
unexpected interrupt from 112
unexpected interrupt from 112
unexpected interrupt from 112
unexpected interrupt from 112
unexpected interrupt from 112
unexpected interrupt from 112
unexpected interrupt from 112
unexpected interrupt from 112
unexpected interrupt from 112
unexpected interrupt from 112
unexpected interrupt from 112
unexpected interrupt from 112
unexpected interrupt from 112
unexpected interrupt from 112
unexpected interrupt from 112
unexpected interrupt from 112
unexpected interrupt from 112
unexpected interrupt from 112
unexpected interrupt from 112
unexpected interrupt from 112

Alan.

#9 lore raw
In reply to Andreas Schwab
Quoted 10 lines · Andreas Schwab
Quoted 8 lines · Geert Uytterhoeven
Quoted 1 line · Alan Hourihane

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.

Quoted 8 lines
Quoted 5 lines

But first the interrupt storm must be fixed.

Quoted 1 line

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.

This irq is used for the timer that generates the clock for the MFP serial port. It should really stay disabled.

Could these spurious interrupts be generated by the debug path, because I'm now using it to output debug data ?

Alan.

#13 lore raw
In reply to Alan Hourihane
Quoted 11 lines · Alan Hourihane
Quoted 10 lines
Quoted 1 line

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.

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

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.

No it didn't work. Same problem.

That's bad. So most probably it's been broken on TT for a long time. AFAIK Atari receives most testing on (emulated -- ARAnyM) Falcon.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]

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

#10 lore raw
In reply to Alan Hourihane
Quoted 2 lines · Alan Hourihane

Could these spurious interrupts be generated by the debug path, because I'm now using it to output debug data ?

None of the debug devices are touching tt_mfp (ser2 uses the SCC, and ser1 uses st_mfp).

Andreas.

Signature · 3 lines
Andreas Schwab, [email protected]
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."
#14 lore raw
In reply to Geert Uytterhoeven

Geert Uytterhoeven dixit:

Quoted 7 lines · Alan Hourihane
Quoted 3 lines
Quoted 3 lines
Quoted 1 line

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.

That's bad. So most probably it's been broken on TT for a long time. AFAIK Atari receives most testing on (emulated -- ARAnyM) Falcon.

Ouch. Nothing on this? gemini8 (Bcc’d) reported the same in IRC using vmlinuz-3.8.0-rc3+m68k-queue+atari-84299-g3f4758a which I cross-built earlier.

Does anyone have an idea how to help debugging that? I’m sure gemini8 and, probably, Alan wouldn’t mind booting test kernels.

00:32 < gemini8> Ok, guys. I'm trying to run mirabilos' vmlinuz-3.8.0-rc3+m68k-queue+atari-84299-g3f4758a on my
TT. Bootstrap unpacks the kernel, kernel says something about booting, I'm getting loads of colourful pixels on my screen, and the floppy starts to blink.
00:32 < gemini8> That's it.
00:32 < gemini8> Anything I can specify in bootargs to maybe get another result?
00:33 < gemini8> It's the same with resolution I adjust in bootargs btw.
00:38 < ij> do you have serial/null modem cable? then try to add debug=ser to the kernel options 00:40 < gemini8> In theory yes.
00:40 < gemini8> Will have to find me a terminal though.
00:43 < ij> at least you can then see what's going wrong... I just did the same on my Amiga 00:58 < gemini8> https://dl.dropbox.com/u/32922157/linux-m68k/linux-m68k-on-tt030.txt

No idea whether adding (or not adding) -s makes a difference. Another thing that could be tried (wrt. the video) is the stram_reserve(IIRC?) option? Michael?

bye,
//mirabilos

Signature · 4 lines
„nein: BerliOS und Sourceforge sind Plattformen für Projekte, github ist
eine Plattform für Einzelkämpfer“
	-- dieses Zitat ist ein Beweis dafür, daß auch ein blindes Huhn
	   mal ein Korn findet, bzw. – in diesem Fall – Recht haben kann