search for: crash_notes

...es 2400 MHz max turbo 3 active cores 2400 MHz max turbo 2 active cores 2400 MHz max turbo 1 active cores # ls -l /sys/devices/system/cpu/cpu0/ total 0 drwxr-xr-x 6 root root 0 Feb 20 14:01 cache drwxr-xr-x 7 root root 0 Feb 20 14:01 cpuidle -r-------- 1 root root 4096 Feb 12 17:44 crash_notes lrwxrwxrwx 1 root root 0 Feb 20 14:01 node0 -> ../../node/node0 drwxr-xr-x 2 root root 0 Feb 20 14:01 thermal_throttle drwxr-xr-x 2 root root 0 Feb 20 14:01 topology # lsmod |grep cpufreq #

..."Can you double-check that 'cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq' outputs the same number as your 'cpuKHZ' setting in your config.ini file?" There is no cpufreq directory under /sys/devices/system/cpu/cpu0; all I see is "cache" (dir), "crash_notes" (a file) and "topology" (dir). However under /sys/devices/system/clocksource/clocksource0, available_clocksource reads acpi_pm jiffies tsc pit, current_clocksource reads pit. (I put in the line clocksource=pit) in the grub boot up line. Divider=10 in the bootup line causes the boo...

..., returning a range of zeros is acceptable, so do this in preference to failing. Changes since v3: * Alter the spinlocks to avoid calling xmalloc/xfree while holding the lock. * Tidy up the coding style used. Changes since v2: * Allocate crash_notes dynamically using nr_cpu_ids at boot time, rather than statically using NR_CPUS. * Fix the incorrect use of signed integers for cpu id. * Fix collateral damage to do_crashdump_trigger() and crashdump_trigger_handler caused by reordering sizeof_note() and setup_no...

Hi, This set of patches contains initial kexec/kdump implementation for Xen v3. Currently only dom0 is supported, however, almost all infrustructure required for domU support is ready. Jan Beulich suggested to merge Xen x86 assembler code with baremetal x86 code. This could simplify and reduce a bit size of kernel code. However, this solution requires some changes in baremetal x86 code. First of

Hi, This set of patches contains initial kexec/kdump implementation for Xen v3. Currently only dom0 is supported, however, almost all infrustructure required for domU support is ready. Jan Beulich suggested to merge Xen x86 assembler code with baremetal x86 code. This could simplify and reduce a bit size of kernel code. However, this solution requires some changes in baremetal x86 code. First of

Hi, This set of patches contains initial kexec/kdump implementation for Xen v3. Currently only dom0 is supported, however, almost all infrustructure required for domU support is ready. Jan Beulich suggested to merge Xen x86 assembler code with baremetal x86 code. This could simplify and reduce a bit size of kernel code. However, this solution requires some changes in baremetal x86 code. First of