From: Antoine Martin <antoine@nagafix.co.uk>
To: "Christopher S. Aker" <caker@theshore.net>
Cc: Blaisorblade <blaisorblade@yahoo.it>,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] UML/64bit is miscompiled by gcc 4.0.3 on Ubuntu 6.06 LTS
Date: Wed, 17 Jan 2007 18:15:28 +0000 [thread overview]
Message-ID: <45AE67C0.5080003@nagafix.co.uk> (raw)
In-Reply-To: <45AE684D.7070802@theshore.net>
>> ptrace(PTRACE_SETREGS, 31586, 0, 0x6096dac8) = 0
>> ptrace(PTRACE_SETFPREGS, 31586, 0, 0x6096dba0) = 0
>> ptrace(PTRACE_SYSCALL, 31586, 0, SIG_0) = 0
>>
>> I'll have to verify whether some code in the stubs is miscompiled. But not
>> until... well, I dunno when I'll be back...
>>
>> Anybody else with the same problem?
>
>
> Isn't this is the same problem we discussed a few months back? What
> I've discovered since then is this is a regression introduced after
> 2.6.16 on the _host_. Any post-2.6.16 host kernel, either skas v8.2 or
> v9.pre causes Ubuntu (and other distros, I believe) to hang after "VFS
> mounting root".
>
> http://marc.theaimsgroup.com/?l=user-mode-linux-devel&m=116008558424368&w=2
> http://marc.theaimsgroup.com/?l=user-mode-linux-devel&m=116711159414443&w=2
Indeed it is.
A fix would be more than welcome. (2.6.16 is a bit dated)
I believe a lot of users are hitting this bug now too (and it is a
regression) as a lot of distros ship recent kernels.
Another regression in 2.6.16 (or later?) is the inability to run 32-bit
guests on 64-bit hosts (the same binaries that used to work before -
statically compiled). The boot stops very early during the "checking
ptrace" step.
Antoine
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2007-01-17 18:39 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-17 16:15 [uml-devel] UML/64bit is miscompiled by gcc 4.0.3 on Ubuntu 6.06 LTS Blaisorblade
2007-01-17 18:17 ` Christopher S. Aker
2007-01-17 18:15 ` Antoine Martin [this message]
2007-01-17 19:50 ` Antoine Martin
2007-01-19 11:00 ` [uml-devel] buggy UML AMD64? Antoine Martin
2007-01-19 16:07 ` Daniel Gryniewicz
2007-01-19 16:14 ` Antoine Martin
2007-01-19 16:38 ` Daniel Gryniewicz
2007-01-19 16:42 ` Antoine Martin
2007-01-19 17:33 ` Antoine Martin
2007-01-19 19:56 ` Antoine Martin
2007-01-21 9:17 ` Boaz Harrosh
2007-01-21 13:04 ` Antoine Martin
2007-01-23 15:20 ` Boaz Harrosh
2007-01-21 14:38 ` Joel Palmius
2007-01-21 14:46 ` Antoine Martin
2007-01-21 14:55 ` Joel Palmius
2007-01-21 16:11 ` Joel Palmius
2007-01-22 22:09 ` Jeff Dike
2007-01-23 0:59 ` Antoine Martin
2007-01-19 16:38 ` Antoine Martin
2007-02-15 3:43 ` [uml-devel] UML/64bit is miscompiled by gcc 4.0.3 on Ubuntu 6.06 LTS Blaisorblade
2007-01-19 23:31 ` Blaisorblade
2007-01-17 23:26 ` Jeff Dike
2007-01-19 23:18 ` Blaisorblade
2007-01-22 20:59 ` Jeff Dike
2007-01-23 8:09 ` Blaisorblade
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=45AE67C0.5080003@nagafix.co.uk \
--to=antoine@nagafix.co.uk \
--cc=blaisorblade@yahoo.it \
--cc=caker@theshore.net \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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