On Mon, 23 Dec 2013, Thorsten Glaser wrote:
> > CONFIG_EARLY_PRINTK=y and CONFIG_SERIAL_PMACZILOG=n
Why is CONFIG_SERIAL_PMACZILOG to be disabled? And why was
CONFIG_EARLY_PRINTK disabled?
> I think we need to file bugs in the BTS for each of these instances in
> the future, instead of trying
Dixi quod…
>Hi $maintainer,
>
>can we still get CONFIG_EARLY_PRINTK=y and
>CONFIG_SERIAL_PMACZILOG=n into 3.12 before it hits unstable?
This was, of course, not integrated into src:linux before the
3.12.6-1 upload. (Which by the way autobuilt, meaning we have
build logs ☻ instead of me building i
Am 22.11.2013 16:46, schrieb Geert Uytterhoeven:
> Hi Finn,
>
> On Fri, Nov 22, 2013 at 1:46 PM, Geert Uytterhoeven
> wrote:
>> pmz_console_init() doesn't do that, so it still registered the console, and
>> caused a crash later.
> Adding a check there is a simpler solution that also works.
>
> Gr
Hi Finn,
On Fri, Nov 22, 2013 at 1:46 PM, Geert Uytterhoeven
wrote:
> pmz_console_init() doesn't do that, so it still registered the console, and
> caused a crash later.
Adding a check there is a simpler solution that also works.
Gr{oetje,eeting}s,
Geert
--
Geert Uytte
On Fri, Nov 22, 2013 at 12:47 AM, Finn Thain wrote:
> On Thu, 21 Nov 2013, Geert Uytterhoeven wrote:
>
>> Unable to handle kernel NULL pointer dereference at virtual address (null)
>> Oops:
>> PC: [<0013ad28>] __pmz_startup+0x32/0x2a0
>
> [snip]
>
>> Call Trace: [<002c5d3e>] pmz_console
On Fri, Nov 22, 2013 at 10:13 AM, Geert Uytterhoeven
wrote:
> On Thu, Nov 21, 2013 at 11:02 PM, Finn Thain
> wrote:
>>> Surprise 2: Instead of a deadly non-Mac driver, I found a deadly Mac driver.
>>> When passing "debug=ser", it crashes with:
>>
>> The __pmz_startup() crash could be expected re
On Thu, Nov 21, 2013 at 11:02 PM, Finn Thain wrote:
>> Surprise 2: Instead of a deadly non-Mac driver, I found a deadly Mac driver.
>> When passing "debug=ser", it crashes with:
>
> The __pmz_startup() crash could be expected regardless of "debug=ser", no?
Yes, that's why I asked Thorsten if the
On Thu, 21 Nov 2013, Geert Uytterhoeven wrote:
> Unable to handle kernel NULL pointer dereference at virtual address (null)
> Oops:
> PC: [<0013ad28>] __pmz_startup+0x32/0x2a0
[snip]
> Call Trace: [<002c5d3e>] pmz_console_setup+0x64/0xe4
> [<9600>] atari_keyboard_interrupt+0x164
On Thu, 21 Nov 2013, Geert Uytterhoeven wrote:
> head.S has this "interesting" piece of code, which plays foul of
> multi-platform kernels:
>
> #ifdef CONFIG_MAC
>
> #include
>
> #ifdef CONFIG_FRAMEBUFFER_CONSOLE
> #define CONSOLE
> #define CONSOLE_PENGUIN
> #endif
>
> #ifdef CONFIG_EARLY_PR
Geert Uytterhoeven dixit:
>On Thu, Nov 21, 2013 at 1:04 PM, Thorsten Glaser wrote:
>>>I guess we can't see whether the '\n' was printed?
>>
>> Put an 'L' directly before it.
>
>Sure, but I meant without adding more debug code.
But adding this one, to show we’re entering C, is still
a good thing
I gave linux-image-3.12-trunk-m68k_3.12-1~exp1_m68k.deb a try on my
Amiga. Actually I tried my own first, using my current tree, and a config
derived from config-3.12-1~exp1, as I couldn't find the Debian kernel.
However, both gave the same result.
Surprise 1: There was no ABC...
head.S has this
On Thu, Nov 21, 2013 at 1:04 PM, Thorsten Glaser wrote:
>>I guess we can't see whether the '\n' was printed?
>
> Put an 'L' directly before it.
Sure, but I meant without adding more debug code.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyo
Geert Uytterhoeven dixit:
>I guess we can't see whether the '\n' was printed?
Put an 'L' directly before it.
bye,
//mirabilos
--
*Ctrl-Alt-L*
Hallo?
*Ctrl-Alt-L*
Ach ja, mein ‘l’ ist ja kaputt…
--
To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org
with a subject of "unsubscribe"
On Thu, Nov 21, 2013 at 10:38 AM, Finn Thain wrote:
> On Thu, 21 Nov 2013, Michael Schmitz wrote:
>
>> Serial or early fb console looks the only way to debug this.
>
> It hangs at "K", which means that none of the messages that would normally
> appear on the early console have appeared yet.
There
14 matches
Mail list logo
