#16190: [input_server] crash in atomic_set
-----------------------------------+----------------------------
Reporter: Sarek01 | Owner: nobody
Type: bug | Status: new
Priority: normal | Milestone: Unscheduled
Component: Servers/input_server | Version: R1/Development
Resolution: | Keywords:
Blocked By: | Blocking:
Platform: All |
-----------------------------------+----------------------------
Changes (by waddlesplash):
* keywords: VM segment violation error =>
* component: System/Kernel => Servers/input_server
* summary: syslog_snippet_startup_kernel_VM_issue_hrev54154+97 =>
[input_server] crash in atomic_set
Old description:
Running haiku hrev54154+97, which was updated with software updater
approximately 24 hours ago. Update proceeded with no issues and haiku
worked normally until normal shutdown.
Upon startup this evening, startup proceeded through the boot screen up
until the Tracker background appeared, then it dropped straight into
KernelDebuggerLand. I was unfortunately not able to get a shot of the
screen, i do however have the syslog.
According to said syslog, it appears that the VM had a segment
violation. Log snippet attached.
KERN: vm_soft_fault: va 0x52000000 not covered by area in address space
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault
at 0x52000700, ip 0x14a6941, write 1, user 1, thread 0x113
KERN: debug_server: Thread 275 entered the debugger: Segment violation
KERN: ps2: keyboard found
KERN: stack trace, current PC 0x14a6941 atomic_set + 0xd:
KERN: (0x79cbad88) 0x1d826a7
_DispatchEvents__11InputServerRt11BObjectList1Z8BMessage + 0x4f
KERN: (0x79cbadb8) 0x1d81b05 _EventLoop__11InputServer + 0x1e1
KERN: (0x79cbae28) 0x1d8191b _EventLooper__11InputServerPv + 0x1f
KERN: (0x79cbae58) 0x14a1ccd thread_entry + 0x29
USER: Notify of added/removed device (Bad port ID)
Last message repeated 3 times
