9:01 p.m.
The last two updates to the F7 kernel, 2930 and 2932, booted for me,
but there is no internet connection with either one. Fortunately, yum
kept 2925 instead of 2930 when it installed 2932, so I am able to send
this message.
I have not had time to troubleshoot it and am about to leave town for
10 days, but wanted to report this and see if any other testers have
this same result.
Thanks.
Gerry
1:16 p.m.
I think this could be same problem as in topic:
"Kernel 2911 still loses network under load"
Adam Pribyl
On Fri, 16 Feb 2007, Gerry Tool wrote:
The last two updates to the F7 kernel, 2930 and 2932, booted for me,
but there is no internet connection with either one. Fortunately, yum
kept 2925 instead of 2930 when it installed 2932, so I am able to send
this message.
I have not had time to troubleshoot it and am about to leave town for
10 days, but wanted to report this and see if any other testers have
this same result.
Thanks.
Gerry
--
fedora-test-list mailing list
fedora-test-list(a)redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
Odchozi zprava neobsahuje viry, protoze nebyla odeslana z Windows.
Otestovano zdarma a legalne na OS Linux.
(Proc pouzivat Linux - http://proc.linux.cz/).
1:26 p.m.
Same thing happens here.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=229099
1:42 p.m.
On Sat, 17 Feb 2007 20:26:59 +0100
Guido Ledermann <guido.ledermann(a)googlemail.com> wrote:
Same thing happens here.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=229099
Shot-in-the-dark follows...
I remember reading somewhere that forcedeth tries to use MSI by default.
If so, maybe your motherboard doesn't play well with MSI. Check for MSI
with:
cat /proc/interrupts | grep MSI
If you see eth0 running with MSI, try booting with pci=nomsi.
5:13 p.m.
Thanks, Jay, but I don't have MSI.
Am Samstag, den 17.02.2007, 13:42 -0600 schrieb Jay Cliburn:
On Sat, 17 Feb 2007 20:26:59 +0100
Guido Ledermann <guido.ledermann(a)googlemail.com> wrote:
> Same thing happens here.
>
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=229099
>
Shot-in-the-dark follows...
I remember reading somewhere that forcedeth tries to use MSI by default.
If so, maybe your motherboard doesn't play well with MSI. Check for MSI
with:
cat /proc/interrupts | grep MSI
If you see eth0 running with MSI, try booting with pci=nomsi.
3:25 p.m.
On Sat, Feb 17, 2007 at 08:26:59PM +0100, Guido Ledermann wrote:
Same thing happens here.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=229099
I seem to recall from older lkml postings that with forcedeth driver
putting an interface into a promiscuous mode allowed, at least in
some situations, to work around the problem. You can do that with a
help of 'ip' or 'ifconfig'.
Of course this is a hack but if it works for you this some extra
information.
Michal
5:17 p.m.
I'll have a look into that, Michal. Thanks.
Am Samstag, den 17.02.2007, 14:25 -0700 schrieb Michal Jaegermann:
On Sat, Feb 17, 2007 at 08:26:59PM +0100, Guido Ledermann wrote:
> Same thing happens here.
>
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=229099
I seem to recall from older lkml postings that with forcedeth driver
putting an interface into a promiscuous mode allowed, at least in
some situations, to work around the problem. You can do that with a
help of 'ip' or 'ifconfig'.
Of course this is a hack but if it works for you this some extra
information.
Michal
5:57 p.m.
Doen't work here folks. Even setting eth0 in promiscous mode I can't
ping anything else than my own ip. I hope this is fixed with the next
kernel.
Am Samstag, den 17.02.2007, 14:25 -0700 schrieb Michal Jaegermann:
On Sat, Feb 17, 2007 at 08:26:59PM +0100, Guido Ledermann wrote:
> Same thing happens here.
>
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=229099
I seem to recall from older lkml postings that with forcedeth driver
putting an interface into a promiscuous mode allowed, at least in
some situations, to work around the problem. You can do that with a
help of 'ip' or 'ifconfig'.
Of course this is a hack but if it works for you this some extra
information.
Michal
11:36 a.m.
On 2/17/07, Guido Ledermann <guido.ledermann(a)googlemail.com> wrote:
Doen't work here folks. Even setting eth0 in promiscous mode I can't
ping anything else than my own ip. I hope this is fixed with the next
kernel.
This is still true with the latest kernel today, 2/24/07, #2942. Is there
some
setting that corrects this? I have selinux disabled (makes no
difference.) I can't even ping other computers on my local network. DHCP
on the router did give me a valid IP address and even the name server IPs
are correct.
Gerry
11:07 a.m.
On 2/24/07, Gerry Tool <gerrytool(a)gmail.com> wrote:
On 2/17/07, Guido Ledermann <guido.ledermann(a)googlemail.com> wrote:
>
> Doen't work here folks. Even setting eth0 in promiscous mode I can't
> ping anything else than my own ip. I hope this is fixed with the next
> kernel.
>
> This is still true with the latest kernel today, 2/24/07, #2942. Is
there some setting that corrects this? I have selinux disabled (makes no
difference.) I can't even ping other computers on my local network. DHCP
on the router did give me a valid IP address and even the name server IPs
are correct.
Gerry
Still true 2/26 with kernel 2947.
1:56 p.m.
On Mon, Feb 26, 2007 at 11:07:56AM -0600, Gerry Tool wrote:
On 2/24/07, Gerry Tool <gerrytool(a)gmail.com> wrote:
>
>
>
> On 2/17/07, Guido Ledermann <guido.ledermann(a)googlemail.com> wrote:
> >
> > Doen't work here folks. Even setting eth0 in promiscous mode I can't
> > ping anything else than my own ip. I hope this is fixed with the next
> > kernel.
> >
> > This is still true with the latest kernel today, 2/24/07, #2942. Is
> there some setting that corrects this? I have selinux disabled (makes no
> difference.) I can't even ping other computers on my local network. DHCP
> on the router did give me a valid IP address and even the name server IPs
> are correct.
Still true 2/26 with kernel 2947.
What NIC ?
Dave
--
http://www.codemonkey.org.uk
1:59 p.m.
Am Montag, den 26.02.2007, 14:56 -0500 schrieb Dave Jones:
On Mon, Feb 26, 2007 at 11:07:56AM -0600, Gerry Tool wrote:
> On 2/24/07, Gerry Tool <gerrytool(a)gmail.com> wrote:
> >
> >
> >
> > On 2/17/07, Guido Ledermann <guido.ledermann(a)googlemail.com> wrote:
> > >
> > > Doen't work here folks. Even setting eth0 in promiscous mode I
can't
> > > ping anything else than my own ip. I hope this is fixed with the next
> > > kernel.
> > >
> > > This is still true with the latest kernel today, 2/24/07, #2942. Is
> > there some setting that corrects this? I have selinux disabled (makes no
> > difference.) I can't even ping other computers on my local network.
DHCP
> > on the router did give me a valid IP address and even the name server IPs
> > are correct.
>
> Still true 2/26 with kernel 2947.
What NIC ?
This seems to hit all of "CK804 Ethernet Controller" at least.
Guido
2:19 p.m.
On Mon, Feb 26, 2007 at 08:59:35PM +0100, Guido Ledermann wrote:
Am Montag, den 26.02.2007, 14:56 -0500 schrieb Dave Jones:
> On Mon, Feb 26, 2007 at 11:07:56AM -0600, Gerry Tool wrote:
> > On 2/24/07, Gerry Tool <gerrytool(a)gmail.com> wrote:
> > >
> > >
> > >
> > > On 2/17/07, Guido Ledermann <guido.ledermann(a)googlemail.com>
wrote:
> > > >
> > > > Doen't work here folks. Even setting eth0 in promiscous mode I
can't
> > > > ping anything else than my own ip. I hope this is fixed with the
next
> > > > kernel.
> > > >
> > > > This is still true with the latest kernel today, 2/24/07, #2942.
Is
> > > there some setting that corrects this? I have selinux disabled (makes
no
> > > difference.) I can't even ping other computers on my local network.
DHCP
> > > on the router did give me a valid IP address and even the name server
IPs
> > > are correct.
> >
> > Still true 2/26 with kernel 2947.
>
> What NIC ?
This seems to hit all of "CK804 Ethernet Controller" at least.
Ok, I'll cc Ayaz, as he did some of the recent optimisations to the forcedeth driver.
Ayaz, this is a regression with the current code in v.2.6.21rc1 that recently
occured since v.2.6.20.
Dave
--
http://www.codemonkey.org.uk
4:40 p.m.
On Mon, Feb 26, 2007 at 03:19:53PM -0500, Dave Jones wrote:
On Mon, Feb 26, 2007 at 08:59:35PM +0100, Guido Ledermann wrote:
> Am Montag, den 26.02.2007, 14:56 -0500 schrieb Dave Jones:
> > On Mon, Feb 26, 2007 at 11:07:56AM -0600, Gerry Tool wrote:
> > > On 2/24/07, Gerry Tool <gerrytool(a)gmail.com> wrote:
> > > >
> > > >
> > > >
> > > > On 2/17/07, Guido Ledermann <guido.ledermann(a)googlemail.com>
wrote:
> > > > >
> > > > > Doen't work here folks. Even setting eth0 in promiscous
mode I can't
> > > > > ping anything else than my own ip. I hope this is fixed with
the next
> > > > > kernel.
> > > > >
> > > > > This is still true with the latest kernel today, 2/24/07,
#2942. Is
> > > > there some setting that corrects this? I have selinux disabled
(makes no
> > > > difference.) I can't even ping other computers on my local
network. DHCP
> > > > on the router did give me a valid IP address and even the name
server IPs
> > > > are correct.
> > >
> > > Still true 2/26 with kernel 2947.
> >
> > What NIC ?
>
> This seems to hit all of "CK804 Ethernet Controller" at least.
Ok, I'll cc Ayaz, as he did some of the recent optimisations to the forcedeth
driver.
Ayaz, this is a regression with the current code in v.2.6.21rc1 that recently
occured since v.2.6.20.
Ah, this is already reported upstream at http://bugzilla.kernel.org/show_bug.cgi?id=8090
For now, I'll back out the changes for the next rawhide kernel
Dave
--
http://www.codemonkey.org.uk
4:52 p.m.
On Mon, Feb 26, 2007 at 12:53:44PM -0800, Tom London wrote:
On 2/26/07, Dave Jones <davej(a)redhat.com> wrote:
>
> What NIC ?
I am having what appears to be stability problems with e1000.
Even on todays build? What exactly are you seeing?
Dave
--
http://www.codemonkey.org.uk
6:26 p.m.
On 2/26/07, Dave Jones <davej(a)redhat.com> wrote:
On Mon, Feb 26, 2007 at 12:53:44PM -0800, Tom London wrote:
> On 2/26/07, Dave Jones <davej(a)redhat.com> wrote:
> >
> > What NIC ?
>
> I am having what appears to be stability problems with e1000.
Even on todays build? What exactly are you seeing?
Dave
Will test later tonight with today's build (.2947).
I got freezes/NMIs with the previous few builds.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=229603
tom
--
Tom London
12:52 p.m.
On 2/26/07, Tom London <selinux(a)gmail.com> wrote:
On 2/26/07, Dave Jones <davej(a)redhat.com> wrote:
> On Mon, Feb 26, 2007 at 12:53:44PM -0800, Tom London wrote:
> > On 2/26/07, Dave Jones <davej(a)redhat.com> wrote:
> > >
> > > What NIC ?
> >
> > I am having what appears to be stability problems with e1000.
>
> Even on todays build? What exactly are you seeing?
>
> Dave
>
Will test later tonight with today's build (.2947).
I got freezes/NMIs with the previous few builds.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=229603
tom
I get a hard system freeze (e.g., mouse doesn't move, no response to
keyboard, etc.) with .2949. I have no problems if I disconnect cable
and use wireless.
System is X60 with e1000 NIC.
tom
--
Tom London
1:59 p.m.
On Tue, Feb 27, 2007 at 10:52:42AM -0800, Tom London wrote:
On 2/26/07, Tom London <selinux(a)gmail.com> wrote:
> On 2/26/07, Dave Jones <davej(a)redhat.com> wrote:
> > On Mon, Feb 26, 2007 at 12:53:44PM -0800, Tom London wrote:
> > > On 2/26/07, Dave Jones <davej(a)redhat.com> wrote:
> > > >
> > > > What NIC ?
> > >
> > > I am having what appears to be stability problems with e1000.
> >
> > Even on todays build? What exactly are you seeing?
> >
> > Dave
> >
> Will test later tonight with today's build (.2947).
>
> I got freezes/NMIs with the previous few builds.
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=229603
>
> tom
I get a hard system freeze (e.g., mouse doesn't move, no response to
keyboard, etc.) with .2949. I have no problems if I disconnect cable
and use wireless.
System is X60 with e1000 NIC.
tom
--
Tom London
Auke, known problem ? (This is on a 2.6.21rc1 kernel)
Dave
--
http://www.codemonkey.org.uk
3:10 p.m.
On 2/26/07, Dave Jones <davej(a)redhat.com> wrote:
On Mon, Feb 26, 2007 at 11:07:56AM -0600, Gerry Tool wrote:
> On 2/24/07, Gerry Tool <gerrytool(a)gmail.com> wrote:
> >
> >
> >
> > On 2/17/07, Guido Ledermann <guido.ledermann(a)googlemail.com> wrote:
> > >
> > > Doen't work here folks. Even setting eth0 in promiscous mode I
can't
> > > ping anything else than my own ip. I hope this is fixed with the
next
> > > kernel.
> > >
> > > This is still true with the latest kernel today, 2/24/07, #2942. Is
> > there some setting that corrects this? I have selinux disabled (makes
no
> > difference.) I can't even ping other computers on my local
network. DHCP
> > on the router did give me a valid IP address and even the name server
IPs
> > are correct.
>
> Still true 2/26 with kernel 2947.
What NIC ?
Dave
nVidia Corporation CK804 Ethernet Controller on an ASUS A8N-E mainboard.
Kernel 2925 works fine, all since then will not allow pinging of anything.
IP address assigned OK.
Gerry
6268
days inactive
6278
days old
19 comments
7 participants
participants (7)
-
Adam Pribyl -
Dave Jones -
Gerry Tool -
Guido Ledermann -
Jay Cliburn -
Michal Jaegermann -
Tom London