Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-11-23 Thread Alan Stern
On Wed, 23 Nov 2016, [ISO-8859-1] Bj�rn Mork wrote: > On November 23, 2016 1:54:57 AM CET, Wim Osterholt > wrote: > >On Tue, Nov 22, 2016 at 07:08:30PM +0100, Bjørn Mork wrote: > >> > On kernel 4.8.8 this crashes hard and produces over a serial link: > >> > >> Huh? That

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-11-23 Thread Alan Stern
On Wed, 23 Nov 2016, [ISO-8859-1] Bj�rn Mork wrote: > On November 23, 2016 1:54:57 AM CET, Wim Osterholt > wrote: > >On Tue, Nov 22, 2016 at 07:08:30PM +0100, Bjørn Mork wrote: > >> > On kernel 4.8.8 this crashes hard and produces over a serial link: > >> > >> Huh? That device shouldn't ever

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-11-22 Thread Bjørn Mork
On November 23, 2016 1:54:57 AM CET, Wim Osterholt wrote: >On Tue, Nov 22, 2016 at 07:08:30PM +0100, Bjørn Mork wrote: >> > On kernel 4.8.8 this crashes hard and produces over a serial link: >> >> Huh? That device shouldn't ever enter that code path AFAICS. >> Unless

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-11-22 Thread Bjørn Mork
On November 23, 2016 1:54:57 AM CET, Wim Osterholt wrote: >On Tue, Nov 22, 2016 at 07:08:30PM +0100, Bjørn Mork wrote: >> > On kernel 4.8.8 this crashes hard and produces over a serial link: >> >> Huh? That device shouldn't ever enter that code path AFAICS. >> Unless you wouldn't happen

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-11-22 Thread Wim Osterholt
On Tue, Nov 22, 2016 at 07:08:30PM +0100, Bjørn Mork wrote: > > On kernel 4.8.8 this crashes hard and produces over a serial link: > > Huh? That device shouldn't ever enter that code path AFAICS. > Unless you wouldn't happen to add a dynamic entry for this device, No idea of what you mean

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-11-22 Thread Wim Osterholt
On Tue, Nov 22, 2016 at 07:08:30PM +0100, Bjørn Mork wrote: > > On kernel 4.8.8 this crashes hard and produces over a serial link: > > Huh? That device shouldn't ever enter that code path AFAICS. > Unless you wouldn't happen to add a dynamic entry for this device, No idea of what you mean

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-11-22 Thread Wim Osterholt
On Tue, Nov 22, 2016 at 06:50:28PM +0100, Bjørn Mork wrote: > > iCountryCodeRelDate4 04052004 > > wCountryCode 0x4803 > > No excuse for crashing of course, but that's one of the sickets > descriptor sets I've seen today. Who got the bright idea to put the >

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-11-22 Thread Wim Osterholt
On Tue, Nov 22, 2016 at 06:50:28PM +0100, Bjørn Mork wrote: > > iCountryCodeRelDate4 04052004 > > wCountryCode 0x4803 > > No excuse for crashing of course, but that's one of the sickets > descriptor sets I've seen today. Who got the bright idea to put the >

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-11-22 Thread Bjørn Mork
Wim Osterholt writes: > On Mon, Nov 21, 2016 at 02:19:32PM +0100, Oliver Neukum wrote: > >> I don't understand it, bit please test the attached patch >> with dynamic debugging for cdc-acm and the kernel log level >> at maximum. > >> diff --git a/drivers/usb/class/cdc-acm.c

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-11-22 Thread Bjørn Mork
Wim Osterholt writes: > On Mon, Nov 21, 2016 at 02:19:32PM +0100, Oliver Neukum wrote: > >> I don't understand it, bit please test the attached patch >> with dynamic debugging for cdc-acm and the kernel log level >> at maximum. > >> diff --git a/drivers/usb/class/cdc-acm.c

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-11-22 Thread Bjørn Mork
Wim Osterholt writes: > On Mon, Nov 21, 2016 at 02:19:32PM +0100, Oliver Neukum wrote: >> On Thu, 2016-11-17 at 17:11 +0100, Wim Osterholt wrote: >> >> > Nov 17 15:07:51 localhost kernel: Check point 10 >> > Nov 17 15:07:51 localhost kernel: BUG: unable to handle kernel

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-11-22 Thread Bjørn Mork
Wim Osterholt writes: > On Mon, Nov 21, 2016 at 02:19:32PM +0100, Oliver Neukum wrote: >> On Thu, 2016-11-17 at 17:11 +0100, Wim Osterholt wrote: >> >> > Nov 17 15:07:51 localhost kernel: Check point 10 >> > Nov 17 15:07:51 localhost kernel: BUG: unable to handle kernel NULL >> > pointer

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-11-22 Thread Wim Osterholt
On Mon, Nov 21, 2016 at 02:19:32PM +0100, Oliver Neukum wrote: > I don't understand it, bit please test the attached patch > with dynamic debugging for cdc-acm and the kernel log level > at maximum. > diff --git a/drivers/usb/class/cdc-acm.c b/drivers/usb/class/cdc-acm.c > index 6895f9e..f03b5db

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-11-22 Thread Wim Osterholt
On Mon, Nov 21, 2016 at 02:19:32PM +0100, Oliver Neukum wrote: > I don't understand it, bit please test the attached patch > with dynamic debugging for cdc-acm and the kernel log level > at maximum. > diff --git a/drivers/usb/class/cdc-acm.c b/drivers/usb/class/cdc-acm.c > index 6895f9e..f03b5db

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-11-21 Thread poma
On 21.11.2016 21:23, Wim Osterholt wrote: > On Mon, Nov 21, 2016 at 04:58:25PM +0100, Wim Osterholt wrote: >> >> I didn't find traces of kernel-4.9-rc5 being ran on any of my laptops, so I >> can't have seen a crash on rc5. It seems rc5 and rc6 is safe now. > > Neither 4.8.10, nor 4.8.9 show the

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-11-21 Thread poma
On 21.11.2016 21:23, Wim Osterholt wrote: > On Mon, Nov 21, 2016 at 04:58:25PM +0100, Wim Osterholt wrote: >> >> I didn't find traces of kernel-4.9-rc5 being ran on any of my laptops, so I >> can't have seen a crash on rc5. It seems rc5 and rc6 is safe now. > > Neither 4.8.10, nor 4.8.9 show the

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-11-21 Thread Wim Osterholt
On Mon, Nov 21, 2016 at 04:58:25PM +0100, Wim Osterholt wrote: > > I didn't find traces of kernel-4.9-rc5 being ran on any of my laptops, so I > can't have seen a crash on rc5. It seems rc5 and rc6 is safe now. Neither 4.8.10, nor 4.8.9 show the bug. It must be a bug ouside cdc_acm that they

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-11-21 Thread Wim Osterholt
On Mon, Nov 21, 2016 at 04:58:25PM +0100, Wim Osterholt wrote: > > I didn't find traces of kernel-4.9-rc5 being ran on any of my laptops, so I > can't have seen a crash on rc5. It seems rc5 and rc6 is safe now. Neither 4.8.10, nor 4.8.9 show the bug. It must be a bug ouside cdc_acm that they

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-11-21 Thread Wim Osterholt
On Mon, Nov 21, 2016 at 02:19:32PM +0100, Oliver Neukum wrote: > On Thu, 2016-11-17 at 17:11 +0100, Wim Osterholt wrote: > > > Nov 17 15:07:51 localhost kernel: Check point 10 > > Nov 17 15:07:51 localhost kernel: BUG: unable to handle kernel NULL pointer > > dereference at 0249 > > Nov 17

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-11-21 Thread Wim Osterholt
On Mon, Nov 21, 2016 at 02:19:32PM +0100, Oliver Neukum wrote: > On Thu, 2016-11-17 at 17:11 +0100, Wim Osterholt wrote: > > > Nov 17 15:07:51 localhost kernel: Check point 10 > > Nov 17 15:07:51 localhost kernel: BUG: unable to handle kernel NULL pointer > > dereference at 0249 > > Nov 17

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-11-21 Thread Oliver Neukum
On Thu, 2016-11-17 at 17:11 +0100, Wim Osterholt wrote: > Nov 17 15:07:51 localhost kernel: Check point 10 > Nov 17 15:07:51 localhost kernel: BUG: unable to handle kernel NULL pointer > dereference at 0249 > Nov 17 15:07:51 localhost kernel: IP: [] acm_probe+0x559/0xe53 > [cdc_acm] > Nov

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-11-21 Thread Oliver Neukum
On Thu, 2016-11-17 at 17:11 +0100, Wim Osterholt wrote: > Nov 17 15:07:51 localhost kernel: Check point 10 > Nov 17 15:07:51 localhost kernel: BUG: unable to handle kernel NULL pointer > dereference at 0249 > Nov 17 15:07:51 localhost kernel: IP: [] acm_probe+0x559/0xe53 > [cdc_acm] > Nov

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-11-17 Thread Wim Osterholt
On Thu, Nov 17, 2016 at 10:14:34AM +0100, Wim Osterholt wrote: > > For completeness I should also try with SMP unset. That is for tomorrow > > then. > > With CONFIG_SMP unset nothing goes wrong here either. > It looks like it has been fixed in 4.9-rc5, but I should also double check > several

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-11-17 Thread Wim Osterholt
On Thu, Nov 17, 2016 at 10:14:34AM +0100, Wim Osterholt wrote: > > For completeness I should also try with SMP unset. That is for tomorrow > > then. > > With CONFIG_SMP unset nothing goes wrong here either. > It looks like it has been fixed in 4.9-rc5, but I should also double check > several

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-11-17 Thread Wim Osterholt
On Thu, Nov 17, 2016 at 02:57:33AM +0100, Wim Osterholt wrote: > Now a retry of 4.9-rc5. I take the config of 4.8.8 and accept > the default for the new options. > SMP set. No call trace appears. > For completeness I should also try with SMP unset. That is for tomorrow > then. With CONFIG_SMP

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-11-17 Thread Wim Osterholt
On Thu, Nov 17, 2016 at 02:57:33AM +0100, Wim Osterholt wrote: > Now a retry of 4.9-rc5. I take the config of 4.8.8 and accept > the default for the new options. > SMP set. No call trace appears. > For completeness I should also try with SMP unset. That is for tomorrow > then. With CONFIG_SMP

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-11-16 Thread Wim Osterholt
On Wed, Nov 16, 2016 at 04:07:57PM +0100, Wim Osterholt wrote: > A bit of patience please. Yesterday I hadn't the modem at hand. Whell, I lost track of what happens where with which config file.. Confusion about the bug not appearing an too many configs with SMP set where I'm sure the machine(s)

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-11-16 Thread Wim Osterholt
On Wed, Nov 16, 2016 at 04:07:57PM +0100, Wim Osterholt wrote: > A bit of patience please. Yesterday I hadn't the modem at hand. Whell, I lost track of what happens where with which config file.. Confusion about the bug not appearing an too many configs with SMP set where I'm sure the machine(s)

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-11-16 Thread Wim Osterholt
On Wed, Nov 16, 2016 at 01:34:30PM +0100, Oliver Neukum wrote: > > This is very odd. We need to know where it crashes. Please try the > insane debug patch I posted. A bit of patience please. Yesterday I hadn't the modem at hand. Groeten, Wim.

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-11-16 Thread Wim Osterholt
On Wed, Nov 16, 2016 at 01:34:30PM +0100, Oliver Neukum wrote: > > This is very odd. We need to know where it crashes. Please try the > insane debug patch I posted. A bit of patience please. Yesterday I hadn't the modem at hand. Groeten, Wim.

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-11-16 Thread Oliver Neukum
On Tue, 2016-11-15 at 14:29 +0100, Wim Osterholt wrote: > I experience a sliding scale. > With debug it crashes immediately. It may crash later on (even at shutdown > time). It's not even an oops but a warning. In the end it happens to just > work. This is very odd. We need to know where it

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-11-16 Thread Oliver Neukum
On Tue, 2016-11-15 at 14:29 +0100, Wim Osterholt wrote: > I experience a sliding scale. > With debug it crashes immediately. It may crash later on (even at shutdown > time). It's not even an oops but a warning. In the end it happens to just > work. This is very odd. We need to know where it

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-11-15 Thread Wim Osterholt
On Tue, Nov 15, 2016 at 12:26:00PM +0100, poma wrote: > > In the process of searching, many options may have changed. The crash/OOPS > > has now mitigated into just a WARNING with a call trace. > > (Or it could be a totally different bug?) > > > > Tests on other machines with (slightly) different

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-11-15 Thread Wim Osterholt
On Tue, Nov 15, 2016 at 12:26:00PM +0100, poma wrote: > > In the process of searching, many options may have changed. The crash/OOPS > > has now mitigated into just a WARNING with a call trace. > > (Or it could be a totally different bug?) > > > > Tests on other machines with (slightly) different

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-11-15 Thread poma
On 15.11.2016 01:16, Wim Osterholt wrote: > On Tue, Oct 18, 2016 at 02:18:43PM +0200, Oliver Neukum wrote: > >> It definitely does not crash and is probed and your .config is not >> extremely unusual. > > Hmmm. > >> ... Something odd is going on. > > Whell, yes. > The only thing that appears

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-11-15 Thread poma
On 15.11.2016 01:16, Wim Osterholt wrote: > On Tue, Oct 18, 2016 at 02:18:43PM +0200, Oliver Neukum wrote: > >> It definitely does not crash and is probed and your .config is not >> extremely unusual. > > Hmmm. > >> ... Something odd is going on. > > Whell, yes. > The only thing that appears

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-11-15 Thread Oliver Neukum
On Tue, 2016-11-15 at 01:16 +0100, Wim Osterholt wrote: Hi, > Whell, yes. > The only thing that appears you'll have to do is unset 'CONFIG_SMP'. OK. I haven't tested that, nor would I ever considered it. > My machines didn't have the luxury of multicore processors (until recently), > so there

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-11-15 Thread Oliver Neukum
On Tue, 2016-11-15 at 01:16 +0100, Wim Osterholt wrote: Hi, > Whell, yes. > The only thing that appears you'll have to do is unset 'CONFIG_SMP'. OK. I haven't tested that, nor would I ever considered it. > My machines didn't have the luxury of multicore processors (until recently), > so there

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-11-14 Thread Wim Osterholt
On Tue, Oct 18, 2016 at 02:18:43PM +0200, Oliver Neukum wrote: > It definitely does not crash and is probed and your .config is not > extremely unusual. Hmmm. > ... Something odd is going on. Whell, yes. The only thing that appears you'll have to do is unset 'CONFIG_SMP'. My machines didn't

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-11-14 Thread Wim Osterholt
On Tue, Oct 18, 2016 at 02:18:43PM +0200, Oliver Neukum wrote: > It definitely does not crash and is probed and your .config is not > extremely unusual. Hmmm. > ... Something odd is going on. Whell, yes. The only thing that appears you'll have to do is unset 'CONFIG_SMP'. My machines didn't

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-11-05 Thread Wim Osterholt
On Tue, Oct 18, 2016 at 02:18:43PM +0200, Oliver Neukum wrote: > On Mon, 2016-10-17 at 17:20 +0200, Wim Osterholt wrote: > > 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

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-11-05 Thread Wim Osterholt
On Tue, Oct 18, 2016 at 02:18:43PM +0200, Oliver Neukum wrote: > On Mon, 2016-10-17 at 17:20 +0200, Wim Osterholt wrote: > > 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

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-10-18 Thread Wim Osterholt
On Tue, Oct 18, 2016 at 02:18:43PM +0200, Oliver Neukum wrote: > Oct 18 14:05:07 linux-dtbq.site kernel: usb 1-9: Manufacturer: Conexant > Oct 18 14:05:07 linux-dtbq.site kernel: usb 1-9: SerialNumber: 12345678 With that unique serial number it must be that very device. :-) > It definitely does

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-10-18 Thread Wim Osterholt
On Tue, Oct 18, 2016 at 02:18:43PM +0200, Oliver Neukum wrote: > Oct 18 14:05:07 linux-dtbq.site kernel: usb 1-9: Manufacturer: Conexant > Oct 18 14:05:07 linux-dtbq.site kernel: usb 1-9: SerialNumber: 12345678 With that unique serial number it must be that very device. :-) > It definitely does

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-10-18 Thread Oliver Neukum
On Mon, 2016-10-17 at 17:20 +0200, Wim Osterholt wrote: > 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

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-10-18 Thread Oliver Neukum
On Mon, 2016-10-17 at 17:20 +0200, Wim Osterholt wrote: > 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

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-10-17 Thread Wim Osterholt
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

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-10-17 Thread Wim Osterholt
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

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-10-17 Thread Oliver Neukum
On Thu, 2016-09-08 at 14:58 +0200, Wim Osterholt wrote: > On Thu, Sep 08, 2016 at 02:20:38PM +0200, Oliver Neukum wrote: > > > > > > The oops tells things that I didn't all write down, but it says > > > null pointer dereference at 0246 > > > > That is the important part. I am sorry, but

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-10-17 Thread Oliver Neukum
On Thu, 2016-09-08 at 14:58 +0200, Wim Osterholt wrote: > On Thu, Sep 08, 2016 at 02:20:38PM +0200, Oliver Neukum wrote: > > > > > > The oops tells things that I didn't all write down, but it says > > > null pointer dereference at 0246 > > > > That is the important part. I am sorry, but

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-10-06 Thread Oliver Neukum
On Thu, 2016-09-29 at 15:26 +0200, Wim Osterholt wrote: > On Wed, Sep 28, 2016 at 05:23:30PM +0200, Oliver Neukum wrote: > > > > > > HP src # sync > > > HP src # [ 3744.914184] BUG: unable to handle kernel NULL pointer > > > dereference at 0249 > > > > The last view lines before that please

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-10-06 Thread Oliver Neukum
On Thu, 2016-09-29 at 15:26 +0200, Wim Osterholt wrote: > On Wed, Sep 28, 2016 at 05:23:30PM +0200, Oliver Neukum wrote: > > > > > > HP src # sync > > > HP src # [ 3744.914184] BUG: unable to handle kernel NULL pointer > > > dereference at 0249 > > > > The last view lines before that please

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-09-29 Thread Wim Osterholt
On Wed, Sep 28, 2016 at 05:23:30PM +0200, Oliver Neukum wrote: > > > > HP src # sync > > HP src # [ 3744.914184] BUG: unable to handle kernel NULL pointer > > dereference at 0249 > > The last view lines before that please with the debugging level ramped > up to 9 please. Recompiled again,

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-09-29 Thread Wim Osterholt
On Wed, Sep 28, 2016 at 05:23:30PM +0200, Oliver Neukum wrote: > > > > HP src # sync > > HP src # [ 3744.914184] BUG: unable to handle kernel NULL pointer > > dereference at 0249 > > The last view lines before that please with the debugging level ramped > up to 9 please. Recompiled again,

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-09-28 Thread Wim Osterholt
On Wed, Sep 28, 2016 at 11:16:04AM +0200, Oliver Neukum wrote: > this should show you where it crashes. In addition I've attached > a patch with paranoid debugging. Could you compile and test a kernel > with it? > > Regards > Oliver If you mean echo "module cdc_acm +mpf" >

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-09-28 Thread Wim Osterholt
On Wed, Sep 28, 2016 at 11:16:04AM +0200, Oliver Neukum wrote: > this should show you where it crashes. In addition I've attached > a patch with paranoid debugging. Could you compile and test a kernel > with it? > > Regards > Oliver If you mean echo "module cdc_acm +mpf" >

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-09-28 Thread Oliver Neukum
On Wed, 2016-09-28 at 17:08 +0200, Wim Osterholt wrote: > On Wed, Sep 28, 2016 at 11:16:04AM +0200, Oliver Neukum wrote: > > this should show you where it crashes. In addition I've attached > > a patch with paranoid debugging. Could you compile and test a kernel > > with it? > > > > Regards >

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-09-28 Thread Oliver Neukum
On Wed, 2016-09-28 at 17:08 +0200, Wim Osterholt wrote: > On Wed, Sep 28, 2016 at 11:16:04AM +0200, Oliver Neukum wrote: > > this should show you where it crashes. In addition I've attached > > a patch with paranoid debugging. Could you compile and test a kernel > > with it? > > > > Regards >

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-09-28 Thread Wim Osterholt
On Wed, Sep 28, 2016 at 11:16:04AM +0200, Oliver Neukum wrote: > > Very good. This is a valid oops. We can do two things. When I > decode it, seems to crash in acm_alloc_minor() which does not make > sense. It is likely that our kernels or compilers are a bit different. > Could you please call

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-09-28 Thread Wim Osterholt
On Wed, Sep 28, 2016 at 11:16:04AM +0200, Oliver Neukum wrote: > > Very good. This is a valid oops. We can do two things. When I > decode it, seems to crash in acm_alloc_minor() which does not make > sense. It is likely that our kernels or compilers are a bit different. > Could you please call

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-09-28 Thread Oliver Neukum
On Tue, 2016-09-27 at 18:34 +0200, Wim Osterholt wrote: > On Thu, Sep 22, 2016 at 04:40:50PM +0200, Oliver Neukum wrote: > > > > dmesg -c > > echo 9 > /proc/sysrq-trigger > > modprobe cdc_acm > > echo "module cdc_acm +mpf" > /sys/kernel/debug/dynamic_debug/control > > > > [plug your device in] >

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-09-28 Thread Oliver Neukum
On Tue, 2016-09-27 at 18:34 +0200, Wim Osterholt wrote: > On Thu, Sep 22, 2016 at 04:40:50PM +0200, Oliver Neukum wrote: > > > > dmesg -c > > echo 9 > /proc/sysrq-trigger > > modprobe cdc_acm > > echo "module cdc_acm +mpf" > /sys/kernel/debug/dynamic_debug/control > > > > [plug your device in] >

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-09-27 Thread Wim Osterholt
On Thu, Sep 22, 2016 at 04:40:50PM +0200, Oliver Neukum wrote: > > dmesg -c > echo 9 > /proc/sysrq-trigger > modprobe cdc_acm > echo "module cdc_acm +mpf" > /sys/kernel/debug/dynamic_debug/control > > [plug your device in] > > and provide the full output of dmesg after that. After some

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-09-27 Thread Wim Osterholt
On Thu, Sep 22, 2016 at 04:40:50PM +0200, Oliver Neukum wrote: > > dmesg -c > echo 9 > /proc/sysrq-trigger > modprobe cdc_acm > echo "module cdc_acm +mpf" > /sys/kernel/debug/dynamic_debug/control > > [plug your device in] > > and provide the full output of dmesg after that. After some

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-09-23 Thread Wim Osterholt
On Thu, Sep 22, 2016 at 04:40:50PM +0200, Oliver Neukum wrote: > > dmesg -c > echo 9 > /proc/sysrq-trigger > modprobe cdc_acm > echo "module cdc_acm +mpf" > /sys/kernel/debug/dynamic_debug/control > > [plug your device in] > > and provide the full output of dmesg after that. That is not

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-09-23 Thread Wim Osterholt
On Thu, Sep 22, 2016 at 04:40:50PM +0200, Oliver Neukum wrote: > > dmesg -c > echo 9 > /proc/sysrq-trigger > modprobe cdc_acm > echo "module cdc_acm +mpf" > /sys/kernel/debug/dynamic_debug/control > > [plug your device in] > > and provide the full output of dmesg after that. That is not

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-09-22 Thread Wim Osterholt
On Thu, Sep 22, 2016 at 04:40:50PM +0200, Oliver Neukum wrote: > OK. Strange. Please do > > dmesg -c > echo 9 > /proc/sysrq-trigger > modprobe cdc_acm > echo "module cdc_acm +mpf" > /sys/kernel/debug/dynamic_debug/control > > [plug your device in] > > and provide the full output of dmesg after

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-09-22 Thread Wim Osterholt
On Thu, Sep 22, 2016 at 04:40:50PM +0200, Oliver Neukum wrote: > OK. Strange. Please do > > dmesg -c > echo 9 > /proc/sysrq-trigger > modprobe cdc_acm > echo "module cdc_acm +mpf" > /sys/kernel/debug/dynamic_debug/control > > [plug your device in] > > and provide the full output of dmesg after

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-09-22 Thread Wim Osterholt
> >Please look up the bConfigurationValue for your device > >in sysfs. I didn't explicitly say that this was done under kernel-4.7.4, otherwise it may have been impossible under 4.8 . On Thu, Sep 22, 2016 at 04:40:50PM +0200, Oliver Neukum wrote: > > OK. Strange. Please do > > dmesg -c >

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-09-22 Thread Wim Osterholt
> >Please look up the bConfigurationValue for your device > >in sysfs. I didn't explicitly say that this was done under kernel-4.7.4, otherwise it may have been impossible under 4.8 . On Thu, Sep 22, 2016 at 04:40:50PM +0200, Oliver Neukum wrote: > > OK. Strange. Please do > > dmesg -c >

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-09-22 Thread Oliver Neukum
On Wed, 2016-09-21 at 18:41 +0200, Wim Osterholt wrote: > On Wed, Sep 21, 2016 at 02:21:17PM +0200, Oliver Neukum wrote: > > in sysfs. > > Google pointed me to /sys/bus/usb/drivers/usb/* > where I find all kinds of 'bConfigurationValue'. > Now is the problem to find which one you could mean. > >

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-09-22 Thread Oliver Neukum
On Wed, 2016-09-21 at 18:41 +0200, Wim Osterholt wrote: > On Wed, Sep 21, 2016 at 02:21:17PM +0200, Oliver Neukum wrote: > > in sysfs. > > Google pointed me to /sys/bus/usb/drivers/usb/* > where I find all kinds of 'bConfigurationValue'. > Now is the problem to find which one you could mean. > >

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-09-21 Thread Wim Osterholt
On Wed, Sep 21, 2016 at 02:21:17PM +0200, Oliver Neukum wrote: > in sysfs. Google pointed me to /sys/bus/usb/drivers/usb/* where I find all kinds of 'bConfigurationValue'. Now is the problem to find which one you could mean. Under /sys/bus/usb/drivers/usb/7-1 I find manufacturer which reads

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-09-21 Thread Wim Osterholt
On Wed, Sep 21, 2016 at 02:21:17PM +0200, Oliver Neukum wrote: > in sysfs. Google pointed me to /sys/bus/usb/drivers/usb/* where I find all kinds of 'bConfigurationValue'. Now is the problem to find which one you could mean. Under /sys/bus/usb/drivers/usb/7-1 I find manufacturer which reads

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-09-21 Thread Wim Osterholt
On Wed, Sep 21, 2016 at 02:21:17PM +0200, Oliver Neukum wrote: > On Tue, 2016-09-20 at 17:45 +0200, Wim Osterholt wrote: > > Anyway, which of its configurations is used? > Please look up the bConfigurationValue for your device > in sysfs. And what might that be? 'locate sysfs' gives one hit at

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-09-21 Thread Wim Osterholt
On Wed, Sep 21, 2016 at 02:21:17PM +0200, Oliver Neukum wrote: > On Tue, 2016-09-20 at 17:45 +0200, Wim Osterholt wrote: > > Anyway, which of its configurations is used? > Please look up the bConfigurationValue for your device > in sysfs. And what might that be? 'locate sysfs' gives one hit at

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-09-21 Thread Oliver Neukum
On Tue, 2016-09-20 at 17:45 +0200, Wim Osterholt wrote: > On Tue, Sep 20, 2016 at 03:05:14PM +0200, Oliver Neukum wrote: > > > > I cannot replicate it. Could you please provide "lsusb -v"? > > > > Regards > > Oliver > > It concerns these type of modems: >

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-09-21 Thread Oliver Neukum
On Tue, 2016-09-20 at 17:45 +0200, Wim Osterholt wrote: > On Tue, Sep 20, 2016 at 03:05:14PM +0200, Oliver Neukum wrote: > > > > I cannot replicate it. Could you please provide "lsusb -v"? > > > > Regards > > Oliver > > It concerns these type of modems: >

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-09-20 Thread Wim Osterholt
On Tue, Sep 20, 2016 at 03:05:14PM +0200, Oliver Neukum wrote: > > I cannot replicate it. Could you please provide "lsusb -v"? > > Regards > Oliver It concerns these type of modems: http://www.ebay.nl/itm/191933738340 http://www.ebay.nl/itm/121590899044 lsusb: Bus 002

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-09-20 Thread Wim Osterholt
On Tue, Sep 20, 2016 at 03:05:14PM +0200, Oliver Neukum wrote: > > I cannot replicate it. Could you please provide "lsusb -v"? > > Regards > Oliver It concerns these type of modems: http://www.ebay.nl/itm/191933738340 http://www.ebay.nl/itm/121590899044 lsusb: Bus 002

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-09-20 Thread Oliver Neukum
On Mon, 2016-09-12 at 04:43 +0200, Wim Osterholt wrote: > > A laptop, more broken than the rest, does not output anything after > inserting. Later on it crashes. No system.map file in /boot. > After booting with the dongle inserted it spits out: I cannot replicate it. Could you please provide

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-09-20 Thread Oliver Neukum
On Mon, 2016-09-12 at 04:43 +0200, Wim Osterholt wrote: > > A laptop, more broken than the rest, does not output anything after > inserting. Later on it crashes. No system.map file in /boot. > After booting with the dongle inserted it spits out: I cannot replicate it. Could you please provide

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-09-11 Thread Wim Osterholt
On Thu, Sep 08, 2016 at 03:05:15PM +0200, Oliver Neukum wrote: > > your stack trace is broken. Did you fail to install the System.map file? > > Regards > Oliver A laptop, more broken than the rest, does not output anything after inserting. Later on it crashes. No system.map

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-09-11 Thread Wim Osterholt
On Thu, Sep 08, 2016 at 03:05:15PM +0200, Oliver Neukum wrote: > > your stack trace is broken. Did you fail to install the System.map file? > > Regards > Oliver A laptop, more broken than the rest, does not output anything after inserting. Later on it crashes. No system.map

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-09-09 Thread Wim Osterholt
> your stack trace is broken. Did you fail to install the System.map file? > > Regards > Oliver >Finally found something. >CONFIG_DEBUG_INFO was not set. Doesn't make any difference either. Compiled cdc_acm in the kernel, not as a module. Doesn't make any difference, except

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-09-09 Thread Wim Osterholt
> your stack trace is broken. Did you fail to install the System.map file? > > Regards > Oliver >Finally found something. >CONFIG_DEBUG_INFO was not set. Doesn't make any difference either. Compiled cdc_acm in the kernel, not as a module. Doesn't make any difference, except

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-09-08 Thread Wim Osterholt
On Thu, Sep 08, 2016 at 03:05:15PM +0200, Oliver Neukum wrote: > > Sep 6 19:12:38 localhost kernel: Call Trace: > > Sep 6 19:12:38 localhost kernel: [] ? 0xc01f4347 > > Hi, > > your stack trace is broken. Did you fail to install the System.map file? Source is available under /usr/src/linux

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-09-08 Thread Wim Osterholt
On Thu, Sep 08, 2016 at 03:05:15PM +0200, Oliver Neukum wrote: > > Sep 6 19:12:38 localhost kernel: Call Trace: > > Sep 6 19:12:38 localhost kernel: [] ? 0xc01f4347 > > Hi, > > your stack trace is broken. Did you fail to install the System.map file? Source is available under /usr/src/linux

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-09-08 Thread Wim Osterholt
On Thu, Sep 08, 2016 at 03:05:15PM +0200, Oliver Neukum wrote: > > Sep 6 19:12:38 localhost kernel: Call Trace: > > Sep 6 19:12:38 localhost kernel: [] ? 0xc01f4347 > > Hi, > > your stack trace is broken. Did you fail to install the System.map file? Never needed that for anything the last 20

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-09-08 Thread Wim Osterholt
On Thu, Sep 08, 2016 at 03:05:15PM +0200, Oliver Neukum wrote: > > Sep 6 19:12:38 localhost kernel: Call Trace: > > Sep 6 19:12:38 localhost kernel: [] ? 0xc01f4347 > > Hi, > > your stack trace is broken. Did you fail to install the System.map file? Never needed that for anything the last 20

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-09-08 Thread Oliver Neukum
On Thu, 2016-09-08 at 14:58 +0200, Wim Osterholt wrote: > On Thu, Sep 08, 2016 at 02:20:38PM +0200, Oliver Neukum wrote: > > > > > > The oops tells things that I didn't all write down, but it says > > > null pointer dereference at 0246 > > > > That is the important part. I am sorry, but

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-09-08 Thread Oliver Neukum
On Thu, 2016-09-08 at 14:58 +0200, Wim Osterholt wrote: > On Thu, Sep 08, 2016 at 02:20:38PM +0200, Oliver Neukum wrote: > > > > > > The oops tells things that I didn't all write down, but it says > > > null pointer dereference at 0246 > > > > That is the important part. I am sorry, but

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-09-08 Thread Wim Osterholt
On Thu, Sep 08, 2016 at 02:20:38PM +0200, Oliver Neukum wrote: > > > > The oops tells things that I didn't all write down, but it says > > null pointer dereference at 0246 > > That is the important part. I am sorry, but without the oops > nobody can help you. Please capture it Sep 6

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-09-08 Thread Wim Osterholt
On Thu, Sep 08, 2016 at 02:20:38PM +0200, Oliver Neukum wrote: > > > > The oops tells things that I didn't all write down, but it says > > null pointer dereference at 0246 > > That is the important part. I am sorry, but without the oops > nobody can help you. Please capture it Sep 6

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-09-08 Thread Oliver Neukum
On Thu, 2016-09-08 at 13:58 +0200, Wim Osterholt wrote: > L.S. > > up to vanilla kernel 4.7.3 I've seen no problems. > On two different dekstops running vanilla kernel-4.8 I can force a > crash by > inserting an USB-modem that requires module cdc_acm.ko . > (Strangely enough that doesn't happen

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-09-08 Thread Oliver Neukum
On Thu, 2016-09-08 at 13:58 +0200, Wim Osterholt wrote: > L.S. > > up to vanilla kernel 4.7.3 I've seen no problems. > On two different dekstops running vanilla kernel-4.8 I can force a > crash by > inserting an USB-modem that requires module cdc_acm.ko . > (Strangely enough that doesn't happen