Pre-defined Queries

Custom Query (12003 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (61 - 63 of 12003)

Ticket Resolution Summary Owner Reporter
#77 fixed unhandled page fault while trying to sync axeld stippi
Description
  • set a background image for the current workspace using Backgrounds, noticed

that Tracker didn't pick it up

  • quitted Tracker through the all-modifiers+q shortcut
  • Tracker didn't quit fully, tried to kill it
  • that didn't work so I synced in the Terminal and rebooted by using the KDL

since Tracker didn't quit and the normal shutdown would not proceed

  • on next boot, I relaunched Backgrounds... the image was not remembered, I

reset it, Tracker didn't pick it up again

  • when trying to sync... the system KDLd:

PANIC vm_page_fault: unhandled page fault in kernel space at 0xc, ip 0x80050351 sc: <kernel> ChunkIndex_11block_rangeP11block_cachePv + 0x000d <kernel> Free_11block_rangeP11block_cachePv + 0x001d <kernel> Free_11block_cachePv + 0x002a <kernel> cache_end_transaction + 0x00f0

<bfs> _WriteTransactionToLog7Journal + 0x070f <bfs> FlushLogAndBlocks7Journal + 0x010f <bfs> Sync6Volume + 0x0018 <bfs> bfs_syncFPv + 0x0016

<kernel> fs_syncF1 + 0x004d <kernel> _kern_sync + 0x001d <kernel> _user_sync + 0x000b <kernel> syscall_dispatcher

#79 fixed Unable to boot HD image: bfs_access:1329: Operation not allowed axeld a.mottola@…
Description

Trying to build my first HD image in about three years of absence from the scene, and I'm experimenting this bug while booting a fresh new image under QEMU on R5: the system starts, I see the boot logo, but then the debug output blocks at this point (I report the lines above too for clarity):

[...] vesa_get_frame_buffer_config() loaded driver /boot/beos/system/add-ons/kernel/drivers/dev/input/ps2_hid ps2_hid: keyboard: buffer not available! bfs: bfs_access:1329: Operation not allowed bfs: bfs_access:1329: Operation not allowed bfs: bfs_access:1329: Operation not allowed bfs: bfs_access:1329: Operation not allowed bfs: bfs_access:1329: Operation not allowed bfs: bfs_access:1329: Operation not allowed bfs: bfs_access:1329: Operation not allowed bfs: bfs_access:1329: Operation not allowed bfs: bfs_access:1329: Operation not allowed bfs: bfs_access:1329: Operation not allowed bfs: bfs_access:1329: Operation not allowed bfs: bfs_access:1329: Operation not allowed vm_soft_fault: va 0x0 not covered by area in address space vm_page_fault: vm_soft_fault returned error -2147478783 on fault at 0x0, ip 0x28afe4, write 1, user 1, thread 0x41 vm_page_fault: sending team "/boot/beos/apps/Terminal" 0x29 SIGSEGV, ip 0x28afe4 ("libroot.so_seg0ro" +0x5cfe4)

Nothing more happens. If I download a prebuilt HD image the same happens, whereas the same image boots just fine under VMWare on WinXP. This leads me to believe it may be a BeOS issue; I'm running an Athlon64 3000. Not sure though so I thought this was worth a bug report...

#80 fixed Terminal hangs on large console output axeld a.mottola@…
Description

If a commandline app that outputs a lot of text is launched from the Terminal, the Terminal itself hangs, hogging most of the CPU. Killing the Terminal doesn't seem to work, the system is just slow as hell due to the CPU hog. You can reproduce the problem by launching listsem or listarea for example. The problem doesn't exist if these apps are launched from the fake_app_server/consoled combo.

Note: See TracQuery for help on using queries.