On 16.11.2015 17:25, Alan Stern wrote:
On Sun, 15 Nov 2015, Stéphane Lavergne wrote:
On Sat, Sep 12, 2015 at 4:08 AM, Hans-Peter Jansen wrote:
With some changes in the 4.0 time frame, AND an update of the epson iscan
stuff, I'm happily scanning with my Epson 4490 Photo
On Sun, 15 Nov 2015, Stéphane Lavergne wrote:
> On Sat, Sep 12, 2015 at 4:08 AM, Hans-Peter Jansen wrote:
> > With some changes in the 4.0 time frame, AND an update of the epson iscan
> > stuff, I'm happily scanning with my Epson 4490 Photo scanner plugged to a
> > USB
> > 3.0
On Sat, Sep 12, 2015 at 4:08 AM, Hans-Peter Jansen wrote:
> With some changes in the 4.0 time frame, AND an update of the epson iscan
> stuff, I'm happily scanning with my Epson 4490 Photo scanner plugged to a USB
> 3.0 port using xsane.
>
> Other USB 3.0 issues are currently
On Samstag, 20. Juni 2015 11:48:15 Stéphane Lavergne wrote:
> Hans-Peter Jansen writes:
> > just a heads up: retesting with 4.0.4 revealed, that this issue isn't
>
> fixed
>
> Thanks for the heads up; I'll stop trying to figure out the "clean" way to
> upgrade my Debian box that far
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear all,
Did just downgrade sane again in order to see if it really was the
combination of upgrading sane and the kernel. Seems like it only was
the kernel. Thanks again,
and kind regards,
Gunter.
On 04.07.2015 00:05, Gunter Königsmann wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear all,
I just retested with the following setup:
- linux kernel 4.1.1-040101 (stock kernel, vanilla flavour)
- The newest driver from Epson
- USB 3.0 enabled
- iscan-backends from git
- and the following line in a .rule file in
Hans-Peter Jansen hpj@... writes:
just a heads up: retesting with 4.0.4 revealed, that this issue isn't
fixed
Thanks for the heads up; I'll stop trying to figure out the clean way to
upgrade my Debian box that far ahead of their packages. :)
This behavior persists since Linux 3.16.x (where
Aww, that's too bad. Let me know if you'd like me to test a modified version
when you get the time.
--Mike Mammarella
On May 21, 2015, at 4:18 AM, Mathias Nyman wrote:
Hi
The fix went upstream, but caused regression for other users, and had to be
reverted.
The cause of the regression
Dear Mathias,
just a heads up: retesting with 4.0.4 revealed, that this issue isn't fixed
for my scanner still. To recap: driving the scanner through a ehci port is
fine, and fails miserably with xhci.
OK:
T: Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 4
D: Ver= 2.00
Hi
The fix went upstream, but caused regression for other users, and had to be
reverted.
The cause of the regression was found but the new version was never properly
tested and
got left behind as more urgent issues arrived.
I still need to attend a few other issues before taking up this again
On Dienstag, 24. Februar 2015 17:53:21 Hans-Peter Jansen wrote:
On Dienstag, 24. Februar 2015 17:53:25 Mathias Nyman wrote:
On 24.02.2015 12:41, Hans-Peter Jansen wrote:
Also 3.19-stable is still dangling..
Just sent it to Greg, with stable CC tags.
Thanks a lot, will test through
On Donnerstag, 19. Februar 2015 16:07:41 Mathias Nyman wrote:
On 18.02.2015 14:27, Hans-Peter Jansen wrote:
Mathias Nyman mathias.nyman@... writes:
On 27.01.2015 13:57, Hans-Peter Jansen wrote:
What about a stable backport? Do you think, it's feasible, too much
work, or too risky?
On 24.02.2015 12:41, Hans-Peter Jansen wrote:
On Donnerstag, 19. Februar 2015 16:07:41 Mathias Nyman wrote:
On 18.02.2015 14:27, Hans-Peter Jansen wrote:
Mathias Nyman mathias.nyman@... writes:
On 27.01.2015 13:57, Hans-Peter Jansen wrote:
What about a stable backport? Do you think, it's
On Dienstag, 24. Februar 2015 17:53:25 Mathias Nyman wrote:
On 24.02.2015 12:41, Hans-Peter Jansen wrote:
On Donnerstag, 19. Februar 2015 16:07:41 Mathias Nyman wrote:
On 18.02.2015 14:27, Hans-Peter Jansen wrote:
Mathias Nyman mathias.nyman@... writes:
On 27.01.2015 13:57, Hans-Peter
On 18.02.2015 14:27, Hans-Peter Jansen wrote:
Mathias Nyman mathias.nyman@... writes:
On 27.01.2015 13:57, Hans-Peter Jansen wrote:
What about a stable backport? Do you think, it's feasible, too much work, or
too risky?
This should definitely be backported to 3.18 stable, which should
Mathias Nyman mathias.nyman@... writes:
On 27.01.2015 13:57, Hans-Peter Jansen wrote:
What about a stable backport? Do you think, it's feasible, too much work, or
too risky?
This should definitely be backported to 3.18 stable, which should be easy.
Older longterms kernels are a
On 27.01.2015 14:12, Gunter Königsmann wrote:
That's very good news indeed.
Will re-run the tests on my scanner and looking forward to the fix entering
mainline. In the meantime I can acknowledge that with the fix my computer
accepts USB memory sticks that normally didn't work.
Kind
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Only in the hope that you might be able to do some additional magic
(but I won't be too disappointed if you tell that this time you have
already archieved enough) a fresh log for my scanner (that never
worked with USB-3.0 on my linux box and still
On Jan 29, 2015, at 8:42 AM, Mathias Nyman wrote:
On 27.01.2015 14:12, Gunter Königsmann wrote:
That's very good news indeed.
Will re-run the tests on my scanner and looking forward to the fix entering
mainline. In the meantime I can acknowledge that with the fix my computer
accepts USB
On Jan 22, 2015, at 7:23 AM, Mathias Nyman wrote:
I was doing this on your ep_reset_halt_test branch, which has a lot of
MATTU messages scrolling by, but I'm pretty sure that the microframe
rounding message was not present when running with either of these
changes. So that may be a red
(Unless, ofcourse I blindly got it right at the first try and everthing
works flawlessly:)
... which appears to have been the case, actually. I love it when code works
the first time. :)
Here's the dmesg log in case there's anything you need to know in there:
Mathias Nyman mathias.nyman@... writes:
Great, that's good news.
Indeed!
The patch is affecting others than just scanner so I'm going to run some basic
tests with it before sending it further.
It might even address some usbstick issues, some people have voiced with xhci.
we're late for
On 27.01.2015 13:57, Hans-Peter Jansen wrote:
What about a stable backport? Do you think, it's feasible, too much work, or
too risky?
This should definitely be backported to 3.18 stable, which should be easy.
Older longterms kernels are a bit tricky as the halt and reset code around this
On 22.01.2015 21:39, Gunter Königsmann wrote:
Seems like this time we are nearly there:
- the scanner appears in lsusb
Bus 001 Device 005: ID 04f2:b33c Chicony Electronics Co., Ltd
Bus 001 Device 006: ID 0489:e056 Foxconn / Hon Hai
Bus 001 Device 002: ID 8087:0024 Intel Corp.
I was doing this on your ep_reset_halt_test branch, which has a lot of
MATTU messages scrolling by, but I'm pretty sure that the microframe
rounding message was not present when running with either of these
changes. So that may be a red herring after all...
I wrote a new hack to test, its
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Seems like this time we are nearly there:
- the scanner appears in lsusb
Bus 001 Device 005: ID 04f2:b33c Chicony Electronics Co., Ltd
Bus 001 Device 006: ID 0489:e056 Foxconn / Hon Hai
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated
Mathias Nyman mathias.nyman@... writes:
Many changes were done in 3.18 and 3.19-rc release regarding to how we handle
halted and stopped endpoints, Can you test if that fixes your issues?
preferably with a 3.19-rc kernel
Here's the result of 3.19-rc4:
2015-01-20T15:26:41.242455+01:00 xrated
Mathias Nyman mathias.nyman@... writes:
Many changes were done in 3.18 and 3.19-rc release regarding to how we handle
halted and stopped endpoints, Can you test if that fixes your issues?
preferably with a 3.19-rc kernel
Here's the result of 3.19-rc4:
2015-01-20T15:26:41.242455+01:00 xrated
Any progress on this one?
Quite a bunch of people, that try to use a scanner on a xhci port gets
bitten by this issue. Given, that modern haswell mainboards tend to only
support xhci ports anymore, this is a real showstopper and kind of
regression from users POV.
Any progress on this one?
Quite a bunch of people, that try to use a scanner on a xhci port gets
bitten by this issue. Given, that modern haswell mainboards tend to only
support xhci ports anymore, this is a real showstopper and kind of
regression from users POV.
Mathias Nyman mathias.nyman@... writes:
On 09/15/2014 10:50 PM, Alan Stern wrote:
On Mon, 15 Sep 2014, Mathias Nyman wrote:
I haven't had time to dig into the usbmon traces, but I just got
another report from Gunter K�ningsmann
about similar scanner problem, and I just noticed
that
On Mon, 15 Sep 2014, Mathias Nyman wrote:
On 09/14/2014 01:52 AM, Mike Mammarella wrote:
On Sat, 26 Jul 2014, Mike Mammarella wrote:
On Fri, 4 Jul 2014, Mathias Nyman wrote:
On 07/01/2014 09:07 AM, Mike Mammarella wrote:
Hi
Can you add xhci debugging by enabling CONFIG_DYNAMIC_DEBUG, and
On 09/16/2014 12:29 AM, Gunter Königsmann wrote:
If after applying the patch I still get the warning and the scanner still
isn't working - did I do something wrong?
cat /proc/version is telling me I'm running the kernel I have compiled.
Thanks a lot,
and
You got two warnings previously,
On 09/15/2014 10:50 PM, Alan Stern wrote:
On Mon, 15 Sep 2014, Mathias Nyman wrote:
I haven't had time to dig into the usbmon traces, but I just got another
report from Gunter K�ningsmann about similar scanner problem, and I just
noticed
that in both cases we round the interval for high
On Tue, 16 Sep 2014, Mathias Nyman wrote:
It's not fully clear how xHCI controllers use the Interval field in the
Endpoint Context. Table 65 notably fails to include a line for HS
bulk-OUT/control endpoints, and the text isn't clear as to whether the
field is interpreted using
On 09/14/2014 01:52 AM, Mike Mammarella wrote:
On Sat, 26 Jul 2014, Mike Mammarella wrote:
On Fri, 4 Jul 2014, Mathias Nyman wrote:
On 07/01/2014 09:07 AM, Mike Mammarella wrote:
Hi
Can you add xhci debugging by enabling CONFIG_DYNAMIC_DEBUG, and run
`echo -n 'module xhci_hcd =p'
On Mon, 15 Sep 2014, Mathias Nyman wrote:
I haven't had time to dig into the usbmon traces, but I just got another
report from Gunter K�ningsmann about similar scanner problem, and I just
noticed
that in both cases we round the interval for high speed bulk _IN_ endpoint,
which should not
If after applying the patch I still get the warning and the scanner still isn't
working - did I do something wrong?
cat /proc/version is telling me I'm running the kernel I have compiled.
Thanks a lot,
and
Kind regards,
Gunter.
On 15.09.2014 21:50, Alan Stern wrote:
On Mon, 15 Sep
On Sat, 26 Jul 2014, Mike Mammarella wrote:
On Fri, 4 Jul 2014, Mathias Nyman wrote:
On 07/01/2014 09:07 AM, Mike Mammarella wrote:
Hi
Can you add xhci debugging by enabling CONFIG_DYNAMIC_DEBUG, and run
`echo -n 'module xhci_hcd =p' /sys/kernel/debug/dynamic_debug/control`
as root,
and
On Fri, 4 Jul 2014, Mathias Nyman wrote:
On 07/01/2014 09:07 AM, Mike Mammarella wrote:
Hi
Can you add xhci debugging by enabling CONFIG_DYNAMIC_DEBUG, and run
`echo -n 'module xhci_hcd =p' /sys/kernel/debug/dynamic_debug/control`
as root,
and send me the output of dmesg.
Without debugging
On 07/01/2014 09:07 AM, Mike Mammarella wrote:
Hi
Can you add xhci debugging by enabling CONFIG_DYNAMIC_DEBUG, and run
`echo -n 'module xhci_hcd =p' /sys/kernel/debug/dynamic_debug/control`
as root,
and send me the output of dmesg.
Without debugging info it's hard to guess what's going
Hi
Can you add xhci debugging by enabling CONFIG_DYNAMIC_DEBUG, and run
`echo -n 'module xhci_hcd =p' /sys/kernel/debug/dynamic_debug/control`
as root,
and send me the output of dmesg.
Without debugging info it's hard to guess what's going on.
The microframe rounding look a bit suspicious:
On 06/30/2014 05:43 PM, Alan Stern wrote:
On Mon, 30 Jun 2014, Mathias Nyman wrote:
xhci specs says it needs the interval rounded to nearest 2^(X) value,
which would be 256, not 128. I'll take a look at that.
Doesn't the spec says it needs the interval rounded _down_ to a
power of 2?
On 06/30/2014 12:02 AM, Mike Mammarella wrote:
recently got a computer [1] with USB3 ports, and plugged my Fujitsu Scansnap
S1500 scanner into one of them. It turns out this doesn't work, and after a
lot of searching the web and tinkering with it I've discovered that it has
something to do
On Mon, 30 Jun 2014, Mathias Nyman wrote:
xhci specs says it needs the interval rounded to nearest 2^(X) value,
which would be 256, not 128. I'll take a look at that.
Doesn't the spec says it needs the interval rounded _down_ to a
power of 2?
Alan Stern
--
To unsubscribe from this list: send
45 matches
Mail list logo