From: Nix <nix@esperi.org.uk>
To: Yehuda Sadeh Weinraub <yehudasa@gmail.com>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Networking issues with 2.6.29
Date: Sun, 29 Mar 2009 13:08:49 +0100 [thread overview]
Message-ID: <87hc1cbkfi.fsf@hades.wkstn.nix> (raw)
In-Reply-To: <a37615150903261150x3642d954y296b6e8c26e53fe8@mail.gmail.com> (Yehuda Sadeh Weinraub's message of "Thu, 26 Mar 2009 11:50:34 -0700")
On 26 Mar 2009, Yehuda Sadeh Weinraub spake thusly:
> Network doesn't seem to work for me in 2.6.29, although it was working
> in 2.6.28. System behavior seemed really strange, as it sometimes did
> work when I was using the same uml machine, when using a different
> user. Bisecting the kernel tree, revels a seemingly unrelated commit
> that when reverted it fixes the problem:
I doubt it. This is a known race, particularly easy to reproduce on UP,
fixed by <http://patchwork.kernel.org/patch/14465/>, which causes
networking to go away at seemingly random moments. I had it everywhere
within ten minutes of upgrading...
> commit 470c66239ef0336429b35345f3f615d47341e13b
> Author: David Brownell <dbrownell@users.sourceforge.net>
> Date: Mon Dec 1 14:31:37 2008 -0800
>
> genirq: warn when IRQF_DISABLED may be ignored
This patch just adds an (annoying and useless to users) warning that's
printed at interface bringup time. If it makes the problem go away I'll
eat my hat.
------------------------------------------------------------------------------
_______________________________________________
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:[~2009-03-29 12:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 18:50 [uml-devel] Networking issues with 2.6.29 Yehuda Sadeh Weinraub
2009-03-29 12:08 ` 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=87hc1cbkfi.fsf@hades.wkstn.nix \
--to=nix@esperi.org.uk \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=yehudasa@gmail.com \
/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