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 h
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
> communi
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
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 ousid
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
> > dereferenc
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 d
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.
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
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.
--
To unsubscribe from this list: send the line "uns
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
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 ha
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&#
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 n
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
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, d
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" > /
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 gdb
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 experime
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 possibl
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 t
> >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
> echo
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 'Co
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 sys
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 Device
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 f
> 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 f
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 --
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
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 19:12:3
t I didn't all write down, but it says
null pointer dereference at 0246
...
failed while handling devices/pci:00/:00:1d.3/usb7/7-1/7-1:1d etc.
...
udevd .. is taking too long..
Could someone please explain and repair the magic that is happening here?
Thanks in advance, Wim Osterhol
30 matches
Mail list logo
