From: Richard Weinberger <richard@nod.at>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: user-mode-linux-devel@lists.sourceforge.net,
Christoph Hellwig <hch@lst.de>,
linux-kernel@vger.kernel.org
Subject: Re: Fwd: Re: UML kernel crash of v2.6.36-rcX kernel
Date: Fri, 15 Oct 2010 19:46:53 +0200 [thread overview]
Message-ID: <201010151946.53402.richard@nod.at> (raw)
In-Reply-To: <201010151133.38170.toralf.foerster@gmx.de>
Hi!
Can you please post more details.
What exactly causes the crash?
phpsysinfo does a lot of stuff.
On my test bed it works fine.
Am Freitag 15 Oktober 2010, 11:33:37 schrieben Sie:
> Hello,
>
> git bisect gave :
>
> tfoerste@n22 ~/devel/linux-2.6 $ git bisect bad
> 365b18189789bfa1acd9939e6312b8a4b4577b28 is the first bad commit
> commit 365b18189789bfa1acd9939e6312b8a4b4577b28
> Author: Christoph Hellwig <hch@lst.de>
> Date: Wed Jul 7 18:53:25 2010 +0200
>
> add f_flags to struct statfs(64)
>
> Add a flags field to help glibc implementing statvfs(3) efficiently.
>
> We copy the flag values from glibc, and add a new ST_VALID flag to
> denote that f_flags is implemented.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
>
> :040000 040000 92f04bf96f0c6bb2df3ddea83a4a27c35985bdcc
>
> e702d8dd95a3897e085bf3fe4919e2dd30a57b47 M arch
>
> :040000 040000 5705bba0e9a2a61112281f7bb1a1030ef9eb337e
>
> 34fc3ea912581ae7923a15246291387bfc354e47 M fs
>
> :040000 040000 578a5bb0743aa85adfec7a25f82d440b2ea4db27
>
> 7e96f95b6f1d6ccc9e004b560670638db66b8a93 M include
>
>
> BTW is UML dead ?
> (I'm asking b/c there're so many different issues - compile errors or the
> UML kernel crashes during start or during shutdown, independent of the
> result of the wget issue I was investigating - there are 120 skip'ed
> commits within the git bisect log beside 46 good and 15 bad commits and I
> didn't saw any chance to fully automate the bisect)
Hmm, I did a lot git bisects on UML 2.6.35 to 2.6.36.
2.6.36-rc1 does not always compile. You need no apply f3c072a first.
I've not seen any crashes during bootup nor shutdown. Can you provide some
more details?
Thanks,
//richard
next prev parent reply other threads:[~2010-10-15 17:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-13 11:28 Toralf Förster
2010-10-15 9:33 ` Toralf Förster
2010-10-15 17:46 ` Richard Weinberger [this message]
2010-10-16 8:55 ` Toralf Förster
2010-10-16 11:12 ` Richard Weinberger
2010-10-17 13:55 ` Toralf Förster
2010-10-17 20:18 ` Christoph Hellwig
2010-10-18 8:43 ` Toralf Förster
2010-10-18 8:48 ` richard -rw- weinberger
2010-10-18 9:08 ` Geert Uytterhoeven
2010-10-18 9:05 ` Toralf Förster
2010-10-18 9:09 ` [uml-devel] " Geert Uytterhoeven
2010-10-18 9:16 ` richard -rw- weinberger
2010-10-18 9:31 ` richard -rw- weinberger
2010-10-18 11:14 ` Toralf Förster
2010-10-18 11:22 ` Richard Weinberger
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=201010151946.53402.richard@nod.at \
--to=richard@nod.at \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=toralf.foerster@gmx.de \
--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
Powered by JetHome