From: Borislav Petkov <bp@alien8.de>
To: "Artem S. Tashkinov" <t.artem@lycos.com>
Cc: pavel@ucw.cz, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, security@kernel.org,
linux-media@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: Re: Re: Re: A reliable kernel panic (3.6.2) and system crash when visiting a particular website
Date: Sun, 21 Oct 2012 13:08:51 +0200 [thread overview]
Message-ID: <20121021110851.GA6504@liondog.tnic> (raw)
In-Reply-To: <1798605268.19162.1350784641831.JavaMail.mail@webmail17>
On Sun, Oct 21, 2012 at 01:57:21AM +0000, Artem S. Tashkinov wrote:
> The freeze happens on my *host* Linux PC. For an experiment I decided
> to check if I could reproduce the freeze under a virtual machine - it
> turns out the Linux kernel running under it also freezes.
I know that - but a freeze != oops - at least not necessarily. Which
means it could very well be a different issue now that vbox is gone.
Or, it could be the same issue with different incarnations: with vbox
you get the corruptions and without it, you get the freezes. I'm
assuming you do the same flash player thing in both cases?
Here's a crazy idea: can you try to reproduce it in KVM?
Thanks.
--
Regards/Gruss,
Boris.
next prev parent reply other threads:[~2012-10-21 11:08 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-20 12:06 Artem S. Tashkinov
2012-10-20 16:27 ` Borislav Petkov
2012-10-20 17:41 ` Artem S. Tashkinov
2012-10-20 18:04 ` Borislav Petkov
2012-10-20 20:57 ` Artem S. Tashkinov
2012-10-20 22:00 ` Artem S. Tashkinov
2012-10-20 20:32 ` Pavel Machek
2012-10-20 22:58 ` Borislav Petkov
2012-10-20 23:15 ` Artem S. Tashkinov
2012-10-21 0:24 ` Borislav Petkov
2012-10-21 1:57 ` Artem S. Tashkinov
2012-10-21 11:08 ` Borislav Petkov [this message]
2012-10-21 11:59 ` Artem S. Tashkinov
2012-10-21 12:03 ` Daniel Mack
2012-10-21 12:30 ` Artem S. Tashkinov
2012-10-21 14:21 ` was: " Daniel Mack
2012-10-21 14:57 ` Artem S. Tashkinov
2012-10-21 15:22 ` Daniel Mack
2012-10-21 15:28 ` Alan Stern
2012-10-21 12:12 ` Daniel Mack
2012-10-21 15:23 ` Re: Re: Re: " Alan Stern
2012-10-21 22:20 ` A strange Linux 3.6 bug: corrupted page table Artem S. Tashkinov
2012-10-21 17:03 ` Re: Re: Re: Re: A reliable kernel panic (3.6.2) and system crash when visiting a particular website Borislav Petkov
2012-10-21 19:49 ` Artem S. Tashkinov
2012-10-21 19:54 ` Daniel Mack
2012-10-21 20:43 ` Artem S. Tashkinov
2012-10-21 21:00 ` Daniel Mack
2012-10-21 20:36 ` Re: Re: Re: Re: " Borislav Petkov
2012-10-22 15:17 ` Alan Stern
2012-10-22 15:30 ` Daniel Mack
2012-10-22 15:54 ` Alan Stern
2012-10-22 17:30 ` Artem S. Tashkinov
2012-10-22 18:01 ` Alan Stern
2012-10-21 2:19 ` Alan Stern
2012-10-21 10:34 ` Daniel Mack
2012-10-21 11:59 ` Daniel Mack
2012-11-03 14:10 ` Christof Meerwald
2012-11-03 14:16 ` Daniel Mack
2012-11-03 14:28 ` Sven-Haegar Koch
2012-11-05 19:13 ` Christof Meerwald
2012-11-07 17:34 ` Alan Stern
2012-11-07 19:19 ` Takashi Iwai
2012-11-07 20:37 ` Alan Stern
2012-11-08 6:48 ` Takashi Iwai
2012-11-07 20:46 ` Christof Meerwald
2012-11-07 20:59 ` Artem S. Tashkinov
2012-11-08 0:42 ` Daniel Mack
2012-11-08 6:43 ` Takashi Iwai
2012-11-08 7:31 ` Daniel Mack
2012-11-08 8:09 ` Takashi Iwai
2012-11-08 15:55 ` Alan Stern
2012-11-08 15:58 ` Takashi Iwai
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=20121021110851.GA6504@liondog.tnic \
--to=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=security@kernel.org \
--cc=t.artem@lycos.com \
/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