On Thu, 2016-10-20 at 10:29 -0600, Jonathan Corbet wrote:
> On Thu, 20 Oct 2016 18:22:28 +0200
> Oliver Neukum wrote:
>
> > > Why does this not remove the .tmpl file?
> >
> > 1. We might want to keep it
> > 2. It is an operation beyond the scope of this
it looks like your patch #2 should also go into stable.
Regards
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Fri, 2016-10-21 at 15:17 -0600, Jonathan Corbet wrote:
> On Thu, 20 Oct 2016 15:15:00 +0200
> Oliver Neukum wrote:
>
> > It does no good to mention The 2.4 kernel series and neglect
> > USB 3.x and XHCI. Also with type C and micro/mini USB we better
> > not talk ab
On Thu, 2016-10-20 at 18:04 +0300, Jani Nikula wrote:
> On Thu, 20 Oct 2016, Oliver Neukum wrote:
Hi,
> > This just is the result of the conversion script and its addition
> > to the index. Just the plain automatic conversion.
>
> How does this relate to [1]?
It is the
This just is the result of the conversion script and its addition
to the index. Just the plain automatic conversion.
Signed-off-by: Oliver Neukum
---
Documentation/index.rst | 1 +
Documentation/usb/conf.py | 5 +
Documentation/usb/usb.rst | 750
It does no good to mention The 2.4 kernel series and neglect
USB 3.x and XHCI. Also with type C and micro/mini USB we better
not talk about the shape of connectors.
Signed-off-by: Oliver Neukum
---
Documentation/DocBook/usb.tmpl | 68 +++---
1 file changed
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?
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
> >
> &
On Fri, 2016-10-14 at 01:16 +0100, Snaper wrote:
> Hi Oliver,
>
> On 10/10/2016 08:19, Oliver Neukum wrote:
> > it is very hard for us to say something about that specific kernel.
> > We don't know the kernel tree. And the error seems to be in the OF
> > code. I
tree. And the error seems to be in the OF
code. I think you are in the wrong list, or can you reproduce
teh problem with a mainline kernel?
Regards
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a messa
ee whether
he reads this list.
Regards
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
one,
> plese advise me which one.
Hi,
patches need to go to the maintainer and the list. Please repost
them to the list and if the maintainer still doesnät answer we will
need to bother Greg.
HTH
Oliver
--
To unsubscribe from this list: send the line "unsubscr
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
> >
and do an
independent post and all will be well.
HTH
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
k
that specific combination. But why put the code for a potentially
common problem into xhci?
Regards
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Wed, 2016-10-05 at 10:29 +0200, Stefan Tauner wrote:
> On Wed, 05 Oct 2016 09:31:29 +0200
> Oliver Neukum wrote:
>
> > On Fri, 2016-09-30 at 17:39 +0200, Stefan Tauner wrote:
> > > Signed-off-by: Stefan Tauner
> >
> > A minimal change log entry w
On Fri, 2016-09-30 at 17:39 +0200, Stefan Tauner wrote:
> Signed-off-by: Stefan Tauner
A minimal change log entry would be good.
Regards
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vg
Hi,
does anybody here want to test patches to improve UAS error
handling?
Regards
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.
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
> > wit
need to check "zombie" in open() or you open up to another
race.
Regards
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
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/dy
On Mon, 2016-09-26 at 18:57 +0100, Malcolm Priestley wrote:
>
> On 26/09/16 09:48, Oliver Neukum wrote:
> > On Sat, 2016-09-24 at 01:21 +0100, Malcolm Priestley wrote:
> >>
> >> On 22/09/16 20:50, Malcolm Priestley wrote:
> >>>
> >>>
>
.c
open
Is that correct? And do we need more fixes for the stable trees?
Regards
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Sat, 2016-09-24 at 01:21 +0100, Malcolm Priestley wrote:
>
> On 22/09/16 20:50, Malcolm Priestley wrote:
> >
> >
> > On 22/09/16 15:25, Oliver Neukum wrote:
> >> On Thu, 2016-09-22 at 14:46 +0300, Binyamin Sharet wrote:
> >>
> >>>> -- B
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 t
tch?
Regards
Oliver
From e0f6d09babd9f30d952389ff98a2a25df9a158a5 Mon Sep 17 00:00:00 2001
From: Oliver Neukum
Date: Thu, 22 Sep 2016 16:22:06 +0200
Subject: [PATCH] vt6656: avoid double free
This data structure is fred in disconnect(). It must not
be freed earlier.
Signed-off-by: Oliver
On Wed, 2016-09-21 at 10:35 -0400, Alan Stern wrote:
> On Wed, 21 Sep 2016, Oliver Neukum wrote:
> > Yes, but this is not the point. A heuristic with a timeout makes
> > sense only if the uses are unpredictable. If you know with a high
> > degree of probability when the nex
On Thu, 2016-09-22 at 14:46 +0300, Binyamin Sharet wrote:
> On Thu, Sep 22, 2016 at 11:18 AM, Binyamin Sharet
> wrote:
> > On Thu, Sep 22, 2016 at 11:02 AM, Oliver Neukum wrote:
> >> On Thu, 2016-09-22 at 10:50 +0300, Binyamin Sharet wrote:
> >>> On Thu, Sep 22
On Thu, 2016-09-22 at 10:50 +0300, Binyamin Sharet wrote:
> On Thu, Sep 22, 2016 at 10:35 AM, Oliver Neukum wrote:
> > On Thu, 2016-09-22 at 09:53 +0300, Binyamin Sharet wrote:
> >> On Wed, Sep 21, 2016 at 11:09 PM, Malcolm Priestley
> >> wrote:
> >> >
&g
you prepare a test kernel
without BPF?
Regards
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Thu, 2016-08-18 at 13:50 +0300, Binyamin Sharet wrote:
> On 08/18/2016 01:31 PM, Oliver Neukum wrote:
> > On Wed, 2016-08-17 at 14:34 +0300, Binyamin Sharet wrote:
> >>> After connecting such a device, NULL pointer dereference in the
> >> kernel.
> >>>
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 concer
On Tue, 2016-09-20 at 10:12 -0400, Alan Stern wrote:
> On Tue, 20 Sep 2016, Oliver Neukum wrote:
> That shouldn't be an issue in this case, at least, not with the current
> code. The sdmmc and memstick drivers block autosuspend if media is
> present.
Good.
>
&g
This should fix the last holes against malicious devices
still open in cdc-acm. It cannot go into stable due to
the introduction of the common parser.
The fix for stable already merged also covers the problems this patch
fixes.
Signed-off-by: Oliver Neukum
---
drivers/usb/class/cdc-acm.c | 5
ease provide "lsusb -v"?
Regards
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
to activate child device host6 but parent
> (2-1.2:1.0) is not active
I see no obvious culprit. Could you bisect?
Regards
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.o
mmediately suspended. The timer
is sensible only if the next wakeup is unknown.
Regards
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Tue, 2016-09-20 at 20:58 +1200, Pierre de Villemereuil wrote:
> Hi Oliver!
>
> Here you are.
>
> dmesg signals when plugging AC in:
> http://paste.opensuse.org/57485b34
>
> dmesg signals when unplugging AC:
> http://paste.opensuse.org/5a8e9910
>
> And
o debugs and it doesn't appear
> in the logs), but I enabled cdc_acm debugs. Nothing is observable in the
> logs when the bug appears. I logged everything as a comment of the gist:
> https://gist.github.com/Julio-Guerra/b6529994f814771c825649bdb8d927c2#gistcomment-1875985
>
&g
On Tue, 2016-09-20 at 11:11 +1200, Pierre de Villemereuil wrote:
> Dear Oliver,
>
> Sorry about my last message, the bug is actually still going on. I found
> something interesting though: when AC is plugged, USB is working totally OK,
> but when on battery, then here comes t
for you?
As far as I can tell, your patches are identical.
Regards
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
hat happens if you unload and
reload the xhci_hcd modules?
And please do
echo "module xhci_hcd +mpf" > /sys/kernel/debug/dynamic_debug/control
(as root) and check dmesg again.
Regards
Oliver
--
To unsubscribe from this list: send the line "unsubscribe lin
On Wed, 2016-09-14 at 15:22 +0300, c400 wrote:
> may be i can help to test something else? I am ready and have enough free time
You may need to mount debugfs at /sys/kernel/debug
HTH
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-usb
Actually make it retutn useful information.
Signed-off-by: Oliver Neukum
---
drivers/usb/class/cdc-acm.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/usb/class/cdc-acm.c b/drivers/usb/class/cdc-acm.c
index fef0d8f..faab151 100644
--- a/drivers/usb/class
Further cleanup making the debug messages more precise, useful
and removing mere trace points.
Signed-off-by: Oliver Neukum
---
drivers/usb/class/cdc-acm.c | 16 ++--
1 file changed, 6 insertions(+), 10 deletions(-)
diff --git a/drivers/usb/class/cdc-acm.c b/drivers/usb/class/cdc
On Fri, 2016-09-09 at 14:15 +0200, Greg KH wrote:
> On Wed, Sep 07, 2016 at 02:30:02PM +0200, Oliver Neukum wrote:
> > Actually make it retutn useful information.
> >
> > Signed-off-by: Oliver Neukum
> > ---
> > drivers/usb/class/cdc-acm.c | 8
> &
Some SATA to USB bridges fail to cooperate with some
drives resulting in no cache being present being reported
to the host. That causes the host to skip sending
a command to synchronize caches. That causes data loss
when the drive is powered down.
Signed-off-by: Oliver Neukum
Reviewed-by: Martin
On Fri, 2016-09-09 at 04:03 +0300, Dmitry Gutov wrote:
> On 06.09.2016 12:56, Oliver Neukum wrote:
>
> > Could you apply the attached patch,
>
> Thanks, will do as soon as I have a chance to reboot.
>
> > enable SCSI logging (with
> > scsi_logging_level) a
for the phy. What is unacceptable is to override
the configuration mechanism in the kernel.
Regards
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
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
> >
> &
help you. Please capture it
dmesg > /root/oops.txt
and report it.
Regards
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Thu, 2016-08-18 at 22:19 -0400, Martin K. Petersen wrote:
> >>>>> "Oliver" == Oliver Neukum writes:
>
> Oliver> Some SATA to USB bridges fail to cooperate with some drives
> Oliver> resulting in no cache being present being reported to the
> Oliv
Actually make it retutn useful information.
Signed-off-by: Oliver Neukum
---
drivers/usb/class/cdc-acm.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/usb/class/cdc-acm.c b/drivers/usb/class/cdc-acm.c
index ea7d361..7c21567 100644
--- a/drivers/usb/class
Some debug messages merely provide a function trace without
additional debug data. They predate ftrace and can be replaced
by it. Drop them without replacement.
Signed-off-by: Oliver Neukum
---
drivers/usb/class/cdc-acm.c | 20 +++-
1 file changed, 3 insertions(+), 17 deletions
Further cleanup making the debug messages more precise, useful
and removing mere trace points.
Signed-off-by: Oliver Neukum
---
drivers/usb/class/cdc-acm.c | 18 +++---
1 file changed, 7 insertions(+), 11 deletions(-)
diff --git a/drivers/usb/class/cdc-acm.c b/drivers/usb/class/cdc
at the
> > beginning.
>
> Here's an excerpt from the full log, from the very first message after
> I physically plugged in the drive:
Please use the
scsi_logging_level
tool to capture the error the drive reports.
Regards
Oliver
--
To unsubscribe from this l
On Mon, 2016-09-05 at 14:31 +0300, Dmitry Gutov wrote:
> On 05.09.2016 14:19, Oliver Neukum wrote:
>
> > You add the device to the kernel quirks list. But if
> > you don't use autosuspend, the point is moot.
>
> The device does get spinned down (after not using it f
On Mon, 2016-09-05 at 14:01 +0300, Dmitry Gutov wrote:
> On 05.09.2016 13:42, Oliver Neukum wrote:
>
> > This very much looks like power saving misbehaving.
>
> It does. But it doesn't seem like my distro enables autosuspend there by
> default.
>
> > Are y
power saving misbehaving.
Are you using autosuspend on this device?
Have you tried the RESET_RESUME quirk on the USB
level?
Regards
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Thu, 2016-09-01 at 10:21 +0800, Lu Baolu wrote:
> Hi Oliver,
>
> Thanks for review.
>
> On 08/31/2016 05:53 PM, Oliver Neukum wrote:
> > On Mon, 2016-08-29 at 13:26 +0800, Lu Baolu wrote:
> >> + /*
> >> +* Memory barrier to ensure hardware
On Wed, 2016-08-31 at 12:48 +0300, Binyamin Sharet wrote:
> Sure, but could you send me the cdc-acm.c file that this patch applies to?
> Otherwise I need to patch it manually each time...
Patch already applied.
HTH
Oliver
/*
* cdc-acm.c
*
* Copyright (c) 1999
ttySn[,baudrate]
> earlyprintk=dbgp[debugController#]
> earlyprintk=pciserial,bus:device.function[,baudrate]
> + earlyprintk=xdbc[xhciController#]
>
How is that defined? Should there be a PCI address?
Regards
else
> + trb->field[3] &= cpu_to_le32(~TRB_CYCLE);
And this manipulation you don't need the hardware to see?
Regards
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to ma
t line of code in skip_normal_probe) which may cause the
> first check to dereference
> a NULL pointer.
Hi,
could you test this updated patch?
Regards
Oliver
From 4274cf2a7f8bf0b97b6d5ecc27882b9d946bf7f0 Mon Sep 17 00:00:00 2001
From: Oliver Neukum
Date: Wed, 17
On Tue, 2016-08-30 at 13:04 +0300, Heikki Krogerus wrote:
> On Tue, Aug 30, 2016 at 11:32:01AM +0200, Oliver Neukum wrote:
Hi,
> > On Mon, 2016-08-29 at 15:36 +0300, Heikki Krogerus wrote:
> > > +What: /sys/class/typec//current_data_role
> > > +Date:
in your case,
albeit with a performance penalty. But the actual cause of kicking in
the error handler is missing in your log. You cut too much at the
beginning.
Regards
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a mess
te operation does not mean
> successful
> + swap.
> +
That is badly formulated. Does it mean that poll() or select()
can be used or does the value need to be repearedly read?
And how would you learn about an error?
Regards
Oliver
--
To unsubscribe from
> Hi Oliver,
>
> It will take me some time to test it on v4.4.6-v7, so I have tried applying
> the patch
> to v4.4 but it failed in the 4th hunk (line 47).
>
> Please advise, should I:
>
> - manually edit the file on v4.4 and retest?
Please do that.
Reg
On Thu, 2016-08-25 at 13:53 +, Binyamin Sharet (bsharet) wrote:
> >
> It’s a good thing you asked, as I forgot to test this one…
>
> Just to be sure - which tag should I use for testing this one?
> Is v4.4 OK?
Yes, perfect.
Thanks
Oliver
--
T
On Wed, 2016-08-17 at 15:26 +0200, Oliver Neukum wrote:
> On Tue, 2016-08-16 at 16:46 +0300, Binyamin Sharet wrote:
> > Kernel version: raspberrypi 4.4.6-v7+ #871
> > Driver source file: drivers/usb/class/cdc-acm.c
> > Umap2 command line: umap2vsscan -P -s 22b8:2d93
>
>
On Thu, 2016-08-25 at 12:07 +0200, Alban Bedel wrote:
> On Thu, 25 Aug 2016 11:16:36 +0200
> Oliver Neukum wrote:
>
> > On Wed, 2016-08-24 at 16:40 +0200, Alban Bedel wrote:
> > > On Wed, 24 Aug 2016 16:30:39 +0200
> > > Oliver Neukum wrote:
> > >
On Wed, 2016-08-24 at 16:40 +0200, Alban Bedel wrote:
> On Wed, 24 Aug 2016 16:30:39 +0200
> Oliver Neukum wrote:
>
> > On Wed, 2016-08-24 at 15:52 +0200, Alban Bedel wrote:
> > > + if (block != data)
> > > + kfree(block);
> >
tic int ssusb_mode_open(struct inode *inode, struct file *file)
> +{
> + return single_open(file, ssusb_mode_show, inode->i_private);
> +}
> +
> +static ssize_t ssusb_mode_write(struct file *file,
> + const char __user *ubuf, size_t count, loff_t *ppos)
> +{
> + st
(offset + i) >> 1,
> + AX_EEPROM_BLOCK >> 1,
> + AX_EEPROM_BLOCK, &block[i]);
> + }
> +
> + if (block != data)
> + kfree(block);
And if block == dta, what frees the memory?
Regards
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Wed, 2016-08-24 at 14:43 +0100, Richard van der Hoff wrote:
> On 24/08/16 13:17, Oliver Neukum wrote:
> > On Wed, 2016-08-24 at 11:27 +0100, Richard van der Hoff wrote:
> >> I'm having problems with a Plugable USB-C docking station, with my
> >> laptop, a De
me dmesg
> traces
> and lspci logs attached to that bug.
It looks like your initial diagnosis was correct. This is a PCI
issue. What did you do at 814s after boot?
Please don't just add a log without comments if you do something.
One cannot tell what happens in response to what.
he series?
Regards
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
finally times out. The fun
> part happens when I unplug the phone. I consistently get a kernel panic.
The HC has crashed thoroughly. Do other devices work after S3?
Regards
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the
and
> re-open() the device. The next read buffer is then correct.
>
Please activate dynamic debugging for the tty and cdc_acm driver.
We need to know where the corruption happens.
Regards
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
, either
a) remote wakeup is not requested
b) remote wakeup is requested and
I) the device supports it
II) the RESET_RESUME quirk is not set for the device
4) it is enabled in sysfs
HTH
Oliver
--
To unsubscribe from this lis
the usb payload
> "00 00 00 00 00 00 00 01".
Hi, how many bytes does read() return?
Regards
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Thu, 2016-08-18 at 15:41 +0300, Binyamin Sharet wrote:
> On 08/18/2016 12:12 PM, Oliver Neukum wrote:
> > On Thu, 2016-08-18 at 12:10 +0300, Binyamin Sharet wrote:
> >> On 08/18/2016 12:02 PM, Oliver Neukum wrote:
> >>> On Thu, 2016-08-18 at 12:03 +0300, Binyamin
t; << Attached: 9022_d483_dmesg_2.log >>
> > << Attached: 9022_d483_kernel.log >>
> kernel: 4.8-rc2
> result: reproduced
> attached an update dmesg log
>
Hi,
could you try the attached patch?
Regards
Oliver
From 7ac7f7f000b69c47a7012
m and I was not able to retrieve the dmesg log.
> I took a photo of the screen, should I send it as an attachment?
Yes, that is better than nothing at all.
Regards
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi,
I was wondering about the fate of this patch.
As it fixes a security issue it should even go into
atable and I fear it has been lost.
Regards
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message
On Thu, 2016-08-18 at 12:10 +0300, Binyamin Sharet wrote:
> On 08/18/2016 12:02 PM, Oliver Neukum wrote:
> > On Thu, 2016-08-18 at 12:03 +0300, Binyamin Sharet wrote:
> >> On 08/18/2016 11:37 AM, Oliver Neukum wrote:
> >>> On Wed, 2016-08-17 at 17:33 +0300, Binyamin
On Wed, 2016-08-17 at 17:33 +0300, Binyamin Sharet wrote:
> On 08/17/2016 05:19 PM, Oliver Neukum wrote:
> > On Wed, 2016-08-17 at 17:07 +0300, Binyamin Sharet wrote:
> >> Downloading firmware...
> >> Firmware loaded. I'll be back...
> >> probe of 1-1.1
kind.
>
> Where exactly would you like to see this implemented if it isn't going
> into those specific usbnet drivers?
Higher up. I'd prefer a flag to tell the network core that a driver
is unsure about the MAC and the core should deal with it.
Regards
point.
Hi,
a question on design. What happens if the system wants to suspend while
we are in the middle of a power negotiation?
Regards
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kerne
On Thu, 2016-08-18 at 10:11 +0300, Binyamin Sharet wrote:
> Hi,
>
> On 08/17/2016 04:26 PM, Oliver Neukum wrote:
> > On Tue, 2016-08-16 at 16:46 +0300, Binyamin Sharet wrote:
> >> Kernel version: raspberrypi 4.4.6-v7+ #871
> >> Driver source file: drivers/usb/c
USB disconnection, and the machine keeps working as
> before.
>
> If you have any suggestion on how to perform it better, I'd be very
> glad
> to hear.
The kaweth driver was loaded and performed as it should.
Whence did you get your kernel sources?
Regards
This fixes the oops discovered by the Umap2 project and Alan Stern.
The intf member needs to be set before the firmware is downloaded.
Signed-off-by: Oliver Neukum
---
drivers/net/usb/kaweth.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/net/usb/kaweth.c b
These patches fix an oops in firmware downloading and an oops due
to a memory allocation failure
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Just return an error upon failure.
Signed-off-by: Oliver Neukum
---
drivers/net/usb/kaweth.c | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/drivers/net/usb/kaweth.c b/drivers/net/usb/kaweth.c
index 37bf715..528b9c9 100644
--- a/drivers/net/usb/kaweth.c
+++ b/drivers
On Wed, 2016-08-17 at 15:15 +0200, Bjørn Mork wrote:
> Oliver Neukum writes:
> Eh, that should be "goto err_free_netdev;", shouldn't it?
Right, thanks. Fixed version coming up.
Regards
Oliver
--
To unsubscribe from this list: send the line "
n go into stable?
Regards
Oliver
From d741851d2b51a4693368487bc0046836b8458d98 Mon Sep 17 00:00:00 2001
From: Oliver Neukum
Date: Wed, 17 Aug 2016 15:19:28 +0200
Subject: [PATCH] cdc-acm: added sanity checking for probe()
This is analter
to majord...@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> kernel: 4.8-rc2
> result: not reproduced
>
>
This is getting odd. There have been no substantial changes to kaweth
between v4.4 and v4.8-rc2. I still think Alan's
Thanks
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
> and USB stops responding.
That was before a major rewrite of the parser. Could you retest
with v4.7?
Regards
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo inf
This fixes the oops discovered by the Umap2 project and Alan Stern.
The intf member needs to be set before the firmware is downloaded.
Signed-off-by: Oliver Neukum
---
drivers/net/usb/kaweth.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/net/usb/kaweth.c b
601 - 700 of 2090 matches
Mail list logo
