#163 Crash with Kernel panic: deputy_wait

open
Moshe Bar
Migration (51)
3
2006-11-26
2005-07-19
Gene Carter
No

I can reliably produce a master node panic. The
resulting console message is:

Process 4126(te), uid=6005, killed because it received
an unrecognized message type (0x0) from the remote site
where it was running
DEPUTY: Unexpected non-urgent request type 0
Kernel panic: deputy_wait

This occurs when I compile my program("te") with profiling
enabled. The compiler is gcc v-3.2.3. The master OS is
RHEL 3 AS
with kernel 2.4.26 and the 2.4.26-om1 patch applied.
The program runs fine for 1-2 minutes then the master
node panics only producing the message I listed above.

If it matters, the nodes are modified versions of the
chaos distribution that run the official 2.4.28-om1 kernel.

Thanks,
Gene

Discussion

  • Gene Carter
    Gene Carter
    2005-07-22

    • labels: --> Migration
     
  • Gene Carter
    Gene Carter
    2005-08-02

    • priority: 5 --> 4
     
  • Gene Carter
    Gene Carter
    2005-08-19

    • priority: 4 --> 5
     
  • Moshe Bar
    Moshe Bar
    2005-09-26

    • priority: 5 --> 6
    • milestone: --> v2.6.9(openMosix 2.0.0)
    • assigned_to: nobody --> tab
    • status: open --> pending
     
  • Logged In: YES
    user_id=1312539

    This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 30 days (the time period specified by
    the administrator of this Tracker).

     
    • status: pending --> closed
     
  • Gene Carter
    Gene Carter
    2005-12-08

    • status: closed --> open
     
  • Gene Carter
    Gene Carter
    2005-12-08

    Logged In: YES
    user_id=271081

    I'm not sure why this was closed. Did I need to supply some
    more information?

     
  • Florian Delizy
    Florian Delizy
    2006-11-26

    • assigned_to: tab --> mosheb
     
  • Florian Delizy
    Florian Delizy
    2006-11-26

    Logged In: YES
    user_id=1283799
    Originator: NO

    I reassign it to moshe, moshe please tell us if this vuf is not relevant anymore.

    This is a 2.4 bug

     
  • Florian Delizy
    Florian Delizy
    2006-11-26

    • priority: 6 --> 3