From: Daniel Mack <zonque@gmail.com>
To: "Artem S. Tashkinov" <t.artem@lycos.com>
Cc: bp@alien8.de, 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,
alsa-devel@alsa-project.org, stern@rowland.harvard.edu
Subject: Re: A reliable kernel panic (3.6.2) and system crash when visiting a particular website
Date: Sun, 21 Oct 2012 21:54:51 +0200 [thread overview]
Message-ID: <5084530B.6030209@gmail.com> (raw)
In-Reply-To: <1906833625.122006.1350848941352.JavaMail.mail@webmail16>
On 21.10.2012 21:49, Artem S. Tashkinov wrote:
>>
>> On Oct 21, 2012, Borislav Petkov <bp@alien8.de> wrote:
>>
>> On Sun, Oct 21, 2012 at 11:59:36AM +0000, Artem S. Tashkinov wrote:
>>> http://imageshack.us/a/img685/9452/panicz.jpg
>>>
>>> list_del corruption. prev->next should be ... but was ...
>>
>> Btw, this is one of the debug options I told you to enable.
>>
>>> I cannot show you more as I have no serial console to use :( and the kernel
>>> doesn't have enough time to push error messages to rsyslog and fsync
>>> /var/log/messages
>>
>> I already told you how to catch that oops: boot with "pause_on_oops=600"
>> on the kernel command line and photograph the screen when the first oops
>> happens. This'll show us where the problem begins.
>
> This option didn't have any effect, or maybe it's because it's such a serious crash
> the kernel has no time to actually print an ooops/panic message.
>
> dmesg messages up to a crash can be seen here: https://bugzilla.kernel.org/attachment.cgi?id=84221
Nice. Could you do that again with the patch applied I sent yo some
hours ago?
Thanks,
Daniel
next prev parent reply other threads:[~2012-10-21 19:55 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-20 12:06 A reliable kernel panic (3.6.2) and system crash when visiting a particular website 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
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 [this message]
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=5084530B.6030209@gmail.com \
--to=zonque@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=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=stern@rowland.harvard.edu \
--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;
as well as URLs for NNTP newsgroup(s).