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 11:59:48 +0100 [thread overview]
Message-ID: <50EE9F24.8010908@gmail.com> (raw)
In-Reply-To: <20130109181520.GB17840@liondog.tnic>
On 09/01/13 19:15, Borislav Petkov wrote:
> On Wed, Jan 09, 2013 at 07:01:20PM +0100, Adrian Byszuk wrote:
>> I started bisecting and got situation where I don't see kernel panic,
>> but the whole system hangs - not sure in what direction go next, but
>
> Hmm, git bisect skip should help here, look at the git-bisect manpage.
>
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?
Regards,
Adrian
next prev parent reply other threads:[~2013-01-10 10:59 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 [this message]
2013-01-10 11:35 ` Borislav Petkov
2013-01-10 14:02 ` Adrian Byszuk
2013-01-10 17:21 ` Adrian Byszuk
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=50EE9F24.8010908@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