2.4.2 USB and "mon>" (was Re: All 6 cards!!!)

2.4.2 USB and "mon>" (was Re: All 6 cards!!!)

[Stefan Jeglinski]

Refer to
<http://lists.linuxppc.org/listarcs/linuxppc-user/200103/msg00229.html>

Running 2.4.2 (kfukui) on 9500-class machine with an OrangeMicro USB
firewire card [ADB keyboard + USB mouse], have noted 2 things:


1. I get a "mon>" prompt on about half of the boots. And on half of
those, typing "x" exits me from mon and continues the boot. The rest
just hang. What is mon anyway? I've already seen reference to this on
the user list, not sure what the solution is...

2. No USB mouse response in X. lspci -vv, in part, gives:

01:0d.0 USB Controller: OPTi Inc. 82C861 (rev 10) (prog-if 10 [OHCI])
         Subsystem: OPTi Inc.: Unknown device c861
         Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
         Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort+ <MAbort- >SERR- <PERR-
         Latency: 32 set, cache line size 08
         Interrupt: pin A routed to IRQ 1
         Region 0: Memory at 80800000 (32-bit, non-prefetchable) [size=4K]


I'm concerned about the "IRQ 1". Is "1" correct?

I can live with the mon, but not without my mouse. Any suggestions here?


Stefan Jeglinski

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: 2.4.2 USB and "mon>" (was Re: All 6 cards!!!)

[Iain Sandoe]

Hi Stefan,

> 1. I get a "mon>" prompt on about half of the boots. And on half of
> those, typing "x" exits me from mon and continues the boot. The rest
> just hang. What is mon anyway? I've already seen reference to this on
> the user list, not sure what the solution is...

the kernel has "oopsed" - and dropped you into xmon (debugger).  You can
find out more by doing "?" to list the commands and getting a traceback and
exception report.

This will tell people where the problem lies.

> 2. No USB mouse response in X. lspci -vv, in part, gives:

> I can live with the mon, but not without my mouse. Any suggestions here?

have you done the changes in /dev to accommodate the new input layer?

iain.

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: 2.4.2 USB and "mon>" (was Re: All 6 cards!!!)

[Stefan Jeglinski]

>  > 1. I get a "mon>" prompt on about half of the boots. And on half of
>>  those, typing "x" exits me from mon and continues the boot. The rest
>>  just hang. What is mon anyway? I've already seen reference to this on
>>  the user list, not sure what the solution is...
>
>the kernel has "oopsed" - and dropped you into xmon (debugger).  You can
>find out more by doing "?" to list the commands and getting a traceback and
>exception report.
>
>This will tell people where the problem lies.

OK, thanks.


>  > 2. No USB mouse response in X. lspci -vv, in part, gives:
>
>>  I can live with the mon, but not without my mouse. Any suggestions here?
>
>have you done the changes in /dev to accommodate the new input layer?


Yes, I was already running input layer on 2.2.18, with no problems.
AFAICT, there are no /dev changes for 2.4.2 if I had already done
them for 2.2.18, no?


Stefan Jeglinski

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: 2.4.2 USB and "mon>" (was Re: All 6 cards!!!)

[Iain Sandoe]

>>have you done the changes in /dev to accommodate the new input layer?

> Yes, I was already running input layer on 2.2.18, with no problems.
> AFAICT, there are no /dev changes for 2.4.2 if I had already done
> them for 2.2.18, no?

well, I guess you'll have to see where the problem lies (i.e. the oops) and
then go from there.
Iain.

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: 2.4.2 USB and "mon>" (was Re: All 6 cards!!!)

[Benjamin Herrenschmidt]

>Running 2.4.2 (kfukui) on 9500-class machine with an OrangeMicro USB
>firewire card [ADB keyboard + USB mouse], have noted 2 things:
>

Can you try a couple of things:

 - First, check if the kernel works without the USB card

 - Then, edit prom.c, and looks for the code that calls OF "quiesce" call.
   This code might be inside a if () checking OF version. If it is, then
remove
   the if () to force a call on all OF versions

Ben.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: 2.4.2 USB and "mon>" (was Re: All 6 cards!!!)

[Michel Lanners]

On   6 Mar, this message from Benjamin Herrenschmidt echoed through cyberspace:
>
>>Running 2.4.2 (kfukui) on 9500-class machine with an OrangeMicro USB
>>firewire card [ADB keyboard + USB mouse], have noted 2 things:
>>
>
> Can you try a couple of things:
>
>  - First, check if the kernel works without the USB card

