Please read the Arch Linux guidelines before reporting a bug, they're very good:
http://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated. Use the "Mark out of date" link on the package page, or the mailing list.
| Tasklist |

FS#2 - system locking after inactivity

Attached to Project: Arch Hurd
Opened by Sébastien Duquette (ekse) - 2010-04-23 00:14:01
Last edited by Matthias Lanzinger (melpo) - 2010-04-25 19:35:49
Task Type Bug Report
Category Backend / Core
Status Researching
Assigned To No-one
Operating System All
Severity High
Priority Normal
Reported Version 1.0
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 1
Private No

Details

The system is becoming unresponsive after a certain amount of inactivity. Currently, a work-around is to run the "vmstat 5" command in a terminal to generate activity.
This task depends upon

Comment by Matthias Lanzinger (melpo) - 2010-04-25 19:38:36
This issue has been reported on different Virtual Machines but does not seem to exist when running on a real machine.
Comment by Diego Martin Nieto Cid (diego) - 2010-07-28 23:51:24
Yes it does block on real machines. (well.. mine at least :( )
Comment by Diego Martin Nieto Cid (diego) - 2010-07-29 19:26:44
The serial console* doesn't block.

* http://article.gmane.org/gmane.linux.debian.ports.hurd/5320
(in quemu Ctrl+Alt+2 shows the serial line on screen)
Comment by Diego Martin Nieto Cid (diego) - 2010-07-29 23:26:52
By killing the console process the machine, now at the mach console, starts reacting to the keyboard. However, the screen is no longer refreshed.

Pretty useless, but at least it's possible to use the machine by heart. :P
Comment by Matthias Lanzinger (melpo) - 2010-08-13 17:11:46
In my opinion it looks like the console drivers (pc_kbd, vga) stop reacting.
Even when the system locks I can perfectly continue using it via ssh.
Any ideas on how to debug this?
Comment by Diego Martin Nieto Cid (diego) - 2010-08-13 19:28:52
If my last comment were reproducible I'd say vga is causing this. But it isn't :P

I tried using gdb from the serial console but after telling gdb to continue, the console hangs. Maybe through ssh it works fine.

Here are some notes about the hurd console: http://wiki.github.com/diegonc/arch-hurd-xkb-driver/notes-hurd-console

Unfortunately I couldn't complete the data flow. I fear glibc is in the middle. :(

BTW, Debian doesn't appear to block *shrug*.
Comment by Diego Martin Nieto Cid (diego) - 2010-08-14 00:38:48
For some reason the thread started by the input driver is dying.

* http://archhurd.pastebin.com/MaEKtjz8
* http://archhurd.pastebin.com/75dHpg1a
Comment by Alexander Preisinger (Giselher) - 2010-08-26 13:33:00
It seems to be better now with the new packages.

Loading...