From: Randy Dunlap <rdunlap@xenotime.net>
To: Nick Bowler <nbowler@elliptictech.com>
Cc: Karel Zak <kzak@redhat.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
util-linux@vger.kernel.org
Subject: Re: [ANNOUNCE] util-linux v2.20
Date: Wed, 31 Aug 2011 23:38:45 -0700 [thread overview]
Message-ID: <20110831233845.d9435e52.rdunlap@xenotime.net> (raw)
In-Reply-To: <20110901051558.GA14777@elliptictech.com>
On Thu, 1 Sep 2011 01:15:58 -0400 Nick Bowler wrote:
> Hi Karel,
>
> On 2011-08-29 14:23 +0200, Karel Zak wrote:
> > The stable util-linux 2.20 release is available at
> >
> > ftp://ftp.kernel.org/pub/linux/utils/util-linux/v2.20/
> >
> > Feedback and bug reports, as always, are welcomed.
>
> Just upgraded on one of my machines today, and I was surprised to
> discover that only a small portion of my kernel log was printed by
> dmesg. "busybox dmesg" and "dmesg -r" both print the full log (~2000
> lines), but plain "dmesg" prints only the first ~150 lines or so. 2.19
> dmesg worked fine.
>
> The last few lines printed by plain "dmesg" are:
>
> [...]
> ACPI: Added _OSI(Module Device)
> ACPI: Added _OSI(Processor Device)
> ACPI: Added _OSI(3.0 _SCP Extensions)
> ACPI: Added _OSI(Processor Aggregator Device)
> ACPI: EC: Look up EC in DSDT
> ACPI: Executed 1 blocks of module-level executable AML code
> ACPI: Actual Package length (234) is larger than NumElements field (3), truncated
>
> Adding the -r option gives much more:
>
> [...]
> <6>ACPI: Added _OSI(Module Device)
> <6>ACPI: Added _OSI(Processor Device)
> <6>ACPI: Added _OSI(3.0 _SCP Extensions)
> <6>ACPI: Added _OSI(Processor Aggregator Device)
> <7>ACPI: EC: Look up EC in DSDT
> <4>ACPI: Executed 1 blocks of module-level executable AML code
> <4>ACPI: Actual Package length (234) is larger than NumElements field (3), truncated
> <4>
> <6>ACPI: Interpreter enabled
> <6>ACPI: (supports S0 S5)
> <6>ACPI: Using IOAPIC for interrupt routing
> <6>ACPI: Power Resource [ISAV] (on)
> <6>ACPI: No dock devices found.
> [...]
>
> So it looks like it's tripping over the blank line in the log?
Karel sent a message earlier (Wed. AUG 31) to util-linux@vger.kernel.org,
Subject: dmesg(1) bug
that explains that and includes a patch.
See http://marc.info/?l=util-linux-ng&m=131478775113617&w=2
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
prev parent reply other threads:[~2011-09-01 6:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-29 12:23 Karel Zak
2011-08-29 13:35 ` richard -rw- weinberger
2011-08-30 20:19 ` Valdis.Kletnieks
2011-09-01 5:15 ` Nick Bowler
2011-09-01 6:38 ` Randy Dunlap [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=20110831233845.d9435e52.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=kzak@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nbowler@elliptictech.com \
--cc=util-linux@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®