> I also checked all the other .ko files and they were properly aligned. So I
> think this should hopefully work, and I like that its not a per-arch fix.
>
> Sachin, sorry to bother you again, but I'm hoping you can try David's latest
> patch to scripts/module-common.lds, just to test in your s
Jason Baron writes:
...
> I also checked all the other .ko files and they were properly aligned.
> So I think this should hopefully work, and I like that its not a
> per-arch fix.
>
> Sachin, sorry to bother you again, but I'm hoping you can try David's
> latest patch to scripts/module-common.l
Stewart Smith writes:
> Vipin K Parashar writes:
>> Added check for OPAL_WRONG_STATE error code returned from OPAL.
>> Currently Linux flashes "unexpected error" over console for this
>> error. This will avoid throwing such message and return I/O error
>> for such OPAL failures.
>>
>> Signed-off
Hi Linus,
Please pull the second set of powerpc updates for 4.11.
This includes an update of the disassembly code in xmon, from binutils. We've
received permission from all the authors of the relevant binutils changes to
relicense their changes to the relevant files from GPLv3 to GPLv2. That was
On Tue, Feb 28, 2017 at 05:03:48PM +1100, Suraj Jitindar Singh wrote:
> On POWER9 the ibm,client-architecture-support (CAS) negotiation process
> has been updated to change how the host to guest negotiation is done for
> the new hash/radix mmu as well as the nest mmu, process tables and guest
> tra
[resending this since it didn't get delivered to the list]
On Tue, 2017-02-28 at 12:52 +0530, Vaibhav Jain wrote:
> The patch resets the freeze counter on eeh_pe struct for PHB
> associated with the cxl pci adapter. This would enable re-flashing of
> the cxl-adapter beyond the default limit of 5.
On Tue, 2017-02-28 at 12:32 +0530, Vaibhav Jain wrote:
> This patch introduces function eeh_pe_reset_freeze_counter which can
> be used to reset the PE's freeze count variable outside eeh code. This
> is useful for devices that can acquire a different personality after
> a PERST event (e.g FPGA Ada
On Tue, 2017-02-28 at 12:32 +0530, Vaibhav Jain wrote:
> This patch introduces a new function named
> eeh_pe_update_freeze_counter replacing existing function
> eeh_pe_update_time_stamp. The new function also manages the value of
> freeze_count along with tstamp to track the number of times the PE
On 27/02/17 21:56, Michael Ellerman wrote:
+/* HDAT attribute for sysfs */
+static struct bin_attribute hdat_attr = {
+ .attr = {.name = "hdat", .mode = 0444},
ajd and oohal report to my office.
...ACK... :/
--
Andrew Donnellan
On Tue, 2017-02-28 at 14:55 +, Laurentiu Tudor wrote:
> Hi,
>
> Some more information on the crash, inline.
>
> On 02/17/2017 02:18 PM, Aneesh Kumar K.V wrote:
> >
> > laurentiu.tu...@nxp.com writes:
> >
> > >
> > > From: Laurentiu Tudor
> > >
> > > On 32-bit book-e machines, hugepd_ok()
On 02/28/2017 03:15 PM, David Daney wrote:
On 02/28/2017 11:34 AM, Jason Baron wrote:
On 02/28/2017 02:22 PM, David Daney wrote:
On 02/28/2017 11:05 AM, David Daney wrote:
On 02/28/2017 10:39 AM, Jason Baron wrote:
[...]
I suspect that the alignment of the __jump_table section in the .ko
On 28/02/17 17:03, Suraj Jitindar Singh wrote:
> On POWER9 the hypervisor requires the guest to decide whether it would
> like to use a hash or radix mmu model at the time it calls
> ibm,client-architecture-support (CAS) based on what the hypervisor has
> said it's allowed to do. It is possible t
Vipin K Parashar writes:
> Added check for OPAL_WRONG_STATE error code returned from OPAL.
> Currently Linux flashes "unexpected error" over console for this
> error. This will avoid throwing such message and return I/O error
> for such OPAL failures.
>
> Signed-off-by: Vipin K Parashar
> ---
> C
Matt Brown writes:
> The HDAT data area is consumed by skiboot and turned into a device-tree.
> In some cases we would like to look directly at the HDAT, so this patch
> adds a sysfs node to allow it to be viewed. This is not possible through
> /dev/mem as it is reserved memory which is stopped b
On 02/28/2017 11:34 AM, Jason Baron wrote:
On 02/28/2017 02:22 PM, David Daney wrote:
On 02/28/2017 11:05 AM, David Daney wrote:
On 02/28/2017 10:39 AM, Jason Baron wrote:
[...]
I suspect that the alignment of the __jump_table section in the .ko
files is not correct, and you are seeing so
On 02/28/2017 02:22 PM, David Daney wrote:
> On 02/28/2017 11:05 AM, David Daney wrote:
>> On 02/28/2017 10:39 AM, Jason Baron wrote:
>>>
> [...]
I suspect that the alignment of the __jump_table section in the .ko
files is not correct, and you are seeing some sort of problem due to
On 02/28/2017 11:05 AM, David Daney wrote:
On 02/28/2017 10:39 AM, Jason Baron wrote:
[...]
I suspect that the alignment of the __jump_table section in the .ko
files is not correct, and you are seeing some sort of problem due to
that.
Hi,
Yes, if you look at the trace that Sachin sent th
On 02/28/2017 10:39 AM, Jason Baron wrote:
On 02/28/2017 01:16 PM, David Daney wrote:
On 02/28/2017 08:21 AM, Steven Rostedt wrote:
On Tue, 28 Feb 2017 10:25:46 +0530
Sachin Sant wrote:
File: ./net/ipv4/xfrm4_input.o
[12] __jump_table PROGBITS 000639
18 1
On 02/28/2017 01:16 PM, David Daney wrote:
On 02/28/2017 08:21 AM, Steven Rostedt wrote:
On Tue, 28 Feb 2017 10:25:46 +0530
Sachin Sant wrote:
File: ./net/ipv4/xfrm4_input.o
[12] __jump_table PROGBITS 000639
18 18 WAM 0 0 1
File: ./net/ipv4/udplite.o
F
On 02/28/2017 08:21 AM, Steven Rostedt wrote:
On Tue, 28 Feb 2017 10:25:46 +0530
Sachin Sant wrote:
File: ./net/ipv4/xfrm4_input.o
[12] __jump_table PROGBITS 000639 18 18 WAM
0 0 1
File: ./net/ipv4/udplite.o
File: ./net/ipv4/xfrm4_output.o
[ 9] __jump_
Hi Nick,
On Fri, Feb 17, 2017 at 12:09 AM, Nicholas Piggin wrote:
> The ISA specifies power save wakeup can cause a machine check interrupt.
> The machine check handler currently has code to handle that for POWER8,
> but POWER9 crashes when trying to execute the P8 style sleep
> instructions.
>
>
On Tue, 28 Feb 2017 10:25:46 +0530
Sachin Sant wrote:
> File: ./net/ipv4/xfrm4_input.o
> [12] __jump_table PROGBITS 000639 18 18
> WAM 0 0 1
> File: ./net/ipv4/udplite.o
> File: ./net/ipv4/xfrm4_output.o
> [ 9] __jump_table PROGBITS00
On Tue, 28 Feb 2017 20:38:19 +0530
Gautham R Shenoy wrote:
> Hi Nick,
>
> On Fri, Feb 17, 2017 at 12:08 AM, Nicholas Piggin wrote:
> > The POWER8 idle code has a neat trick of programming the power on engine
> > to restore a low bit into HSPRG0, so idle wakeup code can test and see
> > if it ha
Hi Nick,
On Fri, Feb 17, 2017 at 12:09 AM, Nicholas Piggin wrote:
> There is only one caller, so this reduces spaghetti of subsequent
> callees returning into the caller.
>
> Signed-off-by: Nicholas Piggin
This patch is good!
Reviewed-by: Gautham R. Shenoy
--
Thanks and Regards
gautham.
Hi Nick,
On Fri, Feb 17, 2017 at 12:08 AM, Nicholas Piggin wrote:
> This reduces the number of nops for POWER8
>
> Signed-off-by: Nicholas Piggin
This change looks ok to me.
Reviewed-by: Gautham R. Shenoy
> ---
> arch/powerpc/kernel/idle_book3s.S | 15 +++
> 1 file changed, 7 in
Hi Nick,
On Fri, Feb 17, 2017 at 12:08 AM, Nicholas Piggin wrote:
> The POWER8 idle code has a neat trick of programming the power on engine
> to restore a low bit into HSPRG0, so idle wakeup code can test and see
> if it has been programmed this way and therefore lost all state. Restore
> time c
Hi,
Some more information on the crash, inline.
On 02/17/2017 02:18 PM, Aneesh Kumar K.V wrote:
> laurentiu.tu...@nxp.com writes:
>
>> From: Laurentiu Tudor
>>
>> On 32-bit book-e machines, hugepd_ok() does not take
>> into account null hugepd values, causing this crash at boot:
>>
>> Unable to
On Tue, 28 Feb 2017 15:04:15 +1100
Michael Ellerman wrote:
kernel/trace/ftrace.c more obvious.
>
> I don't know if it's really worth keeping the names the same across
> arches, especially as we already have:
>
> arch/arm64/kernel/entry-ftrace.S
> arch/arm/kernel/entry-ftrace.S
> arch/blac
Hi Wolfgang,
Thanks for reporting!
On 02/28/2017 01:47 PM, Wolfgang Ocker wrote:> On Tue, 2017-02-28 at
10:57 +0100, Wolfgang Ocker wrote:
>> With kernel v4.10.1 and huge tlb enabled (CONFIG_HUGETLBFS=y) I see
>> the
>> following oops on a P1010:
>
> Just saw that there is already a fix:
On Tue, 2017-02-28 at 10:57 +0100, Wolfgang Ocker wrote:
> With kernel v4.10.1 and huge tlb enabled (CONFIG_HUGETLBFS=y) I see
> the
> following oops on a P1010:
Just saw that there is already a fix:
https://lists.ozlabs.org/pipermail/linuxppc-dev/2017-February/154204.html
Thanks!
Hi Nick,
This patch is fine by me.
Reviewed-by: Gautham R. Shenoy
On Fri, Feb 17, 2017 at 12:08 AM, Nicholas Piggin wrote:
> Should be no functional change.
>
> Signed-off-by: Nicholas Piggin
> ---
> arch/powerpc/kernel/exceptions-64s.S | 26 +---
> arch/powerpc/kernel/id
With kernel v4.10.1 and huge tlb enabled (CONFIG_HUGETLBFS=y) I see the
following oops on a P1010:
Freeing unused kernel memory: 428K
This architecture does not have kernel memory protection.
Unable to handle kernel paging request for data at address 0x8000
Faulting instruction address: 0xc0
Hi Arnd,
On 02/27/2017 10:42 PM, Arnd Bergmann wrote:
> The fsl-mc-bus driver in staging contains a copy of the standard
> 'ranges' property parsing algorithm with a hack to treat a missing
> property the same way as an empty one. This code produces false-positive
> warnings for me in an allmodcon
Ben Hutchings writes:
> [ Unknown signature status ]
> On Mon, 2017-02-27 at 14:40 +0900, Masahiro Yamada wrote:
>> Since commit 6b22b3d1614a ("kbuild: Allow using host dtc instead of
>> kernel's copy"), it is possible to use an external dtc. In this
>> case, we do not know which options are sup
Added check for OPAL_WRONG_STATE error code returned from OPAL.
Currently Linux flashes "unexpected error" over console for this
error. This will avoid throwing such message and return I/O error
for such OPAL failures.
Signed-off-by: Vipin K Parashar
---
Changes in v2:
- Added log message indica
Thanks!! for review.
Sending out v2 with suggested changes.
On Thursday 23 February 2017 09:22 AM, Stewart Smith wrote:
Michael Ellerman writes:
Stewart Smith writes:
Vipin K Parashar writes:
On Monday 13 February 2017 06:13 AM, Michael Ellerman wrote:
Vipin K Parashar writes:
OPA
On Tue, 28 Feb 2017 11:27:29 +0530
Mahesh Jagannath Salgaonkar wrote:
> On 02/28/2017 07:30 AM, Nicholas Piggin wrote:
> > A synchronous machine check is an exception raised by the attempt to
> > execute the current instruction. If the error can't be corrected, it
> > can make sense to SIGBUS the
37 matches
Mail list logo
