From: Maurizio Lombardi <mlombard@redhat.com>
To: Aaron Lu <aaron.lu@intel.com>
Cc: Jens Axboe <axboe@fb.com>, Ming Lei <ming.lei@canonical.com>,
Jet Chen <jet.chen@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
lkp@01.org
Subject: Re: [Merge branch 'for] BUG: unable to handle kernel NULL pointer dereference at 0000000000000028
Date: Fri, 11 Jul 2014 16:58:56 +0200 [thread overview]
Message-ID: <53BFFBB0.7060709@redhat.com> (raw)
In-Reply-To: <53BBB30F.7020304@intel.com>
Hi,
On 07/08/2014 10:59 AM, Aaron Lu wrote:
> The merge 49b3f10e2cf5c1c25d2ce33ab255cff8a8096ce6 seems to have only one
> commit: 254c4407cb84a6dec90336054615b0f0e996bb7c, so I added you guys in.
> Please take a look if this is a real problem, thanks.
>
>
> [ 1010.593031] sda: unknown partition table
> [ 1010.598052] sd 2:0:0:0: [sda] Attached SCSI disk
> [ 1012.893125] sd 2:0:0:0: [sda] Synchronizing SCSI cache
> [ 1012.895934] BUG: unable to handle kernel NULL pointer dereference at 0000000000000028
> [ 1012.896336] IP: [<ffffffff813cf880>] blk_throtl_drain+0x30/0x150
I tried to revert my patch (commit 254c4407cb84a6dec90336054615b0f0e996bb7c)
but I'm still able to hit the very same kernel panic in linux-next, so I think
my patch is not the one to blame.
I was able to reproduce the error in a more easier way:
just execute the "reboot" command after the system boot is finished.
Regards,
Maurizio Lombardi
prev parent reply other threads:[~2014-07-11 14:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <53bbad38.bUEV+/Tm2WTBCfJH%fengguang.wu@intel.com>
2014-07-08 8:59 ` Aaron Lu
2014-07-08 12:55 ` Maurizio Lombardi
2014-07-11 14:58 ` Maurizio Lombardi [this message]
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=53BFFBB0.7060709@redhat.com \
--to=mlombard@redhat.com \
--cc=aaron.lu@intel.com \
--cc=axboe@fb.com \
--cc=jet.chen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=ming.lei@canonical.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
Powered by JetHome