mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: grfgguvf@gmail.com
To: linux-kernel@vger.kernel.org
Cc: acpi-devel@lists.sourceforge.net, willy@debian.org
Subject: Re: Invalid PBLK length for athlon XP-M on Asus laptop
Date: Tue, 17 Oct 2006 23:00:51 +0200	[thread overview]
Message-ID: <8413367b0610171400j2ae2c7b1p9f193d5e33e58581@mail.gmail.com> (raw)

In-Reply-To: <20030823173423.GQ18834@parcelfarce.linux.theplanet.co.uk>
References: <20030823173423.GQ18834@parcelfarce.linux.theplanet.co.uk>,
<20030823125812.GC913@renditai.milesteg.arr>
Newsgroups: linux.kernel

On Aug 23 2003, 7:42 pm, Matthew Wilcox <willy@debian.org> wrote:
> On Sat, Aug 23, 2003 at 02:58:12PM +0200, Daniele Venzano wrote:
> > I checked
> > dmesg with acpi debugging turned on (full dmesg is attached), and I
> > found these:
> >
> > [...]
> > ACPI: Fan [FAN0] (on)
> > acpi_processor-1626 [30] acpi_processor_get_inf: Invalid PBLK length [5]
>
> This is a bug in your ACPI bios, you need a vendor update.  We tried
> fixing this but it broke a number of laptops, so we had to revert it.

And years later... I just got this "Invalid PBLK length [5]" error
message as well, first time ever, when first booting 2.6.18. I never
got it with 2.6.17 or any earlier kernel. My BIOS or any settings
didn't change.

Now this is a desktop so ACPI is not very important to me but is this
possibly a regression?

> --
> "It's not Hollywood.  War is real, war is primarily not about defeat or
> victory, it is about death.  I've seen thousands and thousands of dead bodies.
> Do you think I want to have an academic debate on this subject?" -- Robert Fisk

-- Grifeg

             reply	other threads:[~2006-10-17 21:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-17 21:00 grfgguvf [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-08-23 12:58 Daniele Venzano

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=8413367b0610171400j2ae2c7b1p9f193d5e33e58581@mail.gmail.com \
    --to=grfgguvf@gmail.com \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=willy@debian.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

all inboxes | Powered by JetHome®