From: "John W. Linville" <linville@redhat.com>
To: Thomas Graf <tgraf@suug.ch>
Cc: Development discussions related to Fedora Core
<fedora-devel-list@redhat.com>,
netdev@vger.kernel.org, Pekka Savola <pekkas@netcore.fi>,
linville@tuxdriver.com
Subject: Re: fedora-netdev.1 IPv6 freeze [Re: [ANNOUNCE] fedora-netdev kernel repository]
Date: Wed, 16 Nov 2005 09:25:18 -0500 [thread overview]
Message-ID: <20051116142518.GE8356@redhat.com> (raw)
In-Reply-To: <20051116114224.GB20395@postel.suug.ch>
On Wed, Nov 16, 2005 at 12:42:24PM +0100, Thomas Graf wrote:
> * Pekka Savola <pekkas@netcore.fi> 2005-11-16 12:46
> > On Mon, 14 Nov 2005, John W. Linville wrote:
> > > http://people.redhat.com/linville/kernels/fedora-netdev/
> >
> > I guess the test can be termed a 'success' because after updating from
> > 2.6.14-1.1637_FC4 to 2.6.14-1.1637_FC4.netdev.1, I get 100%
> > reproducible kernel hang (everything just freezes as it is, no message
> > to /var/log/messages or anywhere) after I run '/sbin/ip -6 r l' or try
> > to use IPv6 in basically any other way on my ThinkPad laptop with
> > external orinoco_cs WLAN card.
> >
> > Any thoughts for the next steps?
>
> It's probably missing this patch:
It was...
Pekka, I have included the patch Thomas identified as part of the
FC4.netdev.2 build. You may want to do a 'yum update' and try it out.
Thanks!
John
--
John W. Linville
linville@redhat.com
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
next prev parent reply other threads:[~2005-11-16 14:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-14 20:51 [ANNOUNCE] fedora-netdev kernel repository John W. Linville
2005-11-16 10:46 ` fedora-netdev.1 IPv6 freeze [Re: [ANNOUNCE] fedora-netdev kernel repository] Pekka Savola
[not found] ` <20051116114224.GB20395@postel.suug.ch>
2005-11-16 14:25 ` John W. Linville [this message]
2005-11-16 14:33 ` kernel-2.6.14-1.1637_FC4.netdev.2 now available John W. Linville
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=20051116142518.GE8356@redhat.com \
--to=linville@redhat.com \
--cc=fedora-devel-list@redhat.com \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=pekkas@netcore.fi \
--cc=tgraf@suug.ch \
/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;
as well as URLs for NNTP newsgroup(s).