Latest Bugs & Tasks

I'm going to close this for lack of feedback and under the assumption that if it was a usb_hid problem it's resolved by now through the two rewrites. I haven't heared of any problems regarding usb_hid and GCC4 and also have run GCC4 builds with it with no problems. If this actually was a PS/2 problem then it might persist, in which case a new bug report should be opened with the correct component.

I close it as it's fixed as far I could tell.

Fixed with r35811.
Note, however, that the current implementation of bolding the app name is not translation sensitive as the number of bolded letters is fixed.

This bug report a mess. The original report concerned an interrupt storm (probably fixed), then there were reports of spurious and unacknowledged interrupts (fixed), there was a report about missing interrupts due to bad chipset (different issue) and eventually there was the SMI storm (most probably fixed in r35780). I'm therefore going to close this report, please file new reports if you still encounter any of these issues.

r35770 and earlier.

(gdb) bt
#0  0x002cb362 in BMessage::_FindField () from /boot/system/lib/libbe.so
#1  0x002cba42 in BMessage::FindData () from /boot/system/lib/libbe.so
#2  0x002cd1d7 in BMessage::FindInt32 () from /boot/system/lib/libbe.so
#3  0x00389687 in BWindow::_DetermineTarget () from /boot/system/lib/libbe.so
#4  0x00388eb4 in BWindow::task_looper () from /boot/system/lib/libbe.so
#5  0x002c6f1f in BLooper::_task0_ () from /boot/system/lib/libbe.so
#6  0x0068dbf6 in thread_entry () from /boot/system/lib/libroot.so
#7  0x70184fec in ?? ()
(gdb)

Thanks! Closing ticket.

Earlier today, I downgraded to r34464 which was very stable version for me. After experiencing vm related crashes while compiling Haiku, I swapped the PSU out with a spare. Lo and behold, stability was regained.

By the way, can I get a cup of Earl Grey to go with my humble pie? ;)

Thanks for following up! Closing.

I'm going to close this one. Without further feedback all seems perfectly fine as explained in comment 8 above. I can only guess that by "not recognized" actually "not automounted" was meant as the syslog indicates the device and filesystem were detected fine.

Since this can't be reproduced anymore (due to the hardware not being around anymore) I'm closing this one. Quite likely it was the same issue as the last one of the ones in #2083 and therefore fixed by r35780.

For lack of feedback I'm going to close this under the assumption that it was an address space overflow which was fixed in the meantime, please reopen or create a new ticket if seen again.

Ok, closing, thanks for the feedback!

Closing, thanks for the feedback.

Driver is incomplete, but contained a very small number of GPGPU cards. This adds the majority of the 8xxx series Nvidia cards and also adds information on Chipset version.

And yes, i know it's not used yet.. just doing some of the leg work. Device ID's from  http://www.pcidatabase.com/vendor_details.php?id=606

"OPERATING SYSTEM" was removed from the 'Slogan' field on the  site-information page. To note, the copyright years were also updated.

Closing the ticket. IIRC this was the last offense of directly associating "OS" or "Operating System" with "Haiku". There may be some references in comments and forum postings.

Hi,

When scrolling in terminal and other applications, I get a fair amount of vertical tearing, and sluggish draws. I've verified the nvidia accelerant is being used:

~> listimage 64 |grep accelerant

299 /boot/system/add-ons/accelerants/nvidia.accelerant 0x8cb000 0x903000 0 0

~>

It draws (visibly) about the same rate as my VESA installations on other systems.

Attached is a syslog, if more information is needed, please let me know.

Ok, I managed to boot haiku, and I can confirm the bug is fixed.

Thanks for the feedback! Fixed in r35796.

See screenshot.
Tested with r35795 in VirtualBox 3.0.12

hey registrar '_ABR'

Tested with r35795 in VirtualBox 3.0.12