All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Sebastian Gottschall <s.gottschall@dd-wrt.com>
Cc: linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	torvalds@linux-foundation.org, stable@vger.kernel.org,
	lwn@lwn.net, Jiri Slaby <jslaby@suse.cz>
Subject: Re: Linux 4.9.69
Date: Thu, 14 Dec 2017 21:01:20 +0100	[thread overview]
Message-ID: <20171214200120.GA26465@kroah.com> (raw)
In-Reply-To: <5721b213-975d-8383-1efc-0deedaba8bc3@dd-wrt.com>

On Thu, Dec 14, 2017 at 08:20:08PM +0100, Sebastian Gottschall wrote:
> this happend with the rc1 version. dont know if it still applies, will check
> now. 4.9.68 works
> 
> [    2.523730] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.9.69-rc1 #16
> [    2.523823] Hardware name: Qualcomm (Flattened Device Tree)
> [    2.530247] task: dd41a9c0 task.stack: dd434000
> [    2.535548] PC is at llc_sap_open+0x34/0xf8
> [    2.540053] LR is at llc_sap_open+0x28/0xf8

Odd, nothing has changed in this area since 4.9.13.

Any chance you can run 'git bisect' to find the offending commit?

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Sebastian Gottschall <s.gottschall@dd-wrt.com>
Cc: linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	torvalds@linux-foundation.org, stable@vger.kernel.org,
	lwn@lwn.net, Jiri Slaby <jslaby@suse.cz>
Subject: Re: Linux 4.9.69
Date: Thu, 14 Dec 2017 21:01:20 +0100	[thread overview]
Message-ID: <20171214200120.GA26465@kroah.com> (raw)
In-Reply-To: <5721b213-975d-8383-1efc-0deedaba8bc3@dd-wrt.com>

On Thu, Dec 14, 2017 at 08:20:08PM +0100, Sebastian Gottschall wrote:
> this happend with the rc1 version. dont know if it still applies, will check
> now. 4.9.68 works
> 
> [��� 2.523730] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.9.69-rc1 #16
> [��� 2.523823] Hardware name: Qualcomm (Flattened Device Tree)
> [��� 2.530247] task: dd41a9c0 task.stack: dd434000
> [��� 2.535548] PC is at llc_sap_open+0x34/0xf8
> [��� 2.540053] LR is at llc_sap_open+0x28/0xf8

Odd, nothing has changed in this area since 4.9.13.

Any chance you can run 'git bisect' to find the offending commit?

thanks,

greg k-h

  reply	other threads:[~2017-12-14 20:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-14  9:29 Linux 4.9.69 Greg KH
2017-12-14  9:29 ` Greg KH
2017-12-14 19:20 ` Sebastian Gottschall
2017-12-14 20:01   ` Greg KH [this message]
2017-12-14 20:01     ` Greg KH
2017-12-14 21:07     ` Sebastian Gottschall
2017-12-14 22:18       ` Sebastian Gottschall

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=20171214200120.GA26465@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=jslaby@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lwn@lwn.net \
    --cc=s.gottschall@dd-wrt.com \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.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.