Re: Realtime Preemption, 2.6.12, Beginners Guide?

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

 



On Thursday 07 Jul 2005 13:29, Ingo Molnar wrote:
> * Alistair John Strachan <[email protected]> wrote:
> > http://devzero.co.uk/~alistair/oops1.jpeg
> >
> > I disabled the trace and the STACKOVERFLOW option seems to help; I've
> > got a (slightly truncated) oops from the kernel. What happens is that
> > I get an oops, then I get a BUG: warning me about the softlock, then I
> > get another oops. I'm about to reboot to confirm whether the second
> > oops is identical to the first (I suspect that it is).
>
> unfortunately the EIP is at 0xedc, which is a corrupted value. The stack
> trace portion that is visible on the screen is the usual pagefault trace
> - without any information about the crash site itself. What the oops
> tells us is that it's the openvpn process that crashed (if this was the
> first oops). The preempt_count is 0x20010004, which shows us that this
> was a section that had soft-IRQ-flags disabled and was in a hardirq
> context.  (see the meaning of the preempt bits at the top of
> include/linux/hardirq.h) That it's a hardirq handler that crashed is
> further corroborated by the esp, which points into a kernel data area
> (hardirq_ctx[], the 4K irq stacks), not into the process's kernel stack
> (which is at threadinfo).
>
> the stack pointer itself looks healthy, it's near the end of a 4K page,
> i.e. far from overflowing. So it would be really useful to get the full
> oops output. (that way you can also be sure it's the first crash you are
> seeing.)
>
> (i doubt netconsole debugging will work, given that we are in a hardirq
> context. Serial logging will work.)
>
> one thing you could try is to apply the attached patch and reproduce the
> crash. It should print a pure backtrace and lock the box up afterwards,
> so that you can take a picture.

Done, sorry for the delay.

http://devzero.co.uk/~alistair/oops4.jpeg

I don't think this is really any more helpful, the dereference is at "virtual 
address 00000001" which sounds fishy.

-- 
Cheers,
Alistair.

personal:   alistair()devzero!co!uk
university: s0348365()sms!ed!ac!uk
student:    CS/CSim Undergraduate
contact:    1F2 55 South Clerk Street,
            Edinburgh. EH8 9PP.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]
  Powered by Linux