From: Jesper Krogh <jesper@krogh.cc>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.26-rc5
Date: Sat, 07 Jun 2008 21:44:32 +0200 [thread overview]
Message-ID: <484AE520.7050001@krogh.cc> (raw)
In-Reply-To: <alpine.LFD.1.10.0806042018060.3473@woody.linux-foundation.org>
Not that they seem critical to the system but I do get alot of these. I
cant remember having seen that before.
[ 2.874884] Switched to high resolution mode on CPU 13
[ 2.904452] system 00:06: ioport range 0x190-0x193 has been reserved
[ 2.904456] system 00:06: ioport range 0x4d0-0x4d1 has been reserved
[ 2.904465] system 00:06: iomem range 0xffb80000-0xfffffffe could not
be reserved
[ 2.904467] system 00:06: iomem range 0x0-0x0 could not be reserved
[ 2.904469] system 00:06: iomem range 0x0-0x0 could not be reserved
[ 2.904471] system 00:06: iomem range 0x0-0x0 could not be reserved
[ 2.904473] system 00:06: iomem range 0x0-0x0 could not be reserved
[ 2.904475] system 00:06: iomem range 0x0-0x0 could not be reserved
[ 2.904477] system 00:06: iomem range 0x0-0x0 could not be reserved
[ 2.904479] system 00:06: iomem range 0x0-0x0 could not be reserved
[ 2.904481] system 00:06: iomem range 0x0-0x0 could not be reserved
[ 2.904483] system 00:06: iomem range 0x0-0x0 could not be reserved
[ 2.904484] system 00:06: iomem range 0x0-0x0 could not be reserved
[ 2.904486] system 00:06: iomem range 0x0-0x0 could not be reserved
[ 2.904488] system 00:06: iomem range 0x0-0x0 could not be reserved
[ 2.904490] system 00:06: iomem range 0x0-0x0 could not be reserved
[ 2.904492] system 00:06: iomem range 0x0-0x0 could not be reserved
[ 2.904494] system 00:06: iomem range 0x0-0x0 could not be reserved
[ 2.904496] system 00:06: iomem range 0x0-0x0 could not be reserved
[ 2.904498] system 00:06: iomem range 0x0-0x0 could not be reserved
[ 2.904500] system 00:06: iomem range 0x0-0x0 could not be reserved
[ 2.904502] system 00:06: iomem range 0x0-0x0 could not be reserved
[ 2.904504] system 00:06: iomem range 0x0-0x0 could not be reserved
[ 2.904506] system 00:06: iomem range 0x0-0x0 could not be reserved
[ 2.904508] system 00:06: iomem range 0x0-0x0 could not be reserved
[ 2.904510] system 00:06: iomem range 0x0-0x0 could not be reserved
[ 2.904522] system 00:09: ioport range 0xcf8-0xcff could not be reserved
[ 2.904524] system 00:09: ioport range 0xca0-0xcaf has been reserved
[ 2.904541] system 00:09: iomem range 0xfec00000-0xfec00fff could not
be reserved
[ 2.904543] system 00:09: iomem range 0xfee00000-0xfeefffff could not
be reserved
[ 2.904545] system 00:09: iomem range 0xfefff000-0xfeffffff has been
reserved
[ 2.904547] system 00:09: iomem range 0x0-0x0 could not be reserved
[ 2.904549] system 00:09: iomem range 0x0-0x0 could not be reserved
[ 2.904551] system 00:09: iomem range 0x0-0x0 could not be reserved
[ 2.904552] system 00:09: iomem range 0x0-0x0 could not be reserved
[ 2.904554] system 00:09: iomem range 0x0-0x0 could not be reserved
[ 2.904556] system 00:09: iomem range 0x0-0x0 could not be reserved
[ 2.904558] system 00:09: iomem range 0x0-0x0 could not be reserved
[ 2.904560] system 00:09: iomem range 0x0-0x0 could not be reserved
Full dmesg log here: http://krogh.cc/~jesper/dmesg
--
Jesper
next prev parent reply other threads:[~2008-06-07 19:44 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-05 3:36 Linux 2.6.26-rc5 Linus Torvalds
2008-06-05 11:24 ` Olaf Hering
2008-06-05 12:09 ` Linux 2.6.26-rc5 (G5 SATA broken) Hugh Dickins
2008-06-05 12:54 ` Alan Cox
2008-06-05 13:44 ` [PATCH] libata: fix G5 SATA broken on -rc5 Hugh Dickins
2008-06-05 14:45 ` Olaf Hering
2008-06-06 4:36 ` Linux 2.6.26-rc5 (G5 SATA broken) Benjamin Herrenschmidt
2008-06-05 12:42 ` Linux 2.6.26-rc5 Alan Cox
2008-06-05 13:03 ` Alejandro Riveira Fernández
2008-06-05 14:54 ` Linus Torvalds
2008-06-05 15:12 ` Bjorn Helgaas
2008-06-05 16:12 ` Bjorn Helgaas
2008-06-05 16:19 ` Linus Torvalds
2008-06-05 16:32 ` Bjorn Helgaas
2008-06-05 14:43 ` Ben Dooks
2008-06-06 18:35 ` Linus Torvalds
2008-06-10 12:57 ` ACPI pull for 2.6.26? Adrian Bunk
2008-06-10 15:23 ` Len Brown
2008-06-10 15:39 ` Adrian Bunk
2008-06-05 14:47 ` Linux 2.6.26-rc5 Alex Romosan
2008-06-07 19:44 ` Jesper Krogh [this message]
2008-06-07 21:50 ` Frans Pop
2008-06-09 3:39 ` Bjorn Helgaas
2008-06-09 10:01 ` Frans Pop
2008-06-07 19:52 ` Jesper Krogh
-- strict thread matches above, loose matches on Subject: below --
2008-06-05 15:04 Lior Dotan
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=484AE520.7050001@krogh.cc \
--to=jesper@krogh.cc \
--cc=linux-kernel@vger.kernel.org \
--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