From: Con Kolivas <kernel@kolivas.org>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@osdl.org>, Barry Scott <barry.scott@onelan.co.uk>
Subject: Re: broadcom 5752 in HP dc7600U works on 2.6.13 but does not working on 2.6.16
Date: Mon, 22 May 2006 21:14:11 +1000 [thread overview]
Message-ID: <200605222114.12165.kernel@kolivas.org> (raw)
In-Reply-To: <20060522035943.7829ee32.akpm@osdl.org>
On Monday 22 May 2006 20:59, Andrew Morton 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.
It looks like he's _not_ receiving eth0 interrupts if I'm not mistaken?
The lower one with apic presumably is 2.6.16
> 10: 130 XT-PIC eth0
> 16: 0 IO-APIC-level eth0
and this:
> ENABLING IO-APIC IRQs
> ..TIMER: vector=0x31 apic1=-1 pin1=-1 apic2=-1 pin2=-1
> ...trying to set up timer (IRQ0) through the 8259A ... failed.
> ...trying to set up timer as Virtual Wire IRQ... works.
looks suspiciously like a broken apic/code/workaround/whatever
I'd go with Andrew's suggestion and disable apic in your bootparameters
(noapic and/or nolapic) and possibly in your config if it corrects it
--
-ck
next prev parent reply other threads:[~2006-05-22 11:14 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 [this message]
2006-05-22 14:28 ` Barry Scott
2006-06-01 9:54 ` Barry Scott
2006-06-01 10:06 ` Andrew Morton
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=200605222114.12165.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.