Your message dated Sat, 20 May 2023 11:55:48 +0200
with message-id <651802e7-9405-b7d9-9a05-8214077c3...@debian.org>
and subject line Re: Bug#35970: gnumach hangs because of Linux 2.0.36 adaptec
drivers
has caused the Debian Bug report #35970,
regarding gnumach hangs because of Linux 2.0.36 adaptec drivers
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
35970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=35970
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnumach
Version: 1.1.90-2
[ Hello Gordon. This weekend I tested Marcus' cross-install at home and it
worked great. Congratulations to everybody for all the hard work! ].
However, today I tried to do the same with the computer I have at work,
without success: The booting process hangs.
I think that the reason for this is that gnumach contains the "new"
adaptec drivers from Linux 2.0.36 (in fact, I can't install Debian 2.1
from scratch in my system because of this very reason).
If you could forward this upstream so that this is fixed in gnumach,
it would be great.
Thanks.
--
"e2c6b0921878879b6eddf125d30882f6" (a truly random sig)
--- End Message ---
--- Begin Message ---
El 20/5/23 a las 9:29, Petter Reinholdtsen escribió:
[Guillem Jover 2005]
Can you reproduce #35970 with the latest gnumach packages?
[Santiago Vila 2005]
I don't know, and it is going to be quite difficult for me to check, because
the computer is currently running woody as a server for a lot of people...
Is there any use keeping this issue open?
Not really.
I suspect the hardware in
question has long since been retired and no-one is using the
Adaptec driver any more.
The hardware was retired a long time ago indeed. When I reported this,
the computer was my personal computer at work. In 2005 it was working
as a printer server in my Department, and that's why it was not
possible for me to test.
Now I don't even work there.
The upstream bug is also flagged with 'need more info', and if no-one
can provide the info, it seem useless to keep the issue open.
I agree, so I'm closing this myself.
Thanks.
--- End Message ---
