Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#10436 closed bug (fixed)

Occasional panic on shutdown / reboot

Reported by: anevilyak Owned by: pdziepak
Priority: normal Milestone: R1
Component: System/Kernel Version: R1/Development
Keywords: Cc:
Blocked By: #10442, #10467 Blocking:
Platform: All

Description

A few times today, I've seen a panic that looks like the following on shutdowns or reboots, though not consistently. The CPU in question is an i7-2600 (4 physical cores + HT).

PANIC: page fault, but interrupts were disabled. Touching address 0x000007f4 from ip 0x80094331
...usual iframe + panic backtrace subcomponents removed...
vector: 0xe, error code: 0x2
<kernel_x86> Scheduler::CoreEntry<0x0>::UpdateLoad(int32: -1) + 0x15
<kernel_x86> reschedule(int32: 6) + 0x598
<kernel_x86> scheduler_reschedule + 0x39
<kernel_x86> thread_block_with_timeout + 0x1ba
<kernel_x86> common_snooze_etc(int64: 1000000, int32: 0, uint32: 0x8 (8), NULL) + 0x9e
<kernel_x86> snooze_etc + 0x20
<kernel_x86> snooze + 0x17
<kernel_x86> syslog_sender(NULL) + 0x75
<kernel_x86> common_thread_entry(0x8190cff0) + 0x3b

Change History (6)

comment:1 by pdziepak, 11 years ago

Blocked By: 10442 added

(In #10442) Despite slightly different KDL message this bug and #10436 are both results of trying to update load statistics on a disabled (thus removed from the scheduler structures).

comment:2 by pdziepak, 11 years ago

Should be fixed in hrev46731. Please confirm.

comment:3 by pdziepak, 11 years ago

Blocked By: 10467 added

comment:4 by anevilyak, 11 years ago

Resolution: fixed
Status: newclosed

Haven't seen this one again since the aforementioned commit.

in reply to:  4 comment:5 by vidrep, 11 years ago

Replying to anevilyak:

Haven't seen this one again since the aforementioned commit.

If problem was fixed in hrev46731, then should ticket 10467 be closed , since the crashed occurred with hrev46753?

comment:6 by pdziepak, 11 years ago

The fix, indeed, was only partial. hrev46767 solves the problem completely.

Note: See TracTickets for help on using tickets.