From: Daniel Santos <danielfsantos@att.net>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: bugzilla-daemon@bugzilla.kernel.org, linux-scsi@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Bug 48241] New: oops when setting up LVM (3.6.0-next-20121003)
Date: Thu, 04 Oct 2012 02:34:54 -0500 [thread overview]
Message-ID: <506D3C1E.4050704@att.net> (raw)
In-Reply-To: <1349277786.2404.24.camel@dabdike.int.hansenpartnership.com>
On 10/03/2012 10:23 AM, James Bottomley wrote:
> On Wed, 2012-10-03 at 15:04 +0000, bugzilla-daemon@bugzilla.kernel.org
> wrote:
>> https://bugzilla.kernel.org/show_bug.cgi?id=48241
>>
>> Summary: oops when setting up LVM
>> Product: IO/Storage
>> Version: 2.5
>> Kernel Version: 3.6.0-next-20121003
>> Platform: All
>> OS/Version: Linux
>> Tree: Mainline
>> Status: NEW
>> Severity: normal
>> Priority: P1
>> Component: SCSI
>> AssignedTo: linux-scsi@vger.kernel.org
>> ReportedBy: daniel.santos@pobox.com
>> Regression: No
>>
>>
>> Created an attachment (id=81921)
>> --> (https://bugzilla.kernel.org/attachment.cgi?id=81921)
>> image of oops
>
> The image says the RIP is at kthread_data + 0xb
>
> That implies something went wrong within the workqueue or kthread
> systems, I've cc'd linux-kernel, but it's a bit of a vague thing to go
> on and could conceivably be a hardware issue (or some weird thread
> interaction in linux-next).
>
> The first question would be "does it happen in vanilla 3.6"?
>
> James
So just to CC LKML, works in vanilla 3.6.0, happens in both -next & -mm,
tried compiling with both gcc 4.6.3 & 4.7.1.
Daniel
prev parent reply other threads:[~2012-10-04 7:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-48241-11613@https.bugzilla.kernel.org/>
2012-10-03 15:23 ` [Bug 48241] New: oops when setting up LVM James Bottomley
2012-10-04 7:34 ` Daniel Santos [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=506D3C1E.4050704@att.net \
--to=danielfsantos@att.net \
--cc=James.Bottomley@HansenPartnership.com \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=daniel.santos@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
/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
all inboxes | Powered by JetHome®