Opened 8 years ago

Last modified 4 years ago

#12713 closed bug

"Momen tary" KDL at boot — at Version 2

Reported by: Pete Owned by: korli
Priority: normal Milestone: R1
Component: Servers/input_server Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Platform: All

Description (last modified by diver)

Recent nightlies have been giving me a very odd KDL. I get the KDL white-screen but it goes away before I have time to read it! Then I get a normal looking Desktop... but everything is dead. I have to use Ctrl-Alt-Del to reboot.

I think it's due to having my twitchy hand on the mouse. The crash doesn't always happen but I think it does when I've moved the mouse. I just tried and deliberately moved the mouse, and it crashed. I have a USB wireless mouse.

I've never been able to read the fast-disappearing KDL screen, but looking at the syslog, this seems to be it:

KERN: bfs: mounted "Haiku" (root node at 524288, device = /dev/disk/scsi/0/4/0/2)
KERN: /dev/net/iprowifi4965/0: media change, media 0x300a0 quality 1000 speed 1000000000
KERN: usb_hid: no handlers for hid device
KERN: loaded driver /boot/system/add-ons/kernel/drivers/dev/input/usb_hid
KERN: ps2_hid: init_hardware
KERN: ps2_hid: init_driver
KERN: ps2: active multiplexing v1.1 enabled
KERN: ps2_hid: publish_devices
KERN: ps2_hid: uninit_driver
KERN: loaded driver /boot/system/add-ons/kernel/drivers/dev/input/ps2_hid
KERN: ps2: reset failed
KERN: ps2: devfs_publish_device input/mouse/ps2/0, status = 0xffffffff
KERN: loaded driver /boot/system/add-ons/kernel/drivers/dev/input/wacom
KERN: usb_hid: keyboard device unhandled control 0x00002710
Last message repeated 1 time
KERN: vm_soft_fault: va 0x10000 not covered by area in address space
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x10000, ip 0x60b951, write 1, user 1, thread 0x2b9
KERN: vm_page_fault: thread "_input_server_event_loop_" (697) in team "input_server" (683) tried to write address 0x10000, ip 0x60b951 ("libroot.so_seg0ro" +0x36951)
KERN: debug_server: Thread 697 entered the debugger: Segment violation
KERN: stack trace, current PC 0x60b951  atomic_set + 0xd:
KERN:   (0x79b19948)  0x219b60f  _DispatchEvents__11InputServerRt11BObjectList1Z8BMessage + 0x4f
KERN:   (0x79b19978)  0x219aaa9  _EventLoop__11InputServer + 0x1d9
KERN:   (0x79b199f8)  0x219a8c7  _EventLooper__11InputServerPv + 0x1f
KERN:   (0x79b19a28)  0x606d23  thread_entry + 0x23

Any ideas? I am currently at hrev50180 but it's been happening for a while.

Change History (2)

comment:1 by Pete, 8 years ago

Why can I (as the creator of the ticket) not seem to be able to modify it? Two stupid typos I missed, but also I should see if I can find a better category -- and change the milestone to 'R1'. "Modify Ticket" just gives me the field "Leave as new"...

comment:2 by diver, 8 years ago

Component: - GeneralServers/input_server
Description: modified (diff)
Keywords: KDL removed
Milestone: UnscheduledR1
Owner: changed from nobody to korli
Platform: x86All
Note: See TracTickets for help on using tickets.