* [BUG] Boot failure since df9bcc2bc on veyron_speedy
@ 2017-01-09 14:19 S. Gilles
2017-01-09 14:49 ` S. Gilles
0 siblings, 1 reply; 7+ messages in thread
From: S. Gilles @ 2017-01-09 14:19 UTC (permalink / raw)
To: Jaehoon Chung, Ulf Hansson, Joonyoung Shim, linux-mmc, linux-kernel
Hi,
I have a C201, a veyron_speedy device (which uses rk3288) running vanilla
kernels. With recent kernels it will fail to boot (screen is on, with
blinking cursor, but no login prompt and the machine does not respond
over ssh).
I've bisected this to df9bcc2bc0a1f8d2963bd916698268fb2470713b, and
reverting that commit on -mainline gives me a bootable kernel. I can
provide more information as needed.
Thanks,
S. Gilles
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [BUG] Boot failure since df9bcc2bc on veyron_speedy
2017-01-09 14:19 [BUG] Boot failure since df9bcc2bc on veyron_speedy S. Gilles
@ 2017-01-09 14:49 ` S. Gilles
2017-01-10 0:47 ` Shawn Lin
0 siblings, 1 reply; 7+ messages in thread
From: S. Gilles @ 2017-01-09 14:49 UTC (permalink / raw)
To: Jaehoon Chung, Ulf Hansson, Joonyoung Shim, linux-mmc, linux-kernel
On 2017-01-09T09:19:55-0500, S. Gilles wrote:
> Hi,
>
> I have a C201, a veyron_speedy device (which uses rk3288) running vanilla
> kernels. With recent kernels it will fail to boot (screen is on, with
> blinking cursor, but no login prompt and the machine does not respond
> over ssh).
>
> I've bisected this to df9bcc2bc0a1f8d2963bd916698268fb2470713b, and
> reverting that commit on -mainline gives me a bootable kernel. I can
> provide more information as needed.
As I was writing that, I let it sit in the non-booting state for longer
than usual. After about 6 minutes, I got panic output, which I hadn't
observed before. I've transcribed it by hand, so there may be typos.
...
1f40: 60000013 ffffffff
[<c010cdcc>] (__irq_svc) from [<c0108414>] (arch_cpu_idle+0x2c/0x48)
[<c0108414>] (arch_cpu_idle) from [<c07925d8>] (default_idle_call+0x38/0x3c)
[<c07925d8>] (default_idle_call) from [<c01661e0>] (do_idle+0x108/0x1e4)
[<c01661e0>] (do_idle) from [<c016650>] (cpu_startup_entry+0x28/0x2c)
[<c0166550>] (cpu_startup_entry) from [<c078cbfc>] (rest_init+0x70/0x88)
[<c078cbfc>] (rest_init) from [<c9b99d18>] (start_kernel+0x374/0x3f8)
[<c0b00d18>] (start_kernel) from [<0000807c>] (0x807c)
CPU1: stopping
CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.10.0-rc2-EXPERIMENTAL+ #17
Hardware name: Rockchip (Device Tree)
[<c0110938>] (unwind_backtrace) from [<c010c1e8>] (show_stack+0x20/0x24)
[<c010c1e8>] (show_stack) from [<c03cdd3c>] (dump_stack+0x84/0xa0)
[<c03cdd3c>] (dump_stack) from [<c010ee74>] (handle_IPI+0x1c0/0x298)
[<c010ee74>] (handle_IPI) from [<c0101514>] (gic_handle_irq+0x88/0xa4)
[<c0101514>] (gic_handle_irq) from [<c010cdcc>] (__irq_svc+0x6c/0x90)
Exception stack(0xed93bf40 to 0xed93bf88)
bf40: 00000001 00000000 00000000 c011bde0 00000000 00000000 c0b8efd0 c0c942c0
bf60: 0000406a 410fc0d1 00000000 ed93bf9c ed93bfa0 ed93bf90 c0108424 c0108414
bf80: 60000013 ffffffff
[<c010cdcc>] (__irq_svc) from [<c0108414>] (arch_cpu_idle+0x2c/0x48)
[<c0108414>] (arch_cpu_idle) from [<c0166550>] (default_idle_call+0x38/0x3c)
[<c07925d8>] (default_idle_call) from [<c01661e0>] (do_idle+0x108/0x1e4)
[<c01661e0>] (do_idle) from [<c016650] (cpu_startup_entry+0x28/0x2c)
[<c0166550>] (cpu_startup_entry) from [<c010ea34>] (secondary_start_kernel+0x114/0x134)
[<c010ea34>] (secondary_start_kernel) from [<001018cc>] (0x1018cc)
BUG: spinlock bad magic on CPU#2, khungtaskd/33
lock: 0xeda23a98, .magic: 00000000, .owner: <none>/-1, .owner_cpu: 0
CPU: 2 PID: 33 Comm: khungtaskd Not tainted 4.10-rc2-EXPERIMENTAL+ #17
Hardware name: Rockchip (Device Tree)
[<c0110938>] (unwind_backtrace) from [<c010c1e8>] (show_stack+0x20/0x24)
[<c010c1e8>] (show_stack) from [<c03cdd3c>] (dump_stack+0x84/0xa0)
[<c03cdd3c>] (dump_stack) from [<c0168f74>] (spin_dump+0x8c/0xa0)
[<c0168f74>] (spin_dump) from [<c0168fbc>] (spin_bug+0x34/0x38)
[<c0168fbc>] (spin_bug) from [<c0169060>] (do_raw_spin_lock+0x30/0x1ac)
[<c0169060>] (do_raw_spin_lock) from [<c0792600>] (_raw_spin_lock_irqsave+0x20/0x298)
[<c0792600>] (_raw_spin_lock_irqsave) from [<c036fce0>] (buffer_size_add+0x34/0x74)
[<c036fce0>] (buffer_size_add) from [<c0370234>] (persistent_ram_write+0x34/0xc0)
[<c0370234>] (persistent_ram_write) from [<c036eb00>] (ramoops_pstore_write_buf+0x1ac/0x228)
[<c036eb00>] (ramoops_pstore_write_buf) from [<c036dc4c>] (pstore_write_compat+0x48/0x55)
[<c036dc4c>] (pstore_write_compat) from [<c036e2ec>] (pstore_dump+0x234/0x29c)
[<c036e2ec>] (pstore_dump) from [<c01700ec>] (kmsg_dump+0xb4/0xcc)
[<c01700ec>] (kmsg_dump) from [<c01ec8cc>] (panic+0x114/0x26c)
[<c01ec8cc>] (panic) from [<c91afe5c>] (watchdog+0x36c/0x3ac)
[<c01afe5c>] (watchdog) from [<c0140014>] (kthread+0x134/0x14c)
[<c0140014>] (kthread) from [<c0107998>] (ret_from_fork+0x14/0x3c)
---[ end Kernel panic - not syncing: hung_task: blocked tasks
Hopefully this is helpful.
--
S. Gilles
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [BUG] Boot failure since df9bcc2bc on veyron_speedy
2017-01-09 14:49 ` S. Gilles
@ 2017-01-10 0:47 ` Shawn Lin
2017-01-10 1:04 ` S. Gilles
0 siblings, 1 reply; 7+ messages in thread
From: Shawn Lin @ 2017-01-10 0:47 UTC (permalink / raw)
To: S. Gilles, Jaehoon Chung, Ulf Hansson, Joonyoung Shim, linux-mmc,
linux-kernel
Hi
On 2017/1/9 22:49, S. Gilles wrote:
> On 2017-01-09T09:19:55-0500, S. Gilles wrote:
>> Hi,
>>
>> I have a C201, a veyron_speedy device (which uses rk3288) running vanilla
>> kernels. With recent kernels it will fail to boot (screen is on, with
>> blinking cursor, but no login prompt and the machine does not respond
>> over ssh).
>>
>> I've bisected this to df9bcc2bc0a1f8d2963bd916698268fb2470713b, and
>> reverting that commit on -mainline gives me a bootable kernel. I can
>> provide more information as needed.
>
The fix is on the way,
https://patchwork.kernel.org/patch/9498527/
> As I was writing that, I let it sit in the non-booting state for longer
> than usual. After about 6 minutes, I got panic output, which I hadn't
> observed before. I've transcribed it by hand, so there may be typos.
>
> ...
> 1f40: 60000013 ffffffff
> [<c010cdcc>] (__irq_svc) from [<c0108414>] (arch_cpu_idle+0x2c/0x48)
> [<c0108414>] (arch_cpu_idle) from [<c07925d8>] (default_idle_call+0x38/0x3c)
> [<c07925d8>] (default_idle_call) from [<c01661e0>] (do_idle+0x108/0x1e4)
> [<c01661e0>] (do_idle) from [<c016650>] (cpu_startup_entry+0x28/0x2c)
> [<c0166550>] (cpu_startup_entry) from [<c078cbfc>] (rest_init+0x70/0x88)
> [<c078cbfc>] (rest_init) from [<c9b99d18>] (start_kernel+0x374/0x3f8)
> [<c0b00d18>] (start_kernel) from [<0000807c>] (0x807c)
> CPU1: stopping
> CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.10.0-rc2-EXPERIMENTAL+ #17
> Hardware name: Rockchip (Device Tree)
> [<c0110938>] (unwind_backtrace) from [<c010c1e8>] (show_stack+0x20/0x24)
> [<c010c1e8>] (show_stack) from [<c03cdd3c>] (dump_stack+0x84/0xa0)
> [<c03cdd3c>] (dump_stack) from [<c010ee74>] (handle_IPI+0x1c0/0x298)
> [<c010ee74>] (handle_IPI) from [<c0101514>] (gic_handle_irq+0x88/0xa4)
> [<c0101514>] (gic_handle_irq) from [<c010cdcc>] (__irq_svc+0x6c/0x90)
> Exception stack(0xed93bf40 to 0xed93bf88)
> bf40: 00000001 00000000 00000000 c011bde0 00000000 00000000 c0b8efd0 c0c942c0
> bf60: 0000406a 410fc0d1 00000000 ed93bf9c ed93bfa0 ed93bf90 c0108424 c0108414
> bf80: 60000013 ffffffff
> [<c010cdcc>] (__irq_svc) from [<c0108414>] (arch_cpu_idle+0x2c/0x48)
> [<c0108414>] (arch_cpu_idle) from [<c0166550>] (default_idle_call+0x38/0x3c)
> [<c07925d8>] (default_idle_call) from [<c01661e0>] (do_idle+0x108/0x1e4)
> [<c01661e0>] (do_idle) from [<c016650] (cpu_startup_entry+0x28/0x2c)
> [<c0166550>] (cpu_startup_entry) from [<c010ea34>] (secondary_start_kernel+0x114/0x134)
> [<c010ea34>] (secondary_start_kernel) from [<001018cc>] (0x1018cc)
> BUG: spinlock bad magic on CPU#2, khungtaskd/33
> lock: 0xeda23a98, .magic: 00000000, .owner: <none>/-1, .owner_cpu: 0
> CPU: 2 PID: 33 Comm: khungtaskd Not tainted 4.10-rc2-EXPERIMENTAL+ #17
> Hardware name: Rockchip (Device Tree)
> [<c0110938>] (unwind_backtrace) from [<c010c1e8>] (show_stack+0x20/0x24)
> [<c010c1e8>] (show_stack) from [<c03cdd3c>] (dump_stack+0x84/0xa0)
> [<c03cdd3c>] (dump_stack) from [<c0168f74>] (spin_dump+0x8c/0xa0)
> [<c0168f74>] (spin_dump) from [<c0168fbc>] (spin_bug+0x34/0x38)
> [<c0168fbc>] (spin_bug) from [<c0169060>] (do_raw_spin_lock+0x30/0x1ac)
> [<c0169060>] (do_raw_spin_lock) from [<c0792600>] (_raw_spin_lock_irqsave+0x20/0x298)
> [<c0792600>] (_raw_spin_lock_irqsave) from [<c036fce0>] (buffer_size_add+0x34/0x74)
> [<c036fce0>] (buffer_size_add) from [<c0370234>] (persistent_ram_write+0x34/0xc0)
> [<c0370234>] (persistent_ram_write) from [<c036eb00>] (ramoops_pstore_write_buf+0x1ac/0x228)
> [<c036eb00>] (ramoops_pstore_write_buf) from [<c036dc4c>] (pstore_write_compat+0x48/0x55)
> [<c036dc4c>] (pstore_write_compat) from [<c036e2ec>] (pstore_dump+0x234/0x29c)
> [<c036e2ec>] (pstore_dump) from [<c01700ec>] (kmsg_dump+0xb4/0xcc)
> [<c01700ec>] (kmsg_dump) from [<c01ec8cc>] (panic+0x114/0x26c)
> [<c01ec8cc>] (panic) from [<c91afe5c>] (watchdog+0x36c/0x3ac)
> [<c01afe5c>] (watchdog) from [<c0140014>] (kthread+0x134/0x14c)
> [<c0140014>] (kthread) from [<c0107998>] (ret_from_fork+0x14/0x3c)
> ---[ end Kernel panic - not syncing: hung_task: blocked tasks
>
> Hopefully this is helpful.
>
--
Best Regards
Shawn Lin
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [BUG] Boot failure since df9bcc2bc on veyron_speedy
2017-01-10 0:47 ` Shawn Lin
@ 2017-01-10 1:04 ` S. Gilles
2017-01-10 7:20 ` Ziyuan
0 siblings, 1 reply; 7+ messages in thread
From: S. Gilles @ 2017-01-10 1:04 UTC (permalink / raw)
To: Shawn Lin
Cc: Jaehoon Chung, Ulf Hansson, Joonyoung Shim, linux-mmc, linux-kernel
On 2017-01-10T08:47:16+0800, Shawn Lin wrote:
> Hi
>
> On 2017/1/9 22:49, S. Gilles wrote:
> > On 2017-01-09T09:19:55-0500, S. Gilles wrote:
> > > Hi,
> > >
> > > I have a C201, a veyron_speedy device (which uses rk3288) running vanilla
> > > kernels. With recent kernels it will fail to boot (screen is on, with
> > > blinking cursor, but no login prompt and the machine does not respond
> > > over ssh).
> > >
> > > I've bisected this to df9bcc2bc0a1f8d2963bd916698268fb2470713b, and
> > > reverting that commit on -mainline gives me a bootable kernel. I can
> > > provide more information as needed.
> >
>
> The fix is on the way,
>
> https://patchwork.kernel.org/patch/9498527/
Great - thanks for letting me know.
Thanks,
S. Gilles
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [BUG] Boot failure since df9bcc2bc on veyron_speedy
2017-01-10 1:04 ` S. Gilles
@ 2017-01-10 7:20 ` Ziyuan
2017-01-10 7:23 ` Jaehoon Chung
0 siblings, 1 reply; 7+ messages in thread
From: Ziyuan @ 2017-01-10 7:20 UTC (permalink / raw)
To: S. Gilles, Shawn Lin
Cc: Jaehoon Chung, Ulf Hansson, Joonyoung Shim, linux-mmc, linux-kernel
Hi,
On 01/10/2017 09:04 AM, S. Gilles wrote:
> On 2017-01-10T08:47:16+0800, Shawn Lin wrote:
>> Hi
>>
>> On 2017/1/9 22:49, S. Gilles wrote:
>>> On 2017-01-09T09:19:55-0500, S. Gilles wrote:
>>>> Hi,
>>>>
>>>> I have a C201, a veyron_speedy device (which uses rk3288) running vanilla
>>>> kernels. With recent kernels it will fail to boot (screen is on, with
>>>> blinking cursor, but no login prompt and the machine does not respond
>>>> over ssh).
>>>>
>>>> I've bisected this to df9bcc2bc0a1f8d2963bd916698268fb2470713b, and
>>>> reverting that commit on -mainline gives me a bootable kernel. I can
>>>> provide more information as needed.
>> The fix is on the way,
>>
>> https://patchwork.kernel.org/patch/9498527/
> Great - thanks for letting me know.
Can you share the result ?
BR
Ziyuan Xu
>
> Thanks,
> S. Gilles
> --
> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [BUG] Boot failure since df9bcc2bc on veyron_speedy
2017-01-10 7:20 ` Ziyuan
@ 2017-01-10 7:23 ` Jaehoon Chung
2017-01-10 17:40 ` S. Gilles
0 siblings, 1 reply; 7+ messages in thread
From: Jaehoon Chung @ 2017-01-10 7:23 UTC (permalink / raw)
To: Ziyuan, S. Gilles, Shawn Lin
Cc: Ulf Hansson, Joonyoung Shim, linux-mmc, linux-kernel
Hi
On 01/10/2017 04:20 PM, Ziyuan wrote:
> Hi,
>
> On 01/10/2017 09:04 AM, S. Gilles wrote:
>> On 2017-01-10T08:47:16+0800, Shawn Lin wrote:
>>> Hi
>>>
>>> On 2017/1/9 22:49, S. Gilles wrote:
>>>> On 2017-01-09T09:19:55-0500, S. Gilles wrote:
>>>>> Hi,
>>>>>
>>>>> I have a C201, a veyron_speedy device (which uses rk3288) running vanilla
>>>>> kernels. With recent kernels it will fail to boot (screen is on, with
>>>>> blinking cursor, but no login prompt and the machine does not respond
>>>>> over ssh).
>>>>>
>>>>> I've bisected this to df9bcc2bc0a1f8d2963bd916698268fb2470713b, and
>>>>> reverting that commit on -mainline gives me a bootable kernel. I can
>>>>> provide more information as needed.
>>> The fix is on the way,
>>>
>>> https://patchwork.kernel.org/patch/9498527/
>> Great - thanks for letting me know.
>
> Can you share the result ?
Sorry for late. If it's working fine, I will apply it on fixes.
Best Regards,
Jaehoon Chung
>
> BR
> Ziyuan Xu
>
>>
>> Thanks,
>> S. Gilles
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>>
>>
>
>
>
>
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [BUG] Boot failure since df9bcc2bc on veyron_speedy
2017-01-10 7:23 ` Jaehoon Chung
@ 2017-01-10 17:40 ` S. Gilles
0 siblings, 0 replies; 7+ messages in thread
From: S. Gilles @ 2017-01-10 17:40 UTC (permalink / raw)
To: Jaehoon Chung
Cc: Ziyuan, Shawn Lin, Ulf Hansson, Joonyoung Shim, linux-mmc, linux-kernel
On 2017-01-10T16:23:11+0900, Jaehoon Chung wrote:
> Hi
>
> On 01/10/2017 04:20 PM, Ziyuan wrote:
> > Hi,
> >
> > On 01/10/2017 09:04 AM, S. Gilles wrote:
> >> On 2017-01-10T08:47:16+0800, Shawn Lin wrote:
> >>> Hi
> >>>
> >>> On 2017/1/9 22:49, S. Gilles wrote:
> >>>> On 2017-01-09T09:19:55-0500, S. Gilles wrote:
> >>>>> Hi,
> >>>>>
> >>>>> I have a C201, a veyron_speedy device (which uses rk3288) running vanilla
> >>>>> kernels. With recent kernels it will fail to boot (screen is on, with
> >>>>> blinking cursor, but no login prompt and the machine does not respond
> >>>>> over ssh).
> >>>>>
> >>>>> I've bisected this to df9bcc2bc0a1f8d2963bd916698268fb2470713b, and
> >>>>> reverting that commit on -mainline gives me a bootable kernel. I can
> >>>>> provide more information as needed.
> >>> The fix is on the way,
> >>>
> >>> https://patchwork.kernel.org/patch/9498527/
> >> Great - thanks for letting me know.
> >
> > Can you share the result ?
>
> Sorry for late. If it's working fine, I will apply it on fixes.
My apologies - I wasn't sure if the fix was complete, or just in-progress.
It works fine for me: my system boots as normal.
Thanks,
S. Gilles
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2017-01-10 17:40 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-01-09 14:19 [BUG] Boot failure since df9bcc2bc on veyron_speedy S. Gilles
2017-01-09 14:49 ` S. Gilles
2017-01-10 0:47 ` Shawn Lin
2017-01-10 1:04 ` S. Gilles
2017-01-10 7:20 ` Ziyuan
2017-01-10 7:23 ` Jaehoon Chung
2017-01-10 17:40 ` S. Gilles
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).