From: "Luck, Tony" <tony.luck@intel.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org
Subject: Re: 2.6.17-rc1-mm1
Date: Tue, 04 Apr 2006 23:38:51 +0000 [thread overview]
Message-ID: <20060404233851.GA6411@agluck-lia64.sc.intel.com> (raw)
In-Reply-To: <20060404014504.564bf45a.akpm@osdl.org>
On Tue, Apr 04, 2006 at 01:45:04AM -0700, Andrew Morton wrote:
> - VGA on ia64 is broken - the screen comes up blank. But ia64 otherwise
> seems to work OK. I didn't have time to investigate.
Broken in base 2.6.17-rc1 too :-( VGA comes up and prints a
few messages, and then goes wonky and dies. Comparing
what I _think_ I saw with the dmesg output, it appears to
die here:
[ 6.416740] ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 18 (level, low) -> IRQ 48
[ 6.708439] e1000: 0000:01:00.0: e1000_probe: (PCI:33MHz:32-bit) 00:03:47:fd:bb:42
[ 6.754439] e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
[ 6.761547] netconsole: not configured, aborting
[ 6.766195] initcall at 0xa0000001007c4c30: init_netconsole+0x0/0x140(): returned with error code -22
[ 6.775520] Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
DEAD DEAD DEAD
Should have gone on to say:
[ 6.781924] ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
[ 6.790052] ICH4: IDE controller at PCI slot 0000:00:1f.1
[ 6.795513] PCI: Device 0000:00:1f.1 not available because of resource collisions
[ 6.803100] ACPI: PCI Interrupt 0000:00:1f.1[A]: no GSI
[ 6.808403] ICH4: BIOS configuration fixed.
[ 6.812646] ICH4: chipset revision 1
[ 6.816271] ICH4: not 100% native mode: will probe irqs later
But I might be off by a line or two, the last bit flashed by quite quickly.
I'll start bisecting tomorrow to see when it was broken.
-Tony
next parent reply other threads:[~2006-04-04 23:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060404014504.564bf45a.akpm@osdl.org>
2006-04-04 23:38 ` Luck, Tony [this message]
2006-04-05 2:05 ` 2.6.17-rc1-mm1 Zou Nan hai
2006-04-05 16:15 ` 2.6.17-rc1-mm1 Bjorn Helgaas
2006-04-05 21:17 ` 2.6.17-rc1-mm1 Luck, Tony
2006-04-05 21:37 ` 2.6.17-rc1-mm1 Andrew Morton
2006-04-05 21:39 ` 2.6.17-rc1-mm1 Andreas Schwab
2006-04-05 22:01 ` 2.6.17-rc1-mm1 Bjorn Helgaas
2006-04-06 1:49 ` 2.6.17-rc1-mm1 Antonino A. Daplas
2006-04-06 10:21 ` 2.6.17-rc1-mm1 Russell King
2006-04-06 10:34 ` 2.6.17-rc1-mm1 Russell King
2006-04-06 14:55 ` 2.6.17-rc1-mm1 Bjorn Helgaas
2006-04-06 10:16 ` 2.6.17-rc1-mm1 Russell King
2006-04-05 22:50 ` 2.6.17-rc1-mm1 Luck, Tony
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=20060404233851.GA6411@agluck-lia64.sc.intel.com \
--to=tony.luck@intel.com \
--cc=akpm@osdl.org \
--cc=linux-ia64@vger.kernel.org \
--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