Hi Tom,
On Mon, 2018-11-26 at 19:51 -0500, Tom Rini wrote:
> On Mon, Nov 26, 2018 at 09:07:37PM -0200, Otavio Salvador wrote:
> > Hello Alexey,
> >
> > On Mon, Nov 26, 2018 at 7:30 PM Alexey Brodkin
> > wrote:
> > > On Sat, 2018-11-24 at 06:57 -0800, Khem Raj wrote:
> > > > http://errors.yoctopr
Hi Douglas,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on kgdb/kgdb-next]
[also build test ERROR on v4.20-rc4 next-20181126]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci
Hi,
On Wed, Nov 14, 2018 at 2:07 PM Will Deacon wrote:
>
> > +void __weak kgdb_call_nmi_hook(void *ignored)
> > +{
> > + kgdb_nmicallback(raw_smp_processor_id(), get_irq_regs());
> > +}
>
> I suppose you could pass the cpu as an argument, but it doesn't really
> matter.
I probably won't chan
The function kgdb_roundup_cpus() was passed a parameter that was
documented as:
> the flags that will be used when restoring the interrupts. There is
> local_irq_save() call before kgdb_roundup_cpus().
Nobody used those flags. Anyone who wanted to temporarily turn on
interrupts just did local_ir
When I had lockdep turned on and dropped into kgdb I got a nice splat
on my system. Specifically it hit:
DEBUG_LOCKS_WARN_ON(current->hardirq_context)
Specifically it looked like this:
sysrq: SysRq : DEBUG
[ cut here ]
DEBUG_LOCKS_WARN_ON(current->hardirq_context)
This series was originally part of the series ("serial: Finish kgdb on
qcom_geni; fix many lockdep splats w/ kgdb") but it made sense to
split it up.
It's believed that dropping into kgdb should be more robust once these
patches are applied.
Changes in v5:
- Add a comment about get_irq_regs().
-
On Mon, Nov 26, 2018 at 09:07:37PM -0200, Otavio Salvador wrote:
> Hello Alexey,
>
> On Mon, Nov 26, 2018 at 7:30 PM Alexey Brodkin
> wrote:
> > On Sat, 2018-11-24 at 06:57 -0800, Khem Raj wrote:
> > >
> > > http://errors.yoctoproject.org/Errors/Details/202185/
> >
> > Looking at the target name
Hello Alexey,
On Mon, Nov 26, 2018 at 7:30 PM Alexey Brodkin
wrote:
> On Sat, 2018-11-24 at 06:57 -0800, Khem Raj wrote:
> >
> > http://errors.yoctoproject.org/Errors/Details/202185/
>
> Looking at the target name "u-boot-tools-1_2018.11-r0 do_compile"
> I think it might have something to do with
On Mon, Nov 26, 2018 at 1:30 PM Alexey Brodkin
wrote:
>
> Hi Khem,
>
>
> On Sat, 2018-11-24 at 06:57 -0800, Khem Raj wrote:
> >
> > http://errors.yoctoproject.org/Errors/Details/202185/
>
> Looking at the target name "u-boot-tools-1_2018.11-r0 do_compile"
> I think it might have something to do wi
On Mon, Nov 12, 2018 at 06:22:16PM -0600, Rob Herring wrote:
> On Mon, Nov 12, 2018 at 12:32:50PM -0800, Florian Fainelli wrote:
> > On 11/6/18 6:06 AM, Mike Rapoport wrote:
> > > On Mon, Nov 05, 2018 at 02:54:25PM -0800, Florian Fainelli wrote:
> > >> Hi all,
> > >>
> > >> Changes in v4:
> > >>
>
Hi Khem,
On Sat, 2018-11-24 at 06:57 -0800, Khem Raj wrote:
>
> http://errors.yoctoproject.org/Errors/Details/202185/
Looking at the target name "u-boot-tools-1_2018.11-r0 do_compile"
I think it might have something to do with bump of U-Boot to v2018.11
and the error message in question was add
11 matches
Mail list logo
