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 kernel version as before (that this bug was filed against)
immediately crashed the kernel (OOPS, followed shortly by a constant
terminal bell and no response to any input, not even numlock or SysRq).
Testing this device using linux-image2.6.38-2-amd64 from current sid
(v2.6.38-4) resulted in all 4 ports working perfectly. However, I only
could test them individually on that machine, so I can not confirm they
will work simultaneously as they are used on the real system. But, it
certainly seems better to me.
I will follow up once I get a chance to test this on the live system
with this new kernel version, but that may be a while. I suspect this
bug is now resolved, but I can't confirm this until then.
I found a window to reboot the main system using this hardware to test
this newer kernel, and it just went through a cycle using all 4 serial
ports on this device simultaneously, and worked perfectly.
So, I can confirm this bug has definitely been fixed as of the above
kernel package version (linux-image2.6.38-2-amd64 from sid 5 days ago).
Thanks!
--
Steaphan Greene <sgre...@cs.binghamton.edu>
Lecturer, Computer Science, Binghamton University
GPG public key: http://www.cs.binghamton.edu/~sgreene/gpg.key.txt
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4dc3608e.8030...@cs.binghamton.edu
