From: Len Brown <lenb@kernel.org>
To: "Sunil Naidu" <akula2.shark@gmail.com>
Cc: "Andrew Morton" <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.20-rc6-mm3 - interesting dmesg
Date: Wed, 31 Jan 2007 21:50:58 -0500 [thread overview]
Message-ID: <200701312150.58343.lenb@kernel.org> (raw)
In-Reply-To: <8355959a0701300352l27911a14t853e8dea5fcd820d@mail.gmail.com>
On Tuesday 30 January 2007 06:52, Sunil Naidu wrote:
> Hi Andrew,
>
> I did compile the same, it's a trouble free boot. I did observe
> interesting changes in the dmesg between 2.6.20-rc6 & 2.6.20-rc6-mm3
> (wondering why there are so many changes in the output). Anyway, the
> changes in brief:-
>
> a) ACPI values
The new ACPI messages are normal.
They are the result of new table management code.
thanks,
-Len
> b) pnp - iomem range reserved values
> c) Drive selection (hda, hdb)
> d) USB Subsystem - (usb1, usb2, usb3, usb4, usb5, usb 2-1) - new
> devices found.
> e) EXT3-fs - warning - maximal_mount_count reached (???)
>
> Here is the dmesg info:-
> ACPI: RSDP @ 0x000f4eb0/0x0014 (v000 ACPIAM)
> ACPI: RSDT @ 0x1f730000/0x003C (v001 INTEL D915GAV 0x20060222 MSFT 0x00000097)
> ACPI: FACP @ 0x1f730200/0x0081 (v002 INTEL D915GAV 0x20060222 MSFT 0x00000097)
> ACPI: DSDT @ 0x1f730440/0x5C05 (v001 INTEL D915GAV 0x00000001 INTL 0x02002026)
> ACPI: FACS @ 0x1f740000/0x0040
> ACPI: APIC @ 0x1f730390/0x0068 (v001 INTEL D915GAV 0x20060222 MSFT 0x00000097)
> ACPI: MCFG @ 0x1f730400/0x003C (v001 INTEL D915GAV 0x20060222 MSFT 0x00000097)
> ACPI: ASF! @ 0x1f736050/0x0099 (v016 LEGEND I865PASF 0x00000001 INTL 0x02002026)
> ACPI: TCPA @ 0x1f7360f0/0x0032 (v001 INTEL TBLOEMID 0x00000001 MSFT 0x00000097)
> ACPI: WDDT @ 0x1f736122/0x0040 (v001 INTEL OEMWDDT 0x00000001 INTL 0x02002026)
prev parent reply other threads:[~2007-02-01 2:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-30 11:52 2.6.20-rc6-mm3 - interesting dmesg Sunil Naidu
2007-02-01 2:50 ` Len Brown [this message]
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=200701312150.58343.lenb@kernel.org \
--to=lenb@kernel.org \
--cc=akpm@osdl.org \
--cc=akula2.shark@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.