Comment 2 for bug 304793

z3non (tom-uttenthaler) wrote :

The root of the problem was a future timestamp of the fdi-cache:

-rw-r--r-- 1 root root 1039604 2024-07-20 02:45 fdi-cache

after deleting it, everything works fine again. The future time probably came from a PM_TRACE, which I have activated, since the S2Mem is f*ing instable since intrepid ... nevertheless, I regard this behavior as a bug in hal. It is or has been discussed there for Debian and Ubuntu, so there should:

http://<email address hidden>/msg572726.html
http://groups.google.com/group/linux.debian.bugs.dist/browse_thread/thread/83d30ea7b629e4a4

and here you find a patch (which is secure, as it deletes the fdi-cache on every hal-start, but increases boot-time):

http://groups.google.com/group/linux.debian.bugs.dist/attach/b524a9234fe6547d/hal.fdi-cache.debdiff?part=3

regards,
tom