Re: Canyonlands oops at Shutdown

2016-10-24 Thread Julian Margetson

On 21-Oct-16 6:53 AM, Julian Margetson wrote:

On 08-May-16 10:12 AM, Julian Margetson wrote:

CONFIG_PPC44x_SIMPLE=y

CONFIG_POWER_RESET=y
CONFIG_POWER_RESET_GPIO is not set
# CONFIG_POWER_RESET_GPIO_RESTART is not set
# CONFIG_POWER_RESET_LTC2952 is not set
# CONFIG_POWER_RESET_RESTART is not set
# CONFIG_POWER_RESET_SYSCON is not set
# CONFIG_POWER_RESET_SYSCON_POWEROFF is not set

CONFIG_WATCHDOG=y
CONFIG_WATCHDOG_CORE=y
# CONFIG_WATCHDOG_NOWAYOUT is not set
# CONFIG_WATCHDOG_SYSFS is not set
#
# Watchdog Device Drivers
#
# CONFIG_SOFT_WATCHDOG is not set
# CONFIG_GPIO_WATCHDOG is not set
# CONFIG_XILINX_WATCHDOG is not set
# CONFIG_ZIIRAVE_WATCHDOG is not set
# CONFIG_CADENCE_WATCHDOG is not set
CONFIG_DW_WATCHDOG=y
# CONFIG_MAX63XX_WATCHDOG is not set
# CONFIG_ALIM7101_WDT is not set
# CONFIG_I6300ESB_WDT is not set
# CONFIG_BOOKE_WDT is not set
# CONFIG_MEN_A21_WDT is not set


Issue appears again with kernel 4.9-rc1




Working again with 4.9-rc2



Re: Canyonlands oops with m41t80

2016-10-24 Thread Julian Margetson

On 21-Oct-16 6:56 AM, Julian Margetson wrote:
Been having an oops since kernel 4.6 with m41t80 on Sam460ex 
canyonlands board .


Regards

Julian Margetson



Can't complete a bisect.

too many different issues up to to 4.6.0




Re: Canyonlands oops at Shutdown

2016-10-21 Thread Julian Margetson

On 08-May-16 10:12 AM, Julian Margetson wrote:

CONFIG_PPC44x_SIMPLE=y

CONFIG_POWER_RESET=y
CONFIG_POWER_RESET_GPIO is not set
# CONFIG_POWER_RESET_GPIO_RESTART is not set
# CONFIG_POWER_RESET_LTC2952 is not set
# CONFIG_POWER_RESET_RESTART is not set
# CONFIG_POWER_RESET_SYSCON is not set
# CONFIG_POWER_RESET_SYSCON_POWEROFF is not set

CONFIG_WATCHDOG=y
CONFIG_WATCHDOG_CORE=y
# CONFIG_WATCHDOG_NOWAYOUT is not set
# CONFIG_WATCHDOG_SYSFS is not set
#
# Watchdog Device Drivers
#
# CONFIG_SOFT_WATCHDOG is not set
# CONFIG_GPIO_WATCHDOG is not set
# CONFIG_XILINX_WATCHDOG is not set
# CONFIG_ZIIRAVE_WATCHDOG is not set
# CONFIG_CADENCE_WATCHDOG is not set
CONFIG_DW_WATCHDOG=y
# CONFIG_MAX63XX_WATCHDOG is not set
# CONFIG_ALIM7101_WDT is not set
# CONFIG_I6300ESB_WDT is not set
# CONFIG_BOOKE_WDT is not set
# CONFIG_MEN_A21_WDT is not set


Issue appears again with kernel 4.9-rc1



[  OK  ] Stopped Remount Root and Kernel File Systems.
[  OK  ] Reached target Shutdown.
[  101.580093] Unable to handle kernel paging request for data at address 
0xfe80
[  101.587599] Faulting instruction address: 0xc0420ea4
[  103.592744] Oops: Kernel access of bad area, sig: 11 [#4]
[  103.598153] PREEMPT [  103.600171] Canyonlands
[  103.602621] Modules linked in:
[  103.605697] CPU: 0 PID: 1 Comm: systemd-shutdow Tainted: G  D 
4.9.0-rc1-sam460ex-jm #9
[  103.614672] task: ea848000 task.stack: ea85
[  103.619213] NIP: c0420ea4 LR: c0420e88 CTR: c04d5928
[  103.624188] REGS: ea851b40 TRAP: 0300   Tainted: G  D  
(4.9.0-rc1-sam460ex-jm)
[  103.632463] MSR: 00029000 [  103.634999] <
CE[  103.636767] ,EE
,ME[  103.638798] >
[  103.640380]   CR: 28428228  XER: 
[  103.644394] DEAR: fe80 ESR:  [  103.648239] 
[  103.648239] GPR00: 
c0420e88 [  103.652618] ea851bf0 
ea848000 [  103.655691] ee831720 
00029000 [  103.658763] 0003 
ee851960 [  103.661837]  

GPR08: [  103.664910] 0001 
ee83d4b0 [  103.667983]  
ea851bc0 [  103.671064] 24428222 
2020de94 [  103.674146] 201e3e86 
bfb0bc0c [  103.677227] 
[  103.677227] GPR16: 
ea851d18 [  103.681611] 2090e018 
c0936b84 [  103.684693] bfb0bb10 
bfb0bb0c [  103.687775]  
 [  103.690856] 4321fedc 

GPR24: [  103.693943] 0003 
ee84c2a4 [  103.697028]  
fe68 [  103.700110] fe18 
 [  103.703192] ee83 
ea816000 [  103.706272] 
[  103.707778] NIP [c0420ea4] atombios_crtc_disable+0x40/0x2b0
[  103.713363] LR [c0420e88] atombios_crtc_disable+0x24/0x2b0
[  103.718863] Call Trace:
[  103.721319] [ea851bf0] [c0420e88] atombios_crtc_disable+0x24/0x2b0[  
103.727329]  (unreliable)
[  103.729966] 
[  103.731477] [ea851c40] [c03dc8bc] 
__drm_helper_disable_unused_functions+0x9c/0xd0[  103.738804] 
[  103.740310] [ea851c60] [c03dd230] drm_crtc_helper_set_config+0x1d4/0x8c4[  
103.746844] 
[  103.748366] [ea851cd0] [c0438254] radeon_crtc_set_config+0x50/0xf8[  
103.754378] 
[  103.755890] [ea851cf0] [c03f7fe4] drm_mode_set_config_internal+0x5c/0xe8[  
103.762425] 
[  103.763935] [ea851d10] [c03f80a0] drm_crtc_force_disable+0x30/0x38[  
103.769950] 
[  103.771461] [ea851d40] [c03f80f4] drm_crtc_force_disable_all+0x4c/0x70[  
103.777825] 
[  103.779336] [ea851d60] [c043a830] radeon_modeset_fini+0x78/0x90[  
103.785090] 
[  103.786601] [ea851d80] [c0417fb8] radeon_driver_unload_kms+0x5c/0x80[  
103.792789] 
[  103.794308] [ea851d90] [c03f3be8] drm_dev_unregister+0x4c/0xc8[  103.799977] 
[  103.801482] [ea851db0] [c03f3e34] drm_put_dev+0x64/0x7c[  103.806538] 
[  103.808049] [ea851dc0] [c0384b78] pci_device_shutdown+0x44/0x90[  
103.813805] 
[  103.815320] [ea851de0] [c059796c] device_shutdown+0x140/0x194[  103.820897] 
[  103.822414] [ea851e10] [c00421e0] kernel_halt+0x38/0x64[  103.827467] 
[  103.828975] [ea851e20] [c0042438] SyS_reboot+0x14c/0x1c8[  103.834117] 
[  103.835625] [ea851f40] [c000b108] ret_from_syscall+0x0/0x3c[  103.841026] 
[  103.842533] --- interrupt: c01 at 0x2000ffbc
[  103.842533] LR = 0x201cd878
[  103.849946] Instruction dump:[  103.852742] 
[  103.854241] 90010054 7c7f1b78 8123 83c90018 4bffdab1 813f0050 81290060 
2f89 
[  103.862136] 419e007c 83a90090 3b9dfe18 3b7dfe68 <813dfe80> 7d290034 5529d97e 
0f09 
[  103.870205] ---[ end trace 29b794af26305857 ]---
[  103.874834] 
[  104.878073] systemd-shutdow: 3 output lines suppressed due to ratelimiting
[  104.885163] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x000b
[  104.885163] 
[  104.894339] Rebooting in 180 seconds..

Canyonlands oops with m41t80

2016-10-21 Thread Julian Margetson
Been having an oops since kernel 4.6 with m41t80 on Sam460ex canyonlands 
board .


Regards

Julian Margetson


[7.543123] usbserial: USB Serial support registered for generic
[7.567065] mousedev: PS/2 mouse device common for all mice
[7.590510] i2c /dev entries driver
[7.614508] Unable to handle kernel paging request for data at address 
0x01d0
[7.639373] Faulting instruction address: 0xc08ba94c
[7.661608] Vector: 300 (Data Access) at [eea5dd90]
[7.683715] pc: [7.685849] c08ba94c
: mutex_lock+0x0/0x1c[7.706994] 
[7.725338] lr: [7.727471] c0688b4c
: m41t80_handle_irq+0x28/0xac[7.749219] 
[7.767544] sp: eea5de40
[7.787383]msr: 29000
[7.806717]dar: 1d0
[7.825712]  dsisr: 0
[7.844303]   current = 0xea84e3e0
[7.863944] pid   = 1465, comm = irq/47-m41t80
[7.884997] Linux version 4.9.0-rc1-sam460ex-jm (root@julian-VirtualBox) 
(gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1) ) #9 PREEMPT Fri 
Oct 21 06:43:46 AST 2016
[7.917973] enter ? for help
[7.938176] [link register   ] [7.941319] c0688b4c
 m41t80_handle_irq+0x28/0xac[7.963398] 
[7.982212] [eea5de40] [7.984622] 00021000
[8.004140]  (unreliable)
[8.024015] [eea5de60] [8.026427] c0056ca0
 irq_thread_fn+0x2c/0x48[8.047988] 
[8.066460] [eea5de80] [8.068875] c0056ec0
 irq_thread+0xc4/0x160[8.089976] 
[8.108261] [eea5ded0] [8.110672] c003fac8
 kthread+0xc8/0xcc[8.131354] 
[8.149544] [eea5df40] [8.151957] c000b260
 ret_from_kernel_thread+0x5c/0x64[8.173812] 
[8.191782] mon> [8.193648]  
[   10.213011] sched: RT throttling activated
[   10.213073] Oops: Kernel access of bad area, sig: 11 [#1]
[   10.255754] PREEMPT [   10.257888] Canyonlands
[   10.276581] Modules linked in:
[   10.295337] CPU: 0 PID: 1465 Comm: irq/47-m41t80 Not tainted 
4.9.0-rc1-sam460ex-jm #9
[   10.318703] task: ea84e3e0 task.stack: eea5c000
[   10.338718] NIP: c08ba94c LR: c0688b4c CTR: c0688b24
[   10.359090] REGS: eea5dd90 TRAP: 0300   Not tainted  (4.9.0-rc1-sam460ex-jm)
[   10.381770] MSR: 00029000 [   10.384453] <
CE[   10.401623] ,EE
,ME[   10.419172] >
[   10.436057]   CR: 44000222  XER: 2000
[   10.455412] DEAR: 01d0 ESR:  [   10.459473] 
[   10.459473] GPR00: 
c0056ca0 [   10.494122] eea5de40 
ea84e3e0 [   10.512256] 01d0 
eea30c00 [   10.530251]  
 [   10.548124] ea84e70c 

GPR08: [   10.580531] c0f2cab4 
c0688b24 [   10.598288] 0001 
eea5de80 [   10.615919] 24082284 
 [   10.633376] c003fa00 
eea239e0 [   10.650632] 
[   10.650632] GPR16: 
 [   10.682881]  
 [   10.699869]  
 [   10.716622] c0de 
0001 [   10.733350] ee941954 

GPR24: [   10.763363] eea25a24 
 [   10.779747] ee94195c 
eea25a00 [   10.796031] eea239b0 
ee941900 [   10.812178] eea30c00 
01d0 [   10.828080] 
[   10.842085] NIP [c08ba94c] mutex_lock+0x0/0x1c
[   10.859199] LR [c0688b4c] m41t80_handle_irq+0x28/0xac
[   10.876956] Call Trace:
[   10.892001] [eea5de40] [00021000] 0x21000[   10.896062]  (unreliable)
[   10.911374] 
[   10.925550] [eea5de60] [c0056ca0] irq_thread_fn+0x2c/0x48[   10.931078] 
[   10.945355] [eea5de80] [c0056ec0] irq_thread+0xc4/0x160[   10.950694] 
[   10.965061] [eea5ded0] [c003fac8] kthread+0xc8/0xcc[   10.970033] 
[   10.984550] [eea5df40] [c000b260] ret_from_kernel_thread+0x5c/0x64[   
10.990903] 
[   11.005622] Instruction dump:[   11.008581] 
[   11.023528] 812a0008 2f89 409e0014 812a0010 712a0004 41820008 4bffeb79 
bb410018 
[   11.045441] 80010034 38210030 7c0803a6 4e800020 <7d201828> 3129 7d20192d 
40a2fff4 
[   11.067118] ---[ end trace 29b794af26305853 ]---
[   11.084724] 
[   11.099101] Unable to handle kernel paging request for data at address 
0xffe0
[   11.119804] Faulting instruction address: 0xc00402dc
[   11.137946] Vector: 300 (Data Access) at [eea5dc30]
[   11.156029] pc: [   11.158165] c00402dc
: kthread_data+0x4/0xc[   11.175504] 
[   11.190034] lr: [   11.192167] c0056d94
: irq_thread_dtor+0x48/0xb0[   11.209930] 
[   11.224446] sp: eea5dce0
[   11.240384]msr: 29000
[   11.255894]dar: ffe0
[   11.271521]  dsisr: 0
[   11.286356]   current = 0xea84e3e0
[   11.302265] pid   = 1465, comm = irq/47-m41t80
[   11.319626] Linux version 4.9.0-rc1-sam460ex-jm (root@julian-VirtualBox) 
(gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1) ) #9 PREEMPT Fri 
Oct 21 06:43:46 AST 2016
[   11.348882] enter ? for help
[   11.365247] mon> [   11.367112]  
[   13.383432] Oops: Kernel access of bad area, sig: 11 [#2]
[   13.402318] PREEMPT [   13.404450] Canyonlands
[   13.420088] Modules linked in:
[   13.436358] CPU: 0 PID: 1465 Comm: irq/47-m41t80 Tainted: G  D 
4.9.0-rc1-sam460ex-jm #9
[   13.458960] task: ea84e3e0 task.stack: eea5c000
[   13.476842] NIP: c00402dc LR: c0056d94 CTR: c0056d4c
[   13.495196] R

Re: Problem booting Kernel 4.8-rc1 on Sam460ex ( Canyonlands)

2016-08-14 Thread Julian Margetson

On 8/8/2016 4:19 PM, Rob Herring wrote:

On Mon, Aug 8, 2016 at 2:25 PM, Julian Margetson <runa...@candw.ms> wrote:

On 8/8/2016 9:39 AM, Kefeng Wang wrote:

+cc Rob

On 2016/8/8 20:51, Julian Margetson wrote:

On 8/8/2016 8:22 AM, Kefeng Wang wrote:

On 2016/8/8 19:52, Julian Margetson wrote:

Problem booting Kernel 4.8-rc1 on Sam460ex ( Canyonlands) machine .

This is what I get with the bisect.

Hi Julian

I have no Sam460ex machine, could you show the good and bad kernel
bootlog?

I have no experience about PowerPC, the status shows below,
version boot
v4.7ok
v4.8-rc1fail
v4.7 + this patch   fail(right?)

Does PowerPC support earlyprintk/earlycon? Please set it, and let's show
somethings from earlyprintk.

Not getting any output with earlyprintk so not sure if it works or if my
settings are incorrect .

This should work: earlycon=uart8250,mmio,ef600300,115200n8

Adding "initcall_debug debug" would also be useful here.


I tried to revert the commit but the result is the same so I suspect that
this one may not really be the problem .
Looks like the real problem may be something affecting the the device tree
loading .

That's strange. If it is this commit, the init order changes as it
changed from device to arch initcall. I haven't seen any other
platforms having problems.

Rob



The following patch fixes my issue.

http://linuxppc.10917.n7.nabble.com/PATCH-powerpc-populate-the-default-bus-with-machine-arch-initcall-td112132.html

Thank you

Regards

Julian





Re: Problem booting Kernel 4.8-rc1 on Sam460ex ( Canyonlands)

2016-08-08 Thread Julian Margetson

On 8/8/2016 8:22 AM, Kefeng Wang wrote:

On 2016/8/8 19:52, Julian Margetson wrote:

Problem booting Kernel 4.8-rc1 on Sam460ex ( Canyonlands) machine .

This is what I get with the bisect.

Hi Julian

I have no Sam460ex machine, could you show the good and bad kernel bootlog?

Thanks,
Kefeng


Regards

Julian


44a7185c2ae6383c88ff5b1ef2e2969f35d7b8b7 is the first bad commit
commit 44a7185c2ae6383c88ff5b1ef2e2969f35d7b8b7
Author: Kefeng Wang <wangkefeng.w...@huawei.com>
Date:   Wed Jun 1 14:52:54 2016 +0800

 of/platform: Add common method to populate default bus

 The arch code calls of_platform_populate() with default match table
 when it wants to populate default bus.

 This patch introduce a new of_platform_default_populate_init() and make it
 arch_initcall_sync(it should be later than some iommu configration, eg,
 of_iommu_init() and swiotlb_late_init in arm64), then we can finish above
 job in common method.

 In order to avoid the default bus being populated twice, simply checking
 the flag of bus node whether has be set OF_POPULATED_BUS or not.

 After that, we can safely remove the caller in arch code.

 Btw, add debug print in of_platform_populate(), and use __func__ to
 print function's name of of_platform_bus_create().

 Cc: Rob Herring <robh...@kernel.org>
 Cc: Frank Rowand <frowand.l...@gmail.com>
 Cc: Grant Likely <grant.lik...@linaro.org>
 Signed-off-by: Kefeng Wang <wangkefeng.w...@huawei.com>
 Signed-off-by: Rob Herring <r...@kernel.org>

:04 04 2d2438c33110bd5d0cba9540357c7e81f74485dd 
3ad033aad77298c3a6f50ed4c651d7336825d700 Mdrivers
root@julian-VirtualBox:/usr/src/linux-test#


git bisect log
git bisect start
# good: [523d939ef98fd712632d93a5a2b588e477a7565e] Linux 4.7
git bisect good 523d939ef98fd712632d93a5a2b588e477a7565e
# bad: [29b4817d4018df78086157ea3a55c1d9424a7cfc] Linux 4.8-rc1
git bisect bad 29b4817d4018df78086157ea3a55c1d9424a7cfc
# good: [1c88e19b0f6a8471ee50d5062721ba30b8fd4ba9] Merge branch 'akpm' (patches 
from Andrew)
git bisect good 1c88e19b0f6a8471ee50d5062721ba30b8fd4ba9
# bad: [77a87824ed676ca8ff8482e4157d3adb284fd381] clocksource/drivers/clps_711x: 
fixup for "ARM: clps711x:
git bisect bad 77a87824ed676ca8ff8482e4157d3adb284fd381
# bad: [c9b95e5961c0294e0efffeaa847c1a1e6369204c] Merge tag 'sound-4.8-rc1' of 
git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound
git bisect bad c9b95e5961c0294e0efffeaa847c1a1e6369204c
# good: [1056c9bd2702ea1bb79abf9bd1e78c578589d247] Merge tag 
'clk-for-linus-4.8' of git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux
git bisect good 1056c9bd2702ea1bb79abf9bd1e78c578589d247
# bad: [bad60e6f259a01cf9f29a1ef8d435ab6c60b2de9] Merge tag 'powerpc-4.8-1' of 
git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux
git bisect bad bad60e6f259a01cf9f29a1ef8d435ab6c60b2de9
# bad: [bad60e6f259a01cf9f29a1ef8d435ab6c60b2de9] Merge tag 'powerpc-4.8-1' of 
git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux
git bisect bad bad60e6f259a01cf9f29a1ef8d435ab6c60b2de9
# good: [f7b9ebb79e90b19bf6a2cb805a536258437fc3fa] powerpc: Re-order 
setup_panic()
git bisect good f7b9ebb79e90b19bf6a2cb805a536258437fc3fa
# good: [f7b9ebb79e90b19bf6a2cb805a536258437fc3fa] powerpc: Re-order 
setup_panic()
git bisect good f7b9ebb79e90b19bf6a2cb805a536258437fc3fa
# good: [944171cbf499d3445c749f7c13c46de0a564a905] pNFS: Actively set 
attributes as invalid if LAYOUTCOMMIT is outstanding
git bisect good 944171cbf499d3445c749f7c13c46de0a564a905
# bad: [b325e04ea21081439f0f3e7fe1117e883a9031d8] Merge branch 
'x86-cpu-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
git bisect bad b325e04ea21081439f0f3e7fe1117e883a9031d8
# bad: [b325e04ea21081439f0f3e7fe1117e883a9031d8] Merge branch 
'x86-cpu-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
git bisect bad b325e04ea21081439f0f3e7fe1117e883a9031d8
# bad: [0e13f99d3a4816a3996a69721388b4cf1a982cf8] Documentation: dt: i2c: use 
correct STMicroelectronics vendor prefix
git bisect bad 0e13f99d3a4816a3996a69721388b4cf1a982cf8
# bad: [1a1d2f9968660e016883b21c499158c08d9c87bf] mips: use 
of_platform_default_populate() to populate default bus
git bisect bad 1a1d2f9968660e016883b21c499158c08d9c87bf
# bad: [db41252cf8b58c8a57226204e113b9dffaebf693] cris: Remove unnecessary 
of_platform_populate with default match table
git bisect bad db41252cf8b58c8a57226204e113b9dffaebf693
# bad: [61c78644e7f1bd9445b3d7ddc3d35989a38985ee] arc: Remove unnecessary 
of_platform_populate with default match table
git bisect bad 61c78644e7f1bd9445b3d7ddc3d35989a38985ee
# bad: [44a7185c2ae6383c88ff5b1ef2e2969f35d7b8b7] of/platform: Add common 
method to populate default bus
git bisect bad 44a7185c2ae6383c88ff5b1ef2e2969f35d7b8b7
# good: [bb8e15d60462a84a25a3bf33e8bc29b46c6d470a] of: iommu: make 
of_iommu_init() postcore_initcall_sync
git bisect good bb8e15d60462a84a25

Problem booting Kernel 4.8-rc1 on Sam460ex ( Canyonlands)

2016-08-08 Thread Julian Margetson

Problem booting Kernel 4.8-rc1 on Sam460ex ( Canyonlands) machine .

This is what I get with the bisect.

Regards

Julian


44a7185c2ae6383c88ff5b1ef2e2969f35d7b8b7 is the first bad commit
commit 44a7185c2ae6383c88ff5b1ef2e2969f35d7b8b7
Author: Kefeng Wang 
Date:   Wed Jun 1 14:52:54 2016 +0800

of/platform: Add common method to populate default bus

The arch code calls of_platform_populate() with default match table
when it wants to populate default bus.

This patch introduce a new of_platform_default_populate_init() and 
make it

arch_initcall_sync(it should be later than some iommu configration, eg,
of_iommu_init() and swiotlb_late_init in arm64), then we can finish 
above

job in common method.

In order to avoid the default bus being populated twice, simply 
checking

the flag of bus node whether has be set OF_POPULATED_BUS or not.

After that, we can safely remove the caller in arch code.

Btw, add debug print in of_platform_populate(), and use __func__ to
print function's name of of_platform_bus_create().

Cc: Rob Herring 
Cc: Frank Rowand 
Cc: Grant Likely 
Signed-off-by: Kefeng Wang 
Signed-off-by: Rob Herring 

:04 04 2d2438c33110bd5d0cba9540357c7e81f74485dd 
3ad033aad77298c3a6f50ed4c651d7336825d700 Mdrivers

