All of lore.kernel.org
 help / color / mirror / Atom feed
From: Manuel Reimer <Manuel.Spam@nurfuerspam.de>
To: linux-input@vger.kernel.org
Subject: Re: Pull USB plug while fftest on PS4 pad --> Kernel panic
Date: Sun, 7 Feb 2016 15:08:08 +0100	[thread overview]
Message-ID: <n97j48$219$1@ger.gmane.org> (raw)
In-Reply-To: <n932md$odm$1@ger.gmane.org>

Hello,

I did some more testing (now with a virtual machine).

I've updated to Kernel version 4.4.1. The problem stays the same.

Then I tried with a PS3 controller and (as somehow expected, as the same 
driver is involved), I have the same problem.

The kernel panic, directly after unplugging, only occured once, but the 
following is 100% reproducible:

- Open fftest and run some effect on the controller.
- Unplug the controller while fftest is still running. It doesn't matter 
if an effect is still playing.
- After doing so, plug *any* USB HID game controller, you like. I used 
some cheap noname controller. For me plugging whatever USB HID game 
controller finally crashes the kernel with 100% success rate.

So it seems to be the case, that the hid-sony module somehow breaks 
parts deeper in the USB HID stack in the kernel.

This problem doesn't occur with the xpad driver and a Xbox 360 gamepad, 
so it is no general problem which happens with every supported game 
controller.

Any feedback would be nice. Am I in the right mailing list for bug reports?

Thanks in advance.

Best regards,

Manuel


On 02/05/2016 10:03 PM, Manuel Reimer wrote:
> Hello,
>
> I'm currently using the following Kernel version:
> Linux manuelspc 4.3.3-3-ARCH #1 SMP PREEMPT Sun Jan 24 10:28:30 CET 2016
> x86_64 GNU/Linux
>
> While testing with force feedback, I found the following bug which makes
> it impossible to disconnect the PS4 controller while some "force
> feedback user" (may also be a game) is still running.
>
> To reproduce, connect a PS4 controller via USB. Now run "fftest" on it
> and choose effect number "0".
>
> While the effect still runs, pull the USB plug.
>
> Result: The kernel panics. Had to hard-reset the machine.
>
> Is it OK to just report this here or should I open a bug on Bugzilla for
> that?
> If more information is needed, just ask.
>
> Best regards,
>
> Manuel
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-input" 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-02-07 14:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-05 21:03 Pull USB plug while fftest on PS4 pad --> Kernel panic Manuel Reimer
2016-02-07 14:08 ` Manuel Reimer [this message]
2016-02-07 19:10   ` Simon Wood
2016-02-07 19:59   ` Antonio Ospite
2016-02-07 21:57     ` Manuel Reimer

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='n97j48$219$1@ger.gmane.org' \
    --to=manuel.spam@nurfuerspam.de \
    --cc=linux-input@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.