From 8ed8fdae4eacf6e2b059b524e90be8a31a5fbf8f Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Thu, 17 Feb 2011 19:28:52 +0100 Subject: open_issues/gnumach_console_timestamp: New. --- open_issues/gnumach_console_timestamp.mdwn | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) create mode 100644 open_issues/gnumach_console_timestamp.mdwn (limited to 'open_issues') diff --git a/open_issues/gnumach_console_timestamp.mdwn b/open_issues/gnumach_console_timestamp.mdwn new file mode 100644 index 00000000..b36b47b9 --- /dev/null +++ b/open_issues/gnumach_console_timestamp.mdwn @@ -0,0 +1,27 @@ +[[!meta copyright="Copyright © 2011 Free Software Foundation, Inc."]] + +[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable +id="license" text="Permission is granted to copy, distribute and/or modify this +document under the terms of the GNU Free Documentation License, Version 1.2 or +any later version published by the Free Software Foundation; with no Invariant +Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license +is included in the section entitled [[GNU Free Documentation +License|/fdl]]."]]"""]] + +[[!tag open_issue_gnumach]] + +IRC, freenode, #hurd, 2011-02-17 + + task 39011c10 deallocating an invalid port 349, most probably a + bug. + kernel: Page fault (14), code=6 + Stopped at 0x28b9c7: orb %bh,0(%ecx,%edi,2) + db> + [...] + tschwinge: I doubt the deallocating warning is related to the + later fault + antrik: YOu may be right. + Perhaps it'd be a good idea to add some sort of timestamp to + Mach messages. + Like in Linux' dmesg. + Or just RDTSC (internal processor counter). -- cgit v1.2.3