All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerhard Wiesinger <lists@wiesinger.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] DOS boot problem with LSI 53C895A SCSI controller and LSI option ROM
Date: Mon, 12 Nov 2012 21:53:41 +0100	[thread overview]
Message-ID: <50A161D5.8080005@wiesinger.com> (raw)
In-Reply-To: <50A0B2B1.8050601@redhat.com>

On 12.11.2012 09:26, Paolo Bonzini wrote:
> Il 10/11/2012 22:39, Gerhard Wiesinger ha scritto:
>> Hello,
>>
>> I bisected down a DOS boot problem with LSI 53C895A SCSI controller and
>> LSI option ROM to the following commit:
>> e93176d55f1eb4be1a366b51afeaf4f4c8c31d75
> The emulation is known to be incomplete; the option ROM is not really
> supported, just like the support for the LSI controller in SeaBIOS is
> not meant for real hardware.


The option ROM worked perfect for legacy before this commit for years.

> But if this is a regression, I can look at it.  Problem is, I don't have
> the option ROM and I don't think I can obtain one legally.  Please
> provide at least a trace of the SCSI commands that are sent.

Yes, it is a regression problem.

You can download the option ROM from the LSI homepage:
http://www.lsi.com/support/Pages/Download-Results.aspx?productcode=P00536&assettype=0&component=Storage%20Component&productfamily=0&productname=LSI53C895A
http://www.lsi.com/downloads/Public/Host%20Bus%20Adapters/Host%20Bus%20Adapters%20Common%20Files/lsi_bios.zip
http://www.lsi.com/downloads/Public/SCSI%20HBAs/SCSI%20HBAs%20Common%20Files/lsi_bios.zip
http://www.lsi.com/downloads/Public/SCSI%20ICs%20and%20Expanders/SCSI%20ICs%20and%20Expanders%20Common%20Files/lsi_bios.zip
http://www.lsi.com/downloads/Public/Obsolete/Obsolete%20Common%20Files/lsi_bios.zip

Trace will follow (currently very busy). Best solution to turn it on?

>> BTW: Nearly all KVM coredumps aren't valid anymore and have only a
>> garbage stack trace. Any ideas?
> It seems strange that this would be limited to KVM.  What about other
> programs?  Or try --disable-pie.
>

Looks like a general problem on the FC17 machine with latest updates. 
Was ok 11 days ago on FC17. program below cores, but also no valid core 
dump. Also further information below.

Doesn't look like PIE is active.

Any further hints?

Ciao,
Gerhard

coredump.c:
int main(int argc, char* argv[])
{
   char* p = 0;
   *p = 0;
   return 0;
}

gcc -g coredump.c -o a.out
eu-readelf -h a.out
ELF Header:
   Magic:   7f 45 4c 46 02 01 01 00 00 00 00 00 00 00 00 00
   Class:                             ELF64
   Data:                              2's complement, little endian
   Ident Version:                     1 (current)
   OS/ABI:                            UNIX - System V
   ABI Version:                       0
   Type:                              EXEC (Executable file)
   Machine:                           AMD x86-64
   Version:                           1 (current)
   Entry point address:               0x400390
   Start of program headers:          64 (bytes into file)
   Start of section headers:          3032 (bytes into file)
   Flags:
   Size of this header:               64 (bytes)
   Size of program header entries:    56 (bytes)
   Number of program headers entries: 8
   Size of section header entries:    64 (bytes)
   Number of section headers entries: 35
   Section header string table index: 32

gdb -c core.5671
GNU gdb (GDB) Fedora (7.4.50.20120120-52.fc17)
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Missing separate debuginfo for the main executable file
Try: yum --disablerepo='*' --enablerepo='*-debug*' install 
/usr/lib/debug/.build-id/ff/36de4d6ecfe0c5b80cbc805916d9acc829619e
[New LWP 5671]
Core was generated by `./a.out'.
Program terminated with signal 11, Segmentation fault.
#0  0x00000000004004b3 in ?? ()
(gdb) ba
#0  0x00000000004004b3 in ?? ()
#1  0x0000000000000000 in ?? ()

  reply	other threads:[~2012-11-12 20:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-10 21:39 [Qemu-devel] DOS boot problem with LSI 53C895A SCSI controller and LSI option ROM Gerhard Wiesinger
2012-11-12  8:26 ` Paolo Bonzini
2012-11-12 20:53   ` Gerhard Wiesinger [this message]
2012-11-13 10:50     ` Paolo Bonzini

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=50A161D5.8080005@wiesinger.com \
    --to=lists@wiesinger.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.