Re: Linux 2.6.22-rc2

On Mon, 21 May 2007 10:37:55 -0700
Stephen Hemminger <shemminger@xxxxxxxxxxxxxxxxxxxx> wrote:

On Mon, 21 May 2007 13:10:55 -0400
Mike Houston <mikeserv@xxxxxxxx> wrote:

On Mon, 21 May 2007 08:45:49 -0700
Stephen Hemminger <shemminger@xxxxxxxxxxxxxxxxxxxx> wrote:

It's almost certainly a problem with the BIOS and hardware (not
a sky2) driver issue. Since there are many similar boards and
configurations, I made the decision not to enforce restrictions
in the driver.

May 20 15:57:48 cramit kernel: sky2 0000:04:00.0: v1.14 addr
0xf8000000 irq 16 Yukon-EC Ultra (0xb4) rev 2

Thank you for your answer. I was half wondering if that was the
case after staring at those log messages several more times. I
don't understand hardware at the low level but got thinking maybe
interrupt routing issue. There's an Nvidia PCI Express card in
there that gets IRQ 16, though it was not initialized by a driver
at the time. (plain old VGA console after fresh cold boot... no
framebuffer, no X, no nvidia module). I guess some things don't
share well.

It works well in that other OS that came with the hardware, but
that's beside the point.

It is some low level PCI Express related stuff, try latest BIOS (F9)
and if that doesn't help there is a EEPROM update from Gigabyte
for the Marvell hardware that might help.

Thanks for your suggestions, I followed through on them. It may still
be interesting/useful to hear from me that it didn't help. The
problem is the same.

My motherboard is a newer revision (Gigabyte GA-965P-DS3 Rev 3.3) and
already had the "F10" bios version, but I flashed to the latest F11
version anyways. I also flashed with the EEPROM update from Gigabyte,
from a FAQ entry for my motherboard revision.
(faq_marvell_eeprom.zip). Both operations were successful. I cleared
the CMOS and reconfigured after the bios flash too.

Incidently, it was showing IRQ 16 in that early initialization
message, but actually getting a MSI interrupt (IRQ 219, PCI-MSI-edge)

I've disabled the onboard yukon2 adapter in bios and gone
back to the PCI card now. I think we can consider the matter closed,
since it's not a problem with the driver, but just so you know, I'm
always willing to help test when it's hardware that I have.

Mike Houston
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Relevant Pages

  • [opensuse] openSUSE 10.3 not detecting SATA HD
    ... the sata_sis driver. ... I've tried turning off ACPI in bios and acpi=off which ... openSUSE 10.2 and all my hardware is working fine. ... info.product = 'USB Raw Device Access' ...
    (SuSE)
  • Re: 2008 SBS no longer boots
    ... driver issue initially, the fact that it seems to happen randomly now ... weird with a hardware problem that consistently doesn't get through boot ... other customer, even a 2 week old one, the problem immediately returned. ... There was a time when a server was fired up with a specialized OS and had a battery of tests run against each component to purposefully stress it. ...
    (microsoft.public.windows.server.sbs)
  • Re: Linux, X, ld, gcc, linking, shared libraries and stuff
    ... >> because, originally, video cards / system RAM could NOT afford to have ... > GL actually "copies" everything, but it's done by the graphics card, so ... > anyway if it's not hardware accelerated. ... installed the proper driver, then it zooms around the screen... ...
    (alt.lang.asm)
  • Re: FreeBSD 7.0 problems
    ... Ergo I can't fault the hardware in any way. ... The wifi driver complains of timeout errors. ... vendor = 'Intel Corporation' ... ABI class: ...
    (freebsd-questions)
  • Re: 2008 SBS no longer boots
    ... Any thermal issues and a lot of other hardware problems should show up ... Happen to know a tool to determine driver load order by just having the ... other customer, even a 2 week old one, the problem immediately returned. ... There was a time when a server (even one that had been "burned ...
    (microsoft.public.windows.server.sbs)