From: Andrew Morton <akpm@osdl.org>
To: Barry Scott <barry.scott@onelan.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: broadcom 5752 in HP dc7600U works on 2.6.13 but does not working on 2.6.16
Date: Thu, 1 Jun 2006 03:06:15 -0700 [thread overview]
Message-ID: <20060601030615.41b70b1f.akpm@osdl.org> (raw)
In-Reply-To: <447EB970.8030005@onelan.co.uk>
On Thu, 01 Jun 2006 10:54:56 +0100
Barry Scott <barry.scott@onelan.co.uk> wrote:
> > It appears that the 2.6.13 kernel did not bring up the machine's io-APICs,
> > but 2.6.16 did. However you are receiving eth0 interrupts on 2.6.16 so
> > perhaps that's not relevant.
> >
> > Don't know, sorry - tg3 works OK for most people. You could try booting
> > with the `noapic' kernel paremeter, perhaps.
> >
> > Note that googling for "noapic" gets 212,000 hits - we've _really_ screwed
> > something up in there. Maybe one day some developer will lay hands on one
> > of these machines and will fix something.
> >
> > If noapic doesn't work (and I suspect it won't) then a next step would be
> > to compile a kernel.org kernel and start enabling debug options. It's
> > hard, when we don't know which kernel subsystem broke.
> >
> I'm willing to help get this fixed. I'm happy working inside kernels and
> drivers
> but will need some guidance to know where to focus to track this down.
ACPI, most likely.
> The obvious problem is solve is why are no interrupts being received by
> the tg3.c code.
>
> Which kernel should I use to debug this? 2.6.17 latest RC?
> Which debug options do you suggest I turn on to get closer to the problem?
> What information should I collect?
A git-bisect search would be a suitable way of finding out where it broke.
But then, we don't know if this machine has _ever_ worked with IO-APIC's
enabled, do we?
next prev parent reply other threads:[~2006-06-01 10:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-16 14:51 broadcom 5752 in HP dc7600U works on 2.6.13 but does not working on 2.6.16 Barry Scott
2006-05-22 10:30 ` Barry Scott
2006-05-22 10:59 ` Andrew Morton
2006-05-22 11:14 ` Con Kolivas
2006-05-22 14:28 ` Barry Scott
2006-06-01 9:54 ` Barry Scott
2006-06-01 10:06 ` Andrew Morton [this message]
2006-06-01 10:10 ` Barry Scott
2006-06-01 16:10 ` Andrew Morton
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=20060601030615.41b70b1f.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=barry.scott@onelan.co.uk \
--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