All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 48241] oops when setting up LVM
Date: Thu,  4 Oct 2012 07:34:56 +0000 (UTC)	[thread overview]
Message-ID: <20121004073456.0499F11FC6C@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-48241-11613@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=48241





--- Comment #9 from Anonymous Emailer <anonymous@kernel-bugs.osdl.org>  2012-10-04 07:34:55 ---
Reply-To: danielfsantos@att.net

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)
>>  --> (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

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2012-10-04  7:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-03 15:04 [Bug 48241] New: oops when setting up LVM bugzilla-daemon
2012-10-03 15:05 ` [Bug 48241] " bugzilla-daemon
2012-10-03 15:06 ` bugzilla-daemon
2012-10-03 15:13 ` bugzilla-daemon
2012-10-03 15:23 ` [Bug 48241] New: " James Bottomley
2012-10-04  7:34   ` [Bug 48241] New: oops when setting up LVM (3.6.0-next-20121003) Daniel Santos
2012-10-03 15:23 ` [Bug 48241] oops when setting up LVM bugzilla-daemon
2012-10-03 15:36 ` bugzilla-daemon
2012-10-03 16:16 ` bugzilla-daemon
2012-10-03 16:21 ` bugzilla-daemon
2012-10-03 16:45 ` bugzilla-daemon
2012-10-03 16:46 ` bugzilla-daemon
2012-10-03 16:46 ` bugzilla-daemon
2012-10-04  7:34 ` bugzilla-daemon [this message]
2012-10-05 18:38 ` bugzilla-daemon
2013-11-19 22:58 ` bugzilla-daemon

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=20121004073456.0499F11FC6C@bugzilla.kernel.org \
    --to=bugzilla-daemon@bugzilla.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.