From: Andrew Morton <akpm-3NddpPZAyC0@public.gmane.org>
To: Dane Mutters <dmutters-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: (1) ACPI messes up Parallel support in kernels >2.6.9
Date: Wed, 4 Jan 2006 22:52:09 -0800 [thread overview]
Message-ID: <20060104225209.56e35802.akpm@osdl.org> (raw)
In-Reply-To: <200601042203.12377.dmutters-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Dane Mutters <dmutters-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> I've been attempting to figure out this problem for a long time, and have
> come to the conclusion that it must be a kernel bug (that or perhaps I'm a
> bit dense). Whenever I have the option, "Device Drivers > Plug and Play >
> ACPI Support" enabled, I become unable to print using my parallel port.
hm, regressions are bad and the fact that it _used_ to work meand that we
should be able to make it work again.
Could you please raise a bug reports against acpi at bugzilla.kernel.org?
It might help if that report includes the output of `dmesg -s 1000000' for
both working and non-working kernels.
Thanks.
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next parent reply other threads:[~2006-01-05 6:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200601042203.12377.dmutters@gmail.com>
[not found] ` <200601042203.12377.dmutters-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2006-01-05 6:52 ` Andrew Morton [this message]
[not found] ` <20060104225209.56e35802.akpm-3NddpPZAyC0@public.gmane.org>
2006-01-05 8:55 ` (1) ACPI messes up Parallel support in kernels >2.6.9 Adam Belay
[not found] ` <20060105085559.GA1357-IBH0VoN/3vPQT0dZR+AlfA@public.gmane.org>
2006-01-05 19:20 ` Petr Vandrovec
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=20060104225209.56e35802.akpm@osdl.org \
--to=akpm-3nddppzayc0@public.gmane.org \
--cc=dmutters-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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