Bug#35970: gnumach hangs because of Linux 2.0.36 adaptec drivers
Hi Santiago, Can you reproduce #35970 with the latest gnumach packages? regards, guillem -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#35970: gnumach hangs because of Linux 2.0.36 adaptec drivers
On Sat, 14 May 2005, Guillem Jover wrote: > Hi Santiago, > > Can you reproduce #35970 with the latest gnumach packages? 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... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#35970: gnumach hangs because of Linux 2.0.36 adaptec drivers
[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? I suspect the hardware in question has long since been retired and no-one is using the Adaptec driver any more. 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. -- Happy hacking Petter Reinholdtsen
Bug#35970: gnumach hangs because of Linux 2.0.36 adaptec drivers
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.
