From: Thomas Gleixner <tglx@linutronix.de>
To: Ondrej Zary <linux@zary.sk>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: IOPL emulation breaks hpasmd (hp-health) needed by HP DL380 G4 servers
Date: Thu, 16 Sep 2021 23:25:17 +0200 [thread overview]
Message-ID: <87h7ek9ps2.ffs@tglx> (raw)
In-Reply-To: <202109162227.17415.linux@zary.sk>
On Thu, Sep 16 2021 at 22:27, Ondrej Zary wrote:
> On Thursday 16 September 2021 19:09:31 Thomas Gleixner wrote:
>> Can you please run that failing program with GDB and figure out which
>> instruction causes #GP and what the register content is.
>
> (gdb) run
> Starting program: /opt/hp/hp-health/bin/IrqRouteTbl
>
> Program received signal SIGSEGV, Segmentation fault.
> 0xf7fc509b in ?? ()
> (gdb) bt
> #0 0xf7fc509b in ?? ()
> #1 0x08048848 in ?? ()
> #2 0x08048aa1 in ?? ()
> #3 0x08048e05 in ?? ()
> #4 0xf7df9e46 in __libc_start_main () from /lib32/libc.so.6
> #5 0xf7ffd000 in ?? () from /lib/ld-linux.so.2
> Backtrace stopped: previous frame inner to this frame (corrupt stack?)
> (gdb) x/3i $pc
> => 0xf7fc509b: cli
> 0xf7fc509c: push %ebp
> 0xf7fc509d: mov %esp,%ebp
>
> OMG, maybe is it calling into the mmapped BIOS area?
Pretty much so. From your initial report:
openat(AT_FDCWD, "/dev/mem", O_RDWR) = 3
mmap2(NULL, 8342, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_SHARED, 3, 0xf0000) = 0xf7fc1000
close(3) = 0
iopl(3) = 0
--- SIGSEGV {si_signo=SIGSEGV, si_code=SI_KERNEL, si_addr=NULL} ---
offset 0xf0000 of /dev/mem is clearly the BIOS area. Daft.
That's really qualiteee stuff.
Thanks,
tglx
prev parent reply other threads:[~2021-09-16 21:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 12:23 IOPL emulation breaks hpasmd (hp-health) needed by HP DL380 G4 servers Ondrej Zary
2021-09-16 17:09 ` Thomas Gleixner
2021-09-16 20:27 ` Ondrej Zary
2021-09-16 21:05 ` Peter Zijlstra
2021-09-17 8:11 ` Ondrej Zary
2021-09-17 9:20 ` [PATCH] x86/iopl: Fake iopl(3) CLI/STI usage Peter Zijlstra
2021-09-17 10:29 ` Ondrej Zary
2021-09-17 11:54 ` Peter Zijlstra
2021-09-17 12:33 ` Thomas Gleixner
2021-09-17 12:54 ` Ondrej Zary
2021-09-17 10:40 ` Thomas Gleixner
2021-09-17 22:23 ` Linus Torvalds
2021-09-17 22:24 ` Linus Torvalds
2021-09-18 7:05 ` Peter Zijlstra
2021-09-18 9:06 ` Peter Zijlstra
2021-09-18 15:53 ` Ondrej Zary
2021-09-18 16:35 ` Linus Torvalds
2021-09-21 7:28 ` [tip: x86/core] " tip-bot2 for Peter Zijlstra
2021-09-21 11:09 ` Ondrej Zary
2021-09-21 12:00 ` Peter Zijlstra
2021-09-21 17:31 ` Ondrej Zary
2021-09-21 12:41 ` tip-bot2 for Peter Zijlstra
2021-09-21 21:01 ` [PATCH] " Andy Lutomirski
2021-09-16 21:25 ` Thomas Gleixner [this message]
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=87h7ek9ps2.ffs@tglx \
--to=tglx@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@zary.sk \
--cc=x86@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