root@julian-VirtualBox:/usr/src/linux-test#


git bisect log
git bisect start
# good: [523d939ef98fd712632d93a5a2b588e477a7565e] Linux 4.7
git bisect good 523d939ef98fd712632d93a5a2b588e477a7565e
# bad: [29b4817d4018df78086157ea3a55c1d9424a7cfc] Linux 4.8-rc1
git bisect bad 29b4817d4018df78086157ea3a55c1d9424a7cfc
# good: [1c88e19b0f6a8471ee50d5062721ba30b8fd4ba9] Merge branch 'akpm' 
(patches from Andrew)

git bisect good 1c88e19b0f6a8471ee50d5062721ba30b8fd4ba9
# bad: [77a87824ed676ca8ff8482e4157d3adb284fd381] 
clocksource/drivers/clps_711x: fixup for "ARM: clps711x:

git bisect bad 77a87824ed676ca8ff8482e4157d3adb284fd381
# bad: [c9b95e5961c0294e0efffeaa847c1a1e6369204c] Merge tag 
'sound-4.8-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound

git bisect bad c9b95e5961c0294e0efffeaa847c1a1e6369204c
# good: [1056c9bd2702ea1bb79abf9bd1e78c578589d247] Merge tag 
'clk-for-linus-4.8' of 
git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux

git bisect good 1056c9bd2702ea1bb79abf9bd1e78c578589d247
# bad: [bad60e6f259a01cf9f29a1ef8d435ab6c60b2de9] Merge tag 
'powerpc-4.8-1' of 
git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux

git bisect bad bad60e6f259a01cf9f29a1ef8d435ab6c60b2de9
# bad: [bad60e6f259a01cf9f29a1ef8d435ab6c60b2de9] Merge tag 
'powerpc-4.8-1' of 
git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux

git bisect bad bad60e6f259a01cf9f29a1ef8d435ab6c60b2de9
# good: [f7b9ebb79e90b19bf6a2cb805a536258437fc3fa] powerpc: Re-order 
setup_panic()

git bisect good f7b9ebb79e90b19bf6a2cb805a536258437fc3fa
# good: [f7b9ebb79e90b19bf6a2cb805a536258437fc3fa] powerpc: Re-order 
setup_panic()

git bisect good f7b9ebb79e90b19bf6a2cb805a536258437fc3fa
# good: [944171cbf499d3445c749f7c13c46de0a564a905] pNFS: Actively set 
attributes as invalid if LAYOUTCOMMIT is outstanding

git bisect good 944171cbf499d3445c749f7c13c46de0a564a905
# bad: [b325e04ea21081439f0f3e7fe1117e883a9031d8] Merge branch 
'x86-cpu-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip

git bisect bad b325e04ea21081439f0f3e7fe1117e883a9031d8
# bad: [b325e04ea21081439f0f3e7fe1117e883a9031d8] Merge branch 
'x86-cpu-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip

git bisect bad b325e04ea21081439f0f3e7fe1117e883a9031d8
# bad: [0e13f99d3a4816a3996a69721388b4cf1a982cf8] Documentation: dt: 
i2c: use correct STMicroelectronics vendor prefix

git bisect bad 0e13f99d3a4816a3996a69721388b4cf1a982cf8
# bad: [1a1d2f9968660e016883b21c499158c08d9c87bf] mips: use 
of_platform_default_populate() to populate default bus

git bisect bad 1a1d2f9968660e016883b21c499158c08d9c87bf
# bad: [db41252cf8b58c8a57226204e113b9dffaebf693] cris: Remove 
unnecessary of_platform_populate with default match table

git bisect bad db41252cf8b58c8a57226204e113b9dffaebf693
# bad: [61c78644e7f1bd9445b3d7ddc3d35989a38985ee] arc: Remove 
unnecessary of_platform_populate with default match table

git bisect bad 61c78644e7f1bd9445b3d7ddc3d35989a38985ee
# bad: [44a7185c2ae6383c88ff5b1ef2e2969f35d7b8b7] of/platform: Add 
common method to populate default bus

git bisect bad 44a7185c2ae6383c88ff5b1ef2e2969f35d7b8b7
# good: [bb8e15d60462a84a25a3bf33e8bc29b46c6d470a] of: iommu: make 
of_iommu_init() postcore_initcall_sync

git bisect good bb8e15d60462a84a25a3bf33e8bc29b46c6d470a
# first bad commit: [44a7185c2ae6383c88ff5b1ef2e2969f35d7b8b7] 
of/platform: Add common method to populate default bus






Re: Problems with Kernels 3.17-rc1 and onwards on Acube Sam460 AMCC 460ex board

2016-08-05 Thread Julian Margetson

On 2/18/2015 10:56 PM, Michael Ellerman wrote:

On Wed, 2015-02-18 at 21:36 -0400, Julian Margetson wrote:

On 2/18/2015 8:13 PM, Michael Ellerman wrote:


On Wed, 2015-02-18 at 15:45 -0400, Julian Margetson wrote:

On 2/15/2015 8:18 PM, Michael Ellerman wrote:


On Sun, 2015-02-15 at 08:16 -0400, Julian Margetson wrote:

Hi

I am unable to get any kernel beyond  the 3.16 branch working on an
Acube Sam460ex
  AMCC 460ex based motherboard. Kernel  up 3.16.7-ckt6 working.

Does reverting b0345bbc6d09 change anything?


[6.364350] snd_hda_intel 0001:81:00.1: enabling device ( -> 0002)
[6.453794] snd_hda_intel 0001:81:00.1: ppc4xx_setup_msi_irqs: fail mapping 
irq
[6.487530] Unable to handle kernel paging request for data at address 
0x0fa06c7c
[6.495055] Faulting instruction address: 0xc032202c
[6.500033] Vector: 300 (Data Access) at [efa31cf0]
[6.504922] pc: c032202c: __reg_op+0xe8/0x100
[6.509697] lr: c0014f88: msi_bitmap_free_hwirqs+0x50/0x94
[6.515600] sp: efa31da0
[6.518491]msr: 21000
[6.521112]dar: fa06c7c
[6.523915]  dsisr: 0
[6.526190]   current = 0xef8bab00
[6.529603] pid   = 115, comm = kworker/0:1
[6.534163] enter ? for help
[6.537054] [link register   ] c0014f88 msi_bitmap_free_hwirqs+0x50/0x94
[6.543811] [efa31da0] c0014f78 msi_bitmap_free_hwirqs+0x40/0x94 (unreliable)
[6.551001] [efa31dc0] c001aee8 ppc4xx_setup_msi_irqs+0xac/0xf4
[6.556973] [efa31e00] c03503a4 pci_enable_msi_range+0x1e0/0x280
[6.563032] [efa31e40] f92c2f74 azx_probe_work+0xe0/0x57c [snd_hda_intel]
[6.569906] [efa31e80] c0036344 process_one_work+0x1e8/0x2f0
[6.575627] [efa31eb0] c003677c worker_thread+0x2f4/0x438
[6.581079] [efa31ef0] c003a3e4 kthread+0xc8/0xcc
[6.585844] [efa31f40] c000aec4 ret_from_kernel_thread+0x5c/0x64
[6.591910] mon>  

Managed to do a third git bisect  with the following results .

Great work.


git bisect bad
9279d3286e10736766edcaf815ae10e00856e448 is the first bad commit
commit 9279d3286e10736766edcaf815ae10e00856e448
Author: Rasmus Villemoes <li...@rasmusvillemoes.dk>
Date:   Wed Aug 6 16:10:16 2014 -0700

 lib: bitmap: change parameter of bitmap_*_region to unsigned

So the bug is in the 4xx MSI code, and has always been there, in fact I don't
see how that code has *ever* worked. The commit you bisected to just caused the
existing bug to cause an oops.

Can you try this?

diff --git a/arch/powerpc/sysdev/ppc4xx_msi.c b/arch/powerpc/sysdev/ppc4xx_msi.c
index 6e2e6aa378bb..effb5b878a78 100644
--- a/arch/powerpc/sysdev/ppc4xx_msi.c
+++ b/arch/powerpc/sysdev/ppc4xx_msi.c
@@ -95,11 +95,9 @@ static int ppc4xx_setup_msi_irqs(struct pci_dev *dev, int 
nvec, int type)
  
  	list_for_each_entry(entry, >msi_list, list) {

int_no = msi_bitmap_alloc_hwirqs(_data->bitmap, 1);
-   if (int_no >= 0)
-   break;
if (int_no < 0) {
-   pr_debug("%s: fail allocating msi interrupt\n",
-   __func__);
+   pr_warn("%s: fail allocating msi interrupt\n", 
__func__);
+   return -ENOSPC;
}
virq = irq_of_parse_and_map(msi_data->msi_dev, int_no);
if (virq == NO_IRQ) {


Thanks.
This works with 3.17-rc1. Will try with the 3.18 Branch .

OK great.


Any ideas why drm is not  working ? (It never worked) .

No sorry. You might have more luck if you post a new thread to the dri list.


[5.809802] Linux agpgart interface v0.103
[6.137893] [drm] Initialized drm 1.1.0 20060810
[6.439872] snd_hda_intel 0001:81:00.1: enabling device ( -> 0002)
[6.508544] ppc4xx_setup_msi_irqs: fail allocating msi interrupt

I'm curious why it's failing to allocate MSIs. Possibly it's just run out.

Can you post the output of 'cat /proc/interrupts'?

cheers





Hi Michael

Any chance of this fix being added to the mainline ?


Regards

Julian




Re: Kernel 4.7: PAGE_GUARDED and _PAGE_NO_CACHE

2016-06-06 Thread Julian Margetson

On 6/5/2016 10:00 PM, Michael Ellerman wrote:

On Sun, 2016-06-05 at 21:23 -0400, Julian Margetson wrote:

drivers/gpu/drm/drm_vm.c: In function ‘drm_dma_prot’:
drivers/gpu/drm/drm_vm.c:83:6: error: invalid operands to binary |
(have ‘pgprot_t {aka struct }’ and ‘int’)
 tmp |= _PAGE_NO_CACHE;
 ^


That is because that usage is wrong based on type. _PAGE_NO_CACHE is not
of type pgprot_t. What you really need there is

tmp = __pgprot(pgprot_val(tmp) | _PAGE_NO_CACHE);

or a better option would be

tmp = pgprot_noncached_wc(tmp);

-aneesh

tmp = pgprot_noncached_wc(tmp);

compiles but  I then run in to the following

   CC  drivers/gpu/drm/drm_scatter.o
drivers/gpu/drm/drm_scatter.c: In function ‘drm_vmalloc_dma’:
drivers/gpu/drm/drm_scatter.c:44:49: error: invalid operands to binary |
(have ‘pgprot_t {aka struct }’ and ‘int’)
return __vmalloc(size, GFP_KERNEL, PAGE_KERNEL | _PAGE_NO_CACHE);
   ^
drivers/gpu/drm/drm_scatter.c:48:1: warning: control reaches end of
non-void function [-Wreturn-type]
   }
   ^

Aneesh showed you how to fix that in his reply above.

 return __vmalloc(size, GFP_KERNEL, pgprot_noncached_wc(PAGE_KERNEL));

cheers




Thanks .

With the two adjustment

tmp = pgprot_noncached_wc(tmp);

and

return __vmalloc(size, GFP_KERNEL, pgprot_noncached_wc(PAGE_KERNEL));

The rc2 builds and boots  on Sam460ex

Regards

Julian


___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev

Re: Kernel 4.7: PAGE_GUARDED and _PAGE_NO_CACHE

2016-06-05 Thread Julian Margetson

On 6/5/2016 8:57 PM, Michael Ellerman wrote:

On Sun, 2016-06-05 at 18:09 +0200, Christian Zigotzky wrote:


All,

I need an answer because I think Darren's guess is correct. It isn't a
problem in the pci code. I replaced the file head_64.S that Darren
mentioned with the one from the kernel 4.6 and it compiled but
unfortunately it doesn't boot. We know "head_64.S" is one file for the
early boot phase but I think there are some other files.

There's lots of files used in the early boot, you can't revert individual files
and expect it to work.


On 28 May 2016 at 8:51 PM, Darren Stevens wrote:

You can see from this that the 4.7 kernel hangs right after the booting linux
via __start(), whereas in the 4.4 there's about 29 lines of output before it
gets to the Initialised io_base_virt printk in our patch.

If the last thing you see is "booting linux via __start()" that means the kernel
crashed early, before it could detect and initialise the console.

Do you have a serial or other console in that machine at a known location? If so
you can hard-code the kernel to use that console, which means you can get
messages earlier in boot. See udbg_early_init() for starters.

cheers



Julian Margetson <runa...@candw.ms> writes:


Hi Christian,

I am also having a problem with _PAGE_NO_CACHE on Sam460ex.

Regards
Julian

drivers/gpu/drm/drm_vm.c: In function ‘drm_dma_prot’:
drivers/gpu/drm/drm_vm.c:83:6: error: invalid operands to binary | 
(have ‘pgprot_t {aka struct }’ and ‘int’)

tmp |= _PAGE_NO_CACHE;
^
scripts/Makefile.build:289: recipe for target 
'drivers/gpu/drm/drm_vm.o' failed

make[3]: *** [drivers/gpu/drm/drm_vm.o] Error 1
scripts/Makefile.build:440: recipe for target 'drivers/gpu/drm' failed
make[2]: *** [drivers/gpu/drm] Error 2
scripts/Makefile.build:440: recipe for target 'drivers/gpu' failed
make[1]: *** [drivers/gpu] Error 2
Makefile:985: recipe for target 'drivers' failed
make: *** [drivers] Error 2



That is because that usage is wrong based on type. _PAGE_NO_CACHE is not
of type pgprot_t. What you really need there is

tmp = __pgprot(pgprot_val(tmp) | _PAGE_NO_CACHE);

or a better option would be

tmp = pgprot_noncached_wc(tmp);

-aneesh

@Julian

What about the issues with the Sam460ex? Have you solved the problem 
with the commit powerpc-4.7-1?


Cheers,

Christian

On 04 June 2016 at 5:25 PM, Christian Zigotzky wrote:



tmp = pgprot_noncached_wc(tmp);

compiles but  I then run in to the following

 CC  drivers/gpu/drm/drm_scatter.o
drivers/gpu/drm/drm_scatter.c: In function ‘drm_vmalloc_dma’:
drivers/gpu/drm/drm_scatter.c:44:49: error: invalid operands to binary | 
(have ‘pgprot_t {aka struct }’ and ‘int’)

  return __vmalloc(size, GFP_KERNEL, PAGE_KERNEL | _PAGE_NO_CACHE);
 ^
drivers/gpu/drm/drm_scatter.c:48:1: warning: control reaches end of 
non-void function [-Wreturn-type]

 }
 ^
scripts/Makefile.build:289: recipe for target 
'drivers/gpu/drm/drm_scatter.o' failed

make[3]: *** [drivers/gpu/drm/drm_scatter.o] Error 1
scripts/Makefile.build:440: recipe for target 'drivers/gpu/drm' failed
make[2]: *** [drivers/gpu/drm] Error 2
scripts/Makefile.build:440: recipe for target 'drivers/gpu' failed
make[1]: *** [drivers/gpu] Error 2
Makefile:985: recipe for target 'drivers' failed
make: *** [drivers] Error 2

Regards

Julian


___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev

Re: Canyonlands oops at Shutdown

2016-05-08 Thread Julian Margetson

On 5/6/2016 8:41 AM, Julian Margetson wrote:
Getting the following at shutdown with Kernel 4.6-rc's on Sam460ex 
Canyonlands board .


Regards
Julian


[ 1533.722779] Unable to handle kernel paging request for data at 
address 0x0128

