mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Malte Cornils <malte@cornils.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Lenovo ThinkCentre A55: parport_pc 00:0a: disabled;  probe of 00:0a failed with error -22
Date: Wed, 11 Jun 2008 22:26:44 -0600	[thread overview]
Message-ID: <200806112226.44596.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <1213221122.20453.26.camel@localhost>

On Wednesday 11 June 2008 3:52:01 pm Malte Cornils wrote:
> a friend of mine is unable to print on her system. I could trace that to
> the kernel not finding the parallel port on the system. Windows Vista,
> for whatever that's worth, prints fine.
>
> dmesg says:
> [   40.935843] parport_pc 00:0a: disabled
> [   40.935850] parport_pc: probe of 00:0a failed with error -22
>
> rmmod parport_pc ; modprobe parport_pc io=0x378 irq=none
> did not work either, the detection failed and echoing some bytes to
> the /dev/lp0 device fails, too.
>
> Booting with noapic or pci=routeirq did not help, booting with noacpi
> nolapic generated in the system grinding to a halt, which made getting
> information out of it difficult due to the remote telephone debugging.

There are some known PNPACPI problems that affect parport_pc.
You could try booting with "pnpacpi=off", which should cause
us to use PNPBIOS instead.

It would be very useful if you could build a current -mm tree
with CONFIG_PNP_DEBUG turned on and collect the dmesg log.  That
tree has the known PNPACPI problems fixed, so it *might* fix the
problem you're seeing.  And if not, the debug output might have
more clues.

Bjorn


      parent reply	other threads:[~2008-06-12  4:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-11 21:52 Malte Cornils
2008-06-11 22:27 ` Malte Cornils
2008-06-12  4:26 ` Bjorn Helgaas [this message]

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=200806112226.44596.bjorn.helgaas@hp.com \
    --to=bjorn.helgaas@hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=malte@cornils.net \
    /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

all inboxes | Powered by JetHome®