public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Byszuk <adrian.byszuk@gmail.com>
To: Borislav Petkov <bp@alien8.de>,
	linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	John Stultz <john.stultz@linaro.org>
Subject: Re: BUG: kernel panic on Dell Vostro 3560 when plugging in AC adapter
Date: Thu, 10 Jan 2013 18:21:45 +0100	[thread overview]
Message-ID: <50EEF8A9.5070406@gmail.com> (raw)
In-Reply-To: <50EECA0B.2050407@gmail.com>

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?

  reply	other threads:[~2013-01-10 17:21 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-09  9:23 BUG: kernel panic on Dell Vostro 3560 when plugging in AC adapter Adrian Byszuk
2013-01-09 12:07 ` Borislav Petkov
2013-01-09 16:19   ` Adrian Byszuk
2013-01-09 17:01     ` Borislav Petkov
2013-01-09 18:01       ` Adrian Byszuk
2013-01-09 18:15         ` Borislav Petkov
2013-01-10 10:59           ` Adrian Byszuk
2013-01-10 11:35             ` Borislav Petkov
2013-01-10 14:02               ` Adrian Byszuk
2013-01-10 17:21                 ` Adrian Byszuk [this message]
2013-01-11  6:59                   ` Sujith Manoharan
2013-01-11 11:25                     ` Adrian Byszuk
2013-01-11 11:46                       ` Borislav Petkov
2013-01-11 12:49                         ` Adrian Byszuk
2013-01-11 13:30                           ` Borislav Petkov
2013-01-11 13:48                             ` Greg KH
2013-01-11 11:43                     ` Borislav Petkov

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=50EEF8A9.5070406@gmail.com \
    --to=adrian.byszuk@gmail.com \
    --cc=bp@alien8.de \
    --cc=john.stultz@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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