From: "Luck, Tony" <tony.luck@intel.com>
To: linux-ia64@vger.kernel.org
Subject: 2.4.21 + 64K pagesize == BOOM
Date: Wed, 03 Sep 2003 18:25:40 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106261419520719@msgid-missing> (raw)
Someone here tried to build a 2.4.21 kernel with 64k
page size, but found that the system reset during boot.
Some tracking showed that the problem was an MCA when
the kernel jumped to 0xf000eef3000c0100. Further tracking
showed that the jump came from probe_hwif(). Here's some
disassembled code (showing just the "br.call" before and
after the fatal jump for context):
e0000000046fb93c: (p03) br.call.dpnt.many b0à000000046fde00 <probe_cmos_for_drives>;;
e0000000046fb96c: br.call.sptk.many b0à000000046fb580 <hwif_check_regions>;;
e0000000046fba7c: br.call.sptk.many b0à00000004476ba0 <printk>;;
e0000000046fbabc: (p17) br.call.dpnt.many b0à0000000440dc20 <disable_irq>;;
e0000000046fbbdc: br.call.sptk.many b0à000000044b5480 <kmalloc>;;
e0000000046fbc1c: br.call.sptk.many b0à00000004476ba0 <printk>
e0000000046fbc8c: br.call.sptk.many b0à000000046fb720 <hwif_register>
e0000000046fbd3c: (p17) br.call.dpnt.many b0à0000000440de00 <enable_irq>;;
e0000000046fbe10: ld8 r19=[r40];; // get 0x0 into r19
e0000000046fbe16: ld8 r18=[r19],8 // get 0xf000eef3000c0100 into r18
e0000000046fbe1c: nop.i 0x0;;
e0000000046fbe20: ld8 r1=[r19]
e0000000046fbe26: mov b7=r18
e0000000046fbe2c: br.call.sptk.many b0·;; // JUMP TO 0xf000eef3000c0100 BOOM!
e0000000046fbe5c: br.call.sptk.many b0·;;
e0000000046fbe8c: br.call.sptk.many b0·;;
e0000000046fbedc: br.call.sptk.many b0à00000004476ba0 <printk>;;
e0000000046fbf0c: br.call.sptk.many b0·;;
e0000000046fbfec: br.call.sptk.many b0·;;
e0000000046fc01c: br.call.sptk.many b0à0000000470f1e0 <ide_delay_50ms>;;
I'm not sure why the dereference 0x0 didn't fault.
Building with CONFIG_BLK_DEV_IDE=n avoids this problem.
Anyone know what's going on here?
-Tony
reply other threads:[~2003-09-03 18:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=marc-linux-ia64-106261419520719@msgid-missing \
--to=tony.luck@intel.com \
--cc=linux-ia64@vger.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