All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Horton <pdh@colonel-panic.org>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Martin Michlmayr <tbm@cyrius.com>, linux-mips@linux-mips.org
Subject: Re: Crash on Cobalt with CONFIG_SERIO=y
Date: Sat, 21 Jan 2006 01:04:55 +0000	[thread overview]
Message-ID: <20060121010455.GC3514@colonel-panic.org> (raw)
In-Reply-To: <20060120144710.GA30415@linux-mips.org>

On Fri, Jan 20, 2006 at 03:47:10PM +0100, Ralf Baechle wrote:
> On Fri, Jan 20, 2006 at 12:42:08AM +0000, Martin Michlmayr wrote:
> 
> > I get the following crash on Cobalt when CONFIG_SERIO=y is set.
> > I realize that this option is not really necessary on Cobalt but the
> > kernel should neverless not crash if it is enabled.
> > 
> > 
> >  Activating ISA DMA hang workarounds.
> >  rtc: Digital UNIX epoch (1952) detected
> >  Real Time Clock Driver v1.12a
> >  Cobalt LCD Driver v2.10
> >  i8042.c: i8042 controller self test timeout.
> >  Unhandled kernel unaligned access[#1]:
> 
> The i8042 error message is a little surprising.  The Cobalt boards afair
> have some sort of SuperIO chip on the board which includes PS/2 keyboard
> even though that has not been wired.  I wonder if anybody can take a
> look at the board what type of SuperIO is there?
> 

No SuperIO, but there is a bog standard VIA PCI-ISA bridge which
contains a bog standard PS/2 keyboard controller, which you would have
thought should just work ...

P.

  parent reply	other threads:[~2006-01-21  1:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-20  0:42 Crash on Cobalt with CONFIG_SERIO=y Martin Michlmayr
2006-01-20 14:47 ` Ralf Baechle
2006-01-20 15:02   ` Martin Michlmayr
2006-01-21  1:04   ` Peter Horton [this message]
2006-02-28 16:54     ` Martin Michlmayr
2006-03-01 22:40       ` Peter Horton
2006-03-01 23:14         ` Martin Michlmayr

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=20060121010455.GC3514@colonel-panic.org \
    --to=pdh@colonel-panic.org \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.org \
    --cc=tbm@cyrius.com \
    /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.