lkml.org 
[lkml]   [2010]   [Jan]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    SubjectRe: [Bug 15076] System panic under load with clockevents_program_event
    From
    Lastest git without HIGHMEM look good. If no problems occur, then I
    try use kernel with HIGHMEM and see what change...

    2010/1/25, okias <d.okias@gmail.com>:
    > Okey, I try without highmem soon.
    >
    > 2010/1/25, Thomas Gleixner <tglx@linutronix.de>:
    >> Switched to email. Please reply to all instead of using the bugzilla
    >> interface.
    >>
    >>> --- Comment #4 from okias <d.okias@gmail.com> 2010-01-22 10:17:25 ---
    >>> and it's regression. Now I work on 2.6.32.3 and no problem.
    >>
    >> That's a really weird one. The system is 50 min up and running and out
    >> of the blue it crashes in clockevents_program_event(). This function
    >> has been called a couple of thousand times before that point.
    >>
    >> The only way to crash there is when *dev is pointing into nirwana. dev
    >> comes from
    >>
    >> int tick_program_event(ktime_t expires, int force)
    >> {
    >> struct clock_event_device *dev =
    >> __get_cpu_var(tick_cpu_device).evtdev;
    >>
    >> according to the callchain. At this point nothing fiddles with
    >> tick_cpu_device.evtdev, so I suspect some really nasty memory
    >> corruption going on.
    >>
    >> okias, can you please disable highmem support and verify whether the
    >> problem persists ?
    >>
    >> Thanks,
    >>
    >> tglx
    >>
    >
    >
    > --
    > Jabber/XMPP: okias@isgeek.info
    > SIP VoIP: sip:17474537254@proxy01.sipphone.com
    >


    --
    Jabber/XMPP: okias@isgeek.info
    SIP VoIP: sip:17474537254@proxy01.sipphone.com


    \
     
     \ /
      Last update: 2010-01-26 15:11    [W:0.024 / U:59.024 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site