public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <len.brown@intel.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: Elliot Mackenzie <macka@adixein.com>, linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: Panic booting from USB disk in ioremap.c (line 81)
Date: 26 Feb 2004 03:11:54 -0500	[thread overview]
Message-ID: <1077783113.22401.69.camel@dhcppc4> (raw)
In-Reply-To: <A6974D8E5F98D511BB910002A50A6647615F32F8@hdsmsx402.hd.intel.com>

bootflag.c should not use its own private ACPI table parser/mapper --
this is a bug:

http://bugme.osdl.org/show_bug.cgi?id=1922

Elliot,
If you add your system info to that bug report and volunteer to help
test the fix, I'll be delighted to use your system as an excuse to
address this issue promptly.

thanks,
-Len

ps.
The reason you enter diag mode when SBF is disabled is because w/o SBF,
the BOOTING flag doesn't get cleared, so the BIOS assumes the system
didn't boot correctly and when entered next it is in DIAG mode.  This is
expected.

IMO, module load time is probably too early to clear the BOOTING flag
anyway.  It should be cleared upon completion of successful boot --
though I'm not sure how to identify that point.  Come to think about it,
maybe we should delay clearing the BOOTING flag until Linux initiates a
graceful shutdown, sleep, or reboot?  If the system died b/c of bad RAM
or something, that would make it run through DIAGS when it next enters
POST.



       reply	other threads:[~2004-02-26  8:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <A6974D8E5F98D511BB910002A50A6647615F32F8@hdsmsx402.hd.intel.com>
2004-02-26  8:11 ` Len Brown [this message]
2004-02-29  5:28   ` [PATCH]: PROBLEM: Panic booting from USB disk in ioremap.c (line 81) Elliot Mackenzie
2004-02-21  5:31 Randy.Dunlap
2004-02-22 12:02 ` Elliot Mackenzie
2004-02-26  0:03   ` Randy.Dunlap
  -- strict thread matches above, loose matches on Subject: below --
2004-02-20 15:37 Elliot Mackenzie
2004-02-20 19:30 ` Randy.Dunlap
2004-02-21  0:11   ` Elliot Mackenzie
2004-02-21  0:11     ` Randy.Dunlap
2004-02-21  0:25       ` Elliot Mackenzie
2004-02-21  0:19         ` Randy.Dunlap
2004-02-21  0:36           ` Elliot Mackenzie

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=1077783113.22401.69.camel@dhcppc4 \
    --to=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macka@adixein.com \
    --cc=rddunlap@osdl.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