Opened 16 years ago

Last modified 8 years ago

#2539 in-progress bug

[app_server] crash in HWInterface::_CopyToFront

Reported by: diver Owned by: stippi
Priority: normal Milestone: R1
Component: Servers/app_server Version: R1/Development
Keywords: Cc:
Blocked By: Blocking: #12323, #12749
Platform: All

Description

When using VESA mode I tried to change resolution app_server crashed in HWInterface::_CopyToFront.

Segment violation
Switching to team /boot/beos/system.servers/app_server
HWInterface::_CopyToFront
HWInterface::CopyBackToFront
AccelerantHWInterface::CopyBackToFront
HWInterface::Invalidate
HWInterface::MoveCursorTo

Change History (9)

comment:1 by stippi, 16 years ago

Owner: changed from axeld to stippi
Status: newassigned

I've seen this too once. Thanks for reporting.

comment:2 by stpere, 16 years ago

Hi,

I have the same (or I think it's the same) error here on hrev30464.

vm_soft_fault: va 0x835b8000 not covered by area in address space
vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x835b8bc0, ip 0x2a0cb4, write 1, user 1, thread 0x58
vm_page_fault: thread "cursor loop" (88) in team "app_server" (49) tried to write address 0x835b8bc0, ip 0x2a0cb4 ("???" +0x2a0cb4)
debug_server: Thread 88 entered the debugger: Segment violation
stack trace, current PC 0x2a0cb4  _CopyToFront__C11HWInterfacePUcUlllll + 0x1a8:
  (0x701c5cec)  0x2a0407  _CopyBackToFront__11HWInterfaceR7BRegion + 0xbb
  (0x701c5d5c)  0x2969b4  _CopyBackToFront__21AccelerantHWInterfaceR7BRegion + 0xfc
  (0x701c5dac)  0x2a027a  CopyBackToFront__11HWInterfaceRC5BRect + 0x272
  (0x701c5e5c)  0x29fffc  Invalidate__11HWInterfaceRC5BRect + 0x58
  (0x701c5e8c)  0x29fcc8  MoveCursorTo__11HWInterfaceRCfT1 + 0x1b4
  (0x701c5f0c)  0x29687b  MoveCursorTo__21AccelerantHWInterfaceRCfT1 + 0x27
  (0x701c5f3c)  0x25a48e  _CursorLoop__15EventDispatcher + 0x7a
  (0x701c5f7c)  0x25a59b  _cursor_looper__15EventDispatcherPv + 0x1f
  (0x701c5fac)  0x65bd78  thread_entry + 0x20

comment:3 by michael.weirauch, 16 years ago

Can confirm having had something similar yesterday (something before hrev30464). Not in HWInterface. Never seen this before. Log got lost unfortunately.

comment:4 by diver, 14 years ago

Never saw it again, but I don't change resolution as it always correct.

comment:5 by bonefish, 11 years ago

In the last few days I have run into a similar crash on boot (with qemu, 2 CPUs) a few times:

vm_soft_fault: va 0xd4800000 not covered by area in address space
vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0xd4800000, ip 0x1083119, write 1, user 1, thread 0x11d
vm_page_fault: thread "picasso" (285) in team "app_server" (285) tried to write address 0xd4800000, ip 0x1083119 ("???" +0x1083119)
debug_server: Thread 285 entered the debugger: Segment violation
stack trace, current PC 0x1083119  _ZNK11HWInterface12_CopyToFrontEPhmllll + 0x2d5:
  (0x62b2d6d8)  0x1083555  _ZN11HWInterface16_CopyBackToFrontER7BRegion + 0x85
  (0x62b2d738)  0x105ec83  _ZN21AccelerantHWInterface16_CopyBackToFrontER7BRegion + 0xe3
  (0x62b2d798)  0x1084e85  _ZN11HWInterface15CopyBackToFrontERK5BRect + 0x213
  (0x62b2d868)  0x1082890  _ZN11HWInterface10InvalidateERK5BRect + 0x2e
  (0x62b2d888)  0x107d6f0  _ZN13DrawingEngine10FillRegionER7BRegionRK9rgb_color + 0x10a
  (0x62b2d918)  0x1010b4b  _ZN7Desktop14_SetBackgroundER7BRegion + 0xb3
  (0x62b2d978)  0x1016387  _ZN7Desktop4InitEv + 0x2d1
  (0x62b2da48)  0x100a806  _ZN9AppServer14_CreateDesktopEjPKc + 0x52
  (0x62b2da88)  0x100ab77  _ZN9AppServer16_DispatchMessageElRN8BPrivate12LinkReceiverE + 0xf7
  (0x62b2dae8)  0x101f6c1  _ZN13MessageLooper14_MessageLooperEv + 0xbb
  (0x62b2dc38)  0x101f5ff  _ZN13MessageLooper15_message_threadEPv + 0xf
  (0x62b2dc58)  0x100a7ac  _ZN9AppServer9RunLooperEv + 0x34
  (0x62b2dc78)  0x100afab  main + 0x5e
  (0x62b2dca8)  0x1009e3c  _start + 0x50
  (0x62b2dce0)  0x96a264  runtime_loader + 0x122

The latest version tested with was a PM Haiku equivalent to master hrev46085.

comment:6 by diver, 11 years ago

Version: R1/pre-alpha1R1/Development

comment:7 by kallisti5, 11 years ago

still occurs as of hrev46154

loaded driver /boot/system/add-ons/kernel/drivers/dev/net/ipro1000
vm_soft_fault: va 0xd3000000 not covered by area in address space
vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0xd3000000, ip 0x530119, write 1, user 1, thread 0x12f
vm_page_fault: thread "picasso" (303) in team "app_server" (303) tried to write address 0xd3000000, ip 0x530119 ("???" +0x530119)
debug_server: Thread 303 entered the debugger: Segment violation
ahci: ahci_supports_device
ahci: ahci_supports_device
[net/ipro1000/0] compat_open(0x2)
ifmedia_ioctl: switching lem to   Type: Ethernet
  SubType: autoselect
stack trace, current PC 0x530119  _ZNK11HWInterface12_CopyToFrontEPhmllll + 0x2d5:
  (0x62d53fa8)  0x530555  _ZN11HWInterface16_CopyBackToFrontER7BRegion + 0x85
  (0x62d54008)  0x50bc83  _ZN21AccelerantHWInterface16_CopyBackToFrontER7BRegion + 0xe3
  (0x62d54068)  0x531e85  _ZN11HWInterface15CopyBackToFrontERK5BRect + 0x213
  (0x62d54138)  0x52f890  _ZN11HWInterface10InvalidateERK5BRect + 0x2e
  (0x62d54158)  0x52a6f0  _ZN13DrawingEngine10FillRegionER7BRegionRK9rgb_color + 0x10a
  (0x62d541e8)  0x4bdb4b  _ZN7Desktop14_SetBackgroundER7BRegion + 0xb3
  (0x62d54248)  0x4c3387  _ZN7Desktop4InitEv + 0x2d1
  (0x62d54318)  0x4b7806  _ZN9AppServer14_CreateDesktopEjPKc + 0x52
  (0x62d54358)  0x4b7b77  _ZN9AppServer16_DispatchMessageElRN8BPrivate12LinkReceiverE + 0xf7
  (0x62d543b8)  0x4cc6c1  _ZN13MessageLooper14_MessageLooperEv + 0xbb
  (0x62d54508)  0x4cc5ff  _ZN13MessageLooper15_message_threadEPv + 0xf
  (0x62d54528)  0x4b77ac  _ZN9AppServer9RunLooperEv + 0x34
  (0x62d54548)  0x4b7fab  main + 0x5e
  (0x62d54578)  0x4b6e3c  _start + 0x50
  (0x62d545b0)  0x1d6ef98  runtime_loader + 0x122
/dev/net/ipro1000/0: media change, media 0x20 quality 1000 speed 1000000000
vm_soft_fault: va 0xd3000000 not covered by area in address space
vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0xd3000000, ip 0x80091f9d, write 1, user 0, thread 0x14d

comment:8 by diver, 9 years ago

Blocking: 12323 added

(In #12323) Most likely a duplicate of #2539.

comment:9 by pulkomandy, 8 years ago

Blocking: 12749 added

(In #12749) Thanks, closing as duplicate of the 2 others then.

Note: See TracTickets for help on using tickets.