All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@infradead.org>
To: Andrei Borzenkov <arvidjaar@gmail.com>
Cc: "Gabriele Mazzotta" <gabriele.mzt@gmail.com>,
	"Pali Rohár" <pali.rohar@gmail.com>,
	platform-driver-x86@vger.kernel.org, mjg59@srcf.ucam.org
Subject: Re: Regression with dell-rbtn: radio killed on resume after suspend to RAM
Date: Mon, 23 Nov 2015 11:29:43 -0800	[thread overview]
Message-ID: <20151123192943.GY7413@malice.jf.intel.com> (raw)
In-Reply-To: <56533D81.7070406@gmail.com>

On Mon, Nov 23, 2015 at 07:23:29PM +0300, Andrei Borzenkov wrote:
> 23.11.2015 18:14, Gabriele Mazzotta пишет:
> >On 23/11/2015 15:50, Pali Rohár wrote:
> >>On Sunday 22 November 2015 09:23:19 Andrei Borzenkov wrote:
> >>>21.11.2015 23:39, Andrei Borzenkov пишет:
> >>>>21.11.2015 22:08, Pali Rohár пишет:
> >>>>>On Saturday 21 November 2015 19:57:18 Andrei Borzenkov wrote:
> >>>>>>After installing 4.2 on Dell Latitude E5450 I found that wireless was
> >>>>>>disabled every second resume from suspend to RAM. Blacklisting
> >>>>>>dell-rbtn "fixed" it.
> >>>>>>
> >>>>>>This is probably the same as discussed in this Arch forum and related
> >>>>>>bug report: https://bbs.archlinux.org/viewtopic.php?id=203404. I
> >>>>>>myself hit it on Ubuntu.
> >>>>>>
> >>>>>>I am not familiar with other models, but E5450 does have DELLABCE and
> >>>>>>so is using dell-rbtn driver.
> >>>>>>
> >>>>>>I am happy to test patches if need. Please let me know if formal bug
> >>>>>>report is required.
> >>>>>>
> >>>>>>-andrei
> >>>>>
> >>>>>Hi Andrei!
> >>>>>
> >>>>>About five hours ago Gabriele sent patch which fixing this problem to
> >>>>>LKML. You can find it on: https://lkml.org/lkml/2015/11/21/57
> >>>>>
> >>>>>Can you test that patch and confirm it fix also for you?
> >>>>>
> >>>>
> >>>>Yes, it does.
> >>>
> >>>Unfortunately it was too early. Today after resume I again got disable
> >>>radio, and also several later attempts to suspend/resume. Then last
> >>>time I
> >>>suddenly got radio working again after resume.
> >>>
> >>>Patch looks racy; there is no guarantee we get notification before
> >>>resetting
> >>>in suspend flag.
> >>>
> >>
> >>Gabriele, any idea how to fix this?
> >>
> >
> >I can't think of anything other than ignoring notifications that arrives
> >within X seconds after the execution of the resume callback.
> >Unfortunately, we have no idea on how to detect systems that misbehave
> >and creating a blacklist is not a feasible solution.
> >
> >Something such as the following should work, but maybe it's not a nice
> >solution.
> >
> 
> I looked at what dell-rbtn does. My system (Latitude E5450) has RBTN of type
> TOGGLE. In this case both del-laptop hooks itself into i8042 and dell-rbtn
> delivers KEY_RFKILL event to input susbsystem. IOW dell-rbtn looks
> completely redundant in this configuration.
> 
> Can we detect that rfkill toggle is already avaiable via normal keyboard and
> not activate dell-rbtn in this case?

Also dropping this one until we can arrive at a complete solution.

Pali, Gabriele, this one is in your hands. I will review and provide feedback
where I can - I confess I'm finding it difficult to keep all the pieces straight
in my head, and without any hardware, I have to rely entirely on what I can
piece together (a situation we are all in as this differs across many systems,
nobody has all the necessary bits).

It may be helpful for someone to put together a current status, known issues,
plan of attack to get this moving forward again.

-- 
Darren Hart
Intel Open Source Technology Center

  reply	other threads:[~2015-11-23 19:29 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-21 18:57 Regression with dell-rbtn: radio killed on resume after suspend to RAM Andrei Borzenkov
2015-11-21 19:08 ` Pali Rohár
2015-11-21 20:39   ` Andrei Borzenkov
2015-11-22  6:23     ` Andrei Borzenkov
2015-11-23 14:50       ` Pali Rohár
2015-11-23 15:14         ` Gabriele Mazzotta
2015-11-23 16:23           ` Andrei Borzenkov
2015-11-23 19:29             ` Darren Hart [this message]
2015-11-23 22:33               ` Gabriele Mazzotta
     [not found]                 ` <5653E243.9010707@gmail.com>
2015-11-24  8:32                   ` Pali Rohár
2015-11-24  8:49                   ` Gabriele Mazzotta
2015-11-24  8:52                     ` Matthew Garrett
2015-11-24  9:02                       ` Pali Rohár
2015-11-24  9:42                       ` Gabriele Mazzotta
2015-11-25  3:57                         ` Andrei Borzenkov
2015-11-25  3:53                 ` Andrei Borzenkov
2015-11-25  8:34                   ` Andrei Borzenkov
2015-11-25  8:35                   ` Pali Rohár
2015-11-25  9:31                   ` Gabriele Mazzotta

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=20151123192943.GY7413@malice.jf.intel.com \
    --to=dvhart@infradead.org \
    --cc=arvidjaar@gmail.com \
    --cc=gabriele.mzt@gmail.com \
    --cc=mjg59@srcf.ucam.org \
    --cc=pali.rohar@gmail.com \
    --cc=platform-driver-x86@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.