On 04/30/2011 09:49 PM, Steaphan Greene wrote:
On 04/23/2011 03:41 PM, Moritz Mühlenhoff wrote:
it seems you didn't followup in the kernel.org bugzilla. Is this fixed
in current kernels from sid or testing?
Testing on a different computer, just plugging it in with a clean boot
on the same
On 04/23/2011 03:41 PM, Moritz Mühlenhoff wrote:
On Wed, Dec 29, 2010 at 09:35:30PM +, Ben Hutchings wrote:
On Wed, 2010-12-29 at 14:05 -0500, Steaphan Greene wrote:
On 12/29/2010 09:10 AM, Ben Hutchings wrote:
On Wed, 2010-12-29 at 03:55 -0500, Steaphan Greene wrote:
On 12/26/2010 06:46
On Wed, Dec 29, 2010 at 09:35:30PM +, Ben Hutchings wrote:
On Wed, 2010-12-29 at 14:05 -0500, Steaphan Greene wrote:
On 12/29/2010 09:10 AM, Ben Hutchings wrote:
On Wed, 2010-12-29 at 03:55 -0500, Steaphan Greene wrote:
On 12/26/2010 06:46 AM, Moritz Muehlenhoff wrote:
Could you
On 04/23/2011 03:41 PM, Moritz Mühlenhoff wrote:
On Wed, Dec 29, 2010 at 09:35:30PM +, Ben Hutchings wrote:
On Wed, 2010-12-29 at 14:05 -0500, Steaphan Greene wrote:
On 12/29/2010 09:10 AM, Ben Hutchings wrote:
On Wed, 2010-12-29 at 03:55 -0500, Steaphan Greene wrote:
On 12/26/2010 06:46
On 12/26/2010 06:46 AM, Moritz Muehlenhoff wrote:
Could you try to reproduce this with a current 2.6.37-rcX
kernel from experimental?
The kernel is available from packages.debian.org. If the error can
still be reproduced, we should report it upstream.
Unfortunately, 2.6.37-rc7-amd64 has an
On Wed, 2010-12-29 at 03:55 -0500, Steaphan Greene wrote:
On 12/26/2010 06:46 AM, Moritz Muehlenhoff wrote:
Could you try to reproduce this with a current 2.6.37-rcX
kernel from experimental?
The kernel is available from packages.debian.org. If the error can
still be reproduced, we
On 12/29/2010 09:10 AM, Ben Hutchings wrote:
On Wed, 2010-12-29 at 03:55 -0500, Steaphan Greene wrote:
On 12/26/2010 06:46 AM, Moritz Muehlenhoff wrote:
Could you try to reproduce this with a current 2.6.37-rcX
kernel from experimental?
The kernel is available from packages.debian.org. If
On Wed, 2010-12-29 at 14:05 -0500, Steaphan Greene wrote:
On 12/29/2010 09:10 AM, Ben Hutchings wrote:
On Wed, 2010-12-29 at 03:55 -0500, Steaphan Greene wrote:
On 12/26/2010 06:46 AM, Moritz Muehlenhoff wrote:
Could you try to reproduce this with a current 2.6.37-rcX
kernel from
Hi,
On Sat, Sep 11, 2010 at 02:50:19PM -0400, Steaphan Greene wrote:
Package: linux-2.6
Version: 2.6.32-21
Severity: important
I've confirmed that linux-image-2.6.32-5-amd64 has this same problem.
I believe this problem did not exist in 2.6.31 from backports.
With the Keyspan USA-49WG
On 12/26/2010 06:46 AM, Moritz Muehlenhoff wrote:
Could you try to reproduce this with a current 2.6.37-rcX
kernel from experimental?
The kernel is available from packages.debian.org. If the error can
still be reproduced, we should report it upstream.
Sure. I won't be able to try this
Package: linux-2.6
Version: 2.6.32-21
Severity: important
I've confirmed that linux-image-2.6.32-5-amd64 has this same problem.
I believe this problem did not exist in 2.6.31 from backports.
With the Keyspan USA-49WG (a 4-port USB-to-Serial device), only 3 ports
work. Reads/writes from/to the
11 matches
Mail list logo
