From: Stephen Hemminger <shemminger@linux-foundation.org>
To: Mike Houston <mikeserv@bmts.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.22-rc2
Date: Mon, 21 May 2007 10:37:55 -0700 [thread overview]
Message-ID: <20070521103755.51b954e1@freepuppy> (raw)
In-Reply-To: <20070521131055.0017404f.mikeserv@bmts.com>
On Mon, 21 May 2007 13:10:55 -0400
Mike Houston <mikeserv@bmts.com> wrote:
> On Mon, 21 May 2007 08:45:49 -0700
> Stephen Hemminger <shemminger@linux-foundation.org> 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.
--
Stephen Hemminger <shemminger@linux-foundation.org>
next prev parent reply other threads:[~2007-05-21 17:38 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-19 5:17 Linux 2.6.22-rc2 Linus Torvalds
2007-05-19 6:54 ` Andrey Borzenkov
2007-05-19 14:28 ` [BUG: 2.6.22-rc2] SLAB doesn't like usb_get_configuration() Indan Zupancic
[not found] ` <6101e8c40705190950jb093d65l611995895a182ec0@mail.gmail.com>
2007-05-19 16:51 ` Fwd: " oliver pinter
2007-05-19 18:20 ` Christoph Lameter
2007-05-19 19:33 ` Greg KH
2007-05-19 22:10 ` Indan Zupancic
2007-05-20 12:57 ` Linux 2.6.22-rc2: make -j makes it unresponsive Rafael J. Wysocki
2007-05-20 13:01 ` Krzysztof Halasa
2007-05-20 13:23 ` Rafael J. Wysocki
2007-05-20 21:05 ` Linux 2.6.22-rc2 Mike Houston
2007-05-21 15:45 ` Stephen Hemminger
2007-05-21 17:10 ` Mike Houston
2007-05-21 17:37 ` Stephen Hemminger [this message]
2007-05-22 2:58 ` Mike Houston
2007-05-22 4:31 ` Stephen Hemminger
2007-05-22 4:36 ` Jeff Garzik
2007-05-22 4:42 ` Stephen Hemminger
2007-05-22 5:04 ` Linus Torvalds
2007-05-22 17:19 ` Stephen Hemminger
2007-05-22 17:54 ` H. Peter Anvin
2007-05-22 22:14 ` Mike Houston
2007-05-23 0:00 ` Linus Torvalds
2007-05-23 0:29 ` Stephen Hemminger
2007-05-23 1:53 ` Linus Torvalds
2007-05-23 14:58 ` Stephen Hemminger
2007-05-23 17:39 ` Mike Houston
2007-05-23 17:46 ` Linus Torvalds
2007-05-23 18:04 ` Stephen Hemminger
2007-05-24 18:26 ` Mike Houston
2007-05-24 22:08 ` sky2/pci issues on Gigabyte Stephen Hemminger
2007-05-24 22:48 ` Linus Torvalds
2007-05-24 23:04 ` Stephen Hemminger
2007-05-25 0:01 ` Mike Houston
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=20070521103755.51b954e1@freepuppy \
--to=shemminger@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikeserv@bmts.com \
--cc=torvalds@linux-foundation.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