From: Voluspa <lista1@telia.com>
To: linux-kernel@vger.kernel.org
Cc: akpm@osdl.org
Subject: [2.6.16-gitX] initcall at 0xffffffff804615d1: returned with error code -1
Date: Thu, 30 Mar 2006 13:11:15 +0200 [thread overview]
Message-ID: <20060330131115.73886fd4.lista1@telia.com> (raw)
CC-ing author since I'm unsure about domain responsibility. The commit
"[PATCH] initcall failure reporting" AKA
c1cda48af8b330a23206eceef3bd030b53c979cd immediately triggered:
--- dmesg-cd02b966bfcad12d1b2e265dc8dbc331d4c184c4 2006-03-30 08:41:30.000000000 +0200
+++ dmesg-c1cda48af8b330a23206eceef3bd030b53c979cd 2006-03-30 09:12:31.000000000 +0200
[...]
@@ -83,10 +83,12 @@
SCSI subsystem initialized
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
+initcall at 0xffffffff804615d1: returned with error code -1
pnp: 00:06: ioport range 0x600-0x60f has been reserved
pnp: 00:06: ioport range 0x1c0-0x1cf has been reserved
pnp: 00:06: ioport range 0x4d0-0x4d1 has been reserved
pnp: 00:06: ioport range 0xfe10-0xfe11 could not be reserved
+initcall at 0xffffffff804704fc: returned with error code 2
PCI: Failed to allocate mem resource #6:20000@f0000000 for 0000:01:00.0
PCI: Bridge: 0000:00:01.0
IO window: disabled.
Since then (now at 2.6.16-git18) the last/lower one has vanished, but the
first one remains. The patch says that the initcall function should be
printed, but it seems to need some debugging option set. Please advice if
this is of interest (the addresses do not stay constant).
Mvh
Mats Johannesson
--
next reply other threads:[~2006-03-30 11:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-30 11:11 Voluspa [this message]
2006-03-30 11:19 ` Andrew Morton
2006-03-30 12:01 ` Voluspa
2006-03-30 14:54 ` Andi Kleen
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=20060330131115.73886fd4.lista1@telia.com \
--to=lista1@telia.com \
--cc=akpm@osdl.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
all inboxes | Powered by JetHome®