Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754251Ab2JURDT (ORCPT ); Sun, 21 Oct 2012 13:03:19 -0400 Received: from mail.skyhub.de ([78.46.96.112]:60769 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752397Ab2JURDR (ORCPT ); Sun, 21 Oct 2012 13:03:17 -0400 Date: Sun, 21 Oct 2012 19:03:15 +0200 From: Borislav Petkov To: "Artem S. Tashkinov" 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: Re: A reliable kernel panic (3.6.2) and system crash when visiting a particular website Message-ID: <20121021170315.GB20642@liondog.tnic> Mail-Followup-To: Borislav Petkov , "Artem S. Tashkinov" , 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 References: <2104474742.26357.1350734815286.JavaMail.mail@webmail05> <20121020162759.GA12551@liondog.tnic> <966148591.30347.1350754909449.JavaMail.mail@webmail08> <20121020203227.GC555@elf.ucw.cz> <20121020225849.GA8976@liondog.tnic> <1781795634.31179.1350774917965.JavaMail.mail@webmail04> <20121021002424.GA16247@liondog.tnic> <1798605268.19162.1350784641831.JavaMail.mail@webmail17> <20121021110851.GA6504@liondog.tnic> <121566322.100103.1350820776893.JavaMail.mail@webmail20> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <121566322.100103.1350820776893.JavaMail.mail@webmail20> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 884 Lines: 23 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. -- Regards/Gruss, Boris. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/