linux-kernel - Re: BUG: kernel panic on Dell Vostro 3560 when plugging in AC adapter

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <50EEF8A9.5070406@gmail.com>
Date:	Thu, 10 Jan 2013 18:21:45 +0100
From:	Adrian Byszuk <adrian.byszuk@...il.com>
To:	Borislav Petkov <bp@...en8.de>, linux-kernel@...r.kernel.org,
	Thomas Gleixner <tglx@...utronix.de>,
	John Stultz <john.stultz@...aro.org>
Subject: Re: BUG: kernel panic on Dell Vostro 3560 when plugging in AC adapter

On 10/01/13 15:02, Adrian Byszuk wrote:
> On 10/01/13 12:35, Borislav Petkov wrote:
>> On Thu, Jan 10, 2013 at 11:59:48AM +0100, Adrian Byszuk wrote:
>>> I think I won't get the answer this way. Bisecting between
>>> 3.7 and 3.8-rc2 (from linus tree) led me to commit
>>> 63e1ed2364050073770c085021377d7764969b85 titled "Update vt8500 PWM
>>> driver support", which I think is rather nonsense. Also, depending on
>>> bisected version, sometimes I got kernel panic, but sometimes (more
>>> often) whole system would just freeze completely.
>>>
>>> Any other way diagnose this bug?
>>
>> Hmm, bisection can sometimes lead us in the fields, nasty.
>>
>> Well, you could try bisecting the major releases in between. I.e., test
>> 3.8-rc1, and then test vanilla 3.7.
>>
>> For example, if you still trigger it with -rc1, then no need to bisect
>> the -rc2..-rc1 range. If you still trigger it with 3.7 then not good -
>> in that case you'd need to go further back in time.
>>
>> The best would be if you don't trigger it with 3.7 but trigger it with
>> 3.7.1 :) Then it is easy.
> 
> Life isn't easy :-) with 3.7 I can trigger it too, but I can't trigger
> it with 3.8-rc1, so the fix lies somewhere between 3.7.1..3.8-rc1.
> I'll try bisecting it again.


Aaaand failure again!
I haven't finished bisecting yet, but as of now I have ~20 commits left:
all related to 'mtd' - propably not a source of troubles too.
Any other way to diagnose this bug?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/