From: Michael Buesch <mb@bu3sch.de>
To: "Nelson A. de Oliveira" <naoliv@gmail.com>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
netdev@vger.kernel.org, bugme-daemon@bugzilla.kernel.org,
"Gary Zambrano" <zambrano@broadcom.com>
Subject: Re: [Bugme-new] [Bug 10473] New: Infinite loop "b44: eth0: powering down PHY"
Date: Tue, 22 Apr 2008 15:34:53 +0200 [thread overview]
Message-ID: <200804221534.53825.mb@bu3sch.de> (raw)
In-Reply-To: <9bfa9ae0804212001k5fd81642yba38386c92c8847e@mail.gmail.com>
On Tuesday 22 April 2008 05:01:54 Nelson A. de Oliveira wrote:
> Hi!
>
> Maybe this can help:
> Using a new .config, I started to enable/disable options and test.
> What I found is that if I enable "3G/1G user/kernel split", the kernel
> works (it boots normally, the network interface works, etc). If I
> select "3G/1G user/kernel split (for full 1G low memory)" I get the
> infinite loop of "b44: eth0: powering down PHY".
Ah, so this bug isn't actually caused by a patch but rather by a
different config option.
I think we can't do much about it, currently. The device has strange
memory requirements and changing the split does actually break it.
This cannot be fixed until andi kleen's mask-allocator is merged.
This "bug" has always been there.
> Working config file (on 2.6.25) is attached.
> Diff to the non-working is below:
>
> --- working_config 2008-04-21 23:42:40.000000000 -0300
> +++ not_working_config 2008-04-21 23:55:28.000000000 -0300
> @@ -1,7 +1,7 @@
> #
> # Automatically generated make config: don't edit
> # Linux kernel version: 2.6.25
> -# Mon Apr 21 23:28:49 2008
> +# Mon Apr 21 23:43:04 2008
> #
> # CONFIG_64BIT is not set
> CONFIG_X86_32=y
> @@ -228,12 +228,12 @@
> # CONFIG_NOHIGHMEM is not set
> CONFIG_HIGHMEM4G=y
> # CONFIG_HIGHMEM64G is not set
> -CONFIG_VMSPLIT_3G=y
> -# CONFIG_VMSPLIT_3G_OPT is not set
> +# CONFIG_VMSPLIT_3G is not set
> +CONFIG_VMSPLIT_3G_OPT=y
> # CONFIG_VMSPLIT_2G is not set
> # CONFIG_VMSPLIT_2G_OPT is not set
> # CONFIG_VMSPLIT_1G is not set
> -CONFIG_PAGE_OFFSET=0xC0000000
> +CONFIG_PAGE_OFFSET=0xB0000000
> CONFIG_HIGHMEM=y
> CONFIG_ARCH_FLATMEM_ENABLE=y
> CONFIG_ARCH_SPARSEMEM_ENABLE=y
>
> Can this be the cause?
>
> Thank you!
>
> Best regards,
> Nelson
>
--
Greetings Michael.
prev parent reply other threads:[~2008-04-22 13:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-10473-10286@http.bugzilla.kernel.org/>
2008-04-18 0:12 ` [Bugme-new] [Bug 10473] New: Infinite loop "b44: eth0: powering down PHY" Andrew Morton
2008-04-18 14:06 ` Michael Buesch
2008-04-18 15:23 ` Nelson A. de Oliveira
2008-04-18 15:32 ` Michael Buesch
2008-04-18 17:12 ` Nelson A. de Oliveira
2008-04-18 17:19 ` Michael Buesch
2008-04-18 17:43 ` Nelson A. de Oliveira
2008-04-18 17:59 ` Michael Buesch
2008-04-18 18:09 ` Nelson A. de Oliveira
2008-04-18 18:18 ` Michael Buesch
2008-04-18 19:02 ` Nelson A. de Oliveira
2008-04-18 19:19 ` Michael Buesch
2008-04-18 20:38 ` Nelson A. de Oliveira
2008-04-21 18:14 ` Nelson A. de Oliveira
2008-04-21 18:21 ` Michael Buesch
2008-04-22 3:01 ` Nelson A. de Oliveira
2008-04-22 13:34 ` Michael Buesch [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=200804221534.53825.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=naoliv@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=zambrano@broadcom.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;
as well as URLs for NNTP newsgroup(s).