The probelm with the USB card is related to it getting IRQ1. Something
is fishy with assigning PCI interrupts (still or once again, I don't
know...)

>  - Then, edit prom.c, and looks for the code that calls OF "quiesce" call.
>    This code might be inside a if () checking OF version. If it is, then
> remove
>    the if () to force a call on all OF versions

Are you sure this is right? While trying to solve my
2.4-paulus-doesn't-boot-my-7600 probelm, I came across that code; and
sure enough, OF 1.0.5 (whic Stefan has in his 9500 also) doesn't have a
'quiesce' OF word.

Michel

-------------------------------------------------------------------------
Michel Lanners                 |  " Read Philosophy.  Study Art.
23, Rue Paul Henkes            |    Ask Questions.  Make Mistakes.
L-1710 Luxembourg              |
email   mlan@cpu.lu            |
http://www.cpu.lu/~mlan        |                     Learn Always. "


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: 2.4.2 USB and "mon>" (was Re: All 6 cards!!!)

[Benjamin Herrenschmidt]

>Are you sure this is right? While trying to solve my
>2.4-paulus-doesn't-boot-my-7600 probelm, I came across that code; and
>sure enough, OF 1.0.5 (whic Stefan has in his 9500 also) doesn't have a
>'quiesce' OF word.

It doesn't, yes, but did it break ?

Ben.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: 2.4.2 USB and "mon>" (was Re: All 6 cards!!!)

[Benjamin Herrenschmidt]

>The probelm with the USB card is related to it getting IRQ1. Something
>is fishy with assigning PCI interrupts (still or once again, I don't
>know...)

Right, we may be beeting the infamous IRQ-behind-a-PCI<->PCI bridge problem.

I guess we don't properly walk up the tree to get the interrupt and the card
may have a PCI<->PCI bridge on it.


Stefan: Could you try disabling the driver for the card in the kernel, and
sending me the output of lsprop for your entire device tree ?

lsprop can usually be found on paulus site, just in case, I'll email it to
you separately.

Ben.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: 2.4.2 USB and "mon>" (was Re: All 6 cards!!!)

[Michel Lanners]

On   7 Mar, this message from Benjamin Herrenschmidt echoed through cyberspace:
>
>>Are you sure this is right? While trying to solve my
>>2.4-paulus-doesn't-boot-my-7600 probelm, I came across that code; and
>>sure enough, OF 1.0.5 (whic Stefan has in his 9500 also) doesn't have a
>>'quiesce' OF word.
>
> It doesn't, yes, but did it break ?

Oh yes, sure enough. However, I am unable to tell you _where_ exactly it
breaks.

I've been unable to boot _any_ 2.3/2.4 kernels on my machine since
around 2.3.99 or a bit earlier. Some revisions would boot part of the
time, but most of them not at all. Symtom is always the same: hang
before initializing the framebuffer, i.e. still on the OF screen.

I get the 'retunring 0x... from prom_init' string, but nothing after
that.....

Michel

-------------------------------------------------------------------------
Michel Lanners                 |  " Read Philosophy.  Study Art.
23, Rue Paul Henkes            |    Ask Questions.  Make Mistakes.
L-1710 Luxembourg              |
email   mlan@cpu.lu            |
http://www.cpu.lu/~mlan        |                     Learn Always. "


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: 2.4.2 USB and "mon>" (was Re: All 6 cards!!!)

[Iain Sandoe]

> I've been unable to boot _any_ 2.3/2.4 kernels on my machine since
> around 2.3.99 or a bit earlier.

2.4.2-p3 (BK) boots fine on my 9600/233 as did 2.4.1 (BK).

* only PCI card is the imstt tho' which is in slot $F2 *

2.4.2-p3 is the last one I tried. - and, yes, same OF rev. 1.0.5.

only probs. I've had are:
 an occasional crash on re-boot and
 the (old, but come back) non/corrupted-display of pix maps on the X login
screen.

will try 2.4.3 soon (hopefully).

Iain.

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: 2.4.2 USB and "mon>" (was Re: All 6 cards!!!)

[Benjamin Herrenschmidt]

>Oh yes, sure enough. However, I am unable to tell you _where_ exactly it
>breaks.
>
>I've been unable to boot _any_ 2.3/2.4 kernels on my machine since
>around 2.3.99 or a bit earlier. Some revisions would boot part of the
>time, but most of them not at all. Symtom is always the same: hang
>before initializing the framebuffer, i.e. still on the OF screen.
>
>I get the 'retunring 0x... from prom_init' string, but nothing after
>that.....

