linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Unruh <unruh@physics.ubc.ca>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>, Jiang Liu <liuj97@gmail.com>,
	linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
	bugzilla-daemon@bugzilla.kernel.org
Subject: Re: [Bug 43331] Re: Bug on bootup of Linux kernel on Panasonic Toughbook S10
Date: Sat, 7 Jul 2012 00:22:24 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.1207070017440.13732@info> (raw)
In-Reply-To: <CAE9FiQV5DHZoeXf-bSfuYGUSzmwtdVqGNfhHh7LJ3LBax++Rig@mail.gmail.com>

On Fri, 6 Jul 2012, Yinghai Lu wrote:
>
> so try get one update bios that could return resource for root bus.
>
> or you could try to live with booting with pci=nocrs before your get new BIOS.

Where would I get a new BIOS ? Has Panasonic released a bios update for this
machine that fixes this problem?

I guess the other possibility is to live with the error message, or is this
error part of the reason why my machine has such bad battery use? (less than 
1/2 the time that Windows gets on the same machine).

  reply	other threads:[~2012-07-07  7:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.64.1205311412210.11510@info>
2012-06-01 15:47 ` [Bug 43331] Re: Bug on bootup of Linux kernel on Panasonic Toughbook S10 Bjorn Helgaas
2012-06-01 16:22   ` Bill Unruh
2012-06-02  3:30     ` Jiang Liu
2012-07-06 18:06       ` Bjorn Helgaas
2012-07-06 23:37         ` Bill Unruh
2012-07-07  0:55           ` Yinghai Lu
2012-07-07  7:22             ` Bill Unruh [this message]
2012-07-07 19:02               ` Yinghai Lu
2012-07-09 17:26                 ` Bjorn Helgaas
2012-07-07 13:41             ` Bjorn Helgaas
2012-06-01 17:04   ` Bill Unruh

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=Pine.LNX.4.64.1207070017440.13732@info \
    --to=unruh@physics.ubc.ca \
    --cc=bhelgaas@google.com \
    --cc=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=liuj97@gmail.com \
    --cc=yinghai@kernel.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;
as well as URLs for NNTP newsgroup(s).