Re: Oops on mov %edx,%ds in apic_timer_interrupt()

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 2006-05-31 at 08:38 +0200, Guennadi Liakhovetski wrote:
> On Tue, 30 May 2006, Arjan van de Ven wrote:
> 
> > On Tue, 2006-05-30 at 17:20 +0200, Guennadi Liakhovetski wrote:
> >> Hi all
> >>
> >> I am not a specialist in ix86 asm / architecture, therefore a question
> >> here. Under 2.4.30 I've got an Oops below.
> >>
> >> <1>Unable to handle kernel NULL pointer dereference at virtual address 00000000
> >> c010c881
> >> <1>*pde = 00000000
> >> Oops: 0002
> >> CPU:    0
> >> EIP:    0010:[<c010c881>]    Tainted: P
> >
> > what modules are you using?
> 
> It's some our local module. No idea what it does. But the question is 
> purerlly theoretical - how can such an oops happen and what it means? 

it's probably a garbled oops; they happen, esp when things go out of
sync

> I 
> think in the meantime, the "mov" instruction itself cannot cause it. So, 
> is it corrupted stack, or "imprecise abort", or what?

sometimes the tooling shows the oops one instruction "late"


--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive:       http://mail.nl.linux.org/kernelnewbies/
FAQ:           http://kernelnewbies.org/faq/


[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux