From: Nix <nix@esperi.org.uk>
To: Jeff Dike <jdike@addtoit.com>
Cc: Thomas Gleixner <tglx@timesys.com>,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Lockups with the fixed timer code :/
Date: Thu, 24 Apr 2008 23:18:59 +0100 [thread overview]
Message-ID: <87y7727v70.fsf@hades.wkstn.nix> (raw)
In-Reply-To: <20080424203732.GA11688@c2.user-mode-linux.org> (Jeff Dike's message of "Thu, 24 Apr 2008 16:37:32 -0400")
On 24 Apr 2008, Jeff Dike uttered the following:
> OK, yell if it starts happening again...
I tempted fate, and lo, it happens within the hour...
(gdb) bt
#0 0x08083e3a in getnstimeofday ()
I will now do what I should have done long since and turn on frame
pointers and debugging info so I can get a damn backtrace. (I really
thought that was on, but apparently not...)
One 2.6.25 improvement: in 2.6.24, whenever this happened the TUN/TAP
driver seemed to get some sort of nasty lock taken out, all future
packets sent over it vanished into the aether rather than going over the
(virtual) ether(net), and I had to reboot the host to fix it. No
longer. :)
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2008-04-24 22:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-05 16:45 [uml-devel] Lockups with the fixed timer code :/ Nix
2008-04-14 14:40 ` Jeff Dike
2008-04-15 19:47 ` Nix
2008-04-15 20:59 ` Ryan Finnie
2008-04-16 19:44 ` Nix
2008-04-24 19:57 ` Nix
2008-04-24 20:37 ` Jeff Dike
2008-04-24 22:18 ` Nix [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y7727v70.fsf@hades.wkstn.nix \
--to=nix@esperi.org.uk \
--cc=jdike@addtoit.com \
--cc=tglx@timesys.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox