Hello Mike, On Thu, Feb 20, 2025 at 09:23:16AM -0500, Mike wrote: > Well yeah, it's very old now, two years later I'm now getting the first and > last response on this bug. It is still happening on the latest kernel but > I'm not planning to open another ticket as I didn't see any work whatsoever > on resolving this ticket. Thanks for the waste of time.
While I'm not happy that some bug reports fall through the cracks (like this one), let me tell you how the situation looks from where I sit: The active kernel team consists of four people who fill this role in their spare time and probably have no hardware to reproduce your problem. Compare that to https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=linux . That together means that we don't reach the customer satisfaction that you seem to expect and that we'd like to have. The thing that you can do about it is: Make it easy for us four to act on your bug report. Get some details about your problem. Relevant information would be: Which driver is used to provide /dev/ttyS0? Can you confirm that with the Ubuntu or Slackware kernel you really get the output at 110 Bd? Test a Debian 5.15 kernel (you can get one from snapshot.debian.org) and if that fails as expected compare kernel configuration and patch stacks. (Or even better compare newer working and non-working kernels accordingly.) Tell us if earlier Debian kernels worked for you and ideally identify the newest working and the oldest broken kernel. And note that Salvatore's request to reopen the bug if you still experience it was honest. Ideally in combination with some more information as sketched above. And don't rant while doing so, as this kills motivation on the receiving end. Best regards Uwe
signature.asc
Description: PGP signature
