public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Elliot Mackenzie" <macka@adixein.com>
To: "'Randy.Dunlap'" <rddunlap@osdl.org>
Cc: "'lkml'" <linux-kernel@vger.kernel.org>
Subject: RE: PROBLEM: Panic booting from USB disk in ioremap.c (line 81)
Date: Sun, 22 Feb 2004 22:02:22 +1000	[thread overview]
Message-ID: <001201c3f93b$bbd94170$4301a8c0@waverunner> (raw)
In-Reply-To: <20040220213157.7da96979.rddunlap@osdl.org>

Randy:

This issue just got a lot weirder but I have some more information.  

This is the weird part:
I applied the patch you suggested, and the system stopped panicking at
that point.  Instead, it just hung for about 10 minutes, eventually
kicking off again and finishing bootup.  To be sure, I then removed the
code and recompiled (clean), and now the original code started doing
that too (without your patch).  To my knowledge I changed nothing (not
even in BIOS), but I rebuilt the kernel again from the raw 2.6.3 source
to be sure - same result.

The interesting part (more information):
If we bypass the bootflag.c code (simply by putting "return 0;" as the
first line), the system will boot normally.  On shutdown we seem to be
getting a system jumping to maintenance mode, but I am not sure if its
related.  It appears you are right in assuming that the problem is
related to the bios sbf rather than the usb.  Doug pointed out to me
that looking through the stack trace, sbf_init is giving an rsdt_length
of something in the order of 1GB, and somehow the checks are not picking
it up.

Since it is now relevant, the BIOS is flashed to the most recent stable
BIOS for the ASUS P4SGX-MX motherboard (1005).

This is the tricky part:
When we bypass the bootflag code, and boot the "working" kernel, I am
able to capture a serial transcript.  However, I have been unsuccessful
in establishing a serial console for the broken 2.6.3 kernel to date.
It's possible I have done something strange while building one of the
kernels, but I am just trying to verify that now.  Are there
alternatives?

Currently the text on screen comes up way to quickly for me to capture,
and since I don't have a working serial console for the broken kernel
yet, I am not able to capture a transcript.  Previously I could just
type to you what I saw, but the kernel is now booting to the same point,
hanging 10 minutes then continuing.

Kind regards,
Elliot.

-----Original Message-----
From: Randy.Dunlap [mailto:rddunlap@osdl.org] 
Sent: Saturday, 21 February 2004 3:32 PM
To: macka@adixein.com
Cc: lkml
Subject: RE: PROBLEM: Panic booting from USB disk in ioremap.c (line 81)


As enumerated below:
| Calling initcall 0xc03f7e19 pcibios_init
| Calling initcall 0xc03f819c netdev_init
| Calling initcall 0xc03f1e7c chr_dev_init
| Calling initcall 0xc03e7084 i8259_init_sysfs
| Calling initcall 0xc03e7101 init_timer_sysfs
| Calling initcall 0xc03e90e2 sbf_init


I still don't see how USB enters into it, but please try the patch
below to see if I'm on the right track or not.
It looks like sbf_init() is finding an invalid ACPI RSDT length field.
This patch will telll us if that's the case or not.

--
~Randy




  reply	other threads:[~2004-02-22 12:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-21  5:31 PROBLEM: Panic booting from USB disk in ioremap.c (line 81) Randy.Dunlap
2004-02-22 12:02 ` Elliot Mackenzie [this message]
2004-02-26  0:03   ` Randy.Dunlap
     [not found] <A6974D8E5F98D511BB910002A50A6647615F32F8@hdsmsx402.hd.intel.com>
2004-02-26  8:11 ` Len Brown
  -- 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='001201c3f93b$bbd94170$4301a8c0@waverunner' \
    --to=macka@adixein.com \
    --cc=linux-kernel@vger.kernel.org \
    --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