From trac at haiku-os.org Sat Mar 1 00:53:13 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 29 Feb 2008 23:53:13 -0000 Subject: [Haiku-bugs] [Haiku] #1854: bcm570x driver (GPL) hangs after short period, panics on 'ifconfig --delete' In-Reply-To: <047.72dd8070740df6d55edb31b47fe56576@haiku-os.org> References: <047.72dd8070740df6d55edb31b47fe56576@haiku-os.org> Message-ID: <056.c7fe2e4b16f907440343d45709dbfb72@haiku-os.org> #1854: bcm570x driver (GPL) hangs after short period, panics on 'ifconfig --delete' ---------------------------------+------------------------------------------ Reporter: vortechs2000 | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Resolution: | Platform: x86 ---------------------------------+------------------------------------------ Comment (by vortechs2000): Things appear to be stable for me now too, at least with the network and usb drivers. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 1 07:48:24 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 01 Mar 2008 06:48:24 -0000 Subject: [Haiku-bugs] [Haiku] #1877: Dropdown menu not clickable on all it's surface In-Reply-To: <041.0b1f85cac5c42bee3ea96676fd79151a@haiku-os.org> References: <041.0b1f85cac5c42bee3ea96676fd79151a@haiku-os.org> Message-ID: <050.f25d52bfd5f18d7bb39e83366de5a90f@haiku-os.org> #1877: Dropdown menu not clickable on all it's surface ---------------------------------+------------------------------------------ Reporter: aldeck | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by diver): Let's keep this one. :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 1 09:09:15 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 01 Mar 2008 08:09:15 -0000 Subject: [Haiku-bugs] [Haiku] #1136: replace category module with taxonomies and views In-Reply-To: <045.8647c52a4291f7398749aed9a9acc84e@haiku-os.org> References: <045.8647c52a4291f7398749aed9a9acc84e@haiku-os.org> Message-ID: <054.c108a46ec4f84caf0a1aff7697525bff@haiku-os.org> #1136: replace category module with taxonomies and views --------------------------+------------------------------------------------- Reporter: wkornewald | Owner: haiku-web Type: bug | Status: new Priority: normal | Milestone: Website R2 Component: Website/CMS | Version: Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by nielx): Is this task still relevant? Maybe the 4.x version was buggy, but the module is still developed. Could someone enlighten me why this change would be beneficial? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 1 09:32:49 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 01 Mar 2008 08:32:49 -0000 Subject: [Haiku-bugs] [Haiku] #1879: Cannot create hard link Message-ID: <042.19670a26e8a2a1da7dc5cb3cf061dd9e@haiku-os.org> #1879: Cannot create hard link ---------------------------+------------------------------------------------ Reporter: kaliber | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Platform: All | ---------------------------+------------------------------------------------ {{{ ~>touch t1 ~>ln t1 t2 /bin/ls: creating hard link `t2' => `t1': General system error }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 1 11:08:48 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 01 Mar 2008 10:08:48 -0000 Subject: [Haiku-bugs] [Haiku] #1879: Cannot create hard link In-Reply-To: <042.19670a26e8a2a1da7dc5cb3cf061dd9e@haiku-os.org> References: <042.19670a26e8a2a1da7dc5cb3cf061dd9e@haiku-os.org> Message-ID: <051.6620d8f6514d5f0fae32e427651a0917@haiku-os.org> #1879: Cannot create hard link -------------------------------+-------------------------------------------- Reporter: kaliber | Owner: axeld Type: bug | Status: new Priority: low | Milestone: Unscheduled Component: File Systems/BFS | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Changes (by axeld): * priority: normal => low * component: System/Kernel => File Systems/BFS * milestone: R1 => Unscheduled Comment: That's no surprise as BFS cannot support hard links due to its on disk representation. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 1 11:23:04 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 01 Mar 2008 10:23:04 -0000 Subject: [Haiku-bugs] [Haiku] #1848: [InterfaceKit] down arrow doesn't work in Screen prefs In-Reply-To: <040.1abd894d7ca66e23d5c2833e7b37d47c@haiku-os.org> References: <040.1abd894d7ca66e23d5c2833e7b37d47c@haiku-os.org> Message-ID: <049.27d55507027e4be27103c1480fe7ce66@haiku-os.org> #1848: [InterfaceKit] down arrow doesn't work in Screen prefs ------------------------------+--------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Kernel Kit | Version: R1 development Resolution: duplicate | Platform: All ------------------------------+--------------------------------------------- Changes (by aldeck): * status: new => closed * resolution: => duplicate Comment: duplicate of #1877 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 1 12:47:02 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 01 Mar 2008 11:47:02 -0000 Subject: [Haiku-bugs] [Haiku] #1880: Wrong default folder for 'Other' background images (super easy) Message-ID: <044.fc4e9e5e8cb3dbf119a3f2884ad76ac5@haiku-os.org> #1880: Wrong default folder for 'Other' background images (super easy) -------------------------+-------------------------------------------------- Reporter: meanwhile | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -------------------------+-------------------------------------------------- ATM it's /boot/home, whereas the right folder is /boot/beos/etc/artwork. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 1 16:42:34 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 01 Mar 2008 15:42:34 -0000 Subject: [Haiku-bugs] [Haiku] #1136: replace category module with taxonomies and views In-Reply-To: <045.8647c52a4291f7398749aed9a9acc84e@haiku-os.org> References: <045.8647c52a4291f7398749aed9a9acc84e@haiku-os.org> Message-ID: <054.5a388eb952a4c81f09b49576afbd8063@haiku-os.org> #1136: replace category module with taxonomies and views --------------------------+------------------------------------------------- Reporter: wkornewald | Owner: haiku-web Type: bug | Status: new Priority: normal | Milestone: Website R2 Component: Website/CMS | Version: Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by koki): The category module (http://drupal.org/project/category) is still buggy, and its development has not been very active. Although it is working OK in our current setup, it would be safer and wise (maybe even necessary?) to replace it when upgrading to Drupal 5.x. Might be tricky though. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 1 18:54:30 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 01 Mar 2008 17:54:30 -0000 Subject: [Haiku-bugs] [Haiku] #1136: replace category module with taxonomies and views In-Reply-To: <045.8647c52a4291f7398749aed9a9acc84e@haiku-os.org> References: <045.8647c52a4291f7398749aed9a9acc84e@haiku-os.org> Message-ID: <054.62b18fef9639279d153ca664abcb5524@haiku-os.org> #1136: replace category module with taxonomies and views --------------------------+------------------------------------------------- Reporter: wkornewald | Owner: haiku-web Type: bug | Status: new Priority: normal | Milestone: Website R2 Component: Website/CMS | Version: Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by wkornewald): Replying to [comment:4 koki]: > The category module (http://drupal.org/project/category) is still buggy, and its development has not been very active. Although it is working OK in our current setup, it would be safer and wise (maybe even necessary?) to replace it when upgrading to Drupal 5.x. Might be tricky though. You mean Drupal 6. You're running crusty old technology. Hopefully it won't fall apart too soon. ;) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 1 19:33:05 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 01 Mar 2008 18:33:05 -0000 Subject: [Haiku-bugs] [Haiku] #1136: replace category module with taxonomies and views In-Reply-To: <045.8647c52a4291f7398749aed9a9acc84e@haiku-os.org> References: <045.8647c52a4291f7398749aed9a9acc84e@haiku-os.org> Message-ID: <054.39d6bbb85b8cbe805a1c5df5f75c8a4a@haiku-os.org> #1136: replace category module with taxonomies and views --------------------------+------------------------------------------------- Reporter: wkornewald | Owner: haiku-web Type: bug | Status: new Priority: normal | Milestone: Website R2 Component: Website/CMS | Version: Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by koki): Hi Waldemar. Good to hear from you. :) > You mean Drupal 6. No, I said and meant Drupal 5. I don't know what whoever takes up this task will end up doing, but the initial plan as we talked it with Gavin was to migrate to Drupal 5 first, as Drupal 6 is still missing some modules that we need (including some important ones like Views and CCK). > You're running crusty old technology. Hopefully it won't fall apart too soon. I see no reason why it should fall apart. And new does not necessarily mean better: as of lately, our crusty old Drupal 4.x has for the most part had less problems than Trac, which is supposed to be state of the art technology, right? :P Anyway, as far as I am concerned, you guys feel free to fix/improve/enhance/whatever the website. :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 1 23:16:05 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 01 Mar 2008 22:16:05 -0000 Subject: [Haiku-bugs] [Haiku] #284: BMenu needs diagonal mouse movement support (easy) In-Reply-To: <043.67d09c50fc4e2eee125867b96349314c@haiku-os.org> References: <043.67d09c50fc4e2eee125867b96349314c@haiku-os.org> Message-ID: <052.017e80232b6471a7dfe504ff522a797c@haiku-os.org> #284: BMenu needs diagonal mouse movement support (easy) ---------------------------------+------------------------------------------ Reporter: darkwyrm | Owner: jackburton Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: Resolution: fixed | Platform: All ---------------------------------+------------------------------------------ Changes (by jackburton): * status: new => closed * resolution: => fixed Comment: Applied in r24193. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 1 23:21:21 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 01 Mar 2008 22:21:21 -0000 Subject: [Haiku-bugs] [Haiku] #1881: libc locale functions not implemented Message-ID: <045.97ac8b64c17b4be5c49b3c334028da7b@haiku-os.org> #1881: libc locale functions not implemented ------------------------+--------------------------------------------------- Reporter: jackburton | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | ------------------------+--------------------------------------------------- Our locale methods aren't implemented correctly. Moreover, glibc wide needs glibc's own locale stuff, since they use a lot of private methods. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 1 23:24:07 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 01 Mar 2008 22:24:07 -0000 Subject: [Haiku-bugs] [Haiku] #1855: Glibc wide char functions are disabled In-Reply-To: <045.34bab0da7c7771105187bde6b57a07a9@haiku-os.org> References: <045.34bab0da7c7771105187bde6b57a07a9@haiku-os.org> Message-ID: <054.be0c4e0d0b261702cb631c150b0b9cc6@haiku-os.org> #1855: Glibc wide char functions are disabled --------------------------------+------------------------------------------- Reporter: jackburton | Owner: jackburton Type: bug | Status: assigned Priority: high | Milestone: R1/alpha1 Component: System/libroot.so | Version: R1 development Resolution: | Platform: All --------------------------------+------------------------------------------- Comment (by jackburton): depends on #1881. By the way, don't we have bug dependency tracking ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 2 01:10:15 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 02 Mar 2008 00:10:15 -0000 Subject: [Haiku-bugs] [Haiku] #1865: [StyledEdit] Copying large text into the Clipboard crash StyledEdit In-Reply-To: <038.d831d337a916e15e74e461f7a608f19a@haiku-os.org> References: <038.d831d337a916e15e74e461f7a608f19a@haiku-os.org> Message-ID: <047.42832637af2deab9024d31a93cf3324e@haiku-os.org> #1865: [StyledEdit] Copying large text into the Clipboard crash StyledEdit --------------------------------------+------------------------------------- Reporter: oco | Owner: korli Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/StyledEdit | Version: R1 development Resolution: fixed | Platform: All --------------------------------------+------------------------------------- Changes (by julun): * status: new => closed * resolution: => fixed Comment: fixed in r24196 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 2 01:44:09 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 02 Mar 2008 00:44:09 -0000 Subject: [Haiku-bugs] [Haiku] #1882: "Subscribe to Haiku Daily RSS feed" in Download page is broken Message-ID: <039.ae72c19fa6bc693a5696828bb215f31d@haiku-os.org> #1882: "Subscribe to Haiku Daily RSS feed" in Download page is broken -------------------------+-------------------------------------------------- Reporter: koki | Owner: haiku-web Type: bug | Status: new Priority: normal | Milestone: R1 Component: Website/CMS | Version: R1 development Platform: All | -------------------------+-------------------------------------------------- The "Subscribe to Haiku Daily RSS feed" in the "Raw HDD images" of the Downloads page in the website (http://www.haiku-os.org/downloads) is broken. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 2 01:58:54 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 02 Mar 2008 00:58:54 -0000 Subject: [Haiku-bugs] [Haiku] #1882: "Subscribe to Haiku Daily RSS feed" in Download page is broken In-Reply-To: <039.ae72c19fa6bc693a5696828bb215f31d@haiku-os.org> References: <039.ae72c19fa6bc693a5696828bb215f31d@haiku-os.org> Message-ID: <048.840f15a513ce50cdd70d8f99943e6857@haiku-os.org> #1882: "Subscribe to Haiku Daily RSS feed" in Download page is broken --------------------------+------------------------------------------------- Reporter: koki | Owner: haiku-web Type: bug | Status: new Priority: normal | Milestone: R1 Component: Website/CMS | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by miqlas): Working link: http://www.wotzwot.com/rssxl.php?pageurl=http%3A%2F%2Fhaiku- files.org%2Fraw%2Findex.php%3Fdir%3D%26sort%3Dname%26order%3Ddesc&sf=Raw+Images&si=%3Ctd+class%3D%27clsItem%27%3E&ei=%3C%2Fa%3E%3C%2Ftd%3E%3C%2Ftr%3E&sd=&ed=&linkno=1 miqlas -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 2 09:47:01 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 02 Mar 2008 08:47:01 -0000 Subject: [Haiku-bugs] [Haiku] #1883: Showing available jam targets Message-ID: <042.1a7d21a53a0c47625482a925e857c7c9@haiku-os.org> #1883: Showing available jam targets --------------------------+------------------------------------------------- Reporter: kaliber | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Platform: All | --------------------------+------------------------------------------------- As I know there is no way to display available jam targets. It would be nice to have "help" target. {{{ jam -q help Available targets: haiku-image haiku-vmware-image ... }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 2 11:36:19 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 02 Mar 2008 10:36:19 -0000 Subject: [Haiku-bugs] [Haiku] #347: Imposible to boot from CD In-Reply-To: <054.b7543cd2da05e105ad49b5d2c2877e4d@haiku-os.org> References: <054.b7543cd2da05e105ad49b5d2c2877e4d@haiku-os.org> Message-ID: <063.2ecc06c95a40336baa6ab58abeb06643@haiku-os.org> #347: Imposible to boot from CD ----------------------------------+----------------------------------------- Reporter: daneel at rootshell.be | Owner: axeld Type: bug | Status: reopened Priority: high | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------------+----------------------------------------- Changes (by nielx): * priority: normal => high * version: => R1 development * milestone: R1 => R1/alpha1 Comment: Moving to Alpha 1 milestone. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 2 14:02:54 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 02 Mar 2008 13:02:54 -0000 Subject: [Haiku-bugs] [Haiku] #1884: Rebooting from the deskbar in haiku freeze my laptop (Acer Aspire 1510) Message-ID: <038.8605ee161ded506635ad0543996648aa@haiku-os.org> #1884: Rebooting from the deskbar in haiku freeze my laptop (Acer Aspire 1510) ---------------------------+------------------------------------------------ Reporter: oco | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Platform: x86 | ---------------------------+------------------------------------------------ There is the same problem when i shutdown this computer and i click on the restart button : the mouse cursor freeze. Here is a patch to fix this problem (see attachment) I use a snooze command after sending the reboot command to the keyboard controller. I propose to use the same delay as in FreeBSD (500000 microseconds). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 2 14:51:44 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 02 Mar 2008 13:51:44 -0000 Subject: [Haiku-bugs] [Haiku] #1884: Rebooting from the deskbar in haiku freeze my laptop (Acer Aspire 1510) In-Reply-To: <038.8605ee161ded506635ad0543996648aa@haiku-os.org> References: <038.8605ee161ded506635ad0543996648aa@haiku-os.org> Message-ID: <047.626f9df73a4673a99b162af3dfa94b9c@haiku-os.org> #1884: Rebooting from the deskbar in haiku freeze my laptop (Acer Aspire 1510) ----------------------------+----------------------------------------------- Reporter: oco | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Platform: x86 ----------------------------+----------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Applied in r24202, thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 2 17:20:48 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 02 Mar 2008 16:20:48 -0000 Subject: [Haiku-bugs] [Haiku] #1763: [Cortex] System Clock element have black icon In-Reply-To: <040.f9e6f8eafa7490c9c239c6b00cdb0dfb@haiku-os.org> References: <040.f9e6f8eafa7490c9c239c6b00cdb0dfb@haiku-os.org> Message-ID: <049.109f32706e88b5a8069a579d233ce00c@haiku-os.org> #1763: [Cortex] System Clock element have black icon ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by axeld): Situation improved with r24205. Thanks, Maurice! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 2 21:01:41 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 02 Mar 2008 20:01:41 -0000 Subject: [Haiku-bugs] [Haiku] #957: after boot; kernel: PANIC vm_page_fault: unhandled page fault in kernel space at 0xcccccd44, ip 0x9070fdda In-Reply-To: <041.8428184657b4fba8f0ad6ac03265440a@haiku-os.org> References: <041.8428184657b4fba8f0ad6ac03265440a@haiku-os.org> Message-ID: <050.4e3fb9451f7eefca5787f970d218a645@haiku-os.org> #957: after boot; kernel: PANIC vm_page_fault: unhandled page fault in kernel space at 0xcccccd44, ip 0x9070fdda ----------------------------+----------------------------------------------- Reporter: nutela | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: invalid | Platform: x86 ----------------------------+----------------------------------------------- Comment (by nutela): OK didn't experience this bug, with rev 24195, sorry for the delay. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 2 21:06:26 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 02 Mar 2008 20:06:26 -0000 Subject: [Haiku-bugs] [Haiku] #1203: mutliple issues with usb stack revision 22130 In-Reply-To: <041.a998994b38b90fc6acdc0bd1164ac15d@haiku-os.org> References: <041.a998994b38b90fc6acdc0bd1164ac15d@haiku-os.org> Message-ID: <050.f5d58517487bee386cf9c52262cd86c4@haiku-os.org> #1203: mutliple issues with usb stack revision 22130 --------------------------+------------------------------------------------- Reporter: nutela | Owner: mmlr Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: x86 --------------------------+------------------------------------------------- Comment (by nutela): OK tested now in Haiku rev 24195 on real hw and keys are still virtually stuck when I type 1 or more key fast after the other (fast typing), the last key is stuck. This is a wireless keyboard (logitech mx 3200 keyb and mouse). The mouse won't get recognized (no change thus far). Any ideas which I can test/get more output? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 2 22:25:30 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 02 Mar 2008 21:25:30 -0000 Subject: [Haiku-bugs] [Haiku] #1732: autodetecting resolution does not work for some grafix boards In-Reply-To: <041.f80704f6eca5f056dca0e5ca1f18a602@haiku-os.org> References: <041.f80704f6eca5f056dca0e5ca1f18a602@haiku-os.org> Message-ID: <050.22c91639cd09b7a6cf37738295cf60e7@haiku-os.org> #1732: autodetecting resolution does not work for some grafix boards ---------------------------------+------------------------------------------ Reporter: stippi | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: Servers/app_server | Version: R1 development Resolution: | Platform: x86 ---------------------------------+------------------------------------------ Comment (by axeld): I would think the bug happens because of the dual link card stippi has, while Marcus is using that resolution with a single link card. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 2 22:25:52 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 02 Mar 2008 21:25:52 -0000 Subject: [Haiku-bugs] [Haiku] #1836: OpenGL output not visible on screenshots In-Reply-To: <041.35c11d2f8648ac43478bc54b950533aa@haiku-os.org> References: <041.35c11d2f8648ac43478bc54b950533aa@haiku-os.org> Message-ID: <050.a810f3badc04a35912abb130a6c1d2ba@haiku-os.org> #1836: OpenGL output not visible on screenshots ------------------------------+--------------------------------------------- Reporter: ekdahl | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/OpenGL Kit | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by korli): VESA mode ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 2 22:41:34 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 02 Mar 2008 21:41:34 -0000 Subject: [Haiku-bugs] [Haiku] #1836: OpenGL output not visible on screenshots In-Reply-To: <041.35c11d2f8648ac43478bc54b950533aa@haiku-os.org> References: <041.35c11d2f8648ac43478bc54b950533aa@haiku-os.org> Message-ID: <050.fa650d466e28466ab13d2d50d8edd10f@haiku-os.org> #1836: OpenGL output not visible on screenshots ------------------------------+--------------------------------------------- Reporter: ekdahl | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/OpenGL Kit | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by ekdahl): 1280 x 1024 x 16/32 (32 after the default changed) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 3 00:18:58 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 02 Mar 2008 23:18:58 -0000 Subject: [Haiku-bugs] [Haiku] #1829: BFS mounts CDs read-write for some reason In-Reply-To: <040.ece049f2fc4edce4b72d5358ca86c075@haiku-os.org> References: <040.ece049f2fc4edce4b72d5358ca86c075@haiku-os.org> Message-ID: <049.646ed2dee4ee554f01baa2aaa9992caa@haiku-os.org> #1829: BFS mounts CDs read-write for some reason -------------------------------+-------------------------------------------- Reporter: axeld | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1/alpha1 Component: File Systems/BFS | Version: R1 development Resolution: fixed | Platform: All -------------------------------+-------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed * component: System/Kernel => File Systems/BFS Comment: Fixed in r24212. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 3 00:19:52 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 02 Mar 2008 23:19:52 -0000 Subject: [Haiku-bugs] [Haiku] #1364: Bootloader can't find boot volume, booting from cd In-Reply-To: <041.ff14f133560c18c550bdf6a3c705c6c8@haiku-os.org> References: <041.ff14f133560c18c550bdf6a3c705c6c8@haiku-os.org> Message-ID: <050.d8cc1ddf52ae7560e025319fa60454eb@haiku-os.org> #1364: Bootloader can't find boot volume, booting from cd ---------------------------------+------------------------------------------ Reporter: aldeck | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: System/Boot Loader | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by mmu_man): Ok, r24211 fixes loading of modules from the floppy. It still doesn't find the partition though. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 3 04:39:18 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 03 Mar 2008 03:39:18 -0000 Subject: [Haiku-bugs] [Haiku] #1885: find KDLs when searching iso9660 dvd Message-ID: <042.dccdac296a799b1a691dd7ee32cd9aaf@haiku-os.org> #1885: find KDLs when searching iso9660 dvd -----------------------+---------------------------------------------------- Reporter: qyellow | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- from command line running find /mounteddvd filename ends in KDL error message: PANIC: free(): free failed for address 0x800260bd has semaphore (blocked) from scsi bus service it will have printed out a list of where it has checked, a couple hundred maybe. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 3 10:48:36 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 03 Mar 2008 09:48:36 -0000 Subject: [Haiku-bugs] [Haiku] #1885: find KDLs when searching iso9660 dvd In-Reply-To: <042.dccdac296a799b1a691dd7ee32cd9aaf@haiku-os.org> References: <042.dccdac296a799b1a691dd7ee32cd9aaf@haiku-os.org> Message-ID: <051.4c618ebc24ca173ec98ab89a3c1c8edd@haiku-os.org> #1885: find KDLs when searching iso9660 dvd ------------------------+--------------------------------------------------- Reporter: qyellow | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by axeld): I'm not sure I do not understand: * You put a ISO-9660 DVD in your driver * then you get a crash (free() failed...), right? * How does the semaphore (blocked) come into play? Is it a DVD you burned yourself or one that I could buy in a shop? If it's the latter, which one? I haven't seen such a crash. BTW which revision are you using? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 3 10:49:56 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 03 Mar 2008 09:49:56 -0000 Subject: [Haiku-bugs] [Haiku] #1885: find KDLs when searching iso9660 dvd In-Reply-To: <042.dccdac296a799b1a691dd7ee32cd9aaf@haiku-os.org> References: <042.dccdac296a799b1a691dd7ee32cd9aaf@haiku-os.org> Message-ID: <051.41fcbf7d6feeaa87b7403e28792c4a6a@haiku-os.org> #1885: find KDLs when searching iso9660 dvd ------------------------+--------------------------------------------------- Reporter: qyellow | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by mmlr): This probably is a double free somewhere. Can you please execute the "sc" command in KDL and post here what it prints? Also this is a "continuable" error, you should be able to go further by using "cont" in KDL. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 3 11:13:00 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 03 Mar 2008 10:13:00 -0000 Subject: [Haiku-bugs] [Haiku] #1886: Terminal won't get focus back after quiting app launched from Terminal Message-ID: <041.c23a06a139b1e0b6118a0c219e3653e8@haiku-os.org> #1886: Terminal won't get focus back after quiting app launched from Terminal ----------------------------+----------------------------------------------- Reporter: nutela | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Platform: x86 | ----------------------------+----------------------------------------------- Rev 24195 Set Mouse prefs to FFM with Warping. Start Terminal. Type Workspaces enter. Workspaces is started and get's focus (note mouse cursor stays -> bug, will file a another bug just for this), Press alt-w, Workspaces quits, mouse cursor is still above Terminal window but Terminal's tab is gray and not yellow -> bug. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 3 11:17:41 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 03 Mar 2008 10:17:41 -0000 Subject: [Haiku-bugs] [Haiku] #1887: ctrl-tab: mouse cursor is not warped Message-ID: <041.46821c847840264592c3723869ab46fc@haiku-os.org> #1887: ctrl-tab: mouse cursor is not warped ----------------------------+----------------------------------------------- Reporter: nutela | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Platform: x86 | ----------------------------+----------------------------------------------- Rev 24195 Have more then 1 window open. In mouse prefs set to FFM and Warping. Press ctrl-tab, and select other window, other window gets focus, mouse cursor is not warped but stays on the previous window which had focus -> bug -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 3 11:21:52 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 03 Mar 2008 10:21:52 -0000 Subject: [Haiku-bugs] [Haiku] #1888: Terminal selecting (text) redraws very often= high cpu load+tearing Message-ID: <041.194ced3bd42ba2b954e4d3ac161774d0@haiku-os.org> #1888: Terminal selecting (text) redraws very often= high cpu load+tearing -----------------------------------+---------------------------------------- Reporter: nutela | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Platform: x86 | -----------------------------------+---------------------------------------- Open Terminal, click and drag mouse (selecting) note how the selection gets redrawn multiple times in a loop, note tearing, note high cpu load. -> bug -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 3 11:23:40 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 03 Mar 2008 10:23:40 -0000 Subject: [Haiku-bugs] [Haiku] #1888: Terminal selecting (text) redraws very often= high cpu load+tearing In-Reply-To: <041.194ced3bd42ba2b954e4d3ac161774d0@haiku-os.org> References: <041.194ced3bd42ba2b954e4d3ac161774d0@haiku-os.org> Message-ID: <050.4ceb1e3eccc6dcae004d3a152bcfb2d9@haiku-os.org> #1888: Terminal selecting (text) redraws very often= high cpu load+tearing ------------------------------------+--------------------------------------- Reporter: nutela | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Resolution: | Platform: x86 ------------------------------------+--------------------------------------- Comment (by nutela): Replying to [ticket:1888 nutela]: > Open Terminal, click and drag mouse (selecting) note while left mouse button is clicked how the selection gets redrawn multiple times in a loop , note tearing, note high cpu load. -> bug -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 3 12:16:26 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 03 Mar 2008 11:16:26 -0000 Subject: [Haiku-bugs] [Haiku] #1889: USB plugs on IBM T60 docking station do not work Message-ID: <041.77f36565f665fa528021d2ef48b05963@haiku-os.org> #1889: USB plugs on IBM T60 docking station do not work -------------------------+-------------------------------------------------- Reporter: stippi | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Platform: All | -------------------------+-------------------------------------------------- I don't know where this bug might originate, maybe it's something with device management in general. The laptop is already plugged in the docking station, and for example the network cable needs to be plugged there, the plug on the laptop is then non functional. But USB devices have to be plugged in directly on the laptop, the docking station plugs do not work. I am trying to hook my KVM switch there (have not tried anything else yet), which is like another hub. If I need to supply any more info, please let me know. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 3 12:31:25 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 03 Mar 2008 11:31:25 -0000 Subject: [Haiku-bugs] [Haiku] #1889: USB plugs on IBM T60 docking station do not work In-Reply-To: <041.77f36565f665fa528021d2ef48b05963@haiku-os.org> References: <041.77f36565f665fa528021d2ef48b05963@haiku-os.org> Message-ID: <050.c5233a0584ff91d8021a7ef39efba04f@haiku-os.org> #1889: USB plugs on IBM T60 docking station do not work --------------------------+------------------------------------------------- Reporter: stippi | Owner: mmlr Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Changes (by mmlr): * status: new => assigned Comment: Do you have any relevant syslog information? I don't know how exactly the docking station works. Maybe it is a separate controller that is somehow hot-plugged in or it is just a hub that links to a present port. If you have any other OS on the laptop you could try to find the topology when docked and undocked to see what really happens (lsusb under Linux or the device manager under Windows). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 3 15:20:54 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 03 Mar 2008 14:20:54 -0000 Subject: [Haiku-bugs] [Haiku] #1732: autodetecting resolution does not work for some grafix boards In-Reply-To: <041.f80704f6eca5f056dca0e5ca1f18a602@haiku-os.org> References: <041.f80704f6eca5f056dca0e5ca1f18a602@haiku-os.org> Message-ID: <050.9bf893ecb5d134c5319dd9a3b5bf10f8@haiku-os.org> #1732: autodetecting resolution does not work for some grafix boards ---------------------------------+------------------------------------------ Reporter: stippi | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: Servers/app_server | Version: R1 development Resolution: | Platform: x86 ---------------------------------+------------------------------------------ Comment (by stippi): I am on single link as well. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 3 16:42:49 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 03 Mar 2008 15:42:49 -0000 Subject: [Haiku-bugs] [Haiku] #1889: USB plugs on IBM T60 docking station do not work In-Reply-To: <041.77f36565f665fa528021d2ef48b05963@haiku-os.org> References: <041.77f36565f665fa528021d2ef48b05963@haiku-os.org> Message-ID: <050.eab6e5389380f9cad01751ba86d14e80@haiku-os.org> #1889: USB plugs on IBM T60 docking station do not work --------------------------+------------------------------------------------- Reporter: stippi | Owner: mmlr Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by stippi): I have attached some hopefully interesting lsusb output. The Haiku syslog output will come later. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 3 18:02:06 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 03 Mar 2008 17:02:06 -0000 Subject: [Haiku-bugs] [Haiku] #1889: USB plugs on IBM T60 docking station do not work In-Reply-To: <041.77f36565f665fa528021d2ef48b05963@haiku-os.org> References: <041.77f36565f665fa528021d2ef48b05963@haiku-os.org> Message-ID: <050.903d4ee4fe615cee369f2642c324d010@haiku-os.org> #1889: USB plugs on IBM T60 docking station do not work --------------------------+------------------------------------------------- Reporter: stippi | Owner: mmlr Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by meanwhile): Some info that may be relevant, may be confusing or may be a waste of time: http://beosmeanwhilehaiku.wordpress.com/2006/08/28/beos-docking-stations- and-usb-2/ -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 3 18:40:41 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 03 Mar 2008 17:40:41 -0000 Subject: [Haiku-bugs] [Haiku] #1885: find KDLs when searching iso9660 dvd In-Reply-To: <042.dccdac296a799b1a691dd7ee32cd9aaf@haiku-os.org> References: <042.dccdac296a799b1a691dd7ee32cd9aaf@haiku-os.org> Message-ID: <051.fc527f7eea1a046bf4e2e07611aadc29@haiku-os.org> #1885: find KDLs when searching iso9660 dvd ------------------------+--------------------------------------------------- Reporter: qyellow | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by qyellow): this is happening on revision 24212. (also previous revisions) I can access the DVD fine and copy over files etc without problem. I out in the DVD mount it, got to terminal enter find /DG *.avi it prints out a list of a couple hundred entries of where it has searched ( the DVD has a couple thousand files ) and the KDLs witht he previous free() error. It is a DVD that I burned there is no problems with the DVD, it is a back up of home directory on linux. try and get the sc text in a bit. when I run cont it goes back to KDL with error: vm_page_fault: unhandled page fault in kernel space at 0x0, ip 0x8009a0ed -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 3 19:47:17 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 03 Mar 2008 18:47:17 -0000 Subject: [Haiku-bugs] [Haiku] #1655: vm_page_fault on boot (probably because intel_extreme driver) In-Reply-To: <046.9691dd7df16109140134e321a67e4696@haiku-os.org> References: <046.9691dd7df16109140134e321a67e4696@haiku-os.org> Message-ID: <055.191c642e8642f5a800e86bbdbf85a43e@haiku-os.org> #1655: vm_page_fault on boot (probably because intel_extreme driver) ---------------------------------------------+------------------------------ Reporter: mzunigag_mx | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1/alpha1 Component: Drivers/Graphics/intel_extreme | Version: R1 development Resolution: fixed | Platform: x86 ---------------------------------------------+------------------------------ Comment (by mzunigag_mx): Since r23591 there are no errors at all. It's been quite a long time, so i considered to thank you all again for this fixing. Even the mouse now leaves no track when drag and dropping a rectangle over the desktop. It renders very nicely, with all possible resolutions. Congratulations! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 3 22:12:25 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 03 Mar 2008 21:12:25 -0000 Subject: [Haiku-bugs] [Haiku] #1711: Haiku stops booting at allocate_commpage_entry(4, 34) In-Reply-To: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> References: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> Message-ID: <048.e5b20e5498821d34b6c37cc8a1035113@haiku-os.org> #1711: Haiku stops booting at allocate_commpage_entry(4, 34) ----------------------------+----------------------------------------------- Reporter: euan | Owner: mmlr Type: bug | Status: new Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by korli): Reproduced on a Core2Duo 3GB. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 3 23:19:27 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 03 Mar 2008 22:19:27 -0000 Subject: [Haiku-bugs] [Haiku] #1732: autodetecting resolution does not work for some grafix boards In-Reply-To: <041.f80704f6eca5f056dca0e5ca1f18a602@haiku-os.org> References: <041.f80704f6eca5f056dca0e5ca1f18a602@haiku-os.org> Message-ID: <050.c29417856dcaeef00022e87642d0b441@haiku-os.org> #1732: autodetecting resolution does not work for some grafix boards ---------------------------------+------------------------------------------ Reporter: stippi | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: Servers/app_server | Version: R1 development Resolution: | Platform: x86 ---------------------------------+------------------------------------------ Comment (by axeld): With a dual link card? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 3 23:29:05 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 03 Mar 2008 22:29:05 -0000 Subject: [Haiku-bugs] [Haiku] #1732: autodetecting resolution does not work for some grafix boards In-Reply-To: <041.f80704f6eca5f056dca0e5ca1f18a602@haiku-os.org> References: <041.f80704f6eca5f056dca0e5ca1f18a602@haiku-os.org> Message-ID: <050.9c48cfb8953919470cda6fdb097b8bf3@haiku-os.org> #1732: autodetecting resolution does not work for some grafix boards ---------------------------------+------------------------------------------ Reporter: stippi | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: Servers/app_server | Version: R1 development Resolution: | Platform: x86 ---------------------------------+------------------------------------------ Comment (by stippi): Why would I have a dual link card? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 3 23:54:44 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 03 Mar 2008 22:54:44 -0000 Subject: [Haiku-bugs] [Haiku] #1711: Haiku stops booting at allocate_commpage_entry(4, 34) In-Reply-To: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> References: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> Message-ID: <048.5cb7c2549119cd41b159ad1d447e04a5@haiku-os.org> #1711: Haiku stops booting at allocate_commpage_entry(4, 34) ----------------------------+----------------------------------------------- Reporter: euan | Owner: mmlr Type: bug | Status: new Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by korli): It actually fails in vm_init_post_modules(), just after a call to x86_set_mtrr(). set_memory_type called with : id = -1, base = 0, length = bfee0000, type = 0x50000000 allocate MTRR slot 0, base = 0, length = 100000000 on Linux : cat /proc/mtrr reg00: base=0x00000000 ( 0MB), size=2048MB: write-back, count=1 reg01: base=0x80000000 (2048MB), size=1024MB: write-back, count=1 reg02: base=0xbff00000 (3071MB), size= 1MB: uncachable, count=1 reg03: base=0xd0000000 (3328MB), size= 256MB: write-combining, count=1 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 4 02:10:41 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 04 Mar 2008 01:10:41 -0000 Subject: [Haiku-bugs] [Haiku] #1890: Haiku occasionally KDLs when accessing the net Message-ID: <039.15d61a84a280248ad5a5fa71f6e1bfe2@haiku-os.org> #1890: Haiku occasionally KDLs when accessing the net -----------------------------+---------------------------------------------- Reporter: koki | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Network | Version: R1 development Platform: All | -----------------------------+---------------------------------------------- Haiku occasionally KDLs when accessing the internet. Backtraces seem point to a problem in the RTL8169 driver. I am attaching three backtraces that occured when using different apps. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 4 02:15:56 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 04 Mar 2008 01:15:56 -0000 Subject: [Haiku-bugs] [Haiku] #1890: Haiku occasionally KDLs when accessing the net In-Reply-To: <039.15d61a84a280248ad5a5fa71f6e1bfe2@haiku-os.org> References: <039.15d61a84a280248ad5a5fa71f6e1bfe2@haiku-os.org> Message-ID: <048.d4523211e48dd22dd1f2cbb95ec79536@haiku-os.org> #1890: Haiku occasionally KDLs when accessing the net ------------------------------+--------------------------------------------- Reporter: koki | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Network | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Changes (by koki): * cc: bga (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 4 09:28:06 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 04 Mar 2008 08:28:06 -0000 Subject: [Haiku-bugs] [Haiku] #1268: Incorporation of the well known live cd scripts in the build. In-Reply-To: <043.0ec3b288215ac8d81edd1780fc68e6bc@haiku-os.org> References: <043.0ec3b288215ac8d81edd1780fc68e6bc@haiku-os.org> Message-ID: <052.91e61af31283925a120d6260693a4e9c@haiku-os.org> #1268: Incorporation of the well known live cd scripts in the build. ---------------------------+------------------------------------------------ Reporter: kaoutsis | Owner: bonefish Type: enhancement | Status: new Priority: blocker | Milestone: R1/alpha1 Component: Build System | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by jackburton): This has been done (by mmu_man). Closing ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 4 09:31:15 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 04 Mar 2008 08:31:15 -0000 Subject: [Haiku-bugs] [Haiku] #824: Booting from CD causes the floppy to constantly be polled In-Reply-To: <049.f76a2f3c01bcff3c5c5fb7411b6345c2@haiku-os.org> References: <049.f76a2f3c01bcff3c5c5fb7411b6345c2@haiku-os.org> Message-ID: <058.ec8edbcf0e9116de78888518a97388e7@haiku-os.org> #824: Booting from CD causes the floppy to constantly be polled -----------------------------+---------------------------------------------- Reporter: johndrinkwater | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: System/Kernel | Version: Resolution: | Platform: x86 -----------------------------+---------------------------------------------- Comment (by jackburton): Replying to [comment:6 aldeck]: > For what is worth, maybe i'm alone, but last time i was able to boot from cd was around summer 2006 iirc :) > It stops there for me -> #1364 Booting from a cd now works, since r24224. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 4 10:27:51 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 04 Mar 2008 09:27:51 -0000 Subject: [Haiku-bugs] [Haiku] #1732: autodetecting resolution does not work for some grafix boards In-Reply-To: <041.f80704f6eca5f056dca0e5ca1f18a602@haiku-os.org> References: <041.f80704f6eca5f056dca0e5ca1f18a602@haiku-os.org> Message-ID: <050.766eaad47d3162cee743d93b0ea98bc0@haiku-os.org> #1732: autodetecting resolution does not work for some grafix boards ---------------------------------+------------------------------------------ Reporter: stippi | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: Servers/app_server | Version: R1 development Resolution: | Platform: x86 ---------------------------------+------------------------------------------ Comment (by axeld): Because of your giant... monitor? :-) At least I remember overhearing a conversation between you and Marcus where he mentioned he would drive the same resolution you do with a single link card, where you said a dual link card would be needed for you. To drive that resolution with a single link card, your monitor and graphics card actually need to be able to reduce the blank time. But if you're using a single link card, that's probably a moot point anyway ;-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 4 10:33:18 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 04 Mar 2008 09:33:18 -0000 Subject: [Haiku-bugs] [Haiku] #1732: autodetecting resolution does not work for some grafix boards In-Reply-To: <041.f80704f6eca5f056dca0e5ca1f18a602@haiku-os.org> References: <041.f80704f6eca5f056dca0e5ca1f18a602@haiku-os.org> Message-ID: <050.4ee6d940b9a1a27a3a976665b2f82714@haiku-os.org> #1732: autodetecting resolution does not work for some grafix boards ---------------------------------+------------------------------------------ Reporter: stippi | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: Servers/app_server | Version: R1 development Resolution: | Platform: x86 ---------------------------------+------------------------------------------ Comment (by stippi): I remember the conversation vaguely, but I do have a single link card AFAIK. Marcus and I have the same resolution and it works by reducing the blank time indeed. I think I might have mentioned to Marcus about a monitor once built by IBM, which has four times the resolution at 22" (over 200 dpi?) and requires two dual links to even work at 24 fps refresh rate. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 4 10:48:37 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 04 Mar 2008 09:48:37 -0000 Subject: [Haiku-bugs] [Haiku] #1364: Bootloader can't find boot volume, booting from cd In-Reply-To: <041.ff14f133560c18c550bdf6a3c705c6c8@haiku-os.org> References: <041.ff14f133560c18c550bdf6a3c705c6c8@haiku-os.org> Message-ID: <050.c46d9815417a2b715d4953acc153df34@haiku-os.org> #1364: Bootloader can't find boot volume, booting from cd ---------------------------------+------------------------------------------ Reporter: aldeck | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: System/Boot Loader | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by jackburton): Can we close this ? It's working since r24224. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 4 10:57:54 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 04 Mar 2008 09:57:54 -0000 Subject: [Haiku-bugs] [Haiku] #1268: Incorporation of the well known live cd scripts in the build. In-Reply-To: <043.0ec3b288215ac8d81edd1780fc68e6bc@haiku-os.org> References: <043.0ec3b288215ac8d81edd1780fc68e6bc@haiku-os.org> Message-ID: <052.1cac9ff841050555e7188c62cce67fe6@haiku-os.org> #1268: Incorporation of the well known live cd scripts in the build. ---------------------------+------------------------------------------------ Reporter: kaoutsis | Owner: mmu_man Type: enhancement | Status: new Priority: blocker | Milestone: R1/alpha1 Component: Build System | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Changes (by nielx): * owner: bonefish => mmu_man Comment: I'd say: close it as soon as it is documented (in the ReadMe in short, and maybe a short article on the website). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 4 11:02:18 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 04 Mar 2008 10:02:18 -0000 Subject: [Haiku-bugs] [Haiku] #1890: Haiku occasionally KDLs when accessing the net In-Reply-To: <039.15d61a84a280248ad5a5fa71f6e1bfe2@haiku-os.org> References: <039.15d61a84a280248ad5a5fa71f6e1bfe2@haiku-os.org> Message-ID: <048.7b99d89ced541ef97ef7ad83a91a7a0f@haiku-os.org> #1890: Haiku occasionally KDLs when accessing the net ------------------------------+--------------------------------------------- Reporter: koki | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Network | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by kaliber): Seems it's duplicate of ticket #1661 and/or ticker #1641. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 4 11:21:41 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 04 Mar 2008 10:21:41 -0000 Subject: [Haiku-bugs] [Haiku] #1268: Incorporation of the well known live cd scripts in the build. In-Reply-To: <043.0ec3b288215ac8d81edd1780fc68e6bc@haiku-os.org> References: <043.0ec3b288215ac8d81edd1780fc68e6bc@haiku-os.org> Message-ID: <052.c2a2e7a063a03e7d9e21085dbf88d8d5@haiku-os.org> #1268: Incorporation of the well known live cd scripts in the build. ---------------------------+------------------------------------------------ Reporter: kaoutsis | Owner: mmu_man Type: enhancement | Status: new Priority: blocker | Milestone: R1/alpha1 Component: Build System | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by nielx): Ah, I see that was added in [24222], so feel free to close... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 4 11:44:10 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 04 Mar 2008 10:44:10 -0000 Subject: [Haiku-bugs] [Haiku] #1364: Bootloader can't find boot volume, booting from cd In-Reply-To: <041.ff14f133560c18c550bdf6a3c705c6c8@haiku-os.org> References: <041.ff14f133560c18c550bdf6a3c705c6c8@haiku-os.org> Message-ID: <050.f353e4ac85225722be77d6f171e15c07@haiku-os.org> #1364: Bootloader can't find boot volume, booting from cd ---------------------------------+------------------------------------------ Reporter: aldeck | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: System/Boot Loader | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by aldeck): I still have the problem with some of my test machines and vmware. I'd like to test a bit further. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 4 11:44:22 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 04 Mar 2008 10:44:22 -0000 Subject: [Haiku-bugs] [Haiku] #1268: Incorporation of the well known live cd scripts in the build. In-Reply-To: <043.0ec3b288215ac8d81edd1780fc68e6bc@haiku-os.org> References: <043.0ec3b288215ac8d81edd1780fc68e6bc@haiku-os.org> Message-ID: <052.298a1c465a216deb1f9d72a4fa589bd9@haiku-os.org> #1268: Incorporation of the well known live cd scripts in the build. ---------------------------+------------------------------------------------ Reporter: kaoutsis | Owner: mmu_man Type: enhancement | Status: new Priority: blocker | Milestone: R1/alpha1 Component: Build System | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by stippi): Let's please add the Bootscript.cd yet, and start the Installer from there. Then close this. :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 4 13:17:45 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 04 Mar 2008 12:17:45 -0000 Subject: [Haiku-bugs] [Haiku] #1364: Bootloader can't find boot volume, booting from cd In-Reply-To: <041.ff14f133560c18c550bdf6a3c705c6c8@haiku-os.org> References: <041.ff14f133560c18c550bdf6a3c705c6c8@haiku-os.org> Message-ID: <050.2064f0b2e02b718e85063ab73d77e5da@haiku-os.org> #1364: Bootloader can't find boot volume, booting from cd ---------------------------------+------------------------------------------ Reporter: aldeck | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: System/Boot Loader | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by aldeck): Ok, i re-tested, i got it to work on 3 real hardware machines. Good work Francois :) It still doesnt work under vmware though, i'm seeing a (ultra fast) message before the bootloader starts: "no boot path found, scan for all partitions..." "Could not locate any supported boot device!" See attached serial log. PS: mmu_man, can you add a haiku-cd.cue example or file somewhere, for us poor windows burners? :-) (see attached cue file) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 4 13:28:50 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 04 Mar 2008 12:28:50 -0000 Subject: [Haiku-bugs] [Haiku] #1364: Bootloader can't find boot volume, booting from cd In-Reply-To: <041.ff14f133560c18c550bdf6a3c705c6c8@haiku-os.org> References: <041.ff14f133560c18c550bdf6a3c705c6c8@haiku-os.org> Message-ID: <050.866c1d4cbf8d88a465864b98f421458e@haiku-os.org> #1364: Bootloader can't find boot volume, booting from cd ---------------------------------+------------------------------------------ Reporter: aldeck | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: System/Boot Loader | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by mmu_man): Added 3rdparty/nero/haiku-cd.cue as r24230. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 4 13:34:54 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 04 Mar 2008 12:34:54 -0000 Subject: [Haiku-bugs] [Haiku] #1364: Bootloader can't find boot volume, booting from cd In-Reply-To: <041.ff14f133560c18c550bdf6a3c705c6c8@haiku-os.org> References: <041.ff14f133560c18c550bdf6a3c705c6c8@haiku-os.org> Message-ID: <050.935a8cbdb7215f35e21dadd7c4cdf0c4@haiku-os.org> #1364: Bootloader can't find boot volume, booting from cd ---------------------------------+------------------------------------------ Reporter: aldeck | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: System/Boot Loader | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by mmu_man): As for the serial log, it doesn't seem to find the tgz data... maybe your BIOS doesn't like 1.44 floppy emulation... IIRC some work with 2.88 only. Try changing the count=1440 to count=2880 in build/jam/ImageRules. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 4 13:44:33 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 04 Mar 2008 12:44:33 -0000 Subject: [Haiku-bugs] [Haiku] #1887: ctrl-tab: mouse cursor is not warped In-Reply-To: <041.46821c847840264592c3723869ab46fc@haiku-os.org> References: <041.46821c847840264592c3723869ab46fc@haiku-os.org> Message-ID: <050.ecd80d92f76c50229761c35722be3a9b@haiku-os.org> #1887: ctrl-tab: mouse cursor is not warped -----------------------------+---------------------------------------------- Reporter: nutela | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Platform: x86 -----------------------------+---------------------------------------------- Comment (by axeld): Warping is not yet implemented indeed. I'm not yet sure how to handle it best, but we'll see. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 4 13:50:45 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 04 Mar 2008 12:50:45 -0000 Subject: [Haiku-bugs] [Haiku] #1886: Terminal won't get focus back after quiting app launched from Terminal In-Reply-To: <041.c23a06a139b1e0b6118a0c219e3653e8@haiku-os.org> References: <041.c23a06a139b1e0b6118a0c219e3653e8@haiku-os.org> Message-ID: <050.04d2544ef3dd2a96b3e2653a20f1ebf8@haiku-os.org> #1886: Terminal won't get focus back after quiting app launched from Terminal -----------------------------+---------------------------------------------- Reporter: nutela | Owner: stippi Type: bug | Status: closed Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: fixed | Platform: x86 -----------------------------+---------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: The mouse cursor is not supposed to move in this case (only when you activate the windows using the Deskbar). Also, our FFM behaves like normal mouse mode when you don't actually move the mouse; that's not a bug but supposed to work like this. Fixed in r24234: we now maintain a separate focus list, and will just choose the window that had focus before (no matter what order the windows are). So in your example, the Terminal will always be chosen as the next window having focus (before, it depended on the window order). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 4 14:01:13 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 04 Mar 2008 13:01:13 -0000 Subject: [Haiku-bugs] [Haiku] #1364: Bootloader can't find boot volume, booting from cd In-Reply-To: <041.ff14f133560c18c550bdf6a3c705c6c8@haiku-os.org> References: <041.ff14f133560c18c550bdf6a3c705c6c8@haiku-os.org> Message-ID: <050.9df9052ea72034cc0b43ce6cf6d474c8@haiku-os.org> #1364: Bootloader can't find boot volume, booting from cd ---------------------------------+------------------------------------------ Reporter: aldeck | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: System/Boot Loader | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by aldeck): Replying to [comment:9 mmu_man]: > Try changing the count=1440 to count=2880 in build/jam/ImageRules. Tried that without success. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 4 14:32:54 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 04 Mar 2008 13:32:54 -0000 Subject: [Haiku-bugs] [Haiku] #1364: Bootloader can't find boot volume, booting from cd In-Reply-To: <041.ff14f133560c18c550bdf6a3c705c6c8@haiku-os.org> References: <041.ff14f133560c18c550bdf6a3c705c6c8@haiku-os.org> Message-ID: <050.379e9f64eb0491bf596e27a248b551c5@haiku-os.org> #1364: Bootloader can't find boot volume, booting from cd ---------------------------------+------------------------------------------ Reporter: aldeck | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: System/Boot Loader | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by jackburton): I can confirm this bug happening on vmware lplayer here. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 4 14:33:15 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 04 Mar 2008 13:33:15 -0000 Subject: [Haiku-bugs] [Haiku] #1891: No keyboard or mouse input on real hardware Message-ID: <043.3e5b5319685d174aa810166ac0cef370@haiku-os.org> #1891: No keyboard or mouse input on real hardware -----------------------+---------------------------------------------------- Reporter: salierix | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- My mouse and keyboard don't work when running Haiku on my machine, however everything is fine when using qemu or vmplayer. I've tried both PS/2 and USB but neither seem to work. I'll try to get some log output but lacking a mouse or a keyboard makes that kind of tricky... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 4 15:22:57 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 04 Mar 2008 14:22:57 -0000 Subject: [Haiku-bugs] [Haiku] #1364: Bootloader can't find boot volume, booting from cd In-Reply-To: <041.ff14f133560c18c550bdf6a3c705c6c8@haiku-os.org> References: <041.ff14f133560c18c550bdf6a3c705c6c8@haiku-os.org> Message-ID: <050.91bc194937213d8ee942ee94af9c9d70@haiku-os.org> #1364: Bootloader can't find boot volume, booting from cd ---------------------------------+------------------------------------------ Reporter: aldeck | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: System/Boot Loader | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by aldeck): Ok, just tested a few more things: 1. booting from the hd bootloader, i can't continue booting on cd (even on a cd with a one track image only) 1b. continuing to boot on hd. both the bootimg and full image are found and automounted by tracker. {{{ df gives: /boot bfs 100.0M 3.7M QAM-P-W /dev/disk/ata/0/master/raw /bootimg iso9660 3.2M 0M ----P-- /dev/disk/atapi/1/master/0 /Haiku1 bfs 100.0M 5.0M QAM-P-- /dev/disk/atapi/1/master/1 }}} 2. booting from the cd bootloader, continuing boot on hd. You can see below that the haiku image from the cd is not there. {{{ df gives: /boot bfs 100.0M 3.7M QAM-P-W /dev/disk/ata/0/master/raw /bootimg iso9660 3.2M 0M ----P-- /dev/disk/atapi/1/master/raw }}} Hope this helps -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 4 15:37:47 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 04 Mar 2008 14:37:47 -0000 Subject: [Haiku-bugs] [Haiku] #1364: Bootloader can't find boot volume, booting from cd In-Reply-To: <041.ff14f133560c18c550bdf6a3c705c6c8@haiku-os.org> References: <041.ff14f133560c18c550bdf6a3c705c6c8@haiku-os.org> Message-ID: <050.cf1273e1aba66cc8906b5e0f34680563@haiku-os.org> #1364: Bootloader can't find boot volume, booting from cd ---------------------------------+------------------------------------------ Reporter: aldeck | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: System/Boot Loader | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by mmlr): About VMWare: are you sure that VMWare emulates multi-track CD-Roms correctly at all? In fact, when using an image file of a CD there is no way to tell where one track starts or ends. This is due to the fact that this information is stored in the TOC of the CD, which is not part of images (hence why you have to use a CUE-Sheet to burn, as the application cannot know either). Under Bochs or QEMU, when emulating a CD from an image, a single track CD with the full size of the image is emulated because of that. I hacked in the -cdtoc option in the BeOS version of QEMU to specify the starting sectors of tracks to circumvent that. When emulating using a real CD as a source though, they will read and use the TOC of that CD. So if you are using VMWare with a CD image you might not be able to get this to work. What you can try to test whether or not the multi track CD is emulated correctly is to boot Haiku from the HD image and have the CD image attached and then see if you have both, the iso9660 and the BFS track available in the mount menu. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 4 16:27:08 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 04 Mar 2008 15:27:08 -0000 Subject: [Haiku-bugs] [Haiku] #1364: Bootloader can't find boot volume, booting from cd In-Reply-To: <041.ff14f133560c18c550bdf6a3c705c6c8@haiku-os.org> References: <041.ff14f133560c18c550bdf6a3c705c6c8@haiku-os.org> Message-ID: <050.a9d3c04c81b38404476493d181341309@haiku-os.org> #1364: Bootloader can't find boot volume, booting from cd ---------------------------------+------------------------------------------ Reporter: aldeck | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: System/Boot Loader | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by aldeck): Replying to [comment:13 mmlr]: > About VMWare: are you sure that VMWare emulates multi-track CD-Roms correctly at all? I'm testing with a real cd (which works on real hw), ide1:0.deviceType = "cdrom-raw" in the .vmx file. > [...] boot Haiku from the HD image and have the CD image attached and then see if you have both, the iso9660 and the BFS track available in the mount menu. That's what i just tested in my previous comment. Sorry if i wasn't clear, and thanks for the infos :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 4 16:30:48 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 04 Mar 2008 15:30:48 -0000 Subject: [Haiku-bugs] [Haiku] #1268: Incorporation of the well known live cd scripts in the build. In-Reply-To: <043.0ec3b288215ac8d81edd1780fc68e6bc@haiku-os.org> References: <043.0ec3b288215ac8d81edd1780fc68e6bc@haiku-os.org> Message-ID: <052.89aad8e44bdc01ed2782c790af3834de@haiku-os.org> #1268: Incorporation of the well known live cd scripts in the build. ---------------------------+------------------------------------------------ Reporter: kaoutsis | Owner: mmu_man Type: enhancement | Status: new Priority: blocker | Milestone: R1/alpha1 Component: Build System | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by kaoutsis): i tried to generate the iso file from linux gcc2 (./configure --build-cross-tools ../buildtools/). It seems that the image is missing, see attached file jam_-q_haiku-boot- cd.txt -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 4 16:40:36 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 04 Mar 2008 15:40:36 -0000 Subject: [Haiku-bugs] [Haiku] #1268: Incorporation of the well known live cd scripts in the build. In-Reply-To: <043.0ec3b288215ac8d81edd1780fc68e6bc@haiku-os.org> References: <043.0ec3b288215ac8d81edd1780fc68e6bc@haiku-os.org> Message-ID: <052.db66dbac9fe865e0fb6698d1be5d8e72@haiku-os.org> #1268: Incorporation of the well known live cd scripts in the build. ---------------------------+------------------------------------------------ Reporter: kaoutsis | Owner: mmu_man Type: enhancement | Status: new Priority: blocker | Milestone: R1/alpha1 Component: Build System | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by nielx): Replying to [comment:9 kaoutsis]: > i tried to generate the iso file from linux gcc2 > (./configure --build-cross-tools ../buildtools/). > It seems that the image is missing, see attached file jam_-q_haiku-boot- cd.txt Check the instructions again. You should also perform a 'jam -q haiku- image'. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 4 16:53:25 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 04 Mar 2008 15:53:25 -0000 Subject: [Haiku-bugs] [Haiku] #1268: Incorporation of the well known live cd scripts in the build. In-Reply-To: <043.0ec3b288215ac8d81edd1780fc68e6bc@haiku-os.org> References: <043.0ec3b288215ac8d81edd1780fc68e6bc@haiku-os.org> Message-ID: <052.1e5745bcd294584d5468314c9d8abb87@haiku-os.org> #1268: Incorporation of the well known live cd scripts in the build. ---------------------------+------------------------------------------------ Reporter: kaoutsis | Owner: mmu_man Type: enhancement | Status: new Priority: blocker | Milestone: R1/alpha1 Component: Build System | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by kaoutsis): Replying to [comment:10 nielx]: > Replying to [comment:9 kaoutsis]: > Check the instructions again. You should also perform a 'jam -q haiku- image'. yes, i already did before post, no effect. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 4 16:58:42 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 04 Mar 2008 15:58:42 -0000 Subject: [Haiku-bugs] [Haiku] #1268: Incorporation of the well known live cd scripts in the build. In-Reply-To: <043.0ec3b288215ac8d81edd1780fc68e6bc@haiku-os.org> References: <043.0ec3b288215ac8d81edd1780fc68e6bc@haiku-os.org> Message-ID: <052.1093ce5c68adc60ae2612569a9261b3b@haiku-os.org> #1268: Incorporation of the well known live cd scripts in the build. ---------------------------+------------------------------------------------ Reporter: kaoutsis | Owner: mmu_man Type: enhancement | Status: new Priority: blocker | Milestone: R1/alpha1 Component: Build System | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by kaoutsis): Replying to [comment:11 kaoutsis]: > Replying to [comment:10 nielx]: > > Replying to [comment:9 kaoutsis]: > > > Check the instructions again. You should also perform a 'jam -q haiku- image'. > yes, i already did before post, no effect. oh, my bad sorry. i had the impression that the image should be inside the iso file -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 4 17:12:11 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 04 Mar 2008 16:12:11 -0000 Subject: [Haiku-bugs] [Haiku] #1364: Bootloader can't find boot volume, booting from cd In-Reply-To: <041.ff14f133560c18c550bdf6a3c705c6c8@haiku-os.org> References: <041.ff14f133560c18c550bdf6a3c705c6c8@haiku-os.org> Message-ID: <050.7e1b878374702a9e7cf3fd3d510b9346@haiku-os.org> #1364: Bootloader can't find boot volume, booting from cd ---------------------------------+------------------------------------------ Reporter: aldeck | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: System/Boot Loader | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by mmu_man): You can also just use the floppy image and use the bfs image as a single track CD. For qemu: qemu -cdrom generated/haiku.image -fda generated/haiku-boot-floppy.image -boot a -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 4 17:13:28 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 04 Mar 2008 16:13:28 -0000 Subject: [Haiku-bugs] [Haiku] #1268: Incorporation of the well known live cd scripts in the build. In-Reply-To: <043.0ec3b288215ac8d81edd1780fc68e6bc@haiku-os.org> References: <043.0ec3b288215ac8d81edd1780fc68e6bc@haiku-os.org> Message-ID: <052.eca0f8bba1fd7c229eb343905dd29cba@haiku-os.org> #1268: Incorporation of the well known live cd scripts in the build. ---------------------------+------------------------------------------------ Reporter: kaoutsis | Owner: mmu_man Type: enhancement | Status: new Priority: blocker | Milestone: R1/alpha1 Component: Build System | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by mmu_man): No it's not, it's the second track of the CD. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 4 17:43:41 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 04 Mar 2008 16:43:41 -0000 Subject: [Haiku-bugs] [Haiku] #1364: Bootloader can't find boot volume, booting from cd In-Reply-To: <041.ff14f133560c18c550bdf6a3c705c6c8@haiku-os.org> References: <041.ff14f133560c18c550bdf6a3c705c6c8@haiku-os.org> Message-ID: <050.2980350fdbd76ff4e7c3a82323381036@haiku-os.org> #1364: Bootloader can't find boot volume, booting from cd ---------------------------------+------------------------------------------ Reporter: aldeck | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: System/Boot Loader | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by aldeck): Replying to [comment:15 mmu_man]: > You can also just use the floppy image and use the bfs image as a single track CD. > For qemu: > qemu -cdrom generated/haiku.image -fda generated/haiku-boot-floppy.image -boot a Fran?ois, i'm not sure you're replying to me, but if you read carefully my previous comment, i've basically tried this already to see if it could help you, besides i'm talking about running from the normal two tracks cd under vmware not qemu :-/ -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 4 19:05:25 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 04 Mar 2008 18:05:25 -0000 Subject: [Haiku-bugs] [Haiku] #1364: Bootloader can't find boot volume, booting from cd In-Reply-To: <041.ff14f133560c18c550bdf6a3c705c6c8@haiku-os.org> References: <041.ff14f133560c18c550bdf6a3c705c6c8@haiku-os.org> Message-ID: <050.a2b72ef7899556851dbde405ecdb627d@haiku-os.org> #1364: Bootloader can't find boot volume, booting from cd ---------------------------------+------------------------------------------ Reporter: aldeck | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: System/Boot Loader | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by mmu_man): I was talking about testing cd images, as said it's not easy or even supported on qemu and vmware. So using a floppy image + haiku.image as single track cd instead should have the same functional behaviour, for testing, which avoids burning a cd. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 4 19:16:57 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 04 Mar 2008 18:16:57 -0000 Subject: [Haiku-bugs] [Haiku] #1429: Icons for Chart, Mandelbrot, Email, Cody Cam and Disks use old style. In-Reply-To: <042.1555660311752b958e3000bceb70de58@haiku-os.org> References: <042.1555660311752b958e3000bceb70de58@haiku-os.org> Message-ID: <051.e0d29e6ff81fef3d7f84b4a7e11c5846@haiku-os.org> #1429: Icons for Chart, Mandelbrot, Email, Cody Cam and Disks use old style. -----------------------------+---------------------------------------------- Reporter: scottmc | Owner: stippi Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Platform: All -----------------------------+---------------------------------------------- Comment (by hma): "For the Email preflet, I have one proposal too, but I was thinking of a mailbox which just gets the name plate inserted or something. Maybe it's too difficult to display this conceivably." Mailbox designs are really culture specific. For example, US-style tube with a red L thing on the side may be difficult to recognize if you have only seen them in movies or cartoons. How about something like an envelope with a @ as stamp. Envelopes don't vary that much from country to country and @ should be strongly associated with email. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 4 19:17:47 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 04 Mar 2008 18:17:47 -0000 Subject: [Haiku-bugs] [Haiku] #1641: KDL: rtl8139 In-Reply-To: <043.5f4af7ba053274031187f62bac03de4a@haiku-os.org> References: <043.5f4af7ba053274031187f62bac03de4a@haiku-os.org> Message-ID: <052.68a62a92747073ba2917f306e4d64328@haiku-os.org> #1641: KDL: rtl8139 ------------------------+--------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Changes (by koki): * cc: kaliber (removed) * cc: koki (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 4 19:48:58 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 04 Mar 2008 18:48:58 -0000 Subject: [Haiku-bugs] [Haiku] #1268: Incorporation of the well known live cd scripts in the build. In-Reply-To: <043.0ec3b288215ac8d81edd1780fc68e6bc@haiku-os.org> References: <043.0ec3b288215ac8d81edd1780fc68e6bc@haiku-os.org> Message-ID: <052.1a696fc72fa2741def07ae6d4bbb7f3c@haiku-os.org> #1268: Incorporation of the well known live cd scripts in the build. ---------------------------+------------------------------------------------ Reporter: kaoutsis | Owner: mmu_man Type: enhancement | Status: new Priority: blocker | Milestone: R1/alpha1 Component: Build System | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by kaoutsis): Replying to [comment:13 mmu_man]: > No it's not, it's the second track of the CD. ok, thanks; how can i verify that is there (the haiku.image)? i mount the dvd and i see: /dev/hdc 1808 1808 0 100% /media/cdrom0 ls /media/cdrom0 gives: boot.catalog haiku-boot-floppy.image README.html may be i did something wrong? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 4 20:04:01 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 04 Mar 2008 19:04:01 -0000 Subject: [Haiku-bugs] [Haiku] #1890: Haiku occasionally KDLs when accessing the net In-Reply-To: <039.15d61a84a280248ad5a5fa71f6e1bfe2@haiku-os.org> References: <039.15d61a84a280248ad5a5fa71f6e1bfe2@haiku-os.org> Message-ID: <048.f235939e83c2e3ef4cf4cb6454aed127@haiku-os.org> #1890: Haiku occasionally KDLs when accessing the net ------------------------------+--------------------------------------------- Reporter: koki | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Network | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by koki): Honestly, I could not tell; but if it is the same and this big report can be closed, please feel free to do so then. :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 4 21:11:48 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 04 Mar 2008 20:11:48 -0000 Subject: [Haiku-bugs] [Haiku] #1886: Terminal won't get focus back after quiting app launched from Terminal In-Reply-To: <041.c23a06a139b1e0b6118a0c219e3653e8@haiku-os.org> References: <041.c23a06a139b1e0b6118a0c219e3653e8@haiku-os.org> Message-ID: <050.873d9e9abe9f8299543df50bf4586f15@haiku-os.org> #1886: Terminal won't get focus back after quiting app launched from Terminal -----------------------------+---------------------------------------------- Reporter: nutela | Owner: stippi Type: bug | Status: closed Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: fixed | Platform: x86 -----------------------------+---------------------------------------------- Comment (by nutela): Fixed already, I have to try it out then :) you are sure fast :) I noticed other (bad) behavior too (rev 24195); when I right clicked the terminal 10 min ago, the terminal's tab went to gray even when the mouse was over the window (R5 does not do this, the tab stays yellow), when I moved the mouse the tab became yellow again. Also I noted that by pressing ctrl+tab I couldn't get focus to Tracker windows at all. The mouse did go *from* Tracker to other windows but not back to Tracker. Should I file a separate bug for this? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 4 21:15:05 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 04 Mar 2008 20:15:05 -0000 Subject: [Haiku-bugs] [Haiku] #1886: Terminal won't get focus back after quiting app launched from Terminal In-Reply-To: <041.c23a06a139b1e0b6118a0c219e3653e8@haiku-os.org> References: <041.c23a06a139b1e0b6118a0c219e3653e8@haiku-os.org> Message-ID: <050.f77db2e45d0feeaf9b8dd31ba37724a4@haiku-os.org> #1886: Terminal won't get focus back after quiting app launched from Terminal -----------------------------+---------------------------------------------- Reporter: nutela | Owner: stippi Type: bug | Status: closed Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: fixed | Platform: x86 -----------------------------+---------------------------------------------- Comment (by nutela): I just tested in R5; started the Terminal, started Workspaces from the Terminal. The Terminal's tab stayed yellow, pressing alt+w quit the Terminal (and Workspaces of course) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 4 21:16:03 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 04 Mar 2008 20:16:03 -0000 Subject: [Haiku-bugs] [Haiku] #1887: ctrl-tab: mouse cursor is not warped In-Reply-To: <041.46821c847840264592c3723869ab46fc@haiku-os.org> References: <041.46821c847840264592c3723869ab46fc@haiku-os.org> Message-ID: <050.ccc5fc4fd786a95fc410ca49d4c43751@haiku-os.org> #1887: ctrl-tab: mouse cursor is not warped -----------------------------+---------------------------------------------- Reporter: nutela | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Platform: x86 -----------------------------+---------------------------------------------- Comment (by nutela): Tracker windows can't be focused+raised at all this way. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 4 21:41:39 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 04 Mar 2008 20:41:39 -0000 Subject: [Haiku-bugs] [Haiku] #1203: mutliple issues with usb stack revision 22130 In-Reply-To: <041.a998994b38b90fc6acdc0bd1164ac15d@haiku-os.org> References: <041.a998994b38b90fc6acdc0bd1164ac15d@haiku-os.org> Message-ID: <050.241802d87ec93edc5e02decb4879dd05@haiku-os.org> #1203: mutliple issues with usb stack revision 22130 --------------------------+------------------------------------------------- Reporter: nutela | Owner: mmlr Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: x86 --------------------------+------------------------------------------------- Comment (by nutela): I tested my Wacom Graphire 4, works, although I did notice the cursor was trembling (high sensitivity) when I used it in Zeta it didn't but maybe it was my hand this time :) They keyboard however stopped working when I had the wacom plugged in and resumed again when I unplugged the wacom and plugged in an usb mouse. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 4 23:43:37 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 04 Mar 2008 22:43:37 -0000 Subject: [Haiku-bugs] [Haiku] #1203: mutliple issues with usb stack revision 22130 In-Reply-To: <041.a998994b38b90fc6acdc0bd1164ac15d@haiku-os.org> References: <041.a998994b38b90fc6acdc0bd1164ac15d@haiku-os.org> Message-ID: <050.7ec95c8373df63f7da5a399175b9b248@haiku-os.org> #1203: mutliple issues with usb stack revision 22130 --------------------------+------------------------------------------------- Reporter: nutela | Owner: mmlr Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: x86 --------------------------+------------------------------------------------- Comment (by stippi): Yes, the jittering is a known issue. I can reproduce that with my Graphire. Seems like the driver is currently tweaked for the Intuos typical jitter... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 5 02:59:35 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 05 Mar 2008 01:59:35 -0000 Subject: [Haiku-bugs] [Haiku] #1530: Nvidia GeForce FX 6600 doesn't work In-Reply-To: <050.4cc60a9924bb833736e176bdc0211f65@haiku-os.org> References: <050.4cc60a9924bb833736e176bdc0211f65@haiku-os.org> Message-ID: <059.9b18eaedd64fd5e3d1f63bd93e4dc8bf@haiku-os.org> #1530: Nvidia GeForce FX 6600 doesn't work --------------------------------------+------------------------------------- Reporter: marcusoverhagen | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: | Platform: All --------------------------------------+------------------------------------- Comment (by aldeck): Black screen with a 7600 GO (laptop) here. We might want to exclude it too. 0x0398, /* Nvidia GeForce 7600 GO */ I'll test in the next days with a GeForce FX 6600 GT AGP (0x00f1) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 5 06:31:52 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 05 Mar 2008 05:31:52 -0000 Subject: [Haiku-bugs] [Haiku] #1891: No keyboard or mouse input on real hardware In-Reply-To: <043.3e5b5319685d174aa810166ac0cef370@haiku-os.org> References: <043.3e5b5319685d174aa810166ac0cef370@haiku-os.org> Message-ID: <052.4cf7e05c9e47796de9eefb0274074aa1@haiku-os.org> #1891: No keyboard or mouse input on real hardware ------------------------+--------------------------------------------------- Reporter: salierix | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by salierix): My keyboard seems to work if I boot using the safe mode option. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 5 09:14:50 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 05 Mar 2008 08:14:50 -0000 Subject: [Haiku-bugs] [Haiku] #1755: APR 0.9.x configure hangs In-Reply-To: <043.4f95de578a9238745b55c09b213f0130@haiku-os.org> References: <043.4f95de578a9238745b55c09b213f0130@haiku-os.org> Message-ID: <052.693fa2c8befb0b3a002d85d2319b2df0@haiku-os.org> #1755: APR 0.9.x configure hangs ------------------------+--------------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: x86 ------------------------+--------------------------------------------------- Comment (by andrewbachmann): I also ran into this issue on r24209, and the max/minimize seems to restart just fine. I noticed that if I do a "ps", it prints "Bad semaphore ID(-1)" for sh and sed processes. But this seems to show up all the time so perhaps it doesn't mean anything. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 5 11:29:43 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 05 Mar 2008 10:29:43 -0000 Subject: [Haiku-bugs] [Haiku] #1891: No keyboard or mouse input on real hardware In-Reply-To: <043.3e5b5319685d174aa810166ac0cef370@haiku-os.org> References: <043.3e5b5319685d174aa810166ac0cef370@haiku-os.org> Message-ID: <052.016d9fa2496d408becb553b067bae1be@haiku-os.org> #1891: No keyboard or mouse input on real hardware ------------------------+--------------------------------------------------- Reporter: salierix | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by axeld): If you have a digital camera, one thing you could do is to enable the console debug mode in the safe mode menu, and then just make a photo of each page of the output; that might help, but the app_server might also be started too early for this. Eventually, changing the Bootscript to only start the input_server manually might help, too (and not the app_server); I dunno if that works, though. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 5 13:12:20 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 05 Mar 2008 12:12:20 -0000 Subject: [Haiku-bugs] [Haiku] #1711: Haiku stops booting at allocate_commpage_entry(4, 34) In-Reply-To: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> References: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> Message-ID: <048.8c11a87d6a37cee129e5890859b2215b@haiku-os.org> #1711: Haiku stops booting at allocate_commpage_entry(4, 34) ----------------------------+----------------------------------------------- Reporter: euan | Owner: korli Type: bug | Status: new Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Changes (by korli): * owner: mmlr => korli -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 5 16:16:46 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 05 Mar 2008 15:16:46 -0000 Subject: [Haiku-bugs] [Haiku] #1627: FAT: General System Error! In-Reply-To: <039.df6587c22640f28c424f31fb4641ccee@haiku-os.org> References: <039.df6587c22640f28c424f31fb4641ccee@haiku-os.org> Message-ID: <048.748abcd301ef166bf75ddbc0436147e9@haiku-os.org> #1627: FAT: General System Error! -------------------------------+-------------------------------------------- Reporter: rdmr | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/FAT | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Comment (by rdmr): additional info that may help (i hope): I was able to mount a ntfs partition and was able to read any file(r24238). So it seems like a bug in fat driver. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 5 19:38:03 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 05 Mar 2008 18:38:03 -0000 Subject: [Haiku-bugs] [Haiku] #1755: APR 0.9.x configure hangs In-Reply-To: <043.4f95de578a9238745b55c09b213f0130@haiku-os.org> References: <043.4f95de578a9238745b55c09b213f0130@haiku-os.org> Message-ID: <052.3b92c80cdf8e0332bf4763dabb86a7d6@haiku-os.org> #1755: APR 0.9.x configure hangs ------------------------+--------------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: x86 ------------------------+--------------------------------------------------- Comment (by jonas.kirilla): The error message is due to my recent change to http://dev.haiku-os.org/changeset/24023/haiku/trunk/src/bin/ps.c Previously ps would just list the previous value found by the while loop for each line which now prints the error message instead. I guess the -1 is due to waiting on a condition variable. http://dev.haiku- os.org/browser/haiku/trunk/src/system/kernel/condition_variable.cpp?rev=23980 (Look for -1 in PrivateConditionVariableEntry::Wait()) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 5 19:50:30 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 05 Mar 2008 18:50:30 -0000 Subject: [Haiku-bugs] [Haiku] #1755: APR 0.9.x configure hangs In-Reply-To: <043.4f95de578a9238745b55c09b213f0130@haiku-os.org> References: <043.4f95de578a9238745b55c09b213f0130@haiku-os.org> Message-ID: <052.d9f1e039813479e8ee2a9d76e693a96d@haiku-os.org> #1755: APR 0.9.x configure hangs ------------------------+--------------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: x86 ------------------------+--------------------------------------------------- Comment (by andreasf): Replying to [comment:9 jonas.kirilla]: > I guess the -1 is due to waiting on a condition variable. Yes, Ingo pointed this out [comment:6 above]. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 5 20:24:25 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 05 Mar 2008 19:24:25 -0000 Subject: [Haiku-bugs] [Haiku] #1892: Debugflag in Haiku has opposite default of BeOS Message-ID: <038.5500bc126f752285d37a4141abd749c8@haiku-os.org> #1892: Debugflag in Haiku has opposite default of BeOS -------------------------------+-------------------------------------------- Reporter: tqh | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Platform: All | -------------------------------+-------------------------------------------- BeOS has it default to true, Haiku has false. Changing this to true makes debugging behave as expected: http://haiku.it.su.se:8180/source/xref/src/system/libroot/os/debug.c#190 Also if I understand correctly the DEBUGGER macro in Haiku only takes a string? It crashed inside the debugger call anyway: From BeBook: "DEBUGGER() takes a printf()-style variable-length argument that must be wrapped inside a second set of parentheses;.." I suspect those functions needs at least an overview. Should probably be quite easy task. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 5 20:28:27 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 05 Mar 2008 19:28:27 -0000 Subject: [Haiku-bugs] [Haiku] #1755: APR 0.9.x configure hangs In-Reply-To: <043.4f95de578a9238745b55c09b213f0130@haiku-os.org> References: <043.4f95de578a9238745b55c09b213f0130@haiku-os.org> Message-ID: <052.318094caad3980d7371de952489cec3a@haiku-os.org> #1755: APR 0.9.x configure hangs ------------------------+--------------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: x86 ------------------------+--------------------------------------------------- Comment (by jonas.kirilla): Replying to [comment:10 andreasf]: > Replying to [comment:9 jonas.kirilla]: > > I guess the -1 is due to waiting on a condition variable. > Yes, Ingo pointed this out [comment:6 above]. Yeah, I just wanted to follow up on Andrew's observation of 'ps' output since I'm responsible for the latest change to it. I forgot to press reply (for proper quotation). I didn't mean to comment on the reported issue. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 5 20:41:37 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 05 Mar 2008 19:41:37 -0000 Subject: [Haiku-bugs] [Haiku] #1892: Debugflag in Haiku has opposite default of BeOS In-Reply-To: <038.5500bc126f752285d37a4141abd749c8@haiku-os.org> References: <038.5500bc126f752285d37a4141abd749c8@haiku-os.org> Message-ID: <047.188923abea3eb86dd8728fb503f98886@haiku-os.org> #1892: Debugflag in Haiku has opposite default of BeOS --------------------------------+------------------------------------------- Reporter: tqh | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Resolution: fixed | Platform: All --------------------------------+------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Fixed in r24243. And the BeBook is just wrong about the DEBUGGER() macro. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 5 21:06:39 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 05 Mar 2008 20:06:39 -0000 Subject: [Haiku-bugs] [Haiku] #1711: Haiku stops booting at allocate_commpage_entry(4, 34) In-Reply-To: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> References: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> Message-ID: <048.2d6312104081b0bde63d42dcb9905436@haiku-os.org> #1711: Haiku stops booting at allocate_commpage_entry(4, 34) ----------------------------+----------------------------------------------- Reporter: euan | Owner: korli Type: bug | Status: new Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by korli): This could be fixed in r24244. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 5 21:08:01 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 05 Mar 2008 20:08:01 -0000 Subject: [Haiku-bugs] [Haiku] #1711: Haiku stops booting at allocate_commpage_entry(4, 34) In-Reply-To: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> References: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> Message-ID: <048.ee1803402544820648f68bf5098b9dd3@haiku-os.org> #1711: Haiku stops booting at allocate_commpage_entry(4, 34) ----------------------------+----------------------------------------------- Reporter: euan | Owner: korli Type: bug | Status: new Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by euan): Here's my linux mtrrs for what it's worth. reg00: base=0x00000000 ( 0MB), size=2048MB: write-back, count=1 reg01: base=0x80000000 (2048MB), size= 512MB: write-back, count=1 Doing a build at the moment will update in 15 mins. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 5 22:01:05 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 05 Mar 2008 21:01:05 -0000 Subject: [Haiku-bugs] [Haiku] #1711: Haiku stops booting at allocate_commpage_entry(4, 34) In-Reply-To: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> References: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> Message-ID: <048.f0d54e76588a5b11c77a967bd7b317b1@haiku-os.org> #1711: Haiku stops booting at allocate_commpage_entry(4, 34) ----------------------------+----------------------------------------------- Reporter: euan | Owner: korli Type: bug | Status: new Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by euan): Sorry no change for me. :( Will try to get an updated syslog. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 5 22:24:57 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 05 Mar 2008 21:24:57 -0000 Subject: [Haiku-bugs] [Haiku] #1892: Debugflag in Haiku has opposite default of BeOS In-Reply-To: <038.5500bc126f752285d37a4141abd749c8@haiku-os.org> References: <038.5500bc126f752285d37a4141abd749c8@haiku-os.org> Message-ID: <047.c697d2b9958197ec294efa35161679c9@haiku-os.org> #1892: Debugflag in Haiku has opposite default of BeOS --------------------------------+------------------------------------------- Reporter: tqh | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Resolution: fixed | Platform: All --------------------------------+------------------------------------------- Comment (by tqh): Ah, could have sworn I had used it under R5 to debug.So I looked it up and you are right. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 5 22:39:52 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 05 Mar 2008 21:39:52 -0000 Subject: [Haiku-bugs] [Haiku] #1711: Haiku stops booting at allocate_commpage_entry(4, 34) In-Reply-To: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> References: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> Message-ID: <048.df2e34d55abb9fecebec3dca9a020d69@haiku-os.org> #1711: Haiku stops booting at allocate_commpage_entry(4, 34) ----------------------------+----------------------------------------------- Reporter: euan | Owner: korli Type: bug | Status: new Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by euan): Hmm seems that it now hangs in a part of the boot loading filesystems stuff. Can't be sure if it's another issue, or the same one... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 6 05:56:01 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 06 Mar 2008 04:56:01 -0000 Subject: [Haiku-bugs] [Haiku] #1891: No keyboard or mouse input on real hardware In-Reply-To: <043.3e5b5319685d174aa810166ac0cef370@haiku-os.org> References: <043.3e5b5319685d174aa810166ac0cef370@haiku-os.org> Message-ID: <052.19102fa584df42a6e6c4288a3c76ebcb@haiku-os.org> #1891: No keyboard or mouse input on real hardware ------------------------+--------------------------------------------------- Reporter: salierix | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by salierix): After compiling/installing/booting about 20+ different revisions I tracked the problem all the way to r22521 from over 5 months ago. For some reason lacking the ohci driver prevents my ps/2 mouse and keyboard from working and so adding it to the current revision completely fixes the problem. While I found a workaround to the problem I still have no idea how not having the ohci driver on the image causes this mess, even though I have no usb devices pluged in. This ticket should remain open for the time being. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 6 10:27:23 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 06 Mar 2008 09:27:23 -0000 Subject: [Haiku-bugs] [Haiku] #1891: No keyboard or mouse input on real hardware In-Reply-To: <043.3e5b5319685d174aa810166ac0cef370@haiku-os.org> References: <043.3e5b5319685d174aa810166ac0cef370@haiku-os.org> Message-ID: <052.f2455a0aae35b565aa662bd10740cf7b@haiku-os.org> #1891: No keyboard or mouse input on real hardware --------------------------+------------------------------------------------- Reporter: salierix | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Changes (by axeld): * cc: marcusoverhagen (added) * owner: axeld => mmlr * component: - General => Drivers/USB Comment: Now that sounds really strange. Seems to be related to the legacy emulation of your BIOS then. I'm just wondering why the safe boot fixes it. Anyway, I'm assigning this to Michael, as it seems to be primarily USB related. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 6 11:31:41 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 06 Mar 2008 10:31:41 -0000 Subject: [Haiku-bugs] [Haiku] #1891: No keyboard or mouse input on real hardware In-Reply-To: <043.3e5b5319685d174aa810166ac0cef370@haiku-os.org> References: <043.3e5b5319685d174aa810166ac0cef370@haiku-os.org> Message-ID: <052.b270bc16245dedc0fbc10592b4f24dd5@haiku-os.org> #1891: No keyboard or mouse input on real hardware --------------------------+------------------------------------------------- Reporter: salierix | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by salierix): Safe mode doesn't "fix it". The only reason I mentioned it was because I wanted to take a look at the log file and safe mode helped with that. The fact that safe mode works has nothing at all to do with the problem. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 6 12:30:08 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 06 Mar 2008 11:30:08 -0000 Subject: [Haiku-bugs] [Haiku] #1893: Trac: explain searching better Message-ID: <041.2b7cc3b089ea34bbd4b5501c37e85be9@haiku-os.org> #1893: Trac: explain searching better --------------------------+------------------------------------------------- Reporter: nutela | Owner: haiku-web Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Website/Trac | Version: R1 development Platform: All | --------------------------+------------------------------------------------- Can - be used? eg. auto -automotive, searching for strings "string" etc. all this is not explained in http://dev.haiku-os.org/wiki/TracSearch -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 6 12:34:15 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 06 Mar 2008 11:34:15 -0000 Subject: [Haiku-bugs] [Haiku] #1894: GNU core utils: manual pages missing Message-ID: <041.abb09bd0230ba1256880cf9234301c64@haiku-os.org> #1894: GNU core utils: manual pages missing ---------------------------+------------------------------------------------ Reporter: nutela | Owner: nielx Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Documentation | Version: R1 development Platform: All | ---------------------------+------------------------------------------------ A lot of the manual pages for GNU core utils (like grep, awk, sed) are missing. Please add manual pages for all command line tools. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 6 14:09:21 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 06 Mar 2008 13:09:21 -0000 Subject: [Haiku-bugs] [Haiku] #1895: Add Canna input method to UserBuildConfig.sample Message-ID: <037.3fc2ab2c30c25a03d0f4d3ec2a66cf3f@haiku-os.org> #1895: Add Canna input method to UserBuildConfig.sample -------------------------+-------------------------------------------------- Reporter: mt | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -------------------------+-------------------------------------------------- Please add Canna input method add-on to UserBuildConfig.sample like {{{ # Add optinal Canna input method add-on for Japanese (Kanji). # AddFilesToHaikuImage beos system add-ons input_server methods : canna ; }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 6 16:01:10 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 06 Mar 2008 15:01:10 -0000 Subject: [Haiku-bugs] [Haiku] #1896: /bin/bc crash Message-ID: <040.da90fc9f8a86a95338db1a65efec1ae9@haiku-os.org> #1896: /bin/bc crash --------------------------+------------------------------------------------- Reporter: thorn | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Platform: x86 | --------------------------+------------------------------------------------- Haiku r24244 to get segment violation * open terminal * type: echo v=1 | bc -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 6 16:43:36 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 06 Mar 2008 15:43:36 -0000 Subject: [Haiku-bugs] [Haiku] #1897: BSnow: "Click to remove" does not work Message-ID: <041.7fe61d5c7b93f820f1a1efd2fc499962@haiku-os.org> #1897: BSnow: "Click to remove" does not work --------------------------+------------------------------------------------- Reporter: stippi | Owner: mmu_man Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Platform: All | --------------------------+------------------------------------------------- I don't know if this is a bug in our BShelf implementation or BSnow, but the second time you launch BSnow, I guess you are supposed to be able to remove it from the Desktop, but clicking the window has no effect, even though it says that would remove it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 6 16:48:20 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 06 Mar 2008 15:48:20 -0000 Subject: [Haiku-bugs] [Haiku] #1896: /bin/bc crash In-Reply-To: <040.da90fc9f8a86a95338db1a65efec1ae9@haiku-os.org> References: <040.da90fc9f8a86a95338db1a65efec1ae9@haiku-os.org> Message-ID: <049.3e126b26299a9886a25268ccb1f2c1b3@haiku-os.org> #1896: /bin/bc crash ---------------------------+------------------------------------------------ Reporter: thorn | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Resolution: | Platform: x86 ---------------------------+------------------------------------------------ Changes (by thorn): * cc: thorn (added) Comment: 0x0023e176 in BPrivate::processHead::free () from /boot/beos/system/lib/libroot.so (gdb) bt #0 0x0023e176 in BPrivate:processHeap::free () from /boot/beos/system/lib/libroot.so #1 0x0023f984 in free () from /boot/beos/system/lib/libroot.so #2 0x0020455e in yyparse () #3 0x00202e85 in main () (gdb) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 6 21:19:39 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 06 Mar 2008 20:19:39 -0000 Subject: [Haiku-bugs] [Haiku] #254: Wrongly enabled buttons in apps/prefs (easy) In-Reply-To: <040.d8c8cd1d285f2b0573c32a8a664894eb@haiku-os.org> References: <040.d8c8cd1d285f2b0573c32a8a664894eb@haiku-os.org> Message-ID: <049.3cb4366ffa6f735581d2d107d398c135@haiku-os.org> #254: Wrongly enabled buttons in apps/prefs (easy) ---------------------------+------------------------------------------------ Reporter: diver | Owner: aldeck Type: bug | Status: new Priority: low | Milestone: R1 Component: Applications | Version: Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by aldeck): Screen should be fixed! r24280 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 6 23:57:34 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 06 Mar 2008 22:57:34 -0000 Subject: [Haiku-bugs] [Haiku] #693: Cannot Change Resolution per Workspace (easy) In-Reply-To: <054.cded4538db07e83281123e6417f59949@haiku-os.org> References: <054.cded4538db07e83281123e6417f59949@haiku-os.org> Message-ID: <063.72d766e607ba7c3a033726239b621d84@haiku-os.org> #693: Cannot Change Resolution per Workspace (easy) ----------------------------------+----------------------------------------- Reporter: greg.gd at woosh.co.nz | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: Resolution: | Platform: All ----------------------------------+----------------------------------------- Comment (by aldeck): i disabled the "current workspace" option for now. r24280 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 7 01:09:54 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 07 Mar 2008 00:09:54 -0000 Subject: [Haiku-bugs] [Haiku] #1230: Crash on booting under VirtualBox In-Reply-To: <039.5ec4b60fb1fa7f314fea31996c1f75a3@haiku-os.org> References: <039.5ec4b60fb1fa7f314fea31996c1f75a3@haiku-os.org> Message-ID: <048.3316258c710bd7c7f1ebccaaeeda4518@haiku-os.org> #1230: Crash on booting under VirtualBox ------------------------+--------------------------------------------------- Reporter: myob | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by tombhadac): no the problem still exists - without VT-x / AMD-V -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 7 02:18:38 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 07 Mar 2008 01:18:38 -0000 Subject: [Haiku-bugs] [Haiku] #1891: No keyboard or mouse input on real hardware In-Reply-To: <043.3e5b5319685d174aa810166ac0cef370@haiku-os.org> References: <043.3e5b5319685d174aa810166ac0cef370@haiku-os.org> Message-ID: <052.ac7f7da76c29b9a81f89d71f0cce2dfe@haiku-os.org> #1891: No keyboard or mouse input on real hardware --------------------------+------------------------------------------------- Reporter: salierix | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by salierix): Following Axel's suggestion on the dev list, setting the usb legacy option in my bios to "disabled" from its previous setting of "enabled" also seems to solve the problem whether the ohci driver is installed or not. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 7 17:27:28 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 07 Mar 2008 16:27:28 -0000 Subject: [Haiku-bugs] [Haiku] #1885: find KDLs when searching iso9660 dvd In-Reply-To: <042.dccdac296a799b1a691dd7ee32cd9aaf@haiku-os.org> References: <042.dccdac296a799b1a691dd7ee32cd9aaf@haiku-os.org> Message-ID: <051.347c4be741715e8d30a75d537031f928@haiku-os.org> #1885: find KDLs when searching iso9660 dvd ------------------------+--------------------------------------------------- Reporter: qyellow | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by qyellow): here's the sc 944f7fa8 (+ 0) ffff0104 7ffe6cec (+ 64) <_APP_>:savedir +0x00e5 7ffe6cec (+ 80) <_APP_>:main + 0x074f (nearest) 7ffe6cec (+ 64) <_APP_>:main + 0x06ac (nearest) 7ffe6cec (+ 64) <_APP_>:main + 0x08b7 (nearest) 7ffe6cec (+ 64) <_APP_>:main + 0x06ac (nearest) 7ffe6cec (+ 64) <_APP_>:main + 0x0410(nearest) 7ffe6cec (+ 64) <_APP_>:main + 0x0306 7ffe6cec (+ 64) <_APP_>:_start +0x005b 7ffe6cec (+ 64) 1865:runtime_loader_seg0ro at 0x00100000 + 0x7ca 7ffe6cec (+ 64) 1864:find_main_stack at 7efe7000 + 0xffffec -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 7 17:30:04 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 07 Mar 2008 16:30:04 -0000 Subject: [Haiku-bugs] [Haiku] #1885: find KDLs when searching iso9660 dvd In-Reply-To: <042.dccdac296a799b1a691dd7ee32cd9aaf@haiku-os.org> References: <042.dccdac296a799b1a691dd7ee32cd9aaf@haiku-os.org> Message-ID: <051.f9723be8191c50377ed5c220f3469a33@haiku-os.org> #1885: find KDLs when searching iso9660 dvd ------------------------+--------------------------------------------------- Reporter: qyellow | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by qyellow): sorry did not add in the correct addressess, here is the correct info: 944f7fa8 (+ 0) ffff0104 7ffe6cec (+ 64) <_APP_>:savedir +0x00e5 7ffe6d2c (+ 80) <_APP_>:main + 0x074f (nearest) 7ffe6d7c (+ 128) <_APP_>:main + 0x06ac (nearest) 7ffe6dfc (+ 80) <_APP_>:main + 0x08b7 (nearest) 7ffe6e4c (+ 128) <_APP_>:main + 0x06ac (nearest) 7ffe6ecc (+ 112) <_APP_>:main + 0x0410(nearest) 7ffe6f3c (+ 64) <_APP_>:main + 0x0306 7ffe6f7c (+ 48) <_APP_>:_start +0x005b 7ffe6fac (+ 48) 1865:runtime_loader_seg0ro at 0x00100000 + 0x7ca 7ffe6fdc (+ 0) 1864:find_main_stack at 7efe7000 + 0xffffec -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 7 18:53:47 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 07 Mar 2008 17:53:47 -0000 Subject: [Haiku-bugs] [Haiku] #1885: find KDLs when searching iso9660 dvd In-Reply-To: <042.dccdac296a799b1a691dd7ee32cd9aaf@haiku-os.org> References: <042.dccdac296a799b1a691dd7ee32cd9aaf@haiku-os.org> Message-ID: <051.976bc584855a0ee38f5a80205c8aa6a1@haiku-os.org> #1885: find KDLs when searching iso9660 dvd ------------------------+--------------------------------------------------- Reporter: qyellow | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by axeld): This contains only the user part which is relatively useless. Can you provide the full stack crawl? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 7 18:54:02 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 07 Mar 2008 17:54:02 -0000 Subject: [Haiku-bugs] [Haiku] #1885: find KDLs when searching iso9660 dvd In-Reply-To: <042.dccdac296a799b1a691dd7ee32cd9aaf@haiku-os.org> References: <042.dccdac296a799b1a691dd7ee32cd9aaf@haiku-os.org> Message-ID: <051.77f191d13f00dfe74eaf783ccb7f4c29@haiku-os.org> #1885: find KDLs when searching iso9660 dvd ------------------------------------+--------------------------------------- Reporter: qyellow | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/ISO 9660 | Version: R1 development Resolution: | Platform: All ------------------------------------+--------------------------------------- Changes (by axeld): * component: - General => File Systems/ISO 9660 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 7 19:57:33 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 07 Mar 2008 18:57:33 -0000 Subject: [Haiku-bugs] [Haiku] #1857: Add a search box to the right-top of the page In-Reply-To: <044.390b2d40eb66c5409172eb50961d3ed1@haiku-os.org> References: <044.390b2d40eb66c5409172eb50961d3ed1@haiku-os.org> Message-ID: <053.b90acbbf87563bb58e0275d3138a5d1e@haiku-os.org> #1857: Add a search box to the right-top of the page --------------------------+------------------------------------------------- Reporter: bnickname | Owner: haiku-web Type: enhancement | Status: new Priority: normal | Milestone: Website R2 Component: Website/CMS | Version: Resolution: | Platform: All --------------------------+------------------------------------------------- Changes (by nielx): * milestone: Website R1 => Website R2 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 7 20:40:23 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 07 Mar 2008 19:40:23 -0000 Subject: [Haiku-bugs] [Haiku] #1857: Add a search box to the right-top of the page In-Reply-To: <044.390b2d40eb66c5409172eb50961d3ed1@haiku-os.org> References: <044.390b2d40eb66c5409172eb50961d3ed1@haiku-os.org> Message-ID: <053.b796934f7a97144f696c308eab0f7378@haiku-os.org> #1857: Add a search box to the right-top of the page --------------------------+------------------------------------------------- Reporter: bnickname | Owner: haiku-web Type: enhancement | Status: new Priority: normal | Milestone: Website R2 Component: Website/CMS | Version: Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by jonas.kirilla): Is this is put on hold due to CMS complexity? If the functionality is desired one could in the meantime add an entry field/form which merely calls Google with "foo site:haiku-os.org". Not as cool as something local though, and there's missed intelligence opportunity for Haiku, but it may lessen the load/traffic (if that is or will be a problem post-release). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 7 20:44:22 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 07 Mar 2008 19:44:22 -0000 Subject: [Haiku-bugs] [Haiku] #1857: Add a search box to the right-top of the page In-Reply-To: <044.390b2d40eb66c5409172eb50961d3ed1@haiku-os.org> References: <044.390b2d40eb66c5409172eb50961d3ed1@haiku-os.org> Message-ID: <053.750a384b30842575cf12f8dfc68edf31@haiku-os.org> #1857: Add a search box to the right-top of the page --------------------------+------------------------------------------------- Reporter: bnickname | Owner: haiku-web Type: enhancement | Status: new Priority: normal | Milestone: Website R2 Component: Website/CMS | Version: Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by umccullough): Is this what you're looking for? http://bebits.com/app/4506 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 7 20:49:20 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 07 Mar 2008 19:49:20 -0000 Subject: [Haiku-bugs] [Haiku] #1857: Add a search box to the right-top of the page In-Reply-To: <044.390b2d40eb66c5409172eb50961d3ed1@haiku-os.org> References: <044.390b2d40eb66c5409172eb50961d3ed1@haiku-os.org> Message-ID: <053.863cf8e59f87cfc704b0fbc5a2553c14@haiku-os.org> #1857: Add a search box to the right-top of the page --------------------------+------------------------------------------------- Reporter: bnickname | Owner: haiku-web Type: enhancement | Status: new Priority: normal | Milestone: Website R2 Component: Website/CMS | Version: Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by nielx): This is being pushed forward because there are some major changes (behind the scenes) coming up. These will take precedence before we will implement new features. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 7 21:51:06 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 07 Mar 2008 20:51:06 -0000 Subject: [Haiku-bugs] [Haiku] #1894: GNU core utils: manual pages missing In-Reply-To: <041.abb09bd0230ba1256880cf9234301c64@haiku-os.org> References: <041.abb09bd0230ba1256880cf9234301c64@haiku-os.org> Message-ID: <050.8ee377dbc4e69ba16bd5520acf3248a8@haiku-os.org> #1894: GNU core utils: manual pages missing ----------------------------+----------------------------------------------- Reporter: nutela | Owner: nielx Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Documentation | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by nielx): What's the policy on man pages? Are we going to provide these? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 8 08:38:13 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 08 Mar 2008 07:38:13 -0000 Subject: [Haiku-bugs] [Haiku] #1857: Add a search box to the right-top of the page In-Reply-To: <044.390b2d40eb66c5409172eb50961d3ed1@haiku-os.org> References: <044.390b2d40eb66c5409172eb50961d3ed1@haiku-os.org> Message-ID: <053.65a74d73cd86f3455b7875c696a1d6b8@haiku-os.org> #1857: Add a search box to the right-top of the page --------------------------+------------------------------------------------- Reporter: bnickname | Owner: haiku-web Type: enhancement | Status: new Priority: normal | Milestone: Website R2 Component: Website/CMS | Version: Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by koki): Perhaps he means something like what we have in the NorCal HUG website? http://norcal-hug.org If that's the case, it will be there once the upgrade to Drupal 5 is done. Actually, it is possible to enable the search box in our current website, but for some reason it is not possible to give focus to the search field using the mouse. Any ideas? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 8 14:10:39 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 08 Mar 2008 13:10:39 -0000 Subject: [Haiku-bugs] [Haiku] #1898: getpeername returns size bigger than passed in? Message-ID: <038.caeeb8a1651bd335cee046c5c0969fa0@haiku-os.org> #1898: getpeername returns size bigger than passed in? --------------------------------------+------------------------------------- Reporter: tqh | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Platform: All | --------------------------------------+------------------------------------- Currently investigating Firefox (gcc4) crashes on SSL. One of the things I'm seeing is at least one case where calling getpeername with a size of 28 returns one with size 32. Unfortunatly it's quite messy on Firefox side so I'll just show how it's called: It fails this check, it has other problems as well though: [http://lxr.mozilla.org/mozilla1.8.0/source/nsprpub/pr/src/io/prsocket.c#60] Called from here: [http://lxr.mozilla.org/mozilla1.8.0/source/nsprpub/pr/src/io/prsocket.c#1086] Here is BeOS definition of _PR_MD_GETPEERNAME (Haiku has _PR_HAVE_SOCKADDR_LEN defined): [http://lxr.mozilla.org/mozilla1.8.0/source/nsprpub/pr/src/md/beos/bnet.c#772] And here is the wonderful definition of PrNetAddr: http://lxr.mozilla.org/mozilla1.8.0/source/nsprpub/pr/include/prio.h#174 Simple huh :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 8 15:58:06 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 08 Mar 2008 14:58:06 -0000 Subject: [Haiku-bugs] [Haiku] #1899: Baron's home should be /home/baron Message-ID: <043.0d2b8af4cf592fdd364315345be528b3@haiku-os.org> #1899: Baron's home should be /home/baron -------------------------+-------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: enhancement | Status: new Priority: low | Milestone: Unscheduled Component: System | Version: R1 development Platform: All | -------------------------+-------------------------------------------------- In a multiuser environment baron, should have a proper unix-like home /home/baron and also baron should have not administrator privileges by default. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 8 18:52:37 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 08 Mar 2008 17:52:37 -0000 Subject: [Haiku-bugs] [Haiku] #1898: getpeername returns size bigger than passed in? In-Reply-To: <038.caeeb8a1651bd335cee046c5c0969fa0@haiku-os.org> References: <038.caeeb8a1651bd335cee046c5c0969fa0@haiku-os.org> Message-ID: <047.05cd2d7890eb24bd339e8ad014f4c73d@haiku-os.org> #1898: getpeername returns size bigger than passed in? ---------------------------------------+------------------------------------ Reporter: tqh | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Resolution: fixed | Platform: All ---------------------------------------+------------------------------------ Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Good catch! Indeed, return_address() in kernel_stack.cpp did not take the original buffer size into account when copying the address. Fixed in r24310. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 8 18:54:18 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 08 Mar 2008 17:54:18 -0000 Subject: [Haiku-bugs] [Haiku] #1898: getpeername returns size bigger than passed in? In-Reply-To: <038.caeeb8a1651bd335cee046c5c0969fa0@haiku-os.org> References: <038.caeeb8a1651bd335cee046c5c0969fa0@haiku-os.org> Message-ID: <047.872e02737a51a5594d8cf3456e3160e8@haiku-os.org> #1898: getpeername returns size bigger than passed in? ---------------------------------------+------------------------------------ Reporter: tqh | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Resolution: fixed | Platform: All ---------------------------------------+------------------------------------ Comment (by axeld): BTW getpeername() (and friends) are actually supposed to return the length of the new address returned, even if it's longer than the original buffer (it's just not supposed to overwrite bytes in the target buffer that don't fit the address). See http://www.opengroup.org/onlinepubs/009695399/functions/getpeername.html -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 8 19:11:26 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 08 Mar 2008 18:11:26 -0000 Subject: [Haiku-bugs] [Haiku] #1898: getpeername returns size bigger than passed in? In-Reply-To: <038.caeeb8a1651bd335cee046c5c0969fa0@haiku-os.org> References: <038.caeeb8a1651bd335cee046c5c0969fa0@haiku-os.org> Message-ID: <047.45dca2e2248131c557e8ddefb4311fb4@haiku-os.org> #1898: getpeername returns size bigger than passed in? ---------------------------------------+------------------------------------ Reporter: tqh | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Resolution: fixed | Platform: All ---------------------------------------+------------------------------------ Comment (by tqh): Yes, I added a question mark because I wasn't really sure. Although you are only confusing me, I expect that getting a size bigger than I pass in shouldn't happen. I'll probably find some more stuff as I go along. I'll report them and let you guys sort them out. I think most bugs are on my side though.. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 8 19:22:26 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 08 Mar 2008 18:22:26 -0000 Subject: [Haiku-bugs] [Haiku] #1900: PANIC: page fault, but interrupts were disabled, ... Message-ID: <041.d22ef3f2e64866831498841e104bf80a@haiku-os.org> #1900: PANIC: page fault, but interrupts were disabled, ... ---------------------------+------------------------------------------------ Reporter: stippi | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Platform: All | ---------------------------+------------------------------------------------ ... Touching address 0x00000005 from eip 0x8005f5b6 stack crawl as follows: ... panic page_fault_exception int_bottom iframe... insert_page_after find_page_candidate steal_pages vm_pages_reserve_pages reserve_pages cache_io file_cache_read ReadAt bfs_read file_read common_user_io _user_read pre_syscall_debug_done iframe... GetNextChunk ExtractorThread extractor_thread _get_next_team_info media extractor thread_ Happened while testing certain Mindwork software under Haiku. At the point, the system was running for over 7 hours and downloaded over 4 GB of playback objects. The caches were utilising a good chunk of the 2 GB of memory, the player was just launching, so I guess the system was trying to free no more used cached pages to make room for the player. Don't know yet if it is easily reproducable. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 8 20:59:23 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 08 Mar 2008 19:59:23 -0000 Subject: [Haiku-bugs] [Haiku] #1901: Radeon driver: Get Radeon X1250 working. Message-ID: <038.9bda2c30c08cb1496eea53d36e9b34a6@haiku-os.org> #1901: Radeon driver: Get Radeon X1250 working. -------------------------------------+-------------------------------------- Reporter: tqh | Owner: euan Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/radeon | Version: R1 development Platform: All | -------------------------------------+-------------------------------------- Created a bug so EuanK has someone to bug to test Radeon X1250 support. Haiku currently boots to vesa in r24312 gcc4 build. Nothing urgent as VESA is working fine. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 8 21:31:34 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 08 Mar 2008 20:31:34 -0000 Subject: [Haiku-bugs] [Haiku] #1901: Radeon driver: Get Radeon X1250 working. In-Reply-To: <038.9bda2c30c08cb1496eea53d36e9b34a6@haiku-os.org> References: <038.9bda2c30c08cb1496eea53d36e9b34a6@haiku-os.org> Message-ID: <047.1511653dbe2697ecc1ab20ff7b2f155d@haiku-os.org> #1901: Radeon driver: Get Radeon X1250 working. --------------------------------------+------------------------------------- Reporter: tqh | Owner: euan Type: enhancement | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Graphics/radeon | Version: R1 development Resolution: | Platform: All --------------------------------------+------------------------------------- Changes (by euan): * status: new => assigned Comment: Thanks. The X1250 is a RS690 chipset and one of the AVIVO series. Will need radeon hd support. looking into it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 8 21:34:03 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 08 Mar 2008 20:34:03 -0000 Subject: [Haiku-bugs] [Haiku] #1901: Radeon driver: Get Radeon X1250 working. In-Reply-To: <038.9bda2c30c08cb1496eea53d36e9b34a6@haiku-os.org> References: <038.9bda2c30c08cb1496eea53d36e9b34a6@haiku-os.org> Message-ID: <047.d63ba325f73cbcb47effb5a10e84c21e@haiku-os.org> #1901: Radeon driver: Get Radeon X1250 working. --------------------------------------+------------------------------------- Reporter: tqh | Owner: euan Type: enhancement | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Graphics/radeon | Version: R1 development Resolution: | Platform: All --------------------------------------+------------------------------------- Comment (by stippi): Thanks, Euan! I have a X1400 here. Fingers crossed... :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 9 01:03:41 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 09 Mar 2008 00:03:41 -0000 Subject: [Haiku-bugs] [Haiku] #1898: getpeername returns size bigger than passed in? In-Reply-To: <038.caeeb8a1651bd335cee046c5c0969fa0@haiku-os.org> References: <038.caeeb8a1651bd335cee046c5c0969fa0@haiku-os.org> Message-ID: <047.ffeb19a61759b169e709e58bd4bb3ce2@haiku-os.org> #1898: getpeername returns size bigger than passed in? ---------------------------------------+------------------------------------ Reporter: tqh | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Resolution: | Platform: All ---------------------------------------+------------------------------------ Changes (by tqh): * status: closed => reopened * resolution: fixed => Comment: I think there are still issues, these are just printfs with what I get from Haiku's getpeername: First call: _MD_getpeername:addrlen = 28 [called] _MD_getpeername:addrlen after = 28 _MD_getpeername:sockaddr.sa_len after = 82 Second call: _MD_getpeername:addrlen = 28 [called] _MD_getpeername:addrlen after = 32 _MD_getpeername:sockaddr.sa_len after = 32 First call has very strange things going on with the sa_len field. Mozilla treats sa_len and sa_family and that is set to 8786 in decimal. That's 0x2252 which I can't make any sense of at all. Second at least seems to be ok in general as family is AF_INET at least but there the it returns a bigger size. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 9 06:42:53 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 09 Mar 2008 05:42:53 -0000 Subject: [Haiku-bugs] [Haiku] #1885: find KDLs when searching iso9660 dvd In-Reply-To: <042.dccdac296a799b1a691dd7ee32cd9aaf@haiku-os.org> References: <042.dccdac296a799b1a691dd7ee32cd9aaf@haiku-os.org> Message-ID: <051.8baeb500688efe9f15dd9646efd06454@haiku-os.org> #1885: find KDLs when searching iso9660 dvd ------------------------------------+--------------------------------------- Reporter: qyellow | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/ISO 9660 | Version: R1 development Resolution: | Platform: All ------------------------------------+--------------------------------------- Comment (by qyellow): sorry about that here is the remaining stack crawl: 9472f9ec (+ 52) 80082543 :invoke_debugger_command + 0x00cf 9472fa20 (+ 64) 800832e4 :_ParseCommand__16expressionParserRi +0x01f8 9472fa60 (+ 48) 80082cd6 :EvaluateCommand__16ExpressionParserPCcRi + 0x01f8 9472fa90 (+ 228) 800843f8 :evaluate_debug_command + 0x0088 9472fb74 (+ 64) 80081116 :kernel_debugger_loop_Fr + 0x017a 9472fbb4 (+ 48) 80081d61 :kernel_debugger + 0x017a 9472fbe4 (+ 192) 80081c49 :panic + 0x0029 9472fca4 (+ 48) 800260f8 :free + 0x0074 9472fcd4 (+ 96) 80209286 : InitNode + 0x0682 9472fd34 (+ 384) 80208817 : isoReadDirEnt + 0x01c3 9472fe64 (+ 48) 8020aab9 : fs_read_dir__FPvN20P6direntu1pu1 +0x002d 9472fe94 (+ 64) 8004a716 :dir_read__FP5vnodepvp6direntu1pu1 + 0x004e 9472fed4 (+ 64) 8004a59e :dir_read__FPI5file_descriptorP6direntu1pu1+0x0026 9472ff14 (+ 48) 8004432d :_user_read_dir + 0x0065 9472ff44 (+ 100) 80091de2 :pre_syscall_debug_done +0x0002 (nearest) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 9 10:35:11 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 09 Mar 2008 09:35:11 -0000 Subject: [Haiku-bugs] [Haiku] #1902: Sounds wont play when set for events in Preferences, Sounds Message-ID: <040.ac6900c337f6596133ff0b76557455c7@haiku-os.org> #1902: Sounds wont play when set for events in Preferences, Sounds --------------------------------+------------------------------------------- Reporter: cebif | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Preferences/Sounds | Version: R1 development Platform: All | --------------------------------+------------------------------------------- If I copy some *wav sounds to /boot/beos/etc/sounds, then apply wav sounds to events in Sounds preferences application, when any event occurs that is set with a sound it wont play.If I reboot the BeStartup.wav wont play if I have set it. To reproduce: 1) Open Preferences/Sounds. 2)Assign a *wav sound like BeStartup.wav to BeStartup. 3) Close the Sounds application. 4) Reboot On reboot the BeStartup.wav sound does not play. This is reproduceable every time. On openning Preferences Sounds the assigned sound is seen to be still set but it wont play. A sound will play if you click play in the Sounds application though. The version I was testing was: r24280 on its own partition. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 9 10:35:21 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 09 Mar 2008 09:35:21 -0000 Subject: [Haiku-bugs] [Haiku] #1898: getpeername returns size bigger than passed in? In-Reply-To: <038.caeeb8a1651bd335cee046c5c0969fa0@haiku-os.org> References: <038.caeeb8a1651bd335cee046c5c0969fa0@haiku-os.org> Message-ID: <047.37c6965bdc9d5f25d446672eab61972d@haiku-os.org> #1898: getpeername returns size bigger than passed in? ---------------------------------------+------------------------------------ Reporter: tqh | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Resolution: fixed | Platform: All ---------------------------------------+------------------------------------ Changes (by axeld): * status: reopened => closed * resolution: => fixed Comment: As I said, it is supposed to return the *actual* size, not the one of the buffer. The first call looks like some missing initialization, so it does not have anything to do with the original bug. Please file a new bug report for this problem, and also mention the circumstances, ie. what kind of socket, is it already connected, bound, in use, whatever. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 9 11:37:40 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 09 Mar 2008 10:37:40 -0000 Subject: [Haiku-bugs] [Haiku] #1903: ifconfig: media selection option is available but not supported. Message-ID: <043.e74d07eafcc65776cc6a1ed6b170c066@haiku-os.org> #1903: ifconfig: media selection option is available but not supported. ------------------------------+--------------------------------------------- Reporter: siarzhuk | Owner: axeld Type: bug | Status: new Priority: low | Milestone: Component: Kits/Network Kit | Version: Platform: All | ------------------------------+--------------------------------------------- [Haiku r24319] Yesterday I have asked on IRC about possibility to switch network media to some non-default value under Haiku. mmu_man was so kind that very quickly added media selection option into ifconfig. Following tests and comments in commits e-mail list show me that the problem is a bit deeper. :-) I register this ticket just to document "media option" issue. At the moment this looks like a bug: option is available for user selection in ifconfig but is not supported by Haiku network. Should we rollback media option changes or finish media change possibility in Haiku network? Some words about situation which forces me to switch network media: I have AVM FritzBox! SL DSL modem with possibility to connect PC with ethernet. Second actor of this drama is my laptop with embedded rtl8139 network. In default case laptop network configure media to 100 MBit but resulting connection is non-usable - about 40-50%% of packets are lost. This situation is reproducible under all operating systems I use: R5, Haiku, FreeBSD, Windows. The solution is manual change of media type to 10 MBit. This fixes my problem. At the moment I have hardcoded 10 MBit media mode in my local copy of Haiku rtl8139 driver. I can use and test network under Haiku now so this problem is not urgent or significant for me. ;-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 9 12:06:20 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 09 Mar 2008 11:06:20 -0000 Subject: [Haiku-bugs] [Haiku] #1898: getpeername returns size bigger than passed in? In-Reply-To: <038.caeeb8a1651bd335cee046c5c0969fa0@haiku-os.org> References: <038.caeeb8a1651bd335cee046c5c0969fa0@haiku-os.org> Message-ID: <047.27638b907b37e9c103a7f853d802cf4b@haiku-os.org> #1898: getpeername returns size bigger than passed in? ---------------------------------------+------------------------------------ Reporter: tqh | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Resolution: fixed | Platform: All ---------------------------------------+------------------------------------ Comment (by tqh): That is not how I understand it, also it is not how it is used on ANY other platform in Mozilla. Here is from FreeBSD http://www.freebsd.org/cgi/man.cgi?query=getpeername&apropos=0&sektion=0&manpath=FreeBSD+6.3-RELEASE&format=html: "The namelen argument should be initialized to indicate the amount of space pointed to by name. On return it contains the actual size of the name '''returned''' (in bytes)." -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 9 13:45:58 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 09 Mar 2008 12:45:58 -0000 Subject: [Haiku-bugs] [Haiku] #1898: getpeername returns size bigger than passed in? In-Reply-To: <038.caeeb8a1651bd335cee046c5c0969fa0@haiku-os.org> References: <038.caeeb8a1651bd335cee046c5c0969fa0@haiku-os.org> Message-ID: <047.842e2385635e010eee117c25c2563624@haiku-os.org> #1898: getpeername returns size bigger than passed in? ---------------------------------------+------------------------------------ Reporter: tqh | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Resolution: fixed | Platform: All ---------------------------------------+------------------------------------ Comment (by axeld): I agree that http://www.opengroup.org/onlinepubs/009695399/functions/getpeername.html is not as clear as one could wish for. However, quoting from the POSIX standard 1003.1g: {{{"[...] fromlen shall refer to the value before truncation [...]"}}} I've also written a small test application, and at least Linux behaves exactly like that, too. It might be different on other platforms, but I prefer following the standard. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 9 13:52:49 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 09 Mar 2008 12:52:49 -0000 Subject: [Haiku-bugs] [Haiku] #1898: getpeername returns size bigger than passed in? In-Reply-To: <038.caeeb8a1651bd335cee046c5c0969fa0@haiku-os.org> References: <038.caeeb8a1651bd335cee046c5c0969fa0@haiku-os.org> Message-ID: <047.d3e9f0d9e0af7496c1ba61f4d16e8445@haiku-os.org> #1898: getpeername returns size bigger than passed in? ---------------------------------------+------------------------------------ Reporter: tqh | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Resolution: fixed | Platform: All ---------------------------------------+------------------------------------ Comment (by tqh): Ok, thanks for clearing that up. Following the spec is fine by me. Do you know how BeOS behaves in this case, I guess I'll have to do some adaption at my end and it would be nice to know. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 9 14:33:02 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 09 Mar 2008 13:33:02 -0000 Subject: [Haiku-bugs] [Haiku] #1904: Hardware cursor not working on Matrox G200 Message-ID: <041.06af9b77cc563920e55d0b2a0642c1c8@haiku-os.org> #1904: Hardware cursor not working on Matrox G200 ------------------------------+--------------------------------------------- Reporter: biffuz | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics | Version: R1 development Platform: x86 | ------------------------------+--------------------------------------------- On my Matrox G200 8 Mb SGRAM AGP 2x, hardware mouse cursor acceleration does not work, neither in Haiku or BeOS R5. Under ZETA 1.2 it works, and with the same driver! (this is the latest revision, but this happened with older ones, too) Oh, and in the Ticket Properties, the Matrox driver doesn't even appear... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 9 16:32:44 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 09 Mar 2008 15:32:44 -0000 Subject: [Haiku-bugs] [Haiku] #1898: getpeername returns size bigger than passed in? In-Reply-To: <038.caeeb8a1651bd335cee046c5c0969fa0@haiku-os.org> References: <038.caeeb8a1651bd335cee046c5c0969fa0@haiku-os.org> Message-ID: <047.a7f85f19053547560b5ade334078b3f3@haiku-os.org> #1898: getpeername returns size bigger than passed in? ---------------------------------------+------------------------------------ Reporter: tqh | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Resolution: fixed | Platform: All ---------------------------------------+------------------------------------ Comment (by axeld): I've added the getpeername.cpp test program to the repository, and tested it under Dano (ie. BONE), too. There, getpeername() behaves exactly as you suggested (and obviously as FreeBSD), ie. it returns the buffer size if that is smaller than the actual length of the address. Could you please open a ticket for the case with the strange values? Or did getpeername() just fail in this case? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 9 16:35:52 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 09 Mar 2008 15:35:52 -0000 Subject: [Haiku-bugs] [Haiku] #1904: Hardware cursor not working on Matrox G200 In-Reply-To: <041.06af9b77cc563920e55d0b2a0642c1c8@haiku-os.org> References: <041.06af9b77cc563920e55d0b2a0642c1c8@haiku-os.org> Message-ID: <050.8c5025efd058897975da5ce6691aa60c@haiku-os.org> #1904: Hardware cursor not working on Matrox G200 --------------------------------------+------------------------------------- Reporter: biffuz | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/Matrox | Version: R1 development Resolution: | Platform: x86 --------------------------------------+------------------------------------- Changes (by axeld): * component: Drivers/Graphics => Drivers/Graphics/Matrox Comment: Haiku currently does not support a hardware cursor at all. Since you have a problem on BeOS, we can keep this bug open to see remember checking if there are any issues with that driver once Haiku does support a hardware cursor. And thanks for the note, I've added the Matrox driver as component. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 9 18:21:53 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 09 Mar 2008 17:21:53 -0000 Subject: [Haiku-bugs] [Haiku] #1898: getpeername returns size bigger than passed in? In-Reply-To: <038.caeeb8a1651bd335cee046c5c0969fa0@haiku-os.org> References: <038.caeeb8a1651bd335cee046c5c0969fa0@haiku-os.org> Message-ID: <047.8fd0ff61846ce2094e3adf47f0ea4706@haiku-os.org> #1898: getpeername returns size bigger than passed in? ---------------------------------------+------------------------------------ Reporter: tqh | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Resolution: fixed | Platform: All ---------------------------------------+------------------------------------ Comment (by tqh): I'm not sure what's going on with those values. I want to investigate on my end first. I just posted them to see if it was something known. I'll post if I think it's Haiku's fault. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 9 18:29:45 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 09 Mar 2008 17:29:45 -0000 Subject: [Haiku-bugs] [Haiku] #1905: spurious mouse button presses Message-ID: <048.c86d21dd8a01afb02083fa8ec760c2d6@haiku-os.org> #1905: spurious mouse button presses ---------------------------+------------------------------------------------ Reporter: jonas.kirilla | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Platform: All | ---------------------------+------------------------------------------------ I've been seeing these spurious mouse button presses for a very long time, a year or more. (Mentioned in comments on #155.) The frequency is "often", maybe once per minute or so, I don't know for sure. I don't know if there's any regularity. I think it's always the left mouse button. I'm guessing it has to do with USB, but I really don't know. This is with a Microsoft "Wireless Optical Mouse Blue". See listdev output. Last tested on r24322. Will add USB device info. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 9 18:56:43 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 09 Mar 2008 17:56:43 -0000 Subject: [Haiku-bugs] [Haiku] #1799: sh: child setpgid (216 to 215): Operation not allowed In-Reply-To: <048.e9364d5c302fe040586f32fc48f3687b@haiku-os.org> References: <048.e9364d5c302fe040586f32fc48f3687b@haiku-os.org> Message-ID: <057.9693e91855d4591d6ea33d21704233f2@haiku-os.org> #1799: sh: child setpgid (216 to 215): Operation not allowed ----------------------------+----------------------------------------------- Reporter: jonas.kirilla | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Platform: All ----------------------------+----------------------------------------------- Changes (by bonefish): * status: assigned => closed * resolution: => fixed Comment: Fixed in r24335. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 9 20:43:18 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 09 Mar 2008 19:43:18 -0000 Subject: [Haiku-bugs] [Haiku] #1676: build_haiku_image: attrrmrf function uses linux/GNU specific stat option -c %i In-Reply-To: <039.b71c9c07139e67daa3b0d628042d6a58@haiku-os.org> References: <039.b71c9c07139e67daa3b0d628042d6a58@haiku-os.org> Message-ID: <048.23e7b532931a059307f7b0b84ec93354@haiku-os.org> #1676: build_haiku_image: attrrmrf function uses linux/GNU specific stat option -c %i ---------------------------+------------------------------------------------ Reporter: gogo | Owner: mmu_man Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by mmu_man): Should be fixed in r24337 but I didn't try so please do. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 9 20:58:49 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 09 Mar 2008 19:58:49 -0000 Subject: [Haiku-bugs] [Haiku] #1799: sh: child setpgid (216 to 215): Operation not allowed In-Reply-To: <048.e9364d5c302fe040586f32fc48f3687b@haiku-os.org> References: <048.e9364d5c302fe040586f32fc48f3687b@haiku-os.org> Message-ID: <057.1ce0b9fe9d6c291f5366db7905c00ad6@haiku-os.org> #1799: sh: child setpgid (216 to 215): Operation not allowed ----------------------------+----------------------------------------------- Reporter: jonas.kirilla | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Platform: All ----------------------------+----------------------------------------------- Comment (by jonas.kirilla): I can still reproduce it with r24336. :/ http://www.kirilla.com/haiku/r24336-1.png http://www.kirilla.com/haiku/r24336-2.png -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 10 00:37:17 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 09 Mar 2008 23:37:17 -0000 Subject: [Haiku-bugs] [Haiku] #1799: sh: child setpgid (216 to 215): Operation not allowed In-Reply-To: <048.e9364d5c302fe040586f32fc48f3687b@haiku-os.org> References: <048.e9364d5c302fe040586f32fc48f3687b@haiku-os.org> Message-ID: <057.022123f464e6e4803e49b98d675d0286@haiku-os.org> #1799: sh: child setpgid (216 to 215): Operation not allowed ----------------------------+----------------------------------------------- Reporter: jonas.kirilla | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Platform: All ----------------------------+----------------------------------------------- Comment (by bonefish): Replying to [comment:6 jonas.kirilla]: > I can still reproduce it with r24336. :/ As it looks to me, this only happens when hitting Ctrl-C while the shell is in the middle of setting up the pipe. For the first process setpgid() has already been done and it has been given the terminal. Hitting Ctrl-C right then will cause a SIGINT to be sent to the new process group and kill all child processes that have already joined the group. Since the shell blocks SIGCHLD only while creating a child process, as soon as it is unblocked, the SIGCHLD handler is invoked, which does a waitpid() and thus causes the process group to be deleted for good. Afterwards the shell continues to create the remaining processes of the pipe and setpgid() will fail for them. This seems to be a (design?) problem in bash rather than a bug in Haiku. At least I don't see what we could possibly be doing wrong. The original bug seems to be fixed at any rate. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 10 03:35:04 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 10 Mar 2008 02:35:04 -0000 Subject: [Haiku-bugs] [Haiku] #1711: Haiku stops booting at allocate_commpage_entry(4, 34) In-Reply-To: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> References: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> Message-ID: <048.0fe8566cd6e486b6ae7fe6a4ac28d720@haiku-os.org> #1711: Haiku stops booting at allocate_commpage_entry(4, 34) ----------------------------+----------------------------------------------- Reporter: euan | Owner: korli Type: bug | Status: new Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by dustin howett): Haiku fails to boot when i have 3GB of RAM in my system (128 is shared video ram), but works with 1 or 2 GB. Linux MTRRs: {{{ reg00: base=0x00000000 ( 0MB), size=2048MB: write-back, count=1 reg01: base=0x80000000 (2048MB), size= 512MB: write-back, count=1 reg02: base=0xa0000000 (2560MB), size= 128MB: write-back, count=1 reg03: base=0xc0000000 (3072MB), size= 128MB: write-combining, count=1 }}} Haiku MTRRs: {{{ 0: base=0x00000000, size = 2048 MB. 1: base=0x80000000, size = 1024 MB. 2: base=0xc0000000, size = 1 MB. }}} {{{ (08:41:35 PM) DHowett: geist: Haiku's adds up to 3gb.. linux up to less than that but i take that to be related to my 128 mb shared video ram (08:43:33 PM) geist: could be (08:43:45 PM) geist: yeah, bet haiku is marking over the video ram as regular mem }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 10 03:36:46 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 10 Mar 2008 02:36:46 -0000 Subject: [Haiku-bugs] [Haiku] #1891: No keyboard or mouse input on real hardware In-Reply-To: <043.3e5b5319685d174aa810166ac0cef370@haiku-os.org> References: <043.3e5b5319685d174aa810166ac0cef370@haiku-os.org> Message-ID: <052.db2ea7dd697fd5761a7efffa2740e5c8@haiku-os.org> #1891: No keyboard or mouse input on real hardware --------------------------+------------------------------------------------- Reporter: salierix | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by dustin howett): I'm experiencing this issue as well, but installing ohci does not fix it. Keyboard and mouse are ps/2, and they work in the bootloader, but not in safe mode or normal mode. Can't disable USB Legacy because my manufacturer has locked down the BIOS severely. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 10 16:50:24 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 10 Mar 2008 15:50:24 -0000 Subject: [Haiku-bugs] [Haiku] #1836: OpenGL output not visible on screenshots In-Reply-To: <041.35c11d2f8648ac43478bc54b950533aa@haiku-os.org> References: <041.35c11d2f8648ac43478bc54b950533aa@haiku-os.org> Message-ID: <050.af0ac9fc1365336fc70a3792835957b7@haiku-os.org> #1836: OpenGL output not visible on screenshots ------------------------------+--------------------------------------------- Reporter: ekdahl | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/OpenGL Kit | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by korli): Could you check against r24346 please ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 10 23:52:38 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 10 Mar 2008 22:52:38 -0000 Subject: [Haiku-bugs] [Haiku] #1711: Haiku stops booting at allocate_commpage_entry(4, 34) In-Reply-To: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> References: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> Message-ID: <048.f0a30fda8ef8a18bf79f180b6eaf8138@haiku-os.org> #1711: Haiku stops booting at allocate_commpage_entry(4, 34) ----------------------------+----------------------------------------------- Reporter: euan | Owner: korli Type: bug | Status: new Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by euan): Ok so I managed to hook up my laptop and get a debug trace. Unfortunately the only difference is that it hangs one line before the original log. So the allocate_comm_page_entry line is never printed now. So not fixed as yet. :( -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 11 03:15:48 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 11 Mar 2008 02:15:48 -0000 Subject: [Haiku-bugs] [Haiku] #1891: No keyboard or mouse input on real hardware In-Reply-To: <043.3e5b5319685d174aa810166ac0cef370@haiku-os.org> References: <043.3e5b5319685d174aa810166ac0cef370@haiku-os.org> Message-ID: <052.673c5e1024a46a9b5b267de9a9b9ec7a@haiku-os.org> #1891: No keyboard or mouse input on real hardware --------------------------+------------------------------------------------- Reporter: salierix | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by zenja): I've experienced the same error as Salierix. Adding ohci addon to kernel/busses/usb suddenly allows a PS2 keyboard and mouse to work. nForce 590 motherboard. Weird. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 11 13:18:28 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 11 Mar 2008 12:18:28 -0000 Subject: [Haiku-bugs] [Haiku] #1906: BeIDE crash Message-ID: <040.101ee775fff9b72592882d61daa31318@haiku-os.org> #1906: BeIDE crash --------------------------+------------------------------------------------- Reporter: thorn | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Platform: All | --------------------------+------------------------------------------------- tested under r24348 open BeIDE select File->About BeIDE -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 11 14:12:19 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 11 Mar 2008 13:12:19 -0000 Subject: [Haiku-bugs] [Haiku] #1711: Haiku stops booting at allocate_commpage_entry(4, 34) In-Reply-To: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> References: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> Message-ID: <048.0ec70326fc95ff5b76c446f302e2ebdf@haiku-os.org> #1711: Haiku stops booting at allocate_commpage_entry(4, 34) ----------------------------+----------------------------------------------- Reporter: euan | Owner: korli Type: bug | Status: new Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by korli): I would need additional information if it's possible : on Linux, you should find something about "BIOS-provided physical RAM map" in /var/log/messages, especially lines beginning with "BIOS-e820". Thanks. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 11 14:18:19 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 11 Mar 2008 13:18:19 -0000 Subject: [Haiku-bugs] [Haiku] #1711: Haiku stops booting at allocate_commpage_entry(4, 34) In-Reply-To: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> References: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> Message-ID: <048.617f0d2d88a8d2363c4a5deca6c83e8b@haiku-os.org> #1711: Haiku stops booting at allocate_commpage_entry(4, 34) ----------------------------+----------------------------------------------- Reporter: euan | Owner: korli Type: bug | Status: new Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by euan): Darn I had that saved off to a file too for uploading. I won't be back home until Wednesday sorry. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 11 18:53:08 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 11 Mar 2008 17:53:08 -0000 Subject: [Haiku-bugs] [Haiku] #1907: Replace GNU C library and utilities with BSD-licensed equivalents Message-ID: <048.98b30fdc24139afd5cfafbfcf2ba0441@haiku-os.org> #1907: Replace GNU C library and utilities with BSD-licensed equivalents -------------------------------+-------------------------------------------- Reporter: jonas.kirilla | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Platform: All | -------------------------------+-------------------------------------------- Not that this is strictly necessary but it would lessen the GPL footprint in Haiku and could lead to more cooperation with the BSDs. This could be a GSoC project. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 11 19:04:58 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 11 Mar 2008 18:04:58 -0000 Subject: [Haiku-bugs] [Haiku] #1908: page_fault in network stack (using Firefox) Message-ID: <041.6791160cc3e1d20aeb33f16337318daa@haiku-os.org> #1908: page_fault in network stack (using Firefox) --------------------------------------+------------------------------------- Reporter: stippi | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Platform: All | --------------------------------------+------------------------------------- I just booted Haiku and launched Firefox without much delay. Next thing I know, I was in KDL: {{{ ... page_fault_exception int_bottom iframe... list_remove_link list_remove_head_item delete_children socket_delete socket_free net_stack_free_cookie devfs_free_cookie file_free_fd put_fd common_close _user_close pre_syscall_debug_done iframe... closesocket }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 11 19:37:37 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 11 Mar 2008 18:37:37 -0000 Subject: [Haiku-bugs] [Haiku] #1907: Replace GNU C library and utilities with BSD-licensed equivalents In-Reply-To: <048.98b30fdc24139afd5cfafbfcf2ba0441@haiku-os.org> References: <048.98b30fdc24139afd5cfafbfcf2ba0441@haiku-os.org> Message-ID: <057.c0f07306d869b73492c2da1638ae1c6e@haiku-os.org> #1907: Replace GNU C library and utilities with BSD-licensed equivalents --------------------------------+------------------------------------------- Reporter: jonas.kirilla | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Resolution: | Platform: All --------------------------------+------------------------------------------- Comment (by axeld): The GNU C library is licensed under the LGPL. I personally don't mind GPL utilities at all; and IMO we shouldn't decide by license, but by code quality. Also, I don't think this would be a good GSoC project for now, as it doesn't advance the project in any way. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 11 19:53:13 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 11 Mar 2008 18:53:13 -0000 Subject: [Haiku-bugs] [Haiku] #1909: emuxki/midi related KDLs? Message-ID: <048.7c433231494081c4264c03b82f3ce97f@haiku-os.org> #1909: emuxki/midi related KDLs? ---------------------------+------------------------------------------------ Reporter: jonas.kirilla | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Platform: All | ---------------------------+------------------------------------------------ Two different KDL panics recently, (r24336?) happening at late bootup. thread: media_server_addon - unexpected exception "invalid opcode exception" thread: MidiPortProducer - unhandled page fault in kernel space See screenshots. Look for "midi". Coincidence? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 11 20:34:14 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 11 Mar 2008 19:34:14 -0000 Subject: [Haiku-bugs] [Haiku] #1711: Haiku stops booting at allocate_commpage_entry(4, 34) In-Reply-To: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> References: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> Message-ID: <048.a832966b9096bd70c7499add8d832fff@haiku-os.org> #1711: Haiku stops booting at allocate_commpage_entry(4, 34) ----------------------------+----------------------------------------------- Reporter: euan | Owner: korli Type: bug | Status: new Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by dustin howett): At least for me, with 3 GB RAM -- assuming i'm having the same class of issue as euan... {{{ BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 000000000009dc00 (usable) BIOS-e820: 000000000009dc00 - 00000000000a0000 (reserved) BIOS-e820: 00000000000d2000 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 00000000a7f00000 (usable) BIOS-e820: 00000000a7f00000 - 00000000a7f15000 (ACPI data) BIOS-e820: 00000000a7f15000 - 00000000a7f80000 (ACPI NVS) BIOS-e820: 00000000a7f80000 - 00000000b0000000 (reserved) BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved) BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved) BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved) BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved) BIOS-e820: 0000000100000000 - 0000000110000000 (usable) }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 11 21:46:46 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 11 Mar 2008 20:46:46 -0000 Subject: [Haiku-bugs] [Haiku] #1909: emuxki/midi related KDLs? In-Reply-To: <048.7c433231494081c4264c03b82f3ce97f@haiku-os.org> References: <048.7c433231494081c4264c03b82f3ce97f@haiku-os.org> Message-ID: <057.32899323d2d6b979cb4c4100526bf6c0@haiku-os.org> #1909: emuxki/midi related KDLs? ----------------------------+----------------------------------------------- Reporter: jonas.kirilla | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by jonas.kirilla): Sorry for all the confusing, disordered, undescribed screenshots. :( Most of them are almost identical versions of "invalid opcode exception" in the media_server_addon, with DSC03683.jpg and DSC03684.jpg being page faults instead. The one exception being the unhandled page fault of MidiPortProducer in DSC03675.jpg, which I suppose could be unrelated. These KDLs started appearing around the same time. Before there had been none. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 11 23:39:24 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 11 Mar 2008 22:39:24 -0000 Subject: [Haiku-bugs] [Haiku] #1909: emuxki/midi related KDLs? In-Reply-To: <048.7c433231494081c4264c03b82f3ce97f@haiku-os.org> References: <048.7c433231494081c4264c03b82f3ce97f@haiku-os.org> Message-ID: <057.53366ea6fc5eee62d107e9d18aaa86d8@haiku-os.org> #1909: emuxki/midi related KDLs? ----------------------------+----------------------------------------------- Reporter: jonas.kirilla | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by korli): Is this new ? I don't understand well why the midi dev entry of emuxki is opened by the multiaudio addon ... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 11 23:51:45 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 11 Mar 2008 22:51:45 -0000 Subject: [Haiku-bugs] [Haiku] #1909: emuxki/midi related KDLs? In-Reply-To: <048.7c433231494081c4264c03b82f3ce97f@haiku-os.org> References: <048.7c433231494081c4264c03b82f3ce97f@haiku-os.org> Message-ID: <057.94dad67e4f67f4ce3abfb7f6ec281891@haiku-os.org> #1909: emuxki/midi related KDLs? ----------------------------+----------------------------------------------- Reporter: jonas.kirilla | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by stippi): Are you already using an image which has the fixed VideoWindow media add- on already? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 12 00:03:29 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 11 Mar 2008 23:03:29 -0000 Subject: [Haiku-bugs] [Haiku] #1910: Page fault with hda Message-ID: <044.4be623d20aa6f058c673c3283a04a314@haiku-os.org> #1910: Page fault with hda ---------------------------+------------------------------------------------ Reporter: pieterpan | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Platform: x86 | ---------------------------+------------------------------------------------ With r24364 : When the system has almost finished booting and (I think) wants to do something with the audio driver it kdl's. Probably related to the last commits, hope this info is helpful. Before these changes I would get no kdl, but also no sound (and no controls). If I remove the hda from /boot/beos/system/add-ons/kernel/drivers/bin, it boots fine. I have a laptop with HD audio. Typed from listdev: {{{ device Multimedia controller ( Audio device ) [4|3|0] vendor 8086: Intel Corporation device 284b:82801H (ICH8 Family) HD Audio Controller }}} See attached screenshot (by camera) If someone knows of a way to copy files from Haiku to ubuntu/windows, without having a network driver, let me know :) Perhaps with fs_shell, but I don't know how to use it? Unfortunately beos does not work on my laptop... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 12 00:05:53 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 11 Mar 2008 23:05:53 -0000 Subject: [Haiku-bugs] [Haiku] #1910: Page fault with hda In-Reply-To: <044.4be623d20aa6f058c673c3283a04a314@haiku-os.org> References: <044.4be623d20aa6f058c673c3283a04a314@haiku-os.org> Message-ID: <053.a2dab94f98866907ddaff82e9f4c246a@haiku-os.org> #1910: Page fault with hda ----------------------------+----------------------------------------------- Reporter: pieterpan | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Changes (by korli): * owner: korli => axeld -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 12 00:10:01 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 11 Mar 2008 23:10:01 -0000 Subject: [Haiku-bugs] [Haiku] #1907: Replace GNU C library and utilities with BSD-licensed equivalents In-Reply-To: <048.98b30fdc24139afd5cfafbfcf2ba0441@haiku-os.org> References: <048.98b30fdc24139afd5cfafbfcf2ba0441@haiku-os.org> Message-ID: <057.f220b44f9fc17115f95d29189a5d7370@haiku-os.org> #1907: Replace GNU C library and utilities with BSD-licensed equivalents --------------------------------+------------------------------------------- Reporter: jonas.kirilla | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Resolution: | Platform: All --------------------------------+------------------------------------------- Comment (by korli): And BeOS used them so why not Haiku ? IMO should be marked as invalid. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 12 00:17:10 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 11 Mar 2008 23:17:10 -0000 Subject: [Haiku-bugs] [Haiku] #1909: emuxki/midi related KDLs? In-Reply-To: <048.7c433231494081c4264c03b82f3ce97f@haiku-os.org> References: <048.7c433231494081c4264c03b82f3ce97f@haiku-os.org> Message-ID: <057.dd72a7bddb079deef28e81de9ce0bc60@haiku-os.org> #1909: emuxki/midi related KDLs? ----------------------------+----------------------------------------------- Reporter: jonas.kirilla | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by jonas.kirilla): Replying to [comment:3 stippi]: > Are you already using an image which has the fixed VideoWindow media add-on already? If you're referring to r24273 (5 days ago): yes, I'm way past that rev. If you're referring to r24362 (2 hours ago): no, I have not tried that revision yet. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 12 00:31:48 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 11 Mar 2008 23:31:48 -0000 Subject: [Haiku-bugs] [Haiku] #1907: Replace GNU C library and utilities with BSD-licensed equivalents In-Reply-To: <048.98b30fdc24139afd5cfafbfcf2ba0441@haiku-os.org> References: <048.98b30fdc24139afd5cfafbfcf2ba0441@haiku-os.org> Message-ID: <057.88191bfa0b4b3b1ee5e37670adc43f8d@haiku-os.org> #1907: Replace GNU C library and utilities with BSD-licensed equivalents --------------------------------+------------------------------------------- Reporter: jonas.kirilla | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Resolution: | Platform: All --------------------------------+------------------------------------------- Comment (by jonas.kirilla): If there is a high quality libc and full userland with a license which has synergy with that of core parts of Haiku it seems logical to at least not shut the door completely, even though it may not seem practical right now. I know that it's perfectly okay to run GPL software on Haiku and to integrate LGPL code. But, FWIW, if the GPL parts were BSD-licensed it would be less problematic to reuse that code elsewhere. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 12 07:13:41 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 12 Mar 2008 06:13:41 -0000 Subject: [Haiku-bugs] [Haiku] #1911: PANIC: heap: huge allocation of 6292992 bytes asked! Message-ID: <040.1669ad96ac1dfccf47005827906732ce@haiku-os.org> #1911: PANIC: heap: huge allocation of 6292992 bytes asked! -----------------------+---------------------------------------------------- Reporter: thorn | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- Haiku r24348 backtrace included -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 12 07:21:11 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 12 Mar 2008 06:21:11 -0000 Subject: [Haiku-bugs] [Haiku] #1911: PANIC: heap: huge allocation of 6292992 bytes asked! In-Reply-To: <040.1669ad96ac1dfccf47005827906732ce@haiku-os.org> References: <040.1669ad96ac1dfccf47005827906732ce@haiku-os.org> Message-ID: <049.7e171be7784fede0e0213a8055942722@haiku-os.org> #1911: PANIC: heap: huge allocation of 6292992 bytes asked! -------------------------------+-------------------------------------------- Reporter: thorn | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Changes (by thorn): * component: - General => File Systems/BFS Comment: after reboot: bfs: Replay log, disk was not correctly unmounted... run count: 11264, array max: -1, max runs: 254 bfs: Log entry has broken header! bfs: replaying log entry from 452 failed: Bad data bfs: could not initialize journal/block bitmap allocator! bfs: bfs_mount:127: Out of memory SCSI_DSK -- synchronize_cache: bfs: Remove:1680: No such file or directory bfs: Could not find value in index "size"! bfs: Remove:1680: No such file or directory bfs: Could not find value in index "last_modified"! SCSI_DSK -- synchronize_cache: -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 12 10:03:07 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 12 Mar 2008 09:03:07 -0000 Subject: [Haiku-bugs] [Haiku] #1910: Page fault with hda In-Reply-To: <044.4be623d20aa6f058c673c3283a04a314@haiku-os.org> References: <044.4be623d20aa6f058c673c3283a04a314@haiku-os.org> Message-ID: <053.c181c4c337807ce4c4b63064a9200c6a@haiku-os.org> #1910: Page fault with hda --------------------------------+------------------------------------------- Reporter: pieterpan | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio/HDA | Version: R1 development Resolution: | Platform: x86 --------------------------------+------------------------------------------- Changes (by axeld): * component: Drivers/Audio => Drivers/Audio/HDA Comment: I'm currently rewriting that part. I hope to get HDA working soon. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 12 10:04:45 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 12 Mar 2008 09:04:45 -0000 Subject: [Haiku-bugs] [Haiku] #1911: PANIC: heap: huge allocation of 6292992 bytes asked! In-Reply-To: <040.1669ad96ac1dfccf47005827906732ce@haiku-os.org> References: <040.1669ad96ac1dfccf47005827906732ce@haiku-os.org> Message-ID: <049.b187d4c163c85116fc68d3bfc1c7208c@haiku-os.org> #1911: PANIC: heap: huge allocation of 6292992 bytes asked! -------------------------------+-------------------------------------------- Reporter: thorn | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: File Systems/BFS | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Changes (by axeld): * priority: normal => high * milestone: R1 => R1/alpha1 Comment: What size is your disk? BFS currently loads the whole block bitmap on mount to correct an eventual incorrect used block count. There is no reason why it does it this way, though. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 12 10:06:57 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 12 Mar 2008 09:06:57 -0000 Subject: [Haiku-bugs] [Haiku] #1912: QuickRes: unresolved symbol Message-ID: <040.d1a49ccfaa51c8809d3f3148c6561fbe@haiku-os.org> #1912: QuickRes: unresolved symbol --------------------------------+------------------------------------------- Reporter: thorn | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Platform: All | --------------------------------+------------------------------------------- r24348 /boot/develop/tools/experimental/QuickRes>QuickRes elf_resolve_symbol: could not resolve symbol 'Invoke__15BColumnListViewP8BMessage' resolve symbol "Invoke__15BColumnListViewP8BMessage" returned: -2147478780 runtime_loader: troubles relocating: 0x80001304 (image: _APP_) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 12 11:06:56 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 12 Mar 2008 10:06:56 -0000 Subject: [Haiku-bugs] [Haiku] #1911: PANIC: heap: huge allocation of 6292992 bytes asked! In-Reply-To: <040.1669ad96ac1dfccf47005827906732ce@haiku-os.org> References: <040.1669ad96ac1dfccf47005827906732ce@haiku-os.org> Message-ID: <049.58ee73fbc5455f1456849e5cf402df09@haiku-os.org> #1911: PANIC: heap: huge allocation of 6292992 bytes asked! -------------------------------+-------------------------------------------- Reporter: thorn | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: File Systems/BFS | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Comment (by thorn): I can try to repeat and send broken bfs image to you. bfs volume - 2G block size - 2048 memory - 256M -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 12 11:22:09 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 12 Mar 2008 10:22:09 -0000 Subject: [Haiku-bugs] [Haiku] #1912: QuickRes: unresolved symbol In-Reply-To: <040.d1a49ccfaa51c8809d3f3148c6561fbe@haiku-os.org> References: <040.d1a49ccfaa51c8809d3f3148c6561fbe@haiku-os.org> Message-ID: <049.b3513df25abe7b3dde886f546ea6b959@haiku-os.org> #1912: QuickRes: unresolved symbol ---------------------------------+------------------------------------------ Reporter: thorn | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: invalid | Platform: All ---------------------------------+------------------------------------------ Changes (by axeld): * status: new => closed * resolution: => invalid Comment: Applications that use the private BColumnListView implementation are not supposed to work under Haiku. See bug #418 for more details. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 12 12:52:26 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 12 Mar 2008 11:52:26 -0000 Subject: [Haiku-bugs] [Haiku] #1842: Black box around mouse cursor when holding it in front of GLTeapot In-Reply-To: <041.0221c706d2f7a2d12d78685dd18b9031@haiku-os.org> References: <041.0221c706d2f7a2d12d78685dd18b9031@haiku-os.org> Message-ID: <050.c58487fa084e0f44ebbcc6f889e3472d@haiku-os.org> #1842: Black box around mouse cursor when holding it in front of GLTeapot ------------------------+--------------------------------------------------- Reporter: ekdahl | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: invalid | Platform: All ------------------------+--------------------------------------------------- Comment (by ekdahl): Is this bug really invalid? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 12 12:54:19 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 12 Mar 2008 11:54:19 -0000 Subject: [Haiku-bugs] [Haiku] #1836: OpenGL output not visible on screenshots In-Reply-To: <041.35c11d2f8648ac43478bc54b950533aa@haiku-os.org> References: <041.35c11d2f8648ac43478bc54b950533aa@haiku-os.org> Message-ID: <050.5f358558b93a91515a08839653d2ac3c@haiku-os.org> #1836: OpenGL output not visible on screenshots ------------------------------+--------------------------------------------- Reporter: ekdahl | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/OpenGL Kit | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by ekdahl): Yes, I'll test as soon as I get a build system up and running again. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 12 13:01:48 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 12 Mar 2008 12:01:48 -0000 Subject: [Haiku-bugs] [Haiku] #1836: OpenGL output not visible on screenshots In-Reply-To: <041.35c11d2f8648ac43478bc54b950533aa@haiku-os.org> References: <041.35c11d2f8648ac43478bc54b950533aa@haiku-os.org> Message-ID: <050.7159d38bc8dbe5e06be56600f40de148@haiku-os.org> #1836: OpenGL output not visible on screenshots ------------------------------+--------------------------------------------- Reporter: ekdahl | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/OpenGL Kit | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by stippi): No need, the output is still mysteriously missing from screenshots. Have no time to look into it right now. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 12 13:01:50 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 12 Mar 2008 12:01:50 -0000 Subject: [Haiku-bugs] [Haiku] #1682: AddSourceDirectoryToHaikuImage doesn't work with spaces in file names In-Reply-To: <041.14ef3b7b09156af14e6cab73aca52dd6@haiku-os.org> References: <041.14ef3b7b09156af14e6cab73aca52dd6@haiku-os.org> Message-ID: <050.79d669de01f0fb3a7f5f34633d2cc02a@haiku-os.org> #1682: AddSourceDirectoryToHaikuImage doesn't work with spaces in file names ---------------------------+------------------------------------------------ Reporter: ekdahl | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by ekdahl): Sorry, forgot to test this. Will do ASAP. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 12 13:43:02 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 12 Mar 2008 12:43:02 -0000 Subject: [Haiku-bugs] [Haiku] #1758: Scrollbars not Proportional in Pe In-Reply-To: <043.6042b8202b9e43a69310f3c4d531c04a@haiku-os.org> References: <043.6042b8202b9e43a69310f3c4d531c04a@haiku-os.org> Message-ID: <052.d1d6111e7f2dfb2c544851eca8841e91@haiku-os.org> #1758: Scrollbars not Proportional in Pe ---------------------------------+------------------------------------------ Reporter: bonefish | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by bonefish): Assuming this is related: In Tracker scrolling by one page doesn't move the vertical scrollbar by its full handle size. E.g. open /boot/beos/bin, make the window big enough to have a scrollbar handle about twice the size of its minimum size, and scroll page-wise. The handle moves only about half its height. Terminal has a similar problem. E.g. in an empty standard-sized terminal window do a "seq 300" and then operate the vertical scrollbar. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 12 13:56:59 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 12 Mar 2008 12:56:59 -0000 Subject: [Haiku-bugs] [Haiku] #1913: Horizontal Scrolling in Pe Causes Vertical Scrolling to the Top Message-ID: <043.ffc1d588888090c48d7e2ef2c900a6c2@haiku-os.org> #1913: Horizontal Scrolling in Pe Causes Vertical Scrolling to the Top -----------------------+---------------------------------------------------- Reporter: bonefish | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- r24359, tested under VMware. Reproduce: - Open e.g. the Bootscript in Pe. - Make the window about half as wide (40 chars). - Scroll to the bottom of the document. - Position the caret in a line that doesn't fit the view. - Press End. The window will be scrolled to the top of the document again and to the right. The vertical scrollbar is topmost, the horizontal scrollbar leftmost. Pressing Home causes scrolling back (i.e. the caret becomes visible again), but the document is no longer scrolled fully to the bottom. Related may be #1625 or #1758. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 12 13:57:43 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 12 Mar 2008 12:57:43 -0000 Subject: [Haiku-bugs] [Haiku] #1758: Scrollbars not Proportional in Pe In-Reply-To: <043.6042b8202b9e43a69310f3c4d531c04a@haiku-os.org> References: <043.6042b8202b9e43a69310f3c4d531c04a@haiku-os.org> Message-ID: <052.afb5983903162eb055a9a4a5659ff6e5@haiku-os.org> #1758: Scrollbars not Proportional in Pe ---------------------------------+------------------------------------------ Reporter: bonefish | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by bonefish): Create R1/alpha1 ticket #1913, which might be related. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 12 13:58:12 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 12 Mar 2008 12:58:12 -0000 Subject: [Haiku-bugs] [Haiku] #1625: Scrolling slow --> alright, scrolling fast, changes vert to Horizontal In-Reply-To: <044.04dc774b4104ec39a25f56aced131f57@haiku-os.org> References: <044.04dc774b4104ec39a25f56aced131f57@haiku-os.org> Message-ID: <053.8d2e2894a06641581349d7e24d870cd0@haiku-os.org> #1625: Scrolling slow --> alright, scrolling fast, changes vert to Horizontal -----------------------------------+---------------------------------------- Reporter: hai_cu_be | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: Applications/Tracker | Version: R1 development Resolution: | Platform: All -----------------------------------+---------------------------------------- Changes (by bonefish): * milestone: R1 => R1/alpha1 Comment: Created R1/alpha1 ticket #1913, which might be related. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 12 15:03:15 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 12 Mar 2008 14:03:15 -0000 Subject: [Haiku-bugs] [Haiku] #1913: Horizontal Scrolling in Pe Causes Vertical Scrolling to the Top In-Reply-To: <043.ffc1d588888090c48d7e2ef2c900a6c2@haiku-os.org> References: <043.ffc1d588888090c48d7e2ef2c900a6c2@haiku-os.org> Message-ID: <052.9b62c86b486a3cfca5a28fcbb46dc549@haiku-os.org> #1913: Horizontal Scrolling in Pe Causes Vertical Scrolling to the Top ---------------------------------+------------------------------------------ Reporter: bonefish | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by axeld): * owner: axeld => stippi * component: - General => Kits/Interface Kit -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 12 15:39:29 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 12 Mar 2008 14:39:29 -0000 Subject: [Haiku-bugs] [Haiku] #1758: Scrollbars not Proportional in Pe In-Reply-To: <043.6042b8202b9e43a69310f3c4d531c04a@haiku-os.org> References: <043.6042b8202b9e43a69310f3c4d531c04a@haiku-os.org> Message-ID: <052.bd519390058097c9747b0ad44748a389@haiku-os.org> #1758: Scrollbars not Proportional in Pe ---------------------------------+------------------------------------------ Reporter: bonefish | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by axeld): * owner: axeld => stippi * milestone: R1 => R1/alpha1 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 12 15:47:19 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 12 Mar 2008 14:47:19 -0000 Subject: [Haiku-bugs] [Haiku] #1914: PANIC: vnode 5:45465 already exists (node = 0x90c1b300, vnode->node = 0x91053d80)! Message-ID: <040.572daffe104be83e982ae20fb33b51e3@haiku-os.org> #1914: PANIC: vnode 5:45465 already exists (node = 0x90c1b300, vnode->node = 0x91053d80)! ------------------------------+--------------------------------------------- Reporter: thorn | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Platform: x86 | ------------------------------+--------------------------------------------- and again, r24348 bfs: Insert:1301: Name in use Last message repeated 2 times. wait interval 524536, scan pages 4356, free 2046, target 2050 wait interval 524304, scan pages 4358, free 2045, target 2051 wait interval 524072, scan pages 4360, free 2044, target 2052 wait interval 524072, scan pages 4360, free 2044, target 2052 bfs: Insert:1301: Name in use PANIC: vnode 5:45465 already exists (node = 0x90c1b300, vnode->node = 0x91053d80)! Welcome to Kernel Debugging Land... Running on CPU 0 kdebug> bt stack trace for thread 298 "svn" kernel stack: 0x93af4000 to 0x93af8000 user stack: 0x7efe7000 to 0x7ffe7000 frame caller :function + offset 93af797c (+ 52) 80082db3 :invoke_debugger_command + 0x00cf 93af79b0 (+ 64) 80083b54 :_ParseCommand__16ExpressionParserRi + 0x01f8 93af79f0 (+ 48) 80083546 :EvaluateCommand__16ExpressionParserPCcRi + 0x01de 93af7a20 (+ 228) 80084c68 :evaluate_debug_command + 0x0088 93af7b04 (+ 64) 80081986 :kernel_debugger_loop__Fv + 0x017a 93af7b44 (+ 48) 800825d1 :kernel_debugger + 0x010d 93af7b74 (+ 192) 800824b9 :panic + 0x0029 93af7c34 (+ 64) 800486d6 :new_vnode + 0x005a 93af7c74 (+ 64) 802d6d72 :New__14InodeAllocatorP9block_runUiR9block_runPP5Inode + 0x014a 93af7cb4 (+ 176) 802dd3f1 :Create__5InodeR11TransactionP5InodePCcliUlPbPxPP5Inode + 0x0571 93af7d64 (+ 96) 802e78eb :bfs_create_dir__FPvT0PCciPx + 0x0107 93af7dc4 (+ 320) 8004ab0a :dir_create__FiPcib + 0x0082 93af7f04 (+ 64) 8004ff78 :_user_create_dir + 0x0094 93af7f44 (+ 100) 80092652 :pre_syscall_debug_done + 0x0002 (nearest) iframe at 0x93af7fa8 (end = 0x93af8000) eax 0x50 ebx 0x458bc8 ecx 0x7ffe6734 edx 0xffff0104 esi 0x0 edi 0x19754e08 ebp 0x7ffe6760 esp 0x93af7fdc eip 0xffff0104 eflags 0x206 vector: 0x63, error code: 0x0 93af7fa8 (+ 0) ffff0104 7ffe6760 (+ 48) 0032691f :unknown + 0xf91f 7ffe6790 (+ 144) 002c8516 :unknown + 0xd516 7ffe6820 (+ 64) 002c861b :unknown + 0xd61b 7ffe6860 (+ 64) 0024fd35 :unknown + 0x1ad35 7ffe68a0 (+ 48) 0024d45f :unknown + 0x1845f 7ffe68d0 (+ 176) 0024dd6d :unknown + 0x18d6d 7ffe6980 (+ 64) 002b4bc5 :unknown + 0x1bc5 7ffe69c0 (+ 96) 00299f78 :unknown + 0x7f78 7ffe6a20 (+ 112) 0029ab5a :unknown + 0x8b5a 7ffe6a90 (+ 80) 00299126 :unknown + 0x7126 7ffe6ae0 (+ 64) 00295466 :unknown + 0x3466 7ffe6b20 (+ 176) 0023a1dc :unknown + 0x51dc 7ffe6bd0 (+ 160) 00230426 :unknown + 0x18426 7ffe6c70 (+ 64) 002304f3 :unknown + 0x184f3 7ffe6cb0 (+ 80) 0020c9b1 :unknown + 0xc9b1 7ffe6d00 (+ 640) 002091fc :unknown + 0x91fc 7ffe6f80 (+ 44) 00204c45 :unknown + 0x4c45 7ffe6fac (+ 48) 001007ca 3453:runtime_loader_seg0ro at 0x00100000 + 0x7ca 7ffe6fdc (+ 0) 7ffe6fec 3452:svn_main_stack at 0x7efe7000 + 0xffffec kdebug> vnode 0x90c1b300 VNODE: 0x90c1b300 device: -858993460 id: 0 ref_count: 78233 private_node: 0x00000000 mount: 0x3bbe0ad9 covered_by: 0x00000001 cache: 0xffffffff flags: --- advisory_lock: 0x00000000 kdebug> kdebug> mount  s address id root covers cookie fs_name 0x908ade00 1 0x908ade40 0x00000000 0x90861980 rootfs 0x908ade80 2 0x908adf00 0x908adec0 0x908619c0 devfs 0x908adf40 3 0x908adfc0 0x908adf80 0x908c4a50 pipefs 0x908e2540 4 0x908e2600 0x908e2580 0x908f1000 bfs 0x90b17880 5 0x90b17940 0x90b178c0 0x909d0c00 bfs kdebug> mount 5 MOUNT: 0x90b17880 id: 5 device_name: /dev/disk/ata/0/slave/raw fs_name: bfs cookie: 0x909d0c00 root_vnode: 0x90b17940 covers_vnode: 0x90b178c0 partition: 0x908e9600 lock: 4807 flags: kdebug> -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 12 16:36:31 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 12 Mar 2008 15:36:31 -0000 Subject: [Haiku-bugs] [Haiku] #1911: PANIC: heap: huge allocation of 6292992 bytes asked! In-Reply-To: <040.1669ad96ac1dfccf47005827906732ce@haiku-os.org> References: <040.1669ad96ac1dfccf47005827906732ce@haiku-os.org> Message-ID: <049.3dcb4a021e04dfcb33ecf777d1f2fa71@haiku-os.org> #1911: PANIC: heap: huge allocation of 6292992 bytes asked! -------------------------------+-------------------------------------------- Reporter: thorn | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: File Systems/BFS | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Comment (by axeld): Okay, with that disk size, the block bitmap should be about 120K bytes large. Also, I was wrong with my original statement; BFS only allocates allocation group sized blocks, so probably 10K. Looks like your disk is seriously broken. Probably due to broken log entries. What exactly did you do with that disk before? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 12 17:16:11 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 12 Mar 2008 16:16:11 -0000 Subject: [Haiku-bugs] [Haiku] #1915: Open With does not display candidate apps in the correct order Message-ID: <042.6062ef52ee6ed9cb8435a05a8a836708@haiku-os.org> #1915: Open With does not display candidate apps in the correct order -----------------------+---------------------------------------------------- Reporter: ajsmale | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- In Tracker, navigate to the artwork folder and select one of the png files. Use File->Open With enter the Open With window. The order of the candidate applications is backwards, the preferred application (ShowImage) should be the first item, not the last. Clicking on the Relation attribute title puts the list into the correct order. Tested in VMWare r24361 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 12 18:04:27 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 12 Mar 2008 17:04:27 -0000 Subject: [Haiku-bugs] [Haiku] #1911: PANIC: heap: huge allocation of 6292992 bytes asked! In-Reply-To: <040.1669ad96ac1dfccf47005827906732ce@haiku-os.org> References: <040.1669ad96ac1dfccf47005827906732ce@haiku-os.org> Message-ID: <049.4db1099cd13c49257d77d65e219e435c@haiku-os.org> #1911: PANIC: heap: huge allocation of 6292992 bytes asked! -------------------------------+-------------------------------------------- Reporter: thorn | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: File Systems/BFS | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Comment (by thorn): heh, it's a virtual disk image (vmdk) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 12 19:32:45 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 12 Mar 2008 18:32:45 -0000 Subject: [Haiku-bugs] [Haiku] #1909: emuxki/midi related KDLs? In-Reply-To: <048.7c433231494081c4264c03b82f3ce97f@haiku-os.org> References: <048.7c433231494081c4264c03b82f3ce97f@haiku-os.org> Message-ID: <057.730fca8ccc961d3926ac58e61158da3b@haiku-os.org> #1909: emuxki/midi related KDLs? ----------------------------+----------------------------------------------- Reporter: jonas.kirilla | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by jonas.kirilla): The "invalid opcode exception" still happens in r24361. Will try a later revision ASAP. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 12 23:12:55 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 12 Mar 2008 22:12:55 -0000 Subject: [Haiku-bugs] [Haiku] #1898: getpeername returns size bigger than passed in? In-Reply-To: <038.caeeb8a1651bd335cee046c5c0969fa0@haiku-os.org> References: <038.caeeb8a1651bd335cee046c5c0969fa0@haiku-os.org> Message-ID: <047.25fbae4c893523fdcd9968469564c975@haiku-os.org> #1898: getpeername returns size bigger than passed in? ---------------------------------------+------------------------------------ Reporter: tqh | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Resolution: fixed | Platform: All ---------------------------------------+------------------------------------ Comment (by tqh): I think I'll change that check to see if is same as sockaddr (32) bytes, although I'll need to do that at runtime to support BeOS as well. I'll also need to increase PRNetAddr to 32 bytes to be as large as sockaddr in Haiku. Is there any other things I should be aware of in regards of sizeof sockaddr. Linux and others seems to have different sizes depending on family if I understand the check correctly, but I assume we only use 32 bytes. Anyway working fine with hardcoded check for 32 bytes. Posting with it now. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 12 23:15:38 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 12 Mar 2008 22:15:38 -0000 Subject: [Haiku-bugs] [Haiku] #1711: Haiku stops booting at allocate_commpage_entry(4, 34) In-Reply-To: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> References: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> Message-ID: <048.96788a5ca5f031808159834068f9cfa4@haiku-os.org> #1711: Haiku stops booting at allocate_commpage_entry(4, 34) ----------------------------+----------------------------------------------- Reporter: euan | Owner: korli Type: bug | Status: new Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by euan): BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 000000000009fc00 (usable) BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved) BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 000000009ffb0000 (usable) BIOS-e820: 000000009ffb0000 - 000000009ffbe000 (ACPI data) BIOS-e820: 000000009ffbe000 - 000000009ffe0000 (ACPI NVS) BIOS-e820: 000000009ffe0000 - 00000000a0000000 (reserved) BIOS-e820: 00000000ff780000 - 0000000100000000 (reserved) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 12 23:24:41 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 12 Mar 2008 22:24:41 -0000 Subject: [Haiku-bugs] [Haiku] #1898: getpeername returns size bigger than passed in? In-Reply-To: <038.caeeb8a1651bd335cee046c5c0969fa0@haiku-os.org> References: <038.caeeb8a1651bd335cee046c5c0969fa0@haiku-os.org> Message-ID: <047.4bf036a3fb4f6544c0eb4cfca7ae653f@haiku-os.org> #1898: getpeername returns size bigger than passed in? ---------------------------------------+------------------------------------ Reporter: tqh | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Resolution: fixed | Platform: All ---------------------------------------+------------------------------------ Comment (by axeld): I'm not sure why the size is that important. We actually have different sizes per family, too, it's just that we stayed compatible with BeOS with regards to sockaddr and sockaddr_in. For sockaddr_in6 and others, there is no need to stay compatible, though. We also have a sockaddr_storage which is 256 bytes in size. The last bytes in sockaddr_in are always padding, though, and can be neglected. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 12 23:30:38 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 12 Mar 2008 22:30:38 -0000 Subject: [Haiku-bugs] [Haiku] #1898: getpeername returns size bigger than passed in? In-Reply-To: <038.caeeb8a1651bd335cee046c5c0969fa0@haiku-os.org> References: <038.caeeb8a1651bd335cee046c5c0969fa0@haiku-os.org> Message-ID: <047.ebe0a6add5bee754f8bc9fe9472c7731@haiku-os.org> #1898: getpeername returns size bigger than passed in? ---------------------------------------+------------------------------------ Reporter: tqh | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Resolution: fixed | Platform: All ---------------------------------------+------------------------------------ Comment (by tqh): Mozilla does sanitychecks on the size, as we don't have anything to go on we should either not sanitycheck or check that the addrlen is the same as a sockaddr. Other platforms check that the returned value is the same as a socket for that family, but afaict Haiku returns 32 for inet at least, while other platforms thinks that it should be 16. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 13 04:08:53 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 13 Mar 2008 03:08:53 -0000 Subject: [Haiku-bugs] [Haiku] #1119: The boot screen doesn't have "some" kind of animation to indicate system activity or inactivity. In-Reply-To: <043.a44eb8fd7200ec9aa2b979ec647deb3b@haiku-os.org> References: <043.a44eb8fd7200ec9aa2b979ec647deb3b@haiku-os.org> Message-ID: <052.51e558c3a6ddc53d01dfc03d53df233d@haiku-os.org> #1119: The boot screen doesn't have "some" kind of animation to indicate system activity or inactivity. ---------------------------------+------------------------------------------ Reporter: kaoutsis | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Boot Loader | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by aljen): * cc: harakash at gmail.com (added) Comment: hey, i implemented r5 way of boot progress with icons indicating whats happening here's diff and tool to generate .raw files from .png which are used in loading/displaying splash logo&icons + sample .png's which i used to test splash data are loaded from boot_volume/home/config/settings/kernel/[splash|icons|palette].raw br, aljen -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 13 09:15:59 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 13 Mar 2008 08:15:59 -0000 Subject: [Haiku-bugs] [Haiku] #1909: emuxki/midi related KDLs? In-Reply-To: <048.7c433231494081c4264c03b82f3ce97f@haiku-os.org> References: <048.7c433231494081c4264c03b82f3ce97f@haiku-os.org> Message-ID: <057.daf4cebd599de12edf6bb14b0c5e75cf@haiku-os.org> #1909: emuxki/midi related KDLs? ----------------------------+----------------------------------------------- Reporter: jonas.kirilla | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by jonas.kirilla): It happens also with r24371. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 13 10:31:20 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 13 Mar 2008 09:31:20 -0000 Subject: [Haiku-bugs] [Haiku] #1119: The boot screen doesn't have "some" kind of animation to indicate system activity or inactivity. In-Reply-To: <043.a44eb8fd7200ec9aa2b979ec647deb3b@haiku-os.org> References: <043.a44eb8fd7200ec9aa2b979ec647deb3b@haiku-os.org> Message-ID: <052.3d11751eb39324395f52a9ae3d358502@haiku-os.org> #1119: The boot screen doesn't have "some" kind of animation to indicate system activity or inactivity. ---------------------------------+------------------------------------------ Reporter: kaoutsis | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System/Boot Loader | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by axeld): * type: bug => enhancement Comment: Thanks! While I'm not sure Haiku needs such an indication, there are a the following problems with your way of doing it: 1) The boot loader only runs for a very short time; to make this thing useful, the kernel or even the Bootscript would actually need to update those icons. 2) We do have a coding style that you don't follow at all; when in doubt, always follow the style in the file you're changing (else, see http://www .haiku-os.org/documents/dev/haiku_coding_guidelines) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 13 10:58:41 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 13 Mar 2008 09:58:41 -0000 Subject: [Haiku-bugs] [Haiku] #1119: The boot screen doesn't have "some" kind of animation to indicate system activity or inactivity. In-Reply-To: <043.a44eb8fd7200ec9aa2b979ec647deb3b@haiku-os.org> References: <043.a44eb8fd7200ec9aa2b979ec647deb3b@haiku-os.org> Message-ID: <052.5e1916c7cae06ce69b4415afb576ac37@haiku-os.org> #1119: The boot screen doesn't have "some" kind of animation to indicate system activity or inactivity. ---------------------------------+------------------------------------------ Reporter: kaoutsis | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System/Boot Loader | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by meanwhile): Can you achieve the same richness in colour that the Desktop icons have? Even if that can be done, I think it gives away too much of the 'icon- splendour' that's best introduced in its working context (i.e. on the -loading- Desktop) instead of already on the boot screen. If booting goes so fast, why not design a non-boring version of a progressbar, for example simply through attractive use of colour? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 13 12:22:58 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 13 Mar 2008 11:22:58 -0000 Subject: [Haiku-bugs] [Haiku] #1119: The boot screen doesn't have "some" kind of animation to indicate system activity or inactivity. In-Reply-To: <043.a44eb8fd7200ec9aa2b979ec647deb3b@haiku-os.org> References: <043.a44eb8fd7200ec9aa2b979ec647deb3b@haiku-os.org> Message-ID: <052.39c85523ce281b8c212215c4a77653a1@haiku-os.org> #1119: The boot screen doesn't have "some" kind of animation to indicate system activity or inactivity. ---------------------------------+------------------------------------------ Reporter: kaoutsis | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System/Boot Loader | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by jackburton): Replying to [comment:2 axeld]: > Thanks! While I'm not sure Haiku needs such an indication, I think it would be useful and nice. Although the regular boot process is fast enough, cd-booting is not, and having some kind of visual indication that the process isn't hanged is definitely useful. Moreover, this way one can tell where the booting process hanged, in case of problems. And anyway, it's definitely nicer than an "empty" black screen, even with the logo :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 13 12:37:36 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 13 Mar 2008 11:37:36 -0000 Subject: [Haiku-bugs] [Haiku] #1882: "Subscribe to Haiku Daily RSS feed" in Download page is broken In-Reply-To: <039.ae72c19fa6bc693a5696828bb215f31d@haiku-os.org> References: <039.ae72c19fa6bc693a5696828bb215f31d@haiku-os.org> Message-ID: <048.190b9a24fa14e86b752f68aedad5e02a@haiku-os.org> #1882: "Subscribe to Haiku Daily RSS feed" in Download page is broken --------------------------+------------------------------------------------- Reporter: koki | Owner: haiku-web Type: bug | Status: new Priority: normal | Milestone: R1 Component: Website/CMS | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by nielx): Works. Thanks! It might be a good idea to have the build factory generate a feed automatically, but that's for later concerns. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 13 12:37:48 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 13 Mar 2008 11:37:48 -0000 Subject: [Haiku-bugs] [Haiku] #1882: "Subscribe to Haiku Daily RSS feed" in Download page is broken In-Reply-To: <039.ae72c19fa6bc693a5696828bb215f31d@haiku-os.org> References: <039.ae72c19fa6bc693a5696828bb215f31d@haiku-os.org> Message-ID: <048.5e559759938b25418278a11c63d9c19a@haiku-os.org> #1882: "Subscribe to Haiku Daily RSS feed" in Download page is broken --------------------------+------------------------------------------------- Reporter: koki | Owner: haiku-web Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Website/CMS | Version: R1 development Resolution: fixed | Platform: All --------------------------+------------------------------------------------- Changes (by nielx): * status: new => closed * resolution: => fixed -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 13 13:36:31 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 13 Mar 2008 12:36:31 -0000 Subject: [Haiku-bugs] [Haiku] #1119: The boot screen doesn't have "some" kind of animation to indicate system activity or inactivity. In-Reply-To: <043.a44eb8fd7200ec9aa2b979ec647deb3b@haiku-os.org> References: <043.a44eb8fd7200ec9aa2b979ec647deb3b@haiku-os.org> Message-ID: <052.77ed41079b61ddbcc6d4ba9b3b77ef2c@haiku-os.org> #1119: The boot screen doesn't have "some" kind of animation to indicate system activity or inactivity. ----------------------------+----------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Changes (by axeld): * component: System/Boot Loader => System/Kernel Comment: Indeed, I didn't think of the CD boot; there, a progress bar of some kind would definitely be nice (something unobtrusive). In any way, it has to be the kernel, not the boot loader that is responsible for that. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 13 18:29:26 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 13 Mar 2008 17:29:26 -0000 Subject: [Haiku-bugs] [Haiku] #1119: The boot screen doesn't have "some" kind of animation to indicate system activity or inactivity. In-Reply-To: <043.a44eb8fd7200ec9aa2b979ec647deb3b@haiku-os.org> References: <043.a44eb8fd7200ec9aa2b979ec647deb3b@haiku-os.org> Message-ID: <052.34e644154d07b4b4041802f7ff51c570@haiku-os.org> #1119: The boot screen doesn't have "some" kind of animation to indicate system activity or inactivity. ----------------------------+----------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by aljen): ok i will follow haiku coding style in the future :) ahh sorry my mistake it was my first attempt in haiku boot/kernel development ;/ i could try to reimplement it into kernel, but i will need some guidelines how it should look and who i can ask if i get in trouble understaning the kernel code :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 13 19:30:23 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 13 Mar 2008 18:30:23 -0000 Subject: [Haiku-bugs] [Haiku] #1916: [Bluetooth] Provide RSSI for discovered Bluetooth device Message-ID: <043.4613a06c6f0b9771bf5599f12e42bfc2@haiku-os.org> #1916: [Bluetooth] Provide RSSI for discovered Bluetooth device -------------------------+-------------------------------------------------- Reporter: andreasf | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Kits | Version: R1 development Platform: All | -------------------------+-------------------------------------------------- In {{{DeviceListener::DeviceDiscovered}}}, please add support for retrieving the Received Signal Strength Indicator (RSSI), delivered by {{{INQUIRY_RESULT_WITH_RSSI}}} and newer HCI events. BlueZ' D-Bus callback interface always provides it as argument and sets it to some invalid value for the legacy {{{INQUIRY_RESULT}}}. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 13 19:43:43 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 13 Mar 2008 18:43:43 -0000 Subject: [Haiku-bugs] [Haiku] #1916: [Bluetooth] Provide RSSI for discovered Bluetooth device In-Reply-To: <043.4613a06c6f0b9771bf5599f12e42bfc2@haiku-os.org> References: <043.4613a06c6f0b9771bf5599f12e42bfc2@haiku-os.org> Message-ID: <052.6d5c230621b6ef39decbd7588fed2bab@haiku-os.org> #1916: [Bluetooth] Provide RSSI for discovered Bluetooth device --------------------------+------------------------------------------------- Reporter: andreasf | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Kits | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by andreasf): Sorry, in {{{DiscoveryListener}}} obviously. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 13 21:36:47 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 13 Mar 2008 20:36:47 -0000 Subject: [Haiku-bugs] [Haiku] #158: [Tracker] doesn't show up/down arrows In-Reply-To: <040.78b5899b0625066bee7362ca04368640@haiku-os.org> References: <040.78b5899b0625066bee7362ca04368640@haiku-os.org> Message-ID: <049.b037ed0a3c1c8229fb560abdec47db4c@haiku-os.org> #158: [Tracker] doesn't show up/down arrows ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Servers/app_server | Version: Resolution: fixed | Platform: All ---------------------------------+------------------------------------------ Changes (by jackburton): * status: new => closed * resolution: => fixed Comment: This has been working for some time. Although if the selected font is missing this glyphs, they won't show up. IOW: We still need a fallback in BMenuItem :) Let's close this, anyway. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 13 21:39:03 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 13 Mar 2008 20:39:03 -0000 Subject: [Haiku-bugs] [Haiku] #572: [Vision] crashes wrt ListView In-Reply-To: <049.8203cecefd77c50969e82377a36f53bf@haiku-os.org> References: <049.8203cecefd77c50969e82377a36f53bf@haiku-os.org> Message-ID: <058.bda3078defdaf83f65d4344415c7c27e@haiku-os.org> #572: [Vision] crashes wrt ListView -----------------------------+---------------------------------------------- Reporter: johndrinkwater | Owner: anevilyak Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: Resolution: | Platform: All -----------------------------+---------------------------------------------- Changes (by jackburton): * owner: axeld => anevilyak * platform: => All Old description: > After changing channels/servers a few times, Vision crashed with : > > [Switching to team ./Vision (244) thread w>Freenode - [calvino.freenode. > (272)] > 0x003ebd9a in BListItem::IsSelected () from > /boot/beos/system/lib/libbe.so > (gdb) bt > #0 0x003ebd9a in BListItem::IsSelected () from > /boot/beos/system/lib/libbe.so > #1 0x003efc7a in BListView::_CalcLastSelected () > from /boot/beos/system/lib/libbe.so > #2 0x003efa45 in BListView::_DeselectAll () > from /boot/beos/system/lib/libbe.so > #3 0x003ef381 in BListView::_Select () from > /boot/beos/system/lib/libbe.so > #4 0x003ee3f0 in BListView::Select () from > /boot/beos/system/lib/libbe.so > #5 0x002e4c9c in WindowList::MouseDown () > #6 0x0042d85f in BWindow::DispatchMessage () > from /boot/beos/system/lib/libbe.so > #7 0x00431054 in BWindow::task_looper () from > /boot/beos/system/lib/libbe.so > #8 0x003b3edb in BLooper::_task0_ () from /boot/beos/system/lib/libbe.so > #9 0x0081fa10 in thread_entry () from /boot/beos/system/lib/libroot.so > #10 0x700c1fec in ?? () > (gdb) New description: After changing channels/servers a few times, Vision crashed with : [Switching to team ./Vision (244) thread w>Freenode - [calvino.freenode. (272)] 0x003ebd9a in BListItem::IsSelected () from /boot/beos/system/lib/libbe.so (gdb) bt #0 0x003ebd9a in BListItem::IsSelected () from /boot/beos/system/lib/libbe.so #1 0x003efc7a in BListView::_CalcLastSelected () from /boot/beos/system/lib/libbe.so #2 0x003efa45 in BListView::_DeselectAll () from /boot/beos/system/lib/libbe.so #3 0x003ef381 in BListView::_Select () from /boot/beos/system/lib/libbe.so #4 0x003ee3f0 in BListView::Select () from /boot/beos/system/lib/libbe.so #5 0x002e4c9c in WindowList::MouseDown () #6 0x0042d85f in BWindow::DispatchMessage () from /boot/beos/system/lib/libbe.so #7 0x00431054 in BWindow::task_looper () from /boot/beos/system/lib/libbe.so #8 0x003b3edb in BLooper::_task0_ () from /boot/beos/system/lib/libbe.so #9 0x0081fa10 in thread_entry () from /boot/beos/system/lib/libroot.so #10 0x700c1fec in ?? () (gdb) Comment: Let's see what anevilyak says about this one... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 13 21:47:07 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 13 Mar 2008 20:47:07 -0000 Subject: [Haiku-bugs] [Haiku] #1763: [Cortex] System Clock element have black icon In-Reply-To: <040.f9e6f8eafa7490c9c239c6b00cdb0dfb@haiku-os.org> References: <040.f9e6f8eafa7490c9c239c6b00cdb0dfb@haiku-os.org> Message-ID: <049.837a0da6c014afc002749e55659f596a@haiku-os.org> #1763: [Cortex] System Clock element have black icon ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: fixed | Platform: All ---------------------------------+------------------------------------------ Changes (by jackburton): * status: new => closed * resolution: => fixed Comment: Fixed in r24205. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 13 21:57:05 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 13 Mar 2008 20:57:05 -0000 Subject: [Haiku-bugs] [Haiku] #1792: E-mail preference applet needs a vector icon In-Reply-To: <039.b7445df82775ed20860fbb85515c08e3@haiku-os.org> References: <039.b7445df82775ed20860fbb85515c08e3@haiku-os.org> Message-ID: <048.165ccaf8f6fbae48a90ca65984bb61e3@haiku-os.org> #1792: E-mail preference applet needs a vector icon -----------------------------+---------------------------------------------- Reporter: koki | Owner: stippi Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: fixed | Platform: All -----------------------------+---------------------------------------------- Changes (by jackburton): * status: new => closed * resolution: => fixed Comment: Email has an icon since r24246 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 13 22:41:30 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 13 Mar 2008 21:41:30 -0000 Subject: [Haiku-bugs] [Haiku] #572: [Vision] crashes wrt ListView In-Reply-To: <049.8203cecefd77c50969e82377a36f53bf@haiku-os.org> References: <049.8203cecefd77c50969e82377a36f53bf@haiku-os.org> Message-ID: <058.5b556ccfdf40ee63674baffae5af23ef@haiku-os.org> #572: [Vision] crashes wrt ListView -----------------------------+---------------------------------------------- Reporter: johndrinkwater | Owner: anevilyak Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: - General | Version: Resolution: | Platform: All -----------------------------+---------------------------------------------- Changes (by anevilyak): * status: new => assigned Comment: A little more information please...did you add/remove any channels or collapse any servers? Or are you just clicking back and forth between the server and a channel? At first glance it looks like it's possibly a bug somewhere in the binary searching stuff but need a bit more information to try and replicate it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 14 00:32:33 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 13 Mar 2008 23:32:33 -0000 Subject: [Haiku-bugs] [Haiku] #347: Imposible to boot from CD In-Reply-To: <054.b7543cd2da05e105ad49b5d2c2877e4d@haiku-os.org> References: <054.b7543cd2da05e105ad49b5d2c2877e4d@haiku-os.org> Message-ID: <063.1248565f62c9b3bb271eae056e13f165@haiku-os.org> #347: Imposible to boot from CD ----------------------------------+----------------------------------------- Reporter: daneel at rootshell.be | Owner: axeld Type: bug | Status: reopened Priority: high | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------------+----------------------------------------- Comment (by thenerd): I get this same error on real hardware (Dell Latitude) with an encrypted hard disk. I used TrueCrypt to encrypt the whole system drive and Haiku won't boot. It shows the same "Could not mount boot device" error message. Not sure if that helps but it's another scenario. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 14 00:42:20 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 13 Mar 2008 23:42:20 -0000 Subject: [Haiku-bugs] [Haiku] #1917: vm_cache_remove_consumer() Deadlock Message-ID: <043.cbbdd01e8560ed6dee2cd0f7ba684945@haiku-os.org> #1917: vm_cache_remove_consumer() Deadlock ---------------------------+------------------------------------------------ Reporter: bonefish | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Platform: All | ---------------------------+------------------------------------------------ r24356 vm_cache_remove_consumer() calls release_ref() on the store while the cache is locked. For vnode stores this will call vfs_put_vnode(), which in turn might call the underlying FS's remove_vnode() hook (if the file has been removed). BFS' hook calls file_cache_set_size() which attempts to lock the cache a second time. Possible solutions: - Make vm_cache::lock a recursive lock. This will solve this problem, but the locking order will still be problematic, i.e. calling the VFS (and thus the respective FS) while holding the cache lock. The usual locking order is reverse. - Move release_ref() in vm_cache_remove_consumer() before locking the cache. That sounds promising, but I don't see all the consequences yet. The page writer doesn't hold the cache lock either when releasing the store ref. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 14 01:58:00 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 14 Mar 2008 00:58:00 -0000 Subject: [Haiku-bugs] [Haiku] #572: [Vision] crashes wrt ListView In-Reply-To: <049.8203cecefd77c50969e82377a36f53bf@haiku-os.org> References: <049.8203cecefd77c50969e82377a36f53bf@haiku-os.org> Message-ID: <058.05737291689e9d60a0968c028b5944b1@haiku-os.org> #572: [Vision] crashes wrt ListView -----------------------------+---------------------------------------------- Reporter: johndrinkwater | Owner: anevilyak Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: - General | Version: Resolution: | Platform: All -----------------------------+---------------------------------------------- Comment (by anevilyak): Oops, wait. I just realized this wasn't a newly filed bug, that may well be an issue that's fixed by some of the rewrites I did, since I did catch a few crash bugs that I've since patched. Can you still replicate this problem? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 14 04:25:23 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 14 Mar 2008 03:25:23 -0000 Subject: [Haiku-bugs] [Haiku] #1743: Ftp aborts download if terminal window is resized. In-Reply-To: <042.048efdec999945050463d6e1bf9b4f82@haiku-os.org> References: <042.048efdec999945050463d6e1bf9b4f82@haiku-os.org> Message-ID: <051.b301f45746c1e8d6dff5afb931edee1c@haiku-os.org> #1743: Ftp aborts download if terminal window is resized. ------------------------+--------------------------------------------------- Reporter: bouncer | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Platform: All ------------------------+--------------------------------------------------- Changes (by bonefish): * status: assigned => closed * resolution: => fixed Comment: Considered fixed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 14 04:28:53 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 14 Mar 2008 03:28:53 -0000 Subject: [Haiku-bugs] [Haiku] #1918: Terminal Deadlock When TTY Buffer Full In-Reply-To: <043.655f40b7e12dc80914c04ebdcf2ed1cd@haiku-os.org> References: <043.655f40b7e12dc80914c04ebdcf2ed1cd@haiku-os.org> Message-ID: <052.a366d3787ed6048e84c3ea226fc1c30b@haiku-os.org> #1918: Terminal Deadlock When TTY Buffer Full ------------------------------------+--------------------------------------- Reporter: bonefish | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Resolution: | Platform: All ------------------------------------+--------------------------------------- Comment (by bonefish): Just verified the way to reproduce the bug: "seq 100000" + hammering on the keyboard seems to be reliable. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 14 04:23:08 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 14 Mar 2008 03:23:08 -0000 Subject: [Haiku-bugs] [Haiku] #1918: Terminal Deadlock When TTY Buffer Full Message-ID: <043.655f40b7e12dc80914c04ebdcf2ed1cd@haiku-os.org> #1918: Terminal Deadlock When TTY Buffer Full -----------------------------------+---------------------------------------- Reporter: bonefish | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Platform: All | -----------------------------------+---------------------------------------- r24356 The Terminal can deadlock when the tty buffer runs full. Attached is a KDL session analyzing the situation. In short: - Window thread: Is in Shell::Write() writing to the TTY, blocking because the TTY buffer is full. - PtyReader thread: Is in TermParse::PtyReader(), blocking on fReaderLocker. - EscParse thread: Is in TermView::_Redraw(), blocking trying to lock the window. May or may not be related to #1755. I can't unblock the Terminal by resizing/zooming the window, though, so it probably isn't. Regarding how to reproduce it: I have seen this only once yet. I suppose it helps to have a command line program that prints a lot and type something at the same time. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 14 08:42:06 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 14 Mar 2008 07:42:06 -0000 Subject: [Haiku-bugs] [Haiku] #572: [Vision] crashes wrt ListView In-Reply-To: <049.8203cecefd77c50969e82377a36f53bf@haiku-os.org> References: <049.8203cecefd77c50969e82377a36f53bf@haiku-os.org> Message-ID: <058.6d6b4468956820698e5b6ef4ad0ee2d3@haiku-os.org> #572: [Vision] crashes wrt ListView -----------------------------+---------------------------------------------- Reporter: johndrinkwater | Owner: anevilyak Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: - General | Version: Resolution: | Platform: All -----------------------------+---------------------------------------------- Comment (by jackburton): Replying to [comment:3 anevilyak]: > Oops, wait. I just realized this wasn't a newly filed bug, that may well be an issue that's fixed by some of the rewrites I did, since I did catch a few crash bugs that I've since patched. Yeah, that's why I reassigned this to you. > Can you still replicate this problem? Only johndrinkwater would know. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 14 11:50:57 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 14 Mar 2008 10:50:57 -0000 Subject: [Haiku-bugs] [Haiku] #1919: Cursor hangs on startup Message-ID: <044.216253a81a35f1fd229dcbb677851cfa@haiku-os.org> #1919: Cursor hangs on startup -----------------------+---------------------------------------------------- Reporter: meanwhile | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- On startup, Haiku rev. #24385 has a frozen cursor on a blue desktop with nothing on it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 14 16:13:03 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 14 Mar 2008 15:13:03 -0000 Subject: [Haiku-bugs] [Haiku] #572: [Vision] crashes wrt ListView In-Reply-To: <049.8203cecefd77c50969e82377a36f53bf@haiku-os.org> References: <049.8203cecefd77c50969e82377a36f53bf@haiku-os.org> Message-ID: <058.9ed8a17dadcadcda73fad067cc6cd28b@haiku-os.org> #572: [Vision] crashes wrt ListView -----------------------------+---------------------------------------------- Reporter: johndrinkwater | Owner: anevilyak Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: - General | Version: Resolution: | Platform: All -----------------------------+---------------------------------------------- Comment (by anevilyak): Replying to [comment:4 jackburton]: > Only johndrinkwater would know. I'm hoping he answers indeed...the main crash I remember fixing had to do with add/removing stuff to the view, since it was possible to trip a bug in BListView's quicksort implementation that would cause it to run off the end of the array. That may have affected other things, but I wouldn't have expected selecting items to be one of them, and haven't seen that crash myself. But who knows what the listview code looked like 2 years ago :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 14 17:38:13 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 14 Mar 2008 16:38:13 -0000 Subject: [Haiku-bugs] [Haiku] #1711: Haiku stops booting at allocate_commpage_entry(4, 34) In-Reply-To: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> References: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> Message-ID: <048.abe9e5a4a79f0cb0da864bd1d752d851@haiku-os.org> #1711: Haiku stops booting at allocate_commpage_entry(4, 34) ----------------------------+----------------------------------------------- Reporter: euan | Owner: korli Type: bug | Status: new Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by ddew): I also have that issue with 5GB RAM. Posting my MTRR and RAM map: {{{ Mar 14 17:17:53 workstation kernel: [ 0.000000] BIOS-provided physical RAM map: Mar 14 17:17:53 workstation kernel: [ 0.000000] BIOS-e820: 0000000000000000 - 000000000009e800 (usable) Mar 14 17:17:53 workstation kernel: [ 0.000000] BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved) Mar 14 17:17:53 workstation kernel: [ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) Mar 14 17:17:53 workstation kernel: [ 0.000000] BIOS-e820: 0000000000100000 - 00000000dfee0000 (usable) Mar 14 17:17:53 workstation kernel: [ 0.000000] BIOS-e820: 00000000dfee0000 - 00000000dfee3000 (ACPI NVS) Mar 14 17:17:53 workstation kernel: [ 0.000000] BIOS-e820: 00000000dfee3000 - 00000000dfef0000 (ACPI data) Mar 14 17:17:53 workstation kernel: [ 0.000000] BIOS-e820: 00000000dfef0000 - 00000000dff00000 (reserved) Mar 14 17:17:53 workstation kernel: [ 0.000000] BIOS-e820: 00000000f0000000 - 00000000f4000000 (reserved) Mar 14 17:17:53 workstation kernel: [ 0.000000] BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved) Mar 14 17:17:53 workstation kernel: [ 0.000000] BIOS-e820: 0000000100000000 - 0000000160000000 (usable) }}} {{{ reg00: base=0x00000000 ( 0MB), size=4096MB: write-back, count=1 reg01: base=0xe0000000 (3584MB), size= 512MB: uncachable, count=1 reg02: base=0x100000000 (4096MB), size=2048MB: write-back, count=1 reg03: base=0x160000000 (5632MB), size= 512MB: uncachable, count=1 reg04: base=0xdff00000 (3583MB), size= 1MB: uncachable, count=1 }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 14 19:31:56 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 14 Mar 2008 18:31:56 -0000 Subject: [Haiku-bugs] [Haiku] #1920: Userland Heap Garbage in Kernel Heap Page Message-ID: <043.587b706d72315bf206a07bb81bdbffef@haiku-os.org> #1920: Userland Heap Garbage in Kernel Heap Page ---------------------------+------------------------------------------------ Reporter: bonefish | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Platform: All | ---------------------------+------------------------------------------------ r24356, VMware Cf. attached KDL session. Kernel page fault occurred while running the perl test suite. As can be seen in the attachment, there's a complete page of garbage in the entry array of a hash table. The contents looks like it stems from the heap of one of the perl tests (t/TEST or one of its children). The corresponding page looks good though -- it's in the right cache and has no bogus area mappings. My suspicion would be that e.g. on an exec() a userland heap page has been freed, but not correctly unmapped, so that writes to that virtual address (likely the heap of the exec()ed program) would not cause a page fault and continue to modify that page. At some point the kernel heap would reuse the page and hand out an chunk of memory backed by it. Subsequent writes to the userland heap would then overwrite the contents of this allocation. Needless to say that I've looked through the involved code and didn't spot a problem. There's still a TODO regarding removing page mappings in delete_cache(), but that looks obsolete to me (mappings and wired_count of the page have been checked a few lines before). There's another TODO in vm_soft_fault() talking about the possibility of mapping a page twice, but that seems unrelated. I saved the virtual machine state, so if there're any hints what more to examine, I can do that. Might be related to #1900. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 15 00:15:26 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 14 Mar 2008 23:15:26 -0000 Subject: [Haiku-bugs] [Haiku] #1920: Userland Heap Garbage in Kernel Heap Page In-Reply-To: <043.587b706d72315bf206a07bb81bdbffef@haiku-os.org> References: <043.587b706d72315bf206a07bb81bdbffef@haiku-os.org> Message-ID: <052.b86e42567d98ec9e627cb1ec66a3db15@haiku-os.org> #1920: Userland Heap Garbage in Kernel Heap Page ----------------------------+----------------------------------------------- Reporter: bonefish | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by axeld): I haven't found much time to look into this, but this looks like environment variables. And those aren't only part of userland apps, but also copied inside the kernel when a new app launches (see team.cpp create_team_arg()). Since parts of this page are filled with 0xcccccccc, it might have been handed out by the kernel allocator, not the userland allocator (only the former fills it with 0xcc). And since we found it in the middle of a hashtable allocation, and it's still filled with 0xcc, I'd say the kernel allocator has given this page away twice. It's just the question if it has been mapped twice (as you assumed), or if there is a bug in the heap implementation. Note also that the cache uses hash_insert_grow() which means the memory of the hash table might change over time. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 15 01:23:31 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 15 Mar 2008 00:23:31 -0000 Subject: [Haiku-bugs] [Haiku] #1920: Userland Heap Garbage in Kernel Heap Page In-Reply-To: <043.587b706d72315bf206a07bb81bdbffef@haiku-os.org> References: <043.587b706d72315bf206a07bb81bdbffef@haiku-os.org> Message-ID: <052.798a550497e921c14845217dbe0c5391@haiku-os.org> #1920: Userland Heap Garbage in Kernel Heap Page ----------------------------+----------------------------------------------- Reporter: bonefish | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Changes (by bonefish): * cc: mmlr (added) Comment: Replying to [comment:1 axeld]: > I haven't found much time to look into this, but this looks like environment variables. And those aren't only part of userland apps, but also copied inside the kernel when a new app launches (see team.cpp create_team_arg()). Yep, those definitely are environment variables, but this isn't an intact array. Different variables have been written on top of each other. The longest is BEINCLUDES, on top of it is probably PATH, on top of it something containing the perl test directory path, then some empty variable, on top of that "PERL_DESTRUCT_LEVEL=2" and on top of that "EMXSHELL=sh". The latter two are definitely set only by t/TEST (in that order). That's why I was more thinking of some kind of buffer that perl uses internally. > Since parts of this page are filled with 0xcccccccc, it might have been handed out by the kernel allocator, not the userland allocator (only the former fills it with 0xcc). Good point! I thought the userland allocator did that too. > And since we found it in the middle of a hashtable allocation, and it's still filled with 0xcc, I'd say the kernel allocator has given this page away twice. It's just the question if it has been mapped twice (as you assumed), or if there is a bug in the heap implementation. I'm having the suspicion that the page wasn't mapped twice after all, but that the kernel allocator did indeed hand out the chunk of memory more than once. It probably even kept doing that. That would perfectly explain that memory contents: First the hash table gets the chunk, clears it and repopulates the table. Later another large allocation gets the same chunk and causes the table to be 0xcc'd again. Later an environment array is copied from userland during an exec() call, each string being copied over the previous one. > Note also that the cache uses hash_insert_grow() which means the memory of the hash table might change over time. Yep, I noticed that. The hash table already contains 2622 entries, though, so the last rehashing was already almost 400 entries ago. Since the table contains complete garbage only, I'd suspect that the trouble started only recently, maybe with the ongoing exec(). I guess it doesn't harm to review the allocator code... and add Michael to the CC. :-) Pity that I didn't have the allocator tracing enabled. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 15 10:40:56 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 15 Mar 2008 09:40:56 -0000 Subject: [Haiku-bugs] [Haiku] #1920: Userland Heap Garbage in Kernel Heap Page In-Reply-To: <043.587b706d72315bf206a07bb81bdbffef@haiku-os.org> References: <043.587b706d72315bf206a07bb81bdbffef@haiku-os.org> Message-ID: <052.6a18d3eb2567f7c9516e7e090451b791@haiku-os.org> #1920: Userland Heap Garbage in Kernel Heap Page ----------------------------+----------------------------------------------- Reporter: bonefish | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by axeld): Replying to [comment:2 bonefish]: > I'm having the suspicion that the page wasn't mapped twice after all, but that the kernel allocator did indeed hand out the chunk of memory more than once. It probably even kept doing that. That would perfectly explain that memory contents: First the hash table gets the chunk, clears it and repopulates the table. Later another large allocation gets the same chunk and causes the table to be 0xcc'd again. Later an environment array is copied from userland during an exec() call, each string being copied over the previous one. Not sure if that really fits so well: if the allocator would have done that, it would have overwritten the memory with 0xcc again. Another possibility would be that the page was copied into that region. > Yep, I noticed that. The hash table already contains 2622 entries, though, so the last rehashing was already almost 400 entries ago. Since the table contains complete garbage only, I'd suspect that the trouble started only recently, maybe with the ongoing exec(). Have you had a look at the pages around that one? Maybe it's not the only one with such contents? > I guess it doesn't harm to review the allocator code... and add Michael to the CC. :-) Pity that I didn't have the allocator tracing enabled. Indeed :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 15 10:42:29 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 15 Mar 2008 09:42:29 -0000 Subject: [Haiku-bugs] [Haiku] #1917: vm_cache_remove_consumer() Deadlock In-Reply-To: <043.cbbdd01e8560ed6dee2cd0f7ba684945@haiku-os.org> References: <043.cbbdd01e8560ed6dee2cd0f7ba684945@haiku-os.org> Message-ID: <052.0fe87eb04e5d75c9626003a1023c7c10@haiku-os.org> #1917: vm_cache_remove_consumer() Deadlock ----------------------------+----------------------------------------------- Reporter: bonefish | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by axeld): It should always be sure to release the ref without holding the lock I suppose, but we might want to have a closer look again before choosing that option :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 15 12:27:48 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 15 Mar 2008 11:27:48 -0000 Subject: [Haiku-bugs] [Haiku] #1915: Open With does not display candidate apps in the correct order In-Reply-To: <042.6062ef52ee6ed9cb8435a05a8a836708@haiku-os.org> References: <042.6062ef52ee6ed9cb8435a05a8a836708@haiku-os.org> Message-ID: <051.48d70082a825ad82bfcb7c54decc9de5@haiku-os.org> #1915: Open With does not display candidate apps in the correct order -----------------------------------+---------------------------------------- Reporter: ajsmale | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: | Platform: All -----------------------------------+---------------------------------------- Changes (by axeld): * component: - General => Applications/Tracker Comment: r22113 not only fixed a bug in the comparison functions, it accidently also reverted the sorting order. I'll have a look. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 15 13:40:19 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 15 Mar 2008 12:40:19 -0000 Subject: [Haiku-bugs] [Haiku] #1920: Userland Heap Garbage in Kernel Heap Page In-Reply-To: <043.587b706d72315bf206a07bb81bdbffef@haiku-os.org> References: <043.587b706d72315bf206a07bb81bdbffef@haiku-os.org> Message-ID: <052.de0198ce9205988dcb599dd09ca59f1d@haiku-os.org> #1920: Userland Heap Garbage in Kernel Heap Page ----------------------------+----------------------------------------------- Reporter: bonefish | Owner: bonefish Type: bug | Status: assigned Priority: blocker | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Changes (by bonefish): * owner: axeld => bonefish * status: new => assigned Comment: Replying to [comment:3 axeld]: > Replying to [comment:2 bonefish]: > > I'm having the suspicion that the page wasn't mapped twice after all, but that the kernel allocator did indeed hand out the chunk of memory more than once. It probably even kept doing that. That would perfectly explain that memory contents: First the hash table gets the chunk, clears it and repopulates the table. Later another large allocation gets the same chunk and causes the table to be 0xcc'd again. Later an environment array is copied from userland during an exec() call, each string being copied over the previous one. > > Not sure if that really fits so well: if the allocator would have done that, it would have overwritten the memory with 0xcc again. > Another possibility would be that the page was copied into that region. Sure, I wouldn't rule that out. BTW it's very interesting to have a look at user_copy_strings_array() (team.cpp). It malloc()s a temporary buffer for the environment strings it copies from userland, which would result in exactly the memory pattern seen on that page. Even more interestingly the buffer size is 4 * B_PAGE_SIZE, while the size allocated for the hash table array is 4 * 4093. Both are "large" allocations, i.e. greater than the maximal allocator bin size. I've reviewed the large allocation code and it looks good, save for the allocation ID stuff. heap_next_alloc_id() gives out IDs limited to interval [0, 511]. So, if enough large allocations are made, it is possible that two allocations with the same ID are assigned adjacent page ranges. If the first one is freed, the pages of the second one are freed as well and will thus be reused although still being in use. Which could definitely cause this problem. I don't see why heap_next_alloc_id() limits the IDs like that in the first place, but even if it used the full 16 bits, that would just make the situation less likely. Instead I'd use consecutive numbers for the pages of an allocation (starting with 1). I'll do that. > > Yep, I noticed that. The hash table already contains 2622 entries, though, so the last rehashing was already almost 400 entries ago. Since the table contains complete garbage only, I'd suspect that the trouble started only recently, maybe with the ongoing exec(). > > Have you had a look at the pages around that one? Maybe it's not the only one with such contents? The attachment also shows the last bytes of the previous (0x00) and several bytes of the next page (0xcc). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 15 16:21:06 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 15 Mar 2008 15:21:06 -0000 Subject: [Haiku-bugs] [Haiku] #1915: Open With does not display candidate apps in the correct order In-Reply-To: <042.6062ef52ee6ed9cb8435a05a8a836708@haiku-os.org> References: <042.6062ef52ee6ed9cb8435a05a8a836708@haiku-os.org> Message-ID: <051.10e19f98510566900c7cbce716e34d37@haiku-os.org> #1915: Open With does not display candidate apps in the correct order -----------------------------------+---------------------------------------- Reporter: ajsmale | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: fixed | Platform: All -----------------------------------+---------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Fixed in r24396. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 15 17:16:05 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 15 Mar 2008 16:16:05 -0000 Subject: [Haiku-bugs] [Haiku] #1920: Userland Heap Garbage in Kernel Heap Page In-Reply-To: <043.587b706d72315bf206a07bb81bdbffef@haiku-os.org> References: <043.587b706d72315bf206a07bb81bdbffef@haiku-os.org> Message-ID: <052.87febea6e105a964c1074ee8777223cf@haiku-os.org> #1920: Userland Heap Garbage in Kernel Heap Page ----------------------------+----------------------------------------------- Reporter: bonefish | Owner: bonefish Type: bug | Status: assigned Priority: blocker | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by mmlr): Replying to [comment:4 bonefish]: > I don't see why heap_next_alloc_id() limits the IDs like that in the first place, but even if it used the full 16 bits, that would just make the situation less likely. Instead I'd use consecutive numbers for the pages of an allocation (starting with 1). I'll do that. It needs to limit the count because the allocation_id is in fact the free_count field, which is only 10 bits in size. But it is really a superfluous field anyway. You could use consecutive numbers in that field, or you could simply mark the last page of the allocation by setting the free_count to some specific value. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 15 18:14:47 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 15 Mar 2008 17:14:47 -0000 Subject: [Haiku-bugs] [Haiku] #1920: Userland Heap Garbage in Kernel Heap Page In-Reply-To: <043.587b706d72315bf206a07bb81bdbffef@haiku-os.org> References: <043.587b706d72315bf206a07bb81bdbffef@haiku-os.org> Message-ID: <052.7c1b7f8b6e9af84db321acc8470bd60e@haiku-os.org> #1920: Userland Heap Garbage in Kernel Heap Page ----------------------------+----------------------------------------------- Reporter: bonefish | Owner: bonefish Type: bug | Status: assigned Priority: blocker | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by mmlr): Indeed there is an even simpler way to solve this problem. When using the empty_index field as the allocation_id you get full 16 bits. Then one can simply use the index of the first page of the allocation as the allocation_id. This is guaranteed to be unique and there is no need for any separate id allocation. Also it needs no change to the rest of the code. I will apply a diff for that right after this comment. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 15 18:37:20 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 15 Mar 2008 17:37:20 -0000 Subject: [Haiku-bugs] [Haiku] #1920: Userland Heap Garbage in Kernel Heap Page In-Reply-To: <043.587b706d72315bf206a07bb81bdbffef@haiku-os.org> References: <043.587b706d72315bf206a07bb81bdbffef@haiku-os.org> Message-ID: <052.91fb180a73ae7a7db1337570815c3478@haiku-os.org> #1920: Userland Heap Garbage in Kernel Heap Page ----------------------------+----------------------------------------------- Reporter: bonefish | Owner: bonefish Type: bug | Status: closed Priority: blocker | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: fixed | Platform: All ----------------------------+----------------------------------------------- Changes (by mmlr): * status: assigned => closed * resolution: => fixed Comment: I couldn't resist fixing it right away. Sorry if I stepped on your toes here Ingo. Should be fixed in r24405. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 15 18:50:22 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 15 Mar 2008 17:50:22 -0000 Subject: [Haiku-bugs] [Haiku] #1920: Userland Heap Garbage in Kernel Heap Page In-Reply-To: <043.587b706d72315bf206a07bb81bdbffef@haiku-os.org> References: <043.587b706d72315bf206a07bb81bdbffef@haiku-os.org> Message-ID: <052.f20477defc8360f96c2b8cddfacd6370@haiku-os.org> #1920: Userland Heap Garbage in Kernel Heap Page ----------------------------+----------------------------------------------- Reporter: bonefish | Owner: bonefish Type: bug | Status: closed Priority: blocker | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: fixed | Platform: All ----------------------------+----------------------------------------------- Comment (by bonefish): Replying to [comment:7 mmlr]: > I couldn't resist fixing it right away. Sorry if I stepped on your toes here Ingo. Not at all. Thanks! Will check later, what the Perl test suite has to say about this change. :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 15 19:02:54 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 15 Mar 2008 18:02:54 -0000 Subject: [Haiku-bugs] [Haiku] #1921: www.perforce.com links to outdated build instructions Message-ID: <041.6b10cf74e015f9eec44741cd8f3b20b0@haiku-os.org> #1921: www.perforce.com links to outdated build instructions -------------------------+-------------------------------------------------- Reporter: mmadia | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -------------------------+-------------------------------------------------- http://www.perforce.com/jam/jam.html has links to whitepapers and examples of projects using jam. One of those links is an article, "Building the OpenBeOS kernel with Jam" from 2002. As you may imagine, nearly all of it is outdated. This is a request to get perforce's link updated to one hosted on haiku- os.org -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 15 19:35:26 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 15 Mar 2008 18:35:26 -0000 Subject: [Haiku-bugs] [Haiku] #1922: www.perforce.com links to outdated build instructions Message-ID: <041.a7f816c25d51b85041c5858b56834c88@haiku-os.org> #1922: www.perforce.com links to outdated build instructions -------------------------+-------------------------------------------------- Reporter: mmadia | Owner: haiku-web Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Website/CMS | Version: R1 development Platform: All | -------------------------+-------------------------------------------------- http://www.perforce.com/jam/jam.html has links to whitepapers and examples of projects using jam. One of those links is an article, "Building the OpenBeOS kernel with Jam" from 2002. As you may imagine, nearly all of it is outdated. This is a request to get perforce's link updated to one hosted on haiku- os.org -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 15 19:48:52 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 15 Mar 2008 18:48:52 -0000 Subject: [Haiku-bugs] [Haiku] #1922: www.perforce.com links to outdated build instructions In-Reply-To: <041.a7f816c25d51b85041c5858b56834c88@haiku-os.org> References: <041.a7f816c25d51b85041c5858b56834c88@haiku-os.org> Message-ID: <050.6af31cdb76e106c7e9d3b2be26f6ce43@haiku-os.org> #1922: www.perforce.com links to outdated build instructions --------------------------+------------------------------------------------- Reporter: mmadia | Owner: haiku-web Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Website/CMS | Version: R1 development Resolution: duplicate | Platform: All --------------------------+------------------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => duplicate Comment: Duplicate of #1921. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 15 20:09:31 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 15 Mar 2008 19:09:31 -0000 Subject: [Haiku-bugs] [Haiku] #1886: Terminal won't get focus back after quiting app launched from Terminal In-Reply-To: <041.c23a06a139b1e0b6118a0c219e3653e8@haiku-os.org> References: <041.c23a06a139b1e0b6118a0c219e3653e8@haiku-os.org> Message-ID: <050.14bfb71a0a42f82a30dd8080c6216cc7@haiku-os.org> #1886: Terminal won't get focus back after quiting app launched from Terminal -----------------------------+---------------------------------------------- Reporter: nutela | Owner: stippi Type: bug | Status: closed Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: fixed | Platform: x86 -----------------------------+---------------------------------------------- Comment (by nutela): I hereby confirm that it does work. Sorry for the delay. Nice work and a warm thank you as always : ) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 16 01:18:30 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 16 Mar 2008 00:18:30 -0000 Subject: [Haiku-bugs] [Haiku] #1923: Time Date inaccurate after booting up Haiku Message-ID: <040.8caab11846b17dc28cf60f9f5c70fda6@haiku-os.org> #1923: Time Date inaccurate after booting up Haiku -------------------------------------+-------------------------------------- Reporter: cebif | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Preferences/Time & Date | Version: R1 development Platform: All | -------------------------------------+-------------------------------------- After booting up Haiku the Time and Date has changed. I have to reset it correctly. For example after my last boot the time was 11:04 AM and the Date was 15th March when it should have been 12:04 PM and 16th March, New Zealand time. I am not certain how to reproduce this but it is either caused after having a long session in one of my other operating systems or booting from cold. My other operating systems are Ubuntu 7.10 and BeOSR5.05 Bone. On booting into R5.05 Bone I frequently find exactly the same bug. I don't know if R5.05 Bone is causing the problem in Haiku or the other way around or they both have the same bug. I will do some more testing, by not booting into one of them for a sufficient period and see if the problem occurs in one or both of them. Also I will not mount the other while I have one in session. Sometime I find even Ubuntu 7.10 time has become inaccurate but a lot less than Haiku or BeOS5.05 Bone. The time setting in my BIOS is set at 24 hour GMT +12 hours. It is always accurate. I was testing with r24393. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 16 05:36:10 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 16 Mar 2008 04:36:10 -0000 Subject: [Haiku-bugs] [Haiku] #1923: Time Date inaccurate after booting up Haiku In-Reply-To: <040.8caab11846b17dc28cf60f9f5c70fda6@haiku-os.org> References: <040.8caab11846b17dc28cf60f9f5c70fda6@haiku-os.org> Message-ID: <049.e157335c870f538815bc6cf6e9d24754@haiku-os.org> #1923: Time Date inaccurate after booting up Haiku --------------------------------------+------------------------------------- Reporter: cebif | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Preferences/Time & Date | Version: R1 development Resolution: | Platform: All --------------------------------------+------------------------------------- Comment (by scottmc): Do you recall what day and time this happened? Try setting your date and time back to that same time and see if it's a repeatable thing that is tied to a specific date/time. Almost sounds like a daylight saving time issue. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 16 05:54:57 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 16 Mar 2008 04:54:57 -0000 Subject: [Haiku-bugs] [Haiku] #1923: Time Date inaccurate after booting up Haiku In-Reply-To: <040.8caab11846b17dc28cf60f9f5c70fda6@haiku-os.org> References: <040.8caab11846b17dc28cf60f9f5c70fda6@haiku-os.org> Message-ID: <049.d63b97381c5a65f493844aded9b2a725@haiku-os.org> #1923: Time Date inaccurate after booting up Haiku --------------------------------------+------------------------------------- Reporter: cebif | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Preferences/Time & Date | Version: R1 development Resolution: | Platform: All --------------------------------------+------------------------------------- Comment (by cebif): I just did a cold boot into Haiku after the computer been turned off for 3 hours. The time was out by 13 hours it was 4:20 AM when it should have been 5:20 PM. It looks like the bug is in Haiku and not Ubuntu 7.10 or another operating system putting the Haiku time settings out. I am not certain about why the BeOSR5.05 Bone time is out though. If one operating system affects another through the BIOS I don't know but it is out by about the same too. The BIOS time always seems to be correct but that is after I have corrected the operating system time and then rebooted into the BIOS setup. Next time when the time is out I wont correct it then reboot straight into BIOS setup. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 16 06:14:11 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 16 Mar 2008 05:14:11 -0000 Subject: [Haiku-bugs] [Haiku] #1923: Time Date inaccurate after booting up Haiku In-Reply-To: <040.8caab11846b17dc28cf60f9f5c70fda6@haiku-os.org> References: <040.8caab11846b17dc28cf60f9f5c70fda6@haiku-os.org> Message-ID: <049.12fc8386208c944e43a500d689c237bd@haiku-os.org> #1923: Time Date inaccurate after booting up Haiku --------------------------------------+------------------------------------- Reporter: cebif | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Preferences/Time & Date | Version: R1 development Resolution: | Platform: All --------------------------------------+------------------------------------- Comment (by cebif): Replying to [comment:1 scottmc]: > Do you recall what day and time this happened? Try setting your date and time back to that same time and see if it's a repeatable thing that is tied to a specific date/time. Almost sounds like a daylight saving time issue. I cannot remember when it first happened. I think it was after I deleted Windows XP and put Ubuntu 7.10, about the beginning of February. There is still daylight saving time here in New Zealand until about the 22nd March. I recently had the wrong BIOS settings for a CPU and the computer would not boot. Not even to a error beep, so I had to reset it. When I set the BIOS time I set it one hour less than the actual time because of thinking it was only in the operating system that daylight savings was accounted for. Now when I look in the BIOS the time matches the operating system time. So does the BIOS time stay the same or does it have to change with daylight saving as well? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 16 11:17:36 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 16 Mar 2008 10:17:36 -0000 Subject: [Haiku-bugs] [Haiku] #1923: Time Date inaccurate after booting up Haiku In-Reply-To: <040.8caab11846b17dc28cf60f9f5c70fda6@haiku-os.org> References: <040.8caab11846b17dc28cf60f9f5c70fda6@haiku-os.org> Message-ID: <049.a238a08eaafbf7ba529040e1124048df@haiku-os.org> #1923: Time Date inaccurate after booting up Haiku --------------------------------------+------------------------------------- Reporter: cebif | Owner: axeld Type: bug | Status: new Priority: low | Milestone: R1 Component: Preferences/Time & Date | Version: R1 development Resolution: | Platform: All --------------------------------------+------------------------------------- Changes (by axeld): * priority: normal => low Comment: Haiku currently uses MET and local time by default. Since you live in NZ, the time being off is just natural since you are also using Ubuntu which defaults to GMT. If you'd be using Windows, you wouldn't see a difference. While I am personally in favour of using GMT myself, probably most people are actually using Windows, and would then have exactly your problem. We had spoken about this on the mailing list some time ago, but we didn't come to any conclusion yet. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 16 13:39:09 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 16 Mar 2008 12:39:09 -0000 Subject: [Haiku-bugs] [Haiku] #1806: [Terminal] will look a little better if welcome message will have an offset (easy) In-Reply-To: <040.5fbb6615ca010d8d424faa39a00236dc@haiku-os.org> References: <040.5fbb6615ca010d8d424faa39a00236dc@haiku-os.org> Message-ID: <049.57aa763340a08ca5b029fff927793a3c@haiku-os.org> #1806: [Terminal] will look a little better if welcome message will have an offset (easy) ------------------------------------+--------------------------------------- Reporter: diver | Owner: jackburton Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Resolution: | Platform: All ------------------------------------+--------------------------------------- Comment (by pulkomandy): I just made a patch to add a 3 pixel space at the left of the TermView. There seems to be some problems with characters hiding under the scrollbar, however. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 16 15:57:21 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 16 Mar 2008 14:57:21 -0000 Subject: [Haiku-bugs] [Haiku] #5: PCI bus_manager does not assign IRQs In-Reply-To: <050.1b115f9e56146d5f64bfaf3e88e0f82d@haiku-os.org> References: <050.1b115f9e56146d5f64bfaf3e88e0f82d@haiku-os.org> Message-ID: <059.47d9d2a13370153f603f3bcb31073454@haiku-os.org> #5: PCI bus_manager does not assign IRQs ------------------------------+--------------------------------------------- Reporter: marcusoverhagen | Owner: marcusoverhagen Type: bug | Status: assigned Priority: high | Milestone: R1 Component: System/Kernel | Version: Resolution: | Platform: All ------------------------------+--------------------------------------------- Changes (by siarzhuk): * cc: siarzhuk (added) * platform: => All -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 16 16:32:12 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 16 Mar 2008 15:32:12 -0000 Subject: [Haiku-bugs] [Haiku] #1923: Time Date inaccurate after booting up Haiku In-Reply-To: <040.8caab11846b17dc28cf60f9f5c70fda6@haiku-os.org> References: <040.8caab11846b17dc28cf60f9f5c70fda6@haiku-os.org> Message-ID: <049.b9e5cf07c70e0cd89dc7fe06829534de@haiku-os.org> #1923: Time Date inaccurate after booting up Haiku --------------------------------------+------------------------------------- Reporter: cebif | Owner: axeld Type: bug | Status: new Priority: low | Milestone: R1 Component: Preferences/Time & Date | Version: R1 development Resolution: | Platform: All --------------------------------------+------------------------------------- Changes (by andreasf): * cc: andreasf (added) Comment: Axel, I have been facing this issue too in a triple-boot configuration with Ubuntu, BeOS and Haiku. In BeOS the time looked good but is off in Haiku, leading to issues when accessing a common BFS volume, i.e. for `make` (as mentioned recently on the list). The natural way to fix this would be to offer a choice of storing as local or GMT, like Linux did until recently. It should default to GMT and offer local time for Windows compatibility only. But currently it seems that only displaying GMT time is possible. A workaround might be to add NTP support to Haiku so that at least the time is adjusted to displaying and using the correct time even if storing it in different ways? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 16 16:50:37 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 16 Mar 2008 15:50:37 -0000 Subject: [Haiku-bugs] [Haiku] #1924: Incomplete support of 1002:564f: M26 [Radeon Mobility X700 XL (PCIE)] Message-ID: <043.90f639e039e173df61e8d17f89c32583@haiku-os.org> #1924: Incomplete support of 1002:564f: M26 [Radeon Mobility X700 XL (PCIE)] -------------------------------------+-------------------------------------- Reporter: siarzhuk | Owner: euan Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/radeon | Version: R1 development Platform: All | -------------------------------------+-------------------------------------- I have observed wrong behavior of the radeon driver with laptop that have following graphics hardware: {{{ device Display controller (VGA compatible controller, VGA) [3|0|0] vendor 1002: ATI Technologies Inc device 564f: M26 [Radeon Mobility X700 XL (PCIE)] }}} This test was performed on clean build of Haiku r24409. Attached syslog was acquired during all test session. syslog contains my comments about test phases. Those comments are separated from other log information by following marks: {{{ >>>>>>>>>>>>>>>>>>>>>>>>>> SZ: >>>>>>>>>>>>>>>>>>>>>>>>>> }}} '''Note:''' All issues described in this test are related to embedded laptop LCD panel. No tests with external monitor were performed. '''Note:''' This laptop has some set of extended keyboard shortcuts (function shurtcuts). One of this shortcuts is used to switch graphic output between internal LCD panel of the laptop and external monitor output. This switch output shortcut mentioned below as "Fn- shortcut". '''== The Test. ==''' '''Step 1'''. I boot into Haiku and wait enough time to let system finish all setup actions. The image on the screen is mainly black. Only small band of pixels contains some graphic information. This band has about 10-20 pixels of height and it's height changed sporadically. The image in this band mainly correspond to data at the top of normal Desktop. that means that there top of Deskbar panel at the right side and mouse pointer can be visible in case it was moved at the top of the screen. '''Step 2'''. Now I press the Fn- keyboard shortcut '''once''' and can see normal Haiku desktop at full screen height. Note that Deskbar panel is not visible now. Looks like default resolution is set to 1280x800 but physical resolution of the screen is 800x600 pixels. Deskbar panel is not visible because it is out of the "viewport". '''Step 3'''. I called Screen Perflet and try to change screen resolution to 800x600. After pressing Apply button the screen goes black. I wait for some minutes to let the system change resolution back to initial value. The screen is left black for this time. I have to press Fn- keyboard shortcut '''once''' again to see the Desktop. '''Step 4'''. Next attempt to change screen resolution to 800x600. After pressing Apply button I pressed Fn- button '''immediately''' and acknowledged screen resolution change. Now I can see normal Haiku desktop. Note that Deskbar is visible now at it's normal place at right edge of the screen. Looks like physical screen resolution correspond to Haiku Desktop resolution now. '''Step 5'''. At the next step I tried to change screen resolution to 640x480. After pressing Apply button I pressed Fn- button '''immediately''' and acknowledged screen resolution change. Looks like physical resolution is 800x600 but Desktop resolution was changed to 640x480. The image I have observed after this you can see in attached "640x480" file. Part of information at right side of the screen duplicate the same one from the left edge of the screen. The band at the bottom of the screen contains some garbage. '''Step 6'''. Now I change the resolution to 800x600, press Apply button, press Fn- immediately and confirm resolution change. The situation is the same as in step 4 of this test. Desktop is a bit stretched but looks like usable. '''== Conclusion ==''' Current revison (r24409) of the radeon driver has following problems: - cannot initialize internal laptop display on system start or in case of resolution change. - cannot change physical resolution of the display. Changing of the resolution changes only Desktop one - the "viewport" resolution is always 800x600 pixels. Beside of those problems radeon driver on ATI X700 XL looks usable in 800x600 mode. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 16 17:28:22 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 16 Mar 2008 16:28:22 -0000 Subject: [Haiku-bugs] [Haiku] #1911: PANIC: heap: huge allocation of 6292992 bytes asked! In-Reply-To: <040.1669ad96ac1dfccf47005827906732ce@haiku-os.org> References: <040.1669ad96ac1dfccf47005827906732ce@haiku-os.org> Message-ID: <049.d222a54370232f951b5f7ea023b86b5b@haiku-os.org> #1911: PANIC: heap: huge allocation of 6292992 bytes asked! -------------------------------+-------------------------------------------- Reporter: thorn | Owner: axeld Type: bug | Status: closed Priority: high | Milestone: R1/alpha1 Component: File Systems/BFS | Version: R1 development Resolution: fixed | Platform: All -------------------------------+-------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: I've improved BPlusTree::_SeekDown() in rr24411 to detect errors in the B+tree structure earlier. Since I've also fixed a big bug in r24410 that could have clobbered your disk before, I'm closing this bug. Without more information, I can't do anymore, anyways - and that particular thing cannot happen anymore that way. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 16 18:01:29 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 16 Mar 2008 17:01:29 -0000 Subject: [Haiku-bugs] [Haiku] #1925: Reboot during startup on Toshiba Satellite 2615DVD/6.0 Message-ID: <046.464cc1a60522972f4d6a4db8a13a4bd4@haiku-os.org> #1925: Reboot during startup on Toshiba Satellite 2615DVD/6.0 ---------------------------+------------------------------------------------ Reporter: umccullough | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Platform: x86 | ---------------------------+------------------------------------------------ Booting Haiku natively on this laptop causes it to reboot shortly after showing the HAIKU logo at the bottom of the screen. Tried disabling all options in boot menu, and it won't boot into Safe Mode either. Possibly something I've done wrong, or possible the funky hardware on this laptop (some Linux LiveCDs hang at boot on this machine also - but usually after the X server is started). Laptop is an older Toshiba Satellite 2615DVD/6.0: PII Celeron running at ~430mhz 192MB RAM 6GB disk with Linux on it (first partition on the drive is ~256mb for Haiku) Attaching serial debug log. lspci output will be attached shortly. Note: this was built and installed directly to the partition from within Xubuntu 7.10 which generally doesn't give me any problems on other machines. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 16 18:08:53 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 16 Mar 2008 17:08:53 -0000 Subject: [Haiku-bugs] [Haiku] #1925: Reboot during startup on Toshiba Satellite 2615DVD/6.0 In-Reply-To: <046.464cc1a60522972f4d6a4db8a13a4bd4@haiku-os.org> References: <046.464cc1a60522972f4d6a4db8a13a4bd4@haiku-os.org> Message-ID: <055.8cf22fb7acccdadce327aae03ecf799a@haiku-os.org> #1925: Reboot during startup on Toshiba Satellite 2615DVD/6.0 ----------------------------+----------------------------------------------- Reporter: umccullough | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by umccullough): Should also add that it was r24408 built with gcc2.95.3 and configured with --include-gpl-addons and --include-3rdparty -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 16 20:10:26 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 16 Mar 2008 19:10:26 -0000 Subject: [Haiku-bugs] [Haiku] #1926: PANIC: page fault, but interrupts were disabled. Touching address 0x00000025 from eip 0x8006106c Message-ID: <040.edac3e61ab29cf2ddc247d6fba566fc1@haiku-os.org> #1926: PANIC: page fault, but interrupts were disabled. Touching address 0x00000025 from eip 0x8006106c ---------------------------+------------------------------------------------ Reporter: thorn | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Platform: x86 | ---------------------------+------------------------------------------------ tested on r24348. random bug. i catch it twice today. wait interval 96850, scan pages 7814, free 202, target 3894 wait interval 87109, scan pages 7892, free 160, target 3936 check through wait interval 77136, scan pages 7973, free 117, target 3979 PANIC: page fault, but interrupts were disabled. Touching address 0x00000025 from eip 0x8006106c Welcome to Kernel Debugging Land... Running on CPU 0 kdebug> bt full could not find thread 0 frame caller :function + offset 92333398 (+ 52) 80082db3 :invoke_debugger_command + 0x00cf 923333cc (+ 64) 80083b54 :_ParseCommand__16ExpressionParserRi + 0x01f8 9233340c (+ 48) 80083546 :EvaluateCommand__16ExpressionParserPCcRi + 0x01de 9233343c (+ 228) 80084c68 :evaluate_debug_command + 0x0088 92333520 (+ 64) 80081986 :kernel_debugger_loop__Fv + 0x017a 92333560 (+ 48) 800825d1 :kernel_debugger + 0x010d 92333590 (+ 192) 800824b9 :panic + 0x0029 92333650 (+ 48) 8008f220 :page_fault_exception + 0x0060 92333680 (+ 12) 800924dd :int_bottom + 0x001d (nearest) iframe at 0x9233368c (end = 0x923336e4) eax 0x1 ebx 0x1 ecx 0x800d1df4 edx 0xf0 esi 0x92333768 edi 0x800d1db4 ebp 0x92333704 esp 0x923336c0 eip 0x8006106c eflags 0x10002 vector: 0xe, error code: 0x0 9233368c (+ 120) 8006106c :find_page_candidate__FR7vm_pageb + 0x0094 92333704 (+ 144) 8006136e :steal_pages__FPP7vm_pageUlb + 0x0052 92333794 (+ 96) 80061f61 :vm_page_allocate_page + 0x0139 923337f4 (+ 128) 80058096 :vm_create_anonymous_area + 0x02d6 92333874 (+ 80) 8005d7a7 :create_area + 0x003b 923338c4 (+ 64) 8008a048 :area_allocate_pages__FP12object_cachePPvUl + 0x004c 92333904 (+ 48) 8008b608 :CreateSlab__17HashedObjectCacheUl + 0x0040 92333934 (+ 48) 8008b1d9 :object_cache_reserve_internal__FP12object_cacheUlUl + 0x0049 92333964 (+ 64) 8008ac36 :object_cache_alloc + 0x0076 923339a4 (+ 32) 80062e8b :Allocate__11block_cache + 0x0017 923339c4 (+ 64) 80065e9b :block_cache_get_etc + 0x0087 92333a04 (+ 128) 802ddab7 :GetNext__17AttributeIteratorPcPUlPUlPx + 0x0063 92333a84 (+ 368) 802dc26f :Free__5InodeR11Transaction + 0x007f 92333bf4 (+ 80) 802e4a0c :bfs_remove_vnode__FPvT0b + 0x00bc 92333c44 (+ 48) 8004587a :free_vnode__FP5vnodeb + 0x00e6 92333c74 (+ 48) 800459bb :dec_vnode_ref_count__FP5vnodeb + 0x0103 92333ca4 (+ 48) 80048856 :put_vnode + 0x0052 92333cd4 (+ 48) 802ceba9 :Put__5Vnode + 0x0031 92333d04 (+ 128) 802dce23 :Remove__5InodeR11TransactionPCcPxb + 0x047f 92333d84 (+ 80) 802e5ed1 :bfs_unlink__FPvT0PCc + 0x00d9 92333dd4 (+ 304) 8004b871 :common_unlink__FiPcb + 0x0071 92333f04 (+ 64) 8005053f :_user_unlink + 0x0093 92333f44 (+ 100) 80092652 :pre_syscall_debug_done + 0x0002 (nearest) iframe at 0x92333fa8 (end = 0x92334000) eax 0x55 ebx 0x458bc8 ecx 0x7ffe69c4 edx 0xffff0104 esi 0x18044ed8 edi 0x1a2681e8 ebp 0x7ffe69f0 esp 0x92333fdc eip 0xffff0104 eflags 0x213 vector: 0x63, error code: 0x0 92333fa8 (+ 0) ffff0104 [*** READ/WRITE FAULT ***] kdebug> -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 16 20:18:55 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 16 Mar 2008 19:18:55 -0000 Subject: [Haiku-bugs] [Haiku] #1927: BeIDE: resize drawing bug Message-ID: <040.2cf3162f57a4851d4621a219dafbb412@haiku-os.org> #1927: BeIDE: resize drawing bug ----------------------------------+----------------------------------------- Reporter: thorn | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Application Kit | Version: R1 development Platform: x86 | ----------------------------------+----------------------------------------- see attach -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 16 20:22:49 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 16 Mar 2008 19:22:49 -0000 Subject: [Haiku-bugs] [Haiku] #1927: BeIDE: resize drawing bug In-Reply-To: <040.2cf3162f57a4851d4621a219dafbb412@haiku-os.org> References: <040.2cf3162f57a4851d4621a219dafbb412@haiku-os.org> Message-ID: <049.013b521771aedcc71b08f66fb5a9ff0d@haiku-os.org> #1927: BeIDE: resize drawing bug -----------------------------------+---------------------------------------- Reporter: thorn | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Application Kit | Version: R1 development Resolution: | Platform: x86 -----------------------------------+---------------------------------------- Comment (by thorn): haiku r24348 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 16 21:26:46 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 16 Mar 2008 20:26:46 -0000 Subject: [Haiku-bugs] [Haiku] #1923: Time Date inaccurate after booting up Haiku In-Reply-To: <040.8caab11846b17dc28cf60f9f5c70fda6@haiku-os.org> References: <040.8caab11846b17dc28cf60f9f5c70fda6@haiku-os.org> Message-ID: <049.7a3de56f0095ef092a5e5681a683f70e@haiku-os.org> #1923: Time Date inaccurate after booting up Haiku --------------------------------------+------------------------------------- Reporter: cebif | Owner: axeld Type: bug | Status: new Priority: low | Milestone: R1 Component: Preferences/Time & Date | Version: R1 development Resolution: | Platform: All --------------------------------------+------------------------------------- Comment (by stippi): I am affected by this too. I think it should be "low" priority, but I don't have time to look into it myself right now... ;-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 16 21:29:03 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 16 Mar 2008 20:29:03 -0000 Subject: [Haiku-bugs] [Haiku] #1927: BeIDE: resize drawing bug In-Reply-To: <040.2cf3162f57a4851d4621a219dafbb412@haiku-os.org> References: <040.2cf3162f57a4851d4621a219dafbb412@haiku-os.org> Message-ID: <049.d7896abba1de67087a75e71ed9989a1b@haiku-os.org> #1927: BeIDE: resize drawing bug -----------------------------------+---------------------------------------- Reporter: thorn | Owner: stippi Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Kits/Application Kit | Version: R1 development Resolution: | Platform: x86 -----------------------------------+---------------------------------------- Changes (by stippi): * owner: axeld => stippi * status: new => assigned Comment: This falls into my domain, but feel free to beat me to fixing this. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 16 22:02:24 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 16 Mar 2008 21:02:24 -0000 Subject: [Haiku-bugs] [Haiku] #1924: Incomplete support of 1002:564f: M26 [Radeon Mobility X700 XL (PCIE)] In-Reply-To: <043.90f639e039e173df61e8d17f89c32583@haiku-os.org> References: <043.90f639e039e173df61e8d17f89c32583@haiku-os.org> Message-ID: <052.3584c248eeabd95516042ce87bbcfda9@haiku-os.org> #1924: Incomplete support of 1002:564f: M26 [Radeon Mobility X700 XL (PCIE)] --------------------------------------+------------------------------------- Reporter: siarzhuk | Owner: euan Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Graphics/radeon | Version: R1 development Resolution: | Platform: All --------------------------------------+------------------------------------- Changes (by euan): * status: new => assigned Comment: Looks like the syslog is missing the radeon driver's debug. We should be able to see the memory init, bios readouts, edid, etc. Did you change the debug levels? Regardless it seems similar to the issue I get with Dual DVI when the resolution on the second screen is changed to a non-native resolution. Because there is only one scaler, when the resolution is > native the image wraps over the vieable area (like the screenshot). When < the vertical / horizontal native screen resolution garbage is displayed because the framebuffer isn't cleared before hand (sort of an "uncentered" centered timings rather than using the scaler to stretch). Looks like perhaps the connector table is wrong in the bios, and is worked around in other OS's. Or that our connector mapping can't handle it. At least your backlight comes on. Most M26 owners are greeted with darkness :) Will look into it when merging the Xx000 support. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 16 22:56:26 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 16 Mar 2008 21:56:26 -0000 Subject: [Haiku-bugs] [Haiku] #1923: Time Date inaccurate after booting up Haiku In-Reply-To: <040.8caab11846b17dc28cf60f9f5c70fda6@haiku-os.org> References: <040.8caab11846b17dc28cf60f9f5c70fda6@haiku-os.org> Message-ID: <049.ecaef3bb1c9b43d5e57315e7eeb02cc6@haiku-os.org> #1923: Time Date inaccurate after booting up Haiku --------------------------------------+------------------------------------- Reporter: cebif | Owner: axeld Type: bug | Status: new Priority: low | Milestone: R1 Component: Preferences/Time & Date | Version: R1 development Resolution: | Platform: All --------------------------------------+------------------------------------- Comment (by cebif): Replying to [comment:4 axeld]: > Haiku currently uses MET and local time by default. Since you live in NZ, the time being off is just natural since you are also using Ubuntu which defaults to GMT. > > If you'd be using Windows, you wouldn't see a difference. While I am personally in favour of using GMT myself, probably most people are actually using Windows, and would then have exactly your problem. We had spoken about this on the mailing list some time ago, but we didn't come to any conclusion yet. I have set opened the Time preferences on the Deskbar and put the "Clock set to" at GMT then adjusted to correct time. This set the BIOS time back 13 hours which is correct for GMT. I then rebooted into Ubuntu and the back into Haiku and the Time was correct. This might be a workaround by having Haiku set at GMT. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 16 23:03:45 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 16 Mar 2008 22:03:45 -0000 Subject: [Haiku-bugs] [Haiku] #1924: Incomplete support of 1002:564f: M26 [Radeon Mobility X700 XL (PCIE)] In-Reply-To: <043.90f639e039e173df61e8d17f89c32583@haiku-os.org> References: <043.90f639e039e173df61e8d17f89c32583@haiku-os.org> Message-ID: <052.b4202dca76e9628a9f9761609ab5a687@haiku-os.org> #1924: Incomplete support of 1002:564f: M26 [Radeon Mobility X700 XL (PCIE)] --------------------------------------+------------------------------------- Reporter: siarzhuk | Owner: euan Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Graphics/radeon | Version: R1 development Resolution: | Platform: All --------------------------------------+------------------------------------- Comment (by siarzhuk): Replying to [comment:1 euan]: > Looks like the syslog is missing the radeon driver's debug. We should be able to > see the memory init, bios readouts, edid, etc. Did you change the debug levels? No. I tried to find any "switches" to increase debug output level in source code but was unlucky. Could you, please, say me how can I acquire more informative syslog? > Regardless it seems similar to the issue I get with Dual DVI when the resolution on > the second screen is changed to a non-native resolution. Note that initial state, right after system boot and before I pressed Fn- is looks like 800x600. I see the top of Deskbar panel in this "sporadic band". After pressing Fn- shortcut I get the 1280x800 Desktop resolution. But this pseudo-800x600 can be a result of horizontal overlapping. It looks like "non-initialized height". > Looks like perhaps the connector table is wrong in the bios, and is worked around > in other OS's. Or that our connector mapping can't handle it. I remember Year ago we have used some additional software to get registers under windows. If you need this info again - let me know. This laptop has Windows XP and FreeBSD installations on it. > At least your backlight comes on. Most M26 owners are greeted with darkness :) > I'm just lucky with this "sporadic top band" issue. Note that after I try to switch resolution with Screen Perflet - the screen goes '''completely''' black. I don't think that blackened display with backlight on has different look than display with backlight switched off. ;-) > Will look into it when merging the Xx000 support. Of course, you can request from me any information or tests you will need. Thank you. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 16 23:26:36 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 16 Mar 2008 22:26:36 -0000 Subject: [Haiku-bugs] [Haiku] #1928: Initializing of a partition only succeeds if it's no BFS partition already Message-ID: <040.74e7b25a185020f7ca3bd7bfe2c5b3d8@haiku-os.org> #1928: Initializing of a partition only succeeds if it's no BFS partition already ------------------------------+--------------------------------------------- Reporter: axeld | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: Kits/Storage Kit | Version: R1 development Platform: All | ------------------------------+--------------------------------------------- If you have a BFS partition that you want to initialize again using DriveSetup, it will fail with B_ERROR. The reason is that "initialize" itself is only called when the partition type differs, which is apparently not the case here. Calling the other methods just fail. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 16 23:30:45 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 16 Mar 2008 22:30:45 -0000 Subject: [Haiku-bugs] [Haiku] #1926: PANIC: page fault, but interrupts were disabled. Touching address 0x00000025 from eip 0x8006106c In-Reply-To: <040.edac3e61ab29cf2ddc247d6fba566fc1@haiku-os.org> References: <040.edac3e61ab29cf2ddc247d6fba566fc1@haiku-os.org> Message-ID: <049.a0b8c0ab3067156a48b5ffce5b463ea9@haiku-os.org> #1926: PANIC: page fault, but interrupts were disabled. Touching address 0x00000025 from eip 0x8006106c ----------------------------+----------------------------------------------- Reporter: thorn | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: duplicate | Platform: x86 ----------------------------+----------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => duplicate Comment: Duplicate of bug #1900. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 16 23:31:21 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 16 Mar 2008 22:31:21 -0000 Subject: [Haiku-bugs] [Haiku] #1900: PANIC: page fault, but interrupts were disabled, ... In-Reply-To: <041.d22ef3f2e64866831498841e104bf80a@haiku-os.org> References: <041.d22ef3f2e64866831498841e104bf80a@haiku-os.org> Message-ID: <050.454d121fcbd4d5b5061e1a9903bede40@haiku-os.org> #1900: PANIC: page fault, but interrupts were disabled, ... ----------------------------+----------------------------------------------- Reporter: stippi | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by axeld): Bug #1926 is a duplicate of this one, and contains a slightly different stack crawl. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 17 03:31:19 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 17 Mar 2008 02:31:19 -0000 Subject: [Haiku-bugs] [Haiku] #1929: steal_pages() Livelock Message-ID: <043.816a1d880fac2ebc91ac1ed2e54c6cbd@haiku-os.org> #1929: steal_pages() Livelock ---------------------------+------------------------------------------------ Reporter: bonefish | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Platform: All | ---------------------------+------------------------------------------------ r24417, VMware Cf. attached KDL session. While running a perl test that caused lots of CPU and some memory pressure, the system got into a (quasi) livelock situation: Two high-priority threads (PS/2 mouse watcher and input server event loop) are in steal_pages(), only one inactive page is left. The cache of the page is currently locked by a lower priority thread, hence steal_page() fails for the page. The steal_pages() of the high priority threads gets the page via find_page_candidate(), but steal_page() fails. It does a sFreePageCondition.NotifyOne(), which wakes up the other high priority thread and waits on sFreePageCondition. Since both threads are high priority, the thread owning the lock is starved. There are several factors contributing to this situation: ConditionVariable doesn't use a thread queue, but a stack, so NotifyOne() always wakes up the thread that last started waiting. Furthermore our scheduler is not fair enough. The lower priority thread shouldn't be starved. Anyway, I don't quite see the reason for the NotifyOne() call. It is only done when steal_page() fails, in which case other threads won't be any luckier. A snooze() might be more appropriate. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 17 09:47:23 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 17 Mar 2008 08:47:23 -0000 Subject: [Haiku-bugs] [Haiku] #1921: www.perforce.com links to outdated build instructions In-Reply-To: <041.6b10cf74e015f9eec44741cd8f3b20b0@haiku-os.org> References: <041.6b10cf74e015f9eec44741cd8f3b20b0@haiku-os.org> Message-ID: <050.397912fa87bb8d180ec92b2c062b86ac@haiku-os.org> #1921: www.perforce.com links to outdated build instructions ----------------------------+----------------------------------------------- Reporter: mmadia | Owner: nielx Type: enhancement | Status: assigned Priority: normal | Milestone: Component: Documentation | Version: Resolution: | Platform: All ----------------------------+----------------------------------------------- Changes (by nielx): * owner: axeld => nielx * status: new => assigned * version: R1 development => * component: - General => Documentation * milestone: R1 => -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 17 09:56:17 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 17 Mar 2008 08:56:17 -0000 Subject: [Haiku-bugs] [Haiku] #1921: www.perforce.com links to outdated build instructions In-Reply-To: <041.6b10cf74e015f9eec44741cd8f3b20b0@haiku-os.org> References: <041.6b10cf74e015f9eec44741cd8f3b20b0@haiku-os.org> Message-ID: <050.ca621c89ac411e29197c826b3883f250@haiku-os.org> #1921: www.perforce.com links to outdated build instructions ----------------------------+----------------------------------------------- Reporter: mmadia | Owner: nielx Type: enhancement | Status: assigned Priority: normal | Milestone: Component: Documentation | Version: Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by nielx): Have you actually sent a mail yet, or should I do that? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 17 11:23:45 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 17 Mar 2008 10:23:45 -0000 Subject: [Haiku-bugs] [Haiku] #1925: Reboot during startup on Toshiba Satellite 2615DVD/6.0 In-Reply-To: <046.464cc1a60522972f4d6a4db8a13a4bd4@haiku-os.org> References: <046.464cc1a60522972f4d6a4db8a13a4bd4@haiku-os.org> Message-ID: <055.4eb648305fabe46609714877f22fc9f0@haiku-os.org> #1925: Reboot during startup on Toshiba Satellite 2615DVD/6.0 ----------------------------+----------------------------------------------- Reporter: umccullough | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by jackburton): I have seen a similar issue on an HP DC 7600 (Pentium 4), booting from CD. I haven't filed a bug yet because I don't have the pc at hand to do tests (it's not my pc). I was able to boot further (it then panics by not finding a boot volume) by disabling the "use APIC I/O" (or something similar) option in the bios. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 17 12:22:07 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 17 Mar 2008 11:22:07 -0000 Subject: [Haiku-bugs] [Haiku] #1930: Different behavior when clicking on an application in the leaf menu Message-ID: <042.c8a7d2f2f8b00891f2fe053e7bbcc81f@haiku-os.org> #1930: Different behavior when clicking on an application in the leaf menu ----------------------------+----------------------------------------------- Reporter: emitrax | Owner: anevilyak Type: enhancement | Status: new Priority: normal | Milestone: Unscheduled Component: User Interface | Version: R1 development Platform: All | ----------------------------+----------------------------------------------- As for now, if you click with the left button, or middle-click on an application in the leaf menu, the behavior is the same: the application starts up and the menu gets closed. I think that having a different behavior (e.g keeping the leaf menu opened if you middle click and close it if you use the left button) would be better, as quite often (especially on startup) I find myself, and I'm sure I'm not the only one, in the need to launch many applications at once, and keeping the menu opened is far more better than open it and close it repeatedly. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 17 13:52:25 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 17 Mar 2008 12:52:25 -0000 Subject: [Haiku-bugs] [Haiku] #1928: Initializing of a partition only succeeds if it's no BFS partition already In-Reply-To: <040.74e7b25a185020f7ca3bd7bfe2c5b3d8@haiku-os.org> References: <040.74e7b25a185020f7ca3bd7bfe2c5b3d8@haiku-os.org> Message-ID: <049.4530ce949643d23f34d2a31bbee59a26@haiku-os.org> #1928: Initializing of a partition only succeeds if it's no BFS partition already -------------------------------+-------------------------------------------- Reporter: axeld | Owner: axeld Type: bug | Status: assigned Priority: normal | Milestone: R1/alpha1 Component: Kits/Storage Kit | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Changes (by axeld): * owner: stippi => axeld * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 17 13:54:21 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 17 Mar 2008 12:54:21 -0000 Subject: [Haiku-bugs] [Haiku] #1928: Initializing of a partition only succeeds if it's no BFS partition already In-Reply-To: <040.74e7b25a185020f7ca3bd7bfe2c5b3d8@haiku-os.org> References: <040.74e7b25a185020f7ca3bd7bfe2c5b3d8@haiku-os.org> Message-ID: <049.1ff5a65b40bbd41439cb56cfefe9582d@haiku-os.org> #1928: Initializing of a partition only succeeds if it's no BFS partition already -------------------------------+-------------------------------------------- Reporter: axeld | Owner: axeld Type: bug | Status: assigned Priority: normal | Milestone: R1/alpha1 Component: Kits/Storage Kit | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Comment (by axeld): Situation improved with r24419: the initialization job is now created, but _kern_initialize_partition() now returns B_BUSY. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 17 14:12:01 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 17 Mar 2008 13:12:01 -0000 Subject: [Haiku-bugs] [Haiku] #1928: Initializing of a partition only succeeds if it's no BFS partition already In-Reply-To: <040.74e7b25a185020f7ca3bd7bfe2c5b3d8@haiku-os.org> References: <040.74e7b25a185020f7ca3bd7bfe2c5b3d8@haiku-os.org> Message-ID: <049.a035b6e7192090d5ff2212256475be8c@haiku-os.org> #1928: Initializing of a partition only succeeds if it's no BFS partition already -------------------------------+-------------------------------------------- Reporter: axeld | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1/alpha1 Component: Kits/Storage Kit | Version: R1 development Resolution: fixed | Platform: All -------------------------------+-------------------------------------------- Changes (by axeld): * status: assigned => closed * resolution: => fixed Comment: Fixed in r24421. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 17 14:58:03 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 17 Mar 2008 13:58:03 -0000 Subject: [Haiku-bugs] [Haiku] #426: [Tracker] Incorrect attribute position after attribute clicked In-Reply-To: <057.7a7f623fd1ababecc8fe30e807cd6cc6@haiku-os.org> References: <057.7a7f623fd1ababecc8fe30e807cd6cc6@haiku-os.org> Message-ID: <066.9a5729a44fc0629e7076088e0c2df07a@haiku-os.org> #426: [Tracker] Incorrect attribute position after attribute clicked -------------------------------------+-------------------------------------- Reporter: g.zachrisson at gmail.com | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: Resolution: fixed | Platform: All -------------------------------------+-------------------------------------- Changes (by jackburton): * status: new => closed * resolution: => fixed Comment: Fixed already. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 17 15:19:04 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 17 Mar 2008 14:19:04 -0000 Subject: [Haiku-bugs] [Haiku] #1461: Drag icon of current folder disappears when resizing In-Reply-To: <044.b6ad9d2f724b380ca496d3edcae76948@haiku-os.org> References: <044.b6ad9d2f724b380ca496d3edcae76948@haiku-os.org> Message-ID: <053.3a2259676573c9ca29856c9d1784dfde@haiku-os.org> #1461: Drag icon of current folder disappears when resizing -----------------------------------+---------------------------------------- Reporter: humdinger | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: | Platform: All -----------------------------------+---------------------------------------- Comment (by jackburton): Ah yes definitely! Could be for example a BMenuBar invalidation issue... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 17 15:21:11 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 17 Mar 2008 14:21:11 -0000 Subject: [Haiku-bugs] [Haiku] #1520: Cursor ghosting when trying to rename in tracker In-Reply-To: <042.b87be069ea06c15b6ff80881aac67e2e@haiku-os.org> References: <042.b87be069ea06c15b6ff80881aac67e2e@haiku-os.org> Message-ID: <051.993e37ce4ceb38de386269b81c867093@haiku-os.org> #1520: Cursor ghosting when trying to rename in tracker -----------------------------+---------------------------------------------- Reporter: scottmc | Owner: stippi Type: bug | Status: closed Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: fixed | Platform: All -----------------------------+---------------------------------------------- Changes (by jackburton): * status: new => closed * resolution: => fixed -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 17 15:30:42 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 17 Mar 2008 14:30:42 -0000 Subject: [Haiku-bugs] [Haiku] #1878: Dropdown menu, first item not selectable In-Reply-To: <041.fb2311908f30e9ec71ea3e67244fd591@haiku-os.org> References: <041.fb2311908f30e9ec71ea3e67244fd591@haiku-os.org> Message-ID: <050.7d3df8717317b20916a71f4db771cd05@haiku-os.org> #1878: Dropdown menu, first item not selectable ---------------------------------+------------------------------------------ Reporter: aldeck | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by jackburton): * owner: axeld => jackburton -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 17 15:31:38 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 17 Mar 2008 14:31:38 -0000 Subject: [Haiku-bugs] [Haiku] #1897: BSnow: "Click to remove" does not work In-Reply-To: <041.7fe61d5c7b93f820f1a1efd2fc499962@haiku-os.org> References: <041.7fe61d5c7b93f820f1a1efd2fc499962@haiku-os.org> Message-ID: <050.e5849ed24af02bd797a86be02c4abdac@haiku-os.org> #1897: BSnow: "Click to remove" does not work ---------------------------+------------------------------------------------ Reporter: stippi | Owner: mmu_man Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by jackburton): Looks like a scripting issue... probably in BShelf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 17 16:05:49 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 17 Mar 2008 15:05:49 -0000 Subject: [Haiku-bugs] [Haiku] #1319: [Tracker] desktop icons selection is shifted 1px to the left In-Reply-To: <040.bef90aba15345c94303c110fc6ac4fcf@haiku-os.org> References: <040.bef90aba15345c94303c110fc6ac4fcf@haiku-os.org> Message-ID: <049.ec5b32a593446428910cde5435620878@haiku-os.org> #1319: [Tracker] desktop icons selection is shifted 1px to the left ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by jackburton): I suspect haiku renders the text 1 pixels off to the right in respect to how it's rendered on beos. Evidences: - The problem described here - this comment in BTextView::PointAt() // convert from text rect coordinates // NOTE: I didn't understand why "- 1.0" // and it works only correct without it on Haiku app_server. // Feel free to enlighten me though! result.x += fTextRect.left;// - 1.0; - The fact that our Terminal on BeOS draws the text 1 pixel shifted to the left -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 17 16:43:37 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 17 Mar 2008 15:43:37 -0000 Subject: [Haiku-bugs] [Haiku] #1897: BSnow: "Click to remove" does not work In-Reply-To: <041.7fe61d5c7b93f820f1a1efd2fc499962@haiku-os.org> References: <041.7fe61d5c7b93f820f1a1efd2fc499962@haiku-os.org> Message-ID: <050.ee924d55314bb5af712ee19349e96be4@haiku-os.org> #1897: BSnow: "Click to remove" does not work ---------------------------+------------------------------------------------ Reporter: stippi | Owner: mmu_man Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by mmu_man): It might also be one of the specifiers that got renamed from the BeOS version... would need to check that. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 17 19:25:07 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 17 Mar 2008 18:25:07 -0000 Subject: [Haiku-bugs] [Haiku] #1925: Reboot during startup on Toshiba Satellite 2615DVD/6.0 In-Reply-To: <046.464cc1a60522972f4d6a4db8a13a4bd4@haiku-os.org> References: <046.464cc1a60522972f4d6a4db8a13a4bd4@haiku-os.org> Message-ID: <055.38e1965b988fb79de72405ee23737ac7@haiku-os.org> #1925: Reboot during startup on Toshiba Satellite 2615DVD/6.0 ----------------------------+----------------------------------------------- Reporter: umccullough | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by umccullough): Good idea. I will try messing with some of the more obscure BIOS settings and see if that changes my results. Will update in a day or two with any results I find. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 17 22:43:43 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 17 Mar 2008 21:43:43 -0000 Subject: [Haiku-bugs] [Haiku] #1711: Haiku stops booting at allocate_commpage_entry(4, 34) In-Reply-To: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> References: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> Message-ID: <048.06c84d08ffdd5a83e895be8e4894a126@haiku-os.org> #1711: Haiku stops booting at allocate_commpage_entry(4, 34) ----------------------------+----------------------------------------------- Reporter: euan | Owner: korli Type: bug | Status: new Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by dustin howett): r24424 fixed it for me. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 18 01:30:45 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 18 Mar 2008 00:30:45 -0000 Subject: [Haiku-bugs] [Haiku] #1711: Haiku stops booting at allocate_commpage_entry(4, 34) In-Reply-To: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> References: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> Message-ID: <048.87aa00c908c3987cd293ec98fbab1ac6@haiku-os.org> #1711: Haiku stops booting at allocate_commpage_entry(4, 34) ----------------------------+----------------------------------------------- Reporter: euan | Owner: korli Type: bug | Status: new Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by euan): Still no change for me (as of r24424) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 18 01:57:24 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 18 Mar 2008 00:57:24 -0000 Subject: [Haiku-bugs] [Haiku] #1119: The boot screen doesn't have "some" kind of animation to indicate system activity or inactivity. In-Reply-To: <043.a44eb8fd7200ec9aa2b979ec647deb3b@haiku-os.org> References: <043.a44eb8fd7200ec9aa2b979ec647deb3b@haiku-os.org> Message-ID: <052.2b3fcac1e4a7c385e1a5d259f6320697@haiku-os.org> #1119: The boot screen doesn't have "some" kind of animation to indicate system activity or inactivity. ----------------------------+----------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by aljen): fixed version, using resources generated from .pngs to headers/private/kernel/boot/images.h screenshot included (using example data) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 18 02:41:11 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 18 Mar 2008 01:41:11 -0000 Subject: [Haiku-bugs] [Haiku] #1711: Haiku stops booting at allocate_commpage_entry(4, 34) In-Reply-To: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> References: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> Message-ID: <048.46a9b79520b10717bc6c34d1d71bb187@haiku-os.org> #1711: Haiku stops booting at allocate_commpage_entry(4, 34) ----------------------------+----------------------------------------------- Reporter: euan | Owner: korli Type: bug | Status: new Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by euan): no hold that thought I see differences between the build on my laptop and desktop, even though they are at the same revision. Something must be wrong with my desktop svn repos. I'll wipe it and rebuild from scratch tomorrow... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 18 03:17:46 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 18 Mar 2008 02:17:46 -0000 Subject: [Haiku-bugs] [Haiku] #1931: Negative Modified Page Queue Count Message-ID: <043.fb44406a230138f185b83f0945b8f9c8@haiku-os.org> #1931: Negative Modified Page Queue Count ---------------------------+------------------------------------------------ Reporter: bonefish | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Platform: All | ---------------------------+------------------------------------------------ r24417, VMware While running a relatively harmless Perl test the page writer suddenly and unmotivatedly started to hog the CPU. As the attachment shows the count of the modified queue has become -1, which causes the semaphore acquisition to be skipped (sModifiedTemporaryPages is unsigned). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 18 03:40:27 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 18 Mar 2008 02:40:27 -0000 Subject: [Haiku-bugs] [Haiku] #1931: Negative Modified Page Queue Count In-Reply-To: <043.fb44406a230138f185b83f0945b8f9c8@haiku-os.org> References: <043.fb44406a230138f185b83f0945b8f9c8@haiku-os.org> Message-ID: <052.d55016556a359056158644592ebcc085@haiku-os.org> #1931: Negative Modified Page Queue Count ----------------------------+----------------------------------------------- Reporter: bonefish | Owner: axeld Type: bug | Status: closed Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: fixed | Platform: All ----------------------------+----------------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: Probably fixed in r24430. That race condition would be a good explanation at least. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 18 04:53:56 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 18 Mar 2008 03:53:56 -0000 Subject: [Haiku-bugs] [Haiku] #1932: QueryWatcher crashes on startup when running against a link to a query Message-ID: <039.fb323ed34e5a739978378cbce37254df@haiku-os.org> #1932: QueryWatcher crashes on startup when running against a link to a query ------------------------------+--------------------------------------------- Reporter: koki | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Storage Kit | Version: R1 development Platform: All | ------------------------------+--------------------------------------------- Testing QueryWatcher (QW) in r24424. QW is a little utility app that monitors queries stored in a particular folder (under config/settings), and shows their status in real time. When trying to run QW with a link to a query (as opposed to a query) in the above-mentioned folder, the app crashes upon startup. This does not happen in Zeta. To reproduce, place a link to a query in... /boot/home/config/settings/Nerd Herd Software/QueryWatcher ...and run QW. QW can be downloaded from here: http://www.bebits.com/app/3420 Backtrace attached -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 18 08:23:43 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 18 Mar 2008 07:23:43 -0000 Subject: [Haiku-bugs] [Haiku] #1119: The boot screen doesn't have "some" kind of animation to indicate system activity or inactivity. In-Reply-To: <043.a44eb8fd7200ec9aa2b979ec647deb3b@haiku-os.org> References: <043.a44eb8fd7200ec9aa2b979ec647deb3b@haiku-os.org> Message-ID: <052.596d673709017476b102bdaf42fa8c29@haiku-os.org> #1119: The boot screen doesn't have "some" kind of animation to indicate system activity or inactivity. ----------------------------+----------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by jackburton): That looks good! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 18 09:24:44 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 18 Mar 2008 08:24:44 -0000 Subject: [Haiku-bugs] [Haiku] #1119: The boot screen doesn't have "some" kind of animation to indicate system activity or inactivity. In-Reply-To: <043.a44eb8fd7200ec9aa2b979ec647deb3b@haiku-os.org> References: <043.a44eb8fd7200ec9aa2b979ec647deb3b@haiku-os.org> Message-ID: <052.52127c17c72875618fa34981f47582d4@haiku-os.org> #1119: The boot screen doesn't have "some" kind of animation to indicate system activity or inactivity. ----------------------------+----------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by mmlr): This indeed looks a lot better than the previous versions. But I have some observations: * You mixed in a darwin build fix which doesn't really belong to the rest of the patch * You left stray spaces on a otherwise blank line at least once (probably just a leftover) * The coding style generally looks good now, but you should also put two blank lines between functions * The terminating endif of the header guard in "splash.h" is missing * In "splash.cpp" you include a local "images.h" which doesn't exist * The "headers/private/kernel/boot/platform.h" prototype forplatform_switch_to_logo() is not up to date (probably left out of the diff?) Then it would be nice if the generator would write "0x%02x" instead of just "0x%x" so that the generated files have uniform lines. Otherwise this looks very nice, good work! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 18 09:28:06 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 18 Mar 2008 08:28:06 -0000 Subject: [Haiku-bugs] [Haiku] #1119: The boot screen doesn't have "some" kind of animation to indicate system activity or inactivity. In-Reply-To: <043.a44eb8fd7200ec9aa2b979ec647deb3b@haiku-os.org> References: <043.a44eb8fd7200ec9aa2b979ec647deb3b@haiku-os.org> Message-ID: <052.9eab3c3340a6b0bc09535297571e508f@haiku-os.org> #1119: The boot screen doesn't have "some" kind of animation to indicate system activity or inactivity. ----------------------------+----------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by jackburton): Replying to [comment:9 mmlr]: > This indeed looks a lot better than the previous versions. But I have some observations: Just to clarify: I meant it looks good purely from an aesthetic POV, I didn't even had a look at the code :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 18 10:02:22 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 18 Mar 2008 09:02:22 -0000 Subject: [Haiku-bugs] [Haiku] #1119: The boot screen doesn't have "some" kind of animation to indicate system activity or inactivity. In-Reply-To: <043.a44eb8fd7200ec9aa2b979ec647deb3b@haiku-os.org> References: <043.a44eb8fd7200ec9aa2b979ec647deb3b@haiku-os.org> Message-ID: <052.95950a48053c304d9c9b7e657f88eabe@haiku-os.org> #1119: The boot screen doesn't have "some" kind of animation to indicate system activity or inactivity. ----------------------------+----------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by axeld): I wrote this while mmlr wrote his comment, so there might be some duplicate comments: There are still a number of problems with this patch: * It does not seem to be complete, at least bios_ia32/video.cpp looks like it would not compile (maybe a leftover from a previous version?). * It contains stuff that doesn't belong into that patch (ie. src/tools/fs_shell/unistd.cpp). If that's needed to let Haiku build on Mac OS X, please provide a separate patch for this. * You're mapping the frame buffer twice; it is already mapped in debug/frame_buffer_console.cpp, and that one can and should be reused. * The coding style demands a prefix for const variables, and that should also be honoured in the images your hbsg app creates (since that app is separated, I guess we can live with the style violations there ;-)) Other than that, it looks pretty nice this time (the patch, not the example images, but that's just my personal taste). Thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 18 10:58:03 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 18 Mar 2008 09:58:03 -0000 Subject: [Haiku-bugs] [Haiku] #1820: [DataTranslations] Scrollbar don't move on End key press In-Reply-To: <040.5f752054ecf723e47469863bb7570dab@haiku-os.org> References: <040.5f752054ecf723e47469863bb7570dab@haiku-os.org> Message-ID: <049.e528b7bd40a1e54e38ecd05afe670d81@haiku-os.org> #1820: [DataTranslations] Scrollbar don't move on End key press ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: invalid | Platform: All ---------------------------------+------------------------------------------ Changes (by jackburton): * status: new => closed * resolution: => invalid Comment: I'll mark this as invalid as it's working. Maybe it simply got fixed in the meantime, though :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 18 11:01:17 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 18 Mar 2008 10:01:17 -0000 Subject: [Haiku-bugs] [Haiku] #1119: The boot screen doesn't have "some" kind of animation to indicate system activity or inactivity. In-Reply-To: <043.a44eb8fd7200ec9aa2b979ec647deb3b@haiku-os.org> References: <043.a44eb8fd7200ec9aa2b979ec647deb3b@haiku-os.org> Message-ID: <052.339bbb211844529aa938d62ec1d92acd@haiku-os.org> #1119: The boot screen doesn't have "some" kind of animation to indicate system activity or inactivity. ----------------------------+----------------------------------------------- Reporter: kaoutsis | Owner: stippi Type: enhancement | Status: assigned Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Changes (by stippi): * owner: axeld => stippi * status: new => assigned Comment: In general, the patch looks very good though and it does fix the problem of the outdated logo + has the bonus of animating the boot screen! :-) So I am currently looking into applying this patch, with the needed fixes as pointed out by Axel and Michael. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 18 11:04:01 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 18 Mar 2008 10:04:01 -0000 Subject: [Haiku-bugs] [Haiku] #1850: [Twitcher] have greenish background under icons In-Reply-To: <040.5b327f2a81ba9cf6ca76dcf0f9a0e7f8@haiku-os.org> References: <040.5b327f2a81ba9cf6ca76dcf0f9a0e7f8@haiku-os.org> Message-ID: <049.d7a26ec09a5f56be56544362387f2715@haiku-os.org> #1850: [Twitcher] have greenish background under icons -----------------------------------+---------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Deskbar | Version: R1 development Resolution: | Platform: All -----------------------------------+---------------------------------------- Changes (by jackburton): * summary: [Twitcher] have green background under icons => [Twitcher] have greenish background under icons -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 18 11:25:38 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 18 Mar 2008 10:25:38 -0000 Subject: [Haiku-bugs] [Haiku] #724: Tracker and Terminal unable to delete files with non-ascii filenames In-Reply-To: <058.44e586d5bfc0f2bb2424ec21e4ecf98e@haiku-os.org> References: <058.44e586d5bfc0f2bb2424ec21e4ecf98e@haiku-os.org> Message-ID: <067.1e2baf86197008dcc92d70558a63b9d6@haiku-os.org> #724: Tracker and Terminal unable to delete files with non-ascii filenames --------------------------------------+------------------------------------- Reporter: info at haiku-security.com | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: Resolution: | Platform: All --------------------------------------+------------------------------------- Changes (by jackburton): * platform: => All Comment: Another way to reproduce: Grab the weekly super pack vmware image from haikuware, mount it from your own haiku image, and delete the Wonderbrush directory. Then empty the trash. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 18 11:29:48 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 18 Mar 2008 10:29:48 -0000 Subject: [Haiku-bugs] [Haiku] #1119: The boot screen doesn't have "some" kind of animation to indicate system activity or inactivity. In-Reply-To: <043.a44eb8fd7200ec9aa2b979ec647deb3b@haiku-os.org> References: <043.a44eb8fd7200ec9aa2b979ec647deb3b@haiku-os.org> Message-ID: <052.69fd6ec9116bdb2959768c5ca90f3762@haiku-os.org> #1119: The boot screen doesn't have "some" kind of animation to indicate system activity or inactivity. ----------------------------+----------------------------------------------- Reporter: kaoutsis | Owner: stippi Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Platform: All ----------------------------+----------------------------------------------- Changes (by stippi): * status: assigned => closed * resolution: => fixed Comment: Hi Artur, thank you very much for your work. I have applied everything in separate patches, but ultimately in r24434. Please have a look at my commit comments, maybe you would like to work on some of the TODOs I pointed out? Thanks again! As far as this bug goes, I consider it fixed, despite the room for improvement (build system integration, removal of hardcoded values...). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 18 11:43:36 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 18 Mar 2008 10:43:36 -0000 Subject: [Haiku-bugs] [Haiku] #1820: [DataTranslations] Scrollbar don't move on End key press In-Reply-To: <040.5f752054ecf723e47469863bb7570dab@haiku-os.org> References: <040.5f752054ecf723e47469863bb7570dab@haiku-os.org> Message-ID: <049.0654e3564f6801d3f6da21d5e9f9042d@haiku-os.org> #1820: [DataTranslations] Scrollbar don't move on End key press ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by diver): * status: closed => reopened * resolution: invalid => Comment: Yeah, WonderBrush Translator is shown fully now, but a problem with not movable scrollbar is still here in r24424. Reopening... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 18 11:47:04 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 18 Mar 2008 10:47:04 -0000 Subject: [Haiku-bugs] [Haiku] #1820: [DataTranslations] Scrollbar don't move on End key press In-Reply-To: <040.5f752054ecf723e47469863bb7570dab@haiku-os.org> References: <040.5f752054ecf723e47469863bb7570dab@haiku-os.org> Message-ID: <049.b685262d7330a85792e9e67d5e0c938c@haiku-os.org> #1820: [DataTranslations] Scrollbar don't move on End key press ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by jackburton): Replying to [comment:2 diver]: > Yeah, WonderBrush Translator is shown fully now, but a problem with not movable scrollbar is still here in r24424. Reopening... Can you explain the steps to reproduce ? Here's how I verified that the scrollbar is moving correctly: - Set the font size to 13, so the Translators list doesn't fit into the window - Open DataTranslation - Hit "End". -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 18 11:56:24 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 18 Mar 2008 10:56:24 -0000 Subject: [Haiku-bugs] [Haiku] #1820: [DataTranslations] Scrollbar don't move on End key press In-Reply-To: <040.5f752054ecf723e47469863bb7570dab@haiku-os.org> References: <040.5f752054ecf723e47469863bb7570dab@haiku-os.org> Message-ID: <049.53b92c43e268584a1a56aeafe718bc94@haiku-os.org> #1820: [DataTranslations] Scrollbar don't move on End key press ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by diver): I use default font and font size. When i open DataTranslation i see a little space in the bottom of scrollbar. I expect scrollbar to move down to this space when I hitting "End". -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 18 12:59:10 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 18 Mar 2008 11:59:10 -0000 Subject: [Haiku-bugs] [Haiku] #1933: Design and Implement a Layered File System Extension Architecture Message-ID: <043.1d00aef48aedb0fd3d29bfb8e930fab2@haiku-os.org> #1933: Design and Implement a Layered File System Extension Architecture ---------------------------+------------------------------------------------ Reporter: bonefish | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Platform: All | ---------------------------+------------------------------------------------ Design and implement an architecture to transparently extend the capabilities of file systems. It should make the following features possible: - Add BeOS attributes and query support to non-BeOS/Haiku-native FSs. - Add write support (using volatile storage like memory) to read-only FSs (e.g. ISO9660) or FSs residing on read-only media. - Add features like data encryption to any FS. Those extensions should be pluggable in layers, i.e. it should be possible to extend a ISO9660 FS by attributes, write support, and encryption at the same time. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 18 13:47:29 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 18 Mar 2008 12:47:29 -0000 Subject: [Haiku-bugs] [Haiku] #1107: [StyledEdit] Loading a 500 kbytes syslog file is more than 20 times slower under Haiku In-Reply-To: <038.e5304fce774038edb649654ec8eacbfd@haiku-os.org> References: <038.e5304fce774038edb649654ec8eacbfd@haiku-os.org> Message-ID: <047.402301d50895fe3b2ca158f70e4257ae@haiku-os.org> #1107: [StyledEdit] Loading a 500 kbytes syslog file is more than 20 times slower under Haiku --------------------------------------+------------------------------------- Reporter: oco | Owner: Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Applications/StyledEdit | Version: R1 development Resolution: fixed | Platform: All --------------------------------------+------------------------------------- Changes (by jackburton): * status: new => closed * resolution: => fixed -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 18 13:53:18 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 18 Mar 2008 12:53:18 -0000 Subject: [Haiku-bugs] [Haiku] #1089: Appearance doesn't do anything In-Reply-To: <045.8fc93b7c8f106d428a0d5bebbd6b73d6@haiku-os.org> References: <045.8fc93b7c8f106d428a0d5bebbd6b73d6@haiku-os.org> Message-ID: <054.466d0cbeb62a0a1fdcafd993bf3321aa@haiku-os.org> #1089: Appearance doesn't do anything -------------------------------------+-------------------------------------- Reporter: jackburton | Owner: darkwyrm Type: bug | Status: new Priority: normal | Milestone: R1 Component: Preferences/Appearance | Version: R1 development Resolution: | Platform: All -------------------------------------+-------------------------------------- Comment (by jackburton): AFAIK appearance now works a bit more. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 18 14:20:25 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 18 Mar 2008 13:20:25 -0000 Subject: [Haiku-bugs] [Haiku] #1268: Incorporation of the well known live cd scripts in the build. In-Reply-To: <043.0ec3b288215ac8d81edd1780fc68e6bc@haiku-os.org> References: <043.0ec3b288215ac8d81edd1780fc68e6bc@haiku-os.org> Message-ID: <052.a2df55a97613de9bd7efb68e22270f89@haiku-os.org> #1268: Incorporation of the well known live cd scripts in the build. ---------------------------+------------------------------------------------ Reporter: kaoutsis | Owner: mmu_man Type: enhancement | Status: new Priority: blocker | Milestone: R1/alpha1 Component: Build System | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by jackburton): Can we close this one now ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 18 14:21:39 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 18 Mar 2008 13:21:39 -0000 Subject: [Haiku-bugs] [Haiku] #1934: tcpdump is broken. Message-ID: <038.551535fe70f75fd4c1d0b0eb8fc9c911@haiku-os.org> #1934: tcpdump is broken. --------------------------------------+------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Platform: x86 | --------------------------------------+------------------------------------- Running tcpdump with any options results in it printint a line like this: tcpdump: After that, it exists immediately. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 18 14:43:02 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 18 Mar 2008 13:43:02 -0000 Subject: [Haiku-bugs] [Haiku] #1466: GUI doesn't redraw / freezes In-Reply-To: <050.092965f6d638178942edd6f63de6458f@haiku-os.org> References: <050.092965f6d638178942edd6f63de6458f@haiku-os.org> Message-ID: <059.bce6464e38f83c98816188ff142e6786@haiku-os.org> #1466: GUI doesn't redraw / freezes ---------------------------------+------------------------------------------ Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by jackburton): There was a problem with _BWidthBuffer_, used by Tracker's PoseView, which could've caused this problem. It was was fixed in r24096. I can't reproduce this problem anymore. Can someone confirm ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 18 14:51:29 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 18 Mar 2008 13:51:29 -0000 Subject: [Haiku-bugs] [Haiku] #1307: [MediaPlayer] jumping on screen In-Reply-To: <040.d78f5030e9cf4e660b14da1d3ff4ab0d@haiku-os.org> References: <040.d78f5030e9cf4e660b14da1d3ff4ab0d@haiku-os.org> Message-ID: <049.2c469edb070a9b7de0fab2f39b122343@haiku-os.org> #1307: [MediaPlayer] jumping on screen ---------------------------------+------------------------------------------ Reporter: diver | Owner: stippi Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by jackburton): Replying to [comment:1 diver]: > Same thing happens with LaunchBox btw. Indeed, but only if you grab it around using the "grippy". IOW: Dragging it around using the window tab works fine instead. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 18 15:06:46 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 18 Mar 2008 14:06:46 -0000 Subject: [Haiku-bugs] [Haiku] #1934: tcpdump is broken. In-Reply-To: <038.551535fe70f75fd4c1d0b0eb8fc9c911@haiku-os.org> References: <038.551535fe70f75fd4c1d0b0eb8fc9c911@haiku-os.org> Message-ID: <047.f6b57c5bb5f5c54f84ff8ea96f759fba@haiku-os.org> #1934: tcpdump is broken. ---------------------------------------+------------------------------------ Reporter: bga | Owner: axeld Type: bug | Status: new Priority: low | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Resolution: | Platform: x86 ---------------------------------------+------------------------------------ Changes (by axeld): * priority: normal => low Comment: You're supposed to call it using the '-i' option like this: $ tcpdump -i /dev/net/ipro1000/0 When you don't specify anything, it's supposed to take the first interface, and that's obviously not working. I don't know why it doesn't print an error in this case; I think this might be a bug in tcpdump itself. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 18 15:09:44 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 18 Mar 2008 14:09:44 -0000 Subject: [Haiku-bugs] [Haiku] #1934: tcpdump is broken. In-Reply-To: <038.551535fe70f75fd4c1d0b0eb8fc9c911@haiku-os.org> References: <038.551535fe70f75fd4c1d0b0eb8fc9c911@haiku-os.org> Message-ID: <047.9468c596d692231da94c10aabd674295@haiku-os.org> #1934: tcpdump is broken. ---------------------------------------+------------------------------------ Reporter: bga | Owner: axeld Type: bug | Status: new Priority: low | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Resolution: | Platform: x86 ---------------------------------------+------------------------------------ Comment (by bga): As I said, tcpdump with any options just prints "tcpdump:" and exists. This includes: tcpdump -i /dev/net/ipro1000/0 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 18 15:11:05 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 18 Mar 2008 14:11:05 -0000 Subject: [Haiku-bugs] [Haiku] #1934: tcpdump is broken. In-Reply-To: <038.551535fe70f75fd4c1d0b0eb8fc9c911@haiku-os.org> References: <038.551535fe70f75fd4c1d0b0eb8fc9c911@haiku-os.org> Message-ID: <047.224b8c7eb0cfda9a9b1550cc1e942103@haiku-os.org> #1934: tcpdump is broken. ---------------------------------------+------------------------------------ Reporter: bga | Owner: axeld Type: bug | Status: new Priority: low | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Resolution: | Platform: x86 ---------------------------------------+------------------------------------ Comment (by bga): I mean "exits", not "exists". :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 18 15:32:43 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 18 Mar 2008 14:32:43 -0000 Subject: [Haiku-bugs] [Haiku] #1268: Incorporation of the well known live cd scripts in the build. In-Reply-To: <043.0ec3b288215ac8d81edd1780fc68e6bc@haiku-os.org> References: <043.0ec3b288215ac8d81edd1780fc68e6bc@haiku-os.org> Message-ID: <052.a569e72a5902112ad548f76e7d2e65d7@haiku-os.org> #1268: Incorporation of the well known live cd scripts in the build. ---------------------------+------------------------------------------------ Reporter: kaoutsis | Owner: mmu_man Type: enhancement | Status: new Priority: blocker | Milestone: R1/alpha1 Component: Build System | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by mmu_man): Replying to [comment:14 kaoutsis]: > Replying to [comment:13 mmu_man]: > > No it's not, it's the second track of the CD. > ok, thanks; how can i verify that is there (the haiku.image)? > i mount the dvd and i see: > /dev/hdc 1808 1808 0 100% /media/cdrom0 That's the first track, the ISO one. As the 2nd one is BFS I'm not sure how linux will see it... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 18 15:33:56 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 18 Mar 2008 14:33:56 -0000 Subject: [Haiku-bugs] [Haiku] #1268: Incorporation of the well known live cd scripts in the build. In-Reply-To: <043.0ec3b288215ac8d81edd1780fc68e6bc@haiku-os.org> References: <043.0ec3b288215ac8d81edd1780fc68e6bc@haiku-os.org> Message-ID: <052.628714d77e9d4b51d23623369028e984@haiku-os.org> #1268: Incorporation of the well known live cd scripts in the build. ---------------------------+------------------------------------------------ Reporter: kaoutsis | Owner: mmu_man Type: enhancement | Status: closed Priority: blocker | Milestone: R1/alpha1 Component: Build System | Version: R1 development Resolution: fixed | Platform: All ---------------------------+------------------------------------------------ Changes (by mmu_man): * status: new => closed * resolution: => fixed Comment: Replying to [comment:15 jackburton]: > Can we close this one now ? I think so. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 18 15:39:58 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 18 Mar 2008 14:39:58 -0000 Subject: [Haiku-bugs] [Haiku] #1934: tcpdump is broken. In-Reply-To: <038.551535fe70f75fd4c1d0b0eb8fc9c911@haiku-os.org> References: <038.551535fe70f75fd4c1d0b0eb8fc9c911@haiku-os.org> Message-ID: <047.337d0d26ece930af89b0e2fcb5a53b0d@haiku-os.org> #1934: tcpdump is broken. ---------------------------------------+------------------------------------ Reporter: bga | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Resolution: | Platform: x86 ---------------------------------------+------------------------------------ Changes (by axeld): * priority: low => normal Comment: Ah, I thought that you wanted to say "without" instead. The problem I thought you meant is fixed in r24441. It didn't print an error because I didn't return one :-) "tcpdump" works fine here, and I can't reproduce this, if any error remains. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 18 17:12:46 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 18 Mar 2008 16:12:46 -0000 Subject: [Haiku-bugs] [Haiku] #1932: QueryWatcher crashes on startup when running against a link to a query In-Reply-To: <039.fb323ed34e5a739978378cbce37254df@haiku-os.org> References: <039.fb323ed34e5a739978378cbce37254df@haiku-os.org> Message-ID: <048.7cd001ed67debc45782d0a2c7ea38015@haiku-os.org> #1932: QueryWatcher crashes on startup when running against a link to a query ----------------------------+----------------------------------------------- Reporter: koki | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Platform: All ----------------------------+----------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed * component: Kits/Storage Kit => System/Kernel Comment: Fixed in r24442. The crash is a bug in the application, but it was triggered by Haiku not traversing symlinks when using entry_refs. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 18 18:21:55 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 18 Mar 2008 17:21:55 -0000 Subject: [Haiku-bugs] [Haiku] #1935: Implement Real-Time Signal Support Message-ID: <043.3dc2e28c11edbc2d20b8a9c086e58864@haiku-os.org> #1935: Implement Real-Time Signal Support ---------------------------+------------------------------------------------ Reporter: bonefish | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Platform: All | ---------------------------+------------------------------------------------ This includes among other things implementing sigqueue() and the SA_SIGINFO flag of sigaction(). Cf.: http://www.opengroup.org/onlinepubs/009695399/functions/xsh_chap02_04.html#tag_02_04_02 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 18 18:25:45 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 18 Mar 2008 17:25:45 -0000 Subject: [Haiku-bugs] [Haiku] #1925: Reboot during startup on Toshiba Satellite 2615DVD/6.0 In-Reply-To: <046.464cc1a60522972f4d6a4db8a13a4bd4@haiku-os.org> References: <046.464cc1a60522972f4d6a4db8a13a4bd4@haiku-os.org> Message-ID: <055.ccae576c718d6a413aa1d388a5a35c0b@haiku-os.org> #1925: Reboot during startup on Toshiba Satellite 2615DVD/6.0 ----------------------------+----------------------------------------------- Reporter: umccullough | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by umccullough): I was unable to find any BIOS options that would change the behavior. (The Toshiba BIOS on this laptop is amazingly stupid). I suppose it's time for me to start adding some trace code to find where it fails - any recommendations on where to start based on the attached serial log? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 18 18:30:02 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 18 Mar 2008 17:30:02 -0000 Subject: [Haiku-bugs] [Haiku] #1935: Implement Real-Time Signal Support In-Reply-To: <043.3dc2e28c11edbc2d20b8a9c086e58864@haiku-os.org> References: <043.3dc2e28c11edbc2d20b8a9c086e58864@haiku-os.org> Message-ID: <052.c67f1f28dcff972b98d62b8de26a7ae4@haiku-os.org> #1935: Implement Real-Time Signal Support ----------------------------+----------------------------------------------- Reporter: bonefish | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Old description: > This includes among other things implementing sigqueue() and the > SA_SIGINFO flag of sigaction(). > > Cf.: > http://www.opengroup.org/onlinepubs/009695399/functions/xsh_chap02_04.html#tag_02_04_02 New description: This includes among other things implementing: - sigqueue() - the SA_SIGINFO flag of sigaction() - waitid() Cf.: http://www.opengroup.org/onlinepubs/009695399/functions/xsh_chap02_04.html#tag_02_04_02 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 18 18:39:24 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 18 Mar 2008 17:39:24 -0000 Subject: [Haiku-bugs] [Haiku] #1932: QueryWatcher crashes on startup when running against a link to a query In-Reply-To: <039.fb323ed34e5a739978378cbce37254df@haiku-os.org> References: <039.fb323ed34e5a739978378cbce37254df@haiku-os.org> Message-ID: <048.dd51664714065fba9f585bd168d91647@haiku-os.org> #1932: QueryWatcher crashes on startup when running against a link to a query ----------------------------+----------------------------------------------- Reporter: koki | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Platform: All ----------------------------+----------------------------------------------- Comment (by koki): Thanks Axel! Have not tested it yet, but will do as soon as a fixed revision shows up on the build archive. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 18 18:57:48 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 18 Mar 2008 17:57:48 -0000 Subject: [Haiku-bugs] [Haiku] #1119: The boot screen doesn't have "some" kind of animation to indicate system activity or inactivity. In-Reply-To: <043.a44eb8fd7200ec9aa2b979ec647deb3b@haiku-os.org> References: <043.a44eb8fd7200ec9aa2b979ec647deb3b@haiku-os.org> Message-ID: <052.f7258653d8d21266d8a60cc009b72dae@haiku-os.org> #1119: The boot screen doesn't have "some" kind of animation to indicate system activity or inactivity. ----------------------------+----------------------------------------------- Reporter: kaoutsis | Owner: stippi Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Platform: All ----------------------------+----------------------------------------------- Comment (by stippi): Artur, I hope it's not too late. I am currently working generate_boot_screen and the splash.cpp. I need it all to support 32 bit artwork. The way it handles palettes cannot work right. I mean, I want the artwork to be in the best possible quality to begin with, so that means 24 bit RGB data. For the case that the VGA device can only run in 8 bit palette mode, I want to handle that too, but this is a case that the code currently does not support either. I am on it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 18 20:50:23 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 18 Mar 2008 19:50:23 -0000 Subject: [Haiku-bugs] [Haiku] #1936: 24423 broke networking Message-ID: <039.fa3291b6c5808bc8048d36db4c8a9975@haiku-os.org> #1936: 24423 broke networking -------------------------------------+-------------------------------------- Reporter: ddew | Owner: zooey Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet/IPv4 | Version: R1 development Platform: x86 | -------------------------------------+-------------------------------------- I can't get the interface working. I've setup a static ip, default router etc but i keep getting a network unreachable error. The card is an intel eepro100 and works fine with 24422. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 18 21:05:44 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 18 Mar 2008 20:05:44 -0000 Subject: [Haiku-bugs] [Haiku] #724: Tracker and Terminal unable to delete files with non-ascii filenames In-Reply-To: <058.44e586d5bfc0f2bb2424ec21e4ecf98e@haiku-os.org> References: <058.44e586d5bfc0f2bb2424ec21e4ecf98e@haiku-os.org> Message-ID: <067.ba6e841c5d5b621119a000ab92674eb8@haiku-os.org> #724: Tracker and Terminal unable to delete files with non-ascii filenames --------------------------------------+------------------------------------- Reporter: info at haiku-security.com | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: Resolution: | Platform: All --------------------------------------+------------------------------------- Comment (by axeld): Great, thanks Stefano! I can finally reproduce this problem! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 18 22:02:34 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 18 Mar 2008 21:02:34 -0000 Subject: [Haiku-bugs] [Haiku] #1711: Haiku stops booting at allocate_commpage_entry(4, 34) In-Reply-To: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> References: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> Message-ID: <048.910936af17ef63d64d867ef576dadc53@haiku-os.org> #1711: Haiku stops booting at allocate_commpage_entry(4, 34) ----------------------------+----------------------------------------------- Reporter: euan | Owner: korli Type: bug | Status: new Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by euan): Everything works now. It was probably fixed for me on the first mtrr change. Sadly my svn repos was a bit knackered. I only noticed when the new boot splash logos didn't appear... Thanks very much for the fix. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 18 22:12:24 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 18 Mar 2008 21:12:24 -0000 Subject: [Haiku-bugs] [Haiku] #1711: Haiku stops booting at allocate_commpage_entry(4, 34) In-Reply-To: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> References: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> Message-ID: <048.ec2199029635c8925c842a9b940954cd@haiku-os.org> #1711: Haiku stops booting at allocate_commpage_entry(4, 34) ----------------------------+----------------------------------------------- Reporter: euan | Owner: korli Type: bug | Status: closed Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Platform: All ----------------------------+----------------------------------------------- Changes (by korli): * status: new => closed * resolution: => fixed Comment: Thank both of you for your feedback. Fixed in r24424. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 18 22:16:22 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 18 Mar 2008 21:16:22 -0000 Subject: [Haiku-bugs] [Haiku] #724: Tracker and Terminal unable to delete files with non-ascii filenames In-Reply-To: <058.44e586d5bfc0f2bb2424ec21e4ecf98e@haiku-os.org> References: <058.44e586d5bfc0f2bb2424ec21e4ecf98e@haiku-os.org> Message-ID: <067.037fef1102f49c8efb37fde9db4c6f0a@haiku-os.org> #724: Tracker and Terminal unable to delete files with non-ascii filenames --------------------------------------+------------------------------------- Reporter: info at haiku-security.com | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: Resolution: | Platform: All --------------------------------------+------------------------------------- Changes (by siarzhuk): * cc: siarzhuk (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 19 02:12:29 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 19 Mar 2008 01:12:29 -0000 Subject: [Haiku-bugs] [Haiku] #1937: libroot: malloc bug - Thread 7445 called debugger(): _numBlocks > 0 Message-ID: <040.96a04433cdbba2b96e60fd80b4cc61a4@haiku-os.org> #1937: libroot: malloc bug - Thread 7445 called debugger(): _numBlocks > 0 -------------------------------+-------------------------------------------- Reporter: thorn | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Platform: x86 | -------------------------------+-------------------------------------------- env: haiku - r24413 texinfo-4.11 / makeinfo backtrace: {{{ This GDB was configured as "i586-pc-haiku"... [tcsetpgrp failed in terminal_inferior: Invalid Argument] Thread 7445 called debugger(): _numBlocks > 0 Reading symbols from /boot/beos/system/lib/libroot.so...done. Loaded symbols for /boot/beos/system/lib/libroot.so [tcsetpgrp failed in terminal_inferior: Invalid Argument] [Switching to team makeinfo -I. ./autoconf.texi --no-split --output=autoconf.info (7445) thread makeinfo (7445)] 0xffff0104 in ?? () (gdb) bt full #0 0xffff0104 in ?? () No symbol table info available. #1 0x0026d326 in debugger () from /boot/beos/system/lib/libroot.so No symbol table info available. #2 0x00274491 in __assert_fail () from /boot/beos/system/lib/libroot.so No symbol table info available. #3 0x0027c84c in BPrivate::superblock::isValid () from /boot/beos/system/lib/libroot.so No symbol table info available. #4 0x0027ac6c in BPrivate::threadHeap::malloc () from /boot/beos/system/lib/libroot.so No symbol table info available. #5 0x0027b8c1 in malloc () from /boot/beos/system/lib/libroot.so No symbol table info available. #6 0x002371d0 in xmalloc (n=24) at xmalloc.c:50 p = (void *) 0x9c #7 0x00225e8e in remember_brace_1 (proc=0x20dcf8 , position=8) at makeinfo.c:2337 new = (struct brace_element *) 0x248a14 #8 0x00225f7d in remember_brace (proc=0x20dcf8 ) at makeinfo.c:2354 No locals. #9 0x002255ab in read_command () at makeinfo.c:2075 entry = (struct {...} *) 0x245cbc old_text_offset = 86164 }}} and source: {{{ void * xmalloc (size_t n) { void *p = malloc (n); if (!p && n != 0) xalloc_die (); return p; } }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 19 02:15:08 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 19 Mar 2008 01:15:08 -0000 Subject: [Haiku-bugs] [Haiku] #1937: libroot: malloc bug - Thread 7445 called debugger(): _numBlocks > 0 In-Reply-To: <040.96a04433cdbba2b96e60fd80b4cc61a4@haiku-os.org> References: <040.96a04433cdbba2b96e60fd80b4cc61a4@haiku-os.org> Message-ID: <049.425a78d1f125beae246084d6c9382299@haiku-os.org> #1937: libroot: malloc bug - Thread 7445 called debugger(): _numBlocks > 0 --------------------------------+------------------------------------------- Reporter: thorn | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Resolution: | Platform: x86 --------------------------------+------------------------------------------- Comment (by thorn): like #679 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 19 02:21:34 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 19 Mar 2008 01:21:34 -0000 Subject: [Haiku-bugs] [Haiku] #1938: libroot: free bug - Segment violation Message-ID: <040.119952edd4c2fc54e34694964337fe1e@haiku-os.org> #1938: libroot: free bug - Segment violation -------------------------------+-------------------------------------------- Reporter: thorn | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Platform: x86 | -------------------------------+-------------------------------------------- env: haiku r24413 texinfo-4.11 / makeinfo backtrace: {{{ This GDB was configured as "i586-pc-haiku"... [tcsetpgrp failed in terminal_inferior: Invalid Argument] Thread 7323 caused an exception: Segment violation Reading symbols from /boot/beos/system/lib/libroot.so...done. Loaded symbols for /boot/beos/system/lib/libroot.so [tcsetpgrp failed in terminal_inferior: Invalid Argument] [Switching to team ../makeinfo --html -I./../../doc -I../../doc --no-split ./../.. (7323) thread makeinfo (7323)] 0x0027289c in atomic_test_and_set () from /boot/beos/system/lib/libroot.so (gdb) bt full #0 0x0027289c in atomic_test_and_set () from /boot/beos/system/lib/libroot.so No symbol table info available. #1 0x00276d85 in BPrivate::hoardLock () from /boot/beos/system/lib/libroot.so No symbol table info available. #2 0x0027a406 in BPrivate::processHeap::free () from /boot/beos/system/lib/libroot.so No symbol table info available. #3 0x0027bb08 in free () from /boot/beos/system/lib/libroot.so No symbol table info available. #4 0x00229846 in getdocumenttext (msgid=0x23e447 "Up:") at makeinfo.c:4348 tmp = 0x0 old_LC_ALL = 0x0 old_LANGUAGE = 0x0 result = 0x23e447 "Up:" old_locale = 0x1802bf00 "C" #5 0x0022d0b8 in cm_node () at node.c:1021 epilogue_len = 0 node = 0x1800f548 "Help-FOO" prev = 0x0 next = 0x0 up = 0x1802bef0 "Help-M" new_node_pos = 35337 defaulting = 0 this_section = 4 }}} source: {{{ char* old_locale; .. setlocale (LC_ALL, old_locale); free (old_locale); }}} serial log: {{{ vm_soft_fault: va 0x398 not covered by area in address space vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x398, ip 0x27289c, write 1, user 1, thread 0x1c9b vm_page_fault: sending team "makeinfo" 0x1c9b SIGSEGV, ip 0x27289c ("libroot.so_seg0ro" +0x2289c) stack trace: 0x0027a406 (libroot.so_seg0ro + 0x2a406) 0x0027bb08 (libroot.so_seg0ro + 0x2bb08) 0x00229846 (makeinfo_seg0ro + 0x29846) 0x0022d0b8 (makeinfo_seg0ro + 0x2d0b8) 0x00225718 (makeinfo_seg0ro + 0x25718) 0x00225d35 (makeinfo_seg0ro + 0x25d35) 0x0022482a (makeinfo_seg0ro + 0x2482a) 0x00223cef (makeinfo_seg0ro + 0x23cef) 0x00222ce2 (makeinfo_seg0ro + 0x22ce2) 0x0020c5e5 (makeinfo_seg0ro + 0xc5e5) 0x001007ca (runtime_loader_seg0ro + 0x7ca) 0x7ffe6fec (makeinfo_main_stack + 0xffffec) vm_soft_fault: va 0x0 not covered by area in address space vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x0, ip 0x80092ae8, write 0, user 0, thread 0x1c9b debug_server: Thread 7323 entered the debugger: Segment violation stack trace, current PC 0x27289c atomic_test_and_set + 0xc (closest symbol): (0x7ffe6924) 0x27a406 free__Q28BPrivate11processHeapPv + 0x17a (0x7ffe6964) 0x27bb08 free + 0xa0 (0x7ffe6994) 0x229846 getdocumenttext + 0x1ae (0x7ffe69d4) 0x22d0b8 cm_node + 0x1294 (0x7ffe6e70) 0x225718 init_paragraph + 0x844 (closest symbol) (0x7ffe6eb0) 0x225d35 reader_loop + 0x609 (0x7ffe6ee0) 0x22482a reverse_list + 0xe5a (closest symbol) (0x7ffe6f10) 0x223cef reverse_list + 0x31f (closest symbol) (0x7ffe6f40) 0x222ce2 main + 0xf5e (0x7ffe6f80) 0x20c5e5 _start + 0x61 (0x7ffe6fac) 0x1007ca (runtime_loader_seg0ro + 0x7ca) }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 19 02:28:07 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 19 Mar 2008 01:28:07 -0000 Subject: [Haiku-bugs] [Haiku] #1939: chart demo crashes when moved around Message-ID: <049.3e2bd489cab20a7321e2a9ec7e5f7db7@haiku-os.org> #1939: chart demo crashes when moved around ----------------------------+----------------------------------------------- Reporter: the ringmaster | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | ----------------------------+----------------------------------------------- How to reproduce: This is recreated by setting the animation to fast movement, setting the display to directwindow and selecting two threads. You then move the window around the screen (especially to areas beyond the screen) and the app will crash. Experienced behavior: Application crashes Expected behavior: Application redraws nicely. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 19 02:29:12 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 19 Mar 2008 01:29:12 -0000 Subject: [Haiku-bugs] [Haiku] #1938: libroot: free bug - Segment violation In-Reply-To: <040.119952edd4c2fc54e34694964337fe1e@haiku-os.org> References: <040.119952edd4c2fc54e34694964337fe1e@haiku-os.org> Message-ID: <049.ff43cd71d260e2c1aad4285ccb1724fd@haiku-os.org> #1938: libroot: free bug - Segment violation --------------------------------+------------------------------------------- Reporter: thorn | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Resolution: | Platform: x86 --------------------------------+------------------------------------------- Comment (by thorn): dublicate #1896 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 19 02:32:31 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 19 Mar 2008 01:32:31 -0000 Subject: [Haiku-bugs] [Haiku] #1896: libroot: free bug (was: /bin/bc crash) In-Reply-To: <040.da90fc9f8a86a95338db1a65efec1ae9@haiku-os.org> References: <040.da90fc9f8a86a95338db1a65efec1ae9@haiku-os.org> Message-ID: <049.8fa44eb82eb167d3fdd8df9b7d32f541@haiku-os.org> #1896: libroot: free bug (was: /bin/bc crash) --------------------------------+------------------------------------------- Reporter: thorn | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Resolution: | Platform: x86 --------------------------------+------------------------------------------- Changes (by thorn): * component: Applications => System/libroot.so * summary: /bin/bc crash => libroot: free bug (was: /bin/bc crash) Comment: '''easily replicable ''' serial log: {{{ vm_soft_fault: va 0xd01800e7 not covered by area in address space vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0xd01800e7, ip 0x23e2f2, write 0, user 1, thread 0x1d50 vm_page_fault: sending team "bc" 0x1d50 SIGSEGV, ip 0x23e2f2 ("libroot.so_seg0ro" +0x2a2f2) stack trace: 0x0023fb08 (libroot.so_seg0ro + 0x2bb08) 0x0020455e (bc_seg0ro + 0x455e) 0x00202e85 (bc_seg0ro + 0x2e85) 0x00202953 (bc_seg0ro + 0x2953) 0x001007ca (runtime_loader_seg0ro + 0x7ca) 0x7ffe6fec (bc_main_stack + 0xffffec) vm_soft_fault: va 0x0 not covered by area in address space vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x0, ip 0x80092ae8, write 0, user 0, thread 0x1d50 debug_server: Thread 7504 entered the debugger: Segment violation stack trace, current PC 0x23e2f2 free__Q28BPrivate11processHeapPv + 0x66: (0x7ffe69ac) 0x23fb08 free + 0xa0 (0x7ffe69dc) 0x20455e yyparse + 0x148e (0x7ffe6eec) 0x202e85 main + 0x1e1 (0x7ffe6f7c) 0x202953 _start + 0x5b (0x7ffe6fac) 0x1007ca (runtime_loader_seg0ro + 0x7ca) }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 19 02:41:03 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 19 Mar 2008 01:41:03 -0000 Subject: [Haiku-bugs] [Haiku] #1711: Haiku stops booting at allocate_commpage_entry(4, 34) In-Reply-To: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> References: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> Message-ID: <048.39067303b3139dd592d1eaba827c2a46@haiku-os.org> #1711: Haiku stops booting at allocate_commpage_entry(4, 34) ----------------------------+----------------------------------------------- Reporter: euan | Owner: korli Type: bug | Status: reopened Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Changes (by ddew): * status: closed => reopened * resolution: fixed => Comment: Sadly the fix didn't work for me on 5GB, it gets further in the boot process but still refuses to boot properly. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 19 02:42:54 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 19 Mar 2008 01:42:54 -0000 Subject: [Haiku-bugs] [Haiku] #1939: chart demo crashes when moved around In-Reply-To: <049.3e2bd489cab20a7321e2a9ec7e5f7db7@haiku-os.org> References: <049.3e2bd489cab20a7321e2a9ec7e5f7db7@haiku-os.org> Message-ID: <058.f347d37deb1435edec1b4a43e8ea0e2b@haiku-os.org> #1939: chart demo crashes when moved around -----------------------------+---------------------------------------------- Reporter: the ringmaster | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Resolution: | Platform: x86 -----------------------------+---------------------------------------------- Changes (by thorn): * platform: All => x86 * component: - General => Applications Comment: I can reproduce this backtrace: {{{ This GDB was configured as "i586-pc-haiku"...(no debugging symbols found) Thread 172 caused an exception: Segment violation .. . . . [Switching to team /boot/beos/demos/Chart (167) thread chart animation (172)] 0x00208717 in EraseStar () (gdb) bt #0 0x00208717 in EraseStar () #1 0x0020883a in RefreshStarPacket () #2 0x002142a8 in ChartWindow::RefreshStars () #3 0x002125f0 in ChartWindow::Animation () #4 0x0049d548 in thread_entry () from /boot/beos/system/lib/libroot.so #5 0x70080fec in ?? () }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 19 03:36:49 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 19 Mar 2008 02:36:49 -0000 Subject: [Haiku-bugs] [Haiku] #1940: links browser hangs when starting up Message-ID: <049.15cf6ce51b3b0cb189654c25ee8172e2@haiku-os.org> #1940: links browser hangs when starting up ----------------------------+----------------------------------------------- Reporter: the ringmaster | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: x86 | ----------------------------+----------------------------------------------- I downloaded (via wget) the links browser and I extracted it to ~/config/bin. When I click on the executable, the cpu shoots up to 100 percent. I'll attach a screenshot with the required info. Here's where I got links. http://bebits.com/app/4107 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 19 03:48:46 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 19 Mar 2008 02:48:46 -0000 Subject: [Haiku-bugs] [Haiku] #1940: links browser hangs when starting up In-Reply-To: <049.15cf6ce51b3b0cb189654c25ee8172e2@haiku-os.org> References: <049.15cf6ce51b3b0cb189654c25ee8172e2@haiku-os.org> Message-ID: <058.39d6316905dc42c1e9d553b1ab4ae6b1@haiku-os.org> #1940: links browser hangs when starting up -----------------------------+---------------------------------------------- Reporter: the ringmaster | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: x86 -----------------------------+---------------------------------------------- Comment (by the ringmaster): more info: I was trying to use the stable version I was using r24449 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 19 05:49:20 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 19 Mar 2008 04:49:20 -0000 Subject: [Haiku-bugs] [Haiku] #1711: Haiku stops booting at allocate_commpage_entry(4, 34) In-Reply-To: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> References: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> Message-ID: <048.423be91a5cb4ceea7b9a063cca395de7@haiku-os.org> #1711: Haiku stops booting at allocate_commpage_entry(4, 34) ----------------------------+----------------------------------------------- Reporter: euan | Owner: korli Type: bug | Status: reopened Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by ddew): Here are the relevant lines from the debug log, i had to type it in manually from a photo taken off the screen so I've omitted the lines showing what's being loaded. Last loaded debugger extension is hangman. . {{{ set_memory_write_back base 0 length dfee0000 find_nearest dfee0000 0 find_nearest 5fee0000 1 find_nearest 1fee0000 2 find_nearest fee0000 3 find_nearest 7ee000 4 find_nearest 120000 4 find_nearest 120000 3 find_nearest 20120000 2 find_nearest 120000 3 find_nearest 1fee0000 3 find_nearest 20120000 1 find_nearest 120000 2 find_nearest 1fee0000 2 sols: 0xffffffff00000000 0x20000000 0x100000 allocate MTRR slot 0, base = 0, length = 1000 allocate MTRR slot 1, base = e00000000, length = 20000000 allocate MTRR slot 2, base = dff00000, length = 100000 allocate MTRR slot 3, base = e0000000, length = 800000 ahci: ExecuteAtaRequest port 0: device transfer timeout ahci: sata_request::abort called for command 0x25 }}} The last two lines just keeps on repeating until, after a few minutes, the screen goes black and it hangs when the desktop is normally drawn. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 19 06:10:05 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 19 Mar 2008 05:10:05 -0000 Subject: [Haiku-bugs] [Haiku] #1941: New network stack fails to route broadcast packets, breaking DHCP Message-ID: <044.ca993b45a1b3acfe07115ffd6a448a71@haiku-os.org> #1941: New network stack fails to route broadcast packets, breaking DHCP --------------------------------------+------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: Network & Internet/Stack | Version: R1 development Platform: All | --------------------------------------+------------------------------------- When attempting to start the DHCP server after the recent routing change, the DHCP packets fail to send with "No route to host" returned...syslog with route tracing enabled as follows: KERN: bfs: bfs_open_dir:1483: Invalid Argument KERN: 3com: init_hardware(0x94832918) KERN: 3com: no hardware found. KERN: etherpci: init_driver init_driver: etherpci not found KERN: ipro100: init_hardware(0x9482fee4) KERN: ipro100: no hardware found. KERN: ipro1000: init_hardware(0x9484e784) KERN: ipro1000: no hardware found. KERN: marvell_yukon: init_hardware(0x94835c1c) KERN: marvell_yukon: no hardware found. KERN: loaded driver /boot/beos/system/add- ons/kernel/drivers/dev/net/net_stack KERN: nforce: init_hardware(0x94835c98) KERN: nforce, found NVIDIA nForce4 CK804 MCP9 Networking Adapter at 13 KERN: nforce: init_driver(0x94835c98) KERN: [nforce] (nfe) bus_alloc_resource(3, [16], 0x0, 0xffffffff, 0x1, 0x2) KERN: [nforce] (nfe) bus_alloc_resource(1, [0], 0x0, 0xffffffff, 0x1, 0x6) KERN: if_initname(0x90ec5c00, nfe, 3) KERN: [nforce] nforce: /dev/net/nforce/0 KERN: [nforce] () Found MII: ukphy KERN: [nforce] () OUI 0x005043, model 0x000c, rev. 2 KERN: [nforce] () Adding entry for Ethernet none KERN: Adding entry for Ethernet 10baseT/UTP KERN: 10baseTAdding entry for Ethernet 10baseT/UTP KERN: , 10baseT-FDXAdding entry for Ethernet 100baseTX KERN: , 100baseTXAdding entry for Ethernet 100baseTX KERN: , 100baseTX-FDXAdding entry for Ethernet 1000baseTX KERN: , 1000baseTAdding entry for Ethernet 1000baseTX KERN: , 1000baseT-FDXAdding entry for Ethernet autoselect KERN: , auto KERN: ifmedia_set: target EthernetKERN: autoselect KERN: ifmedia_set: setting to Ethernet autoselect KERN: loaded driver /boot/beos/system/add- ons/kernel/drivers/dev/net/nforce KERN: rtl8139: init_hardware(0x94dcaec0) KERN: rtl8139: no hardware found. KERN: via_rhine: init_hardware(0x94dcb218) KERN: via_rhine: no hardware found. KERN: register_domain(1, internet) KERN: unregister_domain(0x90f17940, 1, internet) KERN: register_domain(1, internet) KERN: get_device_interface: ask "network/devices/ethernet/v1" for loop KERN: get_device_interface: ask "network/devices/loopback/v1" for loop KERN: remove route from domain internet: dest 204.204.204.204, mask , gw , flags 200004 KERN: add route to domain internet: dest 127.0.0.1, mask 255.0.0.0, gw , flags 0 KERN: add route to domain internet: dest 127.0.0.1, mask , gw , flags 200004 KERN: bfs: bfs_open_dir:1483: Invalid Argument KERN: get_device_interface: ask "network/devices/ethernet/v1" for /dev/net/nforce/0 KERN: ipv4_datalink_init(/dev/net/nforce/0) KERN: add route to domain internet: dest , mask , gw , flags 880 KERN: [net/nforce/0] compat_open(0x2) KERN: ifmedia_ioctl: switching nfe to Ethernet autoselect KERN: /dev/net/nforce/0: media change, media 0x22 quality 1000 speed 10000 KERN: register_domain(4, link) KERN: test address 255.255.255.255 for routes... KERN: remove route from domain internet: dest 204.204.204.204, mask , gw , flags 200004 KERN: add route to domain internet: dest 169.254.0.92, mask 255.255.0.0, gw , flags 0 KERN: add route to domain internet: dest 169.254.0.92, mask , gw , flags 200004 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 19 06:10:35 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 19 Mar 2008 05:10:35 -0000 Subject: [Haiku-bugs] [Haiku] #1452: Sudoku locks up when trying to solve puzzle I entered from a book In-Reply-To: <042.8c34e6b972f6f38fab6ce591c15273fe@haiku-os.org> References: <042.8c34e6b972f6f38fab6ce591c15273fe@haiku-os.org> Message-ID: <051.add62632877deee24797aadd33a09619@haiku-os.org> #1452: Sudoku locks up when trying to solve puzzle I entered from a book ----------------------------------+----------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: low | Milestone: R1 Component: Applications/Sudoku | Version: R1 development Resolution: | Platform: All ----------------------------------+----------------------------------------- Comment (by scottmc): Looks like this has been updated to add the undo/redo and saving of markups and such. Axel you rock. This can be closed now I suppose. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 19 06:14:37 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 19 Mar 2008 05:14:37 -0000 Subject: [Haiku-bugs] [Haiku] #1941: New network stack fails to route broadcast packets, breaking DHCP In-Reply-To: <044.ca993b45a1b3acfe07115ffd6a448a71@haiku-os.org> References: <044.ca993b45a1b3acfe07115ffd6a448a71@haiku-os.org> Message-ID: <053.23e0d8218333379a827ba55eec15eecd@haiku-os.org> #1941: New network stack fails to route broadcast packets, breaking DHCP ---------------------------------------+------------------------------------ Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: Network & Internet/Stack | Version: R1 development Resolution: | Platform: All ---------------------------------------+------------------------------------ Changes (by umccullough): * cc: umccullough (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 19 09:51:14 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 19 Mar 2008 08:51:14 -0000 Subject: [Haiku-bugs] [Haiku] #1941: New network stack fails to route broadcast packets, breaking DHCP In-Reply-To: <044.ca993b45a1b3acfe07115ffd6a448a71@haiku-os.org> References: <044.ca993b45a1b3acfe07115ffd6a448a71@haiku-os.org> Message-ID: <053.210fec6cb714fa3275ce6b2e2e111c7a@haiku-os.org> #1941: New network stack fails to route broadcast packets, breaking DHCP ---------------------------------------+------------------------------------ Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: Network & Internet/Stack | Version: R1 development Resolution: | Platform: All ---------------------------------------+------------------------------------ Comment (by axeld): Can you add the output of "ifconfig", too? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 19 09:47:05 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 19 Mar 2008 08:47:05 -0000 Subject: [Haiku-bugs] [Haiku] #724: Tracker and Terminal unable to delete files with non-ascii filenames In-Reply-To: <058.44e586d5bfc0f2bb2424ec21e4ecf98e@haiku-os.org> References: <058.44e586d5bfc0f2bb2424ec21e4ecf98e@haiku-os.org> Message-ID: <067.a7441f495a1deafa22a81e4df64015ec@haiku-os.org> #724: Tracker and Terminal unable to delete files with non-ascii filenames --------------------------------------+------------------------------------- Reporter: info at haiku-security.com | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: Resolution: fixed | Platform: All --------------------------------------+------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Fixed in r24458. No wonder I couldn't reproduce it: the problem was only triggered when using the original BFS to write to Haiku BFS volume. strcmp() and friends did not work correctly!!! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 19 10:03:59 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 19 Mar 2008 09:03:59 -0000 Subject: [Haiku-bugs] [Haiku] #910: [Tracker] can't empty trash with cyrillic (at least) characters in filenames In-Reply-To: <040.025c50821243a0afacfe6ff53fe7166d@haiku-os.org> References: <040.025c50821243a0afacfe6ff53fe7166d@haiku-os.org> Message-ID: <049.4176c4e1016019d52ed62d79f7864360@haiku-os.org> #910: [Tracker] can't empty trash with cyrillic (at least) characters in filenames -----------------------------------+---------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: | Platform: All -----------------------------------+---------------------------------------- Comment (by diver): I'm wondering, could this be fixed by r24458 too? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 19 10:12:46 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 19 Mar 2008 09:12:46 -0000 Subject: [Haiku-bugs] [Haiku] #910: [Tracker] can't empty trash with cyrillic (at least) characters in filenames In-Reply-To: <040.025c50821243a0afacfe6ff53fe7166d@haiku-os.org> References: <040.025c50821243a0afacfe6ff53fe7166d@haiku-os.org> Message-ID: <049.b388dccaddacda06bee3d8840d0c9ad7@haiku-os.org> #910: [Tracker] can't empty trash with cyrillic (at least) characters in filenames -----------------------------------+---------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: | Platform: All -----------------------------------+---------------------------------------- Comment (by jackburton): Yeah, most probably. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 19 10:11:29 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 19 Mar 2008 09:11:29 -0000 Subject: [Haiku-bugs] [Haiku] #724: Tracker and Terminal unable to delete files with non-ascii filenames In-Reply-To: <058.44e586d5bfc0f2bb2424ec21e4ecf98e@haiku-os.org> References: <058.44e586d5bfc0f2bb2424ec21e4ecf98e@haiku-os.org> Message-ID: <067.fed09397159aba2172f31b0ff3dfafba@haiku-os.org> #724: Tracker and Terminal unable to delete files with non-ascii filenames --------------------------------------+------------------------------------- Reporter: info at haiku-security.com | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: Resolution: fixed | Platform: All --------------------------------------+------------------------------------- Comment (by jackburton): Replying to [comment:7 axeld]: > Fixed in r24458. No wonder I couldn't reproduce it: the problem was only triggered when using the original BFS to write to Haiku BFS volume. > strcmp() and friends did not work correctly!!! Whoah! Good catch! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 19 11:01:13 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 19 Mar 2008 10:01:13 -0000 Subject: [Haiku-bugs] [Haiku] #1938: libroot: free bug - Segment violation In-Reply-To: <040.119952edd4c2fc54e34694964337fe1e@haiku-os.org> References: <040.119952edd4c2fc54e34694964337fe1e@haiku-os.org> Message-ID: <049.58fec8053f24203668fa38108dd3f43f@haiku-os.org> #1938: libroot: free bug - Segment violation --------------------------------+------------------------------------------- Reporter: thorn | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Resolution: | Platform: x86 --------------------------------+------------------------------------------- Comment (by axeld): It doesn't have to be a duplicate of #1896. Whenever the allocator runs into a debugger call, it's because we run our allocator in debug mode. And that means it will detect *user* errors better. Can you point out which source file this is and where I can find it? From the source you pasted here, you don't see where old_locale is initialized or allocated. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 19 11:02:22 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 19 Mar 2008 10:02:22 -0000 Subject: [Haiku-bugs] [Haiku] #1940: links browser hangs when starting up In-Reply-To: <049.15cf6ce51b3b0cb189654c25ee8172e2@haiku-os.org> References: <049.15cf6ce51b3b0cb189654c25ee8172e2@haiku-os.org> Message-ID: <058.bf6e3388f81b62e16d3126ca59a577a9@haiku-os.org> #1940: links browser hangs when starting up -----------------------------+---------------------------------------------- Reporter: the ringmaster | Owner: mmu_man Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: x86 -----------------------------+---------------------------------------------- Changes (by axeld): * owner: axeld => mmu_man -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 19 11:03:10 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 19 Mar 2008 10:03:10 -0000 Subject: [Haiku-bugs] [Haiku] #910: [Tracker] can't empty trash with cyrillic (at least) characters in filenames In-Reply-To: <040.025c50821243a0afacfe6ff53fe7166d@haiku-os.org> References: <040.025c50821243a0afacfe6ff53fe7166d@haiku-os.org> Message-ID: <049.926130c80137f957f1d6feef40841168@haiku-os.org> #910: [Tracker] can't empty trash with cyrillic (at least) characters in filenames -----------------------------------+---------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: duplicate | Platform: All -----------------------------------+---------------------------------------- Changes (by axeld): * status: new => closed * resolution: => duplicate Comment: Duplicate of #724. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 19 11:03:23 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 19 Mar 2008 10:03:23 -0000 Subject: [Haiku-bugs] [Haiku] #724: Tracker and Terminal unable to delete files with non-ascii filenames In-Reply-To: <058.44e586d5bfc0f2bb2424ec21e4ecf98e@haiku-os.org> References: <058.44e586d5bfc0f2bb2424ec21e4ecf98e@haiku-os.org> Message-ID: <067.a479e53c0e49c65bf63059902e844eb0@haiku-os.org> #724: Tracker and Terminal unable to delete files with non-ascii filenames --------------------------------------+------------------------------------- Reporter: info at haiku-security.com | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/libroot.so | Version: Resolution: fixed | Platform: All --------------------------------------+------------------------------------- Changes (by axeld): * component: System/Kernel => System/libroot.so -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 19 11:10:26 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 19 Mar 2008 10:10:26 -0000 Subject: [Haiku-bugs] [Haiku] #1711: Haiku stops booting at allocate_commpage_entry(4, 34) In-Reply-To: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> References: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> Message-ID: <048.125f9f15194a8b5a047c299a4be54183@haiku-os.org> #1711: Haiku stops booting at allocate_commpage_entry(4, 34) ----------------------------+----------------------------------------------- Reporter: euan | Owner: korli Type: bug | Status: reopened Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by jackburton): Replying to [comment:32 ddew]: > ahci: ExecuteAtaRequest port 0: device transfer timeout > ahci: sata_request::abort called for command 0x25 > }}} This isn't related at all, looks like a problem with the IDE stack/SATA driver. This shows that the original bug is fixed, though, since the boot process goes on. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 19 11:26:26 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 19 Mar 2008 10:26:26 -0000 Subject: [Haiku-bugs] [Haiku] #1939: chart demo crashes when moved around In-Reply-To: <049.3e2bd489cab20a7321e2a9ec7e5f7db7@haiku-os.org> References: <049.3e2bd489cab20a7321e2a9ec7e5f7db7@haiku-os.org> Message-ID: <058.e05ebaa33dcdc02362df8952fec722b8@haiku-os.org> #1939: chart demo crashes when moved around ---------------------------------+------------------------------------------ Reporter: the ringmaster | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Platform: x86 ---------------------------------+------------------------------------------ Changes (by jackburton): * owner: axeld => jackburton * component: Applications => Servers/app_server Comment: Looks like the visible region passed to BDirectWindow from the app_server doesn't take into account the fact that the window is off screen. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 19 11:27:05 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 19 Mar 2008 10:27:05 -0000 Subject: [Haiku-bugs] [Haiku] #1940: links browser hangs when starting up In-Reply-To: <049.15cf6ce51b3b0cb189654c25ee8172e2@haiku-os.org> References: <049.15cf6ce51b3b0cb189654c25ee8172e2@haiku-os.org> Message-ID: <058.0d889faebd6632ae725effd56e90d317@haiku-os.org> #1940: links browser hangs when starting up -----------------------------+---------------------------------------------- Reporter: the ringmaster | Owner: mmu_man Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: x86 -----------------------------+---------------------------------------------- Changes (by mmu_man): * status: new => assigned Comment: the thread ID was wrong (223 vs 233), so the screenshot doesn't help. Does it happen everytime ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 19 11:31:02 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 19 Mar 2008 10:31:02 -0000 Subject: [Haiku-bugs] [Haiku] #1939: chart demo crashes when moved around In-Reply-To: <049.3e2bd489cab20a7321e2a9ec7e5f7db7@haiku-os.org> References: <049.3e2bd489cab20a7321e2a9ec7e5f7db7@haiku-os.org> Message-ID: <058.be51ebce2011e0fdf447a360a5f44b30@haiku-os.org> #1939: chart demo crashes when moved around ---------------------------------+------------------------------------------ Reporter: the ringmaster | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Platform: x86 ---------------------------------+------------------------------------------ Comment (by stippi): It probably does, but I am suspecting a synchronization bug in this code. It is probably the same reason why BDirectWindows sometimes draw over other windows. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 19 11:32:33 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 19 Mar 2008 10:32:33 -0000 Subject: [Haiku-bugs] [Haiku] #1711: Haiku stops booting at allocate_commpage_entry(4, 34) In-Reply-To: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> References: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> Message-ID: <048.c99b99d8bbc00b9cb0dcbb12446a9bfe@haiku-os.org> #1711: Haiku stops booting at allocate_commpage_entry(4, 34) ----------------------------+----------------------------------------------- Reporter: euan | Owner: korli Type: bug | Status: reopened Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by korli): Replying to [comment:33 jackburton]: > > ahci: ExecuteAtaRequest port 0: device transfer timeout > > ahci: sata_request::abort called for command 0x25 > > }}} > > This isn't related at all, looks like a problem with the IDE stack/SATA driver. > This shows that the original bug is fixed, though, since the boot process goes on. No, I had the same behavior when setting the memory to write back, I/O requests are then stalled because the PCI bus is not refreshed. Though I'm wondering if Haiku is supposed to work with 5GB. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 19 11:34:53 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 19 Mar 2008 10:34:53 -0000 Subject: [Haiku-bugs] [Haiku] #1938: libroot: free bug - Segment violation In-Reply-To: <040.119952edd4c2fc54e34694964337fe1e@haiku-os.org> References: <040.119952edd4c2fc54e34694964337fe1e@haiku-os.org> Message-ID: <049.2e9520712282589ffb19afd92f803710@haiku-os.org> #1938: libroot: free bug - Segment violation --------------------------------+------------------------------------------- Reporter: thorn | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Resolution: | Platform: x86 --------------------------------+------------------------------------------- Comment (by thorn): full source [http://www.google.com/codesearch?hl=en&q=+old_locale+show:xLaUG3jobCQ:cIpfWKcXYcU:xLaUG3jobCQ&sa=N&cd=6&ct=rc&cs_p=cvs+:pserver:anonymous%40cvs.savannah.nongnu.org:/cvsroot/texinfo+texinfo&cs_f=makeinfo/makeinfo.c#l4287 texinfo/makeinfo/makeinfo.c] {{{ /* Translate MSGID according to the document language (--document-language), rather than the environment language (LANG, etc.). This comes from the get_title function in gettext. (xsetenv and unsetenv come from the gnulib xsetenv module.) */ char * getdocumenttext (const char *msgid) { /* The original get_title also saves, sets, and restores OUTPUT_CHARSET, so that the translation will be given in the proper encoding (via canonical_locale_charset). But defining that function ends up pulling a whole lot of subsidiary functions. Not sure how to handle it; skip the whole thing for now. */ const char *tmp; char *old_LC_ALL; char *old_LANGUAGE; const char *result; #ifdef HAVE_SETLOCALE char *old_locale; #endif /* Save LC_ALL, LANGUAGE environment variables. */ tmp = getenv ("LC_ALL"); old_LC_ALL = (tmp != NULL ? xstrdup (tmp) : NULL); tmp = getenv ("LANGUAGE"); old_LANGUAGE = (tmp != NULL ? xstrdup (tmp) : NULL); xsetenv ("LC_ALL", document_language, 1); unsetenv ("LANGUAGE"); #ifdef HAVE_SETLOCALE old_locale = xstrdup (setlocale (LC_ALL, NULL)); if (setlocale (LC_ALL, "") == NULL) /* Nonexistent locale. Use the original. */ result = msgid; else #endif { /* Fetch the translation. */ result = gettext (msgid); } /* Restore LC_ALL, LANGUAGE environment variables. */ if (old_LC_ALL != NULL) xsetenv ("LC_ALL", old_LC_ALL, 1), free (old_LC_ALL); else unsetenv ("LC_ALL"); if (old_LANGUAGE != NULL) xsetenv ("LANGUAGE", old_LANGUAGE, 1), free (old_LANGUAGE); else unsetenv ("LANGUAGE"); #ifdef HAVE_SETLOCALE setlocale (LC_ALL, old_locale); free (old_locale); #endif return result; } }}} and {{{ /* Clone an object P of size S, with error checking. There's no need for xnmemdup (P, N, S), since xmemdup (P, N * S) works without any need for an arithmetic overflow check. */ void * xmemdup (void const *p, size_t s) { return memcpy (xmalloc (s), p, s); } /* Clone STRING. */ char * xstrdup (char const *string) { return xmemdup (string, strlen (string) + 1); } }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 19 11:37:47 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 19 Mar 2008 10:37:47 -0000 Subject: [Haiku-bugs] [Haiku] #1711: Haiku stops booting at allocate_commpage_entry(4, 34) In-Reply-To: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> References: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> Message-ID: <048.6bea3f77207ed770752467006e7686ef@haiku-os.org> #1711: Haiku stops booting at allocate_commpage_entry(4, 34) ----------------------------+----------------------------------------------- Reporter: euan | Owner: korli Type: bug | Status: reopened Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by ddew): Replying to [comment:34 korli]: > Replying to [comment:33 jackburton]: > > > ahci: ExecuteAtaRequest port 0: device transfer timeout > > > ahci: sata_request::abort called for command 0x25 > > > }}} > > > > This isn't related at all, looks like a problem with the IDE stack/SATA driver. > > This shows that the original bug is fixed, though, since the boot process goes on. > > No, I had the same behavior when setting the memory to write back, I/O requests are then stalled because the PCI bus is not refreshed. > Though I'm wondering if Haiku is supposed to work with 5GB. > I'm not picky about having all the RAM being seen and used by the os, having only 3.5gb showing up is acceptable. Although PAE-support would be nice I just want to be able to boot into Haiku without pulling out RAM from the machine.:) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 19 11:40:28 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 19 Mar 2008 10:40:28 -0000 Subject: [Haiku-bugs] [Haiku] #1939: chart demo crashes when moved around In-Reply-To: <049.3e2bd489cab20a7321e2a9ec7e5f7db7@haiku-os.org> References: <049.3e2bd489cab20a7321e2a9ec7e5f7db7@haiku-os.org> Message-ID: <058.204ba297494e7f0a47ec9d4078149639@haiku-os.org> #1939: chart demo crashes when moved around ---------------------------------+------------------------------------------ Reporter: the ringmaster | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Platform: x86 ---------------------------------+------------------------------------------ Comment (by jackburton): Replying to [comment:3 stippi]: > It probably does, but I am suspecting a synchronization bug in this code. It is probably the same reason why BDirectWindows sometimes draw over other windows. Does it ever happen ? I thought it happened only with BGLView in direct mode (which is a slightly different test case) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 19 11:43:20 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 19 Mar 2008 10:43:20 -0000 Subject: [Haiku-bugs] [Haiku] #1936: 24423 broke networking In-Reply-To: <039.fa3291b6c5808bc8048d36db4c8a9975@haiku-os.org> References: <039.fa3291b6c5808bc8048d36db4c8a9975@haiku-os.org> Message-ID: <048.8641d83f328b67dee79d4eea46650a85@haiku-os.org> #1936: 24423 broke networking ---------------------------------------+------------------------------------ Reporter: ddew | Owner: zooey Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Resolution: fixed | Platform: x86 ---------------------------------------+------------------------------------ Changes (by axeld): * status: new => closed * resolution: => fixed * component: Network & Internet/IPv4 => Network & Internet/Stack Comment: Fixed in r24459. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 19 11:45:11 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 19 Mar 2008 10:45:11 -0000 Subject: [Haiku-bugs] [Haiku] #1941: New network stack fails to route broadcast packets, breaking DHCP In-Reply-To: <044.ca993b45a1b3acfe07115ffd6a448a71@haiku-os.org> References: <044.ca993b45a1b3acfe07115ffd6a448a71@haiku-os.org> Message-ID: <053.c681f3b4ae02f4644719f8b2a675d310@haiku-os.org> #1941: New network stack fails to route broadcast packets, breaking DHCP ---------------------------------------+------------------------------------ Reporter: anevilyak | Owner: axeld Type: bug | Status: closed Priority: high | Milestone: R1/alpha1 Component: Network & Internet/Stack | Version: R1 development Resolution: fixed | Platform: All ---------------------------------------+------------------------------------ Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Never mind, I could reproduce this on real hardware as well with the ipro1000 driver; the driver reported no link early, and found the link too late for DHCP (it worked fine in VMware, though). Fixed in r24459. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 19 11:53:48 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 19 Mar 2008 10:53:48 -0000 Subject: [Haiku-bugs] [Haiku] #1936: 24423 broke networking In-Reply-To: <039.fa3291b6c5808bc8048d36db4c8a9975@haiku-os.org> References: <039.fa3291b6c5808bc8048d36db4c8a9975@haiku-os.org> Message-ID: <048.a672a24d741a4bf3ed574fc1c031670d@haiku-os.org> #1936: 24423 broke networking ---------------------------------------+------------------------------------ Reporter: ddew | Owner: zooey Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Resolution: fixed | Platform: x86 ---------------------------------------+------------------------------------ Comment (by jackburton): Replying to [comment:1 axeld]: > Fixed in r24459. This could help with #1744 too. I'll test and report. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 19 11:54:49 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 19 Mar 2008 10:54:49 -0000 Subject: [Haiku-bugs] [Haiku] #1940: links browser hangs when starting up In-Reply-To: <049.15cf6ce51b3b0cb189654c25ee8172e2@haiku-os.org> References: <049.15cf6ce51b3b0cb189654c25ee8172e2@haiku-os.org> Message-ID: <058.2d4cfa5a1863d2dfdc7ac3d7df8ee659@haiku-os.org> #1940: links browser hangs when starting up -----------------------------+---------------------------------------------- Reporter: the ringmaster | Owner: mmu_man Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: x86 -----------------------------+---------------------------------------------- Comment (by mmlr): Note that this is the old 0.99 Links I put on BeBits once, not the current one from Francois. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 19 11:56:22 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 19 Mar 2008 10:56:22 -0000 Subject: [Haiku-bugs] [Haiku] #1711: Haiku stops booting at allocate_commpage_entry(4, 34) In-Reply-To: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> References: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> Message-ID: <048.39f443107bb108b7af20c446e5df3c18@haiku-os.org> #1711: Haiku stops booting at allocate_commpage_entry(4, 34) ----------------------------+----------------------------------------------- Reporter: euan | Owner: korli Type: bug | Status: reopened Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by axeld): How do the MTRR look like when booting Linux with those 5GB? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 19 12:04:13 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 19 Mar 2008 11:04:13 -0000 Subject: [Haiku-bugs] [Haiku] #1711: Haiku stops booting at allocate_commpage_entry(4, 34) In-Reply-To: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> References: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> Message-ID: <048.34ca2d626701750ae68e804bcbc68801@haiku-os.org> #1711: Haiku stops booting at allocate_commpage_entry(4, 34) ----------------------------+----------------------------------------------- Reporter: euan | Owner: korli Type: bug | Status: reopened Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by korli): Replying to [comment:36 axeld]: > How do the MTRR look like when booting Linux with those 5GB? See the comment 25 dated from 03/14/08 11:38:13 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 19 12:14:25 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 19 Mar 2008 11:14:25 -0000 Subject: [Haiku-bugs] [Haiku] #1940: links browser hangs when starting up In-Reply-To: <049.15cf6ce51b3b0cb189654c25ee8172e2@haiku-os.org> References: <049.15cf6ce51b3b0cb189654c25ee8172e2@haiku-os.org> Message-ID: <058.a1693720959cb5fb68ace78c75390f18@haiku-os.org> #1940: links browser hangs when starting up -----------------------------+---------------------------------------------- Reporter: the ringmaster | Owner: mmu_man Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: x86 -----------------------------+---------------------------------------------- Comment (by mmu_man): Eh, didn't even notive the url... Try that one maybe ? http://revolf.free.fr/beos/links-beos-bin.zip -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 19 12:15:34 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 19 Mar 2008 11:15:34 -0000 Subject: [Haiku-bugs] [Haiku] #1940: links browser hangs when starting up In-Reply-To: <049.15cf6ce51b3b0cb189654c25ee8172e2@haiku-os.org> References: <049.15cf6ce51b3b0cb189654c25ee8172e2@haiku-os.org> Message-ID: <058.3a09d3d47ae9239e1ce7047ed686ed87@haiku-os.org> #1940: links browser hangs when starting up -----------------------------+---------------------------------------------- Reporter: the ringmaster | Owner: mmu_man Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: x86 -----------------------------+---------------------------------------------- Comment (by mmu_man): Btw, it's normal the one from bebits doesn't display anything, it's a terminal only app, it's probably looping on reading stdin... Ie. it's *not* meant to be clicked :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 19 12:45:35 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 19 Mar 2008 11:45:35 -0000 Subject: [Haiku-bugs] [Haiku] #1711: Haiku stops booting at allocate_commpage_entry(4, 34) In-Reply-To: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> References: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> Message-ID: <048.f6da8f407bf5c882436502e38a78d725@haiku-os.org> #1711: Haiku stops booting at allocate_commpage_entry(4, 34) ----------------------------+----------------------------------------------- Reporter: euan | Owner: korli Type: bug | Status: reopened Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by jackburton): Replying to [comment:35 ddew]: > > Though I'm wondering if Haiku is supposed to work with 5GB. > > Looks like it works with 4GB at least... http://www.biffuz.it/misc/haiku4gb.jpg -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 19 13:38:55 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 19 Mar 2008 12:38:55 -0000 Subject: [Haiku-bugs] [Haiku] #1940: links browser hangs when starting up In-Reply-To: <049.15cf6ce51b3b0cb189654c25ee8172e2@haiku-os.org> References: <049.15cf6ce51b3b0cb189654c25ee8172e2@haiku-os.org> Message-ID: <058.34a6f7fe8693283d30c1baacfcf20ca2@haiku-os.org> #1940: links browser hangs when starting up -----------------------------+---------------------------------------------- Reporter: the ringmaster | Owner: mmu_man Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: invalid | Platform: x86 -----------------------------+---------------------------------------------- Changes (by mmlr): * status: assigned => closed * resolution: => invalid Comment: Yes, this is exactly the cause. I'll mark it as invalid as this is expected behaviour. Either you should use 0.99 from the Terminal or (the better choice) use the current GUI enabled version from Francois. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 19 19:55:15 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 19 Mar 2008 18:55:15 -0000 Subject: [Haiku-bugs] [Haiku] #1711: Haiku stops booting at allocate_commpage_entry(4, 34) In-Reply-To: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> References: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> Message-ID: <048.e954326d3a82a85b5254e61e499909e0@haiku-os.org> #1711: Haiku stops booting at allocate_commpage_entry(4, 34) ----------------------------+----------------------------------------------- Reporter: euan | Owner: korli Type: bug | Status: reopened Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by korli): Replying to [comment:32 ddew]: > allocate MTRR slot 0, base = 0, length = 1000 > allocate MTRR slot 1, base = e00000000, length = 20000000 > allocate MTRR slot 2, base = dff00000, length = 100000 > allocate MTRR slot 3, base = e0000000, length = 800000 The first line should have a length 0x100000000. Are you sure about it ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 19 21:01:04 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 19 Mar 2008 20:01:04 -0000 Subject: [Haiku-bugs] [Haiku] #1711: Haiku stops booting at allocate_commpage_entry(4, 34) In-Reply-To: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> References: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> Message-ID: <048.204b150d3852270b09218e5b9f354de4@haiku-os.org> #1711: Haiku stops booting at allocate_commpage_entry(4, 34) ----------------------------+----------------------------------------------- Reporter: euan | Owner: korli Type: bug | Status: reopened Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by korli): Could you test again with r24476 please ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 19 22:01:06 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 19 Mar 2008 21:01:06 -0000 Subject: [Haiku-bugs] [Haiku] #1878: Dropdown menu, first item not selectable In-Reply-To: <041.fb2311908f30e9ec71ea3e67244fd591@haiku-os.org> References: <041.fb2311908f30e9ec71ea3e67244fd591@haiku-os.org> Message-ID: <050.63ec01689f405b923dc90cbdb42c4ddf@haiku-os.org> #1878: Dropdown menu, first item not selectable ---------------------------------+------------------------------------------ Reporter: aldeck | Owner: jackburton Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: fixed | Platform: All ---------------------------------+------------------------------------------ Changes (by jackburton): * status: new => closed * resolution: => fixed Comment: It's fixed in r24479. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 19 23:13:37 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 19 Mar 2008 22:13:37 -0000 Subject: [Haiku-bugs] [Haiku] #1711: Haiku stops booting at allocate_commpage_entry(4, 34) In-Reply-To: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> References: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> Message-ID: <048.dc0361af71703a22b49727b7a50c0fca@haiku-os.org> #1711: Haiku stops booting at allocate_commpage_entry(4, 34) ----------------------------+----------------------------------------------- Reporter: euan | Owner: korli Type: bug | Status: reopened Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by ddew): Tried r24479 and it just reboots the box when it starts setting up the MTRRs. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 19 23:55:12 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 19 Mar 2008 22:55:12 -0000 Subject: [Haiku-bugs] [Haiku] #1909: emuxki/midi related KDLs? In-Reply-To: <048.7c433231494081c4264c03b82f3ce97f@haiku-os.org> References: <048.7c433231494081c4264c03b82f3ce97f@haiku-os.org> Message-ID: <057.f35a8872fa51e4594c788cd38a7d7a49@haiku-os.org> #1909: emuxki/midi related KDLs? ----------------------------+----------------------------------------------- Reporter: jonas.kirilla | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by korli): Could you activate TRACE_DEVFS in src/system/kernel/fs/devfs.cpp and provide a serial log ? The emuxki driver has this peculiarity : it publishes two sets of entries in dev/audio/hmultiaudio and dev/midi. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 19 23:55:23 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 19 Mar 2008 22:55:23 -0000 Subject: [Haiku-bugs] [Haiku] #1711: Haiku stops booting at allocate_commpage_entry(4, 34) In-Reply-To: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> References: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> Message-ID: <048.f932b5962358b87d87e9fa9bfbafa8eb@haiku-os.org> #1711: Haiku stops booting at allocate_commpage_entry(4, 34) ----------------------------+----------------------------------------------- Reporter: euan | Owner: korli Type: bug | Status: reopened Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by korli): Maybe it's not a good idea to have a MTRR uncached covering a MTRR write combining (the fourth one) ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 20 00:46:33 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 19 Mar 2008 23:46:33 -0000 Subject: [Haiku-bugs] [Haiku] #1942: vm_soft_fault when booting with pxe and a haiku.image through remote_disk_server, Message-ID: <038.4a960e08b8fc5f80593ec3365106b526@haiku-os.org> #1942: vm_soft_fault when booting with pxe and a haiku.image through remote_disk_server, --------------------------------------+------------------------------------- Reporter: oco | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Platform: All | --------------------------------------+------------------------------------- When booting a machine with pxe and a haiku.image through the remote_disk_server, there is a vm_soft_fault. The system seems to reload the network stack, already used to access the remote disk. Here is the error : vm_soft_fault: va 0x8164a18a not covered by area in address space vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x8164a18a , ip 0x8164a18a, write 0, user 0, thread 0x2d PANIC: vm_page_fault: unhandled page fault in kernel space at 0x8164a18a, ip 0x8 164a18a. The serial output is attached (with stack trace). The computer is an old celeron 300 with a rtl8139 network card. I use a gPXE floppy disk to boot the system. Workaround : - mount the haiku.image - rename //beos/system/add-on/kernel/drivers/dev/net to //beos/system/add-on/kernel/drivers/dev/net.arch. - unmount -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 20 02:10:21 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 20 Mar 2008 01:10:21 -0000 Subject: [Haiku-bugs] [Haiku] #1943: Click b-menu to open AND click b-menu to close Message-ID: <049.5be279cdd1ad894e42a23a739f9459e3@haiku-os.org> #1943: Click b-menu to open AND click b-menu to close ----------------------------+----------------------------------------------- Reporter: the ringmaster | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | ----------------------------+----------------------------------------------- As it is right now I can open the b-menu by clicking on it, but to close the menu I have to click some place on the desktop. I wish I could click the menu again and that would close it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 20 08:20:59 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 20 Mar 2008 07:20:59 -0000 Subject: [Haiku-bugs] [Haiku] #1943: Click b-menu to open AND click b-menu to close In-Reply-To: <049.5be279cdd1ad894e42a23a739f9459e3@haiku-os.org> References: <049.5be279cdd1ad894e42a23a739f9459e3@haiku-os.org> Message-ID: <058.de9f152fedf003d08b824671d2bb826d@haiku-os.org> #1943: Click b-menu to open AND click b-menu to close -----------------------------+---------------------------------------------- Reporter: the ringmaster | Owner: axeld Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: duplicate | Platform: All -----------------------------+---------------------------------------------- Changes (by jackburton): * status: new => closed * resolution: => duplicate Comment: It's a dup of #1826 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 20 13:59:11 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 20 Mar 2008 12:59:11 -0000 Subject: [Haiku-bugs] [Haiku] #1942: vm_soft_fault when booting with pxe and a haiku.image through remote_disk_server, In-Reply-To: <038.4a960e08b8fc5f80593ec3365106b526@haiku-os.org> References: <038.4a960e08b8fc5f80593ec3365106b526@haiku-os.org> Message-ID: <047.7c255a5c6a865b06cfb11499c7fc665a@haiku-os.org> #1942: vm_soft_fault when booting with pxe and a haiku.image through remote_disk_server, ---------------------------------------+------------------------------------ Reporter: oco | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Resolution: | Platform: All ---------------------------------------+------------------------------------ Comment (by korli): Did it work before ? There is also a similar problem in #1909, as if the devfs mixed up vnodes, cookies or hooks when republishing a driver. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 20 14:41:30 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 20 Mar 2008 13:41:30 -0000 Subject: [Haiku-bugs] [Haiku] #1944: Kill command don't work with process names Message-ID: <038.92673db4233c8a78a2bc2c023a4462b9@haiku-os.org> #1944: Kill command don't work with process names --------------------------+------------------------------------------------- Reporter: tqh | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Platform: All | --------------------------+------------------------------------------------- In BeOS R5 I always used {{{ kill Tracker }}} when needed. Unfortunatly Haiku's 'kill' doesn't support this fantastic feature. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 20 15:51:26 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 20 Mar 2008 14:51:26 -0000 Subject: [Haiku-bugs] [Haiku] #1945: [marvell yukon] 11ab:4320 not detected Message-ID: <040.6d7189e51f797abf4deca9c4e5ded43f@haiku-os.org> #1945: [marvell yukon] 11ab:4320 not detected -----------------------------+---------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Network | Version: R1 development Platform: All | -----------------------------+---------------------------------------------- lspci |grep Ethernet 02:05.0 Ethernet controller: Marvell Technology Group Ltd. 88E8001 Gigabit Ethernet Controller (rev 13) 02:05.0 0200: 11ab:4320 (rev 13) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 20 15:52:51 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 20 Mar 2008 14:52:51 -0000 Subject: [Haiku-bugs] [Haiku] #1944: Kill command don't work with process names In-Reply-To: <038.92673db4233c8a78a2bc2c023a4462b9@haiku-os.org> References: <038.92673db4233c8a78a2bc2c023a4462b9@haiku-os.org> Message-ID: <047.531da8ff4a64210ca5646dd2747a9ccc@haiku-os.org> #1944: Kill command don't work with process names ---------------------------+------------------------------------------------ Reporter: tqh | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by diver): Isn't killall is used for that? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 20 15:58:16 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 20 Mar 2008 14:58:16 -0000 Subject: [Haiku-bugs] [Haiku] #1946: [NetPositive] crash on close Message-ID: <040.a8d6e73db596cf0e47e9c54aa3299ad7@haiku-os.org> #1946: [NetPositive] crash on close --------------------------------+------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Platform: All | --------------------------------+------------------------------------------- NetPositive crashing on close. I will attach bt if needed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 20 16:08:46 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 20 Mar 2008 15:08:46 -0000 Subject: [Haiku-bugs] [Haiku] #1947: [Software Valet] fails to install ButterFly pkg Message-ID: <040.90189cb09709edd4c8bc4ae79f81a4ad@haiku-os.org> #1947: [Software Valet] fails to install ButterFly pkg ------------------------------+--------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Support Kit | Version: R1 development Platform: All | ------------------------------+--------------------------------------------- Software Valet fails to install Butterfly pkg. It reports that package is successfully installed It creates destination folder but this folder is empty. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 20 16:45:20 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 20 Mar 2008 15:45:20 -0000 Subject: [Haiku-bugs] [Haiku] #1948: Make dl*() Functions Standard Compliant Message-ID: <043.a78c66b75abe6fc92e5672024e7a9f3e@haiku-os.org> #1948: Make dl*() Functions Standard Compliant -------------------------------+-------------------------------------------- Reporter: bonefish | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Platform: All | -------------------------------+-------------------------------------------- Our dl*() have several issues ATM: - Multiple calls to dlopen() should open the object only once. - Passing NULL to dlopen() should open the executable. - The flags passed to dlopen() are ignored. That is OK for RTLD_LAZY/RTLD_NOW (we always relocate everything when loading), but probably not for RTLD_GLOBAL/RTLD_LOCAL. - dlsym() searches only the object itself, not dependencies. - Other issues I have missed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 20 17:22:56 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 20 Mar 2008 16:22:56 -0000 Subject: [Haiku-bugs] [Haiku] #1948: Make dl*() Functions Standard Compliant In-Reply-To: <043.a78c66b75abe6fc92e5672024e7a9f3e@haiku-os.org> References: <043.a78c66b75abe6fc92e5672024e7a9f3e@haiku-os.org> Message-ID: <052.4dfcbcc8a2ee4eaae74e046c66aec60d@haiku-os.org> #1948: Make dl*() Functions Standard Compliant --------------------------------+------------------------------------------- Reporter: bonefish | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Resolution: | Platform: All --------------------------------+------------------------------------------- Comment (by jackburton): Maybe we should use glibc's dl* functions instead of rolling our own ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 20 18:54:25 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 20 Mar 2008 17:54:25 -0000 Subject: [Haiku-bugs] [Haiku] #1942: vm_soft_fault when booting with pxe and a haiku.image through remote_disk_server, In-Reply-To: <038.4a960e08b8fc5f80593ec3365106b526@haiku-os.org> References: <038.4a960e08b8fc5f80593ec3365106b526@haiku-os.org> Message-ID: <047.08f90d81ce1c20a778c4fe8ccc8f774a@haiku-os.org> #1942: vm_soft_fault when booting with pxe and a haiku.image through remote_disk_server, ---------------------------------------+------------------------------------ Reporter: oco | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Resolution: | Platform: All ---------------------------------------+------------------------------------ Comment (by oco): I don't know ! This is the first time i boot an image through remote_disk_server... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 20 20:40:15 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 20 Mar 2008 19:40:15 -0000 Subject: [Haiku-bugs] [Haiku] #1948: Make dl*() Functions Standard Compliant In-Reply-To: <043.a78c66b75abe6fc92e5672024e7a9f3e@haiku-os.org> References: <043.a78c66b75abe6fc92e5672024e7a9f3e@haiku-os.org> Message-ID: <052.cf0ae59cbccabe003644cf7adb08aeae@haiku-os.org> #1948: Make dl*() Functions Standard Compliant --------------------------------+------------------------------------------- Reporter: bonefish | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Resolution: | Platform: All --------------------------------+------------------------------------------- Comment (by bonefish): Replying to [comment:1 jackburton]: > Maybe we should use glibc's dl* functions instead of rolling our own ? I don't think glibc provides those functions. Given that they need to interface with the platform-specific runtime loader there would be little they could do anyway. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 20 21:14:26 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 20 Mar 2008 20:14:26 -0000 Subject: [Haiku-bugs] [Haiku] #1946: [NetPositive] crash on close In-Reply-To: <040.a8d6e73db596cf0e47e9c54aa3299ad7@haiku-os.org> References: <040.a8d6e73db596cf0e47e9c54aa3299ad7@haiku-os.org> Message-ID: <049.741de450918d6b60261b87eb4ee4ddae@haiku-os.org> #1946: [NetPositive] crash on close ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by bonefish): Please always provide a back trace, if possible. This way people might be able to contribute ideas without needing to test it themselves. Here it comes anyway: {{{ Thread 198 called debugger(): getNumAvailable() < getNumBlocks() [...] [Switching to team /Transfer/downloads/NetPositive (198) thread NetPositive (198)] 0xffff0104 in ?? () (gdb) bt #0 0xffff0104 in ?? () #1 0x00975316 in debugger () from /boot/beos/system/lib/libroot.so #2 0x0097c479 in __assert_fail () from /boot/beos/system/lib/libroot.so #3 0x009813b6 in BPrivate::hoardHeap::freeBlock () from /boot/beos/system/lib/libroot.so #4 0x00982462 in BPrivate::processHeap::free () from /boot/beos/system/lib/libroot.so #5 0x00983af0 in free () from /boot/beos/system/lib/libroot.so #6 0x00972fe8 in __builtin_delete () from /boot/beos/system/lib/libroot.so #7 0x004fefe8 in BArchivable::~BArchivable () from /boot/beos/system/lib/libbe.so #8 0x00423bea in BBitmap::~BBitmap () from /boot/beos/system/lib/libbe.so #9 0x00288ae9 in HTMLView::Cleanup () #10 0x0029ec46 in NetPositive::Cleanup () #11 0x0029e622 in main () }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 21 04:20:35 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 21 Mar 2008 03:20:35 -0000 Subject: [Haiku-bugs] [Haiku] #1925: Reboot during startup on Toshiba Satellite 2615DVD/6.0 In-Reply-To: <046.464cc1a60522972f4d6a4db8a13a4bd4@haiku-os.org> References: <046.464cc1a60522972f4d6a4db8a13a4bd4@haiku-os.org> Message-ID: <055.8d320c6ba2b5e3c7f69a60dda9e95b3e@haiku-os.org> #1925: Reboot during startup on Toshiba Satellite 2615DVD/6.0 ----------------------------+----------------------------------------------- Reporter: umccullough | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by umccullough): I attached a new serial log from Haiku r24494 and I enabled TRACE_VM and TRACE_FAULTS in vm.cpp (had to comment out a trace line that didn't compile, btw). Looks like it maybe fails in find_and_insert_area_slot() Anything I can try or provide to further identify the cause here? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 21 11:05:46 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 21 Mar 2008 10:05:46 -0000 Subject: [Haiku-bugs] [Haiku] #1203: Haiku USB in BeOS R5 In-Reply-To: <041.a998994b38b90fc6acdc0bd1164ac15d@haiku-os.org> References: <041.a998994b38b90fc6acdc0bd1164ac15d@haiku-os.org> Message-ID: <050.61c95a6d9d383f6ce6eb23104f799dfa@haiku-os.org> #1203: Haiku USB in BeOS R5 --------------------------+------------------------------------------------- Reporter: nutela | Owner: mmlr Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: x86 --------------------------+------------------------------------------------- Changes (by nutela): * summary: mutliple issues with usb stack revision 22130 => Haiku USB in BeOS R5 Comment: This was/is getting messy, sorry for messing this up. I changed the summary this should reflect issues using USB from Haiku on R5. I'll open a new bug for USB issues on Haiku. And copy paste the Haiku related ones to that. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 21 11:31:46 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 21 Mar 2008 10:31:46 -0000 Subject: [Haiku-bugs] [Haiku] #1203: Haiku USB in BeOS R5 In-Reply-To: <041.a998994b38b90fc6acdc0bd1164ac15d@haiku-os.org> References: <041.a998994b38b90fc6acdc0bd1164ac15d@haiku-os.org> Message-ID: <050.9515d60f713bfd50e9eb1d5bafca7218@haiku-os.org> #1203: Haiku USB in BeOS R5 --------------------------+------------------------------------------------- Reporter: nutela | Owner: mmlr Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: x86 --------------------------+------------------------------------------------- Comment (by nutela): NEW: revision 24493; I build and installed USB on R5 according to the instructions from Michael Lotz on Haiku-os.org "Using the Haiku USB stack". Deleted all USB related things from R5 from /boot/beos/system/... except some kodak_usb, usb_printer and USB Port 1. Boot to R5, R5 hangs on the Desktop background, no cursor, no icons, no Deskbar. This is with #define TRACE_USB and TRACE_USB_RAW and without it. Tested this also with usb_hid renamed to hid (which seems Be to have done - name the usb_hid "hid"). Also deleted usb_scsi -> always same result (1.) Must "disable user addons" to boot fully. Note1 that this didn't happen with the older stack revision 22130 (see above). Note2 I tested multiple Haiku images r 24195 IIRC with functional USB but with bugs (will create new ticket just for my wireless Logitech mx3200) Note3 the instructions in "Using the Haiku USB stack" or no longer valid for usb_raw, it resides in another folder then "objects/...." Note4: I hope I understood correctly USBKit.a is just for developing purposes, didn't install USBKit.a -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 21 11:53:36 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 21 Mar 2008 10:53:36 -0000 Subject: [Haiku-bugs] [Haiku] #1949: Haiku: wireless Logitech mx3200 keyboard and mouse + USB receiver not working correctly Message-ID: <041.c3b223b19d4d0d2f2f352fd545740f96@haiku-os.org> #1949: Haiku: wireless Logitech mx3200 keyboard and mouse + USB receiver not working correctly -------------------------+-------------------------------------------------- Reporter: nutela | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Platform: x86 | -------------------------+-------------------------------------------------- In Haiku rev 24195 on real HW with UHCI (Asus CuBX). The mouse will not work at all. The keyboard has sticky-effect, when you press a key quickly without releasing the former and release both keys (fast typing so to speak) the last key pressed is repeated quickly. This happened also in R5 with the 22130 revision see #1203 Bug me about attaching syslog -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 21 12:00:29 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 21 Mar 2008 11:00:29 -0000 Subject: [Haiku-bugs] [Haiku] #1203: Haiku USB in BeOS R5 In-Reply-To: <041.a998994b38b90fc6acdc0bd1164ac15d@haiku-os.org> References: <041.a998994b38b90fc6acdc0bd1164ac15d@haiku-os.org> Message-ID: <050.264348c16d22d9bb70a7153bc6ab55d7@haiku-os.org> #1203: Haiku USB in BeOS R5 --------------------------+------------------------------------------------- Reporter: nutela | Owner: mmlr Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: x86 --------------------------+------------------------------------------------- Comment (by nutela): Something amazing happened when I wrote the above bug (still same session!); The USB-wireless mx3200 combo works quite correctly, without sticky-key problem, after I had to "disable user addons" with revision 24493. Will rename "usb_hid" to "hid" to test scroll wheel which doesn't work. Later I will test if this has anything to do with having a ps/2 keyboard and mouse (usb->ps/2) connected to the ps/2 ports. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 21 12:18:55 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 21 Mar 2008 11:18:55 -0000 Subject: [Haiku-bugs] [Haiku] #1944: Kill command don't work with process names In-Reply-To: <038.92673db4233c8a78a2bc2c023a4462b9@haiku-os.org> References: <038.92673db4233c8a78a2bc2c023a4462b9@haiku-os.org> Message-ID: <047.ab8fc418503201e221291678524e87fa@haiku-os.org> #1944: Kill command don't work with process names ---------------------------+------------------------------------------------ Reporter: tqh | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by tqh): This bug is about kill. killall might do that, but it's not really related to the bug. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 21 12:28:34 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 21 Mar 2008 11:28:34 -0000 Subject: [Haiku-bugs] [Haiku] #1949: Haiku: wireless Logitech mx3200 keyboard and mouse + USB receiver not working correctly In-Reply-To: <041.c3b223b19d4d0d2f2f352fd545740f96@haiku-os.org> References: <041.c3b223b19d4d0d2f2f352fd545740f96@haiku-os.org> Message-ID: <050.9dd559d281e0b186e09457f63bf072b4@haiku-os.org> #1949: Haiku: wireless Logitech mx3200 keyboard and mouse + USB receiver not working correctly --------------------------+------------------------------------------------- Reporter: nutela | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: x86 --------------------------+------------------------------------------------- Comment (by emitrax): A syslog is always appreciated. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 21 13:06:25 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 21 Mar 2008 12:06:25 -0000 Subject: [Haiku-bugs] [Haiku] #1203: Haiku USB in BeOS R5 In-Reply-To: <041.a998994b38b90fc6acdc0bd1164ac15d@haiku-os.org> References: <041.a998994b38b90fc6acdc0bd1164ac15d@haiku-os.org> Message-ID: <050.b4e778c4653b8071dcd72d5b6bdb84a6@haiku-os.org> #1203: Haiku USB in BeOS R5 --------------------------+------------------------------------------------- Reporter: nutela | Owner: mmlr Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: x86 --------------------------+------------------------------------------------- Comment (by nutela): Tested with unplugged ps/2 keyboard and mouse, but has no effect, the mx3200 works ok except that the scroll wheel's horizontal abilities seems to be mapped differently, and vertical scrolling does not seem to work at all. The question remains how is this possible with the user addons disabled!? Because really my sound and video won't work when they are in ~/config/... (I have video since I put the driver in /boot/beos/system/... the echo24 however won't because of echo.settings probably) Should it matter if the usb_hid is called "usb_hid" or "hid"? Shall I test more with the usb_hid driver? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 21 13:12:48 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 21 Mar 2008 12:12:48 -0000 Subject: [Haiku-bugs] [Haiku] #1682: AddSourceDirectoryToHaikuImage doesn't work with spaces in file names In-Reply-To: <041.14ef3b7b09156af14e6cab73aca52dd6@haiku-os.org> References: <041.14ef3b7b09156af14e6cab73aca52dd6@haiku-os.org> Message-ID: <050.2e6c8301179c05434623b989baacd52e@haiku-os.org> #1682: AddSourceDirectoryToHaikuImage doesn't work with spaces in file names ---------------------------+------------------------------------------------ Reporter: ekdahl | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by ekdahl): It works as expected now. Thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 21 13:17:39 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 21 Mar 2008 12:17:39 -0000 Subject: [Haiku-bugs] [Haiku] #1682: AddSourceDirectoryToHaikuImage doesn't work with spaces in file names In-Reply-To: <041.14ef3b7b09156af14e6cab73aca52dd6@haiku-os.org> References: <041.14ef3b7b09156af14e6cab73aca52dd6@haiku-os.org> Message-ID: <050.3d553ca531d84d704dc322760956f5a2@haiku-os.org> #1682: AddSourceDirectoryToHaikuImage doesn't work with spaces in file names ---------------------------+------------------------------------------------ Reporter: ekdahl | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: fixed | Platform: All ---------------------------+------------------------------------------------ Changes (by stippi): * status: new => closed * resolution: => fixed Comment: Ok, thanks for notifying! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 21 14:18:31 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 21 Mar 2008 13:18:31 -0000 Subject: [Haiku-bugs] [Haiku] #1199: Haiku-created files with cyrillic names are not visible from R5 and vice versa. In-Reply-To: <043.51a53335ccf6c30927f9fb1dc5f4a7e9@haiku-os.org> References: <043.51a53335ccf6c30927f9fb1dc5f4a7e9@haiku-os.org> Message-ID: <052.0a535a0c3ee49689f4b7c9c92ac1eccb@haiku-os.org> #1199: Haiku-created files with cyrillic names are not visible from R5 and vice versa. -------------------------------+-------------------------------------------- Reporter: siarzhuk | Owner: bga Type: bug | Status: new Priority: low | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Comment (by siarzhuk): After #724 was fixed I have checked the state of this problem. Looks like r24498 works in right way - both cyrillic-named file system entities created in R5 and ones created in Haiku are visible from any system. Looks like the problem is solved. The question to jonas.kirilla: it is all OK now on your side? Have you any objections to close this ticked as fixed? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 21 14:59:05 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 21 Mar 2008 13:59:05 -0000 Subject: [Haiku-bugs] [Haiku] #1203: Haiku USB in BeOS R5 In-Reply-To: <041.a998994b38b90fc6acdc0bd1164ac15d@haiku-os.org> References: <041.a998994b38b90fc6acdc0bd1164ac15d@haiku-os.org> Message-ID: <050.326c883e50a7a82fb009c8871d7e620e@haiku-os.org> #1203: Haiku USB in BeOS R5 --------------------------+------------------------------------------------- Reporter: nutela | Owner: mmlr Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: x86 --------------------------+------------------------------------------------- Comment (by nutela): So this is all BIOS USB legacy support :( didn't know. When I turn it off it doesn't work of course. Makes sense at last. So R5 doesn't boot fully and hangs at the Desktop background with USB from Haiku. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 21 18:25:54 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 21 Mar 2008 17:25:54 -0000 Subject: [Haiku-bugs] [Haiku] #1203: Haiku USB in BeOS R5 In-Reply-To: <041.a998994b38b90fc6acdc0bd1164ac15d@haiku-os.org> References: <041.a998994b38b90fc6acdc0bd1164ac15d@haiku-os.org> Message-ID: <050.9337a1657b91de1d1c200588ab4abe67@haiku-os.org> #1203: Haiku USB in BeOS R5 --------------------------+------------------------------------------------- Reporter: nutela | Owner: mmlr Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: x86 --------------------------+------------------------------------------------- Comment (by siarzhuk): Have you any usb mass storage devices detached from this PC during boot? I've observed very long timeouts in such situation. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 21 20:53:41 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 21 Mar 2008 19:53:41 -0000 Subject: [Haiku-bugs] [Haiku] #1950: Garbled screen contents with true colour mode on nvidia gf2mx Message-ID: <042.f15ad8e18c31676a011caebc5344d3a8@haiku-os.org> #1950: Garbled screen contents with true colour mode on nvidia gf2mx -----------------------+---------------------------------------------------- Reporter: jopadan | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: x86 | -----------------------+---------------------------------------------------- System is a single Opteron 240 on a Gigabyte K8NNXP-940 nForce3 150 Chipsatz Mainboard. Graphics Cards: Nvidia GeForce 2 MX 32MB AGP 2x Voodoo2 12MB SLI Haiku version is current SVN trunk. Initial screen at first boot is garbled too. I don't know if any nvidia accelerant or vesa driver is in use I just use the default configuration Setting 8 and 16 bit modes works fine. 24 and 32 bit modes are garbled and you have a very hard time trying to figure out the contents -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 21 21:07:01 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 21 Mar 2008 20:07:01 -0000 Subject: [Haiku-bugs] [Haiku] #1203: Haiku USB in BeOS R5 In-Reply-To: <041.a998994b38b90fc6acdc0bd1164ac15d@haiku-os.org> References: <041.a998994b38b90fc6acdc0bd1164ac15d@haiku-os.org> Message-ID: <050.d74c8f37e5f404bf7b1d1380f82c135d@haiku-os.org> #1203: Haiku USB in BeOS R5 --------------------------+------------------------------------------------- Reporter: nutela | Owner: mmlr Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: x86 --------------------------+------------------------------------------------- Comment (by nutela): Replying to [comment:24 siarzhuk]: > Have you any usb mass storage devices detached from this PC during boot? I've observed very long timeouts in such situation. I have had no usb mass storage device *attached* during boot, so yes detached then, I shall try with an usb stick *attached*. I have however, tried booting with deleted usb_scsi (and usb_hid) with the same result. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 21 22:03:47 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 21 Mar 2008 21:03:47 -0000 Subject: [Haiku-bugs] [Haiku] #1199: Haiku-created files with cyrillic names are not visible from R5 and vice versa. In-Reply-To: <043.51a53335ccf6c30927f9fb1dc5f4a7e9@haiku-os.org> References: <043.51a53335ccf6c30927f9fb1dc5f4a7e9@haiku-os.org> Message-ID: <052.1229de2cd52aa42e2353698114612524@haiku-os.org> #1199: Haiku-created files with cyrillic names are not visible from R5 and vice versa. -------------------------------+-------------------------------------------- Reporter: siarzhuk | Owner: bga Type: bug | Status: new Priority: low | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Comment (by jonas.kirilla): I can't check as my Haiku screen is garbled at the moment. Feel free to close though. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 21 22:26:20 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 21 Mar 2008 21:26:20 -0000 Subject: [Haiku-bugs] [Haiku] #1199: Haiku-created files with cyrillic names are not visible from R5 and vice versa. In-Reply-To: <043.51a53335ccf6c30927f9fb1dc5f4a7e9@haiku-os.org> References: <043.51a53335ccf6c30927f9fb1dc5f4a7e9@haiku-os.org> Message-ID: <052.659574a9ccbab3dedd503f82a46c1e56@haiku-os.org> #1199: Haiku-created files with cyrillic names are not visible from R5 and vice versa. -------------------------------+-------------------------------------------- Reporter: siarzhuk | Owner: bga Type: bug | Status: closed Priority: low | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: fixed | Platform: All -------------------------------+-------------------------------------------- Changes (by stippi): * status: new => closed * resolution: => fixed Comment: From all the feedback so far, I am guessing that this bug is positively fixed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 22 00:34:01 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 21 Mar 2008 23:34:01 -0000 Subject: [Haiku-bugs] [Haiku] #927: [nvidia] stability problems with GeForce 7300 In-Reply-To: <040.4551861d616e1c747f375cd9bac88b12@haiku-os.org> References: <040.4551861d616e1c747f375cd9bac88b12@haiku-os.org> Message-ID: <049.0c154ae932c4f4bf70482a9f9764b2bd@haiku-os.org> #927: [nvidia] stability problems with GeForce 7300 --------------------------------------+------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: | Platform: All --------------------------------------+------------------------------------- Comment (by mmadia): 0x1d1 GeForce 7300 LE exhibits the same issue. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 22 02:30:37 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 22 Mar 2008 01:30:37 -0000 Subject: [Haiku-bugs] [Haiku] #1950: Garbled screen contents with true colour mode on nvidia gf2mx In-Reply-To: <042.f15ad8e18c31676a011caebc5344d3a8@haiku-os.org> References: <042.f15ad8e18c31676a011caebc5344d3a8@haiku-os.org> Message-ID: <051.e2c5071ae8a69960e3c3484df86da27a@haiku-os.org> #1950: Garbled screen contents with true colour mode on nvidia gf2mx ------------------------+--------------------------------------------------- Reporter: jopadan | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: x86 ------------------------+--------------------------------------------------- Comment (by jonas.kirilla): I see this too with a nVidia FX5500 card. I think r24494 is where it starts happening, so I suppose it's got to do with MTRR. The screen looks like the accelerant isn't working: no block fills and no block moves, everything shown leaves traces. (Even the Shutdown window leaves its mark, already at bootup!) Can provide serial and screenshots tomorrow if desired. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 22 07:47:40 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 22 Mar 2008 06:47:40 -0000 Subject: [Haiku-bugs] [Haiku] #1951: Tracker Crashes on replicant drag from Pulse to desktop Message-ID: <043.0b669dc478b15c06168feedb35872480@haiku-os.org> #1951: Tracker Crashes on replicant drag from Pulse to desktop ----------------------------------+----------------------------------------- Reporter: tigerdog | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Platform: x86 | ----------------------------------+----------------------------------------- To reproduce: enable "show replicants" start pulse drag cpu number replicant to desktop **tracker crashes -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 22 08:00:43 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 22 Mar 2008 07:00:43 -0000 Subject: [Haiku-bugs] [Haiku] #1466: GUI doesn't redraw / freezes In-Reply-To: <050.092965f6d638178942edd6f63de6458f@haiku-os.org> References: <050.092965f6d638178942edd6f63de6458f@haiku-os.org> Message-ID: <059.c98f25f38fc1628b51d1ff447f6d2cbf@haiku-os.org> #1466: GUI doesn't redraw / freezes ---------------------------------+------------------------------------------ Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by tigerdog): Replying to [comment:3 jackburton]: > There was a problem with _BWidthBuffer_, used by Tracker's PoseView, which could've caused this problem. It was was fixed in r24096. I can't reproduce this problem anymore. > Can someone confirm ? I tried to cause the problem under revision 24493 but could not duplicate. I resized the "Filename" column back and forth for > 60 seconds. Display sometimes lagged but never froze. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 22 14:31:02 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 22 Mar 2008 13:31:02 -0000 Subject: [Haiku-bugs] [Haiku] #1952: compilation stops crosscompiling x86 haiku image on linux-ppc Message-ID: <044.602eab6cabde8e6960bb6f0cddb3e209@haiku-os.org> #1952: compilation stops crosscompiling x86 haiku image on linux-ppc --------------------------+------------------------------------------------- Reporter: tradewind | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Platform: All | --------------------------+------------------------------------------------- The compilation stops on bfs.h, claiming that {{{__swap_int }}}is undefined in the scope. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 22 14:44:18 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 22 Mar 2008 13:44:18 -0000 Subject: [Haiku-bugs] [Haiku] #1711: Haiku stops booting at allocate_commpage_entry(4, 34) In-Reply-To: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> References: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> Message-ID: <048.18fa8c1f1eb566ffd93c98a7c692c1ee@haiku-os.org> #1711: Haiku stops booting at allocate_commpage_entry(4, 34) ----------------------------+----------------------------------------------- Reporter: euan | Owner: korli Type: bug | Status: reopened Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by korli): Could you please check again with r24494 ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 22 15:16:54 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 22 Mar 2008 14:16:54 -0000 Subject: [Haiku-bugs] [Haiku] #1203: Haiku USB in BeOS R5 In-Reply-To: <041.a998994b38b90fc6acdc0bd1164ac15d@haiku-os.org> References: <041.a998994b38b90fc6acdc0bd1164ac15d@haiku-os.org> Message-ID: <050.b8c92fe35158b3325ef09664622d99be@haiku-os.org> #1203: Haiku USB in BeOS R5 --------------------------+------------------------------------------------- Reporter: nutela | Owner: mmlr Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: x86 --------------------------+------------------------------------------------- Comment (by nutela): Booted with USB stick with same result. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 22 15:30:59 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 22 Mar 2008 14:30:59 -0000 Subject: [Haiku-bugs] [Haiku] #1952: compilation stops crosscompiling x86 haiku image on linux-ppc In-Reply-To: <044.602eab6cabde8e6960bb6f0cddb3e209@haiku-os.org> References: <044.602eab6cabde8e6960bb6f0cddb3e209@haiku-os.org> Message-ID: <053.3851589246a4254718c5d11f1e9230e8@haiku-os.org> #1952: compilation stops crosscompiling x86 haiku image on linux-ppc ---------------------------+------------------------------------------------ Reporter: tradewind | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by pieterpan): A few days ago I could not build haiku after an update. I tried again today with a complete fresh svn checkout (both trunk and buildtools) of r24521 on ubuntu linux. Not sure what's going on, but it fails to build gcc. Might be related to this ticket, see attachment with the full checkout and build output. I zipped it, cause it's kinda large. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 22 15:49:45 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 22 Mar 2008 14:49:45 -0000 Subject: [Haiku-bugs] [Haiku] #717: kernel: Panic out of range In-Reply-To: <053.77529c3ae36c88bf29329a76e8ecfba6@haiku-os.org> References: <053.77529c3ae36c88bf29329a76e8ecfba6@haiku-os.org> Message-ID: <062.334b5deaedacd07cb88e2ce6aaf9f455@haiku-os.org> #717: kernel: Panic out of range ---------------------------------+------------------------------------------ Reporter: kutspam at wolke7.net | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: System/Kernel | Version: Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by nielx): How's this one doing? Does it still occur? Is there a backtrace somewhere? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 22 17:02:47 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 22 Mar 2008 16:02:47 -0000 Subject: [Haiku-bugs] [Haiku] #1953: Copying large amounts of data fills memory/cache crashes Haiku. Message-ID: <041.980c74acf11a77e044eb5e9876ef5aee@haiku-os.org> #1953: Copying large amounts of data fills memory/cache crashes Haiku. -----------------------+---------------------------------------------------- Reporter: kvdman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- I have tested copying ~600mb from a Haiku partition to another Haiku partition within Haiku rev.24521 with 512mb RAM under Parallels, Qemu, Vmware & Virtual Box. The memory/cache will fill and bring Haiku to KDL. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 22 17:12:29 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 22 Mar 2008 16:12:29 -0000 Subject: [Haiku-bugs] [Haiku] #1952: compilation stops crosscompiling x86 haiku image on linux-ppc In-Reply-To: <044.602eab6cabde8e6960bb6f0cddb3e209@haiku-os.org> References: <044.602eab6cabde8e6960bb6f0cddb3e209@haiku-os.org> Message-ID: <053.eff0c9d6a40008b613c8d5449408607e@haiku-os.org> #1952: compilation stops crosscompiling x86 haiku image on linux-ppc ---------------------------+------------------------------------------------ Reporter: tradewind | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by umccullough): The failed build on linux x86 is a new issue due to Ingo's recent commits (i can confirm it here). You should enter a different bug for that since it's entirely unrelated to the PPC host platform issue. I'll also send a note to the list since I stumbled across this as well last night and reverted to a prior version to succeed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 22 17:55:15 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 22 Mar 2008 16:55:15 -0000 Subject: [Haiku-bugs] [Haiku] #1954: Cross tools build failure on linux Message-ID: <044.21996c09e1d941437ddef98f8dba6123@haiku-os.org> #1954: Cross tools build failure on linux -----------------------+---------------------------------------------------- Reporter: pieterpan | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- I can no longer build the buildtools from a fresh svn checkout of haiku. I hijacked #1952 to report this (so sorry), so now I've opened my own ticket. Reverting the buildtools to r23127 as reported by Urias helps. See the attached file with the full checkout and build process (same as in #1952) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 22 17:59:26 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 22 Mar 2008 16:59:26 -0000 Subject: [Haiku-bugs] [Haiku] #1954: Cross tools build failure on linux In-Reply-To: <044.21996c09e1d941437ddef98f8dba6123@haiku-os.org> References: <044.21996c09e1d941437ddef98f8dba6123@haiku-os.org> Message-ID: <053.457190bcfcadc60fce6600c67718c539@haiku-os.org> #1954: Cross tools build failure on linux ---------------------------+------------------------------------------------ Reporter: pieterpan | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Changes (by pieterpan): * owner: axeld => bonefish * component: - General => Build System -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 22 19:45:55 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 22 Mar 2008 18:45:55 -0000 Subject: [Haiku-bugs] [Haiku] #1855: Glibc wide char functions are disabled In-Reply-To: <045.34bab0da7c7771105187bde6b57a07a9@haiku-os.org> References: <045.34bab0da7c7771105187bde6b57a07a9@haiku-os.org> Message-ID: <054.b6f80230217e7a183e25ba27b555eae2@haiku-os.org> #1855: Glibc wide char functions are disabled --------------------------------+------------------------------------------- Reporter: jackburton | Owner: jackburton Type: bug | Status: assigned Priority: high | Milestone: R1/alpha1 Component: System/libroot.so | Version: R1 development Resolution: | Platform: All --------------------------------+------------------------------------------- Comment (by nielx): Replying to [comment:6 jackburton]: > depends on #1881. By the way, don't we have bug dependency tracking ? I've got a Trac plugin for that, which is unfortunately a Trac 0.11 thing. I will have to wait for Trac 0.11 to stabilize before I can use it. Sorry! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 23 00:09:31 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 22 Mar 2008 23:09:31 -0000 Subject: [Haiku-bugs] [Haiku] #1537: Freecell 0.92 quits responding In-Reply-To: <042.ddea47a145b387ae5cc52984d69fbc15@haiku-os.org> References: <042.ddea47a145b387ae5cc52984d69fbc15@haiku-os.org> Message-ID: <051.40d4eaf1958228f405895d75497932cd@haiku-os.org> #1537: Freecell 0.92 quits responding ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by scottmc): I checked again, this time on r24493 and I now got it to crash and have attached the debug output. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 23 00:37:26 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 22 Mar 2008 23:37:26 -0000 Subject: [Haiku-bugs] [Haiku] #1955: Media Player won't respond after Restarting Media Server Message-ID: <042.0ecb0264e387fa34004c108d0befbb04@haiku-os.org> #1955: Media Player won't respond after Restarting Media Server ---------------------------+------------------------------------------------ Reporter: scottmc | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Audio & Video | Version: R1 development Platform: All | ---------------------------+------------------------------------------------ I tried to see what would happen when playing a song with Media Player and then restarting the Media Server during the song. The result is that after the Media Server is restarted that Media Player refuses to resume or shut-down. VLC however will resume if you press the play button. I did a quick search but didn't find any other tickets that matched. Tested on r24493 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 23 02:38:05 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 23 Mar 2008 01:38:05 -0000 Subject: [Haiku-bugs] [Haiku] #1956: Garbage In Files Message-ID: <043.b26038f2dc2fcacc60d26d407839e6d0@haiku-os.org> #1956: Garbage In Files ---------------------------+------------------------------------------------ Reporter: bonefish | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Platform: All | ---------------------------+------------------------------------------------ r24528, VMware This is somewhat vague... While playing with various build tools, several times some file would suddenly contain garbage. E.g. some large text file would contain one or more chunks of binary data. I believe all of the affected files were created or edited during the session, but were OK in the meantime. I'll try to add some more info when I encounter the issue the next time. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 23 13:14:06 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 23 Mar 2008 12:14:06 -0000 Subject: [Haiku-bugs] [Haiku] #1222: check if AboutHaiku lists an acknowledgment for all packages In-Reply-To: <045.849bde80d50effc77930688f383230ab@haiku-os.org> References: <045.849bde80d50effc77930688f383230ab@haiku-os.org> Message-ID: <054.715cb2fc2104c6f719586bf3c5cbee25@haiku-os.org> #1222: check if AboutHaiku lists an acknowledgment for all packages -------------------------+-------------------------------------------------- Reporter: wkornewald | Owner: Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: - General | Version: R1 development Resolution: | Platform: All -------------------------+-------------------------------------------------- Comment (by emitrax): What's the status of this ticket? And what do you think it is the best way to proceed for a non-developer user? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 23 17:04:16 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 23 Mar 2008 16:04:16 -0000 Subject: [Haiku-bugs] [Haiku] #1957: Command Line FTP app has Name collision when connecting to an FTP site Message-ID: <042.993f6310d8fad8b8b408b4590966d72f@haiku-os.org> #1957: Command Line FTP app has Name collision when connecting to an FTP site -----------------------+---------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- When testing the FTP command line client out I noticed that in Haiku I was getting a Name collision when logging into a certain site, but when using the FTP command line client from Ubuntu to connect to that same site no such name collision occurs. Not sure if this is FTP related or if there's a mis-match of some sort with font names? Anyway, I've attached a screenshot showing a bit more detail. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 23 17:03:29 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 23 Mar 2008 16:03:29 -0000 Subject: [Haiku-bugs] [Haiku] #1222: check if AboutHaiku lists an acknowledgment for all packages In-Reply-To: <045.849bde80d50effc77930688f383230ab@haiku-os.org> References: <045.849bde80d50effc77930688f383230ab@haiku-os.org> Message-ID: <054.4cfd5e572c8bddec29b104ef37d5f471@haiku-os.org> #1222: check if AboutHaiku lists an acknowledgment for all packages -------------------------+-------------------------------------------------- Reporter: wkornewald | Owner: Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: - General | Version: R1 development Resolution: | Platform: All -------------------------+-------------------------------------------------- Comment (by nielx): Funnily enought I just thought about this ticket too, this morning while I was sitting in my car. There once was a thread on the mailing list on how to do this. Here's my take on the problem: let's just make a list of all non-Haiku software that is currently used. Put this in a file in the root of the trunk and list the: * Name of the package and the version * The license * The copyrightholder. If there is more than one, just put down 'several copyright holders'. * The URL where more information on the package can be found. The build system would 'cat' this file into a C-file, which is imported into the AboutHaiku application. This will not make these copyright statements very appealing and sexy, but remember: it is a legal requirement, rather than something our users would look at. (That's just my take). A non-coder could start compiling that list. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 23 17:12:30 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 23 Mar 2008 16:12:30 -0000 Subject: [Haiku-bugs] [Haiku] #1958: FTP put and get seem slow Message-ID: <042.d9ad69d54698c70787999f427815dacb@haiku-os.org> #1958: FTP put and get seem slow --------------------------------+------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Platform: All | --------------------------------+------------------------------------------- When testing the FTP command line client it seems that Haiku's FTP is slower than the one with Ubuntu. When transferring files to and from the same site the Haiku transfer times are about half the speed of Ubuntu's, but this was using Haiku under VMWARE on Ubuntu so that "might" be the cause? Anyways it appears that #1414 is no longer an issue as originally written since I was able to transfer a 7meg file without it stopping, both put and get. So #1414 can be closed, but there still seems to be a speed issue, so use this as the new bug report as #1414 was reporting 2 different bugs and original one is fixed. Attached are screenshots showing Haiku vs. Ubuntu on put and get times. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 23 17:30:35 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 23 Mar 2008 16:30:35 -0000 Subject: [Haiku-bugs] [Haiku] #1956: Garbage In Files In-Reply-To: <043.b26038f2dc2fcacc60d26d407839e6d0@haiku-os.org> References: <043.b26038f2dc2fcacc60d26d407839e6d0@haiku-os.org> Message-ID: <052.376f6eb82a698caa8efa801e1d77517b@haiku-os.org> #1956: Garbage In Files ----------------------------+----------------------------------------------- Reporter: bonefish | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by axeld): Did you ever run low on memory during working? Were these newly created files? Because if you didn't, the files would be kept in memory all the time, and therefore, something would actively clobber it. If they were new files and memory was low, eventually something marked the pages as clean, so they would never be written back to disk. Does that garbage look like something that might have been on disk previously? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 23 17:33:37 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 23 Mar 2008 16:33:37 -0000 Subject: [Haiku-bugs] [Haiku] #1959: nVidia Corporation NV11 [GeForce2 Go]: drawing problems after new splash screen Message-ID: <040.17c8090d9b429398540eaed4e454250d@haiku-os.org> #1959: nVidia Corporation NV11 [GeForce2 Go]: drawing problems after new splash screen -------------------------------------+-------------------------------------- Reporter: nielx | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Platform: All | -------------------------------------+-------------------------------------- After updating my machine to the latest subversion revision, the screen stops drawing correctly. The black boot screen (with logo) seems to be copied twice to the top of the screen. The main color of the desktop is black, and the fonts and borders are drawn. The windows suffer the same problems: it's all very black. When I drag a window to another location, it needs a few seconds to become visible again. My resolution is 1024 x 768. I'm sorry I cannot pinpoint to a more exact point in time, but it my previous checkout was from before the new boot screen with icons. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 23 17:36:32 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 23 Mar 2008 16:36:32 -0000 Subject: [Haiku-bugs] [Haiku] #1959: nVidia Corporation NV11 [GeForce2 Go]: drawing problems after new splash screen In-Reply-To: <040.17c8090d9b429398540eaed4e454250d@haiku-os.org> References: <040.17c8090d9b429398540eaed4e454250d@haiku-os.org> Message-ID: <049.bda9f9cd5a8956f9884c22b6c5dc804c@haiku-os.org> #1959: nVidia Corporation NV11 [GeForce2 Go]: drawing problems after new splash screen --------------------------------------+------------------------------------- Reporter: nielx | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: | Platform: All --------------------------------------+------------------------------------- Changes (by nielx): * cc: stippi (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 23 17:37:51 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 23 Mar 2008 16:37:51 -0000 Subject: [Haiku-bugs] [Haiku] #1947: [Software Valet] fails to install ButterFly pkg In-Reply-To: <040.90189cb09709edd4c8bc4ae79f81a4ad@haiku-os.org> References: <040.90189cb09709edd4c8bc4ae79f81a4ad@haiku-os.org> Message-ID: <049.e1c6561d70678edb3145e4a4e01bf798@haiku-os.org> #1947: [Software Valet] fails to install ButterFly pkg -------------------------------+-------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Support Kit | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Comment (by axeld): Does PackageInstaller installs it correctly? What package version exactly? Can you provide a link? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 23 18:06:39 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 23 Mar 2008 17:06:39 -0000 Subject: [Haiku-bugs] [Haiku] #1711: Haiku stops booting at allocate_commpage_entry(4, 34) In-Reply-To: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> References: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> Message-ID: <048.7810283d5961b7f3cc6eae2b97808f17@haiku-os.org> #1711: Haiku stops booting at allocate_commpage_entry(4, 34) ----------------------------+----------------------------------------------- Reporter: euan | Owner: korli Type: bug | Status: reopened Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by ddew): Still won't boot. Now it resets right after allocating slot 0 judging from what I had time to see. The system resets during the allocation making hard to catch a glimpse of exactly what's being done and I don't have serial access to the machine. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 23 18:40:42 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 23 Mar 2008 17:40:42 -0000 Subject: [Haiku-bugs] [Haiku] #1956: Garbage In Files In-Reply-To: <043.b26038f2dc2fcacc60d26d407839e6d0@haiku-os.org> References: <043.b26038f2dc2fcacc60d26d407839e6d0@haiku-os.org> Message-ID: <052.2fe438d78cf483d8f2a9b1e13fbc6bc0@haiku-os.org> #1956: Garbage In Files ----------------------------+----------------------------------------------- Reporter: bonefish | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by bonefish): Replying to [comment:1 axeld]: > Did you ever run low on memory during working? Usually after a while of working the ProcessController memory bar is full and red. So I suppose it could very well be that in all instances this was the case too. > Were these newly created files? The recent occurrences definitely were. I recall several times that a Makefile created by the binutils/gcc build system would suddenly contain binary data. I had a case where a header file from the texinfo sources was broken. I didn't edit it before, but I think I unzipped the sources earlier in the same session, so that file was newly created in the session, too. I defintely had one occurrence when a perl source file that was not new was garbled. This was before your recent BFS journal related fixes, though, and I may have had to terminate an earlier session without syncing. So this might not be related. > Because if you didn't, the files would be kept in memory all the time, and therefore, something would actively clobber it. > > If they were new files and memory was low, eventually something marked the pages as clean, so they would never be written back to disk. Does that garbage look like something that might have been on disk previously? I didn't examine that any closer, also not whether the garbage was page size. Will do the next time I encounter the problem. I guess a small test suite straining FS/file cache/VM would be a good idea. There still seem to be a few issues with those and when encountering those in the "wild" one usually is doing something else and is not really motivated to examine the problem. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 23 18:51:39 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 23 Mar 2008 17:51:39 -0000 Subject: [Haiku-bugs] [Haiku] #1222: check if AboutHaiku lists an acknowledgment for all packages In-Reply-To: <045.849bde80d50effc77930688f383230ab@haiku-os.org> References: <045.849bde80d50effc77930688f383230ab@haiku-os.org> Message-ID: <054.d293dd5c568acd50286bc1de60e36760@haiku-os.org> #1222: check if AboutHaiku lists an acknowledgment for all packages -------------------------+-------------------------------------------------- Reporter: wkornewald | Owner: Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: - General | Version: R1 development Resolution: | Platform: All -------------------------+-------------------------------------------------- Changes (by bonefish): * cc: bonefish (removed) Comment: Replying to [comment:5 nielx]: > Funnily enought I just thought about this ticket too, this morning while I was sitting in my car. There once was a thread on the mailing list on how to do this. Here's my take on the problem: let's just make a list of all non-Haiku software that is currently used. Put this in a file in the root of the trunk and list the: ... Well, in the end it doesn't make much difference whether you list the files in a separate file or in the AboutSystem sources. The main work is compiling the list. Thanks for attacking this. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 23 20:16:12 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 23 Mar 2008 19:16:12 -0000 Subject: [Haiku-bugs] [Haiku] #1950: Garbled screen contents with true colour mode on nvidia gf2mx In-Reply-To: <042.f15ad8e18c31676a011caebc5344d3a8@haiku-os.org> References: <042.f15ad8e18c31676a011caebc5344d3a8@haiku-os.org> Message-ID: <051.df83bfc58ff4c02170849cd543c3960f@haiku-os.org> #1950: Garbled screen contents with true colour mode on nvidia gf2mx ------------------------+--------------------------------------------------- Reporter: jopadan | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: x86 ------------------------+--------------------------------------------------- Comment (by jonas.kirilla): Screenshots http://www.kirilla.com/tmp/garbledmadness/ -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 23 20:17:43 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 23 Mar 2008 19:17:43 -0000 Subject: [Haiku-bugs] [Haiku] #1959: nVidia Corporation NV11 [GeForce2 Go]: drawing problems after new splash screen In-Reply-To: <040.17c8090d9b429398540eaed4e454250d@haiku-os.org> References: <040.17c8090d9b429398540eaed4e454250d@haiku-os.org> Message-ID: <049.af752f2c97453a76bd98c60311599008@haiku-os.org> #1959: nVidia Corporation NV11 [GeForce2 Go]: drawing problems after new splash screen --------------------------------------+------------------------------------- Reporter: nielx | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: | Platform: All --------------------------------------+------------------------------------- Changes (by axeld): * cc: korli (added) * priority: normal => high * milestone: R1 => R1/alpha1 Comment: This is most probably the cause of Jerome's recent MTRR changes. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 23 20:25:04 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 23 Mar 2008 19:25:04 -0000 Subject: [Haiku-bugs] [Haiku] #1957: Command Line FTP app has Name collision when connecting to an FTP site In-Reply-To: <042.993f6310d8fad8b8b408b4590966d72f@haiku-os.org> References: <042.993f6310d8fad8b8b408b4590966d72f@haiku-os.org> Message-ID: <051.3d68dd5e8860597a874708c0c534316e@haiku-os.org> #1957: Command Line FTP app has Name collision when connecting to an FTP site ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: low | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Changes (by axeld): * priority: normal => low Comment: This is an issue of our termcap file when ncurses parses it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 23 21:12:14 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 23 Mar 2008 20:12:14 -0000 Subject: [Haiku-bugs] [Haiku] #1909: emuxki/midi related KDLs? In-Reply-To: <048.7c433231494081c4264c03b82f3ce97f@haiku-os.org> References: <048.7c433231494081c4264c03b82f3ce97f@haiku-os.org> Message-ID: <057.b70f8840ccbc3b761f5353bead31453e@haiku-os.org> #1909: emuxki/midi related KDLs? ----------------------------+----------------------------------------------- Reporter: jonas.kirilla | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by jonas.kirilla): I hope syslog and syslog.old is good enough. The serial output won't fit in SerialConnect's buffer. Syslog.old was too large for Trac, so I had to zip it. Sorry about that. Let me know if you want me to try something else or find a better log. BTW, having enabled TRACE_DEVFS, moving the mouse results in exceptionally large CPU load, kernel side, in 2 threads, one being the USB mouse watcher thread in the input_server and the other being the multi addon thread in the media_addon_server, the one KDL:ing in screenshot: http://dev.haiku- os.org/attachment/ticket/1909/DSC03665.jpg I find this strange. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 23 21:15:42 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 23 Mar 2008 20:15:42 -0000 Subject: [Haiku-bugs] [Haiku] #1959: nVidia Corporation NV11 [GeForce2 Go]: drawing problems after new splash screen In-Reply-To: <040.17c8090d9b429398540eaed4e454250d@haiku-os.org> References: <040.17c8090d9b429398540eaed4e454250d@haiku-os.org> Message-ID: <049.155e96626c92924aa5e2258031c9ca3d@haiku-os.org> #1959: nVidia Corporation NV11 [GeForce2 Go]: drawing problems after new splash screen --------------------------------------+------------------------------------- Reporter: nielx | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: | Platform: All --------------------------------------+------------------------------------- Comment (by jonas.kirilla): This could be a duplicate of/related to #1950. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 23 22:14:44 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 23 Mar 2008 21:14:44 -0000 Subject: [Haiku-bugs] [Haiku] #1949: Haiku: wireless Logitech mx3200 keyboard and mouse + USB receiver not working correctly In-Reply-To: <041.c3b223b19d4d0d2f2f352fd545740f96@haiku-os.org> References: <041.c3b223b19d4d0d2f2f352fd545740f96@haiku-os.org> Message-ID: <050.660c9d1658919622d2312704eab57258@haiku-os.org> #1949: Haiku: wireless Logitech mx3200 keyboard and mouse + USB receiver not working correctly --------------------------+------------------------------------------------- Reporter: nutela | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: x86 --------------------------+------------------------------------------------- Comment (by nutela): attached part of syslog and usb_dev_info output -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 23 22:39:26 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 23 Mar 2008 21:39:26 -0000 Subject: [Haiku-bugs] [Haiku] #1960: Terminal crash on resize Message-ID: <040.7bdfa53a9c29233f892db4fa7a580f73@haiku-os.org> #1960: Terminal crash on resize -------------------------------+-------------------------------------------- Reporter: thorn | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Platform: x86 | -------------------------------+-------------------------------------------- serial log: {{{ vm_soft_fault: va 0x6e656877 not covered by area in address space vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x6e656877, ip 0x79dfa7, write 0, user 1, thread 0x85 vm_page_fault: sending team "Terminal" 0x55 SIGSEGV, ip 0x79dfa7 ("libroot.so_seg0ro" +0x2afa7) stack trace: 0x0079e8a9 (libroot.so_seg0ro + 0x2b8a9) 0x0079f4d4 (libroot.so_seg0ro + 0x2c4d4) 0x002e8e34 (libbe.so_seg0ro + 0xb3e34) 0x002e9399 (libbe.so_seg0ro + 0xb4399) 0x002ea1a6 (libbe.so_seg0ro + 0xb51a6) 0x00382ce6 (libbe.so_seg0ro + 0x14dce6) 0x00383118 (libbe.so_seg0ro + 0x14e118) 0x00382e26 (libbe.so_seg0ro + 0x14de26) 0x003831aa (libbe.so_seg0ro + 0x14e1aa) 0x00382e26 (libbe.so_seg0ro + 0x14de26) 0x003831aa (libbe.so_seg0ro + 0x14e1aa) 0x00382e26 (libbe.so_seg0ro + 0x14de26) 0x003831aa (libbe.so_seg0ro + 0x14e1aa) 0x00382e26 (libbe.so_seg0ro + 0x14de26) 0x0038b863 (libbe.so_seg0ro + 0x156863) 0x00386b0e (libbe.so_seg0ro + 0x151b0e) 0x0038b4a4 (libbe.so_seg0ro + 0x1564a4) 0x002e4c6b (libbe.so_seg0ro + 0xafc6b) 0x0079452c (libroot.so_seg0ro + 0x2152c) 0x700c1fec (w>Terminal 1_133_stack + 0x3ffec) vm_soft_fault: va 0x0 not covered by area in address space vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x0, ip 0x800935c8, write 0, user 0, thread 0x85 debug_server: Thread 133 entered the debugger: Segment violation stack trace, current PC 0x79dfa7 malloc__Q28BPrivate10threadHeapUl + 0x4e3: (0x700c177c) 0x79e8a9 malloc + 0x145 (0x700c17ac) 0x79f4d4 realloc + 0x114 (0x700c17dc) 0x2e8e34 _ResizeData__8BMessagell + 0xd0 (0x700c180c) 0x2e9399 AddData__8BMessagePCcUlPCvlbl + 0xed (0x700c184c) 0x2ea1a6 AddPoint__8BMessagePCcG6BPoint + 0x36 (0x700c188c) 0x382ce6 _MoveTo__5BViewll + 0xa2 (0x700c192c) 0x383118 _ParentResizedBy__5BViewll + 0x1a8 (0x700c199c) 0x382e26 _ResizeBy__5BViewll + 0x76 (0x700c1a2c) 0x3831aa _ParentResizedBy__5BViewll + 0x23a (0x700c1a8c) 0x382e26 _ResizeBy__5BViewll + 0x76 (0x700c1b1c) 0x3831aa _ParentResizedBy__5BViewll + 0x23a (0x700c1b7c) 0x382e26 _ResizeBy__5BViewll + 0x76 (0x700c1c0c) 0x3831aa _ParentResizedBy__5BViewll + 0x23a (0x700c1c6c) 0x382e26 _ResizeBy__5BViewll + 0x76 (0x700c1cfc) 0x38b863 _AdoptResize__7BWindow + 0xc3 (0x700c1d4c) 0x386b0e DispatchMessage__7BWindowP8BMessageP8BHandler + 0x412 (0x700c1f1c) 0x38b4a4 task_looper__7BWindow + 0x270 (0x700c1f7c) 0x2e4c6b _task0___7BLooperPv + 0x3f (0x700c1fac) 0x79452c _get_next_team_info + 0x5c (closest symbol) }}} gdb {{{ #0 0xffff0104 in ?? () #1 0x00799dd0 in BPrivate::hoardYield () from /boot/beos/system/lib/libroot.so #2 0x00799d7f in BPrivate::hoardLock () from /boot/beos/system/lib/libroot.so #3 0x0079db5a in BPrivate::threadHeap::malloc () from /boot/beos/system/lib/libroot.so #4 0x0079e8a9 in malloc () from /boot/beos/system/lib/libroot.so #5 0x002e4cde in BLooper::ReadRawFromPort () from /boot/beos/system/lib/libbe.so #6 0x002e4d4e in BLooper::ReadMessageFromPort () from /boot/beos/system/lib/libbe.so #7 0x002e43ef in BLooper::MessageFromPort () from /boot/beos/system/lib/libbe.so #8 0x002e4edb in BLooper::task_looper () from /boot/beos/system/lib/libbe.so #9 0x002d9401 in BApplication::Run () from /boot/beos/system/lib/libbe.so #10 0x0021450b in main () }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 24 00:19:45 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 23 Mar 2008 23:19:45 -0000 Subject: [Haiku-bugs] [Haiku] #1954: Cross tools build failure on linux In-Reply-To: <044.21996c09e1d941437ddef98f8dba6123@haiku-os.org> References: <044.21996c09e1d941437ddef98f8dba6123@haiku-os.org> Message-ID: <053.cffe73e38b4f3705a6ec879e6ded1f56@haiku-os.org> #1954: Cross tools build failure on linux ---------------------------+------------------------------------------------ Reporter: pieterpan | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: fixed | Platform: All ---------------------------+------------------------------------------------ Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: Fixed in r24542. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 24 00:32:36 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 23 Mar 2008 23:32:36 -0000 Subject: [Haiku-bugs] [Haiku] #1961: files downloaded or copied from CDs are saved to ram and are not sent to hardrive until shutdown Message-ID: <042.ffad4aa78706436f3f6ec4d69fcde40a@haiku-os.org> #1961: files downloaded or copied from CDs are saved to ram and are not sent to hardrive until shutdown -----------------------+---------------------------------------------------- Reporter: qyellow | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- Running Revision 24470 on real hardware. When files are downloaded via webbrowser or svn etc the files take up immediate room in ram, this space is not released until the files created/downloaded are deleted. Same goes for anything copied from CDs, files go to ram and not harddrive. It seems the files are not written to the harddrive until Haiku is shutdown. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 24 01:50:55 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 24 Mar 2008 00:50:55 -0000 Subject: [Haiku-bugs] [Haiku] #1961: files downloaded or copied from CDs are saved to ram and are not sent to hardrive until shutdown In-Reply-To: <042.ffad4aa78706436f3f6ec4d69fcde40a@haiku-os.org> References: <042.ffad4aa78706436f3f6ec4d69fcde40a@haiku-os.org> Message-ID: <051.c024ac76b5ede6541c3ee86bdf8027ed@haiku-os.org> #1961: files downloaded or copied from CDs are saved to ram and are not sent to hardrive until shutdown ------------------------+--------------------------------------------------- Reporter: qyellow | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by ithamar): did you try doing a sync from a Terminal? On shutdown/restart a sync is done automagicly. I think if you have enough memory the cached file data might stay in memory for quite a while.... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 24 02:07:08 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 24 Mar 2008 01:07:08 -0000 Subject: [Haiku-bugs] [Haiku] #1961: files downloaded or copied from CDs are saved to ram and are not sent to hardrive until shutdown In-Reply-To: <042.ffad4aa78706436f3f6ec4d69fcde40a@haiku-os.org> References: <042.ffad4aa78706436f3f6ec4d69fcde40a@haiku-os.org> Message-ID: <051.dbb5f0d9a92f37e21e0d859457c8b56c@haiku-os.org> #1961: files downloaded or copied from CDs are saved to ram and are not sent to hardrive until shutdown ----------------------------+----------------------------------------------- Reporter: qyellow | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Changes (by anevilyak): * component: - General => System/Kernel Comment: I believe this is a known issue..there needs to be a thread that sweeps the cache periodically and writes back pages beyond a certain age. This may go hand in hand with needing a proper I/O scheduler. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 24 02:34:03 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 24 Mar 2008 01:34:03 -0000 Subject: [Haiku-bugs] [Haiku] #1961: files downloaded or copied from CDs are saved to ram and are not sent to hardrive until shutdown In-Reply-To: <042.ffad4aa78706436f3f6ec4d69fcde40a@haiku-os.org> References: <042.ffad4aa78706436f3f6ec4d69fcde40a@haiku-os.org> Message-ID: <051.e9348f13fd8d0c73f4e27cbcd8267901@haiku-os.org> #1961: files downloaded or copied from CDs are saved to ram and are not sent to hardrive until shutdown ---------------------------+------------------------------------------------ Reporter: qyellow | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Changes (by bonefish): * component: System/Kernel => Applications Comment: There is a thread writing back changes to disk -- it's called "page writer" and does its job more or less well. The kernel uses all available memory for caching and releases that memory only when needed elsewhere. A "sync" will not free any memory; it will only write changes back to disk, still keeping the data in the cache. When watching ProcessController during a Haiku session, particularly when working with many files, it will slowly and steadily (or sometimes even quickly) show an increasing memory usage until the memory bar is full and red. After that it will usually remain that way (unless you delete the cached files). So, if the assumption that nothing is written to disk is only based on the fact that process controller from some point on always shows full memory, it is not correct. You can verify that by dropping into the kernel debugger and check the modified pages count the "page_stats" command prints. ProcessController needs to be adjusted. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 24 02:37:23 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 24 Mar 2008 01:37:23 -0000 Subject: [Haiku-bugs] [Haiku] #1961: files downloaded or copied from CDs are saved to ram and are not sent to hardrive until shutdown In-Reply-To: <042.ffad4aa78706436f3f6ec4d69fcde40a@haiku-os.org> References: <042.ffad4aa78706436f3f6ec4d69fcde40a@haiku-os.org> Message-ID: <051.d0654f7349fd597103db64e8017e7c36@haiku-os.org> #1961: files downloaded or copied from CDs are saved to ram and are not sent to hardrive until shutdown ---------------------------+------------------------------------------------ Reporter: qyellow | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by anevilyak): Ah...thanks for the update, I didn't realize that was done. Is that by any chance why doing an svn checkout from within Haiku shows ~950MB in use in ProcessController afterwards? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 24 03:48:50 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 24 Mar 2008 02:48:50 -0000 Subject: [Haiku-bugs] [Haiku] #1961: files downloaded or copied from CDs are saved to ram and are not sent to hardrive until shutdown In-Reply-To: <042.ffad4aa78706436f3f6ec4d69fcde40a@haiku-os.org> References: <042.ffad4aa78706436f3f6ec4d69fcde40a@haiku-os.org> Message-ID: <051.c6feb268d6879e446ddb97f56fb4698f@haiku-os.org> #1961: files downloaded or copied from CDs are saved to ram and are not sent to hardrive until shutdown ---------------------------+------------------------------------------------ Reporter: qyellow | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by bonefish): Replying to [comment:4 anevilyak]: > Ah...thanks for the update, I didn't realize that was done. Is that by any chance why doing an svn checkout from within Haiku shows ~950MB in use in ProcessController afterwards? Not unlikely, if you checked out the Haiku sources. :-) If you "rm -r" everything afterwards, the memory usage should go back pretty much to what is was before the checkout. Not quite though, since some kernel allocations won't be freed (but rather marked unused). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 24 03:59:58 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 24 Mar 2008 02:59:58 -0000 Subject: [Haiku-bugs] [Haiku] #1961: files downloaded or copied from CDs are saved to ram and are not sent to hardrive until shutdown In-Reply-To: <042.ffad4aa78706436f3f6ec4d69fcde40a@haiku-os.org> References: <042.ffad4aa78706436f3f6ec4d69fcde40a@haiku-os.org> Message-ID: <051.966fb06e2cab096bfc24643c29554ec9@haiku-os.org> #1961: files downloaded or copied from CDs are saved to ram and are not sent to hardrive until shutdown ---------------------------+------------------------------------------------ Reporter: qyellow | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by qyellow): I was wondering why deleting them freed that memory thanks for that info. The reason why I say it is only in memory is that if you just turn off the power to the computer instead of shutting down the files are not their on restart: specifically text documents/files copied over from CDs/sometimes preference files... and it can be awhile that they have been sitting there. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 24 05:02:57 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 24 Mar 2008 04:02:57 -0000 Subject: [Haiku-bugs] [Haiku] #1956: Garbage In Files In-Reply-To: <043.b26038f2dc2fcacc60d26d407839e6d0@haiku-os.org> References: <043.b26038f2dc2fcacc60d26d407839e6d0@haiku-os.org> Message-ID: <052.3fa201f3b80b7a8530d70df727b4e9f5@haiku-os.org> #1956: Garbage In Files ----------------------------+----------------------------------------------- Reporter: bonefish | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by bonefish): I just had a case of garbage file, though this one has different circumstances. I edited the already existing file "haiku.h" (a single line only, increasing the file size by 11 bytes) and did a regular "shutdown -r". There was still plenty of memory available. When trying to build gcc in the next session, the file contained only garbage (cf. haiku.h.zip). Again still plenty of memory available. Don't know, if that means anything, but the syslog of the new session says: {{{ bfs: Insert:1306: Name in use bfs: Insert:1306: Name in use bfs: Insert:1306: Name in use Last message repeated 4 times. }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 24 06:23:01 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 24 Mar 2008 05:23:01 -0000 Subject: [Haiku-bugs] [Haiku] #1917: vm_cache_remove_consumer() Deadlock In-Reply-To: <043.cbbdd01e8560ed6dee2cd0f7ba684945@haiku-os.org> References: <043.cbbdd01e8560ed6dee2cd0f7ba684945@haiku-os.org> Message-ID: <052.5ba68592cf5284c7768d2413c7e6c0e0@haiku-os.org> #1917: vm_cache_remove_consumer() Deadlock ----------------------------+----------------------------------------------- Reporter: bonefish | Owner: axeld Type: bug | Status: closed Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: fixed | Platform: All ----------------------------+----------------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: Applied the proposed change in r24548. As I see it, the worst thing that can happen is, that there can be two caches for a vnode for a short time, but that shouldn't be a problem, since when the release_ref() returns, all of the old cache's pages should either be removed (remove_vnode()) or at least written back and unmapped (put_vnode()). Considering this fixed unless proven otherwise. :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 24 08:04:56 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 24 Mar 2008 07:04:56 -0000 Subject: [Haiku-bugs] [Haiku] #1954: Cross tools build failure on linux In-Reply-To: <044.21996c09e1d941437ddef98f8dba6123@haiku-os.org> References: <044.21996c09e1d941437ddef98f8dba6123@haiku-os.org> Message-ID: <053.94d4e8c09cfafde11c011ea9e81716f1@haiku-os.org> #1954: Cross tools build failure on linux ---------------------------+------------------------------------------------ Reporter: pieterpan | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: fixed | Platform: All ---------------------------+------------------------------------------------ Comment (by pieterpan): I confirm that it is fixed, builds like a charm! Thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 24 10:06:48 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 24 Mar 2008 09:06:48 -0000 Subject: [Haiku-bugs] [Haiku] #1961: files downloaded or copied from CDs are saved to ram and are not sent to hardrive until shutdown In-Reply-To: <042.ffad4aa78706436f3f6ec4d69fcde40a@haiku-os.org> References: <042.ffad4aa78706436f3f6ec4d69fcde40a@haiku-os.org> Message-ID: <051.f64515df1ebc6f0aafbeae080cc66904@haiku-os.org> #1961: files downloaded or copied from CDs are saved to ram and are not sent to hardrive until shutdown ---------------------------+------------------------------------------------ Reporter: qyellow | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Resolution: invalid | Platform: All ---------------------------+------------------------------------------------ Changes (by axeld): * status: new => closed * resolution: => invalid -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 24 12:38:51 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 24 Mar 2008 11:38:51 -0000 Subject: [Haiku-bugs] [Haiku] #1955: Media Player won't respond after Restarting Media Server In-Reply-To: <042.0ecb0264e387fa34004c108d0befbb04@haiku-os.org> References: <042.0ecb0264e387fa34004c108d0befbb04@haiku-os.org> Message-ID: <051.f6be49619577c8c369ef525745754555@haiku-os.org> #1955: Media Player won't respond after Restarting Media Server ----------------------------+----------------------------------------------- Reporter: scottmc | Owner: stippi Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Audio & Video | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Changes (by stippi): * owner: marcusoverhagen => stippi * status: new => assigned Comment: Yes, this is a known problem with MediaKit applications. I have once written an article about it. Don't know when I will have the time, but I can try and look into this. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 24 12:45:13 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 24 Mar 2008 11:45:13 -0000 Subject: [Haiku-bugs] [Haiku] #1959: nVidia Corporation NV11 [GeForce2 Go]: drawing problems after new splash screen In-Reply-To: <040.17c8090d9b429398540eaed4e454250d@haiku-os.org> References: <040.17c8090d9b429398540eaed4e454250d@haiku-os.org> Message-ID: <049.3a8adcbbc984a5bfee635ee9e509a470@haiku-os.org> #1959: nVidia Corporation NV11 [GeForce2 Go]: drawing problems after new splash screen --------------------------------------+------------------------------------- Reporter: nielx | Owner: korli Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: | Platform: All --------------------------------------+------------------------------------- Changes (by stippi): * cc: stippi (removed) * owner: axeld => korli Comment: First a note: Please don't CC me. I am on the ticket mailing list and if you CC me, I will get all emails twice. I also think it has nothing to do with the boot icons, but is rather a problem with the changed MTRR setup. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 24 13:43:26 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 24 Mar 2008 12:43:26 -0000 Subject: [Haiku-bugs] [Haiku] #1414: FTP upload stops around 78k In-Reply-To: <042.f39d93bdbcbbad826398bbcc240d51a8@haiku-os.org> References: <042.f39d93bdbcbbad826398bbcc240d51a8@haiku-os.org> Message-ID: <051.33dbbe31f06cf46e578db729a06f83cf@haiku-os.org> #1414: FTP upload stops around 78k -------------------------------------+-------------------------------------- Reporter: scottmc | Owner: hugosantos Type: bug | Status: closed Priority: critical | Milestone: R1 Component: Network & Internet/TCP | Version: R1 development Resolution: fixed | Platform: x64 -------------------------------------+-------------------------------------- Changes (by stippi): * status: new => closed * resolution: => fixed Comment: Speed issue is tracked in #1958. I have no problem downloading or uploading much larger files, so I am closing this bug, since the original issue seems to be fixed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 24 18:45:36 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 24 Mar 2008 17:45:36 -0000 Subject: [Haiku-bugs] [Haiku] #1444: SATA testing on real hardware - fails to boot In-Reply-To: <042.6d42e64b1d90ed4f4f92d24220c524df@haiku-os.org> References: <042.6d42e64b1d90ed4f4f92d24220c524df@haiku-os.org> Message-ID: <051.1f2d1e7de335edb355d8f977f92bfa92@haiku-os.org> #1444: SATA testing on real hardware - fails to boot ---------------------------+------------------------------------------------ Reporter: scottmc | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: x86 ---------------------------+------------------------------------------------ Comment (by marcusoverhagen): Is "IDE: scan_device_int: waiting 100ms..." the last line that gets printed before booting stops? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 24 21:00:51 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 24 Mar 2008 20:00:51 -0000 Subject: [Haiku-bugs] [Haiku] #1950: Garbled screen contents with true colour mode on nvidia gf2mx In-Reply-To: <042.f15ad8e18c31676a011caebc5344d3a8@haiku-os.org> References: <042.f15ad8e18c31676a011caebc5344d3a8@haiku-os.org> Message-ID: <051.021f84dc933349c0825e5d171042a9ca@haiku-os.org> #1950: Garbled screen contents with true colour mode on nvidia gf2mx ------------------------+--------------------------------------------------- Reporter: jopadan | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: x86 ------------------------+--------------------------------------------------- Comment (by jonas.kirilla): Serial output attached. Part of it: ... allocate MTRR slot 0, base = 0, length = 20000000, type=0x6 kernel debugger extension "debugger/hangman/v1": loaded kernel debugger extension "debugger/invalidate_on_exit/v1": loaded allocate MTRR slot 1, base = f0000000, length = 100000, type=0x1 ... loaded driver /boot/beos/system/add-ons/kernel/drivers/dev/graphics/vesa allocate MTRR failed, it overlaps an existing MTRR slot allocate MTRR slot 2, base = f0000000, length = 8000000, type=0x1 Same base? (f0000000) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 24 23:37:42 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 24 Mar 2008 22:37:42 -0000 Subject: [Haiku-bugs] [Haiku] #1956: Garbage In Files In-Reply-To: <043.b26038f2dc2fcacc60d26d407839e6d0@haiku-os.org> References: <043.b26038f2dc2fcacc60d26d407839e6d0@haiku-os.org> Message-ID: <052.1fd345eba0dfa82515e841f7ebc4a7d9@haiku-os.org> #1956: Garbage In Files ----------------------------+----------------------------------------------- Reporter: bonefish | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by bonefish): Another instance of the problem. This time more like the ones I've seen most of the time. Attached is the file config.guess how it should look like and its garbled version. The garbage starts at offset 1024 and ends at offset 3 * 1024, i.e. it has the length of two FS blocks and only of half a page. So this looks more like a BFS than a file cache/VM problem. In the Haiku session I removed the original config.guess which predated the session and copied another file to the same location. After some configuring and making I hit the problem. I can't tell whether the file was broken right after being copied or got damaged later. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 25 03:18:15 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 25 Mar 2008 02:18:15 -0000 Subject: [Haiku-bugs] [Haiku] #1768: Binutils 2.17 objdump Broken In-Reply-To: <043.8358ec31d4354aed633517bedbdfb836@haiku-os.org> References: <043.8358ec31d4354aed633517bedbdfb836@haiku-os.org> Message-ID: <052.e8aa1af76721a07953b110c3ca777441@haiku-os.org> #1768: Binutils 2.17 objdump Broken ---------------------------+------------------------------------------------ Reporter: bonefish | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by bonefish): I gave the binutils 2.18 a try, but merging the eh-frame stuff scared the shit out of me. Maybe it's possible to update only opcodes... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 25 03:39:23 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 25 Mar 2008 02:39:23 -0000 Subject: [Haiku-bugs] [Haiku] #1844: Provide a convenience script for cross-compiling Haiku software from Linux et al. In-Reply-To: <043.f6fe349c51b7b63a450c03afffab4ed5@haiku-os.org> References: <043.f6fe349c51b7b63a450c03afffab4ed5@haiku-os.org> Message-ID: <052.fc9a4fcd4557e2552d0a7f1c9a697743@haiku-os.org> #1844: Provide a convenience script for cross-compiling Haiku software from Linux et al. ---------------------------+------------------------------------------------ Reporter: andreasf | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by bonefish): Sorry for ignoring this ticket for a while. We can just add the script to some cozy place in the repository of course, if you guys think there're more people who would want to use it. I'd much prefer to get Haiku ready for native development, though. As of r24567 the optional "Development" package installs the build tool chain for the gcc 2.95.3 build. I think I'll stay a little longer in the gcc 2.95.3 world -- there are more tools that are practically must haves for basic development (like ssh and svn) -- and will then look into the gcc 4 tool chain. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 24 18:14:51 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 24 Mar 2008 17:14:51 -0000 Subject: [Haiku-bugs] [Haiku] #1444: SATA testing on real hardware - fails to boot In-Reply-To: <042.6d42e64b1d90ed4f4f92d24220c524df@haiku-os.org> References: <042.6d42e64b1d90ed4f4f92d24220c524df@haiku-os.org> Message-ID: <051.192e7f711192dfad25eaca91769e88df@haiku-os.org> #1444: SATA testing on real hardware - fails to boot ---------------------------+------------------------------------------------ Reporter: scottmc | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: x86 ---------------------------+------------------------------------------------ Comment (by scottmc): Still not booting on my mx7118 Gateway laptop. I've attached a screenshot showing the last 7 screens before it halts. Note that it stops on the hard drive icon when not selecting on-screen debug info. Thanks for adding in the pause after each screen, sure helps in taking screenshots. Sorry for the blurry pics, if you need info from one of the blurry ones just let me know and I can try taking new ones. Hopefully you'll see a red flag here. Let me know if there's anything else you'd like me to try. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 25 08:57:16 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 25 Mar 2008 07:57:16 -0000 Subject: [Haiku-bugs] [Haiku] #1844: Provide a convenience script for cross-compiling Haiku software from Linux et al. In-Reply-To: <043.f6fe349c51b7b63a450c03afffab4ed5@haiku-os.org> References: <043.f6fe349c51b7b63a450c03afffab4ed5@haiku-os.org> Message-ID: <052.e0f0b14f31b41fe2112e160c38ddc119@haiku-os.org> #1844: Provide a convenience script for cross-compiling Haiku software from Linux et al. ---------------------------+------------------------------------------------ Reporter: andreasf | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by tqh): I don't think there would be any harm done if it was added with some small readme on how to use it. Maybe even a reference to this bug. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 25 09:01:43 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 25 Mar 2008 08:01:43 -0000 Subject: [Haiku-bugs] [Haiku] #1956: Garbage In Files In-Reply-To: <043.b26038f2dc2fcacc60d26d407839e6d0@haiku-os.org> References: <043.b26038f2dc2fcacc60d26d407839e6d0@haiku-os.org> Message-ID: <052.5b46e25615b72dcd495723e304bd1ad1@haiku-os.org> #1956: Garbage In Files ----------------------------+----------------------------------------------- Reporter: bonefish | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by axeld): I hope you haven't deleted that file yet? It might be helpful to add a dump of its inode with it (ie. how the data stream is laid out). The super block might be helpful, too. I have the feeling that it might be the same reason as #1914: something freed the blocks that were owned by that file. Did you have BFS tracing enabled? Can you find out when and how those blocks were freed by any chance?? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 25 16:13:58 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 25 Mar 2008 15:13:58 -0000 Subject: [Haiku-bugs] [Haiku] #1956: Garbage In Files In-Reply-To: <043.b26038f2dc2fcacc60d26d407839e6d0@haiku-os.org> References: <043.b26038f2dc2fcacc60d26d407839e6d0@haiku-os.org> Message-ID: <052.5950bbdc4d764a2b37ccbefef0694d4e@haiku-os.org> #1956: Garbage In Files ----------------------------+----------------------------------------------- Reporter: bonefish | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by bonefish): Replying to [comment:5 axeld]: > I hope you haven't deleted that file yet? Of course I did. I needed to get something done. :-) > It might be helpful to add a dump of its inode with it (ie. how the data stream is laid out). The super block might be helpful, too. > > I have the feeling that it might be the same reason as #1914: something freed the blocks that were owned by that file. > > Did you have BFS tracing enabled? Can you find out when and how those blocks were freed by any chance?? Nope. I suppose I'll better enable it now. Not sure, if it helps, though. Those build processes usually run a lot of stuff, so that even 200 MB tracing buffer don't last that long. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 25 16:16:10 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 25 Mar 2008 15:16:10 -0000 Subject: [Haiku-bugs] [Haiku] #1844: Provide a convenience script for cross-compiling Haiku software from Linux et al. In-Reply-To: <043.f6fe349c51b7b63a450c03afffab4ed5@haiku-os.org> References: <043.f6fe349c51b7b63a450c03afffab4ed5@haiku-os.org> Message-ID: <052.9a2ddd67ebcc31722d73779908d8f66f@haiku-os.org> #1844: Provide a convenience script for cross-compiling Haiku software from Linux et al. ---------------------------+------------------------------------------------ Reporter: andreasf | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by bonefish): Replying to [comment:11 tqh]: > I don't think there would be any harm done if it was added with some small readme on how to use it. Maybe even a reference to this bug. Any takers for writing such a ReadMe? I suppose it can simply be added as a comment (or --help text) to the script. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 25 16:40:51 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 25 Mar 2008 15:40:51 -0000 Subject: [Haiku-bugs] [Haiku] #1950: Garbled screen contents with true colour mode on nvidia gf2mx In-Reply-To: <042.f15ad8e18c31676a011caebc5344d3a8@haiku-os.org> References: <042.f15ad8e18c31676a011caebc5344d3a8@haiku-os.org> Message-ID: <051.4dddc542acd9cae67442c6fbba131c77@haiku-os.org> #1950: Garbled screen contents with true colour mode on nvidia gf2mx ------------------------+--------------------------------------------------- Reporter: jopadan | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: x86 ------------------------+--------------------------------------------------- Comment (by korli): I would need additional information if it's possible : on Linux, you should find something about "BIOS-provided physical RAM map" in /var/log/messages, especially lines beginning with "BIOS-e820". Please provide on Linux the result of "cat /proc/mtrr". Thanks. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 25 19:33:06 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 25 Mar 2008 18:33:06 -0000 Subject: [Haiku-bugs] [Haiku] #1950: Garbled screen contents with true colour mode on nvidia gf2mx In-Reply-To: <042.f15ad8e18c31676a011caebc5344d3a8@haiku-os.org> References: <042.f15ad8e18c31676a011caebc5344d3a8@haiku-os.org> Message-ID: <051.eb252778c1191e320f57bfc49300b9ac@haiku-os.org> #1950: Garbled screen contents with true colour mode on nvidia gf2mx ------------------------+--------------------------------------------------- Reporter: jopadan | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: x86 ------------------------+--------------------------------------------------- Comment (by korli): Hmm I didn't notice the two graphics cards, I don't know if this is a problem. I also noticed the second slot (slot 1) seems to be allocated by the function frame_buffer_console_init_post_modules() in src/system/kernel/debug/frame_buffer_console.cpp. How should this case be handled ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 25 19:41:26 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 25 Mar 2008 18:41:26 -0000 Subject: [Haiku-bugs] [Haiku] #1950: Garbled screen contents with true colour mode on nvidia gf2mx In-Reply-To: <042.f15ad8e18c31676a011caebc5344d3a8@haiku-os.org> References: <042.f15ad8e18c31676a011caebc5344d3a8@haiku-os.org> Message-ID: <051.d6cb3f6b80d4059d7069ca5a6c96e4de@haiku-os.org> #1950: Garbled screen contents with true colour mode on nvidia gf2mx ------------------------+--------------------------------------------------- Reporter: jopadan | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: x86 ------------------------+--------------------------------------------------- Comment (by jopadan): I'll attach it here for you without the voodoo mtrr I think and you should keep in mind it is x86_64: reg00: base=0x00000000 ( 0MB), size=1024MB: write-back, count=1 reg01: base=0xe0000000 (3584MB), size= 128MB: write-combining, count=1 BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 000000000009fc00 (usable) BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved) BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 000000003fff0000 (usable) BIOS-e820: 000000003fff0000 - 000000003fff3000 (ACPI NVS) BIOS-e820: 000000003fff3000 - 0000000040000000 (ACPI data) BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved) BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved) BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 25 20:19:30 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 25 Mar 2008 19:19:30 -0000 Subject: [Haiku-bugs] [Haiku] #1364: Bootloader can't find boot volume, booting from cd In-Reply-To: <041.ff14f133560c18c550bdf6a3c705c6c8@haiku-os.org> References: <041.ff14f133560c18c550bdf6a3c705c6c8@haiku-os.org> Message-ID: <050.617ac85ff2fd0825b247d881ca065c34@haiku-os.org> #1364: Bootloader can't find boot volume, booting from cd ---------------------------------+------------------------------------------ Reporter: aldeck | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: System/Boot Loader | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by franxico): Replying to [comment:7 aldeck]: > It still doesnt work under vmware though, i'm seeing a (ultra fast) message before the bootloader starts: > > "no boot path found, scan for all partitions..." > "Could not locate any supported boot device!" I kinda have the same message, but in real hardware: "No boot path found, scan for all partitions *panic* mmu_free: asked to unmap out of range region (0x8010b000, size 1000) Press any key to reboot" Tried with rev24521 built from Haikuware. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 25 20:28:55 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 25 Mar 2008 19:28:55 -0000 Subject: [Haiku-bugs] [Haiku] #1950: Garbled screen contents with true colour mode on nvidia gf2mx In-Reply-To: <042.f15ad8e18c31676a011caebc5344d3a8@haiku-os.org> References: <042.f15ad8e18c31676a011caebc5344d3a8@haiku-os.org> Message-ID: <051.37fd6be9e66154409915477f1a1e2587@haiku-os.org> #1950: Garbled screen contents with true colour mode on nvidia gf2mx ------------------------+--------------------------------------------------- Reporter: jopadan | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: x86 ------------------------+--------------------------------------------------- Comment (by rudolfc): Hi, From the pictures it's clear that the acceleration engine crashes. Since after a few timeouts the driver simply drops all accelerated drawing commands you see what you see here. Instead of the system totally hanging that is (gfx wise). Maybe try: PCI mode versus AGP mode (nvidia.settings or disable AGP busmanager) If PCI mode works then the driver/card might dislike PCI->AGP switching after it was engaged. Fix: hmmm, don't know at this time. Is the splash icons screen being drawn accelerated? maybe not doing that would fix it, but you could call that a work around. AFAIK it's impossible (== not known) to do a full hard reset initiated by software of the cards: sometimes if the acc engine hangs a reboot is nessesary to solve that. MTRR is used in the driver as well indeed. Inside the kerneldriver a temporary recompile with disabled MTRR support could be tried (it sits in multiple places!). If it works without MTRR, well then the MTRR change is probably the problem. Regards, Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 25 21:10:20 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 25 Mar 2008 20:10:20 -0000 Subject: [Haiku-bugs] [Haiku] #1950: Garbled screen contents with true colour mode on nvidia gf2mx In-Reply-To: <042.f15ad8e18c31676a011caebc5344d3a8@haiku-os.org> References: <042.f15ad8e18c31676a011caebc5344d3a8@haiku-os.org> Message-ID: <051.e2162552596bef2bb144207f10c755d0@haiku-os.org> #1950: Garbled screen contents with true colour mode on nvidia gf2mx ------------------------+--------------------------------------------------- Reporter: jopadan | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: x86 ------------------------+--------------------------------------------------- Comment (by korli): Replying to [comment:6 jopadan]: > I'll attach it here for you without the voodoo mtrr I think and you should keep in mind it is x86_64: > Any chance to have a serial log or syslog ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 25 21:57:11 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 25 Mar 2008 20:57:11 -0000 Subject: [Haiku-bugs] [Haiku] #1950: Garbled screen contents with true colour mode on nvidia gf2mx In-Reply-To: <042.f15ad8e18c31676a011caebc5344d3a8@haiku-os.org> References: <042.f15ad8e18c31676a011caebc5344d3a8@haiku-os.org> Message-ID: <051.d5a6b8a1e89292e564e173e00e13f602@haiku-os.org> #1950: Garbled screen contents with true colour mode on nvidia gf2mx ------------------------+--------------------------------------------------- Reporter: jopadan | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: x86 ------------------------+--------------------------------------------------- Comment (by korli): Could you check with r24582 ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 25 22:05:27 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 25 Mar 2008 21:05:27 -0000 Subject: [Haiku-bugs] [Haiku] #1950: Garbled screen contents with true colour mode on nvidia gf2mx In-Reply-To: <042.f15ad8e18c31676a011caebc5344d3a8@haiku-os.org> References: <042.f15ad8e18c31676a011caebc5344d3a8@haiku-os.org> Message-ID: <051.503e7544e91c6610578d8357ee79e437@haiku-os.org> #1950: Garbled screen contents with true colour mode on nvidia gf2mx ------------------------+--------------------------------------------------- Reporter: jopadan | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: x86 ------------------------+--------------------------------------------------- Comment (by jonas.kirilla): /proc/mtrr {{{ reg00: base=0x00000000 ( 0MB), size= 512MB: write-back, count=1 reg01: base=0xf8000000 (3968MB), size= 64MB: write-combining, count=1 }}} /var/log/messages {{{ ... Mar 25 22:02:23 kirilla kernel: [ 0.000000] BIOS-provided physical RAM map: Mar 25 22:02:23 kirilla kernel: [ 0.000000] BIOS-e820: 0000000000000000 - 000000000009fc00 (usable) Mar 25 22:02:23 kirilla kernel: [ 0.000000] BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved) Mar 25 22:02:23 kirilla kernel: [ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) Mar 25 22:02:23 kirilla kernel: [ 0.000000] BIOS-e820: 0000000000100000 - 000000001ffec000 (usable) Mar 25 22:02:23 kirilla kernel: [ 0.000000] BIOS-e820: 000000001ffec000 - 000000001ffef000 (ACPI data) Mar 25 22:02:23 kirilla kernel: [ 0.000000] BIOS-e820: 000000001ffef000 - 000000001ffff000 (reserved) Mar 25 22:02:23 kirilla kernel: [ 0.000000] BIOS-e820: 000000001ffff000 - 0000000020000000 (ACPI NVS) Mar 25 22:02:23 kirilla kernel: [ 0.000000] BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved) Mar 25 22:02:23 kirilla kernel: [ 0.000000] BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved) Mar 25 22:02:23 kirilla kernel: [ 0.000000] BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved) Mar 25 22:02:23 kirilla kernel: [ 0.000000] 0MB HIGHMEM available. Mar 25 22:02:23 kirilla kernel: [ 0.000000] 511MB LOWMEM available. ... Mar 25 22:02:23 kirilla kernel: [ 13.550042] Console: colour VGA+ 80x25 ... Mar 25 22:02:23 kirilla kernel: [ 30.342591] Linux agpgart interface v0.102 (c) Dave Jones Mar 25 22:02:23 kirilla kernel: [ 30.355408] agpgart: Detected an Intel 845G Chipset. Mar 25 22:02:23 kirilla kernel: [ 30.359285] agpgart: AGP aperture is 64M @ 0xf8000000 ... Mar 25 22:02:23 kirilla kernel: [ 32.062146] NVRM: loading NVIDIA UNIX x86 Kernel Module 100.14.19 Wed Sep 12 14:12:24 PDT 2007 ... Mar 25 22:02:27 kirilla kernel: [ 41.341550] agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0. Mar 25 22:02:27 kirilla kernel: [ 41.341578] agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode Mar 25 22:02:27 kirilla kernel: [ 41.341602] agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode ... }}} (BTW, just to be extra clear: jonas.kirilla != jopadan. Two separate sets of hardware.) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 25 22:09:48 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 25 Mar 2008 21:09:48 -0000 Subject: [Haiku-bugs] [Haiku] #1959: nVidia Corporation NV11 [GeForce2 Go]: drawing problems after new splash screen In-Reply-To: <040.17c8090d9b429398540eaed4e454250d@haiku-os.org> References: <040.17c8090d9b429398540eaed4e454250d@haiku-os.org> Message-ID: <049.28db5beabdc70665554f18fff5a8d006@haiku-os.org> #1959: nVidia Corporation NV11 [GeForce2 Go]: drawing problems after new splash screen --------------------------------------+------------------------------------- Reporter: nielx | Owner: korli Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: | Platform: All --------------------------------------+------------------------------------- Comment (by korli): I would need additional information if it's possible : a syslog or serial log. Also, on Linux, you should find something about "BIOS-provided physical RAM map" in /var/log/messages, especially lines beginning with "BIOS-e820". Please provide on Linux the result of "cat /proc/mtrr". Thanks. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Mar 25 22:24:40 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 25 Mar 2008 21:24:40 -0000 Subject: [Haiku-bugs] [Haiku] #1962: Some resolutions in VESA no longer work Message-ID: <044.144153a4a47b9e6b368c0cb2527e4b97@haiku-os.org> #1962: Some resolutions in VESA no longer work -----------------------+---------------------------------------------------- Reporter: j_freeman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- Some resolutions--such as 1440x900 and 1920x1200--can be selected, but after rebooting the resolution is 800x600. The Screen preflet acts as if whatever was chosen is the current resolution, but of course it isn't. I don't know the exact revision that stopped working correctly, but it was recent (last 2 weeks or so). Tested under r24560 in VMware Workstation on Windows XP. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 26 01:02:44 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 26 Mar 2008 00:02:44 -0000 Subject: [Haiku-bugs] [Haiku] #1444: SATA testing on real hardware - fails to boot In-Reply-To: <042.6d42e64b1d90ed4f4f92d24220c524df@haiku-os.org> References: <042.6d42e64b1d90ed4f4f92d24220c524df@haiku-os.org> Message-ID: <051.8f824df1ab04f10a34cc76170837acf8@haiku-os.org> #1444: SATA testing on real hardware - fails to boot ---------------------------+------------------------------------------------ Reporter: scottmc | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: x86 ---------------------------+------------------------------------------------ Comment (by scottmc): Replying to [comment:37 marcusoverhagen]: > Is "IDE: scan_device_int: waiting 100ms..." the last line that gets printed before booting stops? Yes. And it just sits there... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 26 05:55:23 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 26 Mar 2008 04:55:23 -0000 Subject: [Haiku-bugs] [Haiku] #1963: BFS Finds Spurious File Message-ID: <043.8c4fd8cd890b528625ba24c70c6bdf7b@haiku-os.org> #1963: BFS Finds Spurious File ------------------------------+--------------------------------------------- Reporter: bonefish | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: File Systems/BFS | Version: R1 development Platform: All | ------------------------------+--------------------------------------------- r24582, VMware While configuring/building gcc, a spurious "cp" entry appeared in the current output directory (.../gcc-obj/gcc/). According to the kernel tracing access() returned OK for the entry and it could even be opened. Reading from it failed with B_BAD_VALUE, though. There's also a respective "bfs_read()..." line in the serial debug output. I suspended and uploaded the virtual machine state (512 MB RAM, 1 GB disk): http://tfs.cs.tu-berlin.de/~bonefish/private/haiku/CrashOMatic-non- existent-cp.zip BFS tracing was enabled, but I forgot to enable block cache tracing. :-/ -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 26 06:33:53 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 26 Mar 2008 05:33:53 -0000 Subject: [Haiku-bugs] [Haiku] #1962: Some resolutions in VESA no longer work In-Reply-To: <044.144153a4a47b9e6b368c0cb2527e4b97@haiku-os.org> References: <044.144153a4a47b9e6b368c0cb2527e4b97@haiku-os.org> Message-ID: <053.ec8464a095885b682f34aefa278bcb5e@haiku-os.org> #1962: Some resolutions in VESA no longer work ------------------------+--------------------------------------------------- Reporter: j_freeman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by scottmc): I see the same problem on real hardware here. Stuck in 800x600 but prefs app says whatever I pick. Tried with r24581 here. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 26 11:04:22 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 26 Mar 2008 10:04:22 -0000 Subject: [Haiku-bugs] [Haiku] #1945: [marvell yukon] 11ab:4320 not detected In-Reply-To: <040.6d7189e51f797abf4deca9c4e5ded43f@haiku-os.org> References: <040.6d7189e51f797abf4deca9c4e5ded43f@haiku-os.org> Message-ID: <049.2d25490c1c9ac484f52e654b04960529@haiku-os.org> #1945: [marvell yukon] 11ab:4320 not detected ------------------------------+--------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Network | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by diver): Where should i place this patch in the tree and what command i should execute to incorporate your diff to test it? Thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 26 11:11:41 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 26 Mar 2008 10:11:41 -0000 Subject: [Haiku-bugs] [Haiku] #1945: [marvell yukon] 11ab:4320 not detected In-Reply-To: <040.6d7189e51f797abf4deca9c4e5ded43f@haiku-os.org> References: <040.6d7189e51f797abf4deca9c4e5ded43f@haiku-os.org> Message-ID: <049.0579129dea079211471b10f5e2595af4@haiku-os.org> #1945: [marvell yukon] 11ab:4320 not detected ------------------------------+--------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Network | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by stippi): Put it anywhere, like your Desktop. Then open a Terminal, cd into the Haiku trunk folder (where src and headers folder are located). Then execute this: {{{ patch -p0 -i /path/to/the/marvell_100.diff }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 26 13:24:24 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 26 Mar 2008 12:24:24 -0000 Subject: [Haiku-bugs] [Haiku] #1945: [marvell yukon] 11ab:4320 not detected In-Reply-To: <040.6d7189e51f797abf4deca9c4e5ded43f@haiku-os.org> References: <040.6d7189e51f797abf4deca9c4e5ded43f@haiku-os.org> Message-ID: <049.0909f35b302d91de28409b59ec0119ec@haiku-os.org> #1945: [marvell yukon] 11ab:4320 not detected ------------------------------+--------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Network | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by diver): Thanks stippi, it worked as expected. But now i'm in trouble building an image (marvell part builds fine) I use Ubuntu 7.10. I used this document to setup everything http://www.haiku- os.org/documents/dev/building_haiku_on_ubuntu_linux_step_by_step And this is my UserBuildConfig: {{{ HAIKU_IMAGE_NAME = sda7 ; HAIKU_IMAGE_DIR = /dev ; HAIKU_ADD_ALL_OPTIONAL_PACKAGES = 1 ; }}} It was 20 of march when i checked out sources and built everything to a partition. Now whey i used "svn up " in trunk folder and sudo jam -q it compiles successfully but last modification time of every object still says 20 of march and no new marvell driver appeared on a partition. If i use $jam -q (without sudo) i get the following error for every updated object: {{{ Error: Failed to open source path `generated/objects/haiku/x86/release /add-ons/opengl/mesa_software_renderer/Mesa Software Renderer': Bad file descriptor Error: Command failed: Bad file descriptor Error: Command was: cp :generated/objects/haiku/x86/release/add- ons/opengl/mesa_software_renderer/Mesa\ Software\ Renderer /myfs/beos/system/add-ons/opengl }}} I guess i will need some help here :-( -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 26 13:54:26 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 26 Mar 2008 12:54:26 -0000 Subject: [Haiku-bugs] [Haiku] #1945: [marvell yukon] 11ab:4320 not detected In-Reply-To: <040.6d7189e51f797abf4deca9c4e5ded43f@haiku-os.org> References: <040.6d7189e51f797abf4deca9c4e5ded43f@haiku-os.org> Message-ID: <049.3d225d76074e8549d3bcc8bec112198a@haiku-os.org> #1945: [marvell yukon] 11ab:4320 not detected ------------------------------+--------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Network | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by stippi): You are not supposed to be root when compiling. You only need to have permissions to write to the harddrive directly. Here is how I do that: {{{ alias haiku="sudo chmod o+rw /dev/sda; sudo chmod o+rw /dev/sda7; cd /home/stippi/haiku/haiku" }}} Put this line into your ~/.bashrc. After entering the new command "haiku" in any Terminal, you can jam -q haiku-image from your normal account in one pass to generate the image on the partition directly. I would delete your generated/objects folder (as root) and build from scratch, since you generated files only root can change. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 26 13:57:55 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 26 Mar 2008 12:57:55 -0000 Subject: [Haiku-bugs] [Haiku] #1950: Garbled screen contents with true colour mode on nvidia gf2mx In-Reply-To: <042.f15ad8e18c31676a011caebc5344d3a8@haiku-os.org> References: <042.f15ad8e18c31676a011caebc5344d3a8@haiku-os.org> Message-ID: <051.a32b239d289cf533d8cb587f4f989b85@haiku-os.org> #1950: Garbled screen contents with true colour mode on nvidia gf2mx ------------------------+--------------------------------------------------- Reporter: jopadan | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: x86 ------------------------+--------------------------------------------------- Comment (by jopadan): Replying to [comment:8 korli]: > Replying to [comment:6 jopadan]: > > I'll attach it here for you without the voodoo mtrr I think and you should keep in mind it is x86_64: > > > > Any chance to have a serial log or syslog ? I've attached a syslog but I don't see anything MTRR related in it. Also the Tracker seems to crash everytime I try to shutdown. Since I am not able to access any ext3 partitions yet I was unable to install the developer tools yet. Maybe there is bfs write support in linux. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 26 14:33:26 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 26 Mar 2008 13:33:26 -0000 Subject: [Haiku-bugs] [Haiku] #1576: Some headers should be rewritten In-Reply-To: <040.e83e7424b795679f4337b358ef6c301d@haiku-os.org> References: <040.e83e7424b795679f4337b358ef6c301d@haiku-os.org> Message-ID: <049.1387a530caf947661fc016ba220201a7@haiku-os.org> #1576: Some headers should be rewritten ------------------------+--------------------------------------------------- Reporter: korli | Owner: Type: bug | Status: new Priority: high | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Old description: > Here is a list in headers/os. They should be reported in headers/build/. > > headers/os/add-ons/graphics/Accelerant.h > headers/os/add-ons/graphics/GraphicsCard.h > headers/os/add-ons/input_server/InputServerDevice.h > headers/os/add-ons/input_server/InputServerFilter.h > headers/os/add-ons/input_server/InputServerMethod.h > headers/os/app/PropertyInfo.h > headers/os/be_apps/NetPositive/NetPositive.h > headers/os/device/A2D.h > headers/os/device/CAM.h > headers/os/device/D2A.h > headers/os/device/DigitalPort.h > headers/os/device/Joystick.h > headers/os/device/scsi.h > headers/os/device/SerialPort.h > headers/os/drivers/atomizer.h > headers/os/drivers/bus_manager.h > headers/os/drivers/ISA.h > headers/os/drivers/midi_driver.h > headers/os/drivers/PCI.h > headers/os/drivers/USB_printer.h > headers/os/drivers/USB_rle.h > headers/os/drivers/USB_spec.h > headers/os/interface/ChannelControl.h > headers/os/interface/ChannelSlider.h > headers/os/interface/MultiChannelControl.h > headers/os/interface/PrintJob.h > headers/os/kernel/scheduler.h > headers/os/mail/E-mail.h > headers/os/media/BufferConsumer.h > headers/os/media/BufferGroup.h > headers/os/media/Buffer.h > headers/os/media/BufferProducer.h > headers/os/media/Controllable.h > headers/os/media/FileInterface.h > headers/os/media/MediaAddOn.h > headers/os/media/MediaDefs.h > headers/os/media/MediaEventLooper.h > headers/os/media/MediaFiles.h > headers/os/media/MediaFormats.h > headers/os/media/MediaNode.h > headers/os/media/MediaRoster.h > headers/os/media/ParameterWeb.h > headers/os/media/PlaySound.h > headers/os/media/RealtimeAlloc.h > headers/os/media/SoundFile.h > headers/os/media/Sound.h > headers/os/media/SoundPlayer.h > headers/os/media/TimeCode.h > headers/os/media/TimedEventQueue.h > headers/os/media/TimeSource.h > headers/os/net/net_settings.h > headers/os/translation/BitmapStream.h > headers/os/translation/TranslationDefs.h > headers/os/translation/TranslationErrors.h > headers/os/translation/TranslationKit.h > headers/os/translation/TranslatorAddOn.h > headers/os/translation/TranslatorFormats.h > > Done: > headers/os/add-ons/tracker/TrackerAddOn.h > headers/os/game/DirectWindow.h > headers/os/kernel/image.h > headers/os/interface/Input.h > headers/os/interface/MenuBar.h > headers/os/interface/OptionControl.h > headers/os/interface/OptionPopUp.h > headers/os/interface/PopUpMenu.h > headers/os/interface/TextView.h > headers/os/opengl/GLView.h New description: Here is a list in headers/os. They should be reported in headers/build/. headers/os/add-ons/graphics/Accelerant.h headers/os/add-ons/graphics/GraphicsCard.h headers/os/add-ons/input_server/InputServerDevice.h headers/os/add-ons/input_server/InputServerFilter.h headers/os/add-ons/input_server/InputServerMethod.h headers/os/app/PropertyInfo.h headers/os/be_apps/NetPositive/NetPositive.h headers/os/device/A2D.h headers/os/device/CAM.h headers/os/device/D2A.h headers/os/device/DigitalPort.h headers/os/device/Joystick.h headers/os/device/scsi.h headers/os/device/SerialPort.h headers/os/drivers/atomizer.h headers/os/drivers/bus_manager.h headers/os/drivers/ISA.h headers/os/drivers/midi_driver.h headers/os/drivers/PCI.h headers/os/drivers/USB_printer.h headers/os/drivers/USB_rle.h headers/os/drivers/USB_spec.h headers/os/interface/ChannelControl.h headers/os/interface/ChannelSlider.h headers/os/interface/MultiChannelControl.h headers/os/interface/PrintJob.h headers/os/kernel/scheduler.h headers/os/mail/E-mail.h headers/os/media/BufferConsumer.h headers/os/media/BufferGroup.h headers/os/media/Buffer.h headers/os/media/BufferProducer.h headers/os/media/Controllable.h headers/os/media/FileInterface.h headers/os/media/MediaAddOn.h headers/os/media/MediaDefs.h headers/os/media/MediaEventLooper.h headers/os/media/MediaFiles.h headers/os/media/MediaFormats.h headers/os/media/MediaNode.h headers/os/media/ParameterWeb.h headers/os/media/PlaySound.h headers/os/media/RealtimeAlloc.h headers/os/media/SoundFile.h headers/os/media/Sound.h headers/os/media/SoundPlayer.h headers/os/media/TimeCode.h headers/os/media/TimedEventQueue.h headers/os/media/TimeSource.h headers/os/net/net_settings.h headers/os/translation/BitmapStream.h headers/os/translation/TranslationDefs.h headers/os/translation/TranslationErrors.h headers/os/translation/TranslationKit.h headers/os/translation/TranslatorAddOn.h headers/os/translation/TranslatorFormats.h Done: headers/os/add-ons/tracker/TrackerAddOn.h headers/os/game/DirectWindow.h headers/os/kernel/image.h headers/os/interface/Input.h headers/os/interface/MenuBar.h headers/os/interface/OptionControl.h headers/os/interface/OptionPopUp.h headers/os/interface/PopUpMenu.h headers/os/interface/TextView.h headers/os/media/MediaRoster.h headers/os/opengl/GLView.h -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 26 14:59:50 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 26 Mar 2008 13:59:50 -0000 Subject: [Haiku-bugs] [Haiku] #1964: Missing headers in /boot/develop/headers/gnu Message-ID: <037.361dbf129bf102ec6b62d6122dae30b7@haiku-os.org> #1964: Missing headers in /boot/develop/headers/gnu --------------------------+------------------------------------------------- Reporter: mt | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Platform: All | --------------------------+------------------------------------------------- Headers for zlib and libpng is missing. perhaps they will be in /boot/develop/headers/gnu ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 26 15:09:51 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 26 Mar 2008 14:09:51 -0000 Subject: [Haiku-bugs] [Haiku] #1945: [marvell yukon] 11ab:4320 not detected In-Reply-To: <040.6d7189e51f797abf4deca9c4e5ded43f@haiku-os.org> References: <040.6d7189e51f797abf4deca9c4e5ded43f@haiku-os.org> Message-ID: <049.d4916caa5a24f37a13febcbe21a7c76c@haiku-os.org> #1945: [marvell yukon] 11ab:4320 not detected ------------------------------+--------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Network | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by diver): Thanks stippi! I removed genereated folder and rebuild everything, i also added alias to the .bashrc. I recompiled everyting without errors jam -q: {{{ Creating image ... 100+0 records in 100+0 records out 104857600 bytes (105 MB) copied, 1,86814 seconds, 56,1 MB/s Writing boot code to "generated/haiku.image" (partition offset: 0 bytes) ... Populating image ... Deleting old MIME database ... Installing MIME database ... Unmounting ... ...updated 282 target(s)... }}} But my haiku partitioin is still from 20th march. Anything else i could try? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 26 15:12:39 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 26 Mar 2008 14:12:39 -0000 Subject: [Haiku-bugs] [Haiku] #1945: [marvell yukon] 11ab:4320 not detected In-Reply-To: <040.6d7189e51f797abf4deca9c4e5ded43f@haiku-os.org> References: <040.6d7189e51f797abf4deca9c4e5ded43f@haiku-os.org> Message-ID: <049.7e7c33a43366d247df60381f74828ef2@haiku-os.org> #1945: [marvell yukon] 11ab:4320 not detected ------------------------------+--------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Network | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by diver): It seems it updates generated/haiku.image but don't write it to the partition itself. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 26 15:57:00 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 26 Mar 2008 14:57:00 -0000 Subject: [Haiku-bugs] [Haiku] #1671: Asus EEEPC can't boot. In-Reply-To: <041.c509a05634e93da784321f9bc9d62670@haiku-os.org> References: <041.c509a05634e93da784321f9bc9d62670@haiku-os.org> Message-ID: <050.620db2be08756162f6cb4d22424ba661@haiku-os.org> #1671: Asus EEEPC can't boot. ---------------------------+------------------------------------------------ Reporter: kvdman | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by kvdman): Hi Marcus, I've made pictures of all the screens booting up the eeepc and leading up to the crash. They are in this archive: [http://www.haikuware.com/downloads/registered/eeepc.zip] If you can't make out some of them, let me know! Karl -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 26 16:22:44 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 26 Mar 2008 15:22:44 -0000 Subject: [Haiku-bugs] [Haiku] #1671: Asus EEEPC can't boot. In-Reply-To: <041.c509a05634e93da784321f9bc9d62670@haiku-os.org> References: <041.c509a05634e93da784321f9bc9d62670@haiku-os.org> Message-ID: <050.13c0f825525bd40ff0c9f38afff9fdd8@haiku-os.org> #1671: Asus EEEPC can't boot. ---------------------------+------------------------------------------------ Reporter: kvdman | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by kvdman): Some of those weren't very good, I took 2 pictures of each screen and kept the best one. Please use this archive instead: [http://www.haikuware.com/downloads/registered/eeepc2.zip ] The boot screen order goes chronologically by file number. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 26 16:24:33 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 26 Mar 2008 15:24:33 -0000 Subject: [Haiku-bugs] [Haiku] #1671: Asus EEEPC can't boot. In-Reply-To: <041.c509a05634e93da784321f9bc9d62670@haiku-os.org> References: <041.c509a05634e93da784321f9bc9d62670@haiku-os.org> Message-ID: <050.5dd70fa270d6dd57a0b2acffea16fd3d@haiku-os.org> #1671: Asus EEEPC can't boot. ---------------------------+------------------------------------------------ Reporter: kvdman | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by kvdman): Oh, and this was rev24521 with generic_ide removed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 26 17:19:09 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 26 Mar 2008 16:19:09 -0000 Subject: [Haiku-bugs] [Haiku] #1945: [marvell yukon] 11ab:4320 not detected In-Reply-To: <040.6d7189e51f797abf4deca9c4e5ded43f@haiku-os.org> References: <040.6d7189e51f797abf4deca9c4e5ded43f@haiku-os.org> Message-ID: <049.74104004bf4a92f138f6665dd68a6674@haiku-os.org> #1945: [marvell yukon] 11ab:4320 not detected ------------------------------+--------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Network | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by diver): Ok, there was something wrong with my UserBuildConfig. I recreated it and now it writes to a partition. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 26 17:24:52 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 26 Mar 2008 16:24:52 -0000 Subject: [Haiku-bugs] [Haiku] #1945: [marvell yukon] 11ab:4320 not detected In-Reply-To: <040.6d7189e51f797abf4deca9c4e5ded43f@haiku-os.org> References: <040.6d7189e51f797abf4deca9c4e5ded43f@haiku-os.org> Message-ID: <049.82ee0a092ae245299d591b30cd13830d@haiku-os.org> #1945: [marvell yukon] 11ab:4320 not detected ------------------------------+--------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Network | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Changes (by diver): * cc: euan (added) Comment: Now this is strange. I mounted haiku partition using mount -t befs /dev/sda7 /mnt/haiku {{{ cd /mnt/haiku/beos/system/add-ons/kernel/drivers/bin ls -la|grep marvell -rwx--x--x 1 root root 121475 2008-03-20 16:28 marvell_yukon lrwxrwxrwx 1 root root 0 2008-03-20 16:28 marvell_yukon_sk -> ../bin/console }}} So it seems that marvell_yukon_sk is a link to the /bin/console app. Something wrong here, any ideas, euan? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 26 18:36:15 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 26 Mar 2008 17:36:15 -0000 Subject: [Haiku-bugs] [Haiku] #1945: [marvell yukon] 11ab:4320 not detected In-Reply-To: <040.6d7189e51f797abf4deca9c4e5ded43f@haiku-os.org> References: <040.6d7189e51f797abf4deca9c4e5ded43f@haiku-os.org> Message-ID: <049.1eb617d0e1f3131f287927485cab0100@haiku-os.org> #1945: [marvell yukon] 11ab:4320 not detected ------------------------------+--------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Network | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by diver): Going further. i execute ./configure --build-cross-tools ../buildtools/ --include-gpl-addons and jam -q and here it is: {{{ cd /mnt/haiku/beos/system/add-ons/kernel/drivers/bin ls -la|grep marvell -rwx--x--x 1 root root 121475 2008-03-26 19:55 marvell_yukon -rwx--x--x 1 root root 121475 2008-03-26 19:55 marvell_yukon_sk }}} But now i get kernel panic, i wrote relevant (i hope) part of back trace on a paper: {{{ PANIC: should never be called : invoke_debugger_command : _ParseCommand_16ExpressionParserRi : EvaluateCommand_16ExpressionParserPcRi : evaluate_debugger_command : kernel_debugger_loop_Fv : kernel_debugger : panic : /boot/beos/system/add- ons/kernel/drivers/dev/marvell_yukon_sk:_Haiku_disabled_interrupts : /boot/beos/system/add- ons/kernel/drivers/dev/marvell_yukon_sk:_intr_wrapper : int:io_interrupt_handler : hardware_interrupt : _int_bottom }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 26 20:01:41 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 26 Mar 2008 19:01:41 -0000 Subject: [Haiku-bugs] [Haiku] #1959: nVidia Corporation NV11 [GeForce2 Go]: drawing problems after new splash screen In-Reply-To: <040.17c8090d9b429398540eaed4e454250d@haiku-os.org> References: <040.17c8090d9b429398540eaed4e454250d@haiku-os.org> Message-ID: <049.54aaa0db4d0e855dbc86cd1017f87b0d@haiku-os.org> #1959: nVidia Corporation NV11 [GeForce2 Go]: drawing problems after new splash screen --------------------------------------+------------------------------------- Reporter: nielx | Owner: korli Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: | Platform: All --------------------------------------+------------------------------------- Comment (by nielx): From the messages: {{{ Jan 26 19:22:13 nielx-laptop kernel: [ 0.000000] BIOS-provided physical RAM map: Jan 26 19:22:13 nielx-laptop kernel: [ 0.000000] BIOS-e820: 0000000000000000 - 000000000009f000 (usable) Jan 26 19:22:13 nielx-laptop kernel: [ 0.000000] BIOS-e820: 000000000009f000 - 00000000000a0000 (reserved) Jan 26 19:22:13 nielx-laptop kernel: [ 0.000000] BIOS-e820: 00000000000dc000 - 0000000000100000 (reserved) Jan 26 19:22:13 nielx-laptop kernel: [ 0.000000] BIOS-e820: 0000000000100000 - 000000001fef0000 (usable) Jan 26 19:22:13 nielx-laptop kernel: [ 0.000000] BIOS-e820: 000000001fef0000 - 000000001feff000 (ACPI data) Jan 26 19:22:13 nielx-laptop kernel: [ 0.000000] BIOS-e820: 000000001feff000 - 000000001ff00000 (ACPI NVS) Jan 26 19:22:13 nielx-laptop kernel: [ 0.000000] BIOS-e820: 000000001ff00000 - 000000001ff80000 (usable) Jan 26 19:22:13 nielx-laptop kernel: [ 0.000000] BIOS-e820: 000000001ff80000 - 0000000020000000 (reserved) Jan 26 19:22:13 nielx-laptop kernel: [ 0.000000] BIOS-e820: 00000000ff800000 - 00000000ffc00000 (reserved) Jan 26 19:22:13 nielx-laptop kernel: [ 0.000000] BIOS-e820: 00000000fff00000 - 0000000100000000 (reserved) Jan 26 19:22:13 nielx-laptop kernel: [ 0.000000] 0MB HIGHMEM available. Jan 26 19:22:13 nielx-laptop kernel: [ 0.000000] 511MB LOWMEM available. Jan 26 19:22:13 nielx-laptop kernel: [ 0.000000] Zone PFN ranges: Jan 26 19:22:13 nielx-laptop kernel: [ 0.000000] DMA 0 -> 4096 Jan 26 19:22:13 nielx-laptop kernel: [ 0.000000] Normal 4096 -> 130944 Jan 26 19:22:13 nielx-laptop kernel: [ 0.000000] HighMem 130944 -> 130944 Jan 26 19:22:13 nielx-laptop kernel: [ 0.000000] early_node_map[1] active PFN ranges Jan 26 19:22:13 nielx-laptop kernel: [ 0.000000] 0: 0 -> 130944 Jan 26 19:22:13 nielx-laptop kernel: [ 0.000000] DMI 2.3 present. }}} MTRR dump: {{{ reg00: base=0x00000000 ( 0MB), size= 512MB: write-back, count=1 reg01: base=0x1ff80000 ( 511MB), size= 512KB: uncachable, count=1 reg02: base=0x1ff80000 ( 511MB), size= 512KB: uncachable, count=1 reg03: base=0xf0000000 (3840MB), size= 16MB: write-combining, count=1 }}} I'll try to fetch a syslog. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 26 23:06:01 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 26 Mar 2008 22:06:01 -0000 Subject: [Haiku-bugs] [Haiku] #1945: [marvell yukon] 11ab:4320 not detected In-Reply-To: <040.6d7189e51f797abf4deca9c4e5ded43f@haiku-os.org> References: <040.6d7189e51f797abf4deca9c4e5ded43f@haiku-os.org> Message-ID: <049.be18e0637c466ab7b19bb11821b9690f@haiku-os.org> #1945: [marvell yukon] 11ab:4320 not detected ------------------------------+--------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Network | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by euan): hmmm that's odd. I thought I left a comment stating I had an issue with the interrupt handlers (in the glue code). But there is no comment just the diff file. The version up there has interrupts implemented in the glue code. I've seen the same issue once. Typing continue in the kernel debugger makes the os continue running. However it indicates that something isn't quite right. I also tried using the defines that bypass the interrupts but it doesn't work yet. In summary. The patch is 95% there. Still needs a tiny tweak to work I think. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Mar 26 23:40:51 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 26 Mar 2008 22:40:51 -0000 Subject: [Haiku-bugs] [Haiku] #1945: [marvell yukon] 11ab:4320 not detected In-Reply-To: <040.6d7189e51f797abf4deca9c4e5ded43f@haiku-os.org> References: <040.6d7189e51f797abf4deca9c4e5ded43f@haiku-os.org> Message-ID: <049.5bffb89dd9b6f7b4fcdd0ae31177a881@haiku-os.org> #1945: [marvell yukon] 11ab:4320 not detected ------------------------------+--------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Network | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by euan): no it seems my migraine deceives me. the diff is the one without irq handlers. I guess the kernel message is indicating that they should be implemented. I had a stab at it but it didn't work quite right... added another file... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 27 00:02:24 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 26 Mar 2008 23:02:24 -0000 Subject: [Haiku-bugs] [Haiku] #1963: execvp() Tries to Execute Directories In-Reply-To: <043.8c4fd8cd890b528625ba24c70c6bdf7b@haiku-os.org> References: <043.8c4fd8cd890b528625ba24c70c6bdf7b@haiku-os.org> Message-ID: <052.df2b0c21d4b0b937c81c5e2024ab6540@haiku-os.org> #1963: execvp() Tries to Execute Directories --------------------------------+------------------------------------------- Reporter: bonefish | Owner: bonefish Type: bug | Status: assigned Priority: critical | Milestone: R1/alpha1 Component: System/libroot.so | Version: R1 development Resolution: | Platform: All --------------------------------+------------------------------------------- Changes (by bonefish): * owner: axeld => bonefish * status: new => assigned * component: File Systems/BFS => System/libroot.so * summary: BFS Finds Spurious File => execvp() Tries to Execute Directories Old description: > r24582, VMware > > While configuring/building gcc, a spurious "cp" entry appeared in the > current output directory (.../gcc-obj/gcc/). According to the kernel > tracing access() returned OK for the entry and it could even be opened. > Reading from it failed with B_BAD_VALUE, though. There's also a > respective "bfs_read()..." line in the serial debug output. I suspended > and uploaded the virtual machine state (512 MB RAM, 1 GB disk): > > http://tfs.cs.tu-berlin.de/~bonefish/private/haiku/CrashOMatic-non- > existent-cp.zip > > BFS tracing was enabled, but I forgot to enable block cache tracing. :-/ New description: r24582, VMware When execvp() finds a matching entry in the PATH, it doesn't make sure that it is a regular file. E.g. create a "cp" directory in the cwd and make it executable. execvp("cp",...) will try to execute it. Comment: Never write bug reports when too tired. There actually is an entry "cp", I just missed it; it's a directory. This is just another execvp() bug. I thought I was really clever replacing the stat() in the code copied from my APR code by access(), but we obviously also need to make sure that the entry is a regular file. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 27 00:44:03 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 26 Mar 2008 23:44:03 -0000 Subject: [Haiku-bugs] [Haiku] #1963: execvp() Tries to Execute Directories In-Reply-To: <043.8c4fd8cd890b528625ba24c70c6bdf7b@haiku-os.org> References: <043.8c4fd8cd890b528625ba24c70c6bdf7b@haiku-os.org> Message-ID: <052.857886a7abe22d3c053091ba02b08e04@haiku-os.org> #1963: execvp() Tries to Execute Directories --------------------------------+------------------------------------------- Reporter: bonefish | Owner: bonefish Type: bug | Status: closed Priority: critical | Milestone: R1/alpha1 Component: System/libroot.so | Version: R1 development Resolution: fixed | Platform: All --------------------------------+------------------------------------------- Changes (by bonefish): * status: assigned => closed * resolution: => fixed Comment: Fixed in r24599. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 27 00:49:31 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 26 Mar 2008 23:49:31 -0000 Subject: [Haiku-bugs] [Haiku] #1964: Missing headers in /boot/develop/headers/gnu In-Reply-To: <037.361dbf129bf102ec6b62d6122dae30b7@haiku-os.org> References: <037.361dbf129bf102ec6b62d6122dae30b7@haiku-os.org> Message-ID: <046.70730b2e7a1f3b20ca312c23fc58b2e2@haiku-os.org> #1964: Missing headers in /boot/develop/headers/gnu ---------------------------+------------------------------------------------ Reporter: mt | Owner: bonefish Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: fixed | Platform: All ---------------------------+------------------------------------------------ Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: Added the headers in r24600. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 27 03:49:05 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 27 Mar 2008 02:49:05 -0000 Subject: [Haiku-bugs] [Haiku] #1660: registrar eats RAM while unzipping In-Reply-To: <041.c3bbf48b6c0b23748f208db9278c7ea3@haiku-os.org> References: <041.c3bbf48b6c0b23748f208db9278c7ea3@haiku-os.org> Message-ID: <050.7c5ed20a6c6d29e3fce73bc00a86bfe4@haiku-os.org> #1660: registrar eats RAM while unzipping --------------------------------+------------------------------------------- Reporter: shatty | Owner: bonefish Type: bug | Status: assigned Priority: high | Milestone: R1/alpha1 Component: Servers/registrar | Version: R1 development Resolution: | Platform: x86 --------------------------------+------------------------------------------- Changes (by bonefish): * priority: normal => high * status: new => assigned * milestone: R1 => R1/alpha1 Comment: OK, I can reproduce the problem. I strongly suspect a leak in the registrar-side update_mime_info() code. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 27 05:27:06 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 27 Mar 2008 04:27:06 -0000 Subject: [Haiku-bugs] [Haiku] #1660: registrar eats RAM while unzipping In-Reply-To: <041.c3bbf48b6c0b23748f208db9278c7ea3@haiku-os.org> References: <041.c3bbf48b6c0b23748f208db9278c7ea3@haiku-os.org> Message-ID: <050.1e2ebfc6884b0fb4ec9830dc4a5819b6@haiku-os.org> #1660: registrar eats RAM while unzipping --------------------------------+------------------------------------------- Reporter: shatty | Owner: bonefish Type: bug | Status: closed Priority: high | Milestone: R1/alpha1 Component: Servers/registrar | Version: R1 development Resolution: fixed | Platform: x86 --------------------------------+------------------------------------------- Changes (by bonefish): * status: assigned => closed * resolution: => fixed Comment: Fixed in r24604. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 27 06:11:38 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 27 Mar 2008 05:11:38 -0000 Subject: [Haiku-bugs] [Haiku] #1965: No Shell Prompt In Terminal Message-ID: <043.54ec17eb4d0003de0d41f8c19b3b10d9@haiku-os.org> #1965: No Shell Prompt In Terminal -----------------------+---------------------------------------------------- Reporter: bonefish | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- r24604 Sometimes a Terminal comes up without a shell prompt. I've analyzed the situation and apparently the shell had received a SIGWINCH while it was in the allocator (free()) and held the lock. The signal handler it had installed earlier was invoked and this handler called malloc(), thus causing a deadlock when it tried to re-lock. I'm not quite sure, who's to blame. I suppose the memory allocator can't really do anything about it -- temporarily blocking signals would be a little too expensive. So it would be either the Terminal, which maybe shouldn't cause a SIGWINCH that early, or the shell, which should be more careful about what signal handlers it has installed and what signals unblocked while allocating/freeing memory. I tend towards the latter, but also wonder why I've never seen this problem on other platforms before. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 27 06:44:10 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 27 Mar 2008 05:44:10 -0000 Subject: [Haiku-bugs] [Haiku] #1929: steal_pages() Livelock In-Reply-To: <043.816a1d880fac2ebc91ac1ed2e54c6cbd@haiku-os.org> References: <043.816a1d880fac2ebc91ac1ed2e54c6cbd@haiku-os.org> Message-ID: <052.af783c11704a3715f0d5e4fe6059bb7a@haiku-os.org> #1929: steal_pages() Livelock ----------------------------+----------------------------------------------- Reporter: bonefish | Owner: axeld Type: bug | Status: closed Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: fixed | Platform: All ----------------------------+----------------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: I replaced the NotifyOne() by a snooze(10000) in r24605. This should at least fix the problem, even if there might be better solutions. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 27 07:42:43 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 27 Mar 2008 06:42:43 -0000 Subject: [Haiku-bugs] [Haiku] #1966: Panic:vm_page_fault:unhandled page fault in kernel space at 0x0, ip 0x800gcdd7 Message-ID: <047.44f9884037bae402bb9ed1c5501bbaa1@haiku-os.org> #1966: Panic:vm_page_fault:unhandled page fault in kernel space at 0x0, ip 0x800gcdd7 --------------------------+------------------------------------------------- Reporter: skarmiglione | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Add-Ons | Version: R1 development Platform: x64 | --------------------------+------------------------------------------------- while the live cd boot, it present this hang bug, but when i disable the user addons in the failsafe menu then can boot haiku. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 27 07:54:18 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 27 Mar 2008 06:54:18 -0000 Subject: [Haiku-bugs] [Haiku] #1966: Panic:vm_page_fault:unhandled page fault in kernel space at 0x0, ip 0x800gcdd7 In-Reply-To: <047.44f9884037bae402bb9ed1c5501bbaa1@haiku-os.org> References: <047.44f9884037bae402bb9ed1c5501bbaa1@haiku-os.org> Message-ID: <056.22030fc75ff6f7e0d32cb1085c3fbbc8@haiku-os.org> #1966: Panic:vm_page_fault:unhandled page fault in kernel space at 0x0, ip 0x800gcdd7 ---------------------------+------------------------------------------------ Reporter: skarmiglione | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Add-Ons | Version: R1 development Resolution: | Platform: x64 ---------------------------+------------------------------------------------ Comment (by skarmiglione): oh i forget tell my hardware, Via k8m890ce, amd x2 3800+ nvidia 7600gt -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 27 08:33:17 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 27 Mar 2008 07:33:17 -0000 Subject: [Haiku-bugs] [Haiku] #1945: [marvell yukon] 11ab:4320 not detected In-Reply-To: <040.6d7189e51f797abf4deca9c4e5ded43f@haiku-os.org> References: <040.6d7189e51f797abf4deca9c4e5ded43f@haiku-os.org> Message-ID: <049.3c514c3f4daf114cb1bc7b9964dc9ee5@haiku-os.org> #1945: [marvell yukon] 11ab:4320 not detected ------------------------------+--------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Network | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by diver): For me typing "es" in kdl don't make the os running, it just repeat panic message. Should i try your new diff? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 27 08:40:14 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 27 Mar 2008 07:40:14 -0000 Subject: [Haiku-bugs] [Haiku] #1739: Include a build system script to generate a proper 'develop' directory on Haiku In-Reply-To: <040.f743ba11ad5fa7b10c54bfab1bdaea69@haiku-os.org> References: <040.f743ba11ad5fa7b10c54bfab1bdaea69@haiku-os.org> Message-ID: <049.05bed8df721ee445424c3977f5a717d8@haiku-os.org> #1739: Include a build system script to generate a proper 'develop' directory on Haiku ---------------------------+------------------------------------------------ Reporter: nielx | Owner: bonefish Type: enhancement | Status: new Priority: blocker | Milestone: R1/alpha1 Component: Build System | Version: R1 development Resolution: | Platform: x86 ---------------------------+------------------------------------------------ Comment (by nielx): Ingo, as far as I can see you satisfied the requirements of this ticket, didn't you? Can this ticket be closed? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 27 09:57:07 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 27 Mar 2008 08:57:07 -0000 Subject: [Haiku-bugs] [Haiku] #1945: [marvell yukon] 11ab:4320 not detected In-Reply-To: <040.6d7189e51f797abf4deca9c4e5ded43f@haiku-os.org> References: <040.6d7189e51f797abf4deca9c4e5ded43f@haiku-os.org> Message-ID: <049.cbda60f1971a7c1f431b25352b1cf523@haiku-os.org> #1945: [marvell yukon] 11ab:4320 not detected ------------------------------+--------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Network | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by euan): Yeah simply replace the glue.c with the new one (it's not a diff) and recompile (cross fingers I didn't change anything anywhere else). :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 27 10:17:37 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 27 Mar 2008 09:17:37 -0000 Subject: [Haiku-bugs] [Haiku] #1966: Panic:vm_page_fault:unhandled page fault in kernel space at 0x0, ip 0x800gcdd7 In-Reply-To: <047.44f9884037bae402bb9ed1c5501bbaa1@haiku-os.org> References: <047.44f9884037bae402bb9ed1c5501bbaa1@haiku-os.org> Message-ID: <056.459a3b4b2bb29786e5888fcd7d446e14@haiku-os.org> #1966: Panic:vm_page_fault:unhandled page fault in kernel space at 0x0, ip 0x800gcdd7 ----------------------------+----------------------------------------------- Reporter: skarmiglione | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x64 ----------------------------+----------------------------------------------- Changes (by axeld): * component: Add-Ons => System/Kernel Comment: Can you provide a stack trace (by executing "sc" in the kernel debugger)? A digitial photo of the output would be okay. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 27 10:49:48 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 27 Mar 2008 09:49:48 -0000 Subject: [Haiku-bugs] [Haiku] #1914: PANIC: vnode 5:45465 already exists (node = 0x90c1b300, vnode->node = 0x91053d80)! In-Reply-To: <040.572daffe104be83e982ae20fb33b51e3@haiku-os.org> References: <040.572daffe104be83e982ae20fb33b51e3@haiku-os.org> Message-ID: <049.865b141f2590e7c37463bc410b8d3ca0@haiku-os.org> #1914: PANIC: vnode 5:45465 already exists (node = 0x90c1b300, vnode->node = 0x91053d80)! ----------------------------+----------------------------------------------- Reporter: thorn | Owner: axeld Type: bug | Status: closed Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: fixed | Platform: x86 ----------------------------+----------------------------------------------- Changes (by axeld): * priority: normal => critical * resolution: => fixed * status: new => closed * component: File Systems/BFS => System/Kernel * milestone: R1 => R1/alpha1 Comment: Fixed in r24607. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 27 10:50:32 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 27 Mar 2008 09:50:32 -0000 Subject: [Haiku-bugs] [Haiku] #1956: Garbage In Files In-Reply-To: <043.b26038f2dc2fcacc60d26d407839e6d0@haiku-os.org> References: <043.b26038f2dc2fcacc60d26d407839e6d0@haiku-os.org> Message-ID: <052.a455e7ac1944a9be5868a5d9d4c81f83@haiku-os.org> #1956: Garbage In Files ----------------------------+----------------------------------------------- Reporter: bonefish | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by axeld): Should be fixed with r24607. If it doesn't happen for you anymore, please close this ticket. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 27 11:56:43 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 27 Mar 2008 10:56:43 -0000 Subject: [Haiku-bugs] [Haiku] #1909: emuxki/midi related KDLs? In-Reply-To: <048.7c433231494081c4264c03b82f3ce97f@haiku-os.org> References: <048.7c433231494081c4264c03b82f3ce97f@haiku-os.org> Message-ID: <057.4582431fceb6af133bb37974bed8e608@haiku-os.org> #1909: emuxki/midi related KDLs? ----------------------------+----------------------------------------------- Reporter: jonas.kirilla | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by korli): Could you try again with r24597 or superior ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 27 12:10:45 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 27 Mar 2008 11:10:45 -0000 Subject: [Haiku-bugs] [Haiku] #1967: kdl using rtl8139 if_vr: packet not processed Message-ID: <042.fe3fb91518812a33d79bcd0beefe2745@haiku-os.org> #1967: kdl using rtl8139 if_vr: packet not processed --------------------------------+------------------------------------------- Reporter: bbjimmy | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Platform: x86 | --------------------------------+------------------------------------------- r24604 kdl using rtl8139... if_vr: packet not processed This occurs after loading a few web pages in firefox. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 27 12:12:35 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 27 Mar 2008 11:12:35 -0000 Subject: [Haiku-bugs] [Haiku] #1968: kdl using rtl8139 if_vr: packet not processed Message-ID: <042.bedef32b36aa111370c159f415e483ab@haiku-os.org> #1968: kdl using rtl8139 if_vr: packet not processed --------------------------------+------------------------------------------- Reporter: bbjimmy | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Platform: x86 | --------------------------------+------------------------------------------- r24604 kdl using rtl8139... if_vr: packet not processed This occurs after loading a few web pages in firefox. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 27 12:36:59 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 27 Mar 2008 11:36:59 -0000 Subject: [Haiku-bugs] [Haiku] #820: Network preferences In-Reply-To: <040.51b3d1ed078a0ace0f53e4d8d6d5fcef@haiku-os.org> References: <040.51b3d1ed078a0ace0f53e4d8d6d5fcef@haiku-os.org> Message-ID: <049.b88ccb55e26b6a737fe6836711247678@haiku-os.org> #820: Network preferences ---------------------------------+------------------------------------------ Reporter: axeld | Owner: stippi Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Network & Internet | Version: Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by wkornewald): I re-read my proposal a few days ago and one thing certainly needs to be changed: Under "Base" in the longest paragraph (4th from below) I wrote > Values that can't be customized (or all values if you don't customize the preferences) are displayed as simple text instead of grayed-out control. IMHO, the part in the parenthesis should go away because the user should be able to know in advance what can be customized for that location. IOW, simple text for things that can't be customized and grayed-out controls for location-customizable prefs. Since I don't have write access to the wiki I can't change the proposal. Also, I don't want to interfere with your work, so I'll better leave it up to you. Note, you can always contact me if you want me to clarify something. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 27 14:09:55 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 27 Mar 2008 13:09:55 -0000 Subject: [Haiku-bugs] [Haiku] #1739: Include a build system script to generate a proper 'develop' directory on Haiku In-Reply-To: <040.f743ba11ad5fa7b10c54bfab1bdaea69@haiku-os.org> References: <040.f743ba11ad5fa7b10c54bfab1bdaea69@haiku-os.org> Message-ID: <049.72a65715617afb1948da8671a9ed6bac@haiku-os.org> #1739: Include a build system script to generate a proper 'develop' directory on Haiku ---------------------------+------------------------------------------------ Reporter: nielx | Owner: bonefish Type: enhancement | Status: assigned Priority: blocker | Milestone: R1/alpha1 Component: Build System | Version: R1 development Resolution: | Platform: x86 ---------------------------+------------------------------------------------ Changes (by bonefish): * status: new => assigned Comment: Replying to [comment:8 nielx]: > Ingo, as far as I can see you satisfied the requirements of this ticket, didn't you? Nope, a few tools are still missing (jam, flex, bison). > Can this ticket be closed? Will do when I've added the missing stuff. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 27 14:54:18 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 27 Mar 2008 13:54:18 -0000 Subject: [Haiku-bugs] [Haiku] #1969: No video driver for Intel 82845G/GL Message-ID: <042.a72e4d4357e143804e2ca2298780d313@haiku-os.org> #1969: No video driver for Intel 82845G/GL --------------------------------------------+------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/intel_extreme | Version: R1 development Platform: x86 | --------------------------------------------+------------------------------- Testing on real hardware, a DELL Optiplex GX60 small-tower, everything seems to work, except the video drops to VESA mode. Attached listdev output. (listdev > filename.txt) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 27 15:49:16 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 27 Mar 2008 14:49:16 -0000 Subject: [Haiku-bugs] [Haiku] #1968: kdl using rtl8139 if_vr: packet not processed In-Reply-To: <042.bedef32b36aa111370c159f415e483ab@haiku-os.org> References: <042.bedef32b36aa111370c159f415e483ab@haiku-os.org> Message-ID: <051.d6e3bb4cad4932a472a77799b4fa1daf@haiku-os.org> #1968: kdl using rtl8139 if_vr: packet not processed ---------------------------------+------------------------------------------ Reporter: bbjimmy | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Resolution: duplicate | Platform: x86 ---------------------------------+------------------------------------------ Changes (by axeld): * status: new => closed * resolution: => duplicate Comment: Duplicate of #1967 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 27 16:38:13 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 27 Mar 2008 15:38:13 -0000 Subject: [Haiku-bugs] [Haiku] #1955: Media Player won't respond after Restarting Media Server In-Reply-To: <042.0ecb0264e387fa34004c108d0befbb04@haiku-os.org> References: <042.0ecb0264e387fa34004c108d0befbb04@haiku-os.org> Message-ID: <051.531b87ec99813db943a5f2457f767c1e@haiku-os.org> #1955: Media Player won't respond after Restarting Media Server ----------------------------+----------------------------------------------- Reporter: scottmc | Owner: stippi Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Audio & Video | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by scottmc): Not sure if this is related or not, but while playing a song .wav file on media player I hit f12 to drop to kdl to see something else and when i left kdl mediaplayer was frozen. I did a ctrl-alt-del and killed off media player and then reopened it and it still wouldn't play. So closed it again and restarted media server and then media player worked fine again. Not reporting this as a bug as I'm not sure that media server should/would still work after dropping into and out of kdl, just thought it might be related this this bug report. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 27 16:42:41 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 27 Mar 2008 15:42:41 -0000 Subject: [Haiku-bugs] [Haiku] #1970: VM's sAvailableMemory counter is possibly inaccurate Message-ID: <044.e921a4a64e1421d6e6a9995b312a64a9@haiku-os.org> #1970: VM's sAvailableMemory counter is possibly inaccurate ---------------------------+------------------------------------------------ Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Platform: All | ---------------------------+------------------------------------------------ As exposed by the new way of doing get_system_info(), the number given by sAvailableMemory appears to be incorrect. After doing something involving heavy amounts of I/O / memory allocations, (i.e. a large svn checkout or attempting a Haiku build from within Haiku), this number steadily grows until it's significantly larger than the amount of physical RAM in the system. As an example, after attempting the build, sAvailableMemory reports back 4.8GB on a system that has only 1GB of physical RAM. Even accounting for overcommits, this seems far too high, especially given lack of swap. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 27 16:43:45 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 27 Mar 2008 15:43:45 -0000 Subject: [Haiku-bugs] [Haiku] #1971: Negative memory usage being reported in about haiku Message-ID: <042.1c782086df1af045780307acd81c56a5@haiku-os.org> #1971: Negative memory usage being reported in about haiku -----------------------+---------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- See screenshot. Note that this is my first attempt at building Haiku so maybe I have something not set right? Anyone else seeing negative memory usage? This was on r24609. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 27 16:47:56 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 27 Mar 2008 15:47:56 -0000 Subject: [Haiku-bugs] [Haiku] #1970: VM's sAvailableMemory counter is possibly inaccurate In-Reply-To: <044.e921a4a64e1421d6e6a9995b312a64a9@haiku-os.org> References: <044.e921a4a64e1421d6e6a9995b312a64a9@haiku-os.org> Message-ID: <053.7e8df85ef8e1a5cfda34c1478d9bd9ab@haiku-os.org> #1970: VM's sAvailableMemory counter is possibly inaccurate ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by scottmc): I'm guessing this is tied to #1971, so that one's probably a dupe. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 27 17:08:28 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 27 Mar 2008 16:08:28 -0000 Subject: [Haiku-bugs] [Haiku] #1971: Negative memory usage being reported in about haiku In-Reply-To: <042.1c782086df1af045780307acd81c56a5@haiku-os.org> References: <042.1c782086df1af045780307acd81c56a5@haiku-os.org> Message-ID: <051.0a5c292b1d776c4a2faf3a931a7c2f51@haiku-os.org> #1971: Negative memory usage being reported in about haiku ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: duplicate | Platform: All ------------------------+--------------------------------------------------- Changes (by anevilyak): * status: new => closed * resolution: => duplicate Comment: This issue is in fact caused by #1970, thanks for pointing that out scott. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 27 17:23:29 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 27 Mar 2008 16:23:29 -0000 Subject: [Haiku-bugs] [Haiku] #1945: [marvell yukon] 11ab:4320 not detected In-Reply-To: <040.6d7189e51f797abf4deca9c4e5ded43f@haiku-os.org> References: <040.6d7189e51f797abf4deca9c4e5ded43f@haiku-os.org> Message-ID: <049.5f46e9cfc40e60a62cdbb8d4279e580a@haiku-os.org> #1945: [marvell yukon] 11ab:4320 not detected ------------------------------+--------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Network | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by diver): Going a little further again: Now with new glue code a don't get kdl, but a completely freeze at the latest step before app_server kick in. I enabled onscreen console debugging and written down relevant parts, here it is: {{{ marvell_yukon_sk: init hardware marvell_yukon_sk: found Marvell Gigabit Ethernet at 10 marvell_yukon_sk: init driver [marvell_yukon_sk] (sck) buss_alloc_resource (3, [16], 0x0, 0xffffffff, 0x1, 0x2) [marvell_yukon_sk] (sck) buss_alloc_resource (1, [0], 0x0, 0xffffffff. 0x1, 0x6) [marvell_yukon_sk] (sck) interrupt moderation is 100us [marvell_yukon_sk] (sck) Marvell Yukon Lite Gigabit Ethernet rev (0x9) [marvell_yukon_sk] (sck) chip ver 0xb [marvell_yukon_sk] (sck) chip dev 0x09 [marvell_yukon_sk] (sck) SK_EPROM0 = 0x10 [marvell_yukon_sk] (sck) SRAM size = 0x010000 [marvell_yukon_sk] (sck) marvell_yukon_sk: /dev/net/marvell_yukon_sk/0 [marvell_yukon_sk] (sck) () Found MII: e1000phy [marvell_yukon_sk] (sck) () Adding entry for Ethernet node Adding entry for Ethernet 10baseT/UTP 100baseTX-FDX, adding entry for bfs:bfs_access:1360:Operation not allwoed media change, media 0x22 media quality 1000 speed 10000 media change, media 0x909026 media quality 1000 speed 10000 }}} At this point screen ether goes black or flicker several times and completely freeze as num lock don't react. What wondering me is random bfs traces between marvell_yukon logs. What should i try next? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 27 19:21:03 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 27 Mar 2008 18:21:03 -0000 Subject: [Haiku-bugs] [Haiku] #1972: Implement paging (swap file) support Message-ID: <040.6a0030783dc98530450a11a28a320ca9@haiku-os.org> #1972: Implement paging (swap file) support ---------------------------+------------------------------------------------ Reporter: axeld | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Platform: All | ---------------------------+------------------------------------------------ While our VM is prepared to handle paging of anonymous memory, it's not yet implemented yet. Implement swap file support, try to intelligently handle the free space and the swap file (eventually allowing several swap files, or the reuse of other system's swap partitions - note suspend-to-disk issues with that), have a look at page compression, etc. Finally, the swap file should be configurable. There is already the "VirtualMemory" preferences application that could be extended/changed as needed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 27 19:21:22 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 27 Mar 2008 18:21:22 -0000 Subject: [Haiku-bugs] [Haiku] #1972: Implement paging (swap file) support In-Reply-To: <040.6a0030783dc98530450a11a28a320ca9@haiku-os.org> References: <040.6a0030783dc98530450a11a28a320ca9@haiku-os.org> Message-ID: <049.56d70168b8978004511fa953a89894c9@haiku-os.org> #1972: Implement paging (swap file) support ----------------------------+----------------------------------------------- Reporter: axeld | Owner: Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Changes (by axeld): * owner: axeld => -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 27 20:54:01 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 27 Mar 2008 19:54:01 -0000 Subject: [Haiku-bugs] [Haiku] #1973: Video drivers and VESA driver don't work with VIA K8N800 video chipset Message-ID: <044.c690a35a0e5b6d7b59e9d6ffb3cf95aa@haiku-os.org> #1973: Video drivers and VESA driver don't work with VIA K8N800 video chipset ----------------------------------+----------------------------------------- Reporter: zaranthos | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/VIA | Version: R1 development Platform: x86 | ----------------------------------+----------------------------------------- The video driver for the VIA K8N800 chipset isn't working and the VESA modes also fail to work on an ECS 536 laptop. Updating the BIOS to the latest version didn't help. The video driver loads but displays garbage graphics on the screen. In vesa modes the Haiku logo seems to display in different modes until about the time Tracker loads and then the screen goes black. None of the vesa modes work correctly. Full laptop specs can be found here: http://www.ecs.com.tw/ECSWebSite/Products/ProductsDetail.aspx?detailid=520&CategoryID=3&DetailName=Specification&MenuID=59&LanID=0 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 27 21:13:35 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 27 Mar 2008 20:13:35 -0000 Subject: [Haiku-bugs] [Haiku] #1973: Video drivers and VESA driver don't work with VIA K8N800 video chipset In-Reply-To: <044.c690a35a0e5b6d7b59e9d6ffb3cf95aa@haiku-os.org> References: <044.c690a35a0e5b6d7b59e9d6ffb3cf95aa@haiku-os.org> Message-ID: <053.bb231f8812c26fbd212287ffedd50eb8@haiku-os.org> #1973: Video drivers and VESA driver don't work with VIA K8N800 video chipset -----------------------------------+---------------------------------------- Reporter: zaranthos | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/VIA | Version: R1 development Resolution: | Platform: x86 -----------------------------------+---------------------------------------- Comment (by korli): Could you try to activate debug console output and take some pictures of each screen ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 27 21:32:50 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 27 Mar 2008 20:32:50 -0000 Subject: [Haiku-bugs] [Haiku] #1969: No video driver for Intel 82845G/GL In-Reply-To: <042.a72e4d4357e143804e2ca2298780d313@haiku-os.org> References: <042.a72e4d4357e143804e2ca2298780d313@haiku-os.org> Message-ID: <051.f351c454c159571c9976622af2a49294@haiku-os.org> #1969: No video driver for Intel 82845G/GL ---------------------------------------------+------------------------------ Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/intel_extreme | Version: R1 development Resolution: | Platform: x86 ---------------------------------------------+------------------------------ Comment (by korli): Weirdly your VGA device should be supported by the intel_extreme driver (at least the PCI id is included). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 27 21:46:27 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 27 Mar 2008 20:46:27 -0000 Subject: [Haiku-bugs] [Haiku] #1969: No video driver for Intel 82845G/GL In-Reply-To: <042.a72e4d4357e143804e2ca2298780d313@haiku-os.org> References: <042.a72e4d4357e143804e2ca2298780d313@haiku-os.org> Message-ID: <051.330ea192bc7becafef6f47fe391d840c@haiku-os.org> #1969: No video driver for Intel 82845G/GL ---------------------------------------------+------------------------------ Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/intel_extreme | Version: R1 development Resolution: | Platform: x86 ---------------------------------------------+------------------------------ Comment (by umccullough): I think one of my machines (dell inspiron 1100 laptop) even has this chipset and works (with the exception of the new splash boot issue I mentioned on the mailing list - but I will investigate that further). You're sure there's nothing listed in /dev/graphics other than the vesa driver? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 27 22:43:24 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 27 Mar 2008 21:43:24 -0000 Subject: [Haiku-bugs] [Haiku] #1909: emuxki/midi related KDLs? In-Reply-To: <048.7c433231494081c4264c03b82f3ce97f@haiku-os.org> References: <048.7c433231494081c4264c03b82f3ce97f@haiku-os.org> Message-ID: <057.76d807671c1d917ea10455239f5d52b5@haiku-os.org> #1909: emuxki/midi related KDLs? ----------------------------+----------------------------------------------- Reporter: jonas.kirilla | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by jonas.kirilla): Having rebooted Haiku maybe 20 times (shutdown -r in UserBootscript) it didn't happen, so I think it's fixed. Thanks J?r?me! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Mar 27 22:52:55 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 27 Mar 2008 21:52:55 -0000 Subject: [Haiku-bugs] [Haiku] #1909: emuxki/midi related KDLs? In-Reply-To: <048.7c433231494081c4264c03b82f3ce97f@haiku-os.org> References: <048.7c433231494081c4264c03b82f3ce97f@haiku-os.org> Message-ID: <057.c72bb5a9584126a41eee94ffd95f7bd3@haiku-os.org> #1909: emuxki/midi related KDLs? ----------------------------+----------------------------------------------- Reporter: jonas.kirilla | Owner: korli Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: fixed | Platform: All ----------------------------+----------------------------------------------- Changes (by korli): * status: new => closed * resolution: => fixed Comment: Fixed in r24597. Thanks for testing! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 28 06:32:40 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 28 Mar 2008 05:32:40 -0000 Subject: [Haiku-bugs] [Haiku] #1974: PackageInstaller unable to open Subversion.pkg file from haiku-os.org Message-ID: <042.6bb419b2a508d63893383c3c27c4c456@haiku-os.org> #1974: PackageInstaller unable to open Subversion.pkg file from haiku-os.org -----------------------+---------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- PackageInstaller not able to open the Subversion .pkg file on Haiku- os.org. Seems this would be a requirement for someone to be able to set up a build system on Haiku. ;) Screenshot attached. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 28 06:43:15 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 28 Mar 2008 05:43:15 -0000 Subject: [Haiku-bugs] [Haiku] #1974: PackageInstaller unable to open Subversion.pkg file from haiku-os.org In-Reply-To: <042.6bb419b2a508d63893383c3c27c4c456@haiku-os.org> References: <042.6bb419b2a508d63893383c3c27c4c456@haiku-os.org> Message-ID: <051.6e0ac82b6d22168482043a49831e63ef@haiku-os.org> #1974: PackageInstaller unable to open Subversion.pkg file from haiku-os.org ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by umccullough): Worked fine for me - just launch PackageInstaller (I navigated to the apps dir and launched it by double-clicking) and then use the open dialog to launch the subversion package. Then you just click on the Subversion banner that shows in the middle of the screeen. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 28 06:47:46 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 28 Mar 2008 05:47:46 -0000 Subject: [Haiku-bugs] [Haiku] #1974: PackageInstaller unable to open Subversion.pkg file from haiku-os.org In-Reply-To: <042.6bb419b2a508d63893383c3c27c4c456@haiku-os.org> References: <042.6bb419b2a508d63893383c3c27c4c456@haiku-os.org> Message-ID: <051.29a34ec3d36d66a57513d944e87bb7cb@haiku-os.org> #1974: PackageInstaller unable to open Subversion.pkg file from haiku-os.org ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by scottmc): You're right, that worked. So maybe this isn't a bug, or maybe the bug is that PackageInstaller doesn't work correctly from the commandline? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 28 07:04:30 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 28 Mar 2008 06:04:30 -0000 Subject: [Haiku-bugs] [Haiku] #1967: kdl using rtl8139 if_vr: packet not processed In-Reply-To: <042.fe3fb91518812a33d79bcd0beefe2745@haiku-os.org> References: <042.fe3fb91518812a33d79bcd0beefe2745@haiku-os.org> Message-ID: <051.2bc486b23b920ac6d2a8ea055beb6830@haiku-os.org> #1967: kdl using rtl8139 if_vr: packet not processed ---------------------------------+------------------------------------------ Reporter: bbjimmy | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Resolution: | Platform: x86 ---------------------------------+------------------------------------------ Comment (by bbjimmy): corection: PANIK: if_vr: no packet processed -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 28 07:16:27 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 28 Mar 2008 06:16:27 -0000 Subject: [Haiku-bugs] [Haiku] #1975: Boot splash doesn't show with intel i865 and CRT Message-ID: <046.fbd9978ddcd6f37a87cec9ff7fffb2bb@haiku-os.org> #1975: Boot splash doesn't show with intel i865 and CRT --------------------------------+------------------------------------------- Reporter: umccullough | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Boot Loader | Version: R1 development Platform: x86 | --------------------------------+------------------------------------------- Ever since the new boot splash was added, my Dell Optiplex GX270 no longer shows a boot splash using a Cornerstone Color 50/115 21" CRT. The video chip on the GX270 is an integrated Intel 82865G Tested with r24615 (serial log attached) If I manually specify a video mode using the boot menu, it shows up just fine. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 28 07:37:02 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 28 Mar 2008 06:37:02 -0000 Subject: [Haiku-bugs] [Haiku] #1975: Boot splash doesn't show with intel i865 and CRT In-Reply-To: <046.fbd9978ddcd6f37a87cec9ff7fffb2bb@haiku-os.org> References: <046.fbd9978ddcd6f37a87cec9ff7fffb2bb@haiku-os.org> Message-ID: <055.5e830e5e06d7f790fdd99a3fc8e8378c@haiku-os.org> #1975: Boot splash doesn't show with intel i865 and CRT ---------------------------------+------------------------------------------ Reporter: umccullough | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Boot Loader | Version: R1 development Resolution: | Platform: x86 ---------------------------------+------------------------------------------ Comment (by umccullough): In r24615 it appears to be choosing 1600x1200x8bpp - will test r24608 next. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 28 07:57:59 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 28 Mar 2008 06:57:59 -0000 Subject: [Haiku-bugs] [Haiku] #1975: Boot splash doesn't show with intel i865 and CRT In-Reply-To: <046.fbd9978ddcd6f37a87cec9ff7fffb2bb@haiku-os.org> References: <046.fbd9978ddcd6f37a87cec9ff7fffb2bb@haiku-os.org> Message-ID: <055.0edd117ec41dee44e79ef3a9a82ee2bf@haiku-os.org> #1975: Boot splash doesn't show with intel i865 and CRT ---------------------------------+------------------------------------------ Reporter: umccullough | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Boot Loader | Version: R1 development Resolution: | Platform: x86 ---------------------------------+------------------------------------------ Comment (by umccullough): Went back to r24608 (and also made sure to revert video.cpp) - then re- enabled TRACE_VIDEO and re-tested. Still apparently chooses 1600x1200x8bpp in the old rev. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 28 09:21:29 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 28 Mar 2008 08:21:29 -0000 Subject: [Haiku-bugs] [Haiku] #1974: PackageInstaller unable to open Subversion.pkg file from haiku-os.org In-Reply-To: <042.6bb419b2a508d63893383c3c27c4c456@haiku-os.org> References: <042.6bb419b2a508d63893383c3c27c4c456@haiku-os.org> Message-ID: <051.061fc41ad7312d1c98ebb4836081f392@haiku-os.org> #1974: PackageInstaller unable to open Subversion.pkg file from haiku-os.org ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by axeld): What we can definitely agree on is that it should just work by double clicking the package :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 28 09:23:26 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 28 Mar 2008 08:23:26 -0000 Subject: [Haiku-bugs] [Haiku] #1973: Video drivers and VESA driver don't work with VIA K8N800 video chipset In-Reply-To: <044.c690a35a0e5b6d7b59e9d6ffb3cf95aa@haiku-os.org> References: <044.c690a35a0e5b6d7b59e9d6ffb3cf95aa@haiku-os.org> Message-ID: <053.1a62a7aa5940e228c5f5e96af040805d@haiku-os.org> #1973: Video drivers and VESA driver don't work with VIA K8N800 video chipset -----------------------------------+---------------------------------------- Reporter: zaranthos | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/VIA | Version: R1 development Resolution: | Platform: x86 -----------------------------------+---------------------------------------- Comment (by axeld): Have you tried to enable "Use fail-safe video mode" from the safe-mode boot menu? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 28 09:25:36 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 28 Mar 2008 08:25:36 -0000 Subject: [Haiku-bugs] [Haiku] #1974: PackageInstaller unable to open Subversion.pkg file from haiku-os.org In-Reply-To: <042.6bb419b2a508d63893383c3c27c4c456@haiku-os.org> References: <042.6bb419b2a508d63893383c3c27c4c456@haiku-os.org> Message-ID: <051.68325320bb94bd77747313b760cfa1af@haiku-os.org> #1974: PackageInstaller unable to open Subversion.pkg file from haiku-os.org ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by umccullough): BTW, I was able to make it work from the commandline by qualifying the path to the package as such: $ PackageInstaller ./Subversion-1.1.3.pkg -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 28 10:24:55 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 28 Mar 2008 09:24:55 -0000 Subject: [Haiku-bugs] [Haiku] #1973: Video drivers and VESA driver don't work with VIA K8N800 video chipset In-Reply-To: <044.c690a35a0e5b6d7b59e9d6ffb3cf95aa@haiku-os.org> References: <044.c690a35a0e5b6d7b59e9d6ffb3cf95aa@haiku-os.org> Message-ID: <053.9c7272deabeacc262e72b95eb86db068@haiku-os.org> #1973: Video drivers and VESA driver don't work with VIA K8N800 video chipset -----------------------------------+---------------------------------------- Reporter: zaranthos | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/VIA | Version: R1 development Resolution: | Platform: x86 -----------------------------------+---------------------------------------- Comment (by axeld): The problem might be gone with r24620 - I've removed the VIA driver for now. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 28 10:27:11 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 28 Mar 2008 09:27:11 -0000 Subject: [Haiku-bugs] [Haiku] #1975: Boot splash doesn't show with intel i865 and CRT In-Reply-To: <046.fbd9978ddcd6f37a87cec9ff7fffb2bb@haiku-os.org> References: <046.fbd9978ddcd6f37a87cec9ff7fffb2bb@haiku-os.org> Message-ID: <055.26899da7c4970382a94ca349af057f6d@haiku-os.org> #1975: Boot splash doesn't show with intel i865 and CRT ---------------------------------+------------------------------------------ Reporter: umccullough | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Boot Loader | Version: R1 development Resolution: fixed | Platform: x86 ---------------------------------+------------------------------------------ Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Thanks! TRACE_VIDEO was very helpful indeed: what happens is the following: - EDID information could not be read for your monitor. - unlike most (all?) other cards I know, the VESA resolution table is ordered differently than usual. This broke the code that choose the right standard mode. In r24619 I've changed the way this mode is found. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 28 13:06:05 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 28 Mar 2008 12:06:05 -0000 Subject: [Haiku-bugs] [Haiku] #1925: Reboot during startup on Toshiba Satellite 2615DVD/6.0 In-Reply-To: <046.464cc1a60522972f4d6a4db8a13a4bd4@haiku-os.org> References: <046.464cc1a60522972f4d6a4db8a13a4bd4@haiku-os.org> Message-ID: <055.6dff3119b8e5616f1f665b46635ec308@haiku-os.org> #1925: Reboot during startup on Toshiba Satellite 2615DVD/6.0 ----------------------------+----------------------------------------------- Reporter: umccullough | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by axeld): The line "PANIC: looking up page failed for pa 0x41433000" can only be caused by vm_create_anonymous_area() when it tries to create areas for already bound memory. There seems to be something seriously wrong there, which is also underpinned by the fact that it doesn't find its way into the debugger. Could you also provide the output of TRACE_MMU in boot/platform/bios_ia32/mmu.cpp? Would it be possible that the memory is corrupt on this machine? Does it work flawlessly with other operating systems? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 28 14:55:56 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 28 Mar 2008 13:55:56 -0000 Subject: [Haiku-bugs] [Haiku] #1970: VM's sAvailableMemory counter is possibly inaccurate In-Reply-To: <044.e921a4a64e1421d6e6a9995b312a64a9@haiku-os.org> References: <044.e921a4a64e1421d6e6a9995b312a64a9@haiku-os.org> Message-ID: <053.46eba1e5b5dff638dda7a0da68202595@haiku-os.org> #1970: VM's sAvailableMemory counter is possibly inaccurate ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Changes (by bga): * cc: bga (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 28 15:30:42 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 28 Mar 2008 14:30:42 -0000 Subject: [Haiku-bugs] [Haiku] #1429: Icons for Chart, Mandelbrot, Email, Cody Cam and Disks use old style. In-Reply-To: <042.1555660311752b958e3000bceb70de58@haiku-os.org> References: <042.1555660311752b958e3000bceb70de58@haiku-os.org> Message-ID: <051.e47b8766c6966d2da34eac7b11de86db@haiku-os.org> #1429: Icons for Chart, Mandelbrot, Email, Cody Cam and Disks use old style. -----------------------------+---------------------------------------------- Reporter: scottmc | Owner: stippi Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Platform: All -----------------------------+---------------------------------------------- Comment (by scottmc): Looks like chart and disks icons are now in place as of r24609 at least. I'm not sure but it looks like the little speaker box for volume on the deskbar might be the old style as well? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 28 15:35:43 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 28 Mar 2008 14:35:43 -0000 Subject: [Haiku-bugs] [Haiku] #1956: Garbage In Files In-Reply-To: <043.b26038f2dc2fcacc60d26d407839e6d0@haiku-os.org> References: <043.b26038f2dc2fcacc60d26d407839e6d0@haiku-os.org> Message-ID: <052.a337ccea10371ed5e7aa73406700fd51@haiku-os.org> #1956: Garbage In Files ----------------------------+----------------------------------------------- Reporter: bonefish | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by bonefish): Replying to [comment:7 axeld]: > Should be fixed with r24607. If it doesn't happen for you anymore, please close this ticket. I hit the problem again with r24614. I suppose I have to reinitialize partitions that I used with an earlier BFS version, right? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 28 16:02:01 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 28 Mar 2008 15:02:01 -0000 Subject: [Haiku-bugs] [Haiku] #1956: Garbage In Files In-Reply-To: <043.b26038f2dc2fcacc60d26d407839e6d0@haiku-os.org> References: <043.b26038f2dc2fcacc60d26d407839e6d0@haiku-os.org> Message-ID: <052.ecc1ac471c5b15bbee11936ffcbee2c2@haiku-os.org> #1956: Garbage In Files ----------------------------+----------------------------------------------- Reporter: bonefish | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by axeld): You better should - unless you can run chkbfs on that partition and it doesn't notice a block is used twice. BTW how would I go about implement chkbfs on Haiku using the device API? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 28 16:54:46 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 28 Mar 2008 15:54:46 -0000 Subject: [Haiku-bugs] [Haiku] #1956: Garbage In Files In-Reply-To: <043.b26038f2dc2fcacc60d26d407839e6d0@haiku-os.org> References: <043.b26038f2dc2fcacc60d26d407839e6d0@haiku-os.org> Message-ID: <052.2a0e4532c01b815908440c22360e200e@haiku-os.org> #1956: Garbage In Files ----------------------------+----------------------------------------------- Reporter: bonefish | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by bonefish): Replying to [comment:9 axeld]: > BTW how would I go about implement chkbfs on Haiku using the device API? The most important part is obviously implementing the FS repair() hook. :-) I don't know, if everything from BPartition::Repair(), over the BFS userland add-on (I think that isn't implemented yet), over the syscall is wired correctly. The syscall definitely needs a review, and I also think we should consider making BPartition::Repair() immediate, just like Mount(). I don't think one ever wants to edit a few partitions and also schedule a repair on one at the same time (probably the same for Defragment()). I believe generally missing is a back channel from the repair() hook to the userland app. At the moment it can't be interactive ("Inode 19412 is toast. Remove it? [y/n]") at all. That's not so easy to implement in a generic way, though. The userland add-on would need to wrap all the communication with the kernel add-on and probably provide a GUI and a non- GUI alternative. For the communication itself a port could be used (obviously two threads are needed), which would be passed via a driver- settings-style parameters parameter. BPartition::Repair() could then work like this: It takes an additional BDiskDeviceOperationCallback (or, if we need it specialized: BPartitionRepairCallback (*Callback might not fit that well)), which is the interface for the userland add-on to interact with the application. I.e. it could pass a GUI to it, and call hooks for events that require interaction. Repair() would first check with the userland add-on, if repairing is generally OK and ask for additional parameters (driver- settings) to pass to the kernel. It would then spawn a thread and send it into the userland add-on, where it will do the communication with the kernel add-on and the callback object from the application until the repair operation is done. Afterwards Repair() invokes the syscall. Anyway, this is all pretty off-topic for this ticket. :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 28 17:22:37 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 28 Mar 2008 16:22:37 -0000 Subject: [Haiku-bugs] [Haiku] #1925: Reboot during startup on Toshiba Satellite 2615DVD/6.0 In-Reply-To: <046.464cc1a60522972f4d6a4db8a13a4bd4@haiku-os.org> References: <046.464cc1a60522972f4d6a4db8a13a4bd4@haiku-os.org> Message-ID: <055.07fba4ded4f4353173bde7118addcfe9@haiku-os.org> #1925: Reboot during startup on Toshiba Satellite 2615DVD/6.0 ----------------------------+----------------------------------------------- Reporter: umccullough | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by umccullough): It does work fine with Xubuntu on it (in fact, I used Xubuntu on this very machine to build Haiku onto the other partition) and previously had Windows XP on it with no issues that I ever recall. I believe I ran memtest86+ the other day to verify that very notion - but I only let it run through the first couple tests (as these usually find bad ram quickly in my experience). However, if it's a subtle memory issue I can let memtest86+ run through an ENTIRE pass of tests one night and see what it throws out. I will also turn on the TRACE_MMU and rebuild soon and report back my results. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 28 18:26:21 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 28 Mar 2008 17:26:21 -0000 Subject: [Haiku-bugs] [Haiku] #1973: Video drivers and VESA driver don't work with VIA K8N800 video chipset In-Reply-To: <044.c690a35a0e5b6d7b59e9d6ffb3cf95aa@haiku-os.org> References: <044.c690a35a0e5b6d7b59e9d6ffb3cf95aa@haiku-os.org> Message-ID: <053.b6b9017a21fc10a002b031d7c041caa5@haiku-os.org> #1973: Video drivers and VESA driver don't work with VIA K8N800 video chipset -----------------------------------+---------------------------------------- Reporter: zaranthos | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/VIA | Version: R1 development Resolution: | Platform: x86 -----------------------------------+---------------------------------------- Comment (by zaranthos): I've enabled syslog (no serial port for serial debugging. Does it work via USB?). I copied the via.settings file from Zeta to Haiku to capture logging and dump the video ROM file also in case that's useful. I have a few syslogs with different options in case that helps. I'll attach the file with logs and ROM dump. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 28 19:13:24 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 28 Mar 2008 18:13:24 -0000 Subject: [Haiku-bugs] [Haiku] #1973: Video drivers and VESA driver don't work with VIA K8N800 video chipset In-Reply-To: <044.c690a35a0e5b6d7b59e9d6ffb3cf95aa@haiku-os.org> References: <044.c690a35a0e5b6d7b59e9d6ffb3cf95aa@haiku-os.org> Message-ID: <053.82def58dc63dae0f12628898fb377d0c@haiku-os.org> #1973: Video drivers and VESA driver don't work with VIA K8N800 video chipset -----------------------------------+---------------------------------------- Reporter: zaranthos | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/VIA | Version: R1 development Resolution: | Platform: x86 -----------------------------------+---------------------------------------- Comment (by zaranthos): Tried r24609 (have to wait for the next nightly build for 24620) and fail safe video works. I did fail safe video plus VESA 1024x768 and it worked! That's not how any other version of BeOS works though since I was always able to just select the VESA mode I wanted without setting fail safe video. DHCP doesn't work with the network chipset and I can't tell if static works yet since there is no web browser. The sound isn't working either. Hopefully some of this info is helpful. :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 28 19:29:55 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 28 Mar 2008 18:29:55 -0000 Subject: [Haiku-bugs] [Haiku] #1974: PackageInstaller unable to open Subversion.pkg file from haiku-os.org In-Reply-To: <042.6bb419b2a508d63893383c3c27c4c456@haiku-os.org> References: <042.6bb419b2a508d63893383c3c27c4c456@haiku-os.org> Message-ID: <051.7ff670698f0ef6e2e02804d88160a2e1@haiku-os.org> #1974: PackageInstaller unable to open Subversion.pkg file from haiku-os.org ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by j_freeman): Same thing happens to me on real hardware with r24609. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 28 19:54:06 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 28 Mar 2008 18:54:06 -0000 Subject: [Haiku-bugs] [Haiku] #1970: VM's sAvailableMemory counter is possibly inaccurate In-Reply-To: <044.e921a4a64e1421d6e6a9995b312a64a9@haiku-os.org> References: <044.e921a4a64e1421d6e6a9995b312a64a9@haiku-os.org> Message-ID: <053.84bf956e697dbabca62ee0a14dc0950b@haiku-os.org> #1970: VM's sAvailableMemory counter is possibly inaccurate ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by bga): Looking at vm.cpp, it is obvious that sAvailableMemory can grown indefinitely if we keep calling vm_unreserve_memory() (or if we call it with a big enough value for amount, of course). As the code there is pretty straight-forward, I am convinced that this would be the case: void vm_unreserve_memory(size_t amount) { benaphore_lock(&sAvailableMemoryLock); sAvailableMemory += amount; benaphore_unlock(&sAvailableMemoryLock); } We have no check whatsoever for an upper bound value here. Another possibility is that vm_try_reserve_memory is not being called at some point when it should. Anyway, I added a panic() to vm_unreserve_memory() in case sAvailableMemory was bigger than the available physical memory. See attached screen shots of 2 code paths that resulted in the error. They do not look very helpful, unfortunately. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 28 20:16:54 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 28 Mar 2008 19:16:54 -0000 Subject: [Haiku-bugs] [Haiku] #1765: LaunchBox Not Always on All Workspaces In-Reply-To: <043.b4bbeb11419c129c2502f29e48deb9a5@haiku-os.org> References: <043.b4bbeb11419c129c2502f29e48deb9a5@haiku-os.org> Message-ID: <052.34f84eff8fa47df194094eb806d8372a@haiku-os.org> #1765: LaunchBox Not Always on All Workspaces -------------------------------------+-------------------------------------- Reporter: bonefish | Owner: stippi Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/LaunchBox | Version: R1 development Resolution: fixed | Platform: All -------------------------------------+-------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Fixed the app_server relevant part in r24632 - the current workspace was retrieved without holding the window lock which could therefore still return the old workspace with a bit of luck (or a fast machine with SMP :-)). Changed the application to use B_ALL_WORKSPACES in r24633 - now it also don't flicker anymore when switching workspaces. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 28 20:30:32 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 28 Mar 2008 19:30:32 -0000 Subject: [Haiku-bugs] [Haiku] #1925: Reboot during startup on Toshiba Satellite 2615DVD/6.0 In-Reply-To: <046.464cc1a60522972f4d6a4db8a13a4bd4@haiku-os.org> References: <046.464cc1a60522972f4d6a4db8a13a4bd4@haiku-os.org> Message-ID: <055.546e88875d2dc544787bf1b5fd788605@haiku-os.org> #1925: Reboot during startup on Toshiba Satellite 2615DVD/6.0 ----------------------------+----------------------------------------------- Reporter: umccullough | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by axeld): Don't worry about that; if other systems run that stable, there is something wrong with Haiku, I'd guess. It will probably corrupt some memory at some point of the boot process. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 28 20:46:48 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 28 Mar 2008 19:46:48 -0000 Subject: [Haiku-bugs] [Haiku] #1429: Icons for Mandelbrot and other demos as well as all the servers use old style. In-Reply-To: <042.1555660311752b958e3000bceb70de58@haiku-os.org> References: <042.1555660311752b958e3000bceb70de58@haiku-os.org> Message-ID: <051.f63e8dc0039b1313fe6144d8186deade@haiku-os.org> #1429: Icons for Mandelbrot and other demos as well as all the servers use old style. -----------------------------+---------------------------------------------- Reporter: scottmc | Owner: stippi Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Platform: All -----------------------------+---------------------------------------------- Changes (by stippi): * summary: Icons for Chart, Mandelbrot, Email, Cody Cam and Disks use old style. => Icons for Mandelbrot and other demos as well as all the servers use old style. Old description: > Are there plans to make all of the icons for all programs in Haiku use > the new style icons? I looked around and it seems only these 5 are left > to do? There might be some I missed. I searched through the other > tickets but didn't find any that addressed this specific issue. New description: Some filetypes that come included with apps need to be designed as well. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 28 20:50:27 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 28 Mar 2008 19:50:27 -0000 Subject: [Haiku-bugs] [Haiku] #1970: VM's sAvailableMemory counter is possibly inaccurate In-Reply-To: <044.e921a4a64e1421d6e6a9995b312a64a9@haiku-os.org> References: <044.e921a4a64e1421d6e6a9995b312a64a9@haiku-os.org> Message-ID: <053.7095f4cf9daad939fc799c3d259f0d81@haiku-os.org> #1970: VM's sAvailableMemory counter is possibly inaccurate ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by anevilyak): Is it reasonable to assume that a reservation of a given size should always be paired with a corresponding free of the same size? or is it possible that they could be aggregated? I.e. Is it safe to assume that we'll see a pattern like this: Reserve 500 Reserve 200 Unreserve 200 Unreserve 500 or is Unreserve 700 a possibility here? I'm wondering if adding some dprintfs to track the source and size of each reservation/unreservation might help find where we're not reserving when we should here, since our problem is evidently unreserving more than we reserve. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Mar 28 23:23:06 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 28 Mar 2008 22:23:06 -0000 Subject: [Haiku-bugs] [Haiku] #1950: Garbled screen contents with true colour mode on nvidia gf2mx In-Reply-To: <042.f15ad8e18c31676a011caebc5344d3a8@haiku-os.org> References: <042.f15ad8e18c31676a011caebc5344d3a8@haiku-os.org> Message-ID: <051.e914d3e843cf8bf3d1f74d3d90d0499c@haiku-os.org> #1950: Garbled screen contents with true colour mode on nvidia gf2mx ------------------------+--------------------------------------------------- Reporter: jopadan | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: x86 ------------------------+--------------------------------------------------- Comment (by peat): Same here (GeForce 4 Mx 440). Safemode GFX Setting (1280 x 1024 x 32 with Vesa Driver) works fine. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 29 00:18:28 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 28 Mar 2008 23:18:28 -0000 Subject: [Haiku-bugs] [Haiku] #1976: Installing Development package failes Message-ID: <044.1be3b03a867ca3f718f12b5ae151f762@haiku-os.org> #1976: Installing Development package failes --------------------------+------------------------------------------------- Reporter: plfiorini | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Platform: x86 | --------------------------+------------------------------------------------- Haiku rev24633, buildtools rev24633. Here's my UserBuildConfig: ######################## # Install Haiku on device /dev/sda57. Be sure you know what you're doing! HAIKU_IMAGE_DIR = /dev ; HAIKU_IMAGE_NAME = hda2 ; #HAIKU_DONT_CLEAR_IMAGE = 1 ; # Add symlink/file (timezone and keymap settings) to the image. AddSymlinkToHaikuImage home config settings : /boot/beos/etc/timezones/Europe/Rome : timezone ; AddFilesToHaikuImage home config settings : Italian : Key_map ; AddOptionalHaikuImagePackages Development ; ######################## Haiku was built using gcc 2.95.3. After a successful build I added the last line to my UserBuildConfig in order to install the Development package into the image, but I got the output I'm attaching to this report. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 29 01:17:43 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 29 Mar 2008 00:17:43 -0000 Subject: [Haiku-bugs] [Haiku] #1976: Installing Development package failes In-Reply-To: <044.1be3b03a867ca3f718f12b5ae151f762@haiku-os.org> References: <044.1be3b03a867ca3f718f12b5ae151f762@haiku-os.org> Message-ID: <053.99395c0577ed7d94de22a87af0bbf2b5@haiku-os.org> #1976: Installing Development package failes ---------------------------+------------------------------------------------ Reporter: plfiorini | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Platform: x86 ---------------------------+------------------------------------------------ Comment (by bonefish): Can you reproduce this or did it happen only once? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 29 01:25:53 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 29 Mar 2008 00:25:53 -0000 Subject: [Haiku-bugs] [Haiku] #1976: Installing Development package failes In-Reply-To: <044.1be3b03a867ca3f718f12b5ae151f762@haiku-os.org> References: <044.1be3b03a867ca3f718f12b5ae151f762@haiku-os.org> Message-ID: <053.070b8b5607e0ba06cd2b848ca9ab2e6a@haiku-os.org> #1976: Installing Development package failes ---------------------------+------------------------------------------------ Reporter: plfiorini | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Platform: x86 ---------------------------+------------------------------------------------ Comment (by plfiorini): That was my first build with gcc 2.95.3, so I've changed the UserBuildConfig in order to get the Development package installed and ran jam -q -j2 haiku-image. If now I create the haiku-image the error doesn't happen, last lines of the output: AddUnzipFileToContainerUnzipFilesScript haiku.image-unzip- files-dummy-home/config/bin-jam-haiku-gcc2-2008-03-27.zip AddUnzipFileToContainerUnzipFilesScript haiku.image-unzip- files-dummy-develop/tools-gcc-2.95.3-haiku-080323.zip AddUnzipFileToContainerUnzipFilesScript haiku.image-unzip- files-dummy-home-autoconf-2.61-gcc2-2008-03-24.zip AddUnzipFileToContainerUnzipFilesScript haiku.image-unzip- files-dummy-home-automake-1.10.1-gcc2-2008-03-24.zip AddUnzipFileToContainerUnzipFilesScript haiku.image-unzip- files-dummy-home-bison-2.3-gcc2-2008-03-28.zip AddUnzipFileToContainerUnzipFilesScript haiku.image-unzip- files-dummy-home-flex-2.5.35-gcc2-2008-03-28.zip AddUnzipFileToContainerUnzipFilesScript haiku.image-unzip- files-dummy-home-libtool-1.5.26-gcc2-2008-03-24.zip AddUnzipFileToContainerUnzipFilesScript haiku.image-unzip- files-dummy-home-texinfo-4.11-gcc2-2008-03-24.zip AddUnzipFileToContainerUnzipFilesScript haiku.image-unzip- files-dummy-home-perl-5.10.0-gcc2-2008-03-24.zip AppendToContainerCopyFilesScript haiku.image-copy-files-dummy- beos/system/lib BuildHaikuImage1 /dev/hda2 Creating image ... 100+0 records in 100+0 records out 104857600 bytes (105 MB) copied, 7,18794 seconds, 14,6 MB/s Partition::SetTo(): active: 0 Partition::SetTo(): active: 0 Partition::SetTo(): active: 0 Partition::SetTo(): active: 0 Writing boot code to "/dev/hda2" (partition offset: 399974400 bytes) ... Populating image ... Unzipping generated/download/jam-haiku-gcc2-2008-03-27.zip ... Unzipping generated/download/gcc-2.95.3-haiku-080323.zip ... Unzipping generated/download/autoconf-2.61-gcc2-2008-03-24.zip ... Unzipping generated/download/automake-1.10.1-gcc2-2008-03-24.zip ... Unzipping generated/download/bison-2.3-gcc2-2008-03-28.zip ... Unzipping generated/download/flex-2.5.35-gcc2-2008-03-28.zip ... Unzipping generated/download/libtool-1.5.26-gcc2-2008-03-24.zip ... Unzipping generated/download/texinfo-4.11-gcc2-2008-03-24.zip ... Unzipping generated/download/perl-5.10.0-gcc2-2008-03-24.zip ... Deleting old MIME database ... Installing MIME database ... Unmounting ... ...updated 246 target(s)... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 29 01:27:38 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 29 Mar 2008 00:27:38 -0000 Subject: [Haiku-bugs] [Haiku] #1976: Installing Development package failes In-Reply-To: <044.1be3b03a867ca3f718f12b5ae151f762@haiku-os.org> References: <044.1be3b03a867ca3f718f12b5ae151f762@haiku-os.org> Message-ID: <053.61d5e27f35386da49492ee125c3a939d@haiku-os.org> #1976: Installing Development package failes ---------------------------+------------------------------------------------ Reporter: plfiorini | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Platform: x86 ---------------------------+------------------------------------------------ Comment (by plfiorini): As you may already be aware by looking at my UserBuildConfig, I'm compiling from Linux (Debian 4.0 on VMWare). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 29 01:45:29 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 29 Mar 2008 00:45:29 -0000 Subject: [Haiku-bugs] [Haiku] #1976: Installing Development package failes In-Reply-To: <044.1be3b03a867ca3f718f12b5ae151f762@haiku-os.org> References: <044.1be3b03a867ca3f718f12b5ae151f762@haiku-os.org> Message-ID: <053.a138555376a7ed83cf34fa55477e8816@haiku-os.org> #1976: Installing Development package failes ---------------------------+------------------------------------------------ Reporter: plfiorini | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Platform: x86 ---------------------------+------------------------------------------------ Comment (by bonefish): Occasionally (seldom actually) I also get an error when building the image. This is pretty hard to debug, since it always works when building the next time, and it is always an error that theoretically can't happen (like in your case: copying the attributes always happens after creating the directory, so this error shouldn't be possible). I guess I'll have to add some logging to build_haiku_image and the bfs_shell. I'll leave this ticket open for the time being. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 29 01:48:13 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 29 Mar 2008 00:48:13 -0000 Subject: [Haiku-bugs] [Haiku] #1976: Installing Development package failes In-Reply-To: <044.1be3b03a867ca3f718f12b5ae151f762@haiku-os.org> References: <044.1be3b03a867ca3f718f12b5ae151f762@haiku-os.org> Message-ID: <053.f95eeb88e457f54951d38ec58865c021@haiku-os.org> #1976: Installing Development package failes ---------------------------+------------------------------------------------ Reporter: plfiorini | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Platform: x86 ---------------------------+------------------------------------------------ Comment (by umccullough): Possibly related to the use of -j2 ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 29 02:03:12 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 29 Mar 2008 01:03:12 -0000 Subject: [Haiku-bugs] [Haiku] #1945: [marvell yukon] 11ab:4320 not detected In-Reply-To: <040.6d7189e51f797abf4deca9c4e5ded43f@haiku-os.org> References: <040.6d7189e51f797abf4deca9c4e5ded43f@haiku-os.org> Message-ID: <049.a900d4acc6f6ad6cdbea1bf5f8927aff@haiku-os.org> #1945: [marvell yukon] 11ab:4320 not detected ------------------------------+--------------------------------------------- Reporter: diver | Owner: euan Type: enhancement | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Network | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Changes (by euan): * owner: axeld => euan * status: new => assigned * type: bug => enhancement Comment: OK the driver is now fixed. Just needed some tweaking to pipe the interrupts through the soft - interrupt interface. marvell_100.diff has been updated. Don't forget to add $(X86_ONLY)marvell_yukon_sk after the "marvell_yukon" entry in /build/jam/HaikuImage Disregard the glue.c attachment it's now redundant. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 29 00:38:39 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 28 Mar 2008 23:38:39 -0000 Subject: [Haiku-bugs] [Haiku] #1970: VM's sAvailableMemory counter is possibly inaccurate In-Reply-To: <044.e921a4a64e1421d6e6a9995b312a64a9@haiku-os.org> References: <044.e921a4a64e1421d6e6a9995b312a64a9@haiku-os.org> Message-ID: <053.9398ef1191eb7be286047bcd8f1547a2@haiku-os.org> #1970: VM's sAvailableMemory counter is possibly inaccurate ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by axeld): Reserving and unreserving does *not* happen in pairs. The only thing that has to happen is that they need to be balanced in the end - but that's obviously not what happens in some situations :-) I guess the best way would be to see where the commitment changes, and where sAvailableMemory is not properly updated. It might not be simple as the commitment cannot be handled equally for all types of caches. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 29 09:14:20 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 29 Mar 2008 08:14:20 -0000 Subject: [Haiku-bugs] [Haiku] #837: [app_server] crash in Desktop::Cursor() In-Reply-To: <040.b80f98b20f9cfa1b997b8dd28ecbd29e@haiku-os.org> References: <040.b80f98b20f9cfa1b997b8dd28ecbd29e@haiku-os.org> Message-ID: <049.e523f3a7fd89eb1749e3bd7460490e73@haiku-os.org> #837: [app_server] crash in Desktop::Cursor() ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: Servers/app_server | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by nielx): This ticket is a little bit vague for a nomination as blocker of the alpha 1 release. Diver, can you try to find a consistent method for reproduction? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 29 10:43:50 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 29 Mar 2008 09:43:50 -0000 Subject: [Haiku-bugs] [Haiku] #837: [app_server] crash in Desktop::Cursor() In-Reply-To: <040.b80f98b20f9cfa1b997b8dd28ecbd29e@haiku-os.org> References: <040.b80f98b20f9cfa1b997b8dd28ecbd29e@haiku-os.org> Message-ID: <049.1c611c37daa1af68e62e69ef822fb2ae@haiku-os.org> #837: [app_server] crash in Desktop::Cursor() ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: Servers/app_server | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by diver): I didnt' sow this crash for year now. I think its fixed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 29 11:37:40 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 29 Mar 2008 10:37:40 -0000 Subject: [Haiku-bugs] [Haiku] #837: [app_server] crash in Desktop::Cursor() In-Reply-To: <040.b80f98b20f9cfa1b997b8dd28ecbd29e@haiku-os.org> References: <040.b80f98b20f9cfa1b997b8dd28ecbd29e@haiku-os.org> Message-ID: <049.279f76c9799db2253c4d94575d1f357d@haiku-os.org> #837: [app_server] crash in Desktop::Cursor() ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: Servers/app_server | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by axeld): It hasn't been fixed yet, the code is still problematic. It only shows rarely, though (I remember running into it about two month ago the last time). Maybe it would be okay to move it to R1 instead, I dunno. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 29 11:43:50 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 29 Mar 2008 10:43:50 -0000 Subject: [Haiku-bugs] [Haiku] #1945: [marvell yukon] 11ab:4320 not detected In-Reply-To: <040.6d7189e51f797abf4deca9c4e5ded43f@haiku-os.org> References: <040.6d7189e51f797abf4deca9c4e5ded43f@haiku-os.org> Message-ID: <049.8f60a493ea3019ff6e411305ea5be063@haiku-os.org> #1945: [marvell yukon] 11ab:4320 not detected ------------------------------+--------------------------------------------- Reporter: diver | Owner: euan Type: enhancement | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Network | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by axeld): Maybe rename that driver to syskonnect? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 29 14:53:53 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 29 Mar 2008 13:53:53 -0000 Subject: [Haiku-bugs] [Haiku] #1977: build system : support multiple generated folders Message-ID: <041.de1921d2598def3a0f3b67265b9ce418@haiku-os.org> #1977: build system : support multiple generated folders --------------------------+------------------------------------------------- Reporter: mmadia | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Platform: x86 | --------------------------+------------------------------------------------- As the number of possible generated targets has increased over the years, It'd be nice if the build system would have the option to organize the user's generated directories. eg, generated: r5 bone zeta haiku gcc2 gcc4 This would be especially useful for those who build and keep multiple targets on the same system. This would also lay some foundation for creating software similar to Mozilla's Tinderboxes : http://www.mozilla.org/tinderbox.html , http://tinderbox.mozilla.org/ -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 29 15:30:40 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 29 Mar 2008 14:30:40 -0000 Subject: [Haiku-bugs] [Haiku] #1977: build system : support multiple generated folders In-Reply-To: <041.de1921d2598def3a0f3b67265b9ce418@haiku-os.org> References: <041.de1921d2598def3a0f3b67265b9ce418@haiku-os.org> Message-ID: <050.9d7a263e87b07795038decbdbd497af8@haiku-os.org> #1977: build system : support multiple generated folders ---------------------------+------------------------------------------------ Reporter: mmadia | Owner: bonefish Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: invalid | Platform: x86 ---------------------------+------------------------------------------------ Changes (by bonefish): * status: new => closed * resolution: => invalid Comment: The build system already supports multiple output directories. You can create an arbitrary directory and invoke the configure script from there. I usually create them in the root folder of the sources and call them generated-{gcc2,gcc4,ppc,test,...}, but you're free to create the hierarchy you proposed. To build in a specific output directory, you have to cd there to invoke "jam", or alternatively set the HAIKU_OUTPUT_DIR environment variable an run "jam" from within the source tree. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 29 15:35:08 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 29 Mar 2008 14:35:08 -0000 Subject: [Haiku-bugs] [Haiku] #1976: Installing Development package failes In-Reply-To: <044.1be3b03a867ca3f718f12b5ae151f762@haiku-os.org> References: <044.1be3b03a867ca3f718f12b5ae151f762@haiku-os.org> Message-ID: <053.7be08143babf0465c769300c32c44ea3@haiku-os.org> #1976: Installing Development package failes ---------------------------+------------------------------------------------ Reporter: plfiorini | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Platform: x86 ---------------------------+------------------------------------------------ Comment (by bonefish): Replying to [comment:5 umccullough]: > Possibly related to the use of -j2 ? Maybe. I think I recall having seen it also with the default "-j1", but I might be wrong. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 29 15:44:03 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 29 Mar 2008 14:44:03 -0000 Subject: [Haiku-bugs] [Haiku] #1978: 3rdparty : add support for Jamfile.haiku for independent 3rdparty source code Message-ID: <041.230f65b203a021e4107c3c84c4e40221@haiku-os.org> #1978: 3rdparty : add support for Jamfile.haiku for independent 3rdparty source code --------------------------+------------------------------------------------- Reporter: mmadia | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Platform: All | --------------------------+------------------------------------------------- Imagine Application_A currently has its own set of Jamfiles. It also has a Jamfile.haiku, which is only used when Application_A is located in haiku/3rdparty This is to help developers integrate independent applications into Haiku's build system more easily, without removing the ability to be built outside of the tree. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 29 15:50:57 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 29 Mar 2008 14:50:57 -0000 Subject: [Haiku-bugs] [Haiku] #1979: Blank processor name in About This System Message-ID: <044.8c3531e3c5766132f8606f90911b9f8f@haiku-os.org> #1979: Blank processor name in About This System -----------------------+---------------------------------------------------- Reporter: j_freeman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- The processor is blank in "About This System" under VMware. It used to say something like "AMD Athlon X2". Tested with r24635 on VMware Workstation. Not a problem under real hardware (Athlon XP). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 29 16:27:07 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 29 Mar 2008 15:27:07 -0000 Subject: [Haiku-bugs] [Haiku] #1970: VM's sAvailableMemory counter is possibly inaccurate In-Reply-To: <044.e921a4a64e1421d6e6a9995b312a64a9@haiku-os.org> References: <044.e921a4a64e1421d6e6a9995b312a64a9@haiku-os.org> Message-ID: <053.3d1b5d384f59811f2f383a3b282db8bb@haiku-os.org> #1970: VM's sAvailableMemory counter is possibly inaccurate ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by anevilyak): Fyi, the problem is reproducible with the following relatively simple test app: #include #include int main(int argc, char **argv) { printf("Allocating area of 1337 bytes\n"); void *addr = NULL; area_id id = create_area("rgtest", &addr, B_ANY_ADDRESS, 1337, B_NO_LOCK, B_READ_AREA); if (id > 0) printf("Area allocated successfully, id %ld, addr: %p\n", id, addr); printf("Destroying area of 1337 bytes\n"); delete_area(id); return 0; } running this app results in the following pattern of reserve/unreserves: ------------ KERN: try to reserve 90112 bytes, 1003679744 left KERN: Reserve of 90112 bytes succeeded, 1003589632 left KERN: try to reserve 8192 bytes, 1003589632 left KERN: Reserve of 8192 bytes succeeded, 1003581440 left KERN: try to reserve 4096 bytes, 1003581440 left KERN: Reserve of 4096 bytes succeeded, 1003577344 left KERN: try to reserve 65536 bytes, 1003577344 left KERN: Reserve of 65536 bytes succeeded, 1003511808 left KERN: try to reserve 4096 bytes, 1003511808 left KERN: Reserve of 4096 bytes succeeded, 1003507712 left KERN: try to reserve 577536 bytes, 1003507712 left KERN: Reserve of 577536 bytes succeeded, 1002930176 left KERN: try to reserve 28672 bytes, 1002930176 left KERN: Reserve of 28672 bytes succeeded, 1002901504 left KERN: try to reserve 4096 bytes, 1002901504 left KERN: Reserve of 4096 bytes succeeded, 1002897408 left KERN: try to reserve 638976 bytes, 1002897408 left KERN: Reserve of 638976 bytes succeeded, 1002258432 left KERN: try to reserve 32768 bytes, 1002258432 left KERN: Reserve of 32768 bytes succeeded, 1002225664 left KERN: try to reserve 204800 bytes, 1002225664 left KERN: Reserve of 204800 bytes succeeded, 1002020864 left KERN: try to reserve 339968 bytes, 1002020864 left KERN: Reserve of 339968 bytes succeeded, 1001680896 left KERN: Unreserved 0 bytes, 1001680896 left KERN: try to reserve 16384 bytes, 1001680896 left KERN: Reserve of 16384 bytes succeeded, 1001664512 left KERN: try to reserve 4096 bytes, 1001664512 left KERN: Reserve of 4096 bytes succeeded, 1001660416 left KERN: try to reserve 4096 bytes, 1001660416 left KERN: Reserve of 4096 bytes succeeded, 1001656320 left KERN: try to reserve 4096 bytes, 1001656320 left KERN: Reserve of 4096 bytes succeeded, 1001652224 left KERN: Unreserved 90112 bytes, 1001742336 left KERN: Unreserved 8192 bytes, 1001750528 left KERN: Unreserved 0 bytes, 1001750528 left KERN: Unreserved 4096 bytes, 1001754624 left KERN: Unreserved 0 bytes, 1001754624 left KERN: Unreserved 65536 bytes, 1001820160 left KERN: Unreserved 0 bytes, 1001820160 left KERN: Unreserved 4096 bytes, 1001824256 left KERN: Unreserved 0 bytes, 1001824256 left KERN: Unreserved 577536 bytes, 1002401792 left KERN: Unreserved 28672 bytes, 1002430464 left KERN: Unreserved 0 bytes, 1002430464 left KERN: Unreserved 4096 bytes, 1002434560 left KERN: Unreserved 0 bytes, 1002434560 left KERN: Unreserved 638976 bytes, 1003073536 left KERN: Unreserved 32768 bytes, 1003106304 left KERN: Unreserved 0 bytes, 1003106304 left KERN: Unreserved 204800 bytes, 1003311104 left KERN: Unreserved 0 bytes, 1003311104 left KERN: Unreserved 339968 bytes, 1003651072 left KERN: Unreserved 0 bytes, 1003651072 left KERN: Unreserved 12288 bytes, 1003663360 left KERN: Unreserved 0 bytes, 1003663360 left KERN: try to reserve 4096 bytes, 1003663360 left KERN: Reserve of 4096 bytes succeeded, 1003659264 left KERN: try to reserve 90112 bytes, 1003659264 left KERN: Reserve of 90112 bytes succeeded, 1003569152 left KERN: try to reserve 8192 bytes, 1003569152 left KERN: Reserve of 8192 bytes succeeded, 1003560960 left KERN: try to reserve 4096 bytes, 1003560960 left KERN: Reserve of 4096 bytes succeeded, 1003556864 left KERN: try to reserve 4096 bytes, 1003556864 left KERN: Reserve of 4096 bytes succeeded, 1003552768 left KERN: try to reserve 65536 bytes, 1003552768 left KERN: Reserve of 65536 bytes succeeded, 1003487232 left KERN: try to reserve 4096 bytes, 1003487232 left KERN: Reserve of 4096 bytes succeeded, 1003483136 left KERN: try to reserve 4096 bytes, 1003483136 left KERN: Reserve of 4096 bytes succeeded, 1003479040 left KERN: try to reserve 4096 bytes, 1003479040 left KERN: Reserve of 4096 bytes succeeded, 1003474944 left KERN: try to reserve 4096 bytes, 1003474944 left KERN: Reserve of 4096 bytes succeeded, 1003470848 left KERN: try to reserve 638976 bytes, 1003470848 left KERN: Reserve of 638976 bytes succeeded, 1002831872 left KERN: try to reserve 32768 bytes, 1002831872 left KERN: Reserve of 32768 bytes succeeded, 1002799104 left KERN: try to reserve 204800 bytes, 1002799104 left KERN: Reserve of 204800 bytes succeeded, 1002594304 left KERN: try to reserve 204800 bytes, 1002594304 left KERN: Reserve of 204800 bytes succeeded, 1002389504 left KERN: Unreserved 4096 bytes, 1002393600 left KERN: Unreserved 618496 bytes, 1003012096 left KERN: try to reserve 4096 bytes, 1003012096 left KERN: Reserve of 4096 bytes succeeded, 1003008000 left KERN: Unreserved 4096 bytes, 1003012096 left KERN: Unreserved 20480 bytes, 1003032576 left KERN: Unreserved 90112 bytes, 1003122688 left KERN: Unreserved 8192 bytes, 1003130880 left KERN: Unreserved 4096 bytes, 1003134976 left KERN: Unreserved 65536 bytes, 1003200512 left KERN: Unreserved 4096 bytes, 1003204608 left KERN: Unreserved 4096 bytes, 1003208704 left KERN: Unreserved 4096 bytes, 1003212800 left KERN: Unreserved 638976 bytes, 1003851776 left KERN: Unreserved 32768 bytes, 1003884544 left KERN: Unreserved 204800 bytes, 1004089344 left KERN: Unreserved 204800 bytes, 1004294144 left KERN: Unreserved 16384 bytes, 1004310528 left Notice that this is more than we started with. There's also some other weirdness in there like attempts to unreserve 0 bytes for some reason. Hope this helps. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 29 16:31:57 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 29 Mar 2008 15:31:57 -0000 Subject: [Haiku-bugs] [Haiku] #1979: Blank processor name in About This System In-Reply-To: <044.8c3531e3c5766132f8606f90911b9f8f@haiku-os.org> References: <044.8c3531e3c5766132f8606f90911b9f8f@haiku-os.org> Message-ID: <053.1bee171253f72cd07c89b917b735c1c1@haiku-os.org> #1979: Blank processor name in About This System ------------------------+--------------------------------------------------- Reporter: j_freeman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by j_freeman): Update: This seems to also occur on real hardware with an Athlon 64. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 29 17:11:14 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 29 Mar 2008 16:11:14 -0000 Subject: [Haiku-bugs] [Haiku] #1974: PackageInstaller unable to open Subversion.pkg file from haiku-os.org In-Reply-To: <042.6bb419b2a508d63893383c3c27c4c456@haiku-os.org> References: <042.6bb419b2a508d63893383c3c27c4c456@haiku-os.org> Message-ID: <051.cc72fbead6b37ab0a3cf14cf94443ab2@haiku-os.org> #1974: PackageInstaller unable to open Subversion.pkg file from haiku-os.org ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: sil2100 Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Changes (by sil2100): * owner: axeld => sil2100 Comment: Interesting. I will look into this issue as soon as possible, since it's more or less my responsibility ;-) If, of course, there are no objections. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 29 17:55:48 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 29 Mar 2008 16:55:48 -0000 Subject: [Haiku-bugs] [Haiku] #1980: Implement XSI semaphore and IPC API Message-ID: <040.56f95d83cc85c72016c7e381b6cda716@haiku-os.org> #1980: Implement XSI semaphore and IPC API -------------------------------+-------------------------------------------- Reporter: axeld | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: Unscheduled Component: System/libroot.so | Version: R1 development Platform: All | -------------------------------+-------------------------------------------- The XSI extensions of POSIX contains a portable IPC API. To ease porting of Unix applications, it would be beneficial if Haiku supported this extension. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 29 18:14:14 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 29 Mar 2008 17:14:14 -0000 Subject: [Haiku-bugs] [Haiku] #1979: Blank processor name in About This System In-Reply-To: <044.8c3531e3c5766132f8606f90911b9f8f@haiku-os.org> References: <044.8c3531e3c5766132f8606f90911b9f8f@haiku-os.org> Message-ID: <053.e4fd10e898cd95c9d1006f3e6c033892@haiku-os.org> #1979: Blank processor name in About This System ------------------------+--------------------------------------------------- Reporter: j_freeman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by axeld): And that only happened recently? What does "Pulse" say? And "sysinfo"? Can you give the exact model/stepping of your CPU? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 29 18:38:50 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 29 Mar 2008 17:38:50 -0000 Subject: [Haiku-bugs] [Haiku] #1979: Blank processor name in About This System In-Reply-To: <044.8c3531e3c5766132f8606f90911b9f8f@haiku-os.org> References: <044.8c3531e3c5766132f8606f90911b9f8f@haiku-os.org> Message-ID: <053.c60314e225221efb9a73c28778710837@haiku-os.org> #1979: Blank processor name in About This System ------------------------+--------------------------------------------------- Reporter: j_freeman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by j_freeman): I've only noticed it once before, and that was recently (in the last week). The CPU model is "ADA4200CUBOX". It's a 2.2GHz AMD Athlon 64 X2 (dual core) Windsor. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 29 18:55:19 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 29 Mar 2008 17:55:19 -0000 Subject: [Haiku-bugs] [Haiku] #837: [app_server] crash in Desktop::Cursor() In-Reply-To: <040.b80f98b20f9cfa1b997b8dd28ecbd29e@haiku-os.org> References: <040.b80f98b20f9cfa1b997b8dd28ecbd29e@haiku-os.org> Message-ID: <049.2d15f5e953f4e8963549ee8666e61ef6@haiku-os.org> #837: [app_server] crash in Desktop::Cursor() ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: Servers/app_server | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by stippi): I didn't see it either for a _long_ time, but yesterday I got a crash in HWInterface::_DrawCursor(), which I believe is originating from the same problem. I should write a test app which constantly changes the cursor shape, I think this is what triggers it, together with something else in the cursor code. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 29 20:29:50 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 29 Mar 2008 19:29:50 -0000 Subject: [Haiku-bugs] [Haiku] #1950: Garbled screen contents with true colour mode on nvidia gf2mx In-Reply-To: <042.f15ad8e18c31676a011caebc5344d3a8@haiku-os.org> References: <042.f15ad8e18c31676a011caebc5344d3a8@haiku-os.org> Message-ID: <051.e09c77d7e860db5ae015c97a16c34e56@haiku-os.org> #1950: Garbled screen contents with true colour mode on nvidia gf2mx ------------------------+--------------------------------------------------- Reporter: jopadan | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: x86 ------------------------+--------------------------------------------------- Comment (by aliensoldier): I have that bug also Geforce 2 MX400 i think (0x0110). the other day i got that bug in R5 also, only once. It was a once in a lifetime occurence type of bug, so i'm not able to reproduce it but i tought it might help point to a part of the solution. I was starting to play a video in VLC while i noticed i took the wrong one, so i stoped it just when the display was starting. From there i was having the same behavior than the haiku start bug and needed a reboot. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 29 20:47:06 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 29 Mar 2008 19:47:06 -0000 Subject: [Haiku-bugs] [Haiku] #1925: Reboot during startup on Toshiba Satellite 2615DVD/6.0 In-Reply-To: <046.464cc1a60522972f4d6a4db8a13a4bd4@haiku-os.org> References: <046.464cc1a60522972f4d6a4db8a13a4bd4@haiku-os.org> Message-ID: <055.d767da55c1f408e2592f1dff9bd04ae3@haiku-os.org> #1925: Reboot during startup on Toshiba Satellite 2615DVD/6.0 ----------------------------+----------------------------------------------- Reporter: umccullough | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by umccullough): Added another serial log with TRACE_MMU and TRACE_VM enabled. LOTS of info in this one :/ -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 29 20:56:11 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 29 Mar 2008 19:56:11 -0000 Subject: [Haiku-bugs] [Haiku] #1975: Boot splash doesn't show with intel i865 and CRT In-Reply-To: <046.fbd9978ddcd6f37a87cec9ff7fffb2bb@haiku-os.org> References: <046.fbd9978ddcd6f37a87cec9ff7fffb2bb@haiku-os.org> Message-ID: <055.23f4f0227c003442a01b1fb3fd91c86a@haiku-os.org> #1975: Boot splash doesn't show with intel i865 and CRT ---------------------------------+------------------------------------------ Reporter: umccullough | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Boot Loader | Version: R1 development Resolution: fixed | Platform: x86 ---------------------------------+------------------------------------------ Comment (by umccullough): Confirmed fixed - now chooses 1024x768x32bpp in r24660 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 29 21:07:58 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 29 Mar 2008 20:07:58 -0000 Subject: [Haiku-bugs] [Haiku] #1981: mail_daemon can not send mails Message-ID: <043.4176d1431dea833759361f5bf70d5819@haiku-os.org> #1981: mail_daemon can not send mails -----------------------+---------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- r24636 after creating the account settings, i send a mail; the mail was never sent, and it appears to the "in" directory -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 29 22:35:58 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 29 Mar 2008 21:35:58 -0000 Subject: [Haiku-bugs] [Haiku] #1442: [Workspaces] implement context menu support In-Reply-To: <040.d12308de942efeac8f4150bf4190ed7e@haiku-os.org> References: <040.d12308de942efeac8f4150bf4190ed7e@haiku-os.org> Message-ID: <049.3dcd941fae43223bbf6003d955941050@haiku-os.org> #1442: [Workspaces] implement context menu support --------------------------------------+------------------------------------- Reporter: diver | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Workspaces | Version: R1 development Resolution: | Platform: All --------------------------------------+------------------------------------- Comment (by diver): I suppose this could be closed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 29 22:38:15 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 29 Mar 2008 21:38:15 -0000 Subject: [Haiku-bugs] [Haiku] #605: [VLC] resizing main window doesn't work second time In-Reply-To: <040.954808f778b7a7e438936d7892f81c69@haiku-os.org> References: <040.954808f778b7a7e438936d7892f81c69@haiku-os.org> Message-ID: <049.553809c03d5b20b52d7c033860a0de24@haiku-os.org> #605: [VLC] resizing main window doesn't work second time ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by diver): * component: - General => Kits/Interface Kit Comment: I just checked and it still not working. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 29 22:39:49 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 29 Mar 2008 21:39:49 -0000 Subject: [Haiku-bugs] [Haiku] #926: [app_server] could dead lock when scrolling in NetPositive In-Reply-To: <040.c255cf763563c3d545ea7e5c87f12e05@haiku-os.org> References: <040.c255cf763563c3d545ea7e5c87f12e05@haiku-os.org> Message-ID: <049.5ce9b6d7b493f36b4a8655d7afc09717@haiku-os.org> #926: [app_server] could dead lock when scrolling in NetPositive ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by diver): * component: - General => Servers/app_server Comment: Nope. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 29 22:42:26 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 29 Mar 2008 21:42:26 -0000 Subject: [Haiku-bugs] [Haiku] #695: [ButterFly] crash on jpeg translator selection In-Reply-To: <040.8eaf256045813d5f6609f6f35c274052@haiku-os.org> References: <040.8eaf256045813d5f6609f6f35c274052@haiku-os.org> Message-ID: <049.f71339ecdedbca8fbb07f3b447f2e9ee@haiku-os.org> #695: [ButterFly] crash on jpeg translator selection ---------------------------+------------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by diver): Should be fixed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 29 22:46:43 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 29 Mar 2008 21:46:43 -0000 Subject: [Haiku-bugs] [Haiku] #1403: vlance driver calls acquire_sem_etc() from its interrupt routine In-Reply-To: <040.47891ae93a2af2afa21eb597269a0102@haiku-os.org> References: <040.47891ae93a2af2afa21eb597269a0102@haiku-os.org> Message-ID: <049.3cbd3f3d48d22210977e2ab9445120eb@haiku-os.org> #1403: vlance driver calls acquire_sem_etc() from its interrupt routine ------------------------------+--------------------------------------------- Reporter: diver | Owner: Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Network | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by diver): Is there any reason to keep this bug open? Or vlance driver is used somewhere outside vmware? If so, one should be ported from FreeBSD. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 29 22:48:09 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 29 Mar 2008 21:48:09 -0000 Subject: [Haiku-bugs] [Haiku] #1447: [ProcessController] sometimes takes to long to open menu In-Reply-To: <040.ee18a62fe673319ecbdf0cdf94346074@haiku-os.org> References: <040.ee18a62fe673319ecbdf0cdf94346074@haiku-os.org> Message-ID: <049.c2c7fc34615a00ebc96d9f2ed53340c6@haiku-os.org> #1447: [ProcessController] sometimes takes to long to open menu ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by diver): * component: - General => Kits/Interface Kit Comment: Shuld be fixed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 29 22:51:02 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 29 Mar 2008 21:51:02 -0000 Subject: [Haiku-bugs] [Haiku] #254: Wrongly enabled buttons in apps/prefs (easy) In-Reply-To: <040.d8c8cd1d285f2b0573c32a8a664894eb@haiku-os.org> References: <040.d8c8cd1d285f2b0573c32a8a664894eb@haiku-os.org> Message-ID: <049.979b1a7abc24308f686d29735c060508@haiku-os.org> #254: Wrongly enabled buttons in apps/prefs (easy) ---------------------------+------------------------------------------------ Reporter: diver | Owner: aldeck Type: bug | Status: new Priority: low | Milestone: R1 Component: Applications | Version: Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by diver): There are still problems with Background. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 29 22:53:33 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 29 Mar 2008 21:53:33 -0000 Subject: [Haiku-bugs] [Haiku] #484: MenuItem flickering In-Reply-To: <040.a9ee129cb8df850e3581b4efa52bee71@haiku-os.org> References: <040.a9ee129cb8df850e3581b4efa52bee71@haiku-os.org> Message-ID: <049.a759dbfc6b340ad522d9e240ab4824f0@haiku-os.org> #484: MenuItem flickering ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by diver): Can't reproduce under vmware, but on real hw i can, so it seems to be app_server problem indeed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 29 22:59:20 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 29 Mar 2008 21:59:20 -0000 Subject: [Haiku-bugs] [Haiku] #597: [Cortex] double click on audio mixer opens non-resizable window In-Reply-To: <040.805deb18716ca29f129c014aff63ed5f@haiku-os.org> References: <040.805deb18716ca29f129c014aff63ed5f@haiku-os.org> Message-ID: <049.30ca93fa742a045b7975fc73d0f87bc5@haiku-os.org> #597: [Cortex] double click on audio mixer opens non-resizable window -----------------------------+---------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Media Kit | Version: Resolution: | Platform: All -----------------------------+---------------------------------------------- Comment (by diver): Maybe Maurice want to have a look? ;-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 29 23:01:41 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 29 Mar 2008 22:01:41 -0000 Subject: [Haiku-bugs] [Haiku] #1315: [ScreenSaver] shifted images In-Reply-To: <040.b884e1091b64b11e72f50fba8a03b409@haiku-os.org> References: <040.b884e1091b64b11e72f50fba8a03b409@haiku-os.org> Message-ID: <049.dfc861872403c3783ff05b6e692ddc1b@haiku-os.org> #1315: [ScreenSaver] shifted images ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by diver): This is still reproduceble in both vmware and real hardware. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 29 23:04:58 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 29 Mar 2008 22:04:58 -0000 Subject: [Haiku-bugs] [Haiku] #1390: [app_server] Invalid opcode exception In-Reply-To: <040.c22ea4fb382184f71fd2a99eb3f6b578@haiku-os.org> References: <040.c22ea4fb382184f71fd2a99eb3f6b578@haiku-os.org> Message-ID: <049.55b6e247206da18fe187cbaa812a50ec@haiku-os.org> #1390: [app_server] Invalid opcode exception ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by diver): It never happend again. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Mar 29 23:53:56 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 29 Mar 2008 22:53:56 -0000 Subject: [Haiku-bugs] [Haiku] #1442: [Workspaces] implement context menu support In-Reply-To: <040.d12308de942efeac8f4150bf4190ed7e@haiku-os.org> References: <040.d12308de942efeac8f4150bf4190ed7e@haiku-os.org> Message-ID: <049.c902effc50c9741099e31050f5c98529@haiku-os.org> #1442: [Workspaces] implement context menu support --------------------------------------+------------------------------------- Reporter: diver | Owner: axeld Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Applications/Workspaces | Version: R1 development Resolution: fixed | Platform: All --------------------------------------+------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 30 04:15:47 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 30 Mar 2008 02:15:47 -0000 Subject: [Haiku-bugs] [Haiku] #1981: mail_daemon can not send mails In-Reply-To: <043.4176d1431dea833759361f5bf70d5819@haiku-os.org> References: <043.4176d1431dea833759361f5bf70d5819@haiku-os.org> Message-ID: <052.941b4a4a6b6ed181a8f39310557711de@haiku-os.org> #1981: mail_daemon can not send mails ------------------------+--------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Changes (by koki): * cc: koki (added) Comment: I can confirm this. In my case, when trying to send an email, I get a window titled "Mail Daemon Status Log" that shows the following message: email at domain.com: Error while getting a message. Name not found [Sat Mar 29 19:09:28 2008] This is a wild guess, but could this be related to bug #1751 ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 30 05:37:09 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 30 Mar 2008 03:37:09 -0000 Subject: [Haiku-bugs] [Haiku] #1044: USB OHCI support In-Reply-To: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> References: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> Message-ID: <054.9d5d72a7850835f069a0ba9843742173@haiku-os.org> #1044: USB OHCI support --------------------------+------------------------------------------------- Reporter: wkornewald | Owner: emitrax Type: enhancement | Status: new Priority: normal | Milestone: R1/alpha1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Changes (by j_freeman): * cc: j_freeman (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 30 11:02:36 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 30 Mar 2008 09:02:36 -0000 Subject: [Haiku-bugs] [Haiku] #837: [app_server] crash in Desktop::Cursor() In-Reply-To: <040.b80f98b20f9cfa1b997b8dd28ecbd29e@haiku-os.org> References: <040.b80f98b20f9cfa1b997b8dd28ecbd29e@haiku-os.org> Message-ID: <049.995bc921cadfcac62ec85eb9df75bf31@haiku-os.org> #837: [app_server] crash in Desktop::Cursor() ---------------------------------+------------------------------------------ Reporter: diver | Owner: stippi Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: Servers/app_server | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by nielx): * owner: axeld => stippi Comment: Replying to [comment:6 axeld]: > It hasn't been fixed yet, the code is still problematic. It only shows rarely, though (I remember running into it about two month ago the last time). > Maybe it would be okay to move it to R1 instead, I dunno. Let's keep it here until we are at a later stage in the alpha 1 process, and then reevaluate. Anyway, assigning to stippi because he should write a test app :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 30 12:37:19 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 30 Mar 2008 10:37:19 -0000 Subject: [Haiku-bugs] [Haiku] #1982: unmount bug: PANIC: vm_page_fault: unhandled page fault in kernel Message-ID: <040.07f9632ff503a91bdd3f366026b60cfc@haiku-os.org> #1982: unmount bug: PANIC: vm_page_fault: unhandled page fault in kernel ---------------------------+------------------------------------------------ Reporter: thorn | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Platform: x86 | ---------------------------+------------------------------------------------ Haiku r24635 how to repeat: * mount bfs volume from tracker (for example /work) * in terminal - ''cd /work'' * in tracker - unmount volume and press 'cancel' * in tracker - unmount volume again * in terminal - ''ls'' {{{ vm_soft_fault: va 0xdeadbef3 not covered by area in address space vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0xdeadbef3, ip 0x80047d37, write 0, user 0, thread 0x86 PANIC: vm_page_fault: unhandled page fault in kernel space at 0xdeadbef3, ip 0x80047d37 Welcome to Kernel Debugging Land... Running on CPU 0 kdebug> bt stack trace for thread 134 "sh" kernel stack: 0x92720000 to 0x92724000 user stack: 0x7efe7000 to 0x7ffe7000 frame caller :function + offset 92723a18 (+ 52) 800843f3 :invoke_debugger_command + 0x00cf 92723a4c (+ 64) 80085194 :_ParseCommand__16ExpressionParserRi + 0x01f8 92723a8c (+ 48) 80084b86 :EvaluateCommand__16ExpressionParserPCcRi + 0x01de 92723abc (+ 228) 800862a8 :evaluate_debug_command + 0x0088 92723ba0 (+ 64) 80082f36 :kernel_debugger_loop__Fv + 0x017a 92723be0 (+ 48) 80083be1 :kernel_debugger + 0x010d 92723c10 (+ 192) 80083ac9 :panic + 0x0029 92723cd0 (+ 64) 8005ca63 :vm_page_fault + 0x00ab 92723d10 (+ 64) 80090a85 :page_fault_exception + 0x00b1 92723d50 (+ 12) 8009418d :int_bottom + 0x001d (nearest) iframe at 0x92723d5c (end = 0x92723db4) eax 0xdeadbeef ebx 0x90a24c00 ecx 0x800c7e7b edx 0x2e esi 0x90a24c01 edi 0x90b44880 ebp 0x92723df4 esp 0x92723d90 eip 0x80047d37 eflags 0x10206 vector: 0xe, error code: 0x0 92723d5c (+ 152) 80047d37 :vnode_path_to_vnode__FP5vnodePcbiPP5vnodePxPi + 0x0103 92723df4 (+ 64) 800480ee :path_to_vnode__FPcbPP5vnodePxT1 + 0x00de 92723e34 (+ 64) 800488c9 :fd_and_path_to_vnode__FiPcbPP5vnodePxT2 + 0x0061 92723e74 (+ 64) 8004ccd5 :common_path_read_stat__FiPcbP4statT2 + 0x0031 92723eb4 (+ 144) 8005198b :_user_read_stat + 0x00eb 92723f44 (+ 100) 80094302 :pre_syscall_debug_done + 0x0002 (nearest) iframe at 0x92723fa8 (end = 0x92724000) eax 0x72 ebx 0x33459c ecx 0x7ffe6c10 edx 0xffff0104 esi 0x0 edi 0x1800ce13 ebp 0x7ffe6c4c esp 0x92723fdc eip 0xffff0104 eflags 0x207 vector: 0x63, error code: 0x0 92723fa8 (+ 0) ffff0104 7ffe6c4c (+ 48) 00310499 :stat + 0x0025 7ffe6c7c (+ 128) 00244f57 <_APP_>:user_command_matches + 0x04cb (nearest) 7ffe6cfc (+ 48) 00244882 <_APP_>:find_path_file + 0x009a (nearest) 7ffe6d2c (+ 48) 002448af <_APP_>:find_path_file + 0x00c7 (nearest) 7ffe6d5c (+ 48) 002447e1 <_APP_>:find_user_command + 0x0021 7ffe6d8c (+ 48) 00244a50 <_APP_>:search_for_command + 0x0138 7ffe6dbc (+ 48) 00227bcc <_APP_>:setup_async_signals + 0x00dc (nearest) 7ffe6dec (+ 112) 002271c1 <_APP_>:execute_command_internal + 0x344d (nearest) 7ffe6e5c (+ 96) 00224232 <_APP_>:execute_command_internal + 0x04be 7ffe6ebc (+ 80) 00223bbd <_APP_>:execute_command + 0x0065 7ffe6f0c (+ 48) 0021f879 <_APP_>:reader_loop + 0x01d1 7ffe6f3c (+ 64) 0021dab6 <_APP_>:main + 0x07b2 7ffe6f7c (+ 48) 00216773 <_APP_>:_start + 0x005b 7ffe6fac (+ 48) 0010078e 1358:runtime_loader_seg0ro at 0x00100000 + 0x78e 7ffe6fdc (+ 0) 7ffe6fec 1357:sh_main_stack at 0x7efe7000 + 0xffffec kdebug> }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 30 13:02:08 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 30 Mar 2008 11:02:08 -0000 Subject: [Haiku-bugs] [Haiku] #1962: Some resolutions in VESA no longer work In-Reply-To: <044.144153a4a47b9e6b368c0cb2527e4b97@haiku-os.org> References: <044.144153a4a47b9e6b368c0cb2527e4b97@haiku-os.org> Message-ID: <053.369e44432761bc378fe1eee632832e09@haiku-os.org> #1962: Some resolutions in VESA no longer work ------------------------+--------------------------------------------------- Reporter: j_freeman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by axeld): Should be fixed with r24675. Please retest. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 30 15:23:28 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 30 Mar 2008 13:23:28 -0000 Subject: [Haiku-bugs] [Haiku] #1914: PANIC: vnode 5:45465 already exists (node = 0x90c1b300, vnode->node = 0x91053d80)! In-Reply-To: <040.572daffe104be83e982ae20fb33b51e3@haiku-os.org> References: <040.572daffe104be83e982ae20fb33b51e3@haiku-os.org> Message-ID: <049.3f26fc2cc6ba9ebd22f45db7f5412e1d@haiku-os.org> #1914: PANIC: vnode 5:45465 already exists (node = 0x90c1b300, vnode->node = 0x91053d80)! ----------------------------+----------------------------------------------- Reporter: thorn | Owner: axeld Type: bug | Status: reopened Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Changes (by thorn): * status: closed => reopened * resolution: fixed => Comment: Axel, kld again. on Haiku r24635, vmware, 256M ram, 1st ata master 250M, 1st ata slave 2G, block size - 2K. kdled on ''svn co svn://svn.berlios.de/haiku/buildtools/trunk buildtools'' {{{ kdebug> message vnode 5:553669 already exists (node = 0x9102c780, vnode->node = 0x91115480)! kdebug> sc stack trace for thread 197 "svn" kernel stack: 0x9276a000 to 0x9276e000 user stack: 0x7efe7000 to 0x7ffe7000 frame caller :function + offset 9276d97c (+ 52) 800843f3 :invoke_debugger_command + 0x00cf 9276d9b0 (+ 64) 80085194 :_ParseCommand__16ExpressionParserRi + 0x01f8 9276d9f0 (+ 48) 80084b86 :EvaluateCommand__16ExpressionParserPCcRi + 0x01de 9276da20 (+ 228) 800862a8 :evaluate_debug_command + 0x0088 9276db04 (+ 64) 80082f36 :kernel_debugger_loop__Fv + 0x017a 9276db44 (+ 48) 80083be1 :kernel_debugger + 0x010d 9276db74 (+ 192) 80083ac9 :panic + 0x0029 9276dc34 (+ 64) 80049876 :new_vnode + 0x005a 9276dc74 (+ 64) 8032be06 :New__14InodeAllocatorP9block_runUiR9block_runPP5Inode + 0x014a 9276dcb4 (+ 176) 803324dd :Create__5InodeR11TransactionP5InodePCcliUlPbPxPP5Inode + 0x0571 9276dd64 (+ 96) 8033cccb :bfs_create_dir__FPvT0PCciPx + 0x0107 9276ddc4 (+ 320) 8004bcc6 :dir_create__FiPcib + 0x0082 9276df04 (+ 64) 800510d4 :_user_create_dir + 0x0094 9276df44 (+ 100) 80094302 :pre_syscall_debug_done + 0x0002 (nearest) iframe at 0x9276dfa8 (end = 0x9276e000) eax 0x55 ebx 0x45959c ecx 0x7ffe6644 edx 0xffff0104 esi 0x1b726960 edi 0x1b726960 ebp 0x7ffe6670 esp 0x9276dfdc eip 0xffff0104 eflags 0x206 vector: 0x63, error code: 0x0 9276dfa8 (+ 0) ffff0104 7ffe6670 (+ 48) 0032691f :unknown + 0xf91f 7ffe66a0 (+ 144) 002c8516 :unknown + 0xd516 7ffe6730 (+ 64) 002c864f :unknown + 0xd64f 7ffe6770 (+ 48) 0023b894 :unknown + 0x6894 7ffe67a0 (+ 64) 0023ba72 :unknown + 0x6a72 7ffe67e0 (+ 64) 0023bc46 :unknown + 0x6c46 7ffe6820 (+ 64) 0024d480 :unknown + 0x18480 7ffe6860 (+ 176) 0024dd6d :unknown + 0x18d6d 7ffe6910 (+ 64) 002b4bc5 :unknown + 0x1bc5 7ffe6950 (+ 96) 00299f78 :unknown + 0x7f78 7ffe69b0 (+ 112) 0029ab5a :unknown + 0x8b5a 7ffe6a20 (+ 80) 00299126 :unknown + 0x7126 7ffe6a70 (+ 64) 00295466 :unknown + 0x3466 7ffe6ab0 (+ 176) 0023a1dc :unknown + 0x51dc 7ffe6b60 (+ 160) 00230426 :unknown + 0x18426 7ffe6c00 (+ 112) 0021f421 :unknown + 0x7421 7ffe6c70 (+ 64) 0021f544 :unknown + 0x7544 7ffe6cb0 (+ 80) 0020574e :unknown + 0x574e 7ffe6d00 (+ 640) 002091fc :unknown + 0x91fc 7ffe6f80 (+ 44) 00204c45 :unknown + 0x4c45 7ffe6fac (+ 48) 0010078e 1687:runtime_loader_seg0ro at 0x00100000 + 0x78e 7ffe6fdc (+ 0) 7ffe6fec 1686:svn_main_stack at 0x7efe7000 + 0xffffec kdebug> cache -p [*** READ/WRITE FAULT ***] }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 30 15:30:12 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 30 Mar 2008 13:30:12 -0000 Subject: [Haiku-bugs] [Haiku] #1983: npipefs: could not resolve symbol 'new_lock' Message-ID: <040.b19df3da374a73c908d2a011d2e4e2fe@haiku-os.org> #1983: npipefs: could not resolve symbol 'new_lock' --------------------------+------------------------------------------------- Reporter: thorn | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems | Version: R1 development Platform: x86 | --------------------------+------------------------------------------------- Haiku r24635 from serial log {{{ KDiskDeviceManager::_AddDiskSystem() done: No error "/boot/home/config/add-ons/kernel/file_systems/npipefs": could not resolve symbol 'new_lock' Could not load kernel add-on "/boot/home/config/add- ons/kernel/file_systems/npipefs": Symbol not found load_module_image(/boot/home/config/add-ons/kernel/file_systems/npipefs) failed: Symbol not found }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 30 15:36:04 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 30 Mar 2008 13:36:04 -0000 Subject: [Haiku-bugs] [Haiku] #1914: PANIC: vnode 5:45465 already exists (node = 0x90c1b300, vnode->node = 0x91053d80)! In-Reply-To: <040.572daffe104be83e982ae20fb33b51e3@haiku-os.org> References: <040.572daffe104be83e982ae20fb33b51e3@haiku-os.org> Message-ID: <049.704c8a82d31ada8516db129eabd70d5a@haiku-os.org> #1914: PANIC: vnode 5:45465 already exists (node = 0x90c1b300, vnode->node = 0x91053d80)! ----------------------------+----------------------------------------------- Reporter: thorn | Owner: axeld Type: bug | Status: reopened Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by thorn): log before KDL {{{ SCSI_DSK -- synchronize_cache: wait interval 943681, scan pages 968, free 4094, target 258 bfs: Insert:1306: Name in use Last message repeated 5 times. wait interval 973150, scan pages 730, free 4229, target 123 bfs: Insert:1306: Name in use Last message repeated 2 times. wait interval 984064, scan pages 641, free 4279, target 73 bfs: Insert:1306: Name in use Last message repeated 4 times. wait interval 986902, scan pages 618, free 4292, target 60 bfs: Insert:1306: Name in use PANIC: vnode 5:553669 already exists (node = 0x9102c780, vnode->node = 0x91115480)! Welcome to Kernel Debugging Land... Running on CPU 0 kdebug> bt stack trace for thread 197 "svn" }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 30 15:36:27 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 30 Mar 2008 13:36:27 -0000 Subject: [Haiku-bugs] [Haiku] #1983: npipefs: could not resolve symbol 'new_lock' In-Reply-To: <040.b19df3da374a73c908d2a011d2e4e2fe@haiku-os.org> References: <040.b19df3da374a73c908d2a011d2e4e2fe@haiku-os.org> Message-ID: <049.681c5466a65c0e7a4a25b1405439c273@haiku-os.org> #1983: npipefs: could not resolve symbol 'new_lock' ---------------------------+------------------------------------------------ Reporter: thorn | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: File Systems | Version: R1 development Resolution: invalid | Platform: x86 ---------------------------+------------------------------------------------ Changes (by axeld): * status: new => closed * resolution: => invalid Comment: The lock API in the BeOS kernel is private. BeOS file systems cannot be used in Haiku. The npipefs provides no additional value over the Haiku pipefs implementation, anyway. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 30 15:38:06 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 30 Mar 2008 13:38:06 -0000 Subject: [Haiku-bugs] [Haiku] #1914: PANIC: vnode 5:45465 already exists (node = 0x90c1b300, vnode->node = 0x91053d80)! In-Reply-To: <040.572daffe104be83e982ae20fb33b51e3@haiku-os.org> References: <040.572daffe104be83e982ae20fb33b51e3@haiku-os.org> Message-ID: <049.22dd0111decf2d84d11d876ac4706e3e@haiku-os.org> #1914: PANIC: vnode 5:45465 already exists (node = 0x90c1b300, vnode->node = 0x91053d80)! ----------------------------+----------------------------------------------- Reporter: thorn | Owner: axeld Type: bug | Status: reopened Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by axeld): Are you sure you've initialized your BFS volume, and are not using an older one from before the fix? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 30 15:47:39 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 30 Mar 2008 13:47:39 -0000 Subject: [Haiku-bugs] [Haiku] #1984: bulding haiku on haiku-host fails at ... Message-ID: <043.e1d8aee9f24ccbc1be759ecd3448e84c@haiku-os.org> #1984: bulding haiku on haiku-host fails at ... -----------------------+---------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- {{{ C++ generated/objects/haiku/x86/release/libs/stdc++/cstrio.o In file included from /haiku- src/develop/HaikuTree/trunk/src/system/libroot/posix/glibc/include/bits/waitstatus.h:63, from /haiku- src/develop/HaikuTree/trunk/src/system/libroot/posix/glibc/stdlib/stdlib.h:44, from /haiku- src/develop/HaikuTree/trunk/headers/cpp/stl_alloc.h:59, from /haiku- src/develop/HaikuTree/trunk/headers/cpp/alloc.h:21, from /haiku- src/develop/HaikuTree/trunk/headers/cpp/std/bastring.h:39, from /haiku- src/develop/HaikuTree/trunk/headers/cpp/string:6, from /haiku- src/develop/HaikuTree/trunk/src/libs/stdc++/sinst.cc:36: /haiku- src/develop/HaikuTree/trunk/src/system/libroot/posix/glibc/include/endian.h:1: string/endian.h: Operation not allowed In file included from /haiku- src/develop/HaikuTree/trunk/src/system/libroot/posix/glibc/stdlib/stdlib.h:44, from /haiku- src/develop/HaikuTree/trunk/headers/cpp/stl_alloc.h:59, from /haiku- src/develop/HaikuTree/trunk/headers/cpp/alloc.h:21, from /haiku- src/develop/HaikuTree/trunk/headers/cpp/std/bastring.h:39, from /haiku- src/develop/HaikuTree/trunk/headers/cpp/string:6, from /haiku- src/develop/HaikuTree/trunk/src/libs/stdc++/sinst.cc:36: /haiku- src/develop/HaikuTree/trunk/src/system/libroot/posix/glibc/include/bits/waitstatus.h:78: declaration of `unsigned int wait::{anonymous struct}::__w_retcode' /haiku- src/develop/HaikuTree/trunk/src/system/libroot/posix/glibc/include/bits/waitstatus.h:73: conflicts with previous declaration `unsigned int wait::{anonymous struct}::__w_retcode' /haiku- src/develop/HaikuTree/trunk/src/system/libroot/posix/glibc/include/bits/waitstatus.h:79: declaration of `unsigned int wait::{anonymous struct}::__w_coredump' /haiku- src/develop/HaikuTree/trunk/src/system/libroot/posix/glibc/include/bits/waitstatus.h:72: conflicts with previous declaration `unsigned int wait::{anonymous struct}::__w_coredump' /haiku- src/develop/HaikuTree/trunk/src/system/libroot/posix/glibc/include/bits/waitstatus.h:80: declaration of `unsigned int wait::{anonymous struct}::__w_termsig' /haiku- src/develop/HaikuTree/trunk/src/system/libroot/posix/glibc/include/bits/waitstatus.h:71: conflicts with previous declaration `unsigned int wait::{anonymous struct}::__w_termsig' /haiku- src/develop/HaikuTree/trunk/src/system/libroot/posix/glibc/include/bits/waitstatus.h:80: duplicate member `wait::{anonymous struct}::__w_termsig' /haiku- src/develop/HaikuTree/trunk/src/system/libroot/posix/glibc/include/bits/waitstatus.h:79: duplicate member `wait::{anonymous struct}::__w_coredump' /haiku- src/develop/HaikuTree/trunk/src/system/libroot/posix/glibc/include/bits/waitstatus.h:78: duplicate member `wait::{anonymous struct}::__w_retcode' /haiku- src/develop/HaikuTree/trunk/src/system/libroot/posix/glibc/include/bits/waitstatus.h:92: declaration of `unsigned int wait::{anonymous struct}::__w_stopsig' /haiku- src/develop/HaikuTree/trunk/src/system/libroot/posix/glibc/include/bits/waitstatus.h:87: conflicts with previous declaration `unsigned int wait::{anonymous struct}::__w_stopsig' /haiku- src/develop/HaikuTree/trunk/src/system/libroot/posix/glibc/include/bits/waitstatus.h:93: declaration of `unsigned int wait::{anonymous struct}::__w_stopval' /haiku- src/develop/HaikuTree/trunk/src/system/libroot/posix/glibc/include/bits/waitstatus.h:86: conflicts with previous declaration `unsigned int wait::{anonymous struct}::__w_stopval' /haiku- src/develop/HaikuTree/trunk/src/system/libroot/posix/glibc/include/bits/waitstatus.h:93: duplicate member `wait::{anonymous struct}::__w_stopval' /haiku- src/develop/HaikuTree/trunk/src/system/libroot/posix/glibc/include/bits/waitstatus.h:92: duplicate member `wait::{anonymous struct}::__w_stopsig' gcc -c "src/libs/stdc++/sinst.cc" -O2 -Wall -Wno-trigraphs -Wno-ctor-dtor- privacy -Woverloaded-virtual -Wpointer-arith -Wcast-align -Wsign-compare -pipe -nostdinc -Wno-multichar -D_ZETA_USING_DEPRECATED_API_=1 -D_ZETA_TS_FIND_DIR_=1 -nostdinc++ -fno-implicit-templates -Wno-sign- compare -fpic -D__HAIKU__ -DHAIKU_DISTRO_COMPATIBILITY_DEFAULT-D__INTEL__ -DARCH_x86 -D_BEOS_R5_COMPATIBLE_ -DHAIKU_TARGET_PLATFORM_HAIKU -DC -DEXTRACT -DINSERT -DGETLINE -Ibuild/user_config_headers -Ibuild/config_headers -Isrc/libs/stdc++ -Igenerated/objects/common/libs/stdc++ -Igenerated/objects/haiku_host/x86/common/libs/stdc++ -Igenerated/objects/haiku/x86/common/libs/stdc++ -I- -Isrc/libs/stdc++-Isrc/system/libroot/posix/glibc/libio -Isrc/system/libroot/posix/glibc/stdlib -Isrc/system/libroot/posix/glibc /stdio-common -Isrc/system/libroot/posix/glibc/include -Isrc/system/libroot/posix/glibc/include/arch/x86 -Iheaders/cpp -Isrc/system/libroot/posix/glibc -Iheaders/posix -Iheaders/os -Iheaders/os/kernel -Iheaders/os/storage -Iheaders/os/support -Iheaders/build/gcc-2.95.3 -Iheaders/build/gcc-2.95.3 -Iheaders -Iheaders/posix -Iheaders/gnu -Iheaders/glibc -Iheaders/os -Iheaders/os /add-ons -Iheaders/os/add-ons/file_system -Iheaders/os/add-ons/graphics -Iheaders/os/add-ons/input_server -Iheaders/os/add-ons/registrar -Iheaders/os/add-ons/screen_saver -Iheaders/os/add-ons/tracker -Iheaders/os/app -Iheaders/os/device -Iheaders/os/drivers -Iheaders/os/game -Iheaders/os/interface -Iheaders/os/kernel -Iheaders/os/media -Iheaders/os/mail -Iheaders/os/midi -Iheaders/os/midi2 -Iheaders/os/net -Iheaders/os/opengl -Iheaders/os/storage -Iheaders/os/support -Iheaders/os/translation -Iheaders/private/. -Iheaders/cpp -o "generated/objects/haiku/x86/release/libs/stdc++/cstrio.o" ; ...failed C++ generated/objects/haiku/x86/release/libs/stdc++/cstrio.o ... ...skipped libstdc++.r4.so for lack of cstrio.o... ...skipped libbe.so for lack of libstdc++.r4.so... ...skipped libnetwork.so for lack of libbe.so... ...skipped server_with_socket for lack of libnetwork.so... ...failed updating 1 target(s)... ...skipped 4 target(s)... ...updated 651 target(s)... /haiku-src/develop/HaikuTree/trunk> }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 30 15:49:00 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 30 Mar 2008 13:49:00 -0000 Subject: [Haiku-bugs] [Haiku] #1985: bulding haiku on haiku-host fails at ... Message-ID: <043.99b02a402e3894907d9f209a64cb1bae@haiku-os.org> #1985: bulding haiku on haiku-host fails at ... --------------------------+------------------------------------------------- Reporter: kaoutsis | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Platform: All | --------------------------+------------------------------------------------- {{{ C++ generated/objects/haiku/x86/release/libs/stdc++/cstrio.o In file included from /haiku- src/develop/HaikuTree/trunk/src/system/libroot/posix/glibc/include/bits/waitstatus.h:63, from /haiku- src/develop/HaikuTree/trunk/src/system/libroot/posix/glibc/stdlib/stdlib.h:44, from /haiku- src/develop/HaikuTree/trunk/headers/cpp/stl_alloc.h:59, from /haiku- src/develop/HaikuTree/trunk/headers/cpp/alloc.h:21, from /haiku- src/develop/HaikuTree/trunk/headers/cpp/std/bastring.h:39, from /haiku- src/develop/HaikuTree/trunk/headers/cpp/string:6, from /haiku- src/develop/HaikuTree/trunk/src/libs/stdc++/sinst.cc:36: /haiku- src/develop/HaikuTree/trunk/src/system/libroot/posix/glibc/include/endian.h:1: string/endian.h: Operation not allowed In file included from /haiku- src/develop/HaikuTree/trunk/src/system/libroot/posix/glibc/stdlib/stdlib.h:44, from /haiku- src/develop/HaikuTree/trunk/headers/cpp/stl_alloc.h:59, from /haiku- src/develop/HaikuTree/trunk/headers/cpp/alloc.h:21, from /haiku- src/develop/HaikuTree/trunk/headers/cpp/std/bastring.h:39, from /haiku- src/develop/HaikuTree/trunk/headers/cpp/string:6, from /haiku- src/develop/HaikuTree/trunk/src/libs/stdc++/sinst.cc:36: /haiku- src/develop/HaikuTree/trunk/src/system/libroot/posix/glibc/include/bits/waitstatus.h:78: declaration of `unsigned int wait::{anonymous struct}::__w_retcode' /haiku- src/develop/HaikuTree/trunk/src/system/libroot/posix/glibc/include/bits/waitstatus.h:73: conflicts with previous declaration `unsigned int wait::{anonymous struct}::__w_retcode' /haiku- src/develop/HaikuTree/trunk/src/system/libroot/posix/glibc/include/bits/waitstatus.h:79: declaration of `unsigned int wait::{anonymous struct}::__w_coredump' /haiku- src/develop/HaikuTree/trunk/src/system/libroot/posix/glibc/include/bits/waitstatus.h:72: conflicts with previous declaration `unsigned int wait::{anonymous struct}::__w_coredump' /haiku- src/develop/HaikuTree/trunk/src/system/libroot/posix/glibc/include/bits/waitstatus.h:80: declaration of `unsigned int wait::{anonymous struct}::__w_termsig' /haiku- src/develop/HaikuTree/trunk/src/system/libroot/posix/glibc/include/bits/waitstatus.h:71: conflicts with previous declaration `unsigned int wait::{anonymous struct}::__w_termsig' /haiku- src/develop/HaikuTree/trunk/src/system/libroot/posix/glibc/include/bits/waitstatus.h:80: duplicate member `wait::{anonymous struct}::__w_termsig' /haiku- src/develop/HaikuTree/trunk/src/system/libroot/posix/glibc/include/bits/waitstatus.h:79: duplicate member `wait::{anonymous struct}::__w_coredump' /haiku- src/develop/HaikuTree/trunk/src/system/libroot/posix/glibc/include/bits/waitstatus.h:78: duplicate member `wait::{anonymous struct}::__w_retcode' /haiku- src/develop/HaikuTree/trunk/src/system/libroot/posix/glibc/include/bits/waitstatus.h:92: declaration of `unsigned int wait::{anonymous struct}::__w_stopsig' /haiku- src/develop/HaikuTree/trunk/src/system/libroot/posix/glibc/include/bits/waitstatus.h:87: conflicts with previous declaration `unsigned int wait::{anonymous struct}::__w_stopsig' /haiku- src/develop/HaikuTree/trunk/src/system/libroot/posix/glibc/include/bits/waitstatus.h:93: declaration of `unsigned int wait::{anonymous struct}::__w_stopval' /haiku- src/develop/HaikuTree/trunk/src/system/libroot/posix/glibc/include/bits/waitstatus.h:86: conflicts with previous declaration `unsigned int wait::{anonymous struct}::__w_stopval' /haiku- src/develop/HaikuTree/trunk/src/system/libroot/posix/glibc/include/bits/waitstatus.h:93: duplicate member `wait::{anonymous struct}::__w_stopval' /haiku- src/develop/HaikuTree/trunk/src/system/libroot/posix/glibc/include/bits/waitstatus.h:92: duplicate member `wait::{anonymous struct}::__w_stopsig' gcc -c "src/libs/stdc++/sinst.cc" -O2 -Wall -Wno-trigraphs -Wno-ctor-dtor- privacy -Woverloaded-virtual -Wpointer-arith -Wcast-align -Wsign-compare -pipe -nostdinc -Wno-multichar -D_ZETA_USING_DEPRECATED_API_=1 -D_ZETA_TS_FIND_DIR_=1 -nostdinc++ -fno-implicit-templates -Wno-sign- compare -fpic -D__HAIKU__ -DHAIKU_DISTRO_COMPATIBILITY_DEFAULT-D__INTEL__ -DARCH_x86 -D_BEOS_R5_COMPATIBLE_ -DHAIKU_TARGET_PLATFORM_HAIKU -DC -DEXTRACT -DINSERT -DGETLINE -Ibuild/user_config_headers -Ibuild/config_headers -Isrc/libs/stdc++ -Igenerated/objects/common/libs/stdc++ -Igenerated/objects/haiku_host/x86/common/libs/stdc++ -Igenerated/objects/haiku/x86/common/libs/stdc++ -I- -Isrc/libs/stdc++-Isrc/system/libroot/posix/glibc/libio -Isrc/system/libroot/posix/glibc/stdlib -Isrc/system/libroot/posix/glibc /stdio-common -Isrc/system/libroot/posix/glibc/include -Isrc/system/libroot/posix/glibc/include/arch/x86 -Iheaders/cpp -Isrc/system/libroot/posix/glibc -Iheaders/posix -Iheaders/os -Iheaders/os/kernel -Iheaders/os/storage -Iheaders/os/support -Iheaders/build/gcc-2.95.3 -Iheaders/build/gcc-2.95.3 -Iheaders -Iheaders/posix -Iheaders/gnu -Iheaders/glibc -Iheaders/os -Iheaders/os /add-ons -Iheaders/os/add-ons/file_system -Iheaders/os/add-ons/graphics -Iheaders/os/add-ons/input_server -Iheaders/os/add-ons/registrar -Iheaders/os/add-ons/screen_saver -Iheaders/os/add-ons/tracker -Iheaders/os/app -Iheaders/os/device -Iheaders/os/drivers -Iheaders/os/game -Iheaders/os/interface -Iheaders/os/kernel -Iheaders/os/media -Iheaders/os/mail -Iheaders/os/midi -Iheaders/os/midi2 -Iheaders/os/net -Iheaders/os/opengl -Iheaders/os/storage -Iheaders/os/support -Iheaders/os/translation -Iheaders/private/. -Iheaders/cpp -o "generated/objects/haiku/x86/release/libs/stdc++/cstrio.o" ; ...failed C++ generated/objects/haiku/x86/release/libs/stdc++/cstrio.o ... ...skipped libstdc++.r4.so for lack of cstrio.o... ...skipped libbe.so for lack of libstdc++.r4.so... ...skipped libnetwork.so for lack of libbe.so... ...skipped server_with_socket for lack of libnetwork.so... ...failed updating 1 target(s)... ...skipped 4 target(s)... ...updated 651 target(s)... /haiku-src/develop/HaikuTree/trunk> }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 30 15:52:23 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 30 Mar 2008 13:52:23 -0000 Subject: [Haiku-bugs] [Haiku] #1986: ifconfig --delete throws a page fault Message-ID: <040.4d2e35cffee791bdb2faa5e8de1eac3b@haiku-os.org> #1986: ifconfig --delete throws a page fault --------------------------------------+------------------------------------- Reporter: korli | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Platform: All | --------------------------------------+------------------------------------- Qemu, ifconfig --delete /dev/net/etherpci/0 {{{ domain_interface_went_down(1, /dev/net/etherpci/0) invalidate_routes(1, /dev/net/etherpci/0) etherpci: close dev=90b43780 ether: still waiting for read/write to finish etherpci: free dev=90b1ccc0 vm_soft_fault: va 0x0 not covered by area in address space vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x0, ip 0x805579a6, write 0, user 0, thread 0x87 PANIC: vm_page_fault: unhandled page fault in kernel space at 0x0, ip 0x805579a6 Welcome to Kernel Debugging Land... Running on CPU 0 kdebug> bt stack trace for thread 135 "ifconfig" kernel stack: 0x928ba000 to 0x928be000 user stack: 0x7efe7000 to 0x7ffe7000 frame caller :function + offset 928bd58c (+ 52) 80084eab :invoke_debugger_command + 0x00cf 928bd5c0 (+ 64) 80085c4c :_ParseCommand__16ExpressionParserRi + 0x01f8 928bd600 (+ 48) 8008563e :EvaluateCommand__16ExpressionParserPCcRi + 0x01de 928bd630 (+ 228) 80086d60 :evaluate_debug_command + 0x0088 928bd714 (+ 64) 800839ee :kernel_debugger_loop__Fv + 0x017a 928bd754 (+ 48) 80084699 :kernel_debugger + 0x010d 928bd784 (+ 192) 80084581 :panic + 0x0029 928bd844 (+ 64) 8005d51b :vm_page_fault + 0x00ab 928bd884 (+ 64) 80091595 :page_fault_exception + 0x00b1 928bd8c4 (+ 12) 80094c9d :int_bottom + 0x001d (nearest) iframe at 0x928bd8d0 (end = 0x928bd928) eax 0x0 ebx 0x80563a98 ecx 0x1 edx 0x246 esi 0x909ac800 edi 0x90b26400 ebp 0x928bd964 esp 0x928bd904 eip 0x805579a6 eflags 0x293 vector: 0xe, error code: 0x0 928bd8d0 (+ 148) 805579a6 :put_device_interface__FP20net_device_interface + 0x014a 928bd964 (+ 80) 80556a34 :domain_interface_control__FP18net_domain_privatelP5ifreq + 0x0168 928bd9b4 (+ 288) 80555774 :datalink_control__FP10net_domainlPvPUl + 0x0110 928bdad4 (+ 48) 80574a82 :ipv4_control__FP12net_protocoliiPvPUl + 0x0042 928bdb04 (+ 64) 8058e50e :udp_control__FP12net_protocoliiPvPUl + 0x0036 928bdb44 (+ 64) 8055a61f :socket_control__FP10net_socketlPvUl + 0x0037 928bdb84 (+ 432) 80376509 :net_stack_control__FPvUlT0Ul + 0x07cd 928bdd34 (+ 336) 800411bb :devfs_ioctl__FPvN20UlT0Ul + 0x023f 928bde84 (+ 64) 8004cc69 :common_ioctl__FP15file_descriptorUlPvUl + 0x0049 928bdec4 (+ 48) 8004548f :fd_ioctl__FbiUlPvUl + 0x005f 928bdef4 (+ 80) 8004614c :_user_ioctl + 0x0044 928bdf44 (+ 100) 80094e12 :pre_syscall_debug_done + 0x0002 (nearest) iframe at 0x928bdfa8 (end = 0x928be000) eax 0x71 ebx 0x2edec0 ecx 0x7ffe6e20 edx 0xffff0104 esi 0x3 edi 0x7ffef55f ebp 0x7ffe6e4c esp 0x928bdfdc eip 0xffff0104 eflags 0x216 vector: 0x63, error code: 0x0 928bdfa8 (+ 0) ffff0104 7ffe6e4c (+ 240) 00201ce2 <_APP_>:delete_interface__FiPCc + 0x0046 7ffe6f3c (+ 64) 00202b27 <_APP_>:main + 0x0123 7ffe6f7c (+ 48) 00200df7 <_APP_>:_start + 0x005b 7ffe6fac (+ 48) 0010078e 1390:runtime_loader_seg0ro at 0x00100000 + 0x78e 7ffe6fdc (+ 0) 7ffe6fec 1389:ifconfig_main_stack at 0x7efe7000 + 0xffffec }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 30 15:58:03 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 30 Mar 2008 13:58:03 -0000 Subject: [Haiku-bugs] [Haiku] #1984: bulding haiku on haiku-host fails at ... In-Reply-To: <043.e1d8aee9f24ccbc1be759ecd3448e84c@haiku-os.org> References: <043.e1d8aee9f24ccbc1be759ecd3448e84c@haiku-os.org> Message-ID: <052.49274f3e6e27002718f8802da9b079f8@haiku-os.org> #1984: bulding haiku on haiku-host fails at ... ------------------------+--------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: invalid | Platform: All ------------------------+--------------------------------------------------- Changes (by kaoutsis): * status: new => closed * resolution: => invalid Comment: there is the #1985, normally this one shouldn't appear since i got: {{{ Proxy Error The proxy server received an invalid response from an upstream server. The proxy server could not handle the request GET /. Reason: Error reading from remote server }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 30 16:02:21 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 30 Mar 2008 14:02:21 -0000 Subject: [Haiku-bugs] [Haiku] #1985: bulding haiku on haiku-host fails at ... In-Reply-To: <043.99b02a402e3894907d9f209a64cb1bae@haiku-os.org> References: <043.99b02a402e3894907d9f209a64cb1bae@haiku-os.org> Message-ID: <052.3c3fb6df8cdf1a5578a3c7b458ae47fc@haiku-os.org> #1985: bulding haiku on haiku-host fails at ... ---------------------------+------------------------------------------------ Reporter: kaoutsis | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by kaoutsis): revision is r24676 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 30 16:20:39 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 30 Mar 2008 14:20:39 -0000 Subject: [Haiku-bugs] [Haiku] #1983: npipefs: could not resolve symbol 'new_lock' In-Reply-To: <040.b19df3da374a73c908d2a011d2e4e2fe@haiku-os.org> References: <040.b19df3da374a73c908d2a011d2e4e2fe@haiku-os.org> Message-ID: <049.bfb10f9133cb3839ee04c759954f4c7b@haiku-os.org> #1983: npipefs: could not resolve symbol 'new_lock' ---------------------------+------------------------------------------------ Reporter: thorn | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: File Systems | Version: R1 development Resolution: invalid | Platform: x86 ---------------------------+------------------------------------------------ Comment (by thorn): i see, it's come from 'official' subversion package. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 30 16:27:42 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 30 Mar 2008 14:27:42 -0000 Subject: [Haiku-bugs] [Haiku] #1959: nVidia Corporation NV11 [GeForce2 Go]: drawing problems after new splash screen In-Reply-To: <040.17c8090d9b429398540eaed4e454250d@haiku-os.org> References: <040.17c8090d9b429398540eaed4e454250d@haiku-os.org> Message-ID: <049.619894286112b027a37431ad46287a49@haiku-os.org> #1959: nVidia Corporation NV11 [GeForce2 Go]: drawing problems after new splash screen --------------------------------------+------------------------------------- Reporter: nielx | Owner: korli Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: | Platform: All --------------------------------------+------------------------------------- Comment (by korli): Could you check again with r24679 ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 30 17:14:56 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 30 Mar 2008 15:14:56 -0000 Subject: [Haiku-bugs] [Haiku] #1945: [marvell yukon] 11ab:4320 not detected In-Reply-To: <040.6d7189e51f797abf4deca9c4e5ded43f@haiku-os.org> References: <040.6d7189e51f797abf4deca9c4e5ded43f@haiku-os.org> Message-ID: <049.3b996100fa833d46d68986a33d47bd47@haiku-os.org> #1945: [marvell yukon] 11ab:4320 not detected ------------------------------+--------------------------------------------- Reporter: diver | Owner: euan Type: enhancement | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Network | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by euan): agreed, sounds much better. :) Axel, can you commit it for me? I've no keys prepared, and a tree full of broken radeon junk. Uploaded a new diff, I just did find and replace but should be ok. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 30 17:41:25 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 30 Mar 2008 15:41:25 -0000 Subject: [Haiku-bugs] [Haiku] #1978: 3rdparty : add support for Jamfile.haiku for independent 3rdparty source code In-Reply-To: <041.230f65b203a021e4107c3c84c4e40221@haiku-os.org> References: <041.230f65b203a021e4107c3c84c4e40221@haiku-os.org> Message-ID: <050.149cfecd7e76cf25501a09222653beb6@haiku-os.org> #1978: 3rdparty : add support for Jamfile.haiku for independent 3rdparty source code ---------------------------+------------------------------------------------ Reporter: mmadia | Owner: bonefish Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: fixed | Platform: All ---------------------------+------------------------------------------------ Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: It was already possible to include arbitrarily named files in the UserBuildConfig via the built-in "include" rule. In r24680 I changed DeferredSubInclude, so that it can be used for that purpose. I also rearranged a few things, so that the inclusion of 3rdparty targets in the image should work without problems. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 30 17:44:27 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 30 Mar 2008 15:44:27 -0000 Subject: [Haiku-bugs] [Haiku] #1983: npipefs: could not resolve symbol 'new_lock' In-Reply-To: <040.b19df3da374a73c908d2a011d2e4e2fe@haiku-os.org> References: <040.b19df3da374a73c908d2a011d2e4e2fe@haiku-os.org> Message-ID: <049.072edd268bb11d8dbe255d407b058952@haiku-os.org> #1983: npipefs: could not resolve symbol 'new_lock' ---------------------------+------------------------------------------------ Reporter: thorn | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: File Systems | Version: R1 development Resolution: invalid | Platform: x86 ---------------------------+------------------------------------------------ Comment (by bonefish): Replying to [comment:2 thorn]: > i see, it's come from 'official' subversion package. Yep, but that's the official BeOS package. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 30 18:23:03 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 30 Mar 2008 16:23:03 -0000 Subject: [Haiku-bugs] [Haiku] #1967: kdl using rtl8139 if_vr: packet not processed In-Reply-To: <042.fe3fb91518812a33d79bcd0beefe2745@haiku-os.org> References: <042.fe3fb91518812a33d79bcd0beefe2745@haiku-os.org> Message-ID: <051.c6283cb5e887f71866dbad983d451fe4@haiku-os.org> #1967: kdl using rtl8139 if_vr: packet not processed ---------------------------------+------------------------------------------ Reporter: bbjimmy | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Resolution: | Platform: x86 ---------------------------------+------------------------------------------ Comment (by bbjimmy): I got the KDL without even using the network. On a hunch, I disabled the unused built-in NIC, via rhine, and the if_vr KDL seems to have gone away. The issue may be with the via rhine driver or attempting to initialize to use DHCP on a nic without an interface cable plugged in. I am posting using HAIKU r24672. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 30 18:46:26 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 30 Mar 2008 16:46:26 -0000 Subject: [Haiku-bugs] [Haiku] #1987: BeTask Manager - four problems Message-ID: <041.42ce7f7fc451eff37425955e6469652b@haiku-os.org> #1987: BeTask Manager - four problems -----------------------+---------------------------------------------------- Reporter: kvdman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- I'm trying out BeTask Manager: [http://www.haikuware.com/view-details/utilities/system/be-taskmanager] It works, but there's four problems: 1) under the teams tab, you can't select individual teams to kill 2) xkill will only allow you to select tracker to kill with the crosshairs eventhough you select another window. 3) when you have task manager live in the deskbar and right-click it to 'show task manager' deskbar crashes. 4) quitting the program won't actually quit, and spikes your cpu. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 30 18:49:29 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 30 Mar 2008 16:49:29 -0000 Subject: [Haiku-bugs] [Haiku] #1987: BeTask Manager - four problems In-Reply-To: <041.42ce7f7fc451eff37425955e6469652b@haiku-os.org> References: <041.42ce7f7fc451eff37425955e6469652b@haiku-os.org> Message-ID: <050.66a2da70e912266314b5c78c974a40c2@haiku-os.org> #1987: BeTask Manager - four problems ------------------------+--------------------------------------------------- Reporter: kvdman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by kvdman): One more thing, under the teams tab, you can't order items (i.e by most memory usage) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 30 19:44:38 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 30 Mar 2008 17:44:38 -0000 Subject: [Haiku-bugs] [Haiku] #1576: Some headers should be rewritten In-Reply-To: <040.e83e7424b795679f4337b358ef6c301d@haiku-os.org> References: <040.e83e7424b795679f4337b358ef6c301d@haiku-os.org> Message-ID: <049.6554f555abeef61beaf769fbe8b3eb94@haiku-os.org> #1576: Some headers should be rewritten ------------------------+--------------------------------------------------- Reporter: korli | Owner: Type: bug | Status: new Priority: high | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by julun): PrintJob.h done in r24684 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 30 20:04:26 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 30 Mar 2008 18:04:26 -0000 Subject: [Haiku-bugs] [Haiku] #1981: mail_daemon can not send mails In-Reply-To: <043.4176d1431dea833759361f5bf70d5819@haiku-os.org> References: <043.4176d1431dea833759361f5bf70d5819@haiku-os.org> Message-ID: <052.f9cc004590f88e5d11bc730336e71406@haiku-os.org> #1981: mail_daemon can not send mails ------------------------+--------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by kaoutsis): Replying to [comment:1 koki]: > I can confirm this. In my case, when trying to send an email, I get a window titled "Mail Daemon Status Log" that shows the following message: > > email at domain.com: Error while getting a message. Name not found [Sat Mar 29 19:09:28 2008] > yes, i forgot that part > This is a wild guess, but could this be related to bug #1751 ? may be -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 30 20:11:02 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 30 Mar 2008 18:11:02 -0000 Subject: [Haiku-bugs] [Haiku] #1945: [marvell yukon] 11ab:4320 not detected In-Reply-To: <040.6d7189e51f797abf4deca9c4e5ded43f@haiku-os.org> References: <040.6d7189e51f797abf4deca9c4e5ded43f@haiku-os.org> Message-ID: <049.b23b8f6f5b998bd54ad1739f71c53aa4@haiku-os.org> #1945: [marvell yukon] 11ab:4320 not detected ------------------------------+--------------------------------------------- Reporter: diver | Owner: euan Type: enhancement | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Network | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by axeld): I can do so tomorrow. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 30 20:21:35 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 30 Mar 2008 18:21:35 -0000 Subject: [Haiku-bugs] [Haiku] #1988: PANIC: ASSERT FAILED (src/system/kernel/fs/vfs.cpp:747): oldRefCount > 0 Message-ID: <040.da57811c77e0a1a5bc9606fd7edabfb4@haiku-os.org> #1988: PANIC: ASSERT FAILED (src/system/kernel/fs/vfs.cpp:747): oldRefCount > 0 ---------------------------+------------------------------------------------ Reporter: thorn | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Platform: x86 | ---------------------------+------------------------------------------------ Haiku r24635 {{{ kdebug> vnode 0x91672100 VNODE: 0x91672100 device: 5 id: 2146 ref_count: -1 private_node: 0x912b8480 mount: 0x90b7a8c0 covered_by: 0x00000000 cache: 0x00000000 flags: -b- advisory_lock: 0x00000000 kdebug> vnode_usage Unused vnodes: 22271 (max unused 8192) 22482 vnodes total (211 in use). }}} and backtrace {{{ wait interval 994979, scan pages 553, free 4329, target 23 wait interval 996070, scan pages 544, free 4334, target 18 wait interval 1000000, scan pages 512, free 4352, target 0 Last message repeated 2 times. vnode 5:2146 is not becoming unbusy! vnode 0x91672100 PANIC: ASSERT FAILED (src/system/kernel/fs/vfs.cpp:747): oldRefCount > 0 Welcome to Kernel Debugging Land... Running on CPU 0 kdebug> sc stack trace for thread 171 "svn" kernel stack: 0x925da000 to 0x925de000 user stack: 0x7efe7000 to 0x7ffe7000 frame caller :function + offset 925dd85c (+ 52) 800843f3 :invoke_debugger_command + 0x00cf 925dd890 (+ 64) 80085194 :_ParseCommand__16ExpressionParserRi + 0x01f8 925dd8d0 (+ 48) 80084b86 :EvaluateCommand__16ExpressionParserPCcRi + 0x01de 925dd900 (+ 228) 800862a8 :evaluate_debug_command + 0x0088 925dd9e4 (+ 64) 80082f36 :kernel_debugger_loop__Fv + 0x017a 925dda24 (+ 48) 80083be1 :kernel_debugger + 0x010d 925dda54 (+ 192) 80083ac9 :panic + 0x0029 925ddb14 (+ 64) 80046a8e :dec_vnode_ref_count__FP5vnodeb + 0x0056 925ddb54 (+ 48) 800499f6 :put_vnode + 0x0052 925ddb84 (+ 48) 80323c09 :Put__5Vnode + 0x0031 925ddbb4 (+ 80) 8032b0a9 :SetTo__5IndexPCc + 0x00bd 925ddc04 (+ 64) 8032b4b2 :Update__5IndexR11TransactionPCclPCUcUsT4UsP5Inode + 0x00ea 925ddc44 (+ 80) 8032b75f :UpdateName__5IndexR11TransactionPCcT2P5Inode + 0x00bb 925ddc94 (+ 64) 8032b662 :InsertName__5IndexR11TransactionPCcP5Inode + 0x002e 925ddcd4 (+ 144) 8033273d :Create__5InodeR11TransactionP5InodePCcliUlPbPxPP5Inode + 0x07d1 925ddd64 (+ 96) 8033cccb :bfs_create_dir__FPvT0PCciPx + 0x0107 925dddc4 (+ 320) 8004bcc6 :dir_create__FiPcib + 0x0082 925ddf04 (+ 64) 800510d4 :_user_create_dir + 0x0094 925ddf44 (+ 100) 80094302 :pre_syscall_debug_done + 0x0002 (nearest) iframe at 0x925ddfa8 (end = 0x925de000) eax 0x55 ebx 0x45959c ecx 0x7ffe65f4 edx 0xffff0104 esi 0x19244228 edi 0x19244228 ebp 0x7ffe6620 esp 0x925ddfdc eip 0xffff0104 eflags 0x206 vector: 0x63, error code: 0x0 925ddfa8 (+ 0) ffff0104 7ffe6620 (+ 48) 0032691f :unknown + 0xf91f 7ffe6650 (+ 144) 002c8516 :unknown + 0xd516 7ffe66e0 (+ 64) 002c861b :unknown + 0xd61b 7ffe6720 (+ 64) 0023a944 :unknown + 0x5944 7ffe6760 (+ 64) 0023ba32 :unknown + 0x6a32 7ffe67a0 (+ 64) 0023bb3b :unknown + 0x6b3b 7ffe67e0 (+ 64) 0023bc46 :unknown + 0x6c46 7ffe6820 (+ 64) 0024d480 :unknown + 0x18480 7ffe6860 (+ 176) 0024dd6d :unknown + 0x18d6d 7ffe6910 (+ 64) 002b4bc5 :unknown + 0x1bc5 7ffe6950 (+ 96) 00299f78 :unknown + 0x7f78 7ffe69b0 (+ 112) 0029ab5a :unknown + 0x8b5a 7ffe6a20 (+ 80) 00299126 :unknown + 0x7126 7ffe6a70 (+ 64) 00295466 :unknown + 0x3466 7ffe6ab0 (+ 176) 0023a1dc :unknown + 0x51dc 7ffe6b60 (+ 160) 00230426 :unknown + 0x18426 7ffe6c00 (+ 112) 0021f421 :unknown + 0x7421 7ffe6c70 (+ 64) 0021f544 :unknown + 0x7544 7ffe6cb0 (+ 80) 0020574e :unknown + 0x574e 7ffe6d00 (+ 640) 002091fc :unknown + 0x91fc 7ffe6f80 (+ 44) 00204c45 :unknown + 0x4c45 7ffe6fac (+ 48) 0010078e 1616:runtime_loader_seg0ro at 0x00100000 + 0x78e 7ffe6fdc (+ 0) 7ffe6fec 1615:svn_main_stack at 0x7efe7000 + 0xffffec kdebug> }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 30 20:27:53 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 30 Mar 2008 18:27:53 -0000 Subject: [Haiku-bugs] [Haiku] #1988: PANIC: ASSERT FAILED (src/system/kernel/fs/vfs.cpp:747): oldRefCount > 0 In-Reply-To: <040.da57811c77e0a1a5bc9606fd7edabfb4@haiku-os.org> References: <040.da57811c77e0a1a5bc9606fd7edabfb4@haiku-os.org> Message-ID: <049.c0e2ced5acd40d5abc3e78e2e13be822@haiku-os.org> #1988: PANIC: ASSERT FAILED (src/system/kernel/fs/vfs.cpp:747): oldRefCount > 0 ----------------------------+----------------------------------------------- Reporter: thorn | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by thorn): I save vm state, so somebody can ask me about additional information. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 30 21:14:36 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 30 Mar 2008 19:14:36 -0000 Subject: [Haiku-bugs] [Haiku] #1390: [app_server] Invalid opcode exception In-Reply-To: <040.c22ea4fb382184f71fd2a99eb3f6b578@haiku-os.org> References: <040.c22ea4fb382184f71fd2a99eb3f6b578@haiku-os.org> Message-ID: <049.162e46716564d09e4807704a6bdb4b98@haiku-os.org> #1390: [app_server] Invalid opcode exception ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: fixed | Platform: All ---------------------------------+------------------------------------------ Changes (by stippi): * status: new => closed * resolution: => fixed Comment: Ok, please reopen if it does happen again. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 30 21:14:43 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 30 Mar 2008 19:14:43 -0000 Subject: [Haiku-bugs] [Haiku] #1989: Complete termios.h definitions Message-ID: <041.a04e09d0c9df193ee19d31110d8ab39f@haiku-os.org> #1989: Complete termios.h definitions -----------------------+---------------------------------------------------- Reporter: duaneb | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: x86 | -----------------------+---------------------------------------------------- I was attempting to compile jasspa's microemacs (http://www.jasspa.com/), dependent on the termcap stuff, and it revealed at least these missing definitions:ECHOCTL, ECHOKE, CQUIT, CEOF, VLNEXT, CLNEXT, CSUSP, CSTART, and CSTOP. I'm sure there are more missing; I just don't know how many more. Cheers! -duane. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 30 21:15:15 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 30 Mar 2008 19:15:15 -0000 Subject: [Haiku-bugs] [Haiku] #1447: [ProcessController] sometimes takes to long to open menu In-Reply-To: <040.ee18a62fe673319ecbdf0cdf94346074@haiku-os.org> References: <040.ee18a62fe673319ecbdf0cdf94346074@haiku-os.org> Message-ID: <049.5a4f8afcf4b0cae279350fe81cd22d46@haiku-os.org> #1447: [ProcessController] sometimes takes to long to open menu ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: fixed | Platform: All ---------------------------------+------------------------------------------ Changes (by stippi): * status: new => closed * resolution: => fixed Comment: Ok thanks for confirming! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 30 21:16:02 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 30 Mar 2008 19:16:02 -0000 Subject: [Haiku-bugs] [Haiku] #695: [ButterFly] crash on jpeg translator selection In-Reply-To: <040.8eaf256045813d5f6609f6f35c274052@haiku-os.org> References: <040.8eaf256045813d5f6609f6f35c274052@haiku-os.org> Message-ID: <049.81170814c11d732869ffee1bc7603dad@haiku-os.org> #695: [ButterFly] crash on jpeg translator selection ---------------------------+------------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications | Version: Resolution: fixed | Platform: All ---------------------------+------------------------------------------------ Changes (by stippi): * status: new => closed * resolution: => fixed Old description: > ButterFly will crash if you open any image, select Convert menu and > select JPEG > or JPEG2000 translators. > Note that if you Press Debug button upon crash and then close Terminal > with > gdb, ButterFly's window will not close. > bt command says "No stack." > Tested on real hw with r17923. New description: ButterFly will crash if you open any image, select Convert menu and select JPEG or JPEG2000 translators. Note that if you Press Debug button upon crash and then close Terminal with gdb, ButterFly's window will not close. bt command says "No stack." Tested on real hw with r17923. Comment: Ok thanks for confirming. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 30 21:59:53 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 30 Mar 2008 19:59:53 -0000 Subject: [Haiku-bugs] [Haiku] #1962: Some resolutions in VESA no longer work In-Reply-To: <044.144153a4a47b9e6b368c0cb2527e4b97@haiku-os.org> References: <044.144153a4a47b9e6b368c0cb2527e4b97@haiku-os.org> Message-ID: <053.ec6ca1906613896d344d0091a9e18b09@haiku-os.org> #1962: Some resolutions in VESA no longer work ------------------------+--------------------------------------------------- Reporter: j_freeman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by j_freeman): Tested in r24688. 1440x900 and 1920x1200 are no longer even listed as available resolutions. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 30 22:19:04 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 30 Mar 2008 20:19:04 -0000 Subject: [Haiku-bugs] [Haiku] #1990: subversion is not part of the build optional packages Message-ID: <043.8ef46ae040081ccdf00d670ce2d35349@haiku-os.org> #1990: subversion is not part of the build optional packages --------------------------+------------------------------------------------- Reporter: kaoutsis | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Platform: All | --------------------------+------------------------------------------------- Although there is a http://www.haiku-os.org/files/Subversion-1.1.3.pkg that is working perfectly, if i create a haiku installation from linux, when i start working with haiku host build, i have to download every time this package. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 30 22:32:00 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 30 Mar 2008 20:32:00 -0000 Subject: [Haiku-bugs] [Haiku] #1990: subversion is not part of the build optional packages In-Reply-To: <043.8ef46ae040081ccdf00d670ce2d35349@haiku-os.org> References: <043.8ef46ae040081ccdf00d670ce2d35349@haiku-os.org> Message-ID: <052.c4c876790294a2db620861a538c5b309@haiku-os.org> #1990: subversion is not part of the build optional packages ---------------------------+------------------------------------------------ Reporter: kaoutsis | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by bonefish): I'm already working on the tool chain. I just haven't reached subversion yet. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 30 22:44:15 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 30 Mar 2008 20:44:15 -0000 Subject: [Haiku-bugs] [Haiku] #1990: subversion is not part of the build optional packages In-Reply-To: <043.8ef46ae040081ccdf00d670ce2d35349@haiku-os.org> References: <043.8ef46ae040081ccdf00d670ce2d35349@haiku-os.org> Message-ID: <052.9e51b0fb4be0575c81a70c3666ba6c86@haiku-os.org> #1990: subversion is not part of the build optional packages ---------------------------+------------------------------------------------ Reporter: kaoutsis | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by kaoutsis): Replying to [comment:1 bonefish]: > I'm already working on the tool chain. I just haven't reached subversion yet. ok -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 30 22:45:38 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 30 Mar 2008 20:45:38 -0000 Subject: [Haiku-bugs] [Haiku] #1962: Some resolutions in VESA no longer work In-Reply-To: <044.144153a4a47b9e6b368c0cb2527e4b97@haiku-os.org> References: <044.144153a4a47b9e6b368c0cb2527e4b97@haiku-os.org> Message-ID: <053.72c49477eff5887666383e90a4c27d38@haiku-os.org> #1962: Some resolutions in VESA no longer work ------------------------+--------------------------------------------------- Reporter: j_freeman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by stippi): That is because your VESA BIOS does not list them as available modes. The VESA driver can only support the modes listed in your graphics board's BIOS. Ie, it was incorrect before, that the modes got listed, and the code is correct now to not list modes which can not be supported. Please note that your graphics board would probably support these modes if a native driver for your board would be available. Only, the VESA driver can not configure your board for display modes, only through it's VESA BIOS. So everything seems to be working fine now as far as what is possible with VESA. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 30 23:01:45 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 30 Mar 2008 21:01:45 -0000 Subject: [Haiku-bugs] [Haiku] #1962: Some resolutions in VESA no longer work In-Reply-To: <044.144153a4a47b9e6b368c0cb2527e4b97@haiku-os.org> References: <044.144153a4a47b9e6b368c0cb2527e4b97@haiku-os.org> Message-ID: <053.b100e1c31c94caa034b924ae6d3e754c@haiku-os.org> #1962: Some resolutions in VESA no longer work ------------------------+--------------------------------------------------- Reporter: j_freeman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by j_freeman): Ah, I see. In that case, I suppose the ticket can be closed. Off topic: Is there any way to force a certain mode, one that isn't listed? I ask because it was nice having native fullscreen at 1440x900. ;) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 30 23:03:11 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 30 Mar 2008 21:03:11 -0000 Subject: [Haiku-bugs] [Haiku] #1755: APR 0.9.x configure hangs In-Reply-To: <043.4f95de578a9238745b55c09b213f0130@haiku-os.org> References: <043.4f95de578a9238745b55c09b213f0130@haiku-os.org> Message-ID: <052.a84a30abaf5cba753863acf52e761717@haiku-os.org> #1755: APR 0.9.x configure hangs ------------------------+--------------------------------------------------- Reporter: andreasf | Owner: bonefish Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: x86 ------------------------+--------------------------------------------------- Changes (by bonefish): * owner: axeld => bonefish * status: new => assigned Comment: I can reproduce a problem with blocking pipes with {{{unzip -l large.zip | less}}} + "G" (not always, but often enough). Looking into it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 30 23:10:46 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 30 Mar 2008 21:10:46 -0000 Subject: [Haiku-bugs] [Haiku] #1950: Garbled screen contents with true colour mode on nvidia gf2mx In-Reply-To: <042.f15ad8e18c31676a011caebc5344d3a8@haiku-os.org> References: <042.f15ad8e18c31676a011caebc5344d3a8@haiku-os.org> Message-ID: <051.d6c973206296fa8c5cff163539456f3f@haiku-os.org> #1950: Garbled screen contents with true colour mode on nvidia gf2mx ------------------------+--------------------------------------------------- Reporter: jopadan | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: x86 ------------------------+--------------------------------------------------- Comment (by jonas.kirilla): Screen still garbled for me with r24682. No visible change. I tried setting force_pci true in nvidia.settings in an earlier revision (prior to r24679) with no improvement. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 30 23:29:18 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 30 Mar 2008 21:29:18 -0000 Subject: [Haiku-bugs] [Haiku] #1932: QueryWatcher crashes on startup when running against a link to a query In-Reply-To: <039.fb323ed34e5a739978378cbce37254df@haiku-os.org> References: <039.fb323ed34e5a739978378cbce37254df@haiku-os.org> Message-ID: <048.32e12a19802be5b4acc7a187b2c41f01@haiku-os.org> #1932: QueryWatcher crashes on startup when running against a link to a query ----------------------------+----------------------------------------------- Reporter: koki | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Platform: All ----------------------------+----------------------------------------------- Comment (by koki): A bit late, but was able to verify that this bug is fxed now. Thanks again Axel! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Mar 30 23:46:25 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 30 Mar 2008 21:46:25 -0000 Subject: [Haiku-bugs] [Haiku] #1959: nVidia Corporation NV11 [GeForce2 Go]: drawing problems after new splash screen In-Reply-To: <040.17c8090d9b429398540eaed4e454250d@haiku-os.org> References: <040.17c8090d9b429398540eaed4e454250d@haiku-os.org> Message-ID: <049.8d8269a7d184f58b874ea520c5a6a6a8@haiku-os.org> #1959: nVidia Corporation NV11 [GeForce2 Go]: drawing problems after new splash screen --------------------------------------+------------------------------------- Reporter: nielx | Owner: korli Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: | Platform: All --------------------------------------+------------------------------------- Comment (by qyellow): geforce 4 mx (nforce2 integrated graphics) I am having the same problem as nielx. Updating to revision 24695 does not resolve the drawing issues on my setup. cat /proc/mtrr reg00: base=0x00000000 ( 0MB), size= 512MB: write-back, count=1 reg01: base=0x20000000 ( 512MB), size= 128MB: write-back, count=1 reg02: base=0x28000000 ( 640MB), size= 64MB: write-back, count=1 reg03: base=0x2c000000 ( 704MB), size= 32MB: write-back, count=1 and messages Mar 30 09:42:09 cgreen kernel: BIOS-provided physical RAM map: Mar 30 09:42:09 cgreen kernel: BIOS-e820: 0000000000000000 - 000000000009fc00 (usable) Mar 30 09:42:09 cgreen kernel: BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved) Mar 30 09:42:09 cgreen kernel: BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved) Mar 30 09:42:09 cgreen kernel: BIOS-e820: 0000000000100000 - 000000002dfd0000 (usable) Mar 30 09:42:09 cgreen kernel: BIOS-e820: 000000002dfd0000 - 000000002dfdf000 (ACPI data) Mar 30 09:42:09 cgreen kernel: BIOS-e820: 000000002dfdf000 - 000000002e000000 (ACPI NVS) Mar 30 09:42:09 cgreen kernel: BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved) Mar 30 09:42:09 cgreen kernel: BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved) Mar 30 09:42:09 cgreen kernel: BIOS-e820: 00000000ff7c0000 - 0000000100000000 (reserved) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 31 00:32:35 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 30 Mar 2008 22:32:35 -0000 Subject: [Haiku-bugs] [Haiku] #1962: Some resolutions in VESA no longer work In-Reply-To: <044.144153a4a47b9e6b368c0cb2527e4b97@haiku-os.org> References: <044.144153a4a47b9e6b368c0cb2527e4b97@haiku-os.org> Message-ID: <053.fa6ee3db5e674306a5cb6a2769797b35@haiku-os.org> #1962: Some resolutions in VESA no longer work ------------------------+--------------------------------------------------- Reporter: j_freeman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by stippi): Wait... you have been using the VESA driver at 1440x900 before, and now this does not work anymore? Because that would be a bug then. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 31 00:35:58 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 30 Mar 2008 22:35:58 -0000 Subject: [Haiku-bugs] [Haiku] #1755: APR 0.9.x configure hangs In-Reply-To: <043.4f95de578a9238745b55c09b213f0130@haiku-os.org> References: <043.4f95de578a9238745b55c09b213f0130@haiku-os.org> Message-ID: <052.7a5c7af4681ca277c1d30c3dfc0a01a0@haiku-os.org> #1755: APR 0.9.x configure hangs ------------------------+--------------------------------------------------- Reporter: andreasf | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Platform: x86 ------------------------+--------------------------------------------------- Changes (by bonefish): * status: assigned => closed * resolution: => fixed Comment: Fixed in r24701. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 31 00:49:13 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 30 Mar 2008 22:49:13 -0000 Subject: [Haiku-bugs] [Haiku] #1991: jam clean fails on haiku-host Message-ID: <043.313763266e2696b6a7ec3ac769c36996@haiku-os.org> #1991: jam clean fails on haiku-host --------------------------+------------------------------------------------- Reporter: kaoutsis | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Platform: All | --------------------------+------------------------------------------------- {{{ /haiku-src/develop/HaikuTree/trunk>./configure --include-gpl-addons --use- gcc-pipe /haiku-src/develop/HaikuTree/trunk>jam clean ...found 1 target(s)... ...updating 1 target(s)... Clean clean /bin/sh: -c: line 2: unexpected EOF while looking for matching `"' /bin/sh: -c: line 3: syntax error: unexpected end of file rm -f "generated/objects/haiku/x86/release/add- ons/accelerants/common/libaccelerantscommon.a" "generated/objects/haiku/x86/release/add- ons/accelerants/common/create_display_modes.o" "generated/objects/haiku/x86/release/add-ons/accelerants/common/ddc.o" "generated/objects/haiku/x86/release/add- ons/accelerants/common/decode_edid.o" "generated/objects/haiku/x86/release /add-ons/accelerants/common/dump_edid.o" "generated/objects/haiku/x86/release/add-ons/accelerants/common/i2c.o" "generated/objects/haiku/x86/release/add- ons/accelerants/intel_extreme/intel_extreme.accelerant" [...] "generated/objects/haiku/x86/release/add- ons/kernel/drivers/graphics/vesa/vga.o" ...failed Clean clean ... ...failed updating 1 target(s)... /haiku-src/develop/HaikuTree/trunk> -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 31 00:58:57 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 30 Mar 2008 22:58:57 -0000 Subject: [Haiku-bugs] [Haiku] #1991: jam clean fails on haiku-host In-Reply-To: <043.313763266e2696b6a7ec3ac769c36996@haiku-os.org> References: <043.313763266e2696b6a7ec3ac769c36996@haiku-os.org> Message-ID: <052.7f432a041713edcfef05350a87a3fc1b@haiku-os.org> #1991: jam clean fails on haiku-host ---------------------------+------------------------------------------------ Reporter: kaoutsis | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by kaoutsis): /haiku-src/develop/HaikuTree/trunk>uname -a Haiku unknown 1 r24691 Mar 30 2008 21:17:59 BePC BeOS -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 31 01:11:05 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 30 Mar 2008 23:11:05 -0000 Subject: [Haiku-bugs] [Haiku] #1992: vlc invokes gdb when a asx file is dragged upon it Message-ID: <043.fd5579d9086214cca57bcbd895618aad@haiku-os.org> #1992: vlc invokes gdb when a asx file is dragged upon it -----------------------+---------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- r24691 attached: * syslog.txt * the asx file nasa-tv.asx * the gdb console vlc-gdb.txt some months ago is used to working -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 31 01:51:47 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 30 Mar 2008 23:51:47 -0000 Subject: [Haiku-bugs] [Haiku] #1962: Some resolutions in VESA no longer work In-Reply-To: <044.144153a4a47b9e6b368c0cb2527e4b97@haiku-os.org> References: <044.144153a4a47b9e6b368c0cb2527e4b97@haiku-os.org> Message-ID: <053.1ff8c22438aa8bd0327a0ea72f3e302a@haiku-os.org> #1962: Some resolutions in VESA no longer work ------------------------+--------------------------------------------------- Reporter: j_freeman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by j_freeman): > Wait... you have been using the VESA driver at 1440x900 before, and now this does not work anymore? Correct. Up until recently, 1440x900 was listed and worked fine. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 31 07:20:16 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 31 Mar 2008 05:20:16 -0000 Subject: [Haiku-bugs] [Haiku] #1989: Complete termios.h definitions In-Reply-To: <041.a04e09d0c9df193ee19d31110d8ab39f@haiku-os.org> References: <041.a04e09d0c9df193ee19d31110d8ab39f@haiku-os.org> Message-ID: <050.21f856b8f4aacb521cbbb2d994a96a28@haiku-os.org> #1989: Complete termios.h definitions ------------------------+--------------------------------------------------- Reporter: duaneb | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: x86 ------------------------+--------------------------------------------------- Comment (by axeld): Strictly speaking, those aren't part of the POSIX standard, albeit their are reserved constants ("..., therefore strictly conforming applications shall not use them"), see http://www.opengroup.org/onlinepubs/009695399/basedefs/termios.h.html#tag_13_74 Not sure if we should add them, since we would also need to actually support them, right? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 31 07:23:22 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 31 Mar 2008 05:23:22 -0000 Subject: [Haiku-bugs] [Haiku] #1962: Some resolutions in VESA no longer work In-Reply-To: <044.144153a4a47b9e6b368c0cb2527e4b97@haiku-os.org> References: <044.144153a4a47b9e6b368c0cb2527e4b97@haiku-os.org> Message-ID: <053.3ba2decda9b22d8af0f6575650e3aebd@haiku-os.org> #1962: Some resolutions in VESA no longer work ------------------------+--------------------------------------------------- Reporter: j_freeman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by axeld): Replying to [comment:7 j_freeman]: > Correct. Up until recently, 1440x900 was listed and worked fine. Are you sure you haven't changed your hardware that does it? Some adapters publish resolutions like that, some (most) don't. If you are sure your hardware hasn't changed (also no BIOS upgrade in that time), it would be very nice to know what change may have triggered that. Can you try out older revisions? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 31 07:47:56 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 31 Mar 2008 05:47:56 -0000 Subject: [Haiku-bugs] [Haiku] #1993: Implement using HPET timers and other mechanisms than TSC for time keeping Message-ID: <040.ae3712170bf3f602ef64c6312bd6de79@haiku-os.org> #1993: Implement using HPET timers and other mechanisms than TSC for time keeping -------------------------+-------------------------------------------------- Reporter: axeld | Owner: axeld Type: enhancement | Status: new Priority: high | Milestone: R1 Component: - General | Version: R1 development Platform: All | -------------------------+-------------------------------------------------- On CPUs that are able to change their frequency, the TSC increment is not invariant. Therefore, we cannot use it to compute time on these machines. Unfortunately, most recent CPUs are affected due to power saving features. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 31 07:53:19 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 31 Mar 2008 05:53:19 -0000 Subject: [Haiku-bugs] [Haiku] #1993: Implement using HPET timers and other mechanisms than TSC for time keeping In-Reply-To: <040.ae3712170bf3f602ef64c6312bd6de79@haiku-os.org> References: <040.ae3712170bf3f602ef64c6312bd6de79@haiku-os.org> Message-ID: <049.3760551a93f933b9929d85f30395ae98@haiku-os.org> #1993: Implement using HPET timers and other mechanisms than TSC for time keeping --------------------------+------------------------------------------------- Reporter: axeld | Owner: axeld Type: enhancement | Status: new Priority: high | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Old description: > On CPUs that are able to change their frequency, the TSC increment is not > invariant. Therefore, we cannot use it to compute time on these machines. > Unfortunately, most recent CPUs are affected due to power saving > features. New description: On CPUs that are able to change their frequency, the TSC increment is not invariant. Therefore, we cannot use it to compute time on these machines. Unfortunately, most recent CPUs are affected due to power saving features. Furthermore, in a SMP environment, the TSC of the different CPUs can drift apart. See http://lkml.org/lkml/2005/11/4/173 for an interesting insight on that topic. For HPET (and PM timer) see ACPI 3.0 specification: http://www.acpi.info/spec.htm -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 31 08:24:52 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 31 Mar 2008 06:24:52 -0000 Subject: [Haiku-bugs] [Haiku] #1993: Implement using HPET timers and other mechanisms than TSC for time keeping In-Reply-To: <040.ae3712170bf3f602ef64c6312bd6de79@haiku-os.org> References: <040.ae3712170bf3f602ef64c6312bd6de79@haiku-os.org> Message-ID: <049.97c200d4da719267b881c164afad36f2@haiku-os.org> #1993: Implement using HPET timers and other mechanisms than TSC for time keeping --------------------------+------------------------------------------------- Reporter: axeld | Owner: axeld Type: enhancement | Status: new Priority: high | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Old description: > On CPUs that are able to change their frequency, the TSC increment is not > invariant. Therefore, we cannot use it to compute time on these machines. > Unfortunately, most recent CPUs are affected due to power saving > features. > > Furthermore, in a SMP environment, the TSC of the different CPUs can > drift apart. See http://lkml.org/lkml/2005/11/4/173 for an interesting > insight on that topic. > > For HPET (and PM timer) see ACPI 3.0 specification: > http://www.acpi.info/spec.htm New description: On CPUs that are able to change their frequency, the TSC increment is not invariant. Therefore, we cannot use it to compute time on these machines. Unfortunately, most recent CPUs are affected due to power saving features. Furthermore, in a SMP environment, the TSC of the different CPUs can drift apart. See http://lkml.org/lkml/2005/11/4/173 for an interesting insight on that topic. For HPET (and PM timer) see ACPI 3.0 specification http://www.acpi.info/spec.htm and http://www.intel.com/technology/architecture/hpetspec.htm -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 31 08:33:40 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 31 Mar 2008 06:33:40 -0000 Subject: [Haiku-bugs] [Haiku] #1994: TCP does not support urgent (or inline) data Message-ID: <040.392ae018eab8b4c74ac4876113e036b8@haiku-os.org> #1994: TCP does not support urgent (or inline) data ------------------------------------+--------------------------------------- Reporter: axeld | Owner: hugosantos Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet/TCP | Version: R1 development Platform: All | ------------------------------------+--------------------------------------- Our implementation of the TCP protocol does not yet support urgent data. It's not widely used, but has to be implemented anyway. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 31 10:45:48 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 31 Mar 2008 08:45:48 -0000 Subject: [Haiku-bugs] [Haiku] #1993: Implement using HPET timers and other mechanisms than TSC for time keeping In-Reply-To: <040.ae3712170bf3f602ef64c6312bd6de79@haiku-os.org> References: <040.ae3712170bf3f602ef64c6312bd6de79@haiku-os.org> Message-ID: <049.2c7a374845e95196bdf8867e8fa4547a@haiku-os.org> #1993: Implement using HPET timers and other mechanisms than TSC for time keeping --------------------------+------------------------------------------------- Reporter: axeld | Owner: axeld Type: enhancement | Status: new Priority: high | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Old description: > On CPUs that are able to change their frequency, the TSC increment is not > invariant. Therefore, we cannot use it to compute time on these machines. > Unfortunately, most recent CPUs are affected due to power saving > features. > > Furthermore, in a SMP environment, the TSC of the different CPUs can > drift apart. See http://lkml.org/lkml/2005/11/4/173 for an interesting > insight on that topic. > > For HPET (and PM timer) see ACPI 3.0 specification > http://www.acpi.info/spec.htm and > http://www.intel.com/technology/architecture/hpetspec.htm New description: On CPUs that are able to change their frequency, the TSC increment is not invariant. Therefore, we cannot use it to compute time on these machines. Unfortunately, most recent CPUs are affected due to power saving features. Furthermore, in an SMP environment, the TSC of the different CPUs can drift apart. See http://lkml.org/lkml/2005/11/4/173 for an interesting insight on that topic. For HPET (and PM timer) see ACPI 3.0 specification http://www.acpi.info/spec.htm and http://www.intel.com/technology/architecture/hpetspec.htm -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 31 11:27:03 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 31 Mar 2008 09:27:03 -0000 Subject: [Haiku-bugs] [Haiku] #1980: Implement XSI semaphore and IPC API In-Reply-To: <040.56f95d83cc85c72016c7e381b6cda716@haiku-os.org> References: <040.56f95d83cc85c72016c7e381b6cda716@haiku-os.org> Message-ID: <049.dc20608def5b9c2ae5dd322310998a43@haiku-os.org> #1980: Implement XSI semaphore and IPC API --------------------------------+------------------------------------------- Reporter: axeld | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: Unscheduled Component: System/libroot.so | Version: R1 development Resolution: | Platform: All --------------------------------+------------------------------------------- Comment (by mmu_man): Those have a lot of peculiarities, I looked at implementing them through a separate filesystem + library, but there are quite many side-effects on them... Actually it's been long since I've seen something that really required those. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 31 13:22:26 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 31 Mar 2008 11:22:26 -0000 Subject: [Haiku-bugs] [Haiku] #1993: Implement using HPET timers and other mechanisms than TSC for time keeping In-Reply-To: <040.ae3712170bf3f602ef64c6312bd6de79@haiku-os.org> References: <040.ae3712170bf3f602ef64c6312bd6de79@haiku-os.org> Message-ID: <049.485c4f8f14d49c73ab40061285286c08@haiku-os.org> #1993: Implement using HPET timers and other mechanisms than TSC for time keeping --------------------------+------------------------------------------------- Reporter: axeld | Owner: axeld Type: enhancement | Status: new Priority: high | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by mmlr): Just to document that: In fact the same mechanism as in the cpu_fix driver can be used to "resync" the system time after a frequency change. By adjusting the conversion factor and the time base the system_time() can be made reliable without interruption (http://beos.mlotz.ch/documents/cpu_fix.html). So the only thing that is a problem are unsynchronized TSCs across multiple cores/processors. As far as I know though only certain AMD multi core processors do not provide an invariant TSC across the cores (as described in the lkml message you linked). I mention that since using the CPU internal rdtsc is desirable for performance reasons and therefore should be used when possible. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 31 14:03:20 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 31 Mar 2008 12:03:20 -0000 Subject: [Haiku-bugs] [Haiku] #1982: unmount bug: PANIC: vm_page_fault: unhandled page fault in kernel In-Reply-To: <040.07f9632ff503a91bdd3f366026b60cfc@haiku-os.org> References: <040.07f9632ff503a91bdd3f366026b60cfc@haiku-os.org> Message-ID: <049.374e07cd161037ca4d041fa045f98ee6@haiku-os.org> #1982: unmount bug: PANIC: vm_page_fault: unhandled page fault in kernel ----------------------------+----------------------------------------------- Reporter: thorn | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Changes (by axeld): * priority: normal => high Comment: Perfectly reproducible here. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 31 16:16:58 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 31 Mar 2008 14:16:58 -0000 Subject: [Haiku-bugs] [Haiku] #1962: Some resolutions in VESA no longer work In-Reply-To: <044.144153a4a47b9e6b368c0cb2527e4b97@haiku-os.org> References: <044.144153a4a47b9e6b368c0cb2527e4b97@haiku-os.org> Message-ID: <053.56cbf317859272bc175b0a9ad590292f@haiku-os.org> #1962: Some resolutions in VESA no longer work ------------------------+--------------------------------------------------- Reporter: j_freeman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by j_freeman): I'm positive I was able to use the resolution with the VESA driver, but I can't seem to reproduce it. Yesterday I went as far back as a month in testing older revisions, but they either didn't list the resolution or listed it and it displayed as 800x600. I did upgrade my version of VMware Workstation recently, and that could have very well upgraded the VMware BIOS. That's the only thing I can think of. I'll try and go back to an older version of VMware when I have some time and see what that does. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 31 16:39:08 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 31 Mar 2008 14:39:08 -0000 Subject: [Haiku-bugs] [Haiku] #1071: Identify and fix performance bottlenecks in the kernel and I/O subsystems In-Reply-To: <040.061c44f3c8fb802b19eac228751356e4@haiku-os.org> References: <040.061c44f3c8fb802b19eac228751356e4@haiku-os.org> Message-ID: <049.2dc7874b968ecc2c0de778e75b5f7965@haiku-os.org> #1071: Identify and fix performance bottlenecks in the kernel and I/O subsystems ----------------------------+----------------------------------------------- Reporter: axeld | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by kaoutsis): i updated the file area_tests2.results, with r24702, some comments after running the test program for 2 hours, allocating, and freeing all the available memory with various ways: * haiku's create_area() has an almost constant cost of 21 - 25 us (some very rare cases 1 per 5 the cost may reach 87 us, which is the maximum value that haiku gives) * haiku's delete_area() has been significantly improved since r22045; now the value is related to the number and the size of the areas, the overall cost not only has been reduced, but stays the same regardless of the "memory overhead" of the system. Still the haiku numbers is somehow bigger than the r5 equivalent. * touching a page costs a bit more than the cost in r22045 (approximately 20% - 25%) Stressing the system more (allocating and freeing all the available memory for more than an hour with the test program) the cost of touching a page is increased a bit more 10% - 15%, but after two hours seems to stabilized to this maximum value. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 31 17:07:33 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 31 Mar 2008 15:07:33 -0000 Subject: [Haiku-bugs] [Haiku] #1995: if a program takes up all the available memory haiku freezes Message-ID: <043.9d5e00d8abe1ec57c84ca6dd790dca8d@haiku-os.org> #1995: if a program takes up all the available memory haiku freezes -----------------------+---------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- * take this http://dev.haiku- os.org/attachment/ticket/1071/area_creation_test.cpp * run the test and try to take up all the available ram; for example: ./area_creation_test 100 B_ANY_ADDRESS B_NO_LOCK 'B_WRITE_AREA|B_READ_AREA' 500 eats 200MB * when the free memory is vanished, haiku will freeze May be it's better if the program gets killed? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 31 17:14:38 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 31 Mar 2008 15:14:38 -0000 Subject: [Haiku-bugs] [Haiku] #1996: Terminal: the selected area flickers Message-ID: <043.8540bad930f3eb453d9bb5a20b772a31@haiku-os.org> #1996: Terminal: the selected area flickers -----------------------+---------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 31 17:16:28 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 31 Mar 2008 15:16:28 -0000 Subject: [Haiku-bugs] [Haiku] #1996: Terminal: the selected area flickers In-Reply-To: <043.8540bad930f3eb453d9bb5a20b772a31@haiku-os.org> References: <043.8540bad930f3eb453d9bb5a20b772a31@haiku-os.org> Message-ID: <052.2db4885e941fb846ecb7c21f09750631@haiku-os.org> #1996: Terminal: the selected area flickers ------------------------+--------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by kaoutsis): when is selected by the mouse, to be exact. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 31 17:58:32 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 31 Mar 2008 15:58:32 -0000 Subject: [Haiku-bugs] [Haiku] #1997: Restart dialog occasionally comes up with infinite (or extremely large) height Message-ID: <044.5af3e31c218bbd027ebbb17e33bee520@haiku-os.org> #1997: Restart dialog occasionally comes up with infinite (or extremely large) height ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: anevilyak Type: bug | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Platform: All | ----------------------------+----------------------------------------------- Probably once in 20 or so boots of Haiku, the restart dialog has a near- infinite height for some reason. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 31 18:06:15 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 31 Mar 2008 16:06:15 -0000 Subject: [Haiku-bugs] [Haiku] #1071: Identify and fix performance bottlenecks in the kernel and I/O subsystems In-Reply-To: <040.061c44f3c8fb802b19eac228751356e4@haiku-os.org> References: <040.061c44f3c8fb802b19eac228751356e4@haiku-os.org> Message-ID: <049.8b5bcfcf31673b93897e4333cded31b8@haiku-os.org> #1071: Identify and fix performance bottlenecks in the kernel and I/O subsystems ----------------------------+----------------------------------------------- Reporter: axeld | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by bonefish): Thanks for the update! As expected Michael's kernel heap fixes have fixed the worst problem. I suppose now the page fault performance deserves to be looked into -- I wouldn't see why we should be slower than BeOS. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 31 18:52:03 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 31 Mar 2008 16:52:03 -0000 Subject: [Haiku-bugs] [Haiku] #1918: Terminal Deadlock When TTY Buffer Full In-Reply-To: <043.655f40b7e12dc80914c04ebdcf2ed1cd@haiku-os.org> References: <043.655f40b7e12dc80914c04ebdcf2ed1cd@haiku-os.org> Message-ID: <052.b27ce73d77ecbb61cdce53f7ee9b600a@haiku-os.org> #1918: Terminal Deadlock When TTY Buffer Full ------------------------------------+--------------------------------------- Reporter: bonefish | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Resolution: | Platform: All ------------------------------------+--------------------------------------- Comment (by thorn): looks like fixed. I can't reproduce with "seq 100000" -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 31 18:54:12 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 31 Mar 2008 16:54:12 -0000 Subject: [Haiku-bugs] [Haiku] #1997: Restart dialog occasionally comes up with infinite (or extremely large) height In-Reply-To: <044.5af3e31c218bbd027ebbb17e33bee520@haiku-os.org> References: <044.5af3e31c218bbd027ebbb17e33bee520@haiku-os.org> Message-ID: <053.605398d35c6591a70cf5e67f79f407d1@haiku-os.org> #1997: Restart dialog occasionally comes up with infinite (or extremely large) height -----------------------------+---------------------------------------------- Reporter: anevilyak | Owner: anevilyak Type: bug | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Platform: All -----------------------------+---------------------------------------------- Comment (by bonefish): I've also seen the Terminal window opening with only a few pixels height and huge width. Smells like an initialization race condition. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 31 19:09:44 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 31 Mar 2008 17:09:44 -0000 Subject: [Haiku-bugs] [Haiku] #1997: Restart dialog occasionally comes up with infinite (or extremely large) height In-Reply-To: <044.5af3e31c218bbd027ebbb17e33bee520@haiku-os.org> References: <044.5af3e31c218bbd027ebbb17e33bee520@haiku-os.org> Message-ID: <053.d149ce3e2e694daa155ace5302374613@haiku-os.org> #1997: Restart dialog occasionally comes up with infinite (or extremely large) height -----------------------------+---------------------------------------------- Reporter: anevilyak | Owner: anevilyak Type: bug | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Platform: All -----------------------------+---------------------------------------------- Comment (by anevilyak): You mean the terminal that's brought up on startup, or any random Terminal? I haven't observed that as of yet. And init race was my thought exactly, as the restart dialog appears to be created on boot and then just Show/Hidden from there instead of being recreated. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 31 19:17:01 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 31 Mar 2008 17:17:01 -0000 Subject: [Haiku-bugs] [Haiku] #1918: Terminal Deadlock When TTY Buffer Full In-Reply-To: <043.655f40b7e12dc80914c04ebdcf2ed1cd@haiku-os.org> References: <043.655f40b7e12dc80914c04ebdcf2ed1cd@haiku-os.org> Message-ID: <052.4402b618c629a6c6d6e2f2333f156aa5@haiku-os.org> #1918: Terminal Deadlock When TTY Buffer Full ------------------------------------+--------------------------------------- Reporter: bonefish | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Resolution: | Platform: All ------------------------------------+--------------------------------------- Comment (by anevilyak): Possibly related to this, I noticed tail -f on syslog while doing a Haiku build goes dead after a while, no user interaction needed though. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 31 19:18:49 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 31 Mar 2008 17:18:49 -0000 Subject: [Haiku-bugs] [Haiku] #1918: Terminal Deadlock When TTY Buffer Full In-Reply-To: <043.655f40b7e12dc80914c04ebdcf2ed1cd@haiku-os.org> References: <043.655f40b7e12dc80914c04ebdcf2ed1cd@haiku-os.org> Message-ID: <052.4d04177395943375f528915987abad9a@haiku-os.org> #1918: Terminal Deadlock When TTY Buffer Full ------------------------------------+--------------------------------------- Reporter: bonefish | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Resolution: | Platform: All ------------------------------------+--------------------------------------- Changes (by anevilyak): * cc: anevilyak (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 31 19:28:23 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 31 Mar 2008 17:28:23 -0000 Subject: [Haiku-bugs] [Haiku] #1071: Identify and fix performance bottlenecks in the kernel and I/O subsystems In-Reply-To: <040.061c44f3c8fb802b19eac228751356e4@haiku-os.org> References: <040.061c44f3c8fb802b19eac228751356e4@haiku-os.org> Message-ID: <049.8af80ae90204bf0b7c2273236a0694d8@haiku-os.org> #1071: Identify and fix performance bottlenecks in the kernel and I/O subsystems ----------------------------+----------------------------------------------- Reporter: axeld | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by kaoutsis): Replying to [comment:15 bonefish]: > Thanks for the update! As expected Michael's kernel heap fixes have fixed the worst problem. I suppose now the page fault performance deserves to be looked into -- I wouldn't see why we should be slower than BeOS. yes, that would be great. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 31 19:44:26 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 31 Mar 2008 17:44:26 -0000 Subject: [Haiku-bugs] [Haiku] #1918: Terminal Deadlock When TTY Buffer Full In-Reply-To: <043.655f40b7e12dc80914c04ebdcf2ed1cd@haiku-os.org> References: <043.655f40b7e12dc80914c04ebdcf2ed1cd@haiku-os.org> Message-ID: <052.911e4f62b689399bf787a4c5fbc98370@haiku-os.org> #1918: Terminal Deadlock When TTY Buffer Full ------------------------------------+--------------------------------------- Reporter: bonefish | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Resolution: | Platform: All ------------------------------------+--------------------------------------- Comment (by mmlr): The tail -f probably just ends because the syslog is full and a new syslog file is created. You should try tail -F instead as this will reopen the new syslog and follow it when it is exchanged. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 31 19:49:49 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 31 Mar 2008 17:49:49 -0000 Subject: [Haiku-bugs] [Haiku] #1918: Terminal Deadlock When TTY Buffer Full In-Reply-To: <043.655f40b7e12dc80914c04ebdcf2ed1cd@haiku-os.org> References: <043.655f40b7e12dc80914c04ebdcf2ed1cd@haiku-os.org> Message-ID: <052.4ee74ba0aff581102e1c9f32c03831a9@haiku-os.org> #1918: Terminal Deadlock When TTY Buffer Full ------------------------------------+--------------------------------------- Reporter: bonefish | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Resolution: | Platform: All ------------------------------------+--------------------------------------- Comment (by anevilyak): What's the size limit on syslog? It hadn't shown more than maybe 20-30 lines before it stopped. Also ctrl+c to terminate tail didn't work at that point. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 31 20:17:10 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 31 Mar 2008 18:17:10 -0000 Subject: [Haiku-bugs] [Haiku] #1997: Restart dialog occasionally comes up with infinite (or extremely large) height In-Reply-To: <044.5af3e31c218bbd027ebbb17e33bee520@haiku-os.org> References: <044.5af3e31c218bbd027ebbb17e33bee520@haiku-os.org> Message-ID: <053.fb24a3d0ed755feb97814202f90c44ef@haiku-os.org> #1997: Restart dialog occasionally comes up with infinite (or extremely large) height -----------------------------+---------------------------------------------- Reporter: anevilyak | Owner: anevilyak Type: bug | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Platform: All -----------------------------+---------------------------------------------- Comment (by bipolar): I've noticed the Media preflet become exceptionally wide (something that felt like 10000 pixels). Don't know if this is related, but as Ingo mentioned the Terminal... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 31 20:21:55 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 31 Mar 2008 18:21:55 -0000 Subject: [Haiku-bugs] [Haiku] #1918: Terminal Deadlock When TTY Buffer Full In-Reply-To: <043.655f40b7e12dc80914c04ebdcf2ed1cd@haiku-os.org> References: <043.655f40b7e12dc80914c04ebdcf2ed1cd@haiku-os.org> Message-ID: <052.267d4001b97ecdfb6b1b1431aa9ff7c2@haiku-os.org> #1918: Terminal Deadlock When TTY Buffer Full ------------------------------------+--------------------------------------- Reporter: bonefish | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Resolution: | Platform: All ------------------------------------+--------------------------------------- Comment (by mmlr): The limit doesn't really matter, if it was 90% full it might have been exchanged after only a few new lines. But that you couldn't ctrl-c it would obviously be a bug. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 31 21:04:17 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 31 Mar 2008 19:04:17 -0000 Subject: [Haiku-bugs] [Haiku] #1997: Restart dialog occasionally comes up with infinite (or extremely large) height In-Reply-To: <044.5af3e31c218bbd027ebbb17e33bee520@haiku-os.org> References: <044.5af3e31c218bbd027ebbb17e33bee520@haiku-os.org> Message-ID: <053.c3f3163efc6c9a4428b4f01c5ba2891b@haiku-os.org> #1997: Restart dialog occasionally comes up with infinite (or extremely large) height -----------------------------+---------------------------------------------- Reporter: anevilyak | Owner: anevilyak Type: bug | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Platform: All -----------------------------+---------------------------------------------- Comment (by diver): Replying to [comment:1 bonefish]: > I've also seen the Terminal window opening with only a few pixels height and huge width. Smells like an initialization race condition. Yeah. I saw this too several times, last time it was 2 days ago. It was when i started several times Terminal from LaunchBox. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 31 21:12:40 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 31 Mar 2008 19:12:40 -0000 Subject: [Haiku-bugs] [Haiku] #1998: haiku virtual disk image size is not aligned on the disk size Message-ID: <044.cfceee10069717ac2c69d9b1779cb987@haiku-os.org> #1998: haiku virtual disk image size is not aligned on the disk size --------------------------+------------------------------------------------- Reporter: starsseed | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Platform: x86 | --------------------------+------------------------------------------------- For a disk whom the size is about 256 Megabyte, the disk geometry is 16 heads 63 sector. but the VmWare disk image or the raw image disk contain 512000 sector instead of 511056 (507 cylindres) or 512064 (508 cylindres) for an image size aligned on the disk size. when I try to convert the raw image to a Virtual-PC VHD file with 507 cylindres 16 heads 63 sector(ie the disk geometry specified in the Hiaku.vmdk file), the BootLoader boot the kernel and the kernel run in debug mode when mounting the boot FS (Thanks to the new boot animated screen) when I load the image in a disk with 508 cylindres, Haiku boot correctly Is it possible to correct the disk image size to 512064 sectors and 508 cylindres(262176768 bytes ) to align the target image to the disk geometry ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 31 21:27:24 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 31 Mar 2008 19:27:24 -0000 Subject: [Haiku-bugs] [Haiku] #1998: haiku virtual disk image size is not aligned on the disk size In-Reply-To: <044.cfceee10069717ac2c69d9b1779cb987@haiku-os.org> References: <044.cfceee10069717ac2c69d9b1779cb987@haiku-os.org> Message-ID: <053.b02075abab1b128128792c74541ee16d@haiku-os.org> #1998: haiku virtual disk image size is not aligned on the disk size ---------------------------+------------------------------------------------ Reporter: starsseed | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Platform: x86 ---------------------------+------------------------------------------------ Changes (by siarzhuk): * cc: siarzhuk (added) Comment: 2 starsseed: Which tool do you use to convert vmdk to vhd? Btw, I wrote a tool for converting raw haiku images directly into dynamic VHD for using with VPC. I can share it with you. May be it can be interesting as part of Haiku source tree too? ;-) The second question: Do you have problems booting Haiku on VPC? On my system there are sporadic timeouts directly before showing splash screen. :-\ -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 31 21:58:42 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 31 Mar 2008 19:58:42 -0000 Subject: [Haiku-bugs] [Haiku] #1557: Frequency out of range In-Reply-To: <044.15236cb511ee12c72ec612ed24aea2ba@haiku-os.org> References: <044.15236cb511ee12c72ec612ed24aea2ba@haiku-os.org> Message-ID: <053.038807b5a1ec8b14a766fcd7704ca01a@haiku-os.org> #1557: Frequency out of range --------------------------------------+------------------------------------- Reporter: plfiorini | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: | Platform: x86 --------------------------------------+------------------------------------- Comment (by korli): Did you try a fail safe video mode in the boot menu ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Mar 31 23:43:06 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 31 Mar 2008 21:43:06 -0000 Subject: [Haiku-bugs] [Haiku] #1998: haiku virtual disk image size is not aligned on the disk size In-Reply-To: <044.cfceee10069717ac2c69d9b1779cb987@haiku-os.org> References: <044.cfceee10069717ac2c69d9b1779cb987@haiku-os.org> Message-ID: <053.abba3f6239be1b19eea3677be5664480@haiku-os.org> #1998: haiku virtual disk image size is not aligned on the disk size ---------------------------+------------------------------------------------ Reporter: starsseed | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Platform: x86 ---------------------------+------------------------------------------------ Comment (by starsseed): to anevilyak: under virtual-pc the pause is about 2-3 minutes long ! to siarzhuk: I'am interested to share ours sources (I wanted to publish mine when it will more mature and a bit more clean...) but the place of my code is not in the haiku tree because for the moment it's just a tiny tools for MsWindows... -- Ticket URL: Haiku The Haiku operating system.