From: "Alexander Beregalov" <a.beregalov@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>,
Kernel Testers List <kernel-testers@vger.kernel.org>
Subject: Re: linux-next: Tree for July 17: early crash on x86-64
Date: Fri, 18 Jul 2008 17:52:23 +0400 [thread overview]
Message-ID: <a4423d670807180652y352e66lfe04d2b33d2ed176@mail.gmail.com> (raw)
In-Reply-To: <200807180106.08328.rjw@sisk.pl>
2008/7/18 Rafael J. Wysocki <rjw@sisk.pl>:
> This one crashes all of my x86-64 test boxes early during boot.
The same problem with next-20080718.
Unfortunatelly I do not have serial console on that host.
next prev parent reply other threads:[~2008-07-18 13:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080718012842.690b8346.sfr@canb.auug.org.au>
2008-07-17 23:06 ` linux-next: Tree for July 17: early crash on x86-64 Rafael J. Wysocki
2008-07-18 13:52 ` Alexander Beregalov [this message]
2008-07-19 3:52 ` Al Viro
[not found] ` <20080719035231.GU28946-3bDd1+5oDREiFSDQTTA3OLVCufUGDwFn@public.gmane.org>
2008-07-19 18:42 ` Rafael J. Wysocki
2008-07-19 19:54 ` James Morris
[not found] ` <Xine.LNX.4.64.0807200553380.22632-RC8Ws/H8zzudju81dFSl6rpzq4S04n8Q@public.gmane.org>
2008-07-20 9:42 ` BUG at security/selinux/avc.c:883 (was: Re: linux-next: Tree for July 17: early crash on x86-64) Thomas Meyer
2008-07-20 12:15 ` Al Viro
2008-07-28 17:32 ` Stephen Smalley
[not found] ` <1217266358.20373.54.camel-/ugcdrsPCSfIm9DtXLC9OUVfdvkotuLY+aIohriVLy8@public.gmane.org>
2008-07-28 21:38 ` James Morris
[not found] ` <Xine.LNX.4.64.0807290736440.30242-RC8Ws/H8zzudju81dFSl6rpzq4S04n8Q@public.gmane.org>
2008-07-29 0:33 ` Al Viro
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=a4423d670807180652y352e66lfe04d2b33d2ed176@mail.gmail.com \
--to=a.beregalov@gmail.com \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).