[ 1533.744309] Faulting instruction address: 0xc026d3c8
[ 1535.763583] Oops: Kernel access of bad area, sig: 11 [#1]
[ 1535.782886] PREEMPT Canyonlands
[ 1535.799805] Modules linked in:
[ 1535.816546] CPU: 0 PID: 1 Comm: systemd-shutdow Not tainted 
4.6.0-rc6-sam460ex-jm #4

[ 1535.838341] task: ea85 ti: ea846000 task.ti: ea846000
[ 1535.857783] NIP: c026d3c8 LR: c0466984 CTR: c001a8ac
[ 1535.876847] REGS: ea847d10 TRAP: 0300   Not tainted 
(4.6.0-rc6-sam460ex-jm)

[ 1535.898224] MSR: 00029000 <CE,EE,ME>  CR: 44422284  XER: 
[ 1535.918868] DEAR: 0128 ESR: 
GPR00: c0466984 ea847dc0 ea85 0108 000f fff0  
0007
GPR08: 0001 c0b5a19c  ea847de0 28428468 205cfe94 205a946e 
bfff8a7c
GPR16: 2097d008 2097d018 2097d090 bfff8980 bfff897c   
4321fedc
GPR24: 2097d578 c0b3f17c c0b8  c0a95e68 eaa35000 c0b8545c 
0108

[ 1536.024665] NIP [c026d3c8] kobject_get+0x18/0x80
[ 1536.044003] LR [c0466984] get_device+0x1c/0x38
[ 1536.063198] Call Trace:
[ 1536.080424] [ea847dc0] [eaa3fa10] 0xeaa3fa10 (unreliable)
[ 1536.100896] [ea847dd0] [c0466984] get_device+0x1c/0x38
[ 1536.121059] [ea847de0] [c04689f4] device_shutdown+0x58/0x178
[ 1536.141727] [ea847e10] [c003c280] kernel_halt+0x38/0x64
[ 1536.161875] [ea847e20] [c003c4cc] SyS_reboot+0x140/0x1b0
[ 1536.182057] [ea847f40] [c000ad80] ret_from_syscall+0x0/0x3c
[ 1536.202568] --- interrupt: c01 at 0x203d1fbc
[ 1536.202568] LR = 0x2058f878
[ 1536.239761] Instruction dump:
[ 1536.257358] 4b9c 7fa3eb78 484cad91 39610020 7fe3fb78 4bda3d74 
9421fff0 7c0802a6
[ 1536.280308] 93e1000c 7c7f1b79 90010014 41820060 <813f0020> 2f89 
41bc001c 809f

[ 1536.303611] ---[ end trace f5a63492b41c62f2 ]---
[ 1536.323546]
[ 1537.340293] note: systemd-shutdow[1] exited with preempt_count 1
[ 1537.363602] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x000b

[ 1537.363602]
[ 1537.404665] Rebooting in 180 seconds..


Adjusted my .config and it is working now .

Regards

Julian


CONFIG_PPC44x_SIMPLE=y

CONFIG_POWER_RESET=y
CONFIG_POWER_RESET_GPIO is not set
# CONFIG_POWER_RESET_GPIO_RESTART is not set
# CONFIG_POWER_RESET_LTC2952 is not set
# CONFIG_POWER_RESET_RESTART is not set
# CONFIG_POWER_RESET_SYSCON is not set
# CONFIG_POWER_RESET_SYSCON_POWEROFF is not set

CONFIG_WATCHDOG=y
CONFIG_WATCHDOG_CORE=y
# CONFIG_WATCHDOG_NOWAYOUT is not set
# CONFIG_WATCHDOG_SYSFS is not set
#
# Watchdog Device Drivers
#
# CONFIG_SOFT_WATCHDOG is not set
# CONFIG_GPIO_WATCHDOG is not set
# CONFIG_XILINX_WATCHDOG is not set
# CONFIG_ZIIRAVE_WATCHDOG is not set
# CONFIG_CADENCE_WATCHDOG is not set
CONFIG_DW_WATCHDOG=y
# CONFIG_MAX63XX_WATCHDOG is not set
# CONFIG_ALIM7101_WDT is not set
# CONFIG_I6300ESB_WDT is not set
# CONFIG_BOOKE_WDT is not set
# CONFIG_MEN_A21_WDT is not set
#
# PCI-based Watchdog Cards
#
# CONFIG_PCIPCWATCHDOG is not set
# CONFIG_WDTPCI is not set
#
# USB-based Watchdog Cards
#
# CONFIG_USBPCWATCHDOG is not set

___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev

Canyonlands oops at Shutdown

2016-05-06 Thread Julian Margetson
Getting the following at shutdown with Kernel 4.6-rc's on Sam460ex 
Canyonlands board .


Regards
Julian


[ 1533.722779] Unable to handle kernel paging request for data at 
address 0x0128

[ 1533.744309] Faulting instruction address: 0xc026d3c8
[ 1535.763583] Oops: Kernel access of bad area, sig: 11 [#1]
[ 1535.782886] PREEMPT Canyonlands
[ 1535.799805] Modules linked in:
[ 1535.816546] CPU: 0 PID: 1 Comm: systemd-shutdow Not tainted 
4.6.0-rc6-sam460ex-jm #4

[ 1535.838341] task: ea85 ti: ea846000 task.ti: ea846000
[ 1535.857783] NIP: c026d3c8 LR: c0466984 CTR: c001a8ac
[ 1535.876847] REGS: ea847d10 TRAP: 0300   Not tainted 
(4.6.0-rc6-sam460ex-jm)

[ 1535.898224] MSR: 00029000   CR: 44422284  XER: 
[ 1535.918868] DEAR: 0128 ESR: 
GPR00: c0466984 ea847dc0 ea85 0108 000f fff0  
0007
GPR08: 0001 c0b5a19c  ea847de0 28428468 205cfe94 205a946e 
bfff8a7c
GPR16: 2097d008 2097d018 2097d090 bfff8980 bfff897c   
4321fedc
GPR24: 2097d578 c0b3f17c c0b8  c0a95e68 eaa35000 c0b8545c 
0108

[ 1536.024665] NIP [c026d3c8] kobject_get+0x18/0x80
[ 1536.044003] LR [c0466984] get_device+0x1c/0x38
[ 1536.063198] Call Trace:
[ 1536.080424] [ea847dc0] [eaa3fa10] 0xeaa3fa10 (unreliable)
[ 1536.100896] [ea847dd0] [c0466984] get_device+0x1c/0x38
[ 1536.121059] [ea847de0] [c04689f4] device_shutdown+0x58/0x178
[ 1536.141727] [ea847e10] [c003c280] kernel_halt+0x38/0x64
[ 1536.161875] [ea847e20] [c003c4cc] SyS_reboot+0x140/0x1b0
[ 1536.182057] [ea847f40] [c000ad80] ret_from_syscall+0x0/0x3c
[ 1536.202568] --- interrupt: c01 at 0x203d1fbc
[ 1536.202568] LR = 0x2058f878
[ 1536.239761] Instruction dump:
[ 1536.257358] 4b9c 7fa3eb78 484cad91 39610020 7fe3fb78 4bda3d74 
9421fff0 7c0802a6
[ 1536.280308] 93e1000c 7c7f1b79 90010014 41820060 <813f0020> 2f89 
41bc001c 809f

[ 1536.303611] ---[ end trace f5a63492b41c62f2 ]---
[ 1536.323546]
[ 1537.340293] note: systemd-shutdow[1] exited with preempt_count 1
[ 1537.363602] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x000b

[ 1537.363602]
[ 1537.404665] Rebooting in 180 seconds..


U-Boot 2015.a (May 16 2015 - 14:20:11)

CPU:   AMCC PowerPC 460EX Rev. B at 1155 MHz (PLB=231 OPB=115 EBC=115)
   No Security/Kasumi support
   Bootstrap Option H - Boot ROM Location I2C (Addr 0x52)
   Internal PCI arbiter enabled
   32 kB I-Cache 32 kB D-Cache
Board: Sam460ex/cr, PCIe 4x + SATA-2
I2C:   ready
DRAM:  ddr2_boost enabled, level 3
   2 GiB (ECC not enabled, 462 MHz, CL4)
PCI:   Bus Dev VenId DevId Class Int
00  04  1095  3512  0104  00
00  06  126f  0501  0380  00
PCIE1: successfully set as root-complex
02  00  1002  683f  0300  ff
Net:   ppc_4xx_eth0
FPGA:  Revision 03 (2010-10-07)
SM502: found
PERMD2:not found
VGA:   1
VESA:  OK
[0.00] Using Canyonlands machine description
[0.00] Linux version 4.6.0-rc6-sam460ex-jm (root@julian-VirtualBox) 
(gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2) ) #4 PREEMPT Fri May 6 
07:54:21 AST 2016
[0.00] Zone ranges:
[0.00]   DMA  [mem 0x-0x2fff]
[0.00]   Normal   empty
[0.00]   HighMem  [mem 0x3000-0x7fff]
[0.00] Movable zone start for each node
[0.00] Early memory node ranges
[0.00]   node   0: [mem 0x-0x7fff]
[0.00] Initmem setup node 0 [mem 0x-0x7fff]
[0.00] MMU: Allocated 1088 bytes of context maps for 255 contexts
[0.00] Built 1 zonelists in Zone order, mobility grouping on.  Total 
pages: 522752
[0.00] Kernel command line: root=/dev/sda6 console=ttyS0,115200 
console=tty0
[0.00] PID hash table entries: 4096 (order: 2, 16384 bytes)
[0.00] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[0.00] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[0.00] Sorting __ex_table...
[0.00] Memory: 2001664K/2097152K available (7416K kernel code, 316K 
rwdata, 3808K rodata, 240K init, 370K bss, 95488K reserved, 0K cma-reserved, 
1310720K highmem)
[0.00] Kernel virtual memory layout:
[0.00]   * 0xfffcf000..0xf000  : fixmap
[0.00]   * 0xffc0..0xffe0  : highmem PTEs
[0.00]   * 0xffa0..0xffc0  : consistent mem
[0.00]   * 0xffa0..0xffa0  : early ioremap
[0.00]   * 0xf100..0xffa0  : vmalloc & ioremap
[0.00] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[0.00] Preemptible hierarchical RCU implementation.
[0.00] Build-time adjustment of leaf fanout to 32.
[0.00] NR_IRQS:512 nr_irqs:512 16
[0.00] UIC0 (32 IRQ sources) at DCR 0xc0
[0.00] UIC1 (32 IRQ sources) at DCR 0xd0
[0.00] UIC2 (32 IRQ sources) at DCR 0xe0
[0.00] UIC3 (32 IRQ sources) at DCR 0xf0
[

Re: [PATCH v1 00/23] ata: sata_dwc_460ex: make it working again

2016-04-24 Thread Julian Margetson

On 4/24/2016 11:21 AM, Christian Lamparter wrote:

On Sunday, April 24, 2016 09:05:43 AM Julian Margetson wrote:

On 4/23/2016 3:41 PM, Christian Lamparter wrote:

There's a known errata for the 460EX, with the CPU lockup upon
high AHB traffic:
<http://lists.denx.de/pipermail/u-boot/2008-June/036078.html>

"This patch implements a fix provided by AMCC so that the lockup upon
simultanious traffic on AHB USB OTG, USB 2.0 and SATA doesn't occur
anymore:..."

This should be fixed by u-boot. However, there's no telling if
there's more to this workaround in the dma engine. You could try
to do the testing without anything connected to the USB ports
and disable/remove all usb hcds modules. As for fixing this:
I did a quick search but couldn't find any public information.
There's always supp...@apm.com (contact them!), or maybe someone
from the Amiga community knows more?



Tested with kernel with all USB disabled. No sata error messages
during the partition copy but the copying is quite slow.

Ok. The CONFIG_DMADEVICES_DEBUG and CONFIG_DMADEVICES_VDEBUG option
have quite a large overhead, if this fixed the issue for now you
could try to disable them and look if the issue comes back or not.
(also, you can drop the mdelay patch if it's still applied). If
the issue doesn't come back, you could add your "Tested-by" tag
too.

Another thing, the sata dwc driver doesn't yet support NCQ. Do you
know if the driver for the Amiga OS does?


so this does appear to be the problem.

So, how to fix this? I know, there's an AHB DMA Arbiter. But I can't
get any documentation for it from AMCC/APM. Maybe denx.de or someone
from the Amiga community knows how to deal with it. In theory, we
could try if limiting the burst length, pending dma request count or
add code to retry failed dma transfers and reinit the usb-cores would
help.

Regards,
Christian



Disabled

CONFIG_DMADEVICES_DEBUG and CONFIG_DMADEVICES_VDEBUG

Still see issues with the USB enabled.
With USB also disabled I was able to finish the partition copy. But 
again it is very slow.


(parted) mklabel msdos
Warning: The existing disk label on /dev/sda will be destroyed and all 
data on

this disk will be lost. Do you want to continue?
Yes/No? y
(parted) p
Model: ATA WDC WD5000AAKX-0 (scsi)
Disk /dev/sda: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number  Start  End  Size  Type  File system  Flags

(parted) q
Information: You may need to update /etc/fstab.

root@Amigaone:/home/amigaone# dd if=/dev/sdb6 of=/dev/sda
43597824+0 records in
43597824+0 records out
22322085888 bytes (22 GB, 21 GiB) copied, 2825.93 s, 7.9 MB/s

Regards
Julian



___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev

Re: [PATCH v1 00/23] ata: sata_dwc_460ex: make it working again

2016-04-24 Thread Julian Margetson

On 4/23/2016 3:41 PM, Christian Lamparter wrote:

On Saturday, April 23, 2016 11:44:09 AM Julian Margetson wrote:

On 4/23/2016 8:02 AM, Julian Margetson wrote:

On 4/22/2016 7:06 AM, Christian Lamparter wrote:

On Friday, April 22, 2016 06:50:44 AM Julian Margetson wrote:

On 4/21/2016 4:25 PM, Christian Lamparter wrote:

On Thursday, April 21, 2016 09:15:21 PM Andy Shevchenko wrote:

The last approach in the commit 8b3444852a2b ("sata_dwc_460ex:
move to generic
DMA driver") to switch to generic DMA engine API wasn't tested on
bare metal.
Besides that we expecting new board support coming with the same
SATA IP but
with different DMA.

The driver has been tested myself on Sam460ex and WD MyBookLive
(apollo3g)
boards. In any case I ask Christian, Måns, and Julian to
independently test and
provide Tested-by tag or error report.

I did a test run on my WD MyBook Live. I applied all the patches in
this series on top of the topic/dw branch of Vinod Koul:
<https://git.kernel.org/cgit/linux/kernel/git/vkoul/slave-dma.git/>

Tested-by: Christian Lamparter<chunk...@googlemail.com>
---
results for my old ST3808110AS HDD. filesystem is ext4.

# hdparm -t /dev/sda

/dev/sda:
Timing buffered disk reads: 204 MB in  3.02 seconds = 67.51 MB/sec

# bonnie++ -u mbl
Using uid:1000, gid:1000.
Writing a byte at a time...done
Writing intelligently...done
Rewriting...done
Reading a byte at a time...done
Reading intelligently...done
start 'em...done...done...done...done...done...
Create files in sequential order...done.
Stat files in sequential order...done.
Delete files in sequential order...done.
Create files in random order...done.
Stat files in random order...done.
Delete files in random order...done.
Version  1.97   --Sequential Output-- --Sequential
Input- --Random-
Concurrency   1 -Per Chr- --Block-- -Rewrite- -Per Chr-
--Block-- --Seeks--
MachineSize K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec
%CP  /sec %CP
mbl496M98  99 26011  21 17589  20   538  99 80138
39 208.9   8
Latency 95267us1409ms 295ms   26947us 9644us
1787ms
Version  1.97   --Sequential Create-- Random
Create
mbl -Create-- --Read--- -Delete-- -Create--
--Read--- -Delete--
 files  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec
%CP  /sec %CP
16  6959  78 + +++  5197  40  7250 79 +
+++  4718  37
Latency   149ms6742us 212ms 177ms 767us
217ms
1.97,1.97,mbl,1,1461269771,496M,,98,99,26011,21,17589,20,538,99,80138,39,208.9,8,16,6959,78,+,+++,5197,40,7250,79,+,+++,4718,37,95267us,1409ms,295ms,26947us,9644us,1787ms,149ms,6742us,212ms,177ms,767us,217ms



Again on copy partitions .

Ok, here's the copy from my mail off-list.

Well, a unrelated driver "m41t80" caused a crash:
[   12.912739] Oops: Kernel access of bad area, sig: 11 [#3]
[   12.912743] PREEMPT Canyonlands
[   12.912753] CPU: 0 PID: 1413 Comm: irq/45-m41t80 Tainted: G
D 4.6.0-rc4-next-20160421-sam460ex-jm #1
[   12.912757] task: ea9834e0 ti: eea6c000 task.ti: eea6c000
[   12.912760] NIP: c0224480 LR: c0023494 CTR: c0042508
[   12.912764] REGS: eea6daf0 TRAP: 0300   Tainted: G D
(4.6.0-rc4-next-20160421-sam460ex-jm)
[   12.912774] MSR: 00029000 <CE,EE,ME>  CR: 24008282 XER: 
[   12.912825] DEAR: 0008 ESR: 
[...]
[   12.912927] --- interrupt: 300 at mutex_lock+0x0/0x1c
[   12.912927] LR = m41t80_handle_irq+0x28/0xac
[   12.912932] [eea6de40] []   (null) (unreliable)
[   12.912938] [eea6de60] [c004ffac] irq_thread_fn+0x2c/0x48
[   12.912944] [eea6de80] [c00501cc] irq_thread+0xc4/0x160
[   12.912951] [eea6ded0] [c003a3f8] kthread+0xc8/0xcc
[   12.912957] [eea6df40] [c000aee8] ret_from_kernel_thread+0x5c/0x64
[   12.912960] Instruction dump:
[   12.912974] 80010014 7fc3f378 bbc10008 7c0803a6 38210010 4be24ca8
9421ffd0 7c0802a6
[   12.912987] bf210014 90010034 3b4302d8 812302ec <83890008>
812302d8 7f9a4840 419e011c
[   12.912995] Fixing recursive fault but reboot is needed!
   ^^^ "reboot is needed!"

Another thing that came to my mind: Have you checked if your hard drive
and the cables are ok? Are there any pending sectors or suspicious smart
values? Has the drive passed the extended offline test?
   Otherwise, I can't reproduce the error with my MyBook system. I've
tested
your kernel and it worked on the device without crashing. (I
copied/dd'ed
80GB from and back to the hard-drive. It was long and boring, but I
didn't
encounter any issues and the crc32 matched).

Sorry, but I can't help you if I can't reproduce it... And short of
sending
your box to test, I see no efficient way to debug it. However, what I
can
do, if you are interested: I have a few "build your own" My Book Live
kits.
It just needs a 3.5" hard-drive and 12v power adapter. If you are
interested
PM me off-list, this way you can veri

Re: [PATCH v1 00/23] ata: sata_dwc_460ex: make it working again

2016-04-23 Thread Julian Margetson

On 4/22/2016 7:06 AM, Christian Lamparter wrote:

On Friday, April 22, 2016 06:50:44 AM Julian Margetson wrote:

On 4/21/2016 4:25 PM, Christian Lamparter wrote:

On Thursday, April 21, 2016 09:15:21 PM Andy Shevchenko wrote:

The last approach in the commit 8b3444852a2b ("sata_dwc_460ex: move to generic
DMA driver") to switch to generic DMA engine API wasn't tested on bare metal.
Besides that we expecting new board support coming with the same SATA IP but
with different DMA.

The driver has been tested myself on Sam460ex and WD MyBookLive (apollo3g)
boards. In any case I ask Christian, Måns, and Julian to independently test and
provide Tested-by tag or error report.

I did a test run on my WD MyBook Live. I applied all the patches in
this series on top of the topic/dw branch of Vinod Koul:
<https://git.kernel.org/cgit/linux/kernel/git/vkoul/slave-dma.git/>

Tested-by: Christian Lamparter<chunk...@googlemail.com>
---
results for my old ST3808110AS HDD. filesystem is ext4.

# hdparm -t /dev/sda

/dev/sda:
   Timing buffered disk reads: 204 MB in  3.02 seconds =  67.51 MB/sec

# bonnie++ -u mbl
Using uid:1000, gid:1000.
Writing a byte at a time...done
Writing intelligently...done
Rewriting...done
Reading a byte at a time...done
Reading intelligently...done
start 'em...done...done...done...done...done...
Create files in sequential order...done.
Stat files in sequential order...done.
Delete files in sequential order...done.
Create files in random order...done.
Stat files in random order...done.
Delete files in random order...done.
Version  1.97   --Sequential Output-- --Sequential Input- --Random-
Concurrency   1 -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks--
MachineSize K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP  /sec %CP
mbl496M98  99 26011  21 17589  20   538  99 80138  39 208.9   8
Latency 95267us1409ms 295ms   26947us9644us1787ms
Version  1.97   --Sequential Create-- Random Create
mbl -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete--
files  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec 
%CP
   16  6959  78 + +++  5197  40  7250  79 + +++  4718  
37
Latency   149ms6742us 212ms 177ms 767us 217ms
1.97,1.97,mbl,1,1461269771,496M,,98,99,26011,21,17589,20,538,99,80138,39,208.9,8,16,6959,78,+,+++,5197,40,7250,79,+,+++,4718,37,95267us,1409ms,295ms,26947us,9644us,1787ms,149ms,6742us,212ms,177ms,767us,217ms


Again on copy partitions .

Ok, here's the copy from my mail off-list.

Well, a unrelated driver "m41t80" caused a crash:
[   12.912739] Oops: Kernel access of bad area, sig: 11 [#3]
[   12.912743] PREEMPT Canyonlands
[   12.912753] CPU: 0 PID: 1413 Comm: irq/45-m41t80 Tainted: G  D 
4.6.0-rc4-next-20160421-sam460ex-jm #1
[   12.912757] task: ea9834e0 ti: eea6c000 task.ti: eea6c000
[   12.912760] NIP: c0224480 LR: c0023494 CTR: c0042508
[   12.912764] REGS: eea6daf0 TRAP: 0300   Tainted: G  D  
(4.6.0-rc4-next-20160421-sam460ex-jm)
[   12.912774] MSR: 00029000 <CE,EE,ME>  CR: 24008282  XER: 
[   12.912825] DEAR: 0008 ESR: 
[...]
[   12.912927] --- interrupt: 300 at mutex_lock+0x0/0x1c
[   12.912927] LR = m41t80_handle_irq+0x28/0xac
[   12.912932] [eea6de40] []   (null) (unreliable)
[   12.912938] [eea6de60] [c004ffac] irq_thread_fn+0x2c/0x48
[   12.912944] [eea6de80] [c00501cc] irq_thread+0xc4/0x160
[   12.912951] [eea6ded0] [c003a3f8] kthread+0xc8/0xcc
[   12.912957] [eea6df40] [c000aee8] ret_from_kernel_thread+0x5c/0x64
[   12.912960] Instruction dump:
[   12.912974] 80010014 7fc3f378 bbc10008 7c0803a6 38210010 4be24ca8 9421ffd0 
7c0802a6
[   12.912987] bf210014 90010034 3b4302d8 812302ec <83890008> 812302d8 7f9a4840 
419e011c
[   12.912995] Fixing recursive fault but reboot is needed!
  ^^^ "reboot is needed!"

Another thing that came to my mind: Have you checked if your hard drive
and the cables are ok? Are there any pending sectors or suspicious smart
values? Has the drive passed the extended offline test?
  
Otherwise, I can't reproduce the error with my MyBook system. I've tested

your kernel and it worked on the device without crashing. (I copied/dd'ed
80GB from and back to the hard-drive. It was long and boring, but I didn't
encounter any issues and the crc32 matched).

Sorry, but I can't help you if I can't reproduce it... And short of sending
your box to test, I see no efficient way to debug it. However, what I can
do, if you are interested: I have a few "build your own" My Book Live kits.
It just needs a 3.5" hard-drive and 12v power adapter. If you are interested
PM me off-list, this way you can verify that the kernels you build do work,
just in case this error is due to a hardware issue (zapped controller,
bad ram/drive/cab

Re: [PATCH v1 00/23] ata: sata_dwc_460ex: make it working again

2016-04-22 Thread Julian Margetson

On 4/21/2016 4:25 PM, Christian Lamparter wrote:

On Thursday, April 21, 2016 09:15:21 PM Andy Shevchenko wrote:

The last approach in the commit 8b3444852a2b ("sata_dwc_460ex: move to generic
DMA driver") to switch to generic DMA engine API wasn't tested on bare metal.
Besides that we expecting new board support coming with the same SATA IP but
with different DMA.

This series is targetting the following things:
- a few bug fixes to the original driver
- a part to fix the DMA engine usage and in particularly dw_dmac driver
- move driver to use generic PHY and "dmas" property which leads to update in 
DTS

The driver has been tested myself on Sam460ex and WD MyBookLive (apollo3g)
boards. In any case I ask Christian, Måns, and Julian to independently test and
provide Tested-by tag or error report.

I did a test run on my WD MyBook Live. I applied all the patches in
this series on top of the topic/dw branch of Vinod Koul:


Tested-by: Christian Lamparter 
---
results for my old ST3808110AS HDD. filesystem is ext4.

# hdparm -t /dev/sda

/dev/sda:
  Timing buffered disk reads: 204 MB in  3.02 seconds =  67.51 MB/sec

# bonnie++ -u mbl
Using uid:1000, gid:1000.
Writing a byte at a time...done
Writing intelligently...done
Rewriting...done
Reading a byte at a time...done
Reading intelligently...done
start 'em...done...done...done...done...done...
Create files in sequential order...done.
Stat files in sequential order...done.
Delete files in sequential order...done.
Create files in random order...done.
Stat files in random order...done.
Delete files in random order...done.
Version  1.97   --Sequential Output-- --Sequential Input- --Random-
Concurrency   1 -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks--
MachineSize K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP  /sec %CP
mbl496M98  99 26011  21 17589  20   538  99 80138  39 208.9   8
Latency 95267us1409ms 295ms   26947us9644us1787ms
Version  1.97   --Sequential Create-- Random Create
mbl -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete--
   files  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP
  16  6959  78 + +++  5197  40  7250  79 + +++  4718  37
Latency   149ms6742us 212ms 177ms 767us 217ms
1.97,1.97,mbl,1,1461269771,496M,,98,99,26011,21,17589,20,538,99,80138,39,208.9,8,16,6959,78,+,+++,5197,40,7250,79,+,+++,4718,37,95267us,1409ms,295ms,26947us,9644us,1787ms,149ms,6742us,212ms,177ms,767us,217ms





Again on copy partitions .
=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2016.04.21 20:03:45 =~=~=~=~=~=~=~=~=~=~=~=
[0.00] Using Canyonlands machine description
[0.00] Linux version 4.6.0-rc4-next-20160421-sam460ex-jm 
(root@julian-VirtualBox) (gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2) ) 
#1 PREEMPT Thu Apr 21 19:56:14 AST 2016
[0.00] Zone ranges:
[0.00]   DMA  [mem 0x-0x2fff]
[0.00]   Normal   empty
[0.00]   HighMem  [mem 0x3000-0x7fff]
[0.00] Movable zone start for each node
[0.00] Early memory node ranges
[0.00]   node   0: [mem 0x-0x7fff]
[0.00] Initmem setup node 0 [mem 0x-0x7fff]
[0.00] MMU: Allocated 1088 bytes of context maps for 255 contexts
[0.00] Built 1 zonelists in Zone order, mobility grouping on.  Total 
pages: 522752
[0.00] Kernel command line: root=/dev/sdb6 console=ttyS0,115200 
console=tty0
[0.00] PID hash table entries: 4096 (order: 2, 16384 bytes)
[0.00] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[0.00] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[0.00] Sorting __ex_table...
[0.00] Memory: 2001640K/2097152K available (7432K kernel code, 316K 
rwdata, 3816K rodata, 240K init, 370K bss, 95512K reserved, 0K cma-reserved, 
1310720K highmem)
[0.00] Kernel virtual memory layout:
[0.00]   * 0xfffcf000..0xf000  : fixmap
[0.00]   * 0xffc0..0xffe0  : highmem PTEs
[0.00]   * 0xffa0..0xffc0  : consistent mem
[0.00]   * 0xffa0..0xffa0  : early ioremap
[0.00]   * 0xf100..0xffa0  : vmalloc & ioremap
[0.00] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[0.00] Preemptible hierarchical RCU implementation.
[0.00] Build-time adjustment of leaf fanout to 32.
[0.00] NR_IRQS:512 nr_irqs:512 16
[0.00] UIC0 (32 IRQ sources) at DCR 0xc0
[0.00] UIC1 (32 IRQ sources) at DCR 0xd0
[0.00] UIC2 (32 IRQ sources) at DCR 0xe0
[0.00] UIC3 (32 IRQ sources) at DCR 0xf0
[0.13] clocksource: timebase: mask: 

Sam460ex pciex1 sound card issue

2016-04-17 Thread Julian Margetson

Hi

I am having problem with pciex1 sound card on my Sam460ex.
The card is an ice1724 based model.
I have reported the the issue to the alsa-dev mailing list.
So far no one has any ideas so I am exploring the possibility of the 
issue being caused by something going

wrong on the initialization of the motherboard.

The sound card is recognized but only works on about 1 in 5 boots .
By contrast a CMI8738 pciex1 sound card  works perfectly as do USB cm108 
based external cards .


In looking at the dmesg output from a boot where the ice1724 card is 
working the only difference that i can see is

 the start at [ 0.15]

[ 0.15] clocksource: timebase: mask: 0x max_cycles: 
0x10a60dda894, max_idle_ns: 440795207041 ns


for the non working boots is

[ 0.14] clocksource: timebase: mask: 0x max_cycles: 
0x10a60dda894, max_idle_ns: 440795207041 ns


Attached the two dmesg logs.

Regards
Julian








[0.00] Using Canyonlands machine description
[0.00] Initializing cgroup subsys cpu
[0.00] Linux version 4.4.7-sam460ex-jm (root@julian-VirtualBox) (gcc 
version 5.3.1 20160330 (Ubuntu 5.3.1-13ubuntu3) ) #7 PREEMPT Sun Apr 17 
10:38:34 AST 2016
[0.00] Found legacy serial port 0 for /plb/opb/serial@ef600300
[0.00]   mem=4ef600300, taddr=4ef600300, irq=0, clk=11059200, speed=0
[0.00] Found legacy serial port 1 for /plb/opb/serial@ef600400
[0.00]   mem=4ef600400, taddr=4ef600400, irq=0, clk=11059200, speed=0
[0.00] Top of RAM: 0x8000, Total RAM: 0x8000
[0.00] Memory hole size: 0MB
[0.00] Zone ranges:
[0.00]   DMA  [mem 0x-0x2fff]
[0.00]   Normal   empty
[0.00]   HighMem  [mem 0x3000-0x7fff]
[0.00] Movable zone start for each node
[0.00] Early memory node ranges
[0.00]   node   0: [mem 0x-0x7fff]
[0.00] Initmem setup node 0 [mem 0x-0x7fff]
[0.00] On node 0 totalpages: 524288
[0.00] free_area_init_node: node 0, pgdat c0b570cc, node_mem_map 
eefed000
[0.00]   DMA zone: 1536 pages used for memmap
[0.00]   DMA zone: 0 pages reserved
[0.00]   DMA zone: 196608 pages, LIFO batch:31
[0.00]   HighMem zone: 327680 pages, LIFO batch:31
[0.00] MMU: Allocated 1088 bytes of context maps for 255 contexts
[0.00] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[0.00] pcpu-alloc: [0] 0 
[0.00] Built 1 zonelists in Zone order, mobility grouping on.  Total 
pages: 522752
[0.00] Kernel command line: root=/dev/sda6 console=ttyS0,115200 
console=tty0
[0.00] PID hash table entries: 4096 (order: 2, 16384 bytes)
[0.00] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[0.00] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[0.00] Sorting __ex_table...
[0.00] Memory: 2001796K/2097152K available (7308K kernel code, 316K 
rwdata, 3784K rodata, 236K init, 372K bss, 95356K reserved, 0K cma-reserved, 
1310720K highmem)
[0.00] Kernel virtual memory layout:
[0.00]   * 0xfffcf000..0xf000  : fixmap
[0.00]   * 0xffc0..0xffe0  : highmem PTEs
[0.00]   * 0xffa0..0xffc0  : consistent mem
[0.00]   * 0xffa0..0xffa0  : early ioremap
[0.00]   * 0xf100..0xffa0  : vmalloc & ioremap
[0.00] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[0.00] Preemptible hierarchical RCU implementation.
[0.00]  Build-time adjustment of leaf fanout to 32.
[0.00] NR_IRQS:512 nr_irqs:512 16
[0.00] UIC0 (32 IRQ sources) at DCR 0xc0
[0.00] UIC1 (32 IRQ sources) at DCR 0xd0
[0.00] UIC2 (32 IRQ sources) at DCR 0xe0
[0.00] UIC3 (32 IRQ sources) at DCR 0xf0
[0.00] time_init: decrementer frequency = 1155.10 MHz
[0.00] time_init: processor frequency   = 1155.10 MHz
[0.15] clocksource: timebase: mask: 0x max_cycles: 
0x10a60dda894, max_idle_ns: 440795207041 ns
[0.23] clocksource: timebase mult[dda520] shift[24] registered
[0.32] clockevent: decrementer mult[93d70a53] shift[31] cpu[0]
[0.000137] Console: colour dummy device 80x25
[0.000515] console [tty0] enabled
[0.000548] pid_max: default: 32768 minimum: 301
[0.000653] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[0.000677] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[0.003216] devtmpfs: initialized
[0.005878] clocksource: jiffies: mask: 0x max_cycles: 0x, 
max_idle_ns: 1911260446275000 ns
[0.006487] xor: measuring software checksum speed
[0.016595]8regs :   896.000 MB/sec
[0.026428]8regs_prefetch:   708.000 MB/sec
[0.036471]32regs:  1232.000 MB/sec
[0.046543]

Re: commit 9178ba294b6839eeff1a91bed95515d783f3ee6c an A-Eon Tabor Board

2016-03-19 Thread Julian Margetson

On 2/3/2016 6:59 PM, Alexander Graf wrote:



On 02/03/2016 11:54 PM, Julian Margetson wrote:

On 2/3/2016 6:20 PM, Alexander Graf wrote:



On 02/03/2016 11:15 PM, Julian Margetson wrote:

On 2/3/2016 4:43 PM, Alexander Graf wrote:



On 02/03/2016 10:33 AM, Julian Margetson wrote:
Resending as it was attached to and old thread relating to a 
different motherboard.


On 2/2/2016 9:54 AM, Julian Margetson wrote:


Commit 9178ba294b6839eeff1a91bed95515d783f3ee6c prevents 
building of kernel 4.1 branch on A-Eon Tabor Board.


CC arch/powerpc/math-emu/fsqrt.o
arch/powerpc/platforms/85xx/tabor.c:194:2: error: unknown field 
‘power_off’ specified in initializer


I can't seem to find that file in Linux upstream?


Alex





It may have been discontinued as the patches used were maintained 
along with patches for the (Varisys)  A-Eon Cyrus board

which is officially supported from kernel 4.4.

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=c383ee84e1d575b09d167185d15df24bde25eb15 



I don't quite understand how an internal API change in Linux 
breaking random external patches is a bug? Either your code is 
upstream or it can break on every git commit done upstream.



Alex





Sorry I am relatively new at this.
If I manage to pinpoint a problem on my powerpc machines I report it 
. Most of them so far have indeed been bugs.
The random external patches were done by person with far greater 
competence than me who are no longer in the picture.

Any  guidance would be greatly  appreciated.


I think the most important step really is to upstream board support, 
otherwise things will continue to fall apart for sure.


As for the exact breakage you saw, just remove the line and put a line 
like


  pm_power_off = tabor_power_off;

in your board probe function in tabor.c.


Alex





Could not get it to work with the
 pm_power_off = tabor_power_off;


so resorted to the option below and it builds and boots (Tested Kernel 
4.5.0).

shuts down but no power off.
Can live with that for now.


Thanks for your help .


Regards
Julian


define_machine(tabor) {
.name= "Tabor",
.probe= tabor_probe,
.setup_arch= tabor_setup_arch,
.init_IRQ= tabor_pic_init,
#ifdef CONFIG_PCI
.pcibios_fixup_bus= fsl_pcibios_fixup_bus,
.pcibios_fixup_phb= fsl_pcibios_fixup_phb,
#endif
.get_irq= mpic_get_irq,
.restart= fsl_rstcr_restart,
.calibrate_decr= generic_calibrate_decr,
.progress= udbg_progress,
};

___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev

Re: commit 9178ba294b6839eeff1a91bed95515d783f3ee6c an A-Eon Tabor Board

2016-03-19 Thread Julian Margetson

On 3/16/2016 7:56 AM, Julian Margetson wrote:

On 2/3/2016 6:59 PM, Alexander Graf wrote:



On 02/03/2016 11:54 PM, Julian Margetson wrote:

On 2/3/2016 6:20 PM, Alexander Graf wrote:



On 02/03/2016 11:15 PM, Julian Margetson wrote:

On 2/3/2016 4:43 PM, Alexander Graf wrote:



On 02/03/2016 10:33 AM, Julian Margetson wrote:
Resending as it was attached to and old thread relating to a 
different motherboard.


On 2/2/2016 9:54 AM, Julian Margetson wrote:


Commit 9178ba294b6839eeff1a91bed95515d783f3ee6c prevents 
building of kernel 4.1 branch on A-Eon Tabor Board.


CC arch/powerpc/math-emu/fsqrt.o
arch/powerpc/platforms/85xx/tabor.c:194:2: error: unknown field 
‘power_off’ specified in initializer


I can't seem to find that file in Linux upstream?


Alex





It may have been discontinued as the patches used were maintained 
along with patches for the (Varisys)  A-Eon Cyrus board

which is officially supported from kernel 4.4.

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=c383ee84e1d575b09d167185d15df24bde25eb15 



I don't quite understand how an internal API change in Linux 
breaking random external patches is a bug? Either your code is 
upstream or it can break on every git commit done upstream.



Alex





Sorry I am relatively new at this.
If I manage to pinpoint a problem on my powerpc machines I report it 
. Most of them so far have indeed been bugs.
The random external patches were done by person with far greater 
competence than me who are no longer in the picture.

Any  guidance would be greatly  appreciated.


I think the most important step really is to upstream board support, 
otherwise things will continue to fall apart for sure.


As for the exact breakage you saw, just remove the line and put a 
line like


  pm_power_off = tabor_power_off;

in your board probe function in tabor.c.


Alex





Could not get it to work with the
 pm_power_off = tabor_power_off;


so resorted to the option below and it builds and boots (Tested Kernel 
4.5.0).

shuts down but no power off.
Can live with that for now.


Thanks for your help .


Regards
Julian


define_machine(tabor) {
.name= "Tabor",
.probe= tabor_probe,
.setup_arch= tabor_setup_arch,
.init_IRQ= tabor_pic_init,
#ifdef CONFIG_PCI
.pcibios_fixup_bus= fsl_pcibios_fixup_bus,
.pcibios_fixup_phb= fsl_pcibios_fixup_phb,
#endif
.get_irq= mpic_get_irq,
.restart= fsl_rstcr_restart,
.calibrate_decr= generic_calibrate_decr,
.progress= udbg_progress,
};



Revisited and got  everything working  .
Thanks again.

Regards
Julian

static void tabor_power_off(void)
{
local_irq_disable();
if (power_gpio)
/* set mcu control register */
out_be32(power_gpio, in_be32(power_gpio) & 0xefff7fff); /* MCU Power Off */
else
printk(KERN_ERR "Power control not available\n");
while (1) ;

pm_power_off = tabor_power_off;

}


define_machine(tabor) {
.name= "Tabor",
.probe= tabor_probe,
.setup_arch= tabor_setup_arch,
.init_IRQ= tabor_pic_init,
#ifdef CONFIG_PCI
.pcibios_fixup_bus= fsl_pcibios_fixup_bus,
.pcibios_fixup_phb= fsl_pcibios_fixup_phb,
#endif
.restart= tabor_restart,
.halt= tabor_power_off,
.get_irq= mpic_get_irq,
.restart= fsl_rstcr_restart,
.calibrate_decr= generic_calibrate_decr,
.progress= udbg_progress,
};



___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev

Re: commit 9178ba294b6839eeff1a91bed95515d783f3ee6c an A-Eon Tabor Board

2016-02-03 Thread Julian Margetson
Resending as it was attached to and old thread relating to a different 
motherboard.


On 2/2/2016 9:54 AM, Julian Margetson wrote:


Commit 9178ba294b6839eeff1a91bed95515d783f3ee6c prevents building of 
kernel 4.1 branch on A-Eon Tabor Board.


CC arch/powerpc/math-emu/fsqrt.o
arch/powerpc/platforms/85xx/tabor.c:194:2: error: unknown field 
‘power_off’ specified in initializer

  .power_off  = tabor_power_off,
  ^
make[2]: *** [arch/powerpc/platforms/85xx/tabor.o] Error 1
make[1]: *** [arch/powerpc/platforms/85xx] Error 2
make: *** [arch/powerpc/platforms] Error 2


Builds after reverting  85xx portions of commit.

==
commit 9178ba294b6839eeff1a91bed95515d783f3ee6c

Author: Alexander Graf <ag...@suse.de>

Date: Mon Oct 13 16:01:09 2014 +0200


powerpc: Convert power off logic to pm_power_off

The generic Linux framework to power off the machine is a function 
pointer


called pm_power_off. The trick about this pointer is that device 
drivers can


potentially implement it rather than board files.

Today on powerpc we set pm_power_off to invoke our generic full 
machine power


off logic which then calls ppc_md.power_off to invoke machine specific 
power


off.

However, when we want to add a power off GPIO via the "gpio-poweroff" 
driver,


this card house falls apart. That driver only registers itself if 
pm_power_off


is NULL to ensure it doesn't override board specific logic. However, 
since we


always set pm_power_off to the generic power off logic (which will 
just not


power off the machine if no ppc_md.power_off call is implemented), we 
can't


implement power off via the generic GPIO power off driver.

To fix this up, let's get rid of the ppc_md.power_off logic and just 
always use


pm_power_off as was intended. Then individual drivers such as the GPIO 
power off


driver can implement power off logic via that function pointer.

With this patch set applied and a few patches on top of QEMU that 
implement a


power off GPIO on the virt e500 machine, I can successfully turn off 
my virtual


machine after halt.

Signed-off-by: Alexander Graf <ag...@suse.de>

[mpe: Squash into one patch and update changelog based on cover letter]

Signed-off-by: Michael Ellerman <m...@ellerman.id.au>


:04 04 11d9242dda2d364042ad2443b81aa124655ca79d 
8e5c37793f68e09977278bcea28e97ac7e0b812d M arch


root@julian-VirtualBox:/usr/src/linux-test#


root@julian-VirtualBox:/usr/src/linux-test# git bisect log

git bisect start

# bad: [97bf6af1f928216fd6c5a66e8a57bfa95a659672] Linux 3.19-rc1

git bisect bad 97bf6af1f928216fd6c5a66e8a57bfa95a659672

# good: [b2776bf7149bddd1f4161f14f79520f17fc1d71d] Linux 3.18

git bisect good b2776bf7149bddd1f4161f14f79520f17fc1d71d

# bad: [97bf6af1f928216fd6c5a66e8a57bfa95a659672] Linux 3.19-rc1

git bisect bad 97bf6af1f928216fd6c5a66e8a57bfa95a659672

# bad: [97bf6af1f928216fd6c5a66e8a57bfa95a659672] Linux 3.19-rc1

git bisect bad 97bf6af1f928216fd6c5a66e8a57bfa95a659672

# good: [70e71ca0af244f48a5dcf56dc435243792e3a495] Merge 
git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next


git bisect good 70e71ca0af244f48a5dcf56dc435243792e3a495

# bad: [988adfdffdd43cfd841df734664727993076d7cb] Merge branch 
'drm-next' of git://people.freedesktop.org/~airlied/linux


git bisect bad 988adfdffdd43cfd841df734664727993076d7cb

# bad: [e7cf773d431a63a2417902696fcc9e0ebdc83bbe] Merge tag 
'usb-3.19-rc1' of 
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb


git bisect bad e7cf773d431a63a2417902696fcc9e0ebdc83bbe

# bad: [26ceb127f7bcf473db926c6a026b18ddd6f274e8] Merge branch 
'for-linus' of git://ftp.arm.linux.org.uk/~rmk/linux-arm


git bisect bad 26ceb127f7bcf473db926c6a026b18ddd6f274e8

# bad: [9bfccec24e31f4f83445cfe0c1b0a5ef97900628] Merge tag 
'ext4_for_linus' of 
git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4


git bisect bad 9bfccec24e31f4f83445cfe0c1b0a5ef97900628

# good: [e2965cd0003f222bd49f67907c2bc6ed691c6d20] MIPS: Add MFHC0 and 
MTHC0 instructions to uasm.


git bisect good e2965cd0003f222bd49f67907c2bc6ed691c6d20

# bad: [56548fc0e86cb9156af7a7e1f15ba78f251dafaf] powerpc/powernv: 
Return to cpu offline loop when finished in KVM guest


git bisect bad 56548fc0e86cb9156af7a7e1f15ba78f251dafaf

# bad: [59994fb01a102a448ba758c9b824a29b4a99cc1b] powerpc: Use generic 
PIE randomization


git bisect bad 59994fb01a102a448ba758c9b824a29b4a99cc1b

# bad: [7aa189c8f57f2141b8655c2a13c7486d0844d490] powerpc/pseries: 
Quieten ibm,pcie-link-speed-stats warning


git bisect bad 7aa189c8f57f2141b8655c2a13c7486d0844d490

# bad: [6e4c632cdff7bf0238a2543dfe98bd1ad40313c2] powerpc: make __ffs 
return unsigned long


git bisect bad 6e4c632cdff7bf0238a2543dfe98bd1ad40313c2

# bad: [adb7cd732292b06ee964d9f6090b17c70bd8bd3d] powerpc/pci: Quieten 
unset I/O resource warning


git bisect bad adb7cd732292b06ee96

Re: commit 9178ba294b6839eeff1a91bed95515d783f3ee6c an A-Eon Tabor Board

2016-02-03 Thread Julian Margetson

On 2/3/2016 4:43 PM, Alexander Graf wrote:



On 02/03/2016 10:33 AM, Julian Margetson wrote:
Resending as it was attached to and old thread relating to a 
different motherboard.


On 2/2/2016 9:54 AM, Julian Margetson wrote:


Commit 9178ba294b6839eeff1a91bed95515d783f3ee6c prevents building of 
kernel 4.1 branch on A-Eon Tabor Board.


CC arch/powerpc/math-emu/fsqrt.o
arch/powerpc/platforms/85xx/tabor.c:194:2: error: unknown field 
‘power_off’ specified in initializer


I can't seem to find that file in Linux upstream?


Alex





It may have been discontinued as the patches used were maintained along 
with patches for the (Varisys)  A-Eon Cyrus board

which is officially supported from kernel 4.4.

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=c383ee84e1d575b09d167185d15df24bde25eb15

Julian

___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev

Re: commit 9178ba294b6839eeff1a91bed95515d783f3ee6c an A-Eon Tabor Board

2016-02-03 Thread Julian Margetson

On 2/3/2016 6:59 PM, Alexander Graf wrote:



On 02/03/2016 11:54 PM, Julian Margetson wrote:

On 2/3/2016 6:20 PM, Alexander Graf wrote:



On 02/03/2016 11:15 PM, Julian Margetson wrote:

On 2/3/2016 4:43 PM, Alexander Graf wrote:



On 02/03/2016 10:33 AM, Julian Margetson wrote:
Resending as it was attached to and old thread relating to a 
different motherboard.


On 2/2/2016 9:54 AM, Julian Margetson wrote:


Commit 9178ba294b6839eeff1a91bed95515d783f3ee6c prevents 
building of kernel 4.1 branch on A-Eon Tabor Board.


CC arch/powerpc/math-emu/fsqrt.o
arch/powerpc/platforms/85xx/tabor.c:194:2: error: unknown field 
‘power_off’ specified in initializer


I can't seem to find that file in Linux upstream?


Alex





It may have been discontinued as the patches used were maintained 
along with patches for the (Varisys)  A-Eon Cyrus board

which is officially supported from kernel 4.4.

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=c383ee84e1d575b09d167185d15df24bde25eb15 



I don't quite understand how an internal API change in Linux 
breaking random external patches is a bug? Either your code is 
upstream or it can break on every git commit done upstream.



Alex





Sorry I am relatively new at this.
If I manage to pinpoint a problem on my powerpc machines I report it 
. Most of them so far have indeed been bugs.
The random external patches were done by person with far greater 
competence than me who are no longer in the picture.

Any  guidance would be greatly  appreciated.


I think the most important step really is to upstream board support, 
otherwise things will continue to fall apart for sure.


As for the exact breakage you saw, just remove the line and put a line 
like


  pm_power_off = tabor_power_off;

in your board probe function in tabor.c.


Alex





Thanks.
I will give it a try.

Julian

___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev

Re: commit 9178ba294b6839eeff1a91bed95515d783f3ee6c an A-Eon Tabor Board

2016-02-03 Thread Julian Margetson

On 2/3/2016 6:20 PM, Alexander Graf wrote:



On 02/03/2016 11:15 PM, Julian Margetson wrote:

On 2/3/2016 4:43 PM, Alexander Graf wrote:



On 02/03/2016 10:33 AM, Julian Margetson wrote:
Resending as it was attached to and old thread relating to a 
different motherboard.


On 2/2/2016 9:54 AM, Julian Margetson wrote:


Commit 9178ba294b6839eeff1a91bed95515d783f3ee6c prevents building 
of kernel 4.1 branch on A-Eon Tabor Board.


CC arch/powerpc/math-emu/fsqrt.o
arch/powerpc/platforms/85xx/tabor.c:194:2: error: unknown field 
‘power_off’ specified in initializer


I can't seem to find that file in Linux upstream?


Alex





It may have been discontinued as the patches used were maintained 
along with patches for the (Varisys)  A-Eon Cyrus board

which is officially supported from kernel 4.4.

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=c383ee84e1d575b09d167185d15df24bde25eb15 



I don't quite understand how an internal API change in Linux breaking 
random external patches is a bug? Either your code is upstream or it 
can break on every git commit done upstream.



Alex





Sorry I am relatively new at this.
If I manage to pinpoint a problem on my powerpc machines I report it . 
Most of them so far have indeed been bugs.
The random external patches were done by person with far greater 
competence than me who are no longer in the picture.

Any  guidance would be greatly  appreciated .

Julian



___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev

Re: No HDMI Audio with Radeon HD7750 on Acube Sam460ex AMCC powerpc 460ex board

2015-05-06 Thread Julian Margetson

git bisect good
38aef1549b18539eaecd804383a6ccb6588a9ce1 is the first bad commit
commit 38aef1549b18539eaecd804383a6ccb6588a9ce1
Author: Alex Deucher alexander.deuc...@amd.com
Date:   Tue Apr 7 10:20:49 2015 -0400

drm/radeon: only enable audio streams if the monitor supports it

Selectively enable which packets we send based on monitor caps.

Signed-off-by: Alex Deucher alexander.deuc...@amd.com

Cc: sta...@vger.kernel.org

:04 04 e27f98a4a15d2f30baf3ea92420112874b0b1c34 
17af34604734b63ce30cfa3637fa1fa1fa1a38f4 M  drivers


Problems with HDMI audio connection continue.
Kernel 4.0.0 will not boot with HDMI connected only DVI. HD6670  HD7750 
tested .

Kernel 4.1.0-rc1 same. HD7750 tested .
Kernel 4.1.0-rc2 will only boot if monitor connected with DVI to VGA 
adapter . HD7750 tested.


U-Boot 2010.06.05a (Jan 30 2012 - 16:06:56)

CPU:   AMCC PowerPC 460EX Rev. B at 1155 MHz (PLB=231 OPB=115 EBC=115)
   No Security/Kasumi support
   Bootstrap Option H - Boot ROM Location I2C (Addr 0x52)
   Internal PCI arbiter enabled
   32 kB I-Cache 32 kB D-Cache
Board: Sam460ex, PCIe 4x + PCIe 1x
I2C:   ready
DRAM:  2 GiB (ECC not enabled, 462 MHz, CL4)
PCI:   Bus Dev VenId DevId Class Int
00  04  1095  3512  0104  00
00  06  126f  0501  0380  00
PCIE0: successfully set as root-complex
03  00  1412  1724  0401  ff
02  00  1b21  1080  0604  00
PCIE1: successfully set as root-complex
05  00  1002  683f  0300  ff
Net:   ppc_4xx_eth0
FPGA:  Revision 03 (2010-10-07)
SM502: found
VGA:   1
VESA:  OK

[2.752985] Generic non-volatile memory driver v1.1
[2.758430] Linux agpgart interface v0.103
[2.762867] [drm] Initialized drm 1.1.0 20060810
[2.767774] [drm] radeon kernel modesetting enabled.
[2.773908] [drm] initializing kernel modesetting (VERDE 0x1002:0x683F 
0x1545:0x7750).
[2.782084] [drm] register mmio base: 0xe9000
[2.786859] [drm] register mmio size: 262144
[3.123010] ATOM BIOS: C44501
[3.126284] radeon 0001:81:00.0: VRAM: 1024M 0x - 
0x3FFF (1024M used)
[3.135213] radeon 0001:81:00.0: GTT: 1024M 0x4000 - 
0x7FFF
[3.142897] [drm] Detected VRAM RAM=1024M, BAR=256M
[3.147791] [drm] RAM width 128bits DDR
[3.151836] [TTM] Zone  kernel: Available graphics memory: 379234 kiB
[3.158325] [TTM] Zone highmem: Available graphics memory: 1034594 kiB
[3.164877] [TTM] Initializing pool allocator
[3.169271] [TTM] Initializing DMA pool allocator
[3.174101] [drm] radeon: 1024M of VRAM memory ready
[3.179107] [drm] radeon: 1024M of GTT memory ready.
[3.184146] [drm] Loading verde Microcode
[3.188210] [drm] Internal thermal controller with fan control
[3.194379] [drm] probing gen 2 caps for device aaa1:bed1 = 18cc41/0
[3.248227] [drm] radeon: dpm initialized
[3.252458] [drm] GART: num cpu pages 262144, num gpu pages 262144
[3.264041] [drm] probing gen 2 caps for device aaa1:bed1 = 18cc41/0
[3.298301] [drm] PCIE GART of 1024M enabled (table at 0x00277000).
[3.305645] radeon 0001:81:00.0: WB enabled
[3.309885] radeon 0001:81:00.0: fence driver on ring 0 use gpu addr 
0x4c00 and cpu addr 0xffc01c00
[3.320010] radeon 0001:81:00.0: fence driver on ring 1 use gpu addr 
0x4c04 and cpu addr 0xffc01c04
[3.330130] radeon 0001:81:00.0: fence driver on ring 2 use gpu addr 
0x4c08 and cpu addr 0xffc01c08
[3.340252] radeon 0001:81:00.0: fence driver on ring 3 use gpu addr 
0x4c0c and cpu addr 0xffc01c0c
[3.350374] radeon 0001:81:00.0: fence driver on ring 4 use gpu addr 
0x4c10 and cpu addr 0xffc01c10
[3.382285] radeon 0001:81:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0xf90b5a18
[3.392430] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[3.399069] [drm] Driver supports precise vblank timestamp query.
[3.405190] radeon 0001:81:00.0: radeon: MSI limited to 32-bit
[3.411071] ppc4xx_setup_msi_irqs: fail allocating msi interrupt
[3.417195] [drm] radeon: irq initialized.
[4.175889] [drm:r600_ring_test] *ERROR* radeon: ring 0 test failed 
(scratch(0x850C)=0xCAFEDEAD)
[4.184750] radeon 0001:81:00.0: disabling GPU acceleration
[4.388914] [drm] Radeon Display Connectors
[4.393501] [drm] Connector 0:
[4.396624] [drm]   HDMI-A-1
[4.399626] [drm]   HPD4
[4.402211] [drm]   DDC: 0x6570 0x6570 0x6574 0x6574 0x6578 0x6578 0x657c 
0x657c
[4.409664] [drm]   Encoders:
[4.412683] [drm] DFP1: INTERNAL_UNIPHY2
[4.416983] [drm] Connector 1:
[4.420056] [drm]   DVI-I-1
[4.422868] [drm]   HPD2
[4.425423] [drm]   DDC: 0x6560 0x6560 0x6564 0x6564 0x6568 0x6568 0x656c 
0x656c
[4.432841] [drm]   Encoders:
[4.435828] [drm] DFP2: INTERNAL_UNIPHY
[4.440029] [drm] CRT1: INTERNAL_KLDSCP_DAC1
[4.560536] [drm] 

Re: [PATCH 1/1] ata: select DW_DMAC in case of SATA_DWC

2015-05-05 Thread Julian Margetson

Thank you.
this resolves the build issue .

On 5/5/2015 5:14 AM, Andy Shevchenko wrote:

Since sata_dwc_460ex.c was moved to generic DMA driver we have to ensure that
user can still compile it.

Fixes: 8b3444852a2b (sata_dwc_460ex: move to generic DMA driver)
Signed-off-by: Andy Shevchenko andriy.shevche...@linux.intel.com
---
  drivers/ata/Kconfig | 1 +
  1 file changed, 1 insertion(+)

diff --git a/drivers/ata/Kconfig b/drivers/ata/Kconfig
index ee5209f..9dca4b9 100644
--- a/drivers/ata/Kconfig
+++ b/drivers/ata/Kconfig
@@ -270,6 +270,7 @@ config ATA_PIIX
  config SATA_DWC
tristate DesignWare Cores SATA support
depends on 460EX
+   select DW_DMAC
help
  This option enables support for the on-chip SATA controller of the
  AppliedMicro processor 460EX.


___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev

Kernel 4.1-rc1 build fails on Sam460ex amcc 460ex powerpc Canyonlands

2015-04-27 Thread Julian Margetson

Kernel 4.1-rc1 build fails  on Sam460ex amcc 460ex powerpc Canyonlands with
CONFIG_SATA_DWC=y

sata_dwc_460ex.c:(.text+0xa165c): undefined reference to `dw_dma_remove'
drivers/built-in.o: In function `sata_dwc_probe':
sata_dwc_460ex.c:(.text+0xa1900): undefined reference to `dw_dma_probe'
sata_dwc_460ex.c:(.text+0xa1954): undefined reference to `dw_dma_remove'
make: *** [vmlinux] Error 1

___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev

Re: Problems with Kernels 3.17-rc1 and onwards on Acube Sam460 AMCC 460ex board

2015-03-09 Thread Julian Margetson

On 3/9/2015 8:30 PM, Michael Ellerman wrote:

On Sat, 2015-03-07 at 12:10 -0400, Julian Margetson wrote:

With the latest commits

[   29.960572] Unable to handle kernel paging request for data at address 
0x0008
[   29.974350] Faulting instruction address: 0xc04a4f44
[   32.012918] Oops: Kernel access of bad area, sig: 11 [#1]
[   32.044900] PREEMPT Canyonlands
[   32.061504] Modules linked in: cfg80211 bnep rfcomm bluetooth
[   32.081023] CPU: 0 PID: 2087 Comm: Xorg Not tainted 4.0.0-rc2-Sam460ex #1
[   32.101802] task: ed6891a0 ti: ed606000 task.ti: ed606000
[   32.121175] NIP: c04a4f44 LR: c03e6a4c CTR: c03d7b6c
[   32.139995] REGS: ed607c50 TRAP: 0300   Not tainted  (4.0.0-rc2-Sam460ex)
[   32.160678] MSR: 00029000 CE,EE,ME  CR: 24004442  XER: 
[   32.180922] DEAR: 0008 ESR: 
GPR00: c03e6a4c ed607d00 ed6891a0 eeac8000  000f ed607be8 
GPR08: f6a3  eeaae400 ed607cc0 24004422 b7ceeff8 b7d05c14 
GPR16:    ed607e18 eeaae578 eebe2600 0001 4000
GPR24: 4000 c075bd08 fff2  eeac8000 0001 0001 ee51a400
[   32.285496] NIP [c04a4f44] radeon_audio_enable+0x4/0x18
[   32.305509] LR [c03e6a4c] radeon_dvi_detect+0x388/0x3ac
[   32.325444] Call Trace:
[   32.342325] [ed607d00] [c03e6a4c] radeon_dvi_detect+0x388/0x3ac (unreliable)
[   32.364075] [ed607d30] [c0391cc4] 
drm_helper_probe_single_connector_modes_merge_bits+0xf4/0x434
[   32.387631] [ed607d70] [c03adecc] drm_mode_getconnector+0xe4/0x330
[   32.408687] [ed607e10] [c03a0bbc] drm_ioctl+0x348/0x464

You should send that to the Radeon maintainers.

cheers




Thanks.

I have raised a couple of threads on the dri-de...@lists.freedesktop.org 
list .


___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev

Re: Problems with Kernels 3.17-rc1 and onwards on Acube Sam460 AMCC 460ex board

2015-03-07 Thread Julian Margetson

On 3/5/2015 7:15 AM, Julian Margetson wrote:

On 3/4/2015 7:52 PM, Michael Ellerman wrote:

On Wed, 2015-03-04 at 07:46 -0400, Julian Margetson wrote:

Still stuck.
Problem still exist with 4.0.0-rc2 and I cant finish the bisect.
Triggered when using HDMI. No problem when using DVI.
[   33.535692] Unable to handle kernel paging request for data at 
address 0x0008

[   33.566786] Faulting instruction address: 0xc049db84
[   33.574188] Vector: 300 (Data Access) at [eeb13c20]
[   33.579086] pc: c049db84: radeon_audio_enable+0x4/0x18
[   33.584630] lr: c049e2f4: radeon_audio_detect+0x288/0x290
[   33.590429] sp: eeb13cd0
[   33.593310]msr: 29000
[   33.595931]dar: 8
[   33.598207]  dsisr: 0
[   33.600480]   current = 0xeea93ac0
[   33.603885] pid   = 2311, comm = Xorg
[   33.607922] enter ? for help
[   33.610806] [link register   ] c049e2f4 
radeon_audio_detect+0x288/0x290
[   33.617469] [eeb13cd0] c049e254 radeon_audio_detect+0x1e8/0x290 
(unreliable)

[   33.624571] [eeb13d00] c03dfe7c radeon_dvi_detect+0x388/0x3ac
[   33.630369] [eeb13d30] c038b9d4 
drm_helper_probe_single_connector_modes_merge_bits+0xf4/0x434

[   33.638954] [eeb13d70] c03a7670 drm_mode_getconnector+0xf4/0x334
[   33.645022] [eeb13e10] c039a8c0 drm_ioctl+0x348/0x464
[   33.650135] [eeb13ed0] c00d0ca0 do_vfs_ioctl+0x52c/0x6e8
[   33.655507] [eeb13f20] c00d0e9c SyS_ioctl+0x40/0x68
[   33.660438] [eeb13f40] c000ab04 ret_from_syscall+0x0/0x3c
[   33.665896] --- Exception: c01 (System Call) at 6fb1b8dc
[   33.671253] SP (bfa56d20) is in userspace
[   33.675263] mon  no input ...
This just looks like a missing NULL check in the radeon code. 
Probably here:


void radeon_audio_detect(struct drm_connector *connector,
enum drm_connector_status status)
{
struct radeon_device *rdev;
struct radeon_encoder *radeon_encoder;
struct radeon_encoder_atom_dig *dig;

if (!connector || !connector-encoder)
return;

rdev = connector-encoder-dev-dev_private;
   ^

So you could try adding !connector-encoder-dev to the if there.

cheers




Thanks.

Results in the following .
[3.179934] [drm] Radeon Display Connectors
[3.184711] [drm] Connector 0:
[3.187827] [drm]   DP-1
[3.190443] [drm]   HPD1
[3.193018] [drm]   DDC: 0x6470 0x6470 0x6474 0x6474 0x6478 0x6478 
0x647c 0x6 47c

[3.200502] [drm]   Encoders:
[3.203510] [drm] DFP1: INTERNAL_UNIPHY2
[3.207823] [drm] Connector 1:
[3.210923] [drm]   HDMI-A-1
[3.213831] [drm]   HPD5
[3.216381] [drm]   DDC: 0x6480 0x6480 0x6484 0x6484 0x6488 0x6488 
0x648c 0x6 48c

[3.223809] [drm]   Encoders:
[3.226795] [drm] DFP2: INTERNAL_UNIPHY2
[3.231083] [drm] Connector 2:
[3.234155] [drm]   DVI-I-1
[3.236968] [drm]   HPD4
[3.239523] [drm]   DDC: 0x6450 0x6450 0x6454 0x6454 0x6458 0x6458 
0x645c 0x6 45c

[3.246942] [drm]   Encoders:
[3.249929] [drm] DFP3: INTERNAL_UNIPHY
[3.254130] [drm] CRT1: INTERNAL_KLDSCP_DAC1
[3.262872] Unable to handle kernel paging request for data at 
address 0x

[3.270407] Faulting instruction address: 0xc04a4280
[3.275394] Vector: 300 (Data Access) at [ea847b20]
[3.280286] pc: c04a4280: radeon_audio_detect+0x1c/0x290
[3.286016] lr: c03e6170: radeon_dp_detect+0x218/0x224
[3.291563] sp: ea847bd0
[3.294453]msr: 29000
[3.297084]dar: 0
[3.299366]  dsisr: 0
[3.301649]   current = 0xea85
[3.305062] pid   = 1, comm = swapper
[3.309101] enter ? for help
[3.311994] [ea847c00] c03e6170 radeon_dp_detect+0x218/0x224
[3.317709] [ea847c20] c039160c 
drm_helper_probe_single_connector_modes_merge _bits+0xf4/0x434
[3.326303] [ea847c60] c0398d68 
drm_fb_helper_probe_connector_modes+0x5c/0x70
[3.333499] [ea847c80] c039ad40 
drm_fb_helper_initial_config+0x38/0x380

[3.340174] [ea847cc0] c03f1848 radeon_fbdev_init+0xc8/0xfc
[3.345808] [ea847ce0] c03eb1cc radeon_modeset_init+0x77c/0x94c
[3.351781] [ea847d40] c03c72fc radeon_driver_load_kms+0xcc/0x134
[3.357935] [ea847d60] c03a3cfc drm_dev_register+0x9c/0x120
[3.363569] [ea847d80] c03a6538 drm_get_pci_dev+0xf4/0x190
[3.369116] [ea847da0] c033d194 pci_device_probe+0x68/0xb4
[3.374680] [ea847dc0] c04b8a4c driver_probe_device+0xd4/0x1f4
[3.380583] [ea847df0] c04b8c48 __driver_attach+0x78/0xa0
[3.386034] [ea847e10] c04b6fd8 bus_for_each_dev+0x8c/0x9c
[3.391572] [ea847e40] c04b81a8 bus_add_driver+0xf8/0x1d4
[3.397024] [ea847e60] c04b90fc driver_register+0xb4/0xf8
[3.402475] [ea847e80] c00016f0 do_one_initcall+0x114/0x19c
[3.408109] [ea847ef0] c0992a8c kernel_init_freeable+0x124/0x1c0
[3.414176] [ea847f30] c0001cc0 kernel_init+0x14/0xf4
[3.419280] [ea847f40] c000ac5c ret_from_kernel_thread+0x5c/0x64
[3.425347] mon  no input ...
[5.428725] Oops: Kernel access of bad area

Re: Problems with Kernels 3.17-rc1 and onwards on Acube Sam460 AMCC 460ex board

2015-03-05 Thread Julian Margetson

On 3/4/2015 7:52 PM, Michael Ellerman wrote:

On Wed, 2015-03-04 at 07:46 -0400, Julian Margetson wrote:

Still stuck.
Problem still exist with 4.0.0-rc2 and I cant finish the bisect.
Triggered when using HDMI. No problem when using DVI.
[   33.535692] Unable to handle kernel paging request for data at address 
0x0008
[   33.566786] Faulting instruction address: 0xc049db84
[   33.574188] Vector: 300 (Data Access) at [eeb13c20]
[   33.579086] pc: c049db84: radeon_audio_enable+0x4/0x18
[   33.584630] lr: c049e2f4: radeon_audio_detect+0x288/0x290
[   33.590429] sp: eeb13cd0
[   33.593310]msr: 29000
[   33.595931]dar: 8
[   33.598207]  dsisr: 0
[   33.600480]   current = 0xeea93ac0
[   33.603885] pid   = 2311, comm = Xorg
[   33.607922] enter ? for help
[   33.610806] [link register   ] c049e2f4 radeon_audio_detect+0x288/0x290
[   33.617469] [eeb13cd0] c049e254 radeon_audio_detect+0x1e8/0x290 (unreliable)
[   33.624571] [eeb13d00] c03dfe7c radeon_dvi_detect+0x388/0x3ac
[   33.630369] [eeb13d30] c038b9d4 
drm_helper_probe_single_connector_modes_merge_bits+0xf4/0x434
[   33.638954] [eeb13d70] c03a7670 drm_mode_getconnector+0xf4/0x334
[   33.645022] [eeb13e10] c039a8c0 drm_ioctl+0x348/0x464
[   33.650135] [eeb13ed0] c00d0ca0 do_vfs_ioctl+0x52c/0x6e8
[   33.655507] [eeb13f20] c00d0e9c SyS_ioctl+0x40/0x68
[   33.660438] [eeb13f40] c000ab04 ret_from_syscall+0x0/0x3c
[   33.665896] --- Exception: c01 (System Call) at 6fb1b8dc
[   33.671253] SP (bfa56d20) is in userspace
[   33.675263] mon  no input ...

This just looks like a missing NULL check in the radeon code. Probably here:

void radeon_audio_detect(struct drm_connector *connector,
enum drm_connector_status status)
{
struct radeon_device *rdev;
struct radeon_encoder *radeon_encoder;
struct radeon_encoder_atom_dig *dig;

if (!connector || !connector-encoder)
return;

rdev = connector-encoder-dev-dev_private;
   ^

So you could try adding !connector-encoder-dev to the if there.

cheers




Thanks.

Results in the following .
[3.179934] [drm] Radeon Display Connectors
[3.184711] [drm] Connector 0:
[3.187827] [drm]   DP-1
[3.190443] [drm]   HPD1
[3.193018] [drm]   DDC: 0x6470 0x6470 0x6474 0x6474 0x6478 0x6478 
0x647c 0x6 47c

[3.200502] [drm]   Encoders:
[3.203510] [drm] DFP1: INTERNAL_UNIPHY2
[3.207823] [drm] Connector 1:
[3.210923] [drm]   HDMI-A-1
[3.213831] [drm]   HPD5
[3.216381] [drm]   DDC: 0x6480 0x6480 0x6484 0x6484 0x6488 0x6488 
0x648c 0x6 48c

[3.223809] [drm]   Encoders:
[3.226795] [drm] DFP2: INTERNAL_UNIPHY2
[3.231083] [drm] Connector 2:
[3.234155] [drm]   DVI-I-1
[3.236968] [drm]   HPD4
[3.239523] [drm]   DDC: 0x6450 0x6450 0x6454 0x6454 0x6458 0x6458 
0x645c 0x6 45c

[3.246942] [drm]   Encoders:
[3.249929] [drm] DFP3: INTERNAL_UNIPHY
[3.254130] [drm] CRT1: INTERNAL_KLDSCP_DAC1
[3.262872] Unable to handle kernel paging request for data at 
address 0x

[3.270407] Faulting instruction address: 0xc04a4280
[3.275394] Vector: 300 (Data Access) at [ea847b20]
[3.280286] pc: c04a4280: radeon_audio_detect+0x1c/0x290
[3.286016] lr: c03e6170: radeon_dp_detect+0x218/0x224
[3.291563] sp: ea847bd0
[3.294453]msr: 29000
[3.297084]dar: 0
[3.299366]  dsisr: 0
[3.301649]   current = 0xea85
[3.305062] pid   = 1, comm = swapper
[3.309101] enter ? for help
[3.311994] [ea847c00] c03e6170 radeon_dp_detect+0x218/0x224
[3.317709] [ea847c20] c039160c 
drm_helper_probe_single_connector_modes_merge _bits+0xf4/0x434
[3.326303] [ea847c60] c0398d68 
drm_fb_helper_probe_connector_modes+0x5c/0x70

[3.333499] [ea847c80] c039ad40 drm_fb_helper_initial_config+0x38/0x380
[3.340174] [ea847cc0] c03f1848 radeon_fbdev_init+0xc8/0xfc
[3.345808] [ea847ce0] c03eb1cc radeon_modeset_init+0x77c/0x94c
[3.351781] [ea847d40] c03c72fc radeon_driver_load_kms+0xcc/0x134
[3.357935] [ea847d60] c03a3cfc drm_dev_register+0x9c/0x120
[3.363569] [ea847d80] c03a6538 drm_get_pci_dev+0xf4/0x190
[3.369116] [ea847da0] c033d194 pci_device_probe+0x68/0xb4
[3.374680] [ea847dc0] c04b8a4c driver_probe_device+0xd4/0x1f4
[3.380583] [ea847df0] c04b8c48 __driver_attach+0x78/0xa0
[3.386034] [ea847e10] c04b6fd8 bus_for_each_dev+0x8c/0x9c
[3.391572] [ea847e40] c04b81a8 bus_add_driver+0xf8/0x1d4
[3.397024] [ea847e60] c04b90fc driver_register+0xb4/0xf8
[3.402475] [ea847e80] c00016f0 do_one_initcall+0x114/0x19c
[3.408109] [ea847ef0] c0992a8c kernel_init_freeable+0x124/0x1c0
[3.414176] [ea847f30] c0001cc0 kernel_init+0x14/0xf4
[3.419280] [ea847f40] c000ac5c ret_from_kernel_thread+0x5c/0x64
[3.425347] mon  no input ...
[5.428725] Oops: Kernel access of bad area, sig: 11 [#1

Re: Problems with Kernels 3.17-rc1 and onwards on Acube Sam460 AMCC 460ex board

2015-03-04 Thread Julian Margetson

Still stuck.
Problem still exist with 4.0.0-rc2 and I cant finish the bisect.
Triggered when using HDMI. No problem when using DVI.

[   33.535692] Unable to handle kernel paging request for data at address 
0x0008
[   33.566786] Faulting instruction address: 0xc049db84
[   33.574188] Vector: 300 (Data Access) at [eeb13c20]
[   33.579086] pc: c049db84: radeon_audio_enable+0x4/0x18
[   33.584630] lr: c049e2f4: radeon_audio_detect+0x288/0x290
[   33.590429] sp: eeb13cd0
[   33.593310]msr: 29000
[   33.595931]dar: 8
[   33.598207]  dsisr: 0
[   33.600480]   current = 0xeea93ac0
[   33.603885] pid   = 2311, comm = Xorg
[   33.607922] enter ? for help
[   33.610806] [link register   ] c049e2f4 radeon_audio_detect+0x288/0x290
[   33.617469] [eeb13cd0] c049e254 radeon_audio_detect+0x1e8/0x290 (unreliable)
[   33.624571] [eeb13d00] c03dfe7c radeon_dvi_detect+0x388/0x3ac
[   33.630369] [eeb13d30] c038b9d4 
drm_helper_probe_single_connector_modes_merge_bits+0xf4/0x434
[   33.638954] [eeb13d70] c03a7670 drm_mode_getconnector+0xf4/0x334
[   33.645022] [eeb13e10] c039a8c0 drm_ioctl+0x348/0x464
[   33.650135] [eeb13ed0] c00d0ca0 do_vfs_ioctl+0x52c/0x6e8
[   33.655507] [eeb13f20] c00d0e9c SyS_ioctl+0x40/0x68
[   33.660438] [eeb13f40] c000ab04 ret_from_syscall+0x0/0x3c
[   33.665896] --- Exception: c01 (System Call) at 6fb1b8dc
[   33.671253] SP (bfa56d20) is in userspace
[   33.675263] mon  no input ...
[   35.703835] Oops: Kernel access of bad area, sig: 11 [#1]
[   35.709554] PREEMPT Canyonlands
[   35.712876] Modules linked in: cfg80211 snd_ice1724 snd_hda_codec_hdmi 
snd_ak4113 snd_pt2258 snd_ak4114 snd_i2c snd_ice17xx_ak4xxx snd_ak4xxx_adda 
snd_ac97_codec snd_hda_intel ac97_bus snd_hda_controller snd_rawmidi 
snd_hda_codec snd_seq_device snd_pcm snd_timer snd
[   35.738047] CPU: 0 PID: 2311 Comm: Xorg Not tainted 4.0.0-rc1-Sam460ex #1
[   35.745189] task: eea93ac0 ti: eeb12000 task.ti: eeb12000
[   35.750872] NIP: c049db84 LR: c049e2f4 CTR: 
[   35.756098] REGS: eeb13c20 TRAP: 0300   Not tainted  (4.0.0-rc1-Sam460ex)
[   35.763241] MSR: 00029000 CE,EE,ME  CR: 24004422  XER: 2000
[   35.769778] DEAR: 0008 ESR: 
GPR00: c049e254 eeb13cd0 eea93ac0 eaa84000  000f ee0532c0 000190d6
GPR08: eab6da00   eeb13cb0 28004422 b7a11ff4 b7a87a98 b7a87988
GPR16:    eeb13e18 eaa08194 eaa08178 0001 4000
GPR24: 4000 c071cd28 fff2  eab6c000 eaa84000 eab6da00 eab80400
[   35.804302] NIP [c049db84] radeon_audio_enable+0x4/0x18
[   35.809799] LR [c049e2f4] radeon_audio_detect+0x288/0x290
[   35.815480] Call Trace:
[   35.818053] [eeb13cd0] [c049e254] radeon_audio_detect+0x1e8/0x290 
(unreliable)
[   35.825694] [eeb13d00] [c03dfe7c] radeon_dvi_detect+0x388/0x3ac
[   35.831956] [eeb13d30] [c038b9d4] 
drm_helper_probe_single_connector_modes_merge_bits+0xf4/0x434
[   35.841137] [eeb13d70] [c03a7670] drm_mode_getconnector+0xf4/0x334
[   35.847663] [eeb13e10] [c039a8c0] drm_ioctl+0x348/0x464
[   35.853183] [eeb13ed0] [c00d0ca0] do_vfs_ioctl+0x52c/0x6e8
[   35.858974] [eeb13f20] [c00d0e9c] SyS_ioctl+0x40/0x68
[   35.864307] [eeb13f40] [c000ab04] ret_from_syscall+0x0/0x3c
[   35.870196] --- interrupt: c01 at 0x6fb1b8dc
[   35.870196] LR = 0x6fb1b800
[   35.877971] Instruction dump:
[   35.881106] 8129012c 806a0018 2f89 419e0018 81290004 2f89 419e000c 
7d2903a6




On 2/24/2015 4:26 PM, Julian Margetson wrote:

Thanks

after skipping several times :

git bisect skip

There are only 'skip'ped commits left to test.
The first bad commit could be any of:
b486e0e6d599b9ca8667fb9a7d49b7383ee963c7
eab3bbeffd152125ae0f90863b8e9bc8eef49423
960cd9d4fef6dd9e235c0e5c0d4ed027f8a48025
f02ad907cd9e7fe3a6405d2d005840912f1ed258
6a425c2a9b37ca3d2c37e3c1cdf973dba53eaa79
ee0a89cf3c2c550e6d877dda21dd2947afb90cb6
92890583627ee2a0518e55b063fcff86826fef96
95d6eb3b134e1826ed04cc92b224d93de13e281f
9469244d869623e8b54d9f3d4d00737e377af273
We cannot bisect more!



On 2/24/2015 3:14 PM, Gerhard Pircher wrote:

Am 2015-02-24 um 12:08 schrieb Julian Margetson:

Problems with  the Gib bisect
Kernel wont compile after 10th bisect .

You can try git bisect skip to select another commit for testing.
Hopefully that one compiles fine then.

Gerhard


drivers/built-in.o: In function `drm_mode_atomic_ioctl':
(.text+0x865dc): undefined reference to `__get_user_bad'
make: *** [vmlinux] Error 1
root@julian-VirtualBox:/usr/src/linux# git bisect log
git bisect start
# bad: [c517d838eb7d07bbe9507871fab3931deccff539] Linux 4.0-rc1
git bisect bad c517d838eb7d07bbe9507871fab3931deccff539
# good: [bfa76d49576599a4b9f9b7a71f23d73d6dcff735] Linux 3.19
git bisect good bfa76d49576599a4b9f9b7a71f23d73d6dcff735
# good: [02f1f2170d2831b3233e91091c60a66622f29e82] kernel.h: remove ancient 
__FUNCTION__ hack
git bisect good 02f1f2170d2831b3233e91091c60a66622f29e82
# bad: [796e1c55717e9a6ff5c81b12289ffa1ffd919b6f] Merge branch 'drm-next' of 
git

Re: Problems with Kernels 3.17-rc1 and onwards on Acube Sam460 AMCC 460ex board

2015-02-25 Thread Julian Margetson

Problem also seems to exist with P1022 based board as well .
https://community.freescale.com/thread/339022

On 2/25/2015 9:26 AM, Julian Margetson wrote:

Verified that the problems with the
radeon: ring 0 test failed error
go back to at least  Kernel 3.0.1

On 2/24/2015 4:26 PM, Julian Margetson wrote:

Thanks

after skipping several times :

git bisect skip

There are only 'skip'ped commits left to test.
The first bad commit could be any of:
b486e0e6d599b9ca8667fb9a7d49b7383ee963c7
eab3bbeffd152125ae0f90863b8e9bc8eef49423
960cd9d4fef6dd9e235c0e5c0d4ed027f8a48025
f02ad907cd9e7fe3a6405d2d005840912f1ed258
6a425c2a9b37ca3d2c37e3c1cdf973dba53eaa79
ee0a89cf3c2c550e6d877dda21dd2947afb90cb6
92890583627ee2a0518e55b063fcff86826fef96
95d6eb3b134e1826ed04cc92b224d93de13e281f
9469244d869623e8b54d9f3d4d00737e377af273
We cannot bisect more!



On 2/24/2015 3:14 PM, Gerhard Pircher wrote:

Am 2015-02-24 um 12:08 schrieb Julian Margetson:

Problems with  the Gib bisect
Kernel wont compile after 10th bisect .

You can try git bisect skip to select another commit for testing.
Hopefully that one compiles fine then.

Gerhard


drivers/built-in.o: In function `drm_mode_atomic_ioctl':
(.text+0x865dc): undefined reference to `__get_user_bad'
make: *** [vmlinux] Error 1
root@julian-VirtualBox:/usr/src/linux# git bisect log
git bisect start
# bad: [c517d838eb7d07bbe9507871fab3931deccff539] Linux 4.0-rc1
git bisect bad c517d838eb7d07bbe9507871fab3931deccff539
# good: [bfa76d49576599a4b9f9b7a71f23d73d6dcff735] Linux 3.19
git bisect good bfa76d49576599a4b9f9b7a71f23d73d6dcff735
# good: [02f1f2170d2831b3233e91091c60a66622f29e82] kernel.h: remove ancient 
__FUNCTION__ hack
git bisect good 02f1f2170d2831b3233e91091c60a66622f29e82
# bad: [796e1c55717e9a6ff5c81b12289ffa1ffd919b6f] Merge branch 'drm-next' of 
git://people.freedesktop.org/~airlied/linux
git bisect bad 796e1c55717e9a6ff5c81b12289ffa1ffd919b6f
# good: [9682ec9692e5ac11c6caebd079324e727b19e7ce] Merge tag 
'driver-core-3.20-rc1' of 
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core
git bisect good 9682ec9692e5ac11c6caebd079324e727b19e7ce
# good: [a9724125ad014decf008d782e60447c811391326] Merge tag 'tty-3.20-rc1' of 
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty
git bisect good a9724125ad014decf008d782e60447c811391326
# good: [f43dff0ee00a259f524ce17ba4f8030553c66590] Merge tag 
'drm-amdkfd-next-fixes-2015-01-25' of 
git://people.freedesktop.org/~gabbayo/linux into drm-next
git bisect good f43dff0ee00a259f524ce17ba4f8030553c66590
# bad: [cffe1e89dc9bf541a39d9287ced7c5addff07084] drm: sti: HDMI add audio 
infoframe
git bisect bad cffe1e89dc9bf541a39d9287ced7c5addff07084
# good: [2f5b4ef15c60bc5292a3f006c018acb3da53737b] Merge tag 
'drm/tegra/for-3.20-rc1' of git://anongit.freedesktop.org/tegra/linux into 
drm-next
git bisect good 2f5b4ef15c60bc5292a3f006c018acb3da53737b
# bad: [86588ce80ccd714793e9ba4140d7ae214229] drm/udl: optimize 
udl_compress_hline16 (v2)
git bisect bad 86588ce80ccd714793e9ba4140d7ae214229
# bad: [d47df63393ed81977e0f6435988d9cbd70c867f7] drm/panel: simple: Add AVIC 
TM070DDH03 panel support
git bisect bad d47df63393ed81977e0f6435988d9cbd70c867f7
# bad: [9469244d869623e8b54d9f3d4d00737e377af273] drm/atomic: Fix potential use 
of state after free
git bisect bad 9469244d869623e8b54d9f3d4d00737e377af273
root@julian-VirtualBox:/usr/src/linux#



On 02/24/2015, you wrote:


On Fri, 2015-02-20 at 15:25 -0400, Julian Margetson wrote:

On 2/18/2015 11:25 PM, Julian Margetson wrote:
  re PPC4XX PCI(E) MSI support.
https://lists.ozlabs.org/pipermail/linuxppc-dev/2010-November/087273.html

Hmm, I think all those comments were addressed before it was merged.

I tried to get a 4xx board going here last week, but it doesn't seem happy. I
can get a bit of uboot but then it hangs, might be overheating.

cheers



___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev







___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev

Re: Problems with Kernels 3.17-rc1 and onwards on Acube Sam460 AMCC 460ex board

2015-02-25 Thread Julian Margetson

Verified that the problems with the

radeon: ring 0 test failed error

go back to at least  Kernel 3.0.1

On 2/24/2015 4:26 PM, Julian Margetson wrote:

Thanks

after skipping several times :

git bisect skip

There are only 'skip'ped commits left to test.
The first bad commit could be any of:
b486e0e6d599b9ca8667fb9a7d49b7383ee963c7
eab3bbeffd152125ae0f90863b8e9bc8eef49423
960cd9d4fef6dd9e235c0e5c0d4ed027f8a48025
f02ad907cd9e7fe3a6405d2d005840912f1ed258
6a425c2a9b37ca3d2c37e3c1cdf973dba53eaa79
ee0a89cf3c2c550e6d877dda21dd2947afb90cb6
92890583627ee2a0518e55b063fcff86826fef96
95d6eb3b134e1826ed04cc92b224d93de13e281f
9469244d869623e8b54d9f3d4d00737e377af273
We cannot bisect more!



On 2/24/2015 3:14 PM, Gerhard Pircher wrote:

Am 2015-02-24 um 12:08 schrieb Julian Margetson:

Problems with  the Gib bisect
Kernel wont compile after 10th bisect .

You can try git bisect skip to select another commit for testing.
Hopefully that one compiles fine then.

Gerhard


drivers/built-in.o: In function `drm_mode_atomic_ioctl':
(.text+0x865dc): undefined reference to `__get_user_bad'
make: *** [vmlinux] Error 1
root@julian-VirtualBox:/usr/src/linux# git bisect log
git bisect start
# bad: [c517d838eb7d07bbe9507871fab3931deccff539] Linux 4.0-rc1
git bisect bad c517d838eb7d07bbe9507871fab3931deccff539
# good: [bfa76d49576599a4b9f9b7a71f23d73d6dcff735] Linux 3.19
git bisect good bfa76d49576599a4b9f9b7a71f23d73d6dcff735
# good: [02f1f2170d2831b3233e91091c60a66622f29e82] kernel.h: remove ancient 
__FUNCTION__ hack
git bisect good 02f1f2170d2831b3233e91091c60a66622f29e82
# bad: [796e1c55717e9a6ff5c81b12289ffa1ffd919b6f] Merge branch 'drm-next' of 
git://people.freedesktop.org/~airlied/linux
git bisect bad 796e1c55717e9a6ff5c81b12289ffa1ffd919b6f
# good: [9682ec9692e5ac11c6caebd079324e727b19e7ce] Merge tag 
'driver-core-3.20-rc1' of 
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core
git bisect good 9682ec9692e5ac11c6caebd079324e727b19e7ce
# good: [a9724125ad014decf008d782e60447c811391326] Merge tag 'tty-3.20-rc1' of 
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty
git bisect good a9724125ad014decf008d782e60447c811391326
# good: [f43dff0ee00a259f524ce17ba4f8030553c66590] Merge tag 
'drm-amdkfd-next-fixes-2015-01-25' of 
git://people.freedesktop.org/~gabbayo/linux into drm-next
git bisect good f43dff0ee00a259f524ce17ba4f8030553c66590
# bad: [cffe1e89dc9bf541a39d9287ced7c5addff07084] drm: sti: HDMI add audio 
infoframe
git bisect bad cffe1e89dc9bf541a39d9287ced7c5addff07084
# good: [2f5b4ef15c60bc5292a3f006c018acb3da53737b] Merge tag 
'drm/tegra/for-3.20-rc1' of git://anongit.freedesktop.org/tegra/linux into 
drm-next
git bisect good 2f5b4ef15c60bc5292a3f006c018acb3da53737b
# bad: [86588ce80ccd714793e9ba4140d7ae214229] drm/udl: optimize 
udl_compress_hline16 (v2)
git bisect bad 86588ce80ccd714793e9ba4140d7ae214229
# bad: [d47df63393ed81977e0f6435988d9cbd70c867f7] drm/panel: simple: Add AVIC 
TM070DDH03 panel support
git bisect bad d47df63393ed81977e0f6435988d9cbd70c867f7
# bad: [9469244d869623e8b54d9f3d4d00737e377af273] drm/atomic: Fix potential use 
of state after free
git bisect bad 9469244d869623e8b54d9f3d4d00737e377af273
root@julian-VirtualBox:/usr/src/linux#



On 02/24/2015, you wrote:


On Fri, 2015-02-20 at 15:25 -0400, Julian Margetson wrote:

On 2/18/2015 11:25 PM, Julian Margetson wrote:
  re PPC4XX PCI(E) MSI support.
https://lists.ozlabs.org/pipermail/linuxppc-dev/2010-November/087273.html

Hmm, I think all those comments were addressed before it was merged.

I tried to get a 4xx board going here last week, but it doesn't seem happy. I
can get a bit of uboot but then it hangs, might be overheating.

cheers



___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev





___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev

Re: Problems with Kernels 3.17-rc1 and onwards on Acube Sam460 AMCC 460ex board

2015-02-24 Thread Julian Margetson

Thanks

after skipping several times :

git bisect skip

There are only 'skip'ped commits left to test.
The first bad commit could be any of:
b486e0e6d599b9ca8667fb9a7d49b7383ee963c7
eab3bbeffd152125ae0f90863b8e9bc8eef49423
960cd9d4fef6dd9e235c0e5c0d4ed027f8a48025
f02ad907cd9e7fe3a6405d2d005840912f1ed258
6a425c2a9b37ca3d2c37e3c1cdf973dba53eaa79
ee0a89cf3c2c550e6d877dda21dd2947afb90cb6
92890583627ee2a0518e55b063fcff86826fef96
95d6eb3b134e1826ed04cc92b224d93de13e281f
9469244d869623e8b54d9f3d4d00737e377af273
We cannot bisect more!




On 2/24/2015 3:14 PM, Gerhard Pircher wrote:

Am 2015-02-24 um 12:08 schrieb Julian Margetson:

Problems with  the Gib bisect
Kernel wont compile after 10th bisect .

You can try git bisect skip to select another commit for testing.
Hopefully that one compiles fine then.

Gerhard


drivers/built-in.o: In function `drm_mode_atomic_ioctl':
(.text+0x865dc): undefined reference to `__get_user_bad'
make: *** [vmlinux] Error 1
root@julian-VirtualBox:/usr/src/linux# git bisect log
git bisect start
# bad: [c517d838eb7d07bbe9507871fab3931deccff539] Linux 4.0-rc1
git bisect bad c517d838eb7d07bbe9507871fab3931deccff539
# good: [bfa76d49576599a4b9f9b7a71f23d73d6dcff735] Linux 3.19
git bisect good bfa76d49576599a4b9f9b7a71f23d73d6dcff735
# good: [02f1f2170d2831b3233e91091c60a66622f29e82] kernel.h: remove ancient 
__FUNCTION__ hack
git bisect good 02f1f2170d2831b3233e91091c60a66622f29e82
# bad: [796e1c55717e9a6ff5c81b12289ffa1ffd919b6f] Merge branch 'drm-next' of 
git://people.freedesktop.org/~airlied/linux
git bisect bad 796e1c55717e9a6ff5c81b12289ffa1ffd919b6f
# good: [9682ec9692e5ac11c6caebd079324e727b19e7ce] Merge tag 
'driver-core-3.20-rc1' of 
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core
git bisect good 9682ec9692e5ac11c6caebd079324e727b19e7ce
# good: [a9724125ad014decf008d782e60447c811391326] Merge tag 'tty-3.20-rc1' of 
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty
git bisect good a9724125ad014decf008d782e60447c811391326
# good: [f43dff0ee00a259f524ce17ba4f8030553c66590] Merge tag 
'drm-amdkfd-next-fixes-2015-01-25' of 
git://people.freedesktop.org/~gabbayo/linux into drm-next
git bisect good f43dff0ee00a259f524ce17ba4f8030553c66590
# bad: [cffe1e89dc9bf541a39d9287ced7c5addff07084] drm: sti: HDMI add audio 
infoframe
git bisect bad cffe1e89dc9bf541a39d9287ced7c5addff07084
# good: [2f5b4ef15c60bc5292a3f006c018acb3da53737b] Merge tag 
'drm/tegra/for-3.20-rc1' of git://anongit.freedesktop.org/tegra/linux into 
drm-next
git bisect good 2f5b4ef15c60bc5292a3f006c018acb3da53737b
# bad: [86588ce80ccd714793e9ba4140d7ae214229] drm/udl: optimize 
udl_compress_hline16 (v2)
git bisect bad 86588ce80ccd714793e9ba4140d7ae214229
# bad: [d47df63393ed81977e0f6435988d9cbd70c867f7] drm/panel: simple: Add AVIC 
TM070DDH03 panel support
git bisect bad d47df63393ed81977e0f6435988d9cbd70c867f7
# bad: [9469244d869623e8b54d9f3d4d00737e377af273] drm/atomic: Fix potential use 
of state after free
git bisect bad 9469244d869623e8b54d9f3d4d00737e377af273
root@julian-VirtualBox:/usr/src/linux#



On 02/24/2015, you wrote:


On Fri, 2015-02-20 at 15:25 -0400, Julian Margetson wrote:

On 2/18/2015 11:25 PM, Julian Margetson wrote:
  re PPC4XX PCI(E) MSI support.
https://lists.ozlabs.org/pipermail/linuxppc-dev/2010-November/087273.html

Hmm, I think all those comments were addressed before it was merged.

I tried to get a 4xx board going here last week, but it doesn't seem happy. I
can get a bit of uboot but then it hangs, might be overheating.

cheers




___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev





___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev

Re: Problems with Kernels 3.17-rc1 and onwards on Acube Sam460 AMCC 460ex board

2015-02-24 Thread Julian Margetson
I had  a hanging Uboot problem with a Sam440ep board.Never figured the problem 
out but
It workedd for another two years after the problems began. Died for good last 
September with the hanging becoming  a daily issue.
Dont think that it was overheating. I thought that it could have been a problem 
with  the on board  ethernet.

anyway I am still not giving up hopes of DRI and future kernals working, only 
into my second year of trying so too soon to give up .
Doing a git bisect on the 4.00-rc1 now.

On 02/24/2015, you wrote:

 On Fri, 2015-02-20 at 15:25 -0400, Julian Margetson wrote:
 On 2/18/2015 11:25 PM, Julian Margetson wrote:

  re PPC4XX PCI(E) MSI support.
 https://lists.ozlabs.org/pipermail/linuxppc-dev/2010-November/087273.html

 Hmm, I think all those comments were addressed before it was merged.

 I tried to get a 4xx board going here last week, but it doesn't seem happy. I
 can get a bit of uboot but then it hangs, might be overheating.

 cheers




___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev

Re: Problems with Kernels 3.17-rc1 and onwards on Acube Sam460 AMCC 460ex board

2015-02-24 Thread Julian Margetson
Problems with  the Gib bisect
Kernel wont compile after 10th bisect .

drivers/built-in.o: In function `drm_mode_atomic_ioctl':
(.text+0x865dc): undefined reference to `__get_user_bad'
make: *** [vmlinux] Error 1
root@julian-VirtualBox:/usr/src/linux# git bisect log
git bisect start
# bad: [c517d838eb7d07bbe9507871fab3931deccff539] Linux 4.0-rc1
git bisect bad c517d838eb7d07bbe9507871fab3931deccff539
# good: [bfa76d49576599a4b9f9b7a71f23d73d6dcff735] Linux 3.19
git bisect good bfa76d49576599a4b9f9b7a71f23d73d6dcff735
# good: [02f1f2170d2831b3233e91091c60a66622f29e82] kernel.h: remove ancient 
__FUNCTION__ hack
git bisect good 02f1f2170d2831b3233e91091c60a66622f29e82
# bad: [796e1c55717e9a6ff5c81b12289ffa1ffd919b6f] Merge branch 'drm-next' of 
git://people.freedesktop.org/~airlied/linux
git bisect bad 796e1c55717e9a6ff5c81b12289ffa1ffd919b6f
# good: [9682ec9692e5ac11c6caebd079324e727b19e7ce] Merge tag 
'driver-core-3.20-rc1' of 
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core
git bisect good 9682ec9692e5ac11c6caebd079324e727b19e7ce
# good: [a9724125ad014decf008d782e60447c811391326] Merge tag 'tty-3.20-rc1' of 
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty
git bisect good a9724125ad014decf008d782e60447c811391326
# good: [f43dff0ee00a259f524ce17ba4f8030553c66590] Merge tag 
'drm-amdkfd-next-fixes-2015-01-25' of 
git://people.freedesktop.org/~gabbayo/linux into drm-next
git bisect good f43dff0ee00a259f524ce17ba4f8030553c66590
# bad: [cffe1e89dc9bf541a39d9287ced7c5addff07084] drm: sti: HDMI add audio 
infoframe
git bisect bad cffe1e89dc9bf541a39d9287ced7c5addff07084
# good: [2f5b4ef15c60bc5292a3f006c018acb3da53737b] Merge tag 
'drm/tegra/for-3.20-rc1' of git://anongit.freedesktop.org/tegra/linux into 
drm-next
git bisect good 2f5b4ef15c60bc5292a3f006c018acb3da53737b
# bad: [86588ce80ccd714793e9ba4140d7ae214229] drm/udl: optimize 
udl_compress_hline16 (v2)
git bisect bad 86588ce80ccd714793e9ba4140d7ae214229
# bad: [d47df63393ed81977e0f6435988d9cbd70c867f7] drm/panel: simple: Add AVIC 
TM070DDH03 panel support
git bisect bad d47df63393ed81977e0f6435988d9cbd70c867f7
# bad: [9469244d869623e8b54d9f3d4d00737e377af273] drm/atomic: Fix potential use 
of state after free
git bisect bad 9469244d869623e8b54d9f3d4d00737e377af273
root@julian-VirtualBox:/usr/src/linux# 



On 02/24/2015, you wrote:

 On Fri, 2015-02-20 at 15:25 -0400, Julian Margetson wrote:
 On 2/18/2015 11:25 PM, Julian Margetson wrote:

  re PPC4XX PCI(E) MSI support.
 https://lists.ozlabs.org/pipermail/linuxppc-dev/2010-November/087273.html

 Hmm, I think all those comments were addressed before it was merged.

 I tried to get a 4xx board going here last week, but it doesn't seem happy. I
 can get a bit of uboot but then it hangs, might be overheating.

 cheers




___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev

Re: Problems with Kernels 3.17-rc1 and onwards on Acube Sam460 AMCC 460ex board

2015-02-24 Thread Julian Margetson

On 2/24/2015 7:10 AM, Julian Margetson wrote:

Problems with  the Gib bisect
Kernel wont compile after 10th bisect .

drivers/built-in.o: In function `drm_mode_atomic_ioctl':
(.text+0x865dc): undefined reference to `__get_user_bad'
make: *** [vmlinux] Error 1
root@julian-VirtualBox:/usr/src/linux# git bisect log
git bisect start
# bad: [c517d838eb7d07bbe9507871fab3931deccff539] Linux 4.0-rc1
git bisect bad c517d838eb7d07bbe9507871fab3931deccff539
# good: [bfa76d49576599a4b9f9b7a71f23d73d6dcff735] Linux 3.19
git bisect good bfa76d49576599a4b9f9b7a71f23d73d6dcff735
# good: [02f1f2170d2831b3233e91091c60a66622f29e82] kernel.h: remove ancient 
__FUNCTION__ hack
git bisect good 02f1f2170d2831b3233e91091c60a66622f29e82
# bad: [796e1c55717e9a6ff5c81b12289ffa1ffd919b6f] Merge branch 'drm-next' of 
git://people.freedesktop.org/~airlied/linux
git bisect bad 796e1c55717e9a6ff5c81b12289ffa1ffd919b6f
# good: [9682ec9692e5ac11c6caebd079324e727b19e7ce] Merge tag 
'driver-core-3.20-rc1' of 
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core
git bisect good 9682ec9692e5ac11c6caebd079324e727b19e7ce
# good: [a9724125ad014decf008d782e60447c811391326] Merge tag 'tty-3.20-rc1' of 
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty
git bisect good a9724125ad014decf008d782e60447c811391326
# good: [f43dff0ee00a259f524ce17ba4f8030553c66590] Merge tag 
'drm-amdkfd-next-fixes-2015-01-25' of 
git://people.freedesktop.org/~gabbayo/linux into drm-next
git bisect good f43dff0ee00a259f524ce17ba4f8030553c66590
# bad: [cffe1e89dc9bf541a39d9287ced7c5addff07084] drm: sti: HDMI add audio 
infoframe
git bisect bad cffe1e89dc9bf541a39d9287ced7c5addff07084
# good: [2f5b4ef15c60bc5292a3f006c018acb3da53737b] Merge tag 
'drm/tegra/for-3.20-rc1' of git://anongit.freedesktop.org/tegra/linux into 
drm-next
git bisect good 2f5b4ef15c60bc5292a3f006c018acb3da53737b
# bad: [86588ce80ccd714793e9ba4140d7ae214229] drm/udl: optimize 
udl_compress_hline16 (v2)
git bisect bad 86588ce80ccd714793e9ba4140d7ae214229
# bad: [d47df63393ed81977e0f6435988d9cbd70c867f7] drm/panel: simple: Add AVIC 
TM070DDH03 panel support
git bisect bad d47df63393ed81977e0f6435988d9cbd70c867f7
# bad: [9469244d869623e8b54d9f3d4d00737e377af273] drm/atomic: Fix potential use 
of state after free
git bisect bad 9469244d869623e8b54d9f3d4d00737e377af273
root@julian-VirtualBox:/usr/src/linux#



On 02/24/2015, you wrote:


On Fri, 2015-02-20 at 15:25 -0400, Julian Margetson wrote:

On 2/18/2015 11:25 PM, Julian Margetson wrote:
  re PPC4XX PCI(E) MSI support.
https://lists.ozlabs.org/pipermail/linuxppc-dev/2010-November/087273.html

Hmm, I think all those comments were addressed before it was merged.

I tried to get a 4xx board going here last week, but it doesn't seem happy. I
can get a bit of uboot but then it hangs, might be overheating.

cheers



Kernel 4.0.0-rc1 boots ok when  DVI output used but not when HDMI output 
used.

___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev

Re: Problems with DRI on Acube Sam460 AMCC 460ex board

2015-02-23 Thread Julian Margetson

On 2/23/2015 9:03 AM, Julian Margetson wrote:

On 2/18/2015 10:56 PM, Michael Ellerman wrote:

On Wed, 2015-02-18 at 21:36 -0400, Julian Margetson wrote:

On 2/18/2015 8:13 PM, Michael Ellerman wrote:


On Wed, 2015-02-18 at 15:45 -0400, Julian Margetson wrote:

On 2/15/2015 8:18 PM, Michael Ellerman wrote:


On Sun, 2015-02-15 at 08:16 -0400, Julian Margetson wrote:

Hi

I am unable to get any kernel beyond  the 3.16 branch working on an
Acube Sam460ex
  AMCC 460ex based motherboard. Kernel  up 3.16.7-ckt6 working.

Does reverting b0345bbc6d09 change anything?


[6.364350] snd_hda_intel 0001:81:00.1: enabling device ( - 0002)
[6.453794] snd_hda_intel 0001:81:00.1: ppc4xx_setup_msi_irqs: fail mapping 
irq
[6.487530] Unable to handle kernel paging request for data at address 
0x0fa06c7c
[6.495055] Faulting instruction address: 0xc032202c
[6.500033] Vector: 300 (Data Access) at [efa31cf0]
[6.504922] pc: c032202c: __reg_op+0xe8/0x100
[6.509697] lr: c0014f88: msi_bitmap_free_hwirqs+0x50/0x94
[6.515600] sp: efa31da0
[6.518491]msr: 21000
[6.521112]dar: fa06c7c
[6.523915]  dsisr: 0
[6.526190]   current = 0xef8bab00
[6.529603] pid   = 115, comm = kworker/0:1
[6.534163] enter ? for help
[6.537054] [link register   ] c0014f88 msi_bitmap_free_hwirqs+0x50/0x94
[6.543811] [efa31da0] c0014f78 msi_bitmap_free_hwirqs+0x40/0x94 (unreliable)
[6.551001] [efa31dc0] c001aee8 ppc4xx_setup_msi_irqs+0xac/0xf4
[6.556973] [efa31e00] c03503a4 pci_enable_msi_range+0x1e0/0x280
[6.563032] [efa31e40] f92c2f74 azx_probe_work+0xe0/0x57c [snd_hda_intel]
[6.569906] [efa31e80] c0036344 process_one_work+0x1e8/0x2f0
[6.575627] [efa31eb0] c003677c worker_thread+0x2f4/0x438
[6.581079] [efa31ef0] c003a3e4 kthread+0xc8/0xcc
[6.585844] [efa31f40] c000aec4 ret_from_kernel_thread+0x5c/0x64
[6.591910] mon  no input ...

Managed to do a third git bisect  with the following results .

Great work.


git bisect bad
9279d3286e10736766edcaf815ae10e00856e448 is the first bad commit
commit 9279d3286e10736766edcaf815ae10e00856e448
Author: Rasmus Villemoesli...@rasmusvillemoes.dk
Date:   Wed Aug 6 16:10:16 2014 -0700

 lib: bitmap: change parameter of bitmap_*_region to unsigned

So the bug is in the 4xx MSI code, and has always been there, in fact I don't
see how that code has *ever* worked. The commit you bisected to just caused the
existing bug to cause an oops.

Can you try this?

diff --git a/arch/powerpc/sysdev/ppc4xx_msi.c b/arch/powerpc/sysdev/ppc4xx_msi.c
index 6e2e6aa378bb..effb5b878a78 100644
--- a/arch/powerpc/sysdev/ppc4xx_msi.c
+++ b/arch/powerpc/sysdev/ppc4xx_msi.c
@@ -95,11 +95,9 @@ static int ppc4xx_setup_msi_irqs(struct pci_dev *dev, int 
nvec, int type)
  
  	list_for_each_entry(entry, dev-msi_list, list) {

int_no = msi_bitmap_alloc_hwirqs(msi_data-bitmap, 1);
-   if (int_no = 0)
-   break;
if (int_no  0) {
-   pr_debug(%s: fail allocating msi interrupt\n,
-   __func__);
+   pr_warn(%s: fail allocating msi interrupt\n, 
__func__);
+   return -ENOSPC;
}
virq = irq_of_parse_and_map(msi_data-msi_dev, int_no);
if (virq == NO_IRQ) {


Thanks.
This works with 3.17-rc1. Will try with the 3.18 Branch .

OK great.


Any ideas why drm is not  working ? (It never worked) .

No sorry. You might have more luck if you post a new thread to the dri list.


[5.809802] Linux agpgart interface v0.103
[6.137893] [drm] Initialized drm 1.1.0 20060810
[6.439872] snd_hda_intel 0001:81:00.1: enabling device ( - 0002)
[6.508544] ppc4xx_setup_msi_irqs: fail allocating msi interrupt

I'm curious why it's failing to allocate MSIs. Possibly it's just run out.

Can you post the output of 'cat /proc/interrupts'?

cheers






cat /proc/interrupts
CPU0
  18:  0   UIC  11 Edge  L2C
  19:  0   UIC  12 Level snd_ice1724
  20:  1   UIC  16 Level
  21:306   UIC  17 Level snd_hda_intel
  22:  12212   UIC   0 Level 0002:00:04.0
  25:619   UIC   6 Level MAL TX EOB
  26:937   UIC   7 Level MAL RX EOB
  27:  0   UIC   3 Level MAL SERR
  28:  0   UIC   4 Level MAL TX DE
  31:  0   UIC   5 Level MAL RX DE
  32:   6607   UIC  29 Level ehci_hcd:usb1
  33:  1   UIC  30 Level ohci_hcd:usb2
  38: 19   UIC   2 Level IBM IIC
  39:  0   UIC   3 Level IBM IIC
  40:  0   UIC  16 Level EMAC
  44:  0   UIC   0 Edge  aerdrv
  45:  0   UIC   2 Edge  aerdrv
LOC: 117318   Local timer interrupts for timer event device
LOC: 53   Local timer interrupts for others
SPU

Re: Problems with Kernels 3.17-rc1 and onwards on Acube Sam460 AMCC 460ex board

2015-02-20 Thread Julian Margetson

On 2/18/2015 11:25 PM, Julian Margetson wrote:

On 2/18/2015 10:56 PM, Michael Ellerman wrote:

On Wed, 2015-02-18 at 21:36 -0400, Julian Margetson wrote:

On 2/18/2015 8:13 PM, Michael Ellerman wrote:


On Wed, 2015-02-18 at 15:45 -0400, Julian Margetson wrote:

On 2/15/2015 8:18 PM, Michael Ellerman wrote:


On Sun, 2015-02-15 at 08:16 -0400, Julian Margetson wrote:

Hi

I am unable to get any kernel beyond  the 3.16 branch working on an
Acube Sam460ex
  AMCC 460ex based motherboard. Kernel  up 3.16.7-ckt6 working.

Does reverting b0345bbc6d09 change anything?


[6.364350] snd_hda_intel 0001:81:00.1: enabling device ( - 0002)
[6.453794] snd_hda_intel 0001:81:00.1: ppc4xx_setup_msi_irqs: fail mapping 
irq
[6.487530] Unable to handle kernel paging request for data at address 
0x0fa06c7c
[6.495055] Faulting instruction address: 0xc032202c
[6.500033] Vector: 300 (Data Access) at [efa31cf0]
[6.504922] pc: c032202c: __reg_op+0xe8/0x100
[6.509697] lr: c0014f88: msi_bitmap_free_hwirqs+0x50/0x94
[6.515600] sp: efa31da0
[6.518491]msr: 21000
[6.521112]dar: fa06c7c
[6.523915]  dsisr: 0
[6.526190]   current = 0xef8bab00
[6.529603] pid   = 115, comm = kworker/0:1
[6.534163] enter ? for help
[6.537054] [link register   ] c0014f88 msi_bitmap_free_hwirqs+0x50/0x94
[6.543811] [efa31da0] c0014f78 msi_bitmap_free_hwirqs+0x40/0x94 (unreliable)
[6.551001] [efa31dc0] c001aee8 ppc4xx_setup_msi_irqs+0xac/0xf4
[6.556973] [efa31e00] c03503a4 pci_enable_msi_range+0x1e0/0x280
[6.563032] [efa31e40] f92c2f74 azx_probe_work+0xe0/0x57c [snd_hda_intel]
[6.569906] [efa31e80] c0036344 process_one_work+0x1e8/0x2f0
[6.575627] [efa31eb0] c003677c worker_thread+0x2f4/0x438
[6.581079] [efa31ef0] c003a3e4 kthread+0xc8/0xcc
[6.585844] [efa31f40] c000aec4 ret_from_kernel_thread+0x5c/0x64
[6.591910] mon  no input ...

Managed to do a third git bisect  with the following results .

Great work.


git bisect bad
9279d3286e10736766edcaf815ae10e00856e448 is the first bad commit
commit 9279d3286e10736766edcaf815ae10e00856e448
Author: Rasmus Villemoesli...@rasmusvillemoes.dk
Date:   Wed Aug 6 16:10:16 2014 -0700

 lib: bitmap: change parameter of bitmap_*_region to unsigned

So the bug is in the 4xx MSI code, and has always been there, in fact I don't
see how that code has *ever* worked. The commit you bisected to just caused the
existing bug to cause an oops.

Can you try this?

diff --git a/arch/powerpc/sysdev/ppc4xx_msi.c b/arch/powerpc/sysdev/ppc4xx_msi.c
index 6e2e6aa378bb..effb5b878a78 100644
--- a/arch/powerpc/sysdev/ppc4xx_msi.c
+++ b/arch/powerpc/sysdev/ppc4xx_msi.c
@@ -95,11 +95,9 @@ static int ppc4xx_setup_msi_irqs(struct pci_dev *dev, int 
nvec, int type)
  
  	list_for_each_entry(entry, dev-msi_list, list) {

int_no = msi_bitmap_alloc_hwirqs(msi_data-bitmap, 1);
-   if (int_no = 0)
-   break;
if (int_no  0) {
-   pr_debug(%s: fail allocating msi interrupt\n,
-   __func__);
+   pr_warn(%s: fail allocating msi interrupt\n, 
__func__);
+   return -ENOSPC;
}
virq = irq_of_parse_and_map(msi_data-msi_dev, int_no);
if (virq == NO_IRQ) {


Thanks.
This works with 3.17-rc1. Will try with the 3.18 Branch .

OK great.


Any ideas why drm is not  working ? (It never worked) .

No sorry. You might have more luck if you post a new thread to the dri list.


[5.809802] Linux agpgart interface v0.103
[6.137893] [drm] Initialized drm 1.1.0 20060810
[6.439872] snd_hda_intel 0001:81:00.1: enabling device ( - 0002)
[6.508544] ppc4xx_setup_msi_irqs: fail allocating msi interrupt

I'm curious why it's failing to allocate MSIs. Possibly it's just run out.

Can you post the output of 'cat /proc/interrupts'?

cheers




cat /proc/interrupts
CPU0
  18:  0   UIC  11 Edge  L2C
  19:  0   UIC  12 Level snd_ice1724
  20:  1   UIC  16 Level
  21:306   UIC  17 Level snd_hda_intel
  22:  12212   UIC   0 Level 0002:00:04.0
  25:619   UIC   6 Level MAL TX EOB
  26:937   UIC   7 Level MAL RX EOB
  27:  0   UIC   3 Level MAL SERR
  28:  0   UIC   4 Level MAL TX DE
  31:  0   UIC   5 Level MAL RX DE
  32:   6607   UIC  29 Level ehci_hcd:usb1
  33:  1   UIC  30 Level ohci_hcd:usb2
  38: 19   UIC   2 Level IBM IIC
  39:  0   UIC   3 Level IBM IIC
  40:  0   UIC  16 Level EMAC
  44:  0   UIC   0 Edge  aerdrv
  45:  0   UIC   2 Edge  aerdrv
LOC: 117318   Local timer interrupts for timer event device
LOC: 53   Local timer interrupts for others
SPU

Re: Problems with Kernels 3.17-rc1 and onwards on Acube Sam460 AMCC 460ex board

2015-02-19 Thread Julian Margetson

On 2/18/2015 10:56 PM, Michael Ellerman wrote:

On Wed, 2015-02-18 at 21:36 -0400, Julian Margetson wrote:

On 2/18/2015 8:13 PM, Michael Ellerman wrote:


On Wed, 2015-02-18 at 15:45 -0400, Julian Margetson wrote:

On 2/15/2015 8:18 PM, Michael Ellerman wrote:


On Sun, 2015-02-15 at 08:16 -0400, Julian Margetson wrote:

Hi

I am unable to get any kernel beyond  the 3.16 branch working on an
Acube Sam460ex
  AMCC 460ex based motherboard. Kernel  up 3.16.7-ckt6 working.

Does reverting b0345bbc6d09 change anything?


[6.364350] snd_hda_intel 0001:81:00.1: enabling device ( - 0002)
[6.453794] snd_hda_intel 0001:81:00.1: ppc4xx_setup_msi_irqs: fail mapping 
irq
[6.487530] Unable to handle kernel paging request for data at address 
0x0fa06c7c
[6.495055] Faulting instruction address: 0xc032202c
[6.500033] Vector: 300 (Data Access) at [efa31cf0]
[6.504922] pc: c032202c: __reg_op+0xe8/0x100
[6.509697] lr: c0014f88: msi_bitmap_free_hwirqs+0x50/0x94
[6.515600] sp: efa31da0
[6.518491]msr: 21000
[6.521112]dar: fa06c7c
[6.523915]  dsisr: 0
[6.526190]   current = 0xef8bab00
[6.529603] pid   = 115, comm = kworker/0:1
[6.534163] enter ? for help
[6.537054] [link register   ] c0014f88 msi_bitmap_free_hwirqs+0x50/0x94
[6.543811] [efa31da0] c0014f78 msi_bitmap_free_hwirqs+0x40/0x94 (unreliable)
[6.551001] [efa31dc0] c001aee8 ppc4xx_setup_msi_irqs+0xac/0xf4
[6.556973] [efa31e00] c03503a4 pci_enable_msi_range+0x1e0/0x280
[6.563032] [efa31e40] f92c2f74 azx_probe_work+0xe0/0x57c [snd_hda_intel]
[6.569906] [efa31e80] c0036344 process_one_work+0x1e8/0x2f0
[6.575627] [efa31eb0] c003677c worker_thread+0x2f4/0x438
[6.581079] [efa31ef0] c003a3e4 kthread+0xc8/0xcc
[6.585844] [efa31f40] c000aec4 ret_from_kernel_thread+0x5c/0x64
[6.591910] mon  no input ...

Managed to do a third git bisect  with the following results .

Great work.


git bisect bad
9279d3286e10736766edcaf815ae10e00856e448 is the first bad commit
commit 9279d3286e10736766edcaf815ae10e00856e448
Author: Rasmus Villemoes li...@rasmusvillemoes.dk
Date:   Wed Aug 6 16:10:16 2014 -0700

 lib: bitmap: change parameter of bitmap_*_region to unsigned

So the bug is in the 4xx MSI code, and has always been there, in fact I don't
see how that code has *ever* worked. The commit you bisected to just caused the
existing bug to cause an oops.

Can you try this?

diff --git a/arch/powerpc/sysdev/ppc4xx_msi.c b/arch/powerpc/sysdev/ppc4xx_msi.c
index 6e2e6aa378bb..effb5b878a78 100644
--- a/arch/powerpc/sysdev/ppc4xx_msi.c
+++ b/arch/powerpc/sysdev/ppc4xx_msi.c
@@ -95,11 +95,9 @@ static int ppc4xx_setup_msi_irqs(struct pci_dev *dev, int 
nvec, int type)
  
  	list_for_each_entry(entry, dev-msi_list, list) {

int_no = msi_bitmap_alloc_hwirqs(msi_data-bitmap, 1);
-   if (int_no = 0)
-   break;
if (int_no  0) {
-   pr_debug(%s: fail allocating msi interrupt\n,
-   __func__);
+   pr_warn(%s: fail allocating msi interrupt\n, 
__func__);
+   return -ENOSPC;
}
virq = irq_of_parse_and_map(msi_data-msi_dev, int_no);
if (virq == NO_IRQ) {


Thanks.
This works with 3.17-rc1. Will try with the 3.18 Branch .

OK great.


Any ideas why drm is not  working ? (It never worked) .

No sorry. You might have more luck if you post a new thread to the dri list.


[5.809802] Linux agpgart interface v0.103
[6.137893] [drm] Initialized drm 1.1.0 20060810
[6.439872] snd_hda_intel 0001:81:00.1: enabling device ( - 0002)
[6.508544] ppc4xx_setup_msi_irqs: fail allocating msi interrupt

I'm curious why it's failing to allocate MSIs. Possibly it's just run out.

Can you post the output of 'cat /proc/interrupts'?

cheers





With Kernel 3.19.0 for the first time a Radeon HD7750 is now showing 
video  but the HDMI audio not working .


[8.255402] Linux agpgart interface v0.103
[8.491334] [drm] Initialized drm 1.1.0 20060810
[8.867204] snd_hda_intel 0001:81:00.1: enabling device ( - 0002)
[8.968395] snd_hda_intel 0001:81:00.1: Force to snoop mode by module 
option

[9.062427] ppc4xx_setup_msi_irqs: fail allocating msi interrupt
[9.243778] input: HDA ATI HDMI HDMI/DP,pcm=3 as 
/devices/pci0001:80/0001:80:00.0/0001:81:00.1/sound/card0/input3

[9.576242] [drm] radeon kernel modesetting enabled.
[9.586233] [drm] initializing kernel modesetting (VERDE 
0x1002:0x683F 0x1545:0x7750).

[9.595194] [drm] register mmio base: 0xe9000
[9.600195] [drm] register mmio size: 262144
[   10.498475] Adding 62828k swap on /dev/sda10.  Priority:-1 extents:1 
across:62828k FS

[   10.538221] ATOM BIOS: C44501
[   10.577399] radeon 0001:81:00.0: VRAM: 1024M 0x - 
0x3FFF (1024M used)
[   10.652394] radeon 0001:81:00.0

Re: Problems with Kernels 3.17-rc1 and onwards on Acube Sam460 AMCC 460ex board

2015-02-18 Thread Julian Margetson

On 2/15/2015 8:18 PM, Michael Ellerman wrote:

On Sun, 2015-02-15 at 08:16 -0400, Julian Margetson wrote:

Hi

I am unable to get any kernel beyond  the 3.16 branch working on an
Acube Sam460ex
  AMCC 460ex based motherboard. Kernel  up 3.16.7-ckt6 working.

Does reverting b0345bbc6d09 change anything?


[6.364350] snd_hda_intel 0001:81:00.1: enabling device ( - 0002)
[6.453794] snd_hda_intel 0001:81:00.1: ppc4xx_setup_msi_irqs: fail mapping 
irq
[6.487530] Unable to handle kernel paging request for data at address 
0x0fa06c7c
[6.495055] Faulting instruction address: 0xc032202c
[6.500033] Vector: 300 (Data Access) at [efa31cf0]
[6.504922] pc: c032202c: __reg_op+0xe8/0x100
[6.509697] lr: c0014f88: msi_bitmap_free_hwirqs+0x50/0x94
[6.515600] sp: efa31da0
[6.518491]msr: 21000
[6.521112]dar: fa06c7c
[6.523915]  dsisr: 0
[6.526190]   current = 0xef8bab00
[6.529603] pid   = 115, comm = kworker/0:1
[6.534163] enter ? for help
[6.537054] [link register   ] c0014f88 msi_bitmap_free_hwirqs+0x50/0x94
[6.543811] [efa31da0] c0014f78 msi_bitmap_free_hwirqs+0x40/0x94 (unreliable)
[6.551001] [efa31dc0] c001aee8 ppc4xx_setup_msi_irqs+0xac/0xf4
[6.556973] [efa31e00] c03503a4 pci_enable_msi_range+0x1e0/0x280
[6.563032] [efa31e40] f92c2f74 azx_probe_work+0xe0/0x57c [snd_hda_intel]
[6.569906] [efa31e80] c0036344 process_one_work+0x1e8/0x2f0
[6.575627] [efa31eb0] c003677c worker_thread+0x2f4/0x438
[6.581079] [efa31ef0] c003a3e4 kthread+0xc8/0xcc
[6.585844] [efa31f40] c000aec4 ret_from_kernel_thread+0x5c/0x64
[6.591910] mon  no input ...

cheers




Managed to do a third git bisect  with the following results .

git bisect bad
9279d3286e10736766edcaf815ae10e00856e448 is the first bad commit
commit 9279d3286e10736766edcaf815ae10e00856e448
Author: Rasmus Villemoesli...@rasmusvillemoes.dk
Date:   Wed Aug 6 16:10:16 2014 -0700

lib: bitmap: change parameter of bitmap_*_region to unsigned

Changing the pos parameter of __reg_op to unsigned allows the compiler

to generate slightly smaller and simpler code.  Also update its callers
bitmap_*_region to receive and pass unsigned int.  The return types of
bitmap_find_free_region and bitmap_allocate_region are still int to
allow a negative error code to be returned.  An int is certainly capable
of representing any realistic return value.

Signed-off-by: Rasmus Villemoesli...@rasmusvillemoes.dk

Signed-off-by: Andrew Mortona...@linux-foundation.org
Signed-off-by: Linus Torvaldstorva...@linux-foundation.org

:04 04 4f560a7caaba2d05c146a3cea27e0d93739d950c 
c3d4539acad26667a2d78844ead7b75af753f41e M  include
:04 04 7a6fb894aac2a1d4e72f8e36b7c6de3c24509ad3 
31d756da185e07d2de090c9e6aeb12689d58d310 M  lib


___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev

Re: Problems with Kernels 3.17-rc1 and onwards on Acube Sam460 AMCC 460ex board

2015-02-18 Thread Julian Margetson

On 2/15/2015 8:18 PM, Michael Ellerman wrote:

On Sun, 2015-02-15 at 08:16 -0400, Julian Margetson wrote:

Hi

I am unable to get any kernel beyond  the 3.16 branch working on an
Acube Sam460ex
  AMCC 460ex based motherboard. Kernel  up 3.16.7-ckt6 working.

Does reverting b0345bbc6d09 change anything?


[6.364350] snd_hda_intel 0001:81:00.1: enabling device ( - 0002)
[6.453794] snd_hda_intel 0001:81:00.1: ppc4xx_setup_msi_irqs: fail mapping 
irq
[6.487530] Unable to handle kernel paging request for data at address 
0x0fa06c7c
[6.495055] Faulting instruction address: 0xc032202c
[6.500033] Vector: 300 (Data Access) at [efa31cf0]
[6.504922] pc: c032202c: __reg_op+0xe8/0x100
[6.509697] lr: c0014f88: msi_bitmap_free_hwirqs+0x50/0x94
[6.515600] sp: efa31da0
[6.518491]msr: 21000
[6.521112]dar: fa06c7c
[6.523915]  dsisr: 0
[6.526190]   current = 0xef8bab00
[6.529603] pid   = 115, comm = kworker/0:1
[6.534163] enter ? for help
[6.537054] [link register   ] c0014f88 msi_bitmap_free_hwirqs+0x50/0x94
[6.543811] [efa31da0] c0014f78 msi_bitmap_free_hwirqs+0x40/0x94 (unreliable)
[6.551001] [efa31dc0] c001aee8 ppc4xx_setup_msi_irqs+0xac/0xf4
[6.556973] [efa31e00] c03503a4 pci_enable_msi_range+0x1e0/0x280
[6.563032] [efa31e40] f92c2f74 azx_probe_work+0xe0/0x57c [snd_hda_intel]
[6.569906] [efa31e80] c0036344 process_one_work+0x1e8/0x2f0
[6.575627] [efa31eb0] c003677c worker_thread+0x2f4/0x438
[6.581079] [efa31ef0] c003a3e4 kthread+0xc8/0xcc
[6.585844] [efa31f40] c000aec4 ret_from_kernel_thread+0x5c/0x64
[6.591910] mon  no input ...


cheers




Managed to do a third git bisect  with the following results .

git bisect bad
9279d3286e10736766edcaf815ae10e00856e448 is the first bad commit
commit 9279d3286e10736766edcaf815ae10e00856e448
Author: Rasmus Villemoes li...@rasmusvillemoes.dk
Date:   Wed Aug 6 16:10:16 2014 -0700

lib: bitmap: change parameter of bitmap_*_region to unsigned

Changing the pos parameter of __reg_op to unsigned allows the compiler

to generate slightly smaller and simpler code.  Also update its callers
bitmap_*_region to receive and pass unsigned int.  The return types of
bitmap_find_free_region and bitmap_allocate_region are still int to
allow a negative error code to be returned.  An int is certainly capable
of representing any realistic return value.

Signed-off-by: Rasmus Villemoes li...@rasmusvillemoes.dk

Signed-off-by: Andrew Morton a...@linux-foundation.org
Signed-off-by: Linus Torvalds torva...@linux-foundation.org

:04 04 4f560a7caaba2d05c146a3cea27e0d93739d950c 
c3d4539acad26667a2d78844ead7b75af753f41e M  include
:04 04 7a6fb894aac2a1d4e72f8e36b7c6de3c24509ad3 
31d756da185e07d2de090c9e6aeb12689d58d310 M  lib


___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev

Re: Problems with Kernels 3.17-rc1 and onwards on Acube Sam460 AMCC 460ex board

2015-02-18 Thread Julian Margetson

On 2/18/2015 10:56 PM, Michael Ellerman wrote:

On Wed, 2015-02-18 at 21:36 -0400, Julian Margetson wrote:

On 2/18/2015 8:13 PM, Michael Ellerman wrote:


On Wed, 2015-02-18 at 15:45 -0400, Julian Margetson wrote:

On 2/15/2015 8:18 PM, Michael Ellerman wrote:


On Sun, 2015-02-15 at 08:16 -0400, Julian Margetson wrote:

Hi

I am unable to get any kernel beyond  the 3.16 branch working on an
Acube Sam460ex
  AMCC 460ex based motherboard. Kernel  up 3.16.7-ckt6 working.

Does reverting b0345bbc6d09 change anything?


[6.364350] snd_hda_intel 0001:81:00.1: enabling device ( - 0002)
[6.453794] snd_hda_intel 0001:81:00.1: ppc4xx_setup_msi_irqs: fail mapping 
irq
[6.487530] Unable to handle kernel paging request for data at address 
0x0fa06c7c
[6.495055] Faulting instruction address: 0xc032202c
[6.500033] Vector: 300 (Data Access) at [efa31cf0]
[6.504922] pc: c032202c: __reg_op+0xe8/0x100
[6.509697] lr: c0014f88: msi_bitmap_free_hwirqs+0x50/0x94
[6.515600] sp: efa31da0
[6.518491]msr: 21000
[6.521112]dar: fa06c7c
[6.523915]  dsisr: 0
[6.526190]   current = 0xef8bab00
[6.529603] pid   = 115, comm = kworker/0:1
[6.534163] enter ? for help
[6.537054] [link register   ] c0014f88 msi_bitmap_free_hwirqs+0x50/0x94
[6.543811] [efa31da0] c0014f78 msi_bitmap_free_hwirqs+0x40/0x94 (unreliable)
[6.551001] [efa31dc0] c001aee8 ppc4xx_setup_msi_irqs+0xac/0xf4
[6.556973] [efa31e00] c03503a4 pci_enable_msi_range+0x1e0/0x280
[6.563032] [efa31e40] f92c2f74 azx_probe_work+0xe0/0x57c [snd_hda_intel]
[6.569906] [efa31e80] c0036344 process_one_work+0x1e8/0x2f0
[6.575627] [efa31eb0] c003677c worker_thread+0x2f4/0x438
[6.581079] [efa31ef0] c003a3e4 kthread+0xc8/0xcc
[6.585844] [efa31f40] c000aec4 ret_from_kernel_thread+0x5c/0x64
[6.591910] mon  no input ...

Managed to do a third git bisect  with the following results .

Great work.


git bisect bad
9279d3286e10736766edcaf815ae10e00856e448 is the first bad commit
commit 9279d3286e10736766edcaf815ae10e00856e448
Author: Rasmus Villemoes li...@rasmusvillemoes.dk
Date:   Wed Aug 6 16:10:16 2014 -0700

 lib: bitmap: change parameter of bitmap_*_region to unsigned

So the bug is in the 4xx MSI code, and has always been there, in fact I don't
see how that code has *ever* worked. The commit you bisected to just caused the
existing bug to cause an oops.

Can you try this?

diff --git a/arch/powerpc/sysdev/ppc4xx_msi.c b/arch/powerpc/sysdev/ppc4xx_msi.c
index 6e2e6aa378bb..effb5b878a78 100644
--- a/arch/powerpc/sysdev/ppc4xx_msi.c
+++ b/arch/powerpc/sysdev/ppc4xx_msi.c
@@ -95,11 +95,9 @@ static int ppc4xx_setup_msi_irqs(struct pci_dev *dev, int 
nvec, int type)
  
  	list_for_each_entry(entry, dev-msi_list, list) {

int_no = msi_bitmap_alloc_hwirqs(msi_data-bitmap, 1);
-   if (int_no = 0)
-   break;
if (int_no  0) {
-   pr_debug(%s: fail allocating msi interrupt\n,
-   __func__);
+   pr_warn(%s: fail allocating msi interrupt\n, 
__func__);
+   return -ENOSPC;
}
virq = irq_of_parse_and_map(msi_data-msi_dev, int_no);
if (virq == NO_IRQ) {


Thanks.
This works with 3.17-rc1. Will try with the 3.18 Branch .

OK great.


Any ideas why drm is not  working ? (It never worked) .

No sorry. You might have more luck if you post a new thread to the dri list.


[5.809802] Linux agpgart interface v0.103
[6.137893] [drm] Initialized drm 1.1.0 20060810
[6.439872] snd_hda_intel 0001:81:00.1: enabling device ( - 0002)
[6.508544] ppc4xx_setup_msi_irqs: fail allocating msi interrupt

I'm curious why it's failing to allocate MSIs. Possibly it's just run out.

Can you post the output of 'cat /proc/interrupts'?

cheers




cat /proc/interrupts
   CPU0
 18:  0   UIC  11 Edge  L2C
 19:  0   UIC  12 Level snd_ice1724
 20:  1   UIC  16 Level
 21:306   UIC  17 Level snd_hda_intel
 22:  12212   UIC   0 Level 0002:00:04.0
 25:619   UIC   6 Level MAL TX EOB
 26:937   UIC   7 Level MAL RX EOB
 27:  0   UIC   3 Level MAL SERR
 28:  0   UIC   4 Level MAL TX DE
 31:  0   UIC   5 Level MAL RX DE
 32:   6607   UIC  29 Level ehci_hcd:usb1
 33:  1   UIC  30 Level ohci_hcd:usb2
 38: 19   UIC   2 Level IBM IIC
 39:  0   UIC   3 Level IBM IIC
 40:  0   UIC  16 Level EMAC
 44:  0   UIC   0 Edge  aerdrv
 45:  0   UIC   2 Edge  aerdrv
LOC: 117318   Local timer interrupts for timer event device
LOC: 53   Local timer interrupts for others
SPU:  0   Spurious interrupts
PMI:  0   Performance

Re: Problems with Kernels 3.17-rc1 and onwards on Acube Sam460 AMCC 460ex board

2015-02-18 Thread Julian Margetson

On 2/18/2015 8:13 PM, Michael Ellerman wrote:

On Wed, 2015-02-18 at 15:45 -0400, Julian Margetson wrote:

On 2/15/2015 8:18 PM, Michael Ellerman wrote:


On Sun, 2015-02-15 at 08:16 -0400, Julian Margetson wrote:

Hi

I am unable to get any kernel beyond  the 3.16 branch working on an
Acube Sam460ex
  AMCC 460ex based motherboard. Kernel  up 3.16.7-ckt6 working.

Does reverting b0345bbc6d09 change anything?


[6.364350] snd_hda_intel 0001:81:00.1: enabling device ( - 0002)
[6.453794] snd_hda_intel 0001:81:00.1: ppc4xx_setup_msi_irqs: fail mapping 
irq
[6.487530] Unable to handle kernel paging request for data at address 
0x0fa06c7c
[6.495055] Faulting instruction address: 0xc032202c
[6.500033] Vector: 300 (Data Access) at [efa31cf0]
[6.504922] pc: c032202c: __reg_op+0xe8/0x100
[6.509697] lr: c0014f88: msi_bitmap_free_hwirqs+0x50/0x94
[6.515600] sp: efa31da0
[6.518491]msr: 21000
[6.521112]dar: fa06c7c
[6.523915]  dsisr: 0
[6.526190]   current = 0xef8bab00
[6.529603] pid   = 115, comm = kworker/0:1
[6.534163] enter ? for help
[6.537054] [link register   ] c0014f88 msi_bitmap_free_hwirqs+0x50/0x94
[6.543811] [efa31da0] c0014f78 msi_bitmap_free_hwirqs+0x40/0x94 (unreliable)
[6.551001] [efa31dc0] c001aee8 ppc4xx_setup_msi_irqs+0xac/0xf4
[6.556973] [efa31e00] c03503a4 pci_enable_msi_range+0x1e0/0x280
[6.563032] [efa31e40] f92c2f74 azx_probe_work+0xe0/0x57c [snd_hda_intel]
[6.569906] [efa31e80] c0036344 process_one_work+0x1e8/0x2f0
[6.575627] [efa31eb0] c003677c worker_thread+0x2f4/0x438
[6.581079] [efa31ef0] c003a3e4 kthread+0xc8/0xcc
[6.585844] [efa31f40] c000aec4 ret_from_kernel_thread+0x5c/0x64
[6.591910] mon  no input ...

Managed to do a third git bisect  with the following results .

Great work.


git bisect bad
9279d3286e10736766edcaf815ae10e00856e448 is the first bad commit
commit 9279d3286e10736766edcaf815ae10e00856e448
Author: Rasmus Villemoes li...@rasmusvillemoes.dk
Date:   Wed Aug 6 16:10:16 2014 -0700

 lib: bitmap: change parameter of bitmap_*_region to unsigned
 
 Changing the pos parameter of __reg_op to unsigned allows the compiler

 to generate slightly smaller and simpler code.  Also update its callers
 bitmap_*_region to receive and pass unsigned int.  The return types of
 bitmap_find_free_region and bitmap_allocate_region are still int to
 allow a negative error code to be returned.  An int is certainly capable
 of representing any realistic return value.

So that looks feasible as the culprit.

Looking at the 4xx MSI code, it just looks wrong:

static int ppc4xx_setup_msi_irqs(struct pci_dev *dev, int nvec, int type)
{
...

list_for_each_entry(entry, dev-msi_list, list) {
int_no = msi_bitmap_alloc_hwirqs(msi_data-bitmap, 1);
if (int_no = 0)
break;

That's backward, a *negative* return indicates an error.

if (int_no  0) {
pr_debug(%s: fail allocating msi interrupt\n,
__func__);
}

This is the correct check, but it just prints a warning and then continues,
which is not going to work.

virq = irq_of_parse_and_map(msi_data-msi_dev, int_no);

This will fail if int_no is negative.

if (virq == NO_IRQ) {
dev_err(dev-dev, %s: fail mapping irq\n, __func__);
msi_bitmap_free_hwirqs(msi_data-bitmap, int_no, 1);

And so here we can pass a negative int_no to the free routine, which then 
oopses.

return -ENOSPC;
}


So the bug is in the 4xx MSI code, and has always been there, in fact I don't
see how that code has *ever* worked. The commit you bisected to just caused the
existing bug to cause an oops.

Can you try this?

diff --git a/arch/powerpc/sysdev/ppc4xx_msi.c b/arch/powerpc/sysdev/ppc4xx_msi.c
index 6e2e6aa378bb..effb5b878a78 100644
--- a/arch/powerpc/sysdev/ppc4xx_msi.c
+++ b/arch/powerpc/sysdev/ppc4xx_msi.c
@@ -95,11 +95,9 @@ static int ppc4xx_setup_msi_irqs(struct pci_dev *dev, int 
nvec, int type)
  
  	list_for_each_entry(entry, dev-msi_list, list) {

int_no = msi_bitmap_alloc_hwirqs(msi_data-bitmap, 1);
-   if (int_no = 0)
-   break;
if (int_no  0) {
-   pr_debug(%s: fail allocating msi interrupt\n,
-   __func__);
+   pr_warn(%s: fail allocating msi interrupt\n, 
__func__);
+   return -ENOSPC;
}
virq = irq_of_parse_and_map(msi_data-msi_dev, int_no);
if (virq == NO_IRQ) {

cheers





Thanks.
This works with 3.17-rc1. Will try with the 3.18 Branch .
Any ideas why drm is not  working ? (It never worked) .

[5.809802] Linux agpgart interface

Re: Problems with Kernels 3.17-rc1 and onwards on Acube Sam460 AMCC 460ex board

2015-02-18 Thread Julian Margetson

On Wed, 2015-02-18 at 15:45 -0400, Julian Margetson wrote:

On 2/15/2015 8:18 PM, Michael Ellerman wrote:

 On Sun, 2015-02-15 at 08:16 -0400, Julian Margetson wrote:
  Hi
 
  I am unable to get any kernel beyond  the 3.16 branch working on an
  Acube Sam460ex
   AMCC 460ex based motherboard. Kernel  up 3.16.7-ckt6 working.
 Does reverting b0345bbc6d09 change anything?

  [6.364350] snd_hda_intel 0001:81:00.1: enabling device ( - 0002)
  [6.453794] snd_hda_intel 0001:81:00.1: ppc4xx_setup_msi_irqs: fail 
mapping irq
  [6.487530] Unable to handle kernel paging request for data at address 
0x0fa06c7c
  [6.495055] Faulting instruction address: 0xc032202c
  [6.500033] Vector: 300 (Data Access) at [efa31cf0]
  [6.504922] pc: c032202c: __reg_op+0xe8/0x100
  [6.509697] lr: c0014f88: msi_bitmap_free_hwirqs+0x50/0x94
  [6.515600] sp: efa31da0
  [6.518491]msr: 21000
  [6.521112]dar: fa06c7c
  [6.523915]  dsisr: 0
  [6.526190]   current = 0xef8bab00
  [6.529603] pid   = 115, comm = kworker/0:1
  [6.534163] enter ? for help
  [6.537054] [link register   ] c0014f88 msi_bitmap_free_hwirqs+0x50/0x94
  [6.543811] [efa31da0] c0014f78 msi_bitmap_free_hwirqs+0x40/0x94 
(unreliable)
  [6.551001] [efa31dc0] c001aee8 ppc4xx_setup_msi_irqs+0xac/0xf4
  [6.556973] [efa31e00] c03503a4 pci_enable_msi_range+0x1e0/0x280
  [6.563032] [efa31e40] f92c2f74 azx_probe_work+0xe0/0x57c [snd_hda_intel]
  [6.569906] [efa31e80] c0036344 process_one_work+0x1e8/0x2f0
  [6.575627] [efa31eb0] c003677c worker_thread+0x2f4/0x438
  [6.581079] [efa31ef0] c003a3e4 kthread+0xc8/0xcc
  [6.585844] [efa31f40] c000aec4 ret_from_kernel_thread+0x5c/0x64
  [6.591910] mon  no input ...

Managed to do a third git bisect  with the following results .


Great work.


git bisect bad
9279d3286e10736766edcaf815ae10e00856e448 is the first bad commit
commit 9279d3286e10736766edcaf815ae10e00856e448
Author: Rasmus Villemoes li...@rasmusvillemoes.dk
Date:   Wed Aug 6 16:10:16 2014 -0700

lib: bitmap: change parameter of bitmap_*_region to unsigned

Changing the pos parameter of __reg_op to unsigned allows the compiler
to generate slightly smaller and simpler code.  Also update its callers
bitmap_*_region to receive and pass unsigned int.  The return types of
bitmap_find_free_region and bitmap_allocate_region are still int to
allow a negative error code to be returned.  An int is certainly capable
of representing any realistic return value.


So that looks feasible as the culprit.

Looking at the 4xx MSI code, it just looks wrong:

static int ppc4xx_setup_msi_irqs(struct pci_dev *dev, int nvec, int type)
{
...

list_for_each_entry(entry, dev-msi_list, list) {
int_no = msi_bitmap_alloc_hwirqs(msi_data-bitmap, 1);
if (int_no = 0)
break;

That's backward, a *negative* return indicates an error.

if (int_no  0) {
pr_debug(%s: fail allocating msi interrupt\n,
__func__);
}

This is the correct check, but it just prints a warning and then continues,
which is not going to work.

virq = irq_of_parse_and_map(msi_data-msi_dev, int_no);

This will fail if int_no is negative.

if (virq == NO_IRQ) {
dev_err(dev-dev, %s: fail mapping irq\n, __func__);
msi_bitmap_free_hwirqs(msi_data-bitmap, int_no, 1);

And so here we can pass a negative int_no to the free routine, which 
then oopses.


return -ENOSPC;
}


So the bug is in the 4xx MSI code, and has always been there, in fact I 
don't
see how that code has *ever* worked. The commit you bisected to just 
caused the

existing bug to cause an oops.

Can you try this?

diff --git a/arch/powerpc/sysdev/ppc4xx_msi.c 
b/arch/powerpc/sysdev/ppc4xx_msi.c

index 6e2e6aa378bb..effb5b878a78 100644
--- a/arch/powerpc/sysdev/ppc4xx_msi.c
+++ b/arch/powerpc/sysdev/ppc4xx_msi.c
@@ -95,11 +95,9 @@ static int ppc4xx_setup_msi_irqs(struct pci_dev *dev, 
int nvec, int type)

list_for_each_entry(entry, dev-msi_list, list) {
int_no = msi_bitmap_alloc_hwirqs(msi_data-bitmap, 1);
-   if (int_no = 0)
-   break;
if (int_no  0) {
-   pr_debug(%s: fail allocating msi interrupt\n,
-   __func__);
+   pr_warn(%s: fail allocating msi interrupt\n, 
__func__);
+   return -ENOSPC;
}
virq = irq_of_parse_and_map(msi_data-msi_dev, int_no);
if (virq == NO_IRQ) {

cheers


Can also confirm patch working with kernel 3.18.7 .




___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org

Problems with Kernels 3.17-rc1 and onwards on Acube Sam460 AMCC 460ex board

2015-02-15 Thread Julian Margetson

Hi

I am unable to get any kernel beyond  the 3.16 branch working on an 
Acube Sam460ex

 AMCC 460ex based motherboard. Kernel  up 3.16.7-ckt6 working.

These are the patches applied

diff --git a/drivers/gpu/drm/radeon/radeon_device.c 
b/drivers/gpu/drm/radeon/radeon_device.c
index 49b0659..fa33568 100644
--- a/drivers/gpu/drm/radeon/radeon_device.c
+++ b/drivers/gpu/drm/radeon/radeon_device.c
@@ -1066,7 +1066,7 @@ int radeon_device_init(struct radeon_device *rdev,
if (rdev-rmmio == NULL) {
return -ENOMEM;
}
-   DRM_INFO(register mmio base: 0x%08X\n, (uint32_t)rdev-rmmio_base);
+   DRM_INFO(register mmio base: 0x%llx\n, (uint64_t)rdev-rmmio_base);
DRM_INFO(register mmio size: %u\n, (unsigned)rdev-rmmio_size);
 
 	/* io port mapping */

diff --git a/include/drm/ttm/ttm_bo_api.h b/include/drm/ttm/ttm_bo_api.h
index 3cb5d84..fcdb208 100644
--- a/include/drm/ttm/ttm_bo_api.h
+++ b/include/drm/ttm/ttm_bo_api.h
@@ -81,7 +81,7 @@ struct ttm_placement {
  */
 struct ttm_bus_placement {
void*addr;
-   unsigned long   base;
+   phys_addr_t base;
unsigned long   size;
unsigned long   offset;
boolis_iomem;



These are the serial boot messages

U-Boot 2010.06.05a (Jan 30 2012 - 16:06:56)

CPU:   AMCC PowerPC 460EX Rev. B at 1155 MHz (PLB=231 OPB=115 EBC=115)
   No Security/Kasumi support
   Bootstrap Option H - Boot ROM Location I2C (Addr 0x52)
   Internal PCI arbiter enabled
   32 kB I-Cache 32 kB D-Cache
Board: Sam460ex, PCIe 4x + PCIe 1x
I2C:   ready
DRAM:  2 GiB (ECC not enabled, 462 MHz, CL4)
PCI:   Bus Dev VenId DevId Class Int
00  04  1095  3512  0104  00
00  06  126f  0501  0380  00
PCIE0: successfully set as root-complex
03  00  1412  1724  0401  ff
02  00  1b21  1080  0604  00
PCIE1: successfully set as root-complex
05  00  1002  6758  0300  ff
Net:   ppc_4xx_eth0
FPGA:  Revision 03 (2010-10-07)
SM502: found
VGA:   1
VESA:  OK
[0.00] Using Canyonlands machine description
[0.00] Initializing cgroup subsys cpu
[0.00] Linux version 3.17.0-rc1-Sam460ex (root@julian-VirtualBox) (gcc 
version 4.8.2 (Ubuntu 4.8.2-16ubuntu3) ) #1 PREEMPT Sat Feb 14 19:45:33 AST 2015
[0.00] Zone ranges:
[0.00]   DMA  [mem 0x-0x2fff]
[0.00]   Normal   empty
[0.00]   HighMem  [mem 0x3000-0x7fff]
[0.00] Movable zone start for each node
[0.00] Early memory node ranges
[0.00]   node   0: [mem 0x-0x7fff]
[0.00] MMU: Allocated 1088 bytes of context maps for 255 contexts
[0.00] Built 1 zonelists in Zone order, mobility grouping on.  Total 
pages: 522752
[0.00] Kernel command line: root=/dev/sda12 console=ttyS0,115200 
console=tty0
[0.00] PID hash table entries: 4096 (order: 2, 16384 bytes)
[0.00] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[0.00] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[0.00] Sorting __ex_table...
[0.00] Memory: 2004844K/2097152K available (5764K kernel code, 232K 
rwdata, 1456K rodata, 236K init, 1333K bss, 92308K reserved, 1310720K highmem)
[0.00] Kernel virtual memory layout:
[0.00]   * 0xfffcf000..0xf000  : fixmap
[0.00]   * 0xffc0..0xffe0  : highmem PTEs
[0.00]   * 0xffa0..0xffc0  : consistent mem
[0.00]   * 0xffa0..0xffa0  : early ioremap
[0.00]   * 0xf100..0xffa0  : vmalloc  ioremap
[0.00] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[0.00] Preemptible hierarchical RCU implementation.
[0.00] NR_IRQS:512 nr_irqs:512 16
[0.00] UIC0 (32 IRQ sources) at DCR 0xc0
[0.00] UIC1 (32 IRQ sources) at DCR 0xd0
[0.00] UIC2 (32 IRQ sources) at DCR 0xe0
[0.00] UIC3 (32 IRQ sources) at DCR 0xf0
[0.13] clocksource: timebase mult[dda520] shift[24] registered
[0.000138] Console: colour dummy device 80x25
[0.000557] console [tty0] enabled
[0.000581] pid_max: default: 32768 minimum: 301
[0.000683] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[0.000706] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[0.002800] devtmpfs: initialized
[0.003674] xor: measuring software checksum speed
[0.013505]8regs :   856.000 MB/sec
[0.023276]8regs_prefetch:   780.000 MB/sec
[0.033309]32regs:  1120.000 MB/sec
[0.043362]32regs_prefetch:   996.000 MB/sec
[0.043388] xor: using function: 32regs (1120.000 MB/sec)
[0.045174] NET: Registered protocol family 16
[0.046996] 256k L2-cache enabled
[0.047113] PCIE0: Checking link...
[0.047126] PCIE0: Device detected, waiting for link...
[0.047140] PCIE0: link is up !
[0.149234] PCI host bridge /plb/pciex@d (primary) ranges:
[