>x86-64 has quite different time code (at least until the dyntick patches currently in mm) Obvious thing would be to diff the boot messages and see if anything jumps out (e.g. in interrupt routing). Or check with mm and if x86-64 is broken there too then it's likely the new time code. -Andi -
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Bart Van Assche | Integration of SCST in the mainstream Linux kernel |
| David Dillow | CONFIG_NO_HZ breaks blktrace timestamps |
| David Miller | Re: tg3: unable to handle null pointer dereference |
git: | |
| Martin Langhoff | Handling large files with GIT |
| Jakub Narebski | Re: VCS comparison table |
| Scott Chacon | Git Community Book |
| Matthew L Foster | git and time |
| Daniel Ouellet | identifying sparse files and get ride of them trick available? |
| Richard Stallman | Real men don't attack straw men |
| Stefan Beke | mail dovecot: pipe() failed: Too many open files |
| Rico Secada | Re: Binary kernel and base update |
| Evgeniy Polyakov | Re: [PKT_SCHED]: Add stateless NAT |
| Tantilov, Emil S | RE: [BUG] NULL pointer dereference in skb_dequeue |
| KOVACS Krisztian | [PATCH 10/14] iptables socket match |
| Ilpo Järvinen | [PATCH] [TCP]: Separate lost_retrans loop into own function |
