> I took a quick look and we are stuck in update_group_power:
>
> do {
> power += group->cpu_power;
> group = group->next;
> } while (group != child->groups);
>
> I looked at the linked list:
>
> child->groups = c07b2f74ff00
>
> and dumping g
From: Kai.Jiang
Parameter offset_in_page in function edac_mc_handle_ce should be masked
the higher bits above the page size, not the lower bits. The original input
sometimes causes crash.
Signed-off-by: Kai.Jiang
---
drivers/edac/mpc85xx_edac.c |4 ++--
1 files changed, 2 insertions(+), 2
On Wed, Jul 13, 2011 at 07:33:31PM -0500, Ayman El-Khashab wrote:
> Adds a register to the config space for the 460sx. Changes the vc0
> detect to a pll detect. maps configuration space to test the link
> status. changes the setup to enable gen2 devices to operate at gen2
> speeds. fixes mappin
Adds a register to the config space for the 460sx. Changes the vc0
detect to a pll detect. maps configuration space to test the link
status. changes the setup to enable gen2 devices to operate at gen2
speeds. fixes mapping that was not correct for the 460sx.
tested on the 460sx eiger and custo
Old code didn't check the proper registers for the 460sx and so the link check
would always fail. This changes the link check to use the config space reg and
adds the definition for the register. Also changes the vc0 to a pll check.
Sets up the port for gen2 speeds.
This uses the check_link fu
Hi Peter,
> Surely this isn't the first multi-node P7 to boot a kernel with this
> patch? If my git foo is any good it hit -next on 23rd of May.
>
> I guess I'm asking is, do smaller P7 machines boot? And if so, is
> there any difference except size?
>
> How many nodes does the thing have anywa
On Thu, 14 Jul 2011 03:02:40 +0600
Александр Лясин wrote:
> I'm writing module for "falc" device.
> During loading of the module the probe function is called.
> But request_irq(48, falc_irq_handler, IRQF_DISABLED, "falc",
> falc_staff) function return -38. I see, interrupt 48 (irq_chip) absent
>
Hi all!
I have a problem with getting interrupt on the MPC8308erdb processor
in Linux 2.6.29 from Freescale edition. I work in LTIB toolchain.
I have a SoC board with the MPC8308 processor. There are a few SPI devices on
the SPI Bus. The devices are the conclusions to the interrupts IPIC.
The dts (
From: Mahesh Salgaonkar
This patch introduces a new config option CONFIG_FA_DUMP for firmware
assisted dump feature on Powerpc (ppc64) architecture.
Signed-off-by: Mahesh Salgaonkar
---
arch/powerpc/Kconfig | 13 +
1 files changed, 13 insertions(+), 0 deletions(-)
diff --git a/a
From: Mahesh Salgaonkar
If dump is active during system reboot, shutdown or halt then invalidate
the fadump registration as it does not get invalidated automatically.
Signed-off-by: Mahesh Salgaonkar
---
arch/powerpc/kernel/setup-common.c |9 +
1 files changed, 9 insertions(+), 0 d
From: Mahesh Salgaonkar
This patch introduces an sysfs interface '/sys/kernel/fadump_release_mem' to
invalidate the last fadump registration, invalidate '/proc/vmcore', release
the reserved memory for general use and re-register for future kernel dump.
Once the dump is copied to the disk, the use
From: Mahesh Salgaonkar
With the firmware-assisted dump support we don't require a reboot when we
are in second kernel after crash. The second kernel after crash is a normal
kernel boot and has knowledge about entire system RAM with the page tables
initialized for entire system RAM. Hence once th
From: Mahesh Salgaonkar
Introduce a PT_NOTE program header that points to physical address of
vmcoreinfo_note buffer declared in kernel/kexec.c. The vmcoreinfo
note buffer is populated during crash_fadump() at the time of system
crash.
Signed-off-by: Mahesh Salgaonkar
---
arch/powerpc/kernel/f
From: Mahesh Salgaonkar
When registered for firmware assisted dump on powerpc, firmware preserves
the registers for the active CPUs during a system crash. This patch reads
the cpu register data stored in Firmware-assisted dump format (except for
crashing cpu) and converts it into elf notes and up
From: Mahesh Salgaonkar
Build the crash memory range list by traversing through system memory during
the first kernel before we register for firmware-assisted dump. After the
successful dump registration, initialize the elfcore header and populate
PT_LOAD program headers with crash memory ranges.
From: Mahesh Salgaonkar
This patch registers for firmware-assisted dump using rtas token
ibm,configure-kernel-dump. During registration firmware is informed about
the reserved area where it saves the CPU state data, HPTE table and contents
of RMR region at the time of kernel crash. Apart from thi
From: Mahesh Salgaonkar
Reserve the memory during early boot to preserve CPU state data, HPTE region
and RMR region data in case of kernel crash. At the time of crash, powerpc
firmware will store CPU state data, HPTE region data and move RMR region
data to the reserved memory area.
If the firmwa
From: Mahesh Salgaonkar
Documentation for firmware-assisted dump. This document is based on the
original documentation written for phyp assisted dump by Linas Vepstas
and Manish Ahuja, with few changes to reflect the current implementation.
Signed-off-by: Mahesh Salgaonkar
---
Documentation/po
Hi All,
Please find the series of the patchset that implements firmware-assisted
dump mechanism to capture kernel crash dump for Powerpc architecture. The
firmware-assisted dump is a robust mechanism to get reliable kernel crash
dump with assistance from firmware. This approach does not use kexec,
Hi,
We have a MPC7410 based board and we are trying to port Linux on the same.
the Board Architecture/UART connection is as follows
*MPC7410 ---> MPC107(PCI Bridge) ---> PLX9052(PCI->Local Bus Bridge) --->
UART*
The address mapping is as follows
PLX9052 @ 0xDB00_
UART @ 0xDB
Hi
The problem was that "reverse-path filtering" was enabled. after
disabling reverse-path filtering I could receive broadcasts as
expected.
As a side note - interface does not need to be in promiscuous mode
cheers pieter
On 13/07/2011 10:03,
The 64-bit Book-E parts (to date) dont utilize the 'server' class
perfmon. So building or depending on it makes no sense (and does break
FSL Book-E 64-bit support). Move the selection of PPC_HAVE_PMU_SUPPORT
to be based on PPC_BOOK3S_64.
Based on a patch from Scott Wood.
Signed-off-by: Kumar Ga
On Wed, Jul 13, 2011 at 9:02 AM, Ayman El-Khashab wrote:
> I've had problems with the mpt2sas driver
> (drivers/scsi/mpt2sas/mpt2sas_base.c) when using it on my
> ppc44x. Basically, there is a check in the code for
> BITS_PER_LONG and certain code is executed if it is 64 vs 32
> bit. I am guessi
Hi,
> > Add poll_get_char and poll_put_char for kdb. Enable kdb at boot
> > with:
>
> Did you mean "...for kgdb. Enable kgdb at boot.." ?
>
> I thought kdb and kgdb shared some infrastructure now, but your patch
> and comments seem to be all about kgdb.
No I do mean kdb :) From the Documentat
I've had problems with the mpt2sas driver
(drivers/scsi/mpt2sas/mpt2sas_base.c) when using it on my
ppc44x. Basically, there is a check in the code for
BITS_PER_LONG and certain code is executed if it is 64 vs 32
bit. I am guessing it is a problem with the driver but it
only shows up on powerpc.
On Wed, Jul 13, 2011 at 1:44 AM, Anton Blanchard wrote:
>
> Add poll_get_char and poll_put_char for kdb. Enable kdb at boot with:
Did you mean "...for kgdb. Enable kgdb at boot.." ?
I thought kdb and kgdb shared some infrastructure now, but your patch
and comments seem to be all about kgdb.
jo
On Wed, Jul 13, 2011 at 12:28:36AM -0500, Kumar Gala wrote:
>
>On Jul 12, 2011, at 1:44 AM, Suzuki K. Poulose wrote:
>
>> Changes from V1: Uses a tmp mapping in the other address space to setup
>> the 1:1 mapping (suggested by Sebastian Andrzej Siewior).
>>
>> Note: Should we do the
On Sat, Jul 09, 2011 at 03:38:14PM -0500, Timur Tabi wrote:
> Instead of using ill-defined numbers (0, 1, and 2) for the monitor port, allow
> the user to specify the port by name ("dvi", "lvds", or "dlvds"). This works
> on the kernel command line, the module command-line, and the sysfs "monitor"
Hi All
Im running Linux 2.6.32.14 on an embedded MPC4858.
One of the Application (CLI) must reciece a UDP broadcast packet.
The problem is that I only receive packets broadcast from within the
same subnet (192.168.0.x) even though the broadcast app sends the
broadcast to 255.255.255.255.
Le mercredi 13 juillet 2011 à 09:20 +0200, Thomas De Schampheleire a
écrit :
> I just want to mention that, although you seem to think that we
> shouldn't have created this thread in the first place, your and Eric's
> remarks have actually helped us in identifying the problem and
> increasing our
On Tue, Jul 12, 2011 at 2:13 PM, David Miller wrote:
> From: David Miller
> Date: Tue, 12 Jul 2011 05:08:17 -0700 (PDT)
>
>> From: Ronny Meeus
>> Date: Tue, 12 Jul 2011 14:03:04 +0200
>>
>>> but we still see the issue "BUG: sleeping function called from invalid
>>> context":
>>>
>>> [ 91.0159
31 matches
Mail list logo