Jonathan Nieder <[email protected]> wrote:
> Thanks for reporting, and sorry for the long silence.
That's understandable.
>
> Do you still have access to this hardware? If so, would you still be
> interested in pursuing this bug? ("No" is an ok answer, but please do
> let us know so we can plan accordingly.)
The corresponding kernel bug was closed with a suggestion to reopen it if it
can be reproduced with a recent kernel. I think that's entirely reasonable.
I still have the hardware on a shelf somewhere here. At some point I'll take
it out, clear the drive and install a recent Debian (probably easier than
trying to upgrade a system that hasn't been booted for four years and there's
nothing worth preserving on the disk anyway).
That's a long way of saying, perhaps just close the bug and when I get to play
with the hardware I'll reopen the bug if I can still reproduce the issue with
an up to date kernel.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
Archive: http://lists.debian.org/[email protected]
