From: "Tony.LI" <1890545@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1890545] Re: (ARM64) qemu-x86_64+schroot(Debian bullseye) can't run chrome and can't load HTML
Date: Wed, 19 Aug 2020 01:24:51 -0000 [thread overview]
Message-ID: <159780029108.2865.14096545580952605253.malone@chaenomeles.canonical.com> (raw)
In-Reply-To: 159670025270.3099.13280483088179052036.malonedeb@gac.canonical.com
Now, I found something new when I use gdb:
=> 0x400523c858: ud2
0x400523c85a: pushq $0xd
0x400523c85c: mov -0x230(%rbp),%rax
0x400523c863: mov -0x240(%rbp),%rdi
0x400523c86a: mov $0x1,%esi
0x400523c86f: movq $0x0,-0x230(%rbp)
0x400523c87a: mov %rax,-0x220(%rbp)
0x400523c881: callq 0x40051ccf00
0x400523c886: callq 0x400266c540
0x400523c88b: cmp $0x1,%eax
0x400523c88e: je 0x400523c8ed
0x400523c890: lea -0x220(%rbp),%rdi
0x400523c897: callq 0x40040fe8e0
0x400523c89c: jmpq 0x400523c60c
0x400523c8a1: int3
0x400523c8a2: ud2
0x400523c8a4: pushq $0x10
0x400523c8a6: int3
0x400523c8a7: ud2
0x400523c8a9: pushq $0x11
0x400523c8ab: mov -0x200(%rbp),%rax
0x400523c8b2: lea -0x1c0(%rbp),%rbx
0x400523c8b9: movq $0x0,-0x200(%rbp)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1890545
Title:
(ARM64) qemu-x86_64+schroot(Debian bullseye) can't run chrome and
can't load HTML
Status in QEMU:
New
Bug description:
First I creat a file system that is debian(bullseye amd64)on arm64
machine,then I download google-chrome,however, when I ran Google
browser, some errors occurred.
$ google-chrome --no-sandbox
or
$ qemu-x86_64-static google-chrome --no-sandbox
qemu: uncaught target signal 5 (Trace/breakpoint trap) - core dumped
qemu: uncaught target signal 5 (Trace/breakpoint trap) - core dumped
[1661:1661:0806/074307.502638:ERROR:nacl_fork_delegate_linux.cc(323)] Bad NaCl helper startup ack (0 bytes)
[1664:1664:0806/074307.504159:ERROR:nacl_fork_delegate_linux.cc(323)] Bad NaCl helper startup ack (0 bytes)
qemu: uncaught target signal 5 (Trace/breakpoint trap) - core dumped
qemu: uncaught target signal 5 (Trace/breakpoint trap) - core dumped
[1637:1678:0806/074308.337567:ERROR:file_path_watcher_linux.cc(315)] inotify_init() failed: Function not implemented (38)
Fontconfig warning: "/etc/fonts/fonts.conf", line 100: unknown element "blank"
qemu: unknown option 'type=utility'
[1637:1680:0806/074313.598432:FATAL:gpu_data_manager_impl_private.cc(439)] GPU process isn't usable. Goodbye.
qemu: uncaught target signal 5 (Trace/breakpoint trap) - core dumped
Trace/breakpoint trap
Why?
And then I run firefox,it can be opened, but it can't load any web pages and HTML.
I really need help!
Thank.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1890545/+subscriptions
next prev parent reply other threads:[~2020-08-19 1:31 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-06 7:50 [Bug 1890545] [NEW] (ARM64) qemu-x86_64+schroot(Debian bullseye) can't run chrome and can't load HTML Tony.LI
2020-08-10 6:24 ` [Bug 1890545] " Tony.LI
2020-08-10 10:02 ` Tony.LI
2020-08-10 10:12 ` Peter Maydell
2020-08-10 10:24 ` Tony.LI
2020-08-10 10:36 ` Tony.LI
2020-08-10 11:06 ` Alex Bennée
2020-08-10 11:06 ` Alex Bennée
2020-08-11 1:17 ` Tony.LI
2020-08-11 8:41 ` Alex Bennée
2020-08-11 8:41 ` Alex Bennée
2020-08-11 8:58 ` Tony.LI
2020-08-11 10:00 ` Tony.LI
2020-08-11 10:04 ` Tony.LI
2020-08-11 11:13 ` Peter Maydell
2020-08-12 9:56 ` Tony.LI
2020-08-13 7:41 ` Tony.LI
2020-08-14 10:06 ` Tony.LI
2020-08-16 11:23 ` Laurent Vivier
2020-08-17 8:40 ` Tony.LI
2020-08-18 7:46 ` Tony.LI
2020-08-18 7:50 ` Tony.LI
2020-08-19 1:24 ` Tony.LI [this message]
2020-08-19 2:15 ` Tony.LI
2021-04-27 7:27 ` Wind Li
2021-05-13 12:15 ` Thomas Huth
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=159780029108.2865.14096545580952605253.malone@chaenomeles.canonical.com \
--to=1890545@bugs.launchpad.net \
--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.