[arch-general] is udev-164 a safe solution at the moment
Hi, still again after every 20 or 30 new boot udev-165 hangs both pc's with archlinux. So my question is that if i step back to udev-164 will there be problems with the initscripts or any other plans what you the devs have in the near future? If yes than i can (or have to) live with this because it is very seldom and therefore very hard to find out what is the problem. See you, Attila
Am 20.01.2011 06:51, schrieb Attila:
Hi,
still again after every 20 or 30 new boot udev-165 hangs both pc's with archlinux. So my question is that if i step back to udev-164 will there be problems with the initscripts or any other plans what you the devs have in the near future? If yes than i can (or have to) live with this because it is very seldom and therefore very hard to find out what is the problem.
See you, Attila
Some people actually tracked down the kernel bug that is causing this, but nobody opened a bug report about it upstream. If this is the same bug I heard about, a workaround is deleting /lib/udev/ata_id.
On Thu, 2011-01-20 at 10:38 +0100, Thomas Bächler wrote:
Am 20.01.2011 06:51, schrieb Attila:
Hi,
still again after every 20 or 30 new boot udev-165 hangs both pc's with archlinux. So my question is that if i step back to udev-164 will there be problems with the initscripts or any other plans what you the devs have in the near future? If yes than i can (or have to) live with this because it is very seldom and therefore very hard to find out what is the problem.
See you, Attila
Some people actually tracked down the kernel bug that is causing this, but nobody opened a bug report about it upstream. If this is the same bug I heard about, a workaround is deleting /lib/udev/ata_id.
Is there a big report on this? I would like to know if it is the same problem as what I am experiencing or not.
At Donnerstag, 20. Januar 2011 10:38 Thomas Bächler wrote:
Some people actually tracked down the kernel bug that is causing this, but nobody opened a bug report about it upstream. If this is the same bug I heard about, a workaround is deleting /lib/udev/ata_id.
Thanks for the hint and i move ata_id to another place. I think the biggest problem for writing a bugreport is that this happens very, very seldom. See you, Attila
participants (3)
-
Attila
-
Thomas Bächler
-
Ty John (sand_man)