From: Andrew Morton <akpm@digeo.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, Martin.Bligh@us.ibm.com
Subject: Re: problems with 2.5.61-mm1
Date: Sat, 15 Feb 2003 01:09:54 -0800 [thread overview]
Message-ID: <20030215010954.44153675.akpm@digeo.com> (raw)
In-Reply-To: <3E4E0153.3000008@us.ibm.com>
Dave Hansen <haveblue@us.ibm.com> wrote:
>
> I've been beating on various versions of 2.5.59 all day long with no
> problems that I didn't cause. I started testing 2.5.61-mm1 and rand
> into a couple problems right away.
>
> The first I really doubt is -mm specific. I gets _loads_ of these, and
> the e1000 isn't working:
> NETDEV WATCHDOG: eth0: transmit timed out
> e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex
>
> The e1000 driver hasn't been touched in weeks.
Don't know.
> Here's my /proc/interrupts:
> http://www.sr71.net/linux/interrupts
> I'm pretty sure we can see the problem here. Almost all interrupts are
> going to CPU0. Is this a summit thing?
No, that's the new irq balancing code. It only starts distributing
interrupts to other CPUs when the load gets higher. See how it
spread the ethernet interrupts. Apparently this is as-designed.
> The other looks a bit more insidious.
>
> Unable to handle kernel NULL pointer dereference at virtual address 0000003d
It might be best to test 2.5.61 first.
next prev parent reply other threads:[~2003-02-15 8:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-15 8:58 Dave Hansen
2003-02-15 9:09 ` Andrew Morton [this message]
2003-02-15 18:20 ` Martin J. Bligh
2003-02-15 18:47 ` Dave Hansen
2003-02-15 21:11 ` Martin J. Bligh
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=20030215010954.44153675.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=Martin.Bligh@us.ibm.com \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®