Date: Mon, 17 Oct 2016 17:20:42 +0200
From: Wim Osterholt <wim@djo.tudelft.nl>
To: Oliver Neukum <oneukum@suse.com>
Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
        Wim Osterholt <wim@djo.tudelft.nl>
Subject: Re: crash by cdc_acm driver in kernels 4.8-rc1/5
Message-ID: <20161017152042.GA26559@djo.tudelft.nl>
Reply-To: wim@djo.tudelft.nl
References: <20160908115803.GA28274@djo.tudelft.nl>
 <1473337238.32073.2.camel@suse.com>
 <20160908125850.GC28274@djo.tudelft.nl>
 <1476713445.3938.1.camel@suse.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1476713445.3938.1.camel@suse.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 767
Lines: 22

On Mon, Oct 17, 2016 at 04:10:45PM +0200, Oliver Neukum wrote:
> Hi,
>    
> I got one of those devices. However, I don't get a crash.
> Could you please give me instructions on how you trigger it?
  
That's not too hard, just plug it in. :-)
  
However you must have set cdc_acm in your kernel, or availabe as a module. 
It happens on all my machines on kernels 4.8 and 4.9.
Now, all my kernel configs will differ a bit, but must have something
peculiar in common. Or you've received a totally different device.
 
Here's one config at http://webserver.djo.tudelft.nl/.config-4.8.1
 
Many options are inherited by 'make oldconfig' from version to version,
without me knowing what it all means. So maybe it's just a weird combination
of options then?


Regards, Wim.