That's weird ? I suppose you tried removing/moving PCI cards ?

You can also try to hack printk so that it calls prom_prinf (or xmon_printf),
that may help figure out where it goes wrong.

Ben.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: 2.4.2 USB and "mon>" (was Re: All 6 cards!!!)

[Benjamin Herrenschmidt]

>Yes, it helps a lot. The USB mouse now works in X. Attached are
>several (perhaps) pertinent records. There are no more USB errors in
>dmesg, lspci now shows a believable interrupt (IRQ 23). I've also
>attached lsprop, I'm not sure how to interpret it...
>
>Thanks for all the help. Awaiting the discussion. Posted to the
>dev-list also, hope that's OK with everybody...
>

Everything looks fine.

I'll push either that patch or a cleaner version to the bk tree
asap.

Ben.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: 2.4 not booting on 7600 (was: Re: 2.4.2 USB and "mon>")

[Michel Lanners]

Hi all,

On   7 Mar, this message from Benjamin Herrenschmidt echoed through cyberspace:
>>I've been unable to boot _any_ 2.3/2.4 kernels on my machine since
>>around 2.3.99 or a bit earlier. Some revisions would boot part of the
>>time, but most of them not at all. Symtom is always the same: hang
>>before initializing the framebuffer, i.e. still on the OF screen.

I should have added that there are some 2.4 kernels that _did_ boot
reliably: benh's 2.5 rsync tree (that's now dead, right?).

>>I get the 'retunring 0x... from prom_init' string, but nothing after
>>that.....
>
> That's weird ? I suppose you tried removing/moving PCI cards ?

No, because I have no reason to suspect a PCI card problem. I never had
those; I had non-functional cards because of the Io port trouble; but
never did any PCI problem lock up the box. Especially not that early in
the boot process....

But than again, I have a Matrox Millenium and a Promise IDE controller
in there; I could try removing the Matrox and see..

Also, this box has a G3 upgrade card, and seems to be weird in some
respect. I seem to be the only ne that couldn't boot from the internal
(MESH) bus with one specific hard disk; slowing the processor through
ICTC solved that problem....

> You can also try to hack printk so that it calls prom_prinf (or xmon_printf),
> that may help figure out where it goes wrong.

I'll get back to debugging. However, from my last tries in
November/December, I remember it hanging somewhere in the early stages
of init/main.c, in one of these files (this is from the patch with my
debuggiong printk's):

arch/ppc/kernel/pmac_pic.c
arch/ppc/kernel/pmac_time.c
arch/ppc/mm/init.c

This is the relevant part in init/main.c:

        lock_kernel();
        printk(linux_banner);
        setup_arch(&command_line);
+if ( ppc_md.progress ) ppc_md.progress("main: setup_arch done", 0x3eab);
        printk("Kernel command line: %s\n", saved_command_line);
+if ( ppc_md.progress ) ppc_md.progress("main: 1", 0x3eab);
        parse_options(command_line);
+if ( ppc_md.progress ) ppc_md.progress("main: 2", 0x3eab);
        trap_init();
+if ( ppc_md.progress ) ppc_md.progress("main: 3", 0x3eab);
        init_IRQ();
+if ( ppc_md.progress ) ppc_md.progress("main: 4", 0x3eab);
        sched_init();
+if ( ppc_md.progress ) ppc_md.progress("main: 5", 0x3eab);
        time_init();
+if ( ppc_md.progress ) ppc_md.progress("main: 6", 0x3eab);
        softirq_init();
+if ( ppc_md.progress ) ppc_md.progress("main: 7", 0x3eab);

Also, I've found that it would lock up at _different_ stages in early
boot, not at one specific step.

This led me to conclude that 2.4 kernels do something different in early
processor, memory or cache setup, which _may_ break something else
somewhere later.

But I'll try again and do some more debugging. Also, I'll try a boot
with the original 604/132 processor, to see whether that makes any
difference.

For the record, tried the latest bk tree yesterday evening: same hang.


Michel

-------------------------------------------------------------------------
Michel Lanners                 |  " Read Philosophy.  Study Art.
23, Rue Paul Henkes            |    Ask Questions.  Make Mistakes.
L-1710 Luxembourg              |
email   mlan@cpu.lu            |
http://www.cpu.lu/~mlan        |                     Learn Always. "


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/