The down time displayed is the downtime + following uptime Reproducible: Always Steps to Reproduce: 1. run last -x 2. 3. Actual Results: sample output: reboot system boot 2.6.10-gentoo-r6 Thu Mar 17 16:50 (19:40) shutdown system down 2.6.10-gentoo-r6 Thu Mar 17 16:46 - 12:31 (19:44) Expected Results: reboot system boot 2.6.10-gentoo-r6 Thu Mar 17 16:50 (19:40) shutdown system down 2.6.10-gentoo-r6 Thu Mar 17 16:46 - 16:50 (00:04)
Created attachment 54547 [details, diff] proposed fix
maybe it's me but that patch doesnt seem to work right ... before: root tty1 Mon Mar 21 20:19 still logged in runlevel (to lvl 3) 2.6.12-rc1 Mon Mar 21 15:21 - 00:11 (7+08:49) reboot system boot 2.6.12-rc1 Mon Mar 21 15:21 (7+08:49) shutdown system down 2.6.11 Mon Mar 21 18:07 - 00:11 (7+06:03) runlevel (to lvl 0) 2.6.11 Mon Mar 21 18:07 - 18:07 (00:00) after: root tty1 Mon Mar 21 20:19 still logged in runlevel (to lvl 3) 2.6.12-rc1 Mon Mar 21 15:21 - 00:18 (7+08:57) reboot system boot 2.6.12-rc1 Mon Mar 21 15:21 (7+08:57) shutdown system down 2.6.11 Mon Mar 21 18:07 - 15:21 (-2:-45) runlevel (to lvl 0) 2.6.11 Mon Mar 21 18:07 - 18:07 (00:00)
it seems your system went down at 18:07 and then went up at 15:21 on the same day, so the output is correct, it is your system clock that is messed up.
How does this work for you? With 2.86-r8 I am still seeing the same behaviour.