From: Andrew Morton <akpm@linux-foundation.org>
To: for.dev.null@gmail.com
Cc: bugme-daemon@bugzilla.kernel.org, netdev@vger.kernel.org,
mostrows@speakeasy.net
Subject: Re: [Bugme-new] [Bug 10739] New: PPPoE not working, if ethernet wire not plugged during boot
Date: Sat, 17 May 2008 22:10:18 -0700 [thread overview]
Message-ID: <20080517221018.0a31f9df.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-10739-10286@http.bugzilla.kernel.org/>
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).
On Sat, 17 May 2008 21:56:36 -0700 (PDT) bugme-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=10739
>
> Summary: PPPoE not working, if ethernet wire not plugged during
> boot
> Product: Networking
> Version: 2.5
> KernelVersion: 2.6.22-14-generic
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: high
> Priority: P1
> Component: Other
> AssignedTo: acme@ghostprotocols.net
> ReportedBy: for.dev.null@gmail.com
>
>
> Latest working kernel version:
>
> Earliest failing kernel version:
>
> Distribution:Ubuntu Gutsy and Hardy
>
> Hardware Environment:DFE-538TX 10/100 Ethernet Adapter
> RTL8139 Ethernet
>
>
> Software Environment:
> Problem Description:
>
> Steps to reproduce:
> 1. Shutdown machine
> 2. Unplug network wire
> 3. Restart machine
> 4. Wait for complete boot and login
> 5. Plug the network wire **
> 6. Run pppoe-discovery, pppoe-start
> 7. Cannot discovery any access concentrators / servers
> 8. Shutdown
> 9. Keep the network wire plugged
> 10. Start machine and boot
> 11. Wait for complete boot and login
> 12. Run pppoe-discovery, pppoe-start - Works this time !
>
> The network wire has to be kept connected during boot to use the
> pppoe-discovery command. If the network wire is plugged in later - the
> network/pppoe fails to work.
2.6.22 is awfully old in terms of kernel.org development. Are you able
to determine whether more recent kernels have the same problem?
This could be dependent upon the devidce driver which is in use.
Please provide details about the physical layer?
next parent reply other threads:[~2008-05-18 5:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-10739-10286@http.bugzilla.kernel.org/>
2008-05-18 5:10 ` Andrew Morton [this message]
2008-05-27 8:06 ` [Bug 10739] 8139too carrier state problem, was: PPPoE not working Jarek Poplawski
[not found] <bug-10739-11547@http.bugzilla.kernel.org/>
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=20080517221018.0a31f9df.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=for.dev.null@gmail.com \
--cc=mostrows@speakeasy.net \
--cc=netdev@vger.kernel.org \
/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).