public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Evgeniy Polyakov <zbr@ioremap.net>
To: Sven Geggus <lists@fuchsschwanzdomain.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: reproducible w1 oops on recent kernels (at least since 3.2.x)
Date: Wed, 16 Jan 2013 18:16:27 +0400	[thread overview]
Message-ID: <20130116141627.GA23638@ioremap.net> (raw)
In-Reply-To: <20130110184419.GA4524@geggus.net>

Hi

Sorry for long answer

On Thu, Jan 10, 2013 at 07:44:20PM +0100, Sven Geggus (lists@fuchsschwanzdomain.de) wrote:
> I first thought this to be a Raspberry Pi thing, but its not. Looks
> like w1 driver is broken in some platform and busmaster independent
> way at least since kernel 3.2.x (which Raspberry Pi uses).

> P.S.: Looks like this is the same bug, as the one reported at
> https://bugzilla.redhat.com/show_bug.cgi?id=857954

Its indeed looks the same.
Can you confirm that bug still persists and that it doesn't exist in
3.1? Do you have a possibility to bisect w1 bits down to broken commit?

-- 
	Evgeniy Polyakov

  reply	other threads:[~2013-01-16 14:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-10 18:44 reproducible w1 oops on recent kernels (at least since 3.2.x) Sven Geggus
2013-01-16 14:16 ` Evgeniy Polyakov [this message]
2013-03-02  0:11   ` Marcin Jurkowski
2013-03-02  9:45     ` Sven Geggus
2013-03-02 13:50       ` [PATCH 1/1] w1: fix oops when w1_search is called from netlink connector Marcin Jurkowski
2013-03-03 15:36         ` Sven Geggus
2013-03-03 20:54         ` Evgeniy Polyakov
2013-03-03 22:41           ` GregKH
2013-03-11 13:18             ` Josh Boyer

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=20130116141627.GA23638@ioremap.net \
    --to=zbr@ioremap.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@fuchsschwanzdomain.de \
    /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