All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Christie <michaelc@cs.wisc.edu>
To: linux-scsi@vger.kernel.org, sbezverk@cisco.com
Subject: Re: [Bug 111441] New: iscsi fails to attach to targets
Date: Thu, 28 Jan 2016 20:13:36 -0600	[thread overview]
Message-ID: <56AACAD0.30705@cs.wisc.edu> (raw)
In-Reply-To: <56AAC605.1080707@cs.wisc.edu>

I thought you could just reply to kernel bugzilla mails and it would
automatically add your reply to the bz, but I got some errors. Ccing the
bug reporter here, so I do not have to make an account and go through bz.

Serguei see below. I need some extra info.

On 01/28/2016 07:53 PM, Mike Christie wrote:
> On 01/28/2016 04:51 PM, bugzilla-daemon@bugzilla.kernel.org wrote:
>> https://bugzilla.kernel.org/show_bug.cgi?id=111441
>>
>>             Bug ID: 111441
>>            Summary: iscsi fails to attach to targets
>>            Product: IO/Storage
>>            Version: 2.5
>>     Kernel Version: 4.4.0-1
>>           Hardware: x86-64
>>                 OS: Linux
>>               Tree: Mainline
>>             Status: NEW
> 
> 
>> 4.4.0-1.el7.elrepo.x86_64 #1
> 
> I have not seen this oops before. We saw similar ones around 5 or 6
> years ago, but they were due to some sysfs or block or scsi issue (I
> cannot remember exacty) and fixed there.
> 
> Is this a distro kernel or mainline. BZ says mainline, but the kernel
> name in bug looks like a red hat related one. Where did you get it?
> 
> I do not hit this in 4.4 mainline. Send me your kernel .config, so I can
> make sure I have the same options.
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


  reply	other threads:[~2016-01-29  2:13 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-28 22:51 [Bug 111441] New: iscsi fails to attach to targets bugzilla-daemon
2016-01-29  1:53 ` Mike Christie
2016-01-29  2:13   ` Mike Christie [this message]
2016-01-29  2:55   ` Serguei Bezverkhi (sbezverk)
2016-01-29  8:01     ` Michael Christie
2016-01-29  8:25       ` Mike Christie
2016-01-29 12:04       ` Serguei Bezverkhi (sbezverk)
2016-01-29 19:08         ` Michael Christie
2016-01-29 19:11           ` Serguei Bezverkhi (sbezverk)
2016-01-29 19:26             ` Mike Christie
2016-01-29 22:21               ` Serguei Bezverkhi (sbezverk)
2016-01-29 23:32                 ` Mike Christie
2016-01-30  7:38                   ` Nicholas A. Bellinger
2016-02-01 16:55                     ` Mike Christie
2016-02-02 16:41                       ` Serguei Bezverkhi (sbezverk)
2016-02-02 22:56                       ` Nicholas A. Bellinger
2016-02-02 23:21                         ` Serguei Bezverkhi (sbezverk)
2016-02-08  8:01                         ` Nicholas A. Bellinger
2016-02-16 19:08                           ` Hannes Reinecke
2016-02-27 22:15                             ` Nicholas A. Bellinger
2016-02-02 18:09                   ` Christoph Hellwig
2016-02-02 20:12                     ` Mike Christie
2016-02-02 20:25                       ` Serguei Bezverkhi (sbezverk)
2016-02-02 21:54                       ` Serguei Bezverkhi (sbezverk)
2016-02-22  0:45                   ` Serguei Bezverkhi (sbezverk)
2016-02-22  7:08                     ` Hannes Reinecke
2016-02-22 11:36                       ` Serguei Bezverkhi (sbezverk)
2016-01-29  3:00 ` [Bug 111441] " bugzilla-daemon
2016-01-29  3:05 ` bugzilla-daemon
2016-01-29  3:32 ` bugzilla-daemon
2016-01-29  3:40 ` bugzilla-daemon
2016-01-29 12:04 ` bugzilla-daemon
2016-01-29 19:11 ` bugzilla-daemon
2016-01-29 22:21 ` bugzilla-daemon
2016-01-30  7:46 ` bugzilla-daemon
2016-02-01  2:13 ` bugzilla-daemon
2016-02-02 16:41 ` bugzilla-daemon
2016-02-02 20:25 ` bugzilla-daemon
2016-02-02 22:03 ` bugzilla-daemon
2016-02-02 22:56 ` bugzilla-daemon
2016-02-02 23:21 ` bugzilla-daemon
2016-02-08  8:01 ` bugzilla-daemon
2016-02-22  0:45 ` bugzilla-daemon
2016-02-22  7:08 ` bugzilla-daemon
2016-02-22 11:36 ` bugzilla-daemon
2016-02-27 22:15 ` 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=56AACAD0.30705@cs.wisc.edu \
    --to=michaelc@cs.wisc.edu \
    --cc=linux-scsi@vger.kernel.org \
    --cc=sbezverk@cisco.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 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.