>> [] __put_user_4+0x12/0x18
>> DWARF2 unwinder stuck at __put_user_4+0x12/0x18
>> Leftover inexact backtrace:
>> [] ret_from_fork+0x6/0x1c
>
>Hmpf. I saw it once in child_rip here too. Then I wanted to reproduce it to
>report
>properly and couldn't again. I had a few other backtraces that were
On 31/03/07, Michal Piotrowski <[EMAIL PROTECTED]> wrote:
> Were there any strange binutils in use, Michal?
I don't remember when I had problems with this compiler.
^^^
(sorry, to many bottles of beer)
ld --version
GNU ld version 2.17.50.0.6-2.fc6 20061020
Regards,
Michal
--
Michal K. K.
Andi Kleen napisał(a):
>> BUG: NMI Watchdog detected LOCKUP on CPU0, eip c014ce9c, registers:
>
> I suspect it is just because his console is too slow and then unwinding
> took too long and it happened to hit the unwinder.
>
> You did use a slow console, right?
console=ttyS0,115200n8
>
> I su
* Andi Kleen <[EMAIL PROTECTED]> wrote:
> > [] ret_from_fork+0x6/0x1c
>
> Hmpf. I saw it once in child_rip here too. Then I wanted to reproduce
> it to report properly and couldn't again. I had a few other backtraces
> that were all non stuck with child_rip then on essentially the same
> ker
>
> BUG: NMI Watchdog detected LOCKUP on CPU0, eip c014ce9c, registers:
I suspect it is just because his console is too slow and then unwinding
took too long and it happened to hit the unwinder.
You did use a slow console, right?
I suppose it just needs a strategic touch_nmi_watchdog. Will ad
5 matches
Mail list logo
