The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Adam Belay <ambx1@neo.rr.com>
To: CaT <cat@zip.com.au>
Cc: greg@kroah.com, linux@brodo.de, Tamagucci@libero.it,
	alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org
Subject: Re: 2.5.45 / boottime oops (pnp bios I think)
Date: Mon, 4 Nov 2002 21:24:44 +0000	[thread overview]
Message-ID: <20021104212444.GH316@neo.rr.com> (raw)
In-Reply-To: <20021105020630.GA644@zip.com.au>

On Tue, Nov 05, 2002 at 01:06:30PM +1100, CaT wrote:
> On Mon, Nov 04, 2002 at 08:28:00PM +0000, Adam Belay wrote:
> > occured when the pnp bios protocol reached node 0x13.  This node, pnp id
> > PNP0f13, is of course a standard mouse port.  If you look at the output of 
> > lspnp for my system, the following can be seen.
> > 
> > 12 PNP0f13 input device: mouse
> >     flags: [no disable] [no config] [static]
> >     allocated resources:
> > 	irq 12 [high edge]
>
> Mine is #13 (ie the first line reads 13 PNP0f13...)
>
> > Please feel free to send any questions or comments.  The patch is below.
>
> The patch lets me boot just fine. (Woo) One hassle though, doing
> lspci -v 13 or cat /proc/bus/pnp/13 causes an oops. I presume it's the
> same deal as what you were talking about?
>

Oops, I forgot to fix the pnpbios proc interface for this problem.  I have
to look into it some more.  None the less this is not a big problem.  If
it boots you're in good shape.

Could you, however send me the output of lspnp for /proc/bus/pnp/boot/13.
This will not fault.  Also could you try lspnp on /proc/bus/pnp/14.  If
all is well this one should not fault.

by the way

/proc/bus/pnp/*.* = current
/proc/bus/pnp/boot/*.* = boot

current config has the problem but boot does not.  I'll work on a patch to
fix this.

Thanks,
Adam

  reply	other threads:[~2002-11-05  2:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-04  2:54 2.5.45 / boottime oops (pnp bios I think) CaT
2002-11-04 13:05 ` Alan Cox
2002-11-04 13:46   ` CaT
2002-11-04 14:21     ` Alan Cox
2002-11-07 14:33   ` David Woodhouse
2002-11-07 14:51     ` Dave Jones
2002-11-07 14:55       ` David Woodhouse
2002-11-07 15:46         ` Dave Jones
2002-11-07 15:50           ` David Woodhouse
2002-11-07 15:54         ` Brian Gerst
2002-11-04 16:15 ` Adam Belay
2002-11-04 23:54   ` CaT
2002-11-04 20:28     ` Adam Belay
2002-11-05  2:06       ` CaT
2002-11-04 21:24         ` Adam Belay [this message]
2002-11-05  2:29           ` CaT

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=20021104212444.GH316@neo.rr.com \
    --to=ambx1@neo.rr.com \
    --cc=Tamagucci@libero.it \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=cat@zip.com.au \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@brodo.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