Primax98 Posted January 16, 2023 Report Posted January 16, 2023 Hi Guys, We are starting to have issues with our desk crashing and becoming unreliable. Typically these always seem to choose to crash during production time...... Desk is a Zero88 solution OS 7.10 Generic Microsoft Mouse and Dell keyboard. VGA Monitor no touch screen. ZerOS System WAtchdod has detected and error condition A debug report has been saves and can be cpoied to a USB flash drive on the next boot SIGSEGV : Segmentation Fault! info.si_signo = 11 info.si_errno = 0Info.si_code = 1 (SEGV_MAPERR) info.si_addr = 0xb4 Registers: reg[00] = 0x00000033 and there are more.......... Stack trace (non-dedicated): Bootdev/desk/desk() [0x85a1136] and more.... attached image if it helps too. Obviously were nervous about doing a further update. Any help appreciated. Thank you all. Quote
kgallen Posted January 16, 2023 Report Posted January 16, 2023 Did you manage to get the debug report onto a USB stick? If you haven't already, I'd attach it here or email in to support@zero88.com (with a covering note) so Edward can take a look at it. Quote
Primax98 Posted January 16, 2023 Author Report Posted January 16, 2023 We didnt no, we were already nearly an hour late. I will attach to this post and email on when it happens nex. Thank you @kgallen Paul Quote
iank99 Posted January 17, 2023 Report Posted January 17, 2023 It looks from your image that the desk might be moved around regularly? In which case I'd be tempted to open it and ensure the Compact Flash drive is seated properly on it's connector - there's no retaining clip on it & it's feasible that it might have worked slightly loose, a gentle push to reseat it might be enough... I'd also change the internal battery whilst you have the case open - just in case or if you haven't swapped the battery lately - it's a CR2032 so commonly available. It would also be worth trying a boot without the keyboard attached, they do go bad & it might be drawing too much current from the onboard USBHub (but to be honest - this is a rare error these days). Quote Ian Knight aka The Service Guy - www.serviceguy.co.uk
Primax98 Posted January 17, 2023 Author Report Posted January 17, 2023 HI ian, thank you for the reply. i have just arrived on site.... Yes she is a busy girl indeed. we are on the road pretty much for the next 3 weeks from school to school so this could indeed be a possibility. I am awaiting my colleague to arrive before firing up the desk. I am pretty sure i replaced the bios battery last year, however you never know how good they are out of the packet so..... I will reply with any news. Thank you all indeed. Quote
Primax98 Posted January 21, 2023 Author Report Posted January 21, 2023 HI all, well it happened on a show night , ahhhhhh. It all went ok in the end, but this time got a crash report. debug_27-3-2017_19-51-54.zdb Quote
Edward Z88 Posted January 23, 2023 Report Posted January 23, 2023 Thank you for emailing us the debug file from your console. We will be in touch. Edward Quote Edward Smith Product Specialist Email Support
Desgeorge Posted April 7, 2023 Report Posted April 7, 2023 WE have a similar problem did you get it fixed? Quote
Primax98 Posted April 7, 2023 Author Report Posted April 7, 2023 Yes we did in the end. There was a newer version available that we went to and all was good. Typically that version had issues and was directed Zero88 to put their latest on. Good luck ! Quote
lacapella Posted April 27, 2023 Report Posted April 27, 2023 Hello Edward, Can you help for this bugs. Thanks, debug_6-5-2022_07-33-05.zdb debug_6-5-2022_07-33-09.zdb debug_6-5-2022_07-33-01.zdb debug_6-5-2022_07-33-19.zdb debug_6-5-2022_07-33-25.zdb Quote
Edward Z88 Posted May 2, 2023 Report Posted May 2, 2023 Hi @lacapella On 4/27/2023 at 12:16 PM, lacapella said: Can you help for this bugs. Thank you for attaching the debug files from your console. Sorry to see you encountered this error. The debug files are reporting very little information. Unfortunately there is not enough data to understand what may have occurred. Are you able to send us an email, with step-by-step instructions of what you did on the console when these errors occurred? For example, did these occur during patching, or upon pressing a particular button? We will then be able to troubleshoot further. Quote Edward Smith Product Specialist Email Support
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.