linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Olaf Hering <olh@suse.de>
Cc: linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>
Subject: Re: common config fails to open /dev/console
Date: Wed, 12 Nov 2003 13:00:15 +1100	[thread overview]
Message-ID: <1068602414.13217.25.camel@gaston> (raw)
In-Reply-To: <20031111211016.GA9623@suse.de>


On Wed, 2003-11-12 at 08:10, Olaf Hering wrote:
> I got this oops with the attached config. it dies in init_dev() because
> driver->ttys contains NULL.
>
> sys_open -> filp_open -> dentry_open -> chrdev_open -> tty_open -> init_dev
>
> maybe pmac_zilog doesnt play well together with the 8250, or it doesnt
> initalize everything correctly.

Sure, pmac_zilog doesn't play well with 8250, but shouldn't cause such
a crash. What machine is it btw ? Can you send me a fix for pmac_feature
not detecting the model properly ?

Ben.


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

  reply	other threads:[~2003-11-12  2:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-11 21:10 common config fails to open /dev/console Olaf Hering
2003-11-12  2:00 ` Benjamin Herrenschmidt [this message]
2003-11-12  8:00   ` Olaf Hering

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=1068602414.13217.25.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=olh@suse.de \
    /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;
as well as URLs for NNTP newsgroup(s).