In message 4e1543b6.9060...@linux.vnet.ibm.com you wrote:
Hi ,
Problem Description:
Firmware update using the update_flash -ffilename results to soft lockup
BUG
FLASH: preparing saved firmware image for flash
FLASH: flash image is 50141296 bytes
FLASH: performing flash and reboot
FLASH:
On Thursday 07 July 2011 11:42 AM, Michael Neuling wrote:
In message4e1543b6.9060...@linux.vnet.ibm.com you wrote:
Hi ,
Problem Description:
Firmware update using the update_flash -ffilename results to soft lockup
BUG
FLASH: preparing saved firmware image for flash
FLASH: flash image is
On P1022DS both ethernet controllers are connected to RGMII PHYs
accessible via MDIO bus. Remove fixed-link property from ethernet
nodes as they only required when fixed link PHYs without MDIO bus
are used.
Signed-off-by: Felix Radensky fe...@embedded-sol.com
---
As a result of changes to Kconfig files, we no longer enable
the lockup and hung task detectors. Both are very light weight
and provide useful information in the event of a hang, so
reenable them.
...
+CONFIG_LOCKUP_DETECTOR=y
+CONFIG_DETECT_HUNG_TASK=y
Is one of thise responsible for
Hi,
linux-3.0-rc fails to boot on a power7 system with 1TB ram and 896 CPUs.
While the initial boot log shows a soft-lockup [1], the machine is hung after.
Dropping into xmon shows the cpus are all struck at:
cpu 0xa: Vector: 100 (System Reset) at [c00fae51fae0]
pc:
On Thu, 2011-07-07 at 15:52 +0530, Mahesh J Salgaonkar wrote:
2.6.39 booted fine on the system and a git bisect shows commit cd4ea6ae -
sched: Change NODE sched_domain group creation as the cause.
Weird, there's no locking anywhere around there. The typical problems
with this patch-set were
On 2011-07-07 12:59:35 Thu, Peter Zijlstra wrote:
On Thu, 2011-07-07 at 15:52 +0530, Mahesh J Salgaonkar wrote:
2.6.39 booted fine on the system and a git bisect shows commit cd4ea6ae -
sched: Change NODE sched_domain group creation as the cause.
Weird, there's no locking anywhere
On Thu, 2011-07-07 at 17:25 +0530, Mahesh J Salgaonkar wrote:
I guess I'm asking is, do smaller P7 machines boot? And if so, is there
any difference except size?
Yes, the smaller P7 machine that I have with 20 CPUs and 2GB ram boots
fine with 3.0.0-rc.
That sounds like a single node
We use both MSCAN controllers on this board, so do not disable
them in the device tree.
Signed-off-by: Anatolij Gustschin ag...@denx.de
---
arch/powerpc/boot/dts/digsy_mtc.dts |8
1 files changed, 0 insertions(+), 8 deletions(-)
diff --git a/arch/powerpc/boot/dts/digsy_mtc.dts
On Jul 1, 2011, at 5:09 PM, Greg KH wrote:
On Thu, Jun 23, 2011 at 06:33:57AM -0500, Kumar Gala wrote:
On some architectures we need to setup pdev_archdata before we add the
device. Waiting til a bus_notifier is too late since we might need the
pdev_archdata in the bus notifier. One
mpc85xx_smp_init platform init function assumed that smp_ops.message_pass
was set to default arch dependent smp_muxed_ipi_message_pass.
However this does not seem to happen. Moreover, the arch specific code
in arch/powerpc/kernel/smp.c handles smp_ops.message_pass == NULL and if so
calls the
On Thu, Jul 07, 2011 at 08:55:44AM -0500, Kumar Gala wrote:
On Jul 1, 2011, at 5:09 PM, Greg KH wrote:
On Thu, Jun 23, 2011 at 06:33:57AM -0500, Kumar Gala wrote:
On some architectures we need to setup pdev_archdata before we add the
device. Waiting til a bus_notifier is too late since
I'll expand a bit on my previous message. Here's a more detailed dump of what
happens when my system receives a second
interrupt (the 1st one works fine) from my hardware:
[ 263.586996] do_IRQ: stack overflow: 1920
[ 263.590785] Call Trace:
[ 263.593275] [c7792780] [c00073ac]
Felix Radensky wrote:
On P1022DS both ethernet controllers are connected to RGMII PHYs
accessible via MDIO bus. Remove fixed-link property from ethernet
nodes as they only required when fixed link PHYs without MDIO bus
are used.
Signed-off-by: Felix Radensky fe...@embedded-sol.com
Commit 4018294b53d1dae026880e45f174c1cc63b5d435 broke the ppc4xx_edac driver at
line 210 where the struct member is missing a comma.
Signed-off-by: Mike Williams m...@mikebwilliams.com
---
drivers/edac/ppc4xx_edac.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git
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
device.
Note that changing the monitor port does not currently work on
On Thu, Jul 07, 2011 at 02:49:50PM +0200, Anatolij Gustschin wrote:
We use both MSCAN controllers on this board, so do not disable
them in the device tree.
Signed-off-by: Anatolij Gustschin ag...@denx.de
Applied, thanks.
g.
---
arch/powerpc/boot/dts/digsy_mtc.dts |8
1
On Fri, 2011-07-01 at 18:44 +0200, Segher Boessenkool wrote:
CPC925/CPC945 use special window to access host bridge
functionality of
u3-ht. Provide a way to access this device.
Why? Is anything going to use it?
+static int u3_ht_root_read_config(struct pci_controller *hose, u8
On Tue, 2011-07-05 at 16:19 +0200, Guillaume Dargaud wrote:
Hello all,
one of my drivers is causing a kernel panic and I _think_ it happens in the
1st call to the interrupt routine.
What kind of information can I extract from the following ?
Is it like a core dump that I can load with the
Hello,
I am using perf to collect data from powerpc and analyze the data on a
local server.
When I am trying to use perf report the error fatal:imcompatible file
format comes up. It is noticed that the error is generated due to
perf_header size dismatch.
The issue is caused by that the powerpc
In message 4e155f15.1030...@linux.vnet.ibm.com you wrote:
This is a multi-part message in MIME format.
--===3790206687486290502==
Content-Type: multipart/alternative;
boundary=080309090408040507080807
This is a multi-part message in MIME format.
On some architectures we need to setup pdev_archdata before we add the
device. Waiting til a bus_notifier is too late since we might need the
pdev_archdata in the bus notifier. One example is setting up of dma_mask
pointers such that it can be used in a bus_notifier.
We add weak noop version of
We have a long standing issues with platform devices not have a valid
dma_mask pointer. This hasn't been an issue to date as no platform
device has tried to set its dma_mask value to a non-default value.
Signed-off-by: Kumar Gala ga...@kernel.crashing.org
---
arch/powerpc/kernel/setup-common.c
The only reason to require a dma_ops struct is to see if it has
implemented set_dma_mask. If not we can fall back to setting the mask
directly.
This resolves an issue with how to sequence the setting of a DMA mask
for platform devices. Before we had an issue in that we have no way of
setting
On Jul 7, 2011, at 9:11 AM, Greg KH wrote:
On Thu, Jul 07, 2011 at 08:55:44AM -0500, Kumar Gala wrote:
On Jul 1, 2011, at 5:09 PM, Greg KH wrote:
On Thu, Jun 23, 2011 at 06:33:57AM -0500, Kumar Gala wrote:
On some architectures we need to setup pdev_archdata before we add the
device.
On Jul 7, 2011, at 8:44 AM, Laurentiu TUDOR wrote:
mpc85xx_smp_init platform init function assumed that smp_ops.message_pass
was set to default arch dependent smp_muxed_ipi_message_pass.
However this does not seem to happen. Moreover, the arch specific code
in arch/powerpc/kernel/smp.c
On Jul 7, 2011, at 2:37 AM, Felix Radensky wrote:
On P1022DS both ethernet controllers are connected to RGMII PHYs
accessible via MDIO bus. Remove fixed-link property from ethernet
nodes as they only required when fixed link PHYs without MDIO bus
are used.
Signed-off-by: Felix Radensky
On Jun 28, 2011, at 2:52 AM, Mingkai Hu wrote:
P2040RDB Specification:
---
2Gbyte unbuffered DDR3 SDRAM SO-DIMM(64bit bus)
128 Mbyte NOR flash single-chip memory
256 Kbit M24256 I2C EEPROM
16 Mbyte SPI memory
SD connector to interface with the SD memory card
dTSEC1:
On Jun 28, 2011, at 2:54 PM, Becky Bruce wrote:
From: Becky Bruce bec...@kernel.crashing.org
This is used to round-robin TLBCAM entries.
Signed-off-by: Becky Bruce bec...@kernel.crashing.org
---
arch/powerpc/include/asm/mmu.h |5 +
arch/powerpc/kernel/smp.c |4
On Thu, Jul 07, 2011 at 11:00:41PM -0500, Kumar Gala wrote:
On some architectures we need to setup pdev_archdata before we add the
device. Waiting til a bus_notifier is too late since we might need the
pdev_archdata in the bus notifier. One example is setting up of dma_mask
pointers such
On Jul 7, 2011, at 11:22 PM, Greg KH wrote:
On Thu, Jul 07, 2011 at 11:00:41PM -0500, Kumar Gala wrote:
On some architectures we need to setup pdev_archdata before we add the
device. Waiting til a bus_notifier is too late since we might need the
pdev_archdata in the bus notifier. One
31 matches
Mail list logo
