public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Seyfried <stefan.seyfried@googlemail.com>
To: Ming Lei <tom.leiming@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [REGRESSION] 4.1-rc6 unloading loop OOPS
Date: Thu, 04 Jun 2015 16:36:21 +0200	[thread overview]
Message-ID: <55706265.8020609@message-id.googlemail.com> (raw)
In-Reply-To: <CACVXFVMor88EM7=qpHZtg8MST8-b=oBUiW9aNE4CX2w3UcamuQ@mail.gmail.com>

Hi Ming,

Am 04.06.2015 um 12:24 schrieb Ming Lei:
> On Thu, Jun 4, 2015 at 5:11 PM, Stefan Seyfried
> <stefan.seyfried@googlemail.com> wrote:

>> I can reproduce the backtrace after a reboot once (subsequent modprobe/rmmod loop
>> do not complain anymore), but not the OOPS.
> 
> One fix[1] was just merged to linus tree, and could you test that to see if your
> issue can be addressed?
> 
> [1] http://marc.info/?t=143201518300001&r=1&w=2

I just tried current Linus' master v4.1-rc6-49-g8a7deb3 which contains
this commit and do no longer get the Warning

Unfortunately, due to this I cannot really test your patch for the OOPS
(but the OOPS was only happening once for me, so it was not reliably
triggered).

Thanks, things work well for me, again :-)

Best regards,

	Stefan
-- 
Stefan Seyfried
Linux Consultant & Developer -- GPG Key: 0x731B665B

B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

  reply	other threads:[~2015-06-04 14:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-04  9:11 [REGRESSION] 4.1-rc6 unloading loop OOPS Stefan Seyfried
2015-06-04 10:24 ` Ming Lei
2015-06-04 14:36   ` Stefan Seyfried [this message]
2015-06-04 14:43     ` Ming Lei

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=55706265.8020609@message-id.googlemail.com \
    --to=stefan.seyfried@googlemail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tom.leiming@gmail.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