Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Giuseppe Sacco <giuseppe@eppesuigoccas.homedns.org>
To: linux-mips@linux-mips.org
Subject: Re: 2.6.24-rc1 does not boot on SGI
Date: Mon, 10 Dec 2007 12:58:49 +0100	[thread overview]
Message-ID: <1197287929.17265.6.camel@scarafaggio> (raw)
In-Reply-To: <1194281699.4192.3.camel@casa>

I reply to my own message, providing more details, hoping that anyone
here could give a hint or the solution.

During bootup on ip32, since 2.4.24-rc1, the system loop printing a
message about unexpected interrupt #13. (see transcript below.)

I enabled more debug in the kernel, and studied the code. What I
understood is that interrupt #13 from CRIME means that the system should
check on MACEISA for the real interrupt.

The interrupt start appearing just after executing the code
psmouse_init() that enable ps2 drivers for keyboard and mouse. Keyboard
interrupt #49 is enabled first and mouse interrupt #51 is enabled later.

When initialising the keyboard interrupt (it is a MACEISA interrupt),
the interrupt start appearing, so I am pretty sure that interrupt #13 is
related to the keyboard interrupt.

When the system receive interrupt #13, it correctly detect it is a
MACEISA interrupt, and check for mace->perif.ctrl.istat value. The
problem seems to be that this value is zero instead of having bit #9 on
(that would mean, interrupt #49, keyboard).

So, either the interrupt #49 is not correctly enabled, or maceisa
interrupt aren't correctly checked.

Does this description ring a bell to anyone?

Bye,
Giuseppe

Calling initcall 0xffffffff80496ca0: serport_init+0x0/0x48()
initcall 0xffffffff80496ca0: serport_init+0x0/0x48() returned 0.
initcall 0xffffffff80496ca0 ran for 0 msecs: serport_init+0x0/0x48()
Calling initcall 0xffffffff80496ce8: maceps2_init+0x0/0xe0()
initcall 0xffffffff80496ce8: maceps2_init+0x0/0xe0() returned 0.
initcall 0xffffffff80496ce8 ran for 1 msecs: maceps2_init+0x0/0xe0()
Calling initcall 0xffffffff80496dc8: serio_raw_init+0x0/0x18()
initcall 0xffffffff80496dc8: serio_raw_init+0x0/0x18() returned 0.
initcall 0xffffffff80496dc8 ran for 1 msecs: serio_raw_init+0x0/0x18()
Calling initcall 0xffffffff80496f40: mousedev_init+0x0/0xd0()
mice: PS/2 mouse device common for all mice
initcall 0xffffffff80496f40: mousedev_init+0x0/0xd0() returned 0.
initcall 0xffffffff80496f40 ran for 16 msecs: mousedev_init+0x0/0xd0()
Calling initcall 0xffffffff80497010: atkbd_init+0x0/0x18()
initcall 0xffffffff80497010: atkbd_init+0x0/0x18() returned 0.
initcall 0xffffffff80497010 ran for 0 msecs: atkbd_init+0x0/0x18()
Calling initcall 0xffffffff80497028: psmouse_init+0x0/0x90()
maceisa enable: 49
crime_int 00000020 enabled
*irq 13, crime_int=00002000, crime_mask=003003a0, mace_int=00000000*
irq 13, desc: ffffffff80448390, depth: 1, count: 0, unhandled: 0
->handle_irq():  ffffffff80065eb0, handle_bad_irq+0x0/0x2c0
->chip(): ffffffff8043e320, 0xffffffff8043e320
->action(): 0000000000000000
  IRQ_DISABLED set

  reply	other threads:[~2007-12-10 11:58 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-27  7:07 2.4.24-rc1 does not boot on SGI Giuseppe Sacco
2007-10-27  7:12 ` 2.6.24-rc1 does not boot on SGI [was: 2.4.24-rc1 does not boot on SGI] Giuseppe Sacco
2007-10-28 15:07 ` 2.4.24-rc1 does not boot on SGI Atsushi Nemoto
2007-10-28 19:17   ` 2.6.24-rc1 does not boot on SGI [was: Re: 2.4.24-rc1 does not boot on SGI] Giuseppe Sacco
2007-10-29 15:06     ` Ralf Baechle
2007-11-05 13:15       ` 2.6.24-rc1 does not boot on SGI Giuseppe Sacco
2007-11-05 16:54         ` Giuseppe Sacco
2007-12-10 11:58           ` Giuseppe Sacco [this message]
2007-12-10 18:05             ` Ricardo Mendoza
2007-12-11  5:35               ` Giuseppe Sacco
2007-12-11 11:04               ` Still no 2.6.24 on ip32 [was: Re: 2.6.24-rc1 does not boot on SGI] Giuseppe Sacco
2007-12-11 13:26                 ` Ricardo Mendoza
2007-12-11 20:44                   ` Giuseppe Sacco
2007-12-11 17:18                     ` Ricardo Mendoza
2007-12-15 20:07                       ` Still no 2.6.24 on ip32 Giuseppe Sacco
2007-10-30  8:31 ` 2.4.24-rc1 does not boot on SGI Martin Michlmayr
2007-10-30  8:41   ` Giuseppe Sacco
2007-10-30  9:09     ` Martin Michlmayr
2007-10-30  9:27       ` Giuseppe Sacco
2007-10-30 11:20     ` J. Scott Kasten
2007-10-30 11:41       ` Giuseppe Sacco
2007-10-30 13:09         ` J. Scott Kasten
2007-10-30  9:09   ` Martin Michlmayr
2007-10-30 12:48   ` Ralf Baechle

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=1197287929.17265.6.camel@scarafaggio \
    --to=giuseppe@eppesuigoccas.homedns.org \
    --cc=linux-mips@linux-mips.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox