On 01/02/2011 11:51 PM, Ben Hutchings wrote:
Yes, I see, it doesn't say that this is a fatal error for watchdog
initialisation.
I've seen just now the patch (v1 and v2) you sent upstream: thank you
very much for improving the error message and the documentation.
Very very appreciated.
Cesar
On Sun, 2011-01-02 at 23:37 +0100, Cesare Leonardi wrote:
> On 01/02/2011 10:44 PM, Ben Hutchings wrote:
> >> Then add +1 to what Michael Biebl already asked: why that message should
> >> be showed?
> >
> > Because the watchdog feature was enabled at compile-time and you
> > presumably want it to w
On 01/02/2011 10:44 PM, Ben Hutchings wrote:
Then add +1 to what Michael Biebl already asked: why that message should
be showed?
Because the watchdog feature was enabled at compile-time and you
presumably want it to work. If you add 'nowatchdog' to the kernel
parameters then the kernel will no
On Wed, 2010-12-29 at 21:34 +0100, Cesare Leonardi wrote:
> On 12/27/2010 09:36 PM, Cesare Leonardi wrote:
> > Grub command lines are identical except that "lapic hpet=force" in
> > normal boot is substituted by "single" in recovery mode.
>
> I've found that if i remove "lapic" from the command li
On 12/27/2010 09:36 PM, Cesare Leonardi wrote:
Grub command lines are identical except that "lapic hpet=force" in
normal boot is substituted by "single" in recovery mode.
I've found that if i remove "lapic" from the command line, then the NMI
error appears. And in fact that paramter it's not p
On Mon, 2010-12-27 at 22:31 +0100, Cesare Leonardi wrote:
> On 12/27/2010 10:16 PM, Ben Hutchings wrote:
> > In a default GRUB configuration, kernel logging to the console is
> > limited using the 'quiet' parameter, except in recovery mode.
>
> I use "quiet" in recovery mode too.
> Do you mean tha
On 12/27/2010 10:16 PM, Ben Hutchings wrote:
In a default GRUB configuration, kernel logging to the console is
limited using the 'quiet' parameter, except in recovery mode.
I use "quiet" in recovery mode too.
Do you mean that when i use the "single" parameter, "quiet" is less quiet?
Cesare.
On Mon, 2010-12-27 at 22:02 +0100, Cesare Leonardi wrote:
> On 12/27/2010 09:48 PM, Michael Prokop wrote:
> > This is not an initramfs-tools issue. Re-assigning to linux-2.6 and
> > leaving it to the kernel maintainers how to proceed with this issue
>
> Ah, thanks! In fact i were not sure at what
On 12/27/2010 09:48 PM, Michael Prokop wrote:
This is not an initramfs-tools issue. Re-assigning to linux-2.6 and
leaving it to the kernel maintainers how to proceed with this issue
Ah, thanks! In fact i were not sure at what package address this bug.
(see #599368 for similar issue).
Sorry,
reassign 608138 linux-2.6
thanks
* Cesare Leonardi [Mon Dec 27, 2010 at 09:36:44PM +0100]:
> Every time i boot in recovery mode, i see this message:
> -
> Loading Linux 2.6.37-rc5-686 ...
> Loading initial ramdisk ...
> [0.020165] NMI watchdog failed to create perf event on cpu0: ffa
Package: initramfs-tools
Version: 0.98.7
Severity: normal
Every time i boot in recovery mode, i see this message:
-
Loading Linux 2.6.37-rc5-686 ...
Loading initial ramdisk ...
[0.020165] NMI watchdog failed to create perf event on cpu0: ffa1
Loading, please wait...
resume: libgcrypt v
11 matches
Mail list logo
