Performed an apt dist-upgrade and rebooted with agpmode=4 and still the GPU
is failing with errors. Should I proceed to place a bug report on this?
Herminio
On Tue, Sep 20, 2016 at 11:20 PM, Herminio Hernandez, Jr. <
herminio.hernande...@gmail.com> wrote:
> I am still getting errors even with ra
Hi Peter,
> > I updated to mainline as of today and tried CPU hotplug via the
> > ppc64_cpu tool:
>
> http://lkml.kernel.org/r/1475922278-3306-1-git-send-email-wanpeng...@hotmail.com
Thanks, this fixes the issue for me.
Anton
On Sat, 2016-10-08 at 22:16 +1100, Anton Blanchard wrote:
> Hi,
>
> Unfortunately sysrq-b seems to tie us up in knots, instead of
> rebooting
> the box. This is mainline from today.
Argh yeah reboot from interrupt context, what a PITA...
ppc_md.machine_shutdown is called which is supposed to be
Am 07.10.2016 um 21:26 schrieb Heiner Kallweit:
> Am 07.10.2016 um 07:51 schrieb Oliver O'Halloran:
>> Hi, Heiner
>>
>> Could you send me a copy of the kernel .config (or which defconfig)
>> that you're using, the name of the HW platform that you're using and
>> if possible the kernel image itself?
On Sat, Oct 08, 2016 at 10:07:33PM +1100, Anton Blanchard wrote:
> Hi,
>
> I updated to mainline as of today and tried CPU hotplug via the ppc64_cpu
> tool:
http://lkml.kernel.org/r/1475922278-3306-1-git-send-email-wanpeng...@hotmail.com
When the linux kernel is build with (typical kernel ship with Debian
installer):
CONFIG_FB_OF=y
CONFIG_VT_HW_CONSOLE_BINDING=y
CONFIG_FB_RADEON=m
The offb driver takes precedence over module radeonfb. It is then
impossible to load the module, error reported is:
[ 96.551486] radeonfb :00:10
Hi,
Unfortunately sysrq-b seems to tie us up in knots, instead of rebooting
the box. This is mainline from today.
Anton
--
Trying to free IRQ 17 from IRQ context!
[ cut here ]
WARNING: CPU: 32 PID: 0 at kernel/irq/manage.c:1460 __free_irq+0x298/0x380
Modules linked in: kv
Hi,
I updated to mainline as of today and tried CPU hotplug via the ppc64_cpu
tool:
# ppc64_cpu --smt=off
Segmentation fault
Looks like a NULL pointer in select_idle_sibling():
Unable to handle kernel paging request for data at address 0x0078
Faulting instruction address: 0xc0101520
Le 07/10/2016 à 22:58, Christophe JAILLET a écrit :
Size used with 'dma_alloc_coherent()' and 'dma_free_coherent()' should be
consistent.
Here, the size of a pointer is used in dma_alloc... and the size of the
pointed structure is used in dma_free...
This has been spotted with coccinelle, usin
