[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <53BFFBB0.7060709@redhat.com>
Date: Fri, 11 Jul 2014 16:58:56 +0200
From: Maurizio Lombardi <mlombard@...hat.com>
To: Aaron Lu <aaron.lu@...el.com>
CC: Jens Axboe <axboe@...com>, Ming Lei <ming.lei@...onical.com>,
Jet Chen <jet.chen@...el.com>,
LKML <linux-kernel@...r.kernel.org>, lkp@...org
Subject: Re: [Merge branch 'for] BUG: unable to handle kernel NULL pointer
dereference at 0000000000000028
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
--
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/
Powered by blists - more mailing lists