[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110901051558.GA14777@elliptictech.com>
Date: Thu, 1 Sep 2011 01:15:58 -0400
From: Nick Bowler <nbowler@...iptictech.com>
To: Karel Zak <kzak@...hat.com>
Cc: linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
util-linux@...r.kernel.org
Subject: Re: [ANNOUNCE] util-linux v2.20
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?
Cheers,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists