Thread: [ES40-developers] Code formatting
Status: Alpha
Brought to you by:
iamcamiel
Menu
▾
▴
es40-developers
|
From: Camiel V. <iam...@gm...> - 2008-03-14 16:24:22
|
Hello Everyone, I've committed a couple of large patches today and yesterday to improve both multithreading and exception handling. This results in restoration of the functionality of the <break> menu on the serial ports. After these changes, I've run all code through a source code formatter to make the coding style a bit more consistent. I'd like you to check out the new code, and let me know if there are aspects of the source formatting that you don't like. I'm hoping this will improve readibility of the source code, and will help to develop a set of guidelines for coding style. Thanks! Camiel. P.S. I've tagged the repository before committing the re-formatted code; if anything has gone horribly wrong, we can revert... |
|
From: Fausto S. <fa...@un...> - 2008-03-14 19:04:55
|
Hello Camiel, I just updated the cvs, and the build is fine. But I have a new issue with IDE cdrom. I'm using the device (under Windows Vista) and when I try to mound a cdrom, I have : %MOUNT-I-WRITELOCK, volume is write locked and the system is freezed. On the DOS console the counter still runs, but nothing happens, and I don't have error messages. Yesterday, before the latest patch, I had the same problem, but on the DOS console I had these error messages (looping on the console): CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: ff-ff-ff-ff-ff-ff .. src: 00-19-3e-36-70-1b CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: ff-ff-ff-ff-ff-ff .. src: 00-19-3e-36-70-1b CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: ff-ff-ff-ff-ff-ff .. src: 00-19-3e-36-70-1b CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: ff-ff-ff-ff-ff-ff .. src: 00-19-3e-36-70-1b CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: ff-ff-ff-ff-ff-ff .. src: 00-19-3e-36-70-1b CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: ff-ff-ff-ff-ff-ff .. src: 00-19-3e-36-70-1b CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: ff-ff-ff-ff-ff-ff .. src: 00-19-3e-36-70-1b the only thing to do is CTRL-C, and when I do it the quit procedure doesn't complete, stopping at Freeing memory in use by system... cpu0 pressing again CTRL-C, the emulator quits. regards, fausto Quoting Camiel Vanderhoeven <iam...@gm...>: > Hello Everyone, > > I've committed a couple of large patches today and yesterday to > improve both multithreading and exception handling. This results in > restoration of the functionality of the <break> menu on the serial > ports. After these changes, I've run all code through a source code > formatter to make the coding style a bit more consistent. I'd like you > to check out the new code, and let me know if there are aspects of the > source formatting that you don't like. I'm hoping this will improve > readibility of the source code, and will help to develop a set of > guidelines for coding style. > > Thanks! > > Camiel. > > P.S. I've tagged the repository before committing the re-formatted > code; if anything has gone horribly wrong, we can revert... > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Es40-developers mailing list > Es4...@li... > https://lists.sourceforge.net/lists/listinfo/es40-developers > |
|
From: Hittner, D. T. <dav...@ng...> - 2008-03-14 19:21:26
|
The CPacketQueue() messages are debug warnings that packets are not being added to the queue; in this case, it's because someone is transmitting runts (packets that are too small (size < 64)) on your network. These are usually (but not always) ARP packets from a really old device or a OS that doesn't care about the following the ethernet spec exactly. You can ignore the CPacketQueue messages... Feel free to comment them out to shut it up. If you look, they are broadcast message to all (ff-ff-ff-ff-ff-ff) from src device: 00-19-3e-36-70-1b. If you track that ID down on your network, I'll be willing to help add code to deal with it if you can tell me the OS and Version that it's running. Dave > -----Original Message----- > From: es4...@li... > [mailto:es4...@li...] On > Behalf Of Fausto Saporito > Sent: Friday, March 14, 2008 3:05 PM > To: es4...@li... > Subject: Re: [ES40-developers] Code formatting > > Hello Camiel, > > I just updated the cvs, and the build is fine. > But I have a new issue with IDE cdrom. I'm using the device > (under Windows Vista) and when I try to mound a cdrom, I have : > > %MOUNT-I-WRITELOCK, volume is write locked > > and the system is freezed. > On the DOS console the counter still runs, but nothing > happens, and I don't have error messages. > > Yesterday, before the latest patch, I had the same problem, > but on the DOS console I had these error messages (looping on > the console): > > CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > ff-ff-ff-ff-ff-ff .. > src: 00-19-3e-36-70-1b > CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > ff-ff-ff-ff-ff-ff .. > src: 00-19-3e-36-70-1b > CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > ff-ff-ff-ff-ff-ff .. > src: 00-19-3e-36-70-1b > CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > ff-ff-ff-ff-ff-ff .. > src: 00-19-3e-36-70-1b > CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > ff-ff-ff-ff-ff-ff .. > src: 00-19-3e-36-70-1b > CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > ff-ff-ff-ff-ff-ff .. > src: 00-19-3e-36-70-1b > CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > ff-ff-ff-ff-ff-ff .. > src: 00-19-3e-36-70-1b > > the only thing to do is CTRL-C, and when I do it the quit > procedure doesn't complete, stopping at > > Freeing memory in use by system... > cpu0 > > pressing again CTRL-C, the emulator quits. > > regards, > fausto > > Quoting Camiel Vanderhoeven <iam...@gm...>: > > > Hello Everyone, > > > > I've committed a couple of large patches today and yesterday to > > improve both multithreading and exception handling. This results in > > restoration of the functionality of the <break> menu on the serial > > ports. After these changes, I've run all code through a source code > > formatter to make the coding style a bit more consistent. > I'd like you > > to check out the new code, and let me know if there are > aspects of the > > source formatting that you don't like. I'm hoping this will improve > > readibility of the source code, and will help to develop a set of > > guidelines for coding style. > > > > Thanks! > > > > Camiel. > > > > P.S. I've tagged the repository before committing the re-formatted > > code; if anything has gone horribly wrong, we can revert... > > > > > ---------------------------------------------------------------------- > > --- This SF.net email is sponsored by: Microsoft Defy all > challenges. > > Microsoft(R) Visual Studio 2008. > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > _______________________________________________ > > Es40-developers mailing list > > Es4...@li... > > https://lists.sourceforge.net/lists/listinfo/es40-developers > > > > > > -------------------------------------------------------------- > ----------- > This SF.net email is sponsored by: Microsoft Defy all > challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Es40-developers mailing list > Es4...@li... > https://lists.sourceforge.net/lists/listinfo/es40-developers > |
|
From: Fausto S. <fa...@un...> - 2008-03-14 19:26:10
|
Hello David, so they are unrelated :-) Sorry for the confusion... by the way I tried to enable the DHCP, but I have always timeout... and no IP address assigned. So those errors are related to this kind of activity... Do you have TCPIP working on OpenVMS? regards, fausto Quoting "Hittner, David T." <dav...@ng...>: > The CPacketQueue() messages are debug warnings that packets are not > being added to the queue; in this case, it's because someone is > transmitting runts (packets that are too small (size < 64)) on your > network. These are usually (but not always) ARP packets from a really > old device or a OS that doesn't care about the following the ethernet > spec exactly. > > You can ignore the CPacketQueue messages... Feel free to comment them > out to shut it up. > > If you look, they are broadcast message to all (ff-ff-ff-ff-ff-ff) from > src device: 00-19-3e-36-70-1b. > If you track that ID down on your network, I'll be willing to help add > code to deal with it if you can tell me the OS and Version that it's > running. > > Dave > >> -----Original Message----- >> From: es4...@li... >> [mailto:es4...@li...] On >> Behalf Of Fausto Saporito >> Sent: Friday, March 14, 2008 3:05 PM >> To: es4...@li... >> Subject: Re: [ES40-developers] Code formatting >> >> Hello Camiel, >> >> I just updated the cvs, and the build is fine. >> But I have a new issue with IDE cdrom. I'm using the device >> (under Windows Vista) and when I try to mound a cdrom, I have : >> >> %MOUNT-I-WRITELOCK, volume is write locked >> >> and the system is freezed. >> On the DOS console the counter still runs, but nothing >> happens, and I don't have error messages. >> >> Yesterday, before the latest patch, I had the same problem, >> but on the DOS console I had these error messages (looping on >> the console): >> >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: >> ff-ff-ff-ff-ff-ff .. >> src: 00-19-3e-36-70-1b >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: >> ff-ff-ff-ff-ff-ff .. >> src: 00-19-3e-36-70-1b >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: >> ff-ff-ff-ff-ff-ff .. >> src: 00-19-3e-36-70-1b >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: >> ff-ff-ff-ff-ff-ff .. >> src: 00-19-3e-36-70-1b >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: >> ff-ff-ff-ff-ff-ff .. >> src: 00-19-3e-36-70-1b >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: >> ff-ff-ff-ff-ff-ff .. >> src: 00-19-3e-36-70-1b >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: >> ff-ff-ff-ff-ff-ff .. >> src: 00-19-3e-36-70-1b >> >> the only thing to do is CTRL-C, and when I do it the quit >> procedure doesn't complete, stopping at >> >> Freeing memory in use by system... >> cpu0 >> >> pressing again CTRL-C, the emulator quits. >> >> regards, >> fausto >> >> Quoting Camiel Vanderhoeven <iam...@gm...>: >> >> > Hello Everyone, >> > >> > I've committed a couple of large patches today and yesterday to >> > improve both multithreading and exception handling. This results in >> > restoration of the functionality of the <break> menu on the serial >> > ports. After these changes, I've run all code through a source code >> > formatter to make the coding style a bit more consistent. >> I'd like you >> > to check out the new code, and let me know if there are >> aspects of the >> > source formatting that you don't like. I'm hoping this will improve >> > readibility of the source code, and will help to develop a set of >> > guidelines for coding style. >> > >> > Thanks! >> > >> > Camiel. >> > >> > P.S. I've tagged the repository before committing the re-formatted >> > code; if anything has gone horribly wrong, we can revert... >> > >> > >> ---------------------------------------------------------------------- >> > --- This SF.net email is sponsored by: Microsoft Defy all >> challenges. >> > Microsoft(R) Visual Studio 2008. >> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> > _______________________________________________ >> > Es40-developers mailing list >> > Es4...@li... >> > https://lists.sourceforge.net/lists/listinfo/es40-developers >> > >> >> >> >> -------------------------------------------------------------- >> ----------- >> This SF.net email is sponsored by: Microsoft Defy all >> challenges. Microsoft(R) Visual Studio 2008. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> _______________________________________________ >> Es40-developers mailing list >> Es4...@li... >> https://lists.sourceforge.net/lists/listinfo/es40-developers >> > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Es40-developers mailing list > Es4...@li... > https://lists.sourceforge.net/lists/listinfo/es40-developers > |
|
From: Camiel V. <iam...@gm...> - 2008-03-14 19:28:53
|
Hi Fausto, I have TCP/IP running, but without DHCP (I'm not running a DHCP server here); try tcpip ifconfig we0 inet 192.168.0.200 255.255.255.0 (change according to your desired IP address, of course) Camiel. On Fri, Mar 14, 2008 at 8:26 PM, Fausto Saporito <fa...@un...> wrote: > Hello David, > > so they are unrelated :-) > Sorry for the confusion... by the way I tried to enable the DHCP, but > I have always timeout... and no IP address assigned. > > So those errors are related to this kind of activity... > > Do you have TCPIP working on OpenVMS? > > regards, > fausto > > > Quoting "Hittner, David T." <dav...@ng...>: > > > The CPacketQueue() messages are debug warnings that packets are not > > being added to the queue; in this case, it's because someone is > > transmitting runts (packets that are too small (size < 64)) on your > > network. These are usually (but not always) ARP packets from a really > > old device or a OS that doesn't care about the following the ethernet > > spec exactly. > > > > You can ignore the CPacketQueue messages... Feel free to comment them > > out to shut it up. > > > > If you look, they are broadcast message to all (ff-ff-ff-ff-ff-ff) from > > src device: 00-19-3e-36-70-1b. > > If you track that ID down on your network, I'll be willing to help add > > code to deal with it if you can tell me the OS and Version that it's > > running. > > > > Dave > > > >> -----Original Message----- > >> From: es4...@li... > >> [mailto:es4...@li...] On > >> Behalf Of Fausto Saporito > >> Sent: Friday, March 14, 2008 3:05 PM > >> To: es4...@li... > >> Subject: Re: [ES40-developers] Code formatting > >> > >> Hello Camiel, > >> > >> I just updated the cvs, and the build is fine. > >> But I have a new issue with IDE cdrom. I'm using the device > >> (under Windows Vista) and when I try to mound a cdrom, I have : > >> > >> %MOUNT-I-WRITELOCK, volume is write locked > >> > >> and the system is freezed. > >> On the DOS console the counter still runs, but nothing > >> happens, and I don't have error messages. > >> > >> Yesterday, before the latest patch, I had the same problem, > >> but on the DOS console I had these error messages (looping on > >> the console): > >> > >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > >> ff-ff-ff-ff-ff-ff .. > >> src: 00-19-3e-36-70-1b > >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > >> ff-ff-ff-ff-ff-ff .. > >> src: 00-19-3e-36-70-1b > >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > >> ff-ff-ff-ff-ff-ff .. > >> src: 00-19-3e-36-70-1b > >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > >> ff-ff-ff-ff-ff-ff .. > >> src: 00-19-3e-36-70-1b > >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > >> ff-ff-ff-ff-ff-ff .. > >> src: 00-19-3e-36-70-1b > >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > >> ff-ff-ff-ff-ff-ff .. > >> src: 00-19-3e-36-70-1b > >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > >> ff-ff-ff-ff-ff-ff .. > >> src: 00-19-3e-36-70-1b > >> > >> the only thing to do is CTRL-C, and when I do it the quit > >> procedure doesn't complete, stopping at > >> > >> Freeing memory in use by system... > >> cpu0 > >> > >> pressing again CTRL-C, the emulator quits. > >> > >> regards, > >> fausto > >> > >> Quoting Camiel Vanderhoeven <iam...@gm...>: > >> > >> > Hello Everyone, > >> > > >> > I've committed a couple of large patches today and yesterday to > >> > improve both multithreading and exception handling. This results in > >> > restoration of the functionality of the <break> menu on the serial > >> > ports. After these changes, I've run all code through a source code > >> > formatter to make the coding style a bit more consistent. > >> I'd like you > >> > to check out the new code, and let me know if there are > >> aspects of the > >> > source formatting that you don't like. I'm hoping this will improve > >> > readibility of the source code, and will help to develop a set of > >> > guidelines for coding style. > >> > > >> > Thanks! > >> > > >> > Camiel. > >> > > >> > P.S. I've tagged the repository before committing the re-formatted > >> > code; if anything has gone horribly wrong, we can revert... > >> > > >> > > >> ---------------------------------------------------------------------- > >> > --- This SF.net email is sponsored by: Microsoft Defy all > >> challenges. > >> > Microsoft(R) Visual Studio 2008. > >> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > >> > _______________________________________________ > >> > Es40-developers mailing list > >> > Es4...@li... > >> > https://lists.sourceforge.net/lists/listinfo/es40-developers > >> > > >> > >> > >> > >> -------------------------------------------------------------- > >> ----------- > >> This SF.net email is sponsored by: Microsoft Defy all > >> challenges. Microsoft(R) Visual Studio 2008. > >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > >> _______________________________________________ > >> Es40-developers mailing list > >> Es4...@li... > >> https://lists.sourceforge.net/lists/listinfo/es40-developers > >> > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Microsoft > > Defy all challenges. Microsoft(R) Visual Studio 2008. > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > _______________________________________________ > > Es40-developers mailing list > > Es4...@li... > > https://lists.sourceforge.net/lists/listinfo/es40-developers > > > > > > ------------------------------------------------------------------------- > > > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Es40-developers mailing list > Es4...@li... > https://lists.sourceforge.net/lists/listinfo/es40-developers > |
|
From: Hittner, D. T. <dav...@ng...> - 2008-03-14 20:51:37
|
Yes, TCP/IP works, but FTP fails on any significant transfer size. It's mostly telnet that works ;-) I've never tried to configure via DHCP though - I've always set a hard address. > -----Original Message----- > From: es4...@li... > [mailto:es4...@li...] On > Behalf Of Fausto Saporito > Sent: Friday, March 14, 2008 3:26 PM > To: es4...@li... > Subject: Re: [ES40-developers] Code formatting > > Hello David, > > so they are unrelated :-) > Sorry for the confusion... by the way I tried to enable the > DHCP, but I have always timeout... and no IP address assigned. > > So those errors are related to this kind of activity... > > Do you have TCPIP working on OpenVMS? > > regards, > fausto > Quoting "Hittner, David T." <dav...@ng...>: > > > The CPacketQueue() messages are debug warnings that packets are not > > being added to the queue; in this case, it's because someone is > > transmitting runts (packets that are too small (size < 64)) on your > > network. These are usually (but not always) ARP packets > from a really > > old device or a OS that doesn't care about the following > the ethernet > > spec exactly. > > > > You can ignore the CPacketQueue messages... Feel free to > comment them > > out to shut it up. > > > > If you look, they are broadcast message to all (ff-ff-ff-ff-ff-ff) > > from src device: 00-19-3e-36-70-1b. > > If you track that ID down on your network, I'll be willing > to help add > > code to deal with it if you can tell me the OS and Version > that it's > > running. > > > > Dave > > > >> -----Original Message----- > >> From: es4...@li... > >> [mailto:es4...@li...] On > Behalf Of > >> Fausto Saporito > >> Sent: Friday, March 14, 2008 3:05 PM > >> To: es4...@li... > >> Subject: Re: [ES40-developers] Code formatting > >> > >> Hello Camiel, > >> > >> I just updated the cvs, and the build is fine. > >> But I have a new issue with IDE cdrom. I'm using the device (under > >> Windows Vista) and when I try to mound a cdrom, I have : > >> > >> %MOUNT-I-WRITELOCK, volume is write locked > >> > >> and the system is freezed. > >> On the DOS console the counter still runs, but nothing > happens, and I > >> don't have error messages. > >> > >> Yesterday, before the latest patch, I had the same problem, but on > >> the DOS console I had these error messages (looping on the > console): > >> > >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > >> ff-ff-ff-ff-ff-ff .. > >> src: 00-19-3e-36-70-1b > >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > >> ff-ff-ff-ff-ff-ff .. > >> src: 00-19-3e-36-70-1b > >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > >> ff-ff-ff-ff-ff-ff .. > >> src: 00-19-3e-36-70-1b > >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > >> ff-ff-ff-ff-ff-ff .. > >> src: 00-19-3e-36-70-1b > >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > >> ff-ff-ff-ff-ff-ff .. > >> src: 00-19-3e-36-70-1b > >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > >> ff-ff-ff-ff-ff-ff .. > >> src: 00-19-3e-36-70-1b > >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > >> ff-ff-ff-ff-ff-ff .. > >> src: 00-19-3e-36-70-1b > >> > >> the only thing to do is CTRL-C, and when I do it the quit > procedure > >> doesn't complete, stopping at > >> > >> Freeing memory in use by system... > >> cpu0 > >> > >> pressing again CTRL-C, the emulator quits. > >> > >> regards, > >> fausto > >> > >> Quoting Camiel Vanderhoeven <iam...@gm...>: > >> > >> > Hello Everyone, > >> > > >> > I've committed a couple of large patches today and yesterday to > >> > improve both multithreading and exception handling. This > results in > >> > restoration of the functionality of the <break> menu on > the serial > >> > ports. After these changes, I've run all code through a > source code > >> > formatter to make the coding style a bit more consistent. > >> I'd like you > >> > to check out the new code, and let me know if there are > >> aspects of the > >> > source formatting that you don't like. I'm hoping this > will improve > >> > readibility of the source code, and will help to develop > a set of > >> > guidelines for coding style. > >> > > >> > Thanks! > >> > > >> > Camiel. > >> > > >> > P.S. I've tagged the repository before committing the > re-formatted > >> > code; if anything has gone horribly wrong, we can revert... > >> > > >> > > >> > --------------------------------------------------------------------- > >> - > >> > --- This SF.net email is sponsored by: Microsoft Defy all > >> challenges. > >> > Microsoft(R) Visual Studio 2008. > >> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > >> > _______________________________________________ > >> > Es40-developers mailing list > >> > Es4...@li... > >> > https://lists.sourceforge.net/lists/listinfo/es40-developers > >> > > >> > >> > >> > >> -------------------------------------------------------------- > >> ----------- > >> This SF.net email is sponsored by: Microsoft Defy all challenges. > >> Microsoft(R) Visual Studio 2008. > >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > >> _______________________________________________ > >> Es40-developers mailing list > >> Es4...@li... > >> https://lists.sourceforge.net/lists/listinfo/es40-developers > >> > > > > > ---------------------------------------------------------------------- > > --- This SF.net email is sponsored by: Microsoft Defy all > challenges. > > Microsoft(R) Visual Studio 2008. > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > _______________________________________________ > > Es40-developers mailing list > > Es4...@li... > > https://lists.sourceforge.net/lists/listinfo/es40-developers > > > > > > -------------------------------------------------------------- > ----------- > This SF.net email is sponsored by: Microsoft Defy all > challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Es40-developers mailing list > Es4...@li... > https://lists.sourceforge.net/lists/listinfo/es40-developers > |
|
From: Camiel V. <iam...@gm...> - 2008-03-14 19:11:38
|
Hello Fausto, A frozen system in this case probably means that the CPU is trying to acquire a lock that is held by the IDE device. Could you try to compile the code with HIDE_COUNTER and DEBUG_LOCKS defined to confirm that this is the case? Thanks, Camiel. On Fri, Mar 14, 2008 at 8:04 PM, Fausto Saporito <fa...@un...> wrote: > Hello Camiel, > > I just updated the cvs, and the build is fine. > But I have a new issue with IDE cdrom. I'm using the device (under > Windows Vista) and when I try to mound a cdrom, I have : > > %MOUNT-I-WRITELOCK, volume is write locked > > and the system is freezed. > On the DOS console the counter still runs, but nothing happens, and I > don't have error messages. > > Yesterday, before the latest patch, I had the same problem, but on the > DOS console I had these error messages (looping on the console): > > CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > ff-ff-ff-ff-ff-ff .. > src: 00-19-3e-36-70-1b > CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > ff-ff-ff-ff-ff-ff .. > src: 00-19-3e-36-70-1b > CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > ff-ff-ff-ff-ff-ff .. > src: 00-19-3e-36-70-1b > CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > ff-ff-ff-ff-ff-ff .. > src: 00-19-3e-36-70-1b > CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > ff-ff-ff-ff-ff-ff .. > src: 00-19-3e-36-70-1b > CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > ff-ff-ff-ff-ff-ff .. > src: 00-19-3e-36-70-1b > CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > ff-ff-ff-ff-ff-ff .. > src: 00-19-3e-36-70-1b > > the only thing to do is CTRL-C, and when I do it the quit procedure > doesn't complete, stopping at > > Freeing memory in use by system... > cpu0 > > pressing again CTRL-C, the emulator quits. > > regards, > fausto > > > > Quoting Camiel Vanderhoeven <iam...@gm...>: > > > Hello Everyone, > > > > I've committed a couple of large patches today and yesterday to > > improve both multithreading and exception handling. This results in > > restoration of the functionality of the <break> menu on the serial > > ports. After these changes, I've run all code through a source code > > formatter to make the coding style a bit more consistent. I'd like you > > to check out the new code, and let me know if there are aspects of the > > source formatting that you don't like. I'm hoping this will improve > > readibility of the source code, and will help to develop a set of > > guidelines for coding style. > > > > Thanks! > > > > Camiel. > > > > P.S. I've tagged the repository before committing the re-formatted > > code; if anything has gone horribly wrong, we can revert... > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Microsoft > > Defy all challenges. Microsoft(R) Visual Studio 2008. > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > _______________________________________________ > > Es40-developers mailing list > > Es4...@li... > > https://lists.sourceforge.net/lists/listinfo/es40-developers > > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Es40-developers mailing list > Es4...@li... > https://lists.sourceforge.net/lists/listinfo/es40-developers > |
|
From: Fausto S. <fa...@un...> - 2008-03-14 19:23:54
|
Hello Camiel,
I defined the two macros, but now I have (looping on the console):
UNLOCK mutex cpu-locking-lock from thread cpu0.
UNLOCKED mutex cpu-locking-lock from thread cpu0.
LOCK mutex gui-lock from thread kbd.
LOCKED mutex gui-lock from thread kbd.
UNLOCK mutex gui-lock from thread kbd.
UNLOCKED mutex gui-lock from thread kbd.
LOCK mutex cpu-locking-lock from thread cpu0.
LOCKED mutex cpu-locking-lock from thread cpu0.
UNLOCK mutex cpu-locking-lock from thread cpu0.
UNLOCKED mutex cpu-locking-lock from thread cpu0.
LOCK mutex cpu-locking-lock from thread cpu0.
LOCKED mutex cpu-locking-lock from thread cpu0.
UNLOCK mutex cpu-locking-lock from thread cpu0.
UNLOCKED mutex cpu-locking-lock from thread cpu0.
LOCK mutex gui-lock from thread cirrus.
LOCKED mutex gui-lock from thread cirrus.
UNLOCK mutex gui-lock from thread cirrus.
UNLOCKED mutex gui-lock from thread cirrus.
LOCK mutex cpu-locking-lock from thread cpu0.
LOCKED mutex cpu-locking-lock from thread cpu0.
UNLOCK mutex cpu-locking-lock from thread cpu0.
UNLOCKED mutex cpu-locking-lock from thread cpu0.
LOCK mutex cpu-locking-lock from thread cpu0.
and no BIOS info are displayed... is it normal? is the initialization slower?
It's very strange...
regards,
fausto
Quoting Camiel Vanderhoeven <iam...@gm...>:
> Hello Fausto,
>
> A frozen system in this case probably means that the CPU is trying to
> acquire a lock that is held by the IDE device. Could you try to
> compile the code with HIDE_COUNTER and DEBUG_LOCKS defined to confirm
> that this is the case?
>
> Thanks,
>
> Camiel.
>
> On Fri, Mar 14, 2008 at 8:04 PM, Fausto Saporito <fa...@un...> wrote:
>> Hello Camiel,
>>
>> I just updated the cvs, and the build is fine.
>> But I have a new issue with IDE cdrom. I'm using the device (under
>> Windows Vista) and when I try to mound a cdrom, I have :
>>
>> %MOUNT-I-WRITELOCK, volume is write locked
>>
>> and the system is freezed.
>> On the DOS console the counter still runs, but nothing happens, and I
>> don't have error messages.
>>
>> Yesterday, before the latest patch, I had the same problem, but on the
>> DOS console I had these error messages (looping on the console):
>>
>> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst:
>> ff-ff-ff-ff-ff-ff ..
>> src: 00-19-3e-36-70-1b
>> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst:
>> ff-ff-ff-ff-ff-ff ..
>> src: 00-19-3e-36-70-1b
>> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst:
>> ff-ff-ff-ff-ff-ff ..
>> src: 00-19-3e-36-70-1b
>> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst:
>> ff-ff-ff-ff-ff-ff ..
>> src: 00-19-3e-36-70-1b
>> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst:
>> ff-ff-ff-ff-ff-ff ..
>> src: 00-19-3e-36-70-1b
>> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst:
>> ff-ff-ff-ff-ff-ff ..
>> src: 00-19-3e-36-70-1b
>> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst:
>> ff-ff-ff-ff-ff-ff ..
>> src: 00-19-3e-36-70-1b
>>
>> the only thing to do is CTRL-C, and when I do it the quit procedure
>> doesn't complete, stopping at
>>
>> Freeing memory in use by system...
>> cpu0
>>
>> pressing again CTRL-C, the emulator quits.
>>
>> regards,
>> fausto
>>
>>
>>
>> Quoting Camiel Vanderhoeven <iam...@gm...>:
>>
>> > Hello Everyone,
>> >
>> > I've committed a couple of large patches today and yesterday to
>> > improve both multithreading and exception handling. This results in
>> > restoration of the functionality of the <break> menu on the serial
>> > ports. After these changes, I've run all code through a source code
>> > formatter to make the coding style a bit more consistent. I'd like you
>> > to check out the new code, and let me know if there are aspects of the
>> > source formatting that you don't like. I'm hoping this will improve
>> > readibility of the source code, and will help to develop a set of
>> > guidelines for coding style.
>> >
>> > Thanks!
>> >
>> > Camiel.
>> >
>> > P.S. I've tagged the repository before committing the re-formatted
>> > code; if anything has gone horribly wrong, we can revert...
>> >
>> > -------------------------------------------------------------------------
>> > This SF.net email is sponsored by: Microsoft
>> > Defy all challenges. Microsoft(R) Visual Studio 2008.
>> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>> > _______________________________________________
>> > Es40-developers mailing list
>> > Es4...@li...
>> > https://lists.sourceforge.net/lists/listinfo/es40-developers
>> >
>>
>>
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Microsoft
>> Defy all challenges. Microsoft(R) Visual Studio 2008.
>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>> _______________________________________________
>> Es40-developers mailing list
>> Es4...@li...
>> https://lists.sourceforge.net/lists/listinfo/es40-developers
>>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Es40-developers mailing list
> Es4...@li...
> https://lists.sourceforge.net/lists/listinfo/es40-developers
>
|
|
From: Camiel V. <iam...@gm...> - 2008-03-14 19:25:02
|
To help track down locking-issues, I've added a standard 2-second timeout on simple mutex locking operations. I feel that no thread should ever have to wait more than a few milliseconds to acquire a lock, so 2 seconds should be safe. Whenever one of the threads runs into a lock that's being held for more than two seconds, it will fail with an error message. That said, unfortunately this won't help with the IDE device's locks, as these are read/write locks, rather than simple mutexes. I'll see if I can do this for those locks as well. Camiel. On Fri, Mar 14, 2008 at 8:11 PM, Camiel Vanderhoeven <iam...@gm...> wrote: > Hello Fausto, > > A frozen system in this case probably means that the CPU is trying to > acquire a lock that is held by the IDE device. Could you try to > compile the code with HIDE_COUNTER and DEBUG_LOCKS defined to confirm > that this is the case? > > Thanks, > > Camiel. > > > > On Fri, Mar 14, 2008 at 8:04 PM, Fausto Saporito <fa...@un...> wrote: > > Hello Camiel, > > > > I just updated the cvs, and the build is fine. > > But I have a new issue with IDE cdrom. I'm using the device (under > > Windows Vista) and when I try to mound a cdrom, I have : > > > > %MOUNT-I-WRITELOCK, volume is write locked > > > > and the system is freezed. > > On the DOS console the counter still runs, but nothing happens, and I > > don't have error messages. > > > > Yesterday, before the latest patch, I had the same problem, but on the > > DOS console I had these error messages (looping on the console): > > > > CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > > ff-ff-ff-ff-ff-ff .. > > src: 00-19-3e-36-70-1b > > CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > > ff-ff-ff-ff-ff-ff .. > > src: 00-19-3e-36-70-1b > > CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > > ff-ff-ff-ff-ff-ff .. > > src: 00-19-3e-36-70-1b > > CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > > ff-ff-ff-ff-ff-ff .. > > src: 00-19-3e-36-70-1b > > CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > > ff-ff-ff-ff-ff-ff .. > > src: 00-19-3e-36-70-1b > > CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > > ff-ff-ff-ff-ff-ff .. > > src: 00-19-3e-36-70-1b > > CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > > ff-ff-ff-ff-ff-ff .. > > src: 00-19-3e-36-70-1b > > > > the only thing to do is CTRL-C, and when I do it the quit procedure > > doesn't complete, stopping at > > > > Freeing memory in use by system... > > cpu0 > > > > pressing again CTRL-C, the emulator quits. > > > > regards, > > fausto > > > > > > > > Quoting Camiel Vanderhoeven <iam...@gm...>: > > > > > Hello Everyone, > > > > > > I've committed a couple of large patches today and yesterday to > > > improve both multithreading and exception handling. This results in > > > restoration of the functionality of the <break> menu on the serial > > > ports. After these changes, I've run all code through a source code > > > formatter to make the coding style a bit more consistent. I'd like you > > > to check out the new code, and let me know if there are aspects of the > > > source formatting that you don't like. I'm hoping this will improve > > > readibility of the source code, and will help to develop a set of > > > guidelines for coding style. > > > > > > Thanks! > > > > > > Camiel. > > > > > > P.S. I've tagged the repository before committing the re-formatted > > > code; if anything has gone horribly wrong, we can revert... > > > > > > ------------------------------------------------------------------------- > > > This SF.net email is sponsored by: Microsoft > > > Defy all challenges. Microsoft(R) Visual Studio 2008. > > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > > _______________________________________________ > > > Es40-developers mailing list > > > Es4...@li... > > > https://lists.sourceforge.net/lists/listinfo/es40-developers > > > > > > > > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Microsoft > > Defy all challenges. Microsoft(R) Visual Studio 2008. > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > _______________________________________________ > > Es40-developers mailing list > > Es4...@li... > > https://lists.sourceforge.net/lists/listinfo/es40-developers > > > |
|
From: Camiel V. <iam...@gm...> - 2008-03-14 20:25:23
|
I've now also added a 2-second timeout to the read/write mutex locks. I can reproduce the IDE CD-ROM issue, and now get the following output: Exception in CPU thread: Threading error: Locking error (Timeout: ..\Lock.h, line 563) trying to read-lock mutex ide0-registers from thread cpu0: ..\Lock.h, line 569. Emulator Failure: Threading error: CPU thread has died: ..\AlphaCPU.cpp, line 498 So this confirms my suspicions... Brian, could you take a look at this? Camiel. On Fri, Mar 14, 2008 at 8:24 PM, Camiel Vanderhoeven <iam...@gm...> wrote: > To help track down locking-issues, I've added a standard 2-second > timeout on simple mutex locking operations. I feel that no thread > should ever have to wait more than a few milliseconds to acquire a > lock, so 2 seconds should be safe. Whenever one of the threads runs > into a lock that's being held for more than two seconds, it will fail > with an error message. > > That said, unfortunately this won't help with the IDE device's locks, > as these are read/write locks, rather than simple mutexes. I'll see if > I can do this for those locks as well. > > Camiel. > > > > > On Fri, Mar 14, 2008 at 8:11 PM, Camiel Vanderhoeven > <iam...@gm...> wrote: > > Hello Fausto, > > > > A frozen system in this case probably means that the CPU is trying to > > acquire a lock that is held by the IDE device. Could you try to > > compile the code with HIDE_COUNTER and DEBUG_LOCKS defined to confirm > > that this is the case? > > > > Thanks, > > > > Camiel. > > > > > > > > On Fri, Mar 14, 2008 at 8:04 PM, Fausto Saporito <fa...@un...> wrote: > > > Hello Camiel, > > > > > > I just updated the cvs, and the build is fine. > > > But I have a new issue with IDE cdrom. I'm using the device (under > > > Windows Vista) and when I try to mound a cdrom, I have : > > > > > > %MOUNT-I-WRITELOCK, volume is write locked > > > > > > and the system is freezed. > > > On the DOS console the counter still runs, but nothing happens, and I > > > don't have error messages. > > > > > > Yesterday, before the latest patch, I had the same problem, but on the > > > DOS console I had these error messages (looping on the console): > > > > > > CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > > > ff-ff-ff-ff-ff-ff .. > > > src: 00-19-3e-36-70-1b > > > CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > > > ff-ff-ff-ff-ff-ff .. > > > src: 00-19-3e-36-70-1b > > > CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > > > ff-ff-ff-ff-ff-ff .. > > > src: 00-19-3e-36-70-1b > > > CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > > > ff-ff-ff-ff-ff-ff .. > > > src: 00-19-3e-36-70-1b > > > CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > > > ff-ff-ff-ff-ff-ff .. > > > src: 00-19-3e-36-70-1b > > > CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > > > ff-ff-ff-ff-ff-ff .. > > > src: 00-19-3e-36-70-1b > > > CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > > > ff-ff-ff-ff-ff-ff .. > > > src: 00-19-3e-36-70-1b > > > > > > the only thing to do is CTRL-C, and when I do it the quit procedure > > > doesn't complete, stopping at > > > > > > Freeing memory in use by system... > > > cpu0 > > > > > > pressing again CTRL-C, the emulator quits. > > > > > > regards, > > > fausto > > > > > > > > > > > > Quoting Camiel Vanderhoeven <iam...@gm...>: > > > > > > > Hello Everyone, > > > > > > > > I've committed a couple of large patches today and yesterday to > > > > improve both multithreading and exception handling. This results in > > > > restoration of the functionality of the <break> menu on the serial > > > > ports. After these changes, I've run all code through a source code > > > > formatter to make the coding style a bit more consistent. I'd like you > > > > to check out the new code, and let me know if there are aspects of the > > > > source formatting that you don't like. I'm hoping this will improve > > > > readibility of the source code, and will help to develop a set of > > > > guidelines for coding style. > > > > > > > > Thanks! > > > > > > > > Camiel. > > > > > > > > P.S. I've tagged the repository before committing the re-formatted > > > > code; if anything has gone horribly wrong, we can revert... > > > > > > > > ------------------------------------------------------------------------- > > > > This SF.net email is sponsored by: Microsoft > > > > Defy all challenges. Microsoft(R) Visual Studio 2008. > > > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > > > _______________________________________________ > > > > Es40-developers mailing list > > > > Es4...@li... > > > > https://lists.sourceforge.net/lists/listinfo/es40-developers > > > > > > > > > > > > > > > > ------------------------------------------------------------------------- > > > This SF.net email is sponsored by: Microsoft > > > Defy all challenges. Microsoft(R) Visual Studio 2008. > > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > > _______________________________________________ > > > Es40-developers mailing list > > > Es4...@li... > > > https://lists.sourceforge.net/lists/listinfo/es40-developers > > > > > > |
|
From: Camiel V. <iam...@gm...> - 2008-03-14 19:26:56
|
Hi Fausto, This adds a lot of extra debugging info, so it will be a bit slower. If I remember correctly, you're on Linux; you could try doing es40 | grep ide to minimize the output. On Fri, Mar 14, 2008 at 8:23 PM, Fausto Saporito <fa...@un...> wrote: > Hello Camiel, > > I defined the two macros, but now I have (looping on the console): > > UNLOCK mutex cpu-locking-lock from thread cpu0. > UNLOCKED mutex cpu-locking-lock from thread cpu0. > LOCK mutex gui-lock from thread kbd. > LOCKED mutex gui-lock from thread kbd. > UNLOCK mutex gui-lock from thread kbd. > UNLOCKED mutex gui-lock from thread kbd. > LOCK mutex cpu-locking-lock from thread cpu0. > LOCKED mutex cpu-locking-lock from thread cpu0. > UNLOCK mutex cpu-locking-lock from thread cpu0. > UNLOCKED mutex cpu-locking-lock from thread cpu0. > LOCK mutex cpu-locking-lock from thread cpu0. > LOCKED mutex cpu-locking-lock from thread cpu0. > UNLOCK mutex cpu-locking-lock from thread cpu0. > UNLOCKED mutex cpu-locking-lock from thread cpu0. > LOCK mutex gui-lock from thread cirrus. > LOCKED mutex gui-lock from thread cirrus. > UNLOCK mutex gui-lock from thread cirrus. > UNLOCKED mutex gui-lock from thread cirrus. > LOCK mutex cpu-locking-lock from thread cpu0. > LOCKED mutex cpu-locking-lock from thread cpu0. > UNLOCK mutex cpu-locking-lock from thread cpu0. > UNLOCKED mutex cpu-locking-lock from thread cpu0. > LOCK mutex cpu-locking-lock from thread cpu0. > > and no BIOS info are displayed... is it normal? is the initialization slower? > > It's very strange... > > > > regards, > fausto > > Quoting Camiel Vanderhoeven <iam...@gm...>: > > > Hello Fausto, > > > > A frozen system in this case probably means that the CPU is trying to > > acquire a lock that is held by the IDE device. Could you try to > > compile the code with HIDE_COUNTER and DEBUG_LOCKS defined to confirm > > that this is the case? > > > > Thanks, > > > > Camiel. > > > > On Fri, Mar 14, 2008 at 8:04 PM, Fausto Saporito <fa...@un...> wrote: > >> Hello Camiel, > >> > >> I just updated the cvs, and the build is fine. > >> But I have a new issue with IDE cdrom. I'm using the device (under > >> Windows Vista) and when I try to mound a cdrom, I have : > >> > >> %MOUNT-I-WRITELOCK, volume is write locked > >> > >> and the system is freezed. > >> On the DOS console the counter still runs, but nothing happens, and I > >> don't have error messages. > >> > >> Yesterday, before the latest patch, I had the same problem, but on the > >> DOS console I had these error messages (looping on the console): > >> > >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > >> ff-ff-ff-ff-ff-ff .. > >> src: 00-19-3e-36-70-1b > >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > >> ff-ff-ff-ff-ff-ff .. > >> src: 00-19-3e-36-70-1b > >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > >> ff-ff-ff-ff-ff-ff .. > >> src: 00-19-3e-36-70-1b > >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > >> ff-ff-ff-ff-ff-ff .. > >> src: 00-19-3e-36-70-1b > >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > >> ff-ff-ff-ff-ff-ff .. > >> src: 00-19-3e-36-70-1b > >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > >> ff-ff-ff-ff-ff-ff .. > >> src: 00-19-3e-36-70-1b > >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > >> ff-ff-ff-ff-ff-ff .. > >> src: 00-19-3e-36-70-1b > >> > >> the only thing to do is CTRL-C, and when I do it the quit procedure > >> doesn't complete, stopping at > >> > >> Freeing memory in use by system... > >> cpu0 > >> > >> pressing again CTRL-C, the emulator quits. > >> > >> regards, > >> fausto > >> > >> > >> > >> Quoting Camiel Vanderhoeven <iam...@gm...>: > >> > >> > Hello Everyone, > >> > > >> > I've committed a couple of large patches today and yesterday to > >> > improve both multithreading and exception handling. This results in > >> > restoration of the functionality of the <break> menu on the serial > >> > ports. After these changes, I've run all code through a source code > >> > formatter to make the coding style a bit more consistent. I'd like you > >> > to check out the new code, and let me know if there are aspects of the > >> > source formatting that you don't like. I'm hoping this will improve > >> > readibility of the source code, and will help to develop a set of > >> > guidelines for coding style. > >> > > >> > Thanks! > >> > > >> > Camiel. > >> > > >> > P.S. I've tagged the repository before committing the re-formatted > >> > code; if anything has gone horribly wrong, we can revert... > >> > > >> > ------------------------------------------------------------------------- > >> > This SF.net email is sponsored by: Microsoft > >> > Defy all challenges. Microsoft(R) Visual Studio 2008. > >> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > >> > _______________________________________________ > >> > Es40-developers mailing list > >> > Es4...@li... > >> > https://lists.sourceforge.net/lists/listinfo/es40-developers > >> > > >> > >> > >> > >> ------------------------------------------------------------------------- > >> This SF.net email is sponsored by: Microsoft > >> Defy all challenges. Microsoft(R) Visual Studio 2008. > >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > >> _______________________________________________ > >> Es40-developers mailing list > >> Es4...@li... > >> https://lists.sourceforge.net/lists/listinfo/es40-developers > >> > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Microsoft > > Defy all challenges. Microsoft(R) Visual Studio 2008. > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > _______________________________________________ > > Es40-developers mailing list > > Es4...@li... > > https://lists.sourceforge.net/lists/listinfo/es40-developers > > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Es40-developers mailing list > Es4...@li... > https://lists.sourceforge.net/lists/listinfo/es40-developers > |
|
From: Fausto S. <fa...@un...> - 2008-03-14 19:30:41
|
Hello Camiel, I'm actually running under Windows. But still it's looping... maybe there's something strange in the code when I defined DEBUG_LOCKS. Normally in 2 mins I have the alpha prompt... now it's 5/6 mins and always loops. regards, fausto Quoting Camiel Vanderhoeven <iam...@gm...>: > Hi Fausto, > > This adds a lot of extra debugging info, so it will be a bit slower. > If I remember correctly, you're on Linux; you could try doing > > es40 | grep ide > > to minimize the output. > > On Fri, Mar 14, 2008 at 8:23 PM, Fausto Saporito <fa...@un...> wrote: >> Hello Camiel, >> >> I defined the two macros, but now I have (looping on the console): >> >> UNLOCK mutex cpu-locking-lock from thread cpu0. >> UNLOCKED mutex cpu-locking-lock from thread cpu0. >> LOCK mutex gui-lock from thread kbd. >> LOCKED mutex gui-lock from thread kbd. >> UNLOCK mutex gui-lock from thread kbd. >> UNLOCKED mutex gui-lock from thread kbd. >> LOCK mutex cpu-locking-lock from thread cpu0. >> LOCKED mutex cpu-locking-lock from thread cpu0. >> UNLOCK mutex cpu-locking-lock from thread cpu0. >> UNLOCKED mutex cpu-locking-lock from thread cpu0. >> LOCK mutex cpu-locking-lock from thread cpu0. >> LOCKED mutex cpu-locking-lock from thread cpu0. >> UNLOCK mutex cpu-locking-lock from thread cpu0. >> UNLOCKED mutex cpu-locking-lock from thread cpu0. >> LOCK mutex gui-lock from thread cirrus. >> LOCKED mutex gui-lock from thread cirrus. >> UNLOCK mutex gui-lock from thread cirrus. >> UNLOCKED mutex gui-lock from thread cirrus. >> LOCK mutex cpu-locking-lock from thread cpu0. >> LOCKED mutex cpu-locking-lock from thread cpu0. >> UNLOCK mutex cpu-locking-lock from thread cpu0. >> UNLOCKED mutex cpu-locking-lock from thread cpu0. >> LOCK mutex cpu-locking-lock from thread cpu0. >> >> and no BIOS info are displayed... is it normal? is the >> initialization slower? >> >> It's very strange... >> >> >> >> regards, >> fausto >> >> Quoting Camiel Vanderhoeven <iam...@gm...>: >> >> > Hello Fausto, >> > >> > A frozen system in this case probably means that the CPU is trying to >> > acquire a lock that is held by the IDE device. Could you try to >> > compile the code with HIDE_COUNTER and DEBUG_LOCKS defined to confirm >> > that this is the case? >> > >> > Thanks, >> > >> > Camiel. >> > >> > On Fri, Mar 14, 2008 at 8:04 PM, Fausto Saporito <fa...@un...> wrote: >> >> Hello Camiel, >> >> >> >> I just updated the cvs, and the build is fine. >> >> But I have a new issue with IDE cdrom. I'm using the device (under >> >> Windows Vista) and when I try to mound a cdrom, I have : >> >> >> >> %MOUNT-I-WRITELOCK, volume is write locked >> >> >> >> and the system is freezed. >> >> On the DOS console the counter still runs, but nothing happens, and I >> >> don't have error messages. >> >> >> >> Yesterday, before the latest patch, I had the same problem, but on the >> >> DOS console I had these error messages (looping on the console): >> >> >> >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: >> >> ff-ff-ff-ff-ff-ff .. >> >> src: 00-19-3e-36-70-1b >> >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: >> >> ff-ff-ff-ff-ff-ff .. >> >> src: 00-19-3e-36-70-1b >> >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: >> >> ff-ff-ff-ff-ff-ff .. >> >> src: 00-19-3e-36-70-1b >> >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: >> >> ff-ff-ff-ff-ff-ff .. >> >> src: 00-19-3e-36-70-1b >> >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: >> >> ff-ff-ff-ff-ff-ff .. >> >> src: 00-19-3e-36-70-1b >> >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: >> >> ff-ff-ff-ff-ff-ff .. >> >> src: 00-19-3e-36-70-1b >> >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: >> >> ff-ff-ff-ff-ff-ff .. >> >> src: 00-19-3e-36-70-1b >> >> >> >> the only thing to do is CTRL-C, and when I do it the quit procedure >> >> doesn't complete, stopping at >> >> >> >> Freeing memory in use by system... >> >> cpu0 >> >> >> >> pressing again CTRL-C, the emulator quits. >> >> >> >> regards, >> >> fausto >> >> >> >> >> >> >> >> Quoting Camiel Vanderhoeven <iam...@gm...>: >> >> >> >> > Hello Everyone, >> >> > >> >> > I've committed a couple of large patches today and yesterday to >> >> > improve both multithreading and exception handling. This results in >> >> > restoration of the functionality of the <break> menu on the serial >> >> > ports. After these changes, I've run all code through a source code >> >> > formatter to make the coding style a bit more consistent. >> I'd like you >> >> > to check out the new code, and let me know if there are >> aspects of the >> >> > source formatting that you don't like. I'm hoping this will improve >> >> > readibility of the source code, and will help to develop a set of >> >> > guidelines for coding style. >> >> > >> >> > Thanks! >> >> > >> >> > Camiel. >> >> > >> >> > P.S. I've tagged the repository before committing the re-formatted >> >> > code; if anything has gone horribly wrong, we can revert... >> >> > >> >> > >> ------------------------------------------------------------------------- >> >> > This SF.net email is sponsored by: Microsoft >> >> > Defy all challenges. Microsoft(R) Visual Studio 2008. >> >> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> >> > _______________________________________________ >> >> > Es40-developers mailing list >> >> > Es4...@li... >> >> > https://lists.sourceforge.net/lists/listinfo/es40-developers >> >> > >> >> >> >> >> >> >> >> >> ------------------------------------------------------------------------- >> >> This SF.net email is sponsored by: Microsoft >> >> Defy all challenges. Microsoft(R) Visual Studio 2008. >> >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> >> _______________________________________________ >> >> Es40-developers mailing list >> >> Es4...@li... >> >> https://lists.sourceforge.net/lists/listinfo/es40-developers >> >> >> > >> > ------------------------------------------------------------------------- >> > This SF.net email is sponsored by: Microsoft >> > Defy all challenges. Microsoft(R) Visual Studio 2008. >> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> > _______________________________________________ >> > Es40-developers mailing list >> > Es4...@li... >> > https://lists.sourceforge.net/lists/listinfo/es40-developers >> > >> >> >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2008. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> _______________________________________________ >> Es40-developers mailing list >> Es4...@li... >> https://lists.sourceforge.net/lists/listinfo/es40-developers >> > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Es40-developers mailing list > Es4...@li... > https://lists.sourceforge.net/lists/listinfo/es40-developers > |
|
From: Camiel V. <iam...@gm...> - 2008-03-14 19:32:33
|
Hi Fausto, Could you minimize the DOS window? On my system it's faster that way. Updating the screen for output takes up a lot of time on Windows... Camiel. On Fri, Mar 14, 2008 at 8:30 PM, Fausto Saporito <fa...@un...> wrote: > Hello Camiel, > > I'm actually running under Windows. > But still it's looping... maybe there's something strange in the code > when I defined DEBUG_LOCKS. > > Normally in 2 mins I have the alpha prompt... now it's 5/6 mins and > always loops. > > > > regards, > fausto > > Quoting Camiel Vanderhoeven <iam...@gm...>: > > > Hi Fausto, > > > > This adds a lot of extra debugging info, so it will be a bit slower. > > If I remember correctly, you're on Linux; you could try doing > > > > es40 | grep ide > > > > to minimize the output. > > > > On Fri, Mar 14, 2008 at 8:23 PM, Fausto Saporito <fa...@un...> wrote: > >> Hello Camiel, > >> > >> I defined the two macros, but now I have (looping on the console): > >> > >> UNLOCK mutex cpu-locking-lock from thread cpu0. > >> UNLOCKED mutex cpu-locking-lock from thread cpu0. > >> LOCK mutex gui-lock from thread kbd. > >> LOCKED mutex gui-lock from thread kbd. > >> UNLOCK mutex gui-lock from thread kbd. > >> UNLOCKED mutex gui-lock from thread kbd. > >> LOCK mutex cpu-locking-lock from thread cpu0. > >> LOCKED mutex cpu-locking-lock from thread cpu0. > >> UNLOCK mutex cpu-locking-lock from thread cpu0. > >> UNLOCKED mutex cpu-locking-lock from thread cpu0. > >> LOCK mutex cpu-locking-lock from thread cpu0. > >> LOCKED mutex cpu-locking-lock from thread cpu0. > >> UNLOCK mutex cpu-locking-lock from thread cpu0. > >> UNLOCKED mutex cpu-locking-lock from thread cpu0. > >> LOCK mutex gui-lock from thread cirrus. > >> LOCKED mutex gui-lock from thread cirrus. > >> UNLOCK mutex gui-lock from thread cirrus. > >> UNLOCKED mutex gui-lock from thread cirrus. > >> LOCK mutex cpu-locking-lock from thread cpu0. > >> LOCKED mutex cpu-locking-lock from thread cpu0. > >> UNLOCK mutex cpu-locking-lock from thread cpu0. > >> UNLOCKED mutex cpu-locking-lock from thread cpu0. > >> LOCK mutex cpu-locking-lock from thread cpu0. > >> > >> and no BIOS info are displayed... is it normal? is the > >> initialization slower? > >> > >> It's very strange... > >> > >> > >> > >> regards, > >> fausto > >> > >> Quoting Camiel Vanderhoeven <iam...@gm...>: > >> > >> > Hello Fausto, > >> > > >> > A frozen system in this case probably means that the CPU is trying to > >> > acquire a lock that is held by the IDE device. Could you try to > >> > compile the code with HIDE_COUNTER and DEBUG_LOCKS defined to confirm > >> > that this is the case? > >> > > >> > Thanks, > >> > > >> > Camiel. > >> > > >> > On Fri, Mar 14, 2008 at 8:04 PM, Fausto Saporito <fa...@un...> wrote: > >> >> Hello Camiel, > >> >> > >> >> I just updated the cvs, and the build is fine. > >> >> But I have a new issue with IDE cdrom. I'm using the device (under > >> >> Windows Vista) and when I try to mound a cdrom, I have : > >> >> > >> >> %MOUNT-I-WRITELOCK, volume is write locked > >> >> > >> >> and the system is freezed. > >> >> On the DOS console the counter still runs, but nothing happens, and I > >> >> don't have error messages. > >> >> > >> >> Yesterday, before the latest patch, I had the same problem, but on the > >> >> DOS console I had these error messages (looping on the console): > >> >> > >> >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > >> >> ff-ff-ff-ff-ff-ff .. > >> >> src: 00-19-3e-36-70-1b > >> >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > >> >> ff-ff-ff-ff-ff-ff .. > >> >> src: 00-19-3e-36-70-1b > >> >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > >> >> ff-ff-ff-ff-ff-ff .. > >> >> src: 00-19-3e-36-70-1b > >> >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > >> >> ff-ff-ff-ff-ff-ff .. > >> >> src: 00-19-3e-36-70-1b > >> >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > >> >> ff-ff-ff-ff-ff-ff .. > >> >> src: 00-19-3e-36-70-1b > >> >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > >> >> ff-ff-ff-ff-ff-ff .. > >> >> src: 00-19-3e-36-70-1b > >> >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > >> >> ff-ff-ff-ff-ff-ff .. > >> >> src: 00-19-3e-36-70-1b > >> >> > >> >> the only thing to do is CTRL-C, and when I do it the quit procedure > >> >> doesn't complete, stopping at > >> >> > >> >> Freeing memory in use by system... > >> >> cpu0 > >> >> > >> >> pressing again CTRL-C, the emulator quits. > >> >> > >> >> regards, > >> >> fausto > >> >> > >> >> > >> >> > >> >> Quoting Camiel Vanderhoeven <iam...@gm...>: > >> >> > >> >> > Hello Everyone, > >> >> > > >> >> > I've committed a couple of large patches today and yesterday to > >> >> > improve both multithreading and exception handling. This results in > >> >> > restoration of the functionality of the <break> menu on the serial > >> >> > ports. After these changes, I've run all code through a source code > >> >> > formatter to make the coding style a bit more consistent. > >> I'd like you > >> >> > to check out the new code, and let me know if there are > >> aspects of the > >> >> > source formatting that you don't like. I'm hoping this will improve > >> >> > readibility of the source code, and will help to develop a set of > >> >> > guidelines for coding style. > >> >> > > >> >> > Thanks! > >> >> > > >> >> > Camiel. > >> >> > > >> >> > P.S. I've tagged the repository before committing the re-formatted > >> >> > code; if anything has gone horribly wrong, we can revert... > >> >> > > >> >> > > >> ------------------------------------------------------------------------- > >> >> > This SF.net email is sponsored by: Microsoft > >> >> > Defy all challenges. Microsoft(R) Visual Studio 2008. > >> >> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > >> >> > _______________________________________________ > >> >> > Es40-developers mailing list > >> >> > Es4...@li... > >> >> > https://lists.sourceforge.net/lists/listinfo/es40-developers > >> >> > > >> >> > >> >> > >> >> > >> >> > >> ------------------------------------------------------------------------- > >> >> This SF.net email is sponsored by: Microsoft > >> >> Defy all challenges. Microsoft(R) Visual Studio 2008. > >> >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > >> >> _______________________________________________ > >> >> Es40-developers mailing list > >> >> Es4...@li... > >> >> https://lists.sourceforge.net/lists/listinfo/es40-developers > >> >> > >> > > >> > ------------------------------------------------------------------------- > >> > This SF.net email is sponsored by: Microsoft > >> > Defy all challenges. Microsoft(R) Visual Studio 2008. > >> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > >> > _______________________________________________ > >> > Es40-developers mailing list > >> > Es4...@li... > >> > https://lists.sourceforge.net/lists/listinfo/es40-developers > >> > > >> > >> > >> > >> ------------------------------------------------------------------------- > >> This SF.net email is sponsored by: Microsoft > >> Defy all challenges. Microsoft(R) Visual Studio 2008. > >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > >> _______________________________________________ > >> Es40-developers mailing list > >> Es4...@li... > >> https://lists.sourceforge.net/lists/listinfo/es40-developers > >> > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Microsoft > > Defy all challenges. Microsoft(R) Visual Studio 2008. > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > _______________________________________________ > > Es40-developers mailing list > > Es4...@li... > > https://lists.sourceforge.net/lists/listinfo/es40-developers > > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Es40-developers mailing list > Es4...@li... > https://lists.sourceforge.net/lists/listinfo/es40-developers > |
|
From: Fausto S. <fa...@un...> - 2008-03-14 19:34:58
|
it seems quite ok... one char each 2 seconds :-) I think the startup will take 30/40 mins... later, fausto Quoting Camiel Vanderhoeven <iam...@gm...>: > Hi Fausto, > > Could you minimize the DOS window? On my system it's faster that way. > > Updating the screen for output takes up a lot of time on Windows... > > Camiel. > > On Fri, Mar 14, 2008 at 8:30 PM, Fausto Saporito <fa...@un...> wrote: >> Hello Camiel, >> >> I'm actually running under Windows. >> But still it's looping... maybe there's something strange in the code >> when I defined DEBUG_LOCKS. >> >> Normally in 2 mins I have the alpha prompt... now it's 5/6 mins and >> always loops. >> >> >> >> regards, >> fausto >> >> Quoting Camiel Vanderhoeven <iam...@gm...>: >> >> > Hi Fausto, >> > >> > This adds a lot of extra debugging info, so it will be a bit slower. >> > If I remember correctly, you're on Linux; you could try doing >> > >> > es40 | grep ide >> > >> > to minimize the output. >> > >> > On Fri, Mar 14, 2008 at 8:23 PM, Fausto Saporito <fa...@un...> wrote: >> >> Hello Camiel, >> >> >> >> I defined the two macros, but now I have (looping on the console): >> >> >> >> UNLOCK mutex cpu-locking-lock from thread cpu0. >> >> UNLOCKED mutex cpu-locking-lock from thread cpu0. >> >> LOCK mutex gui-lock from thread kbd. >> >> LOCKED mutex gui-lock from thread kbd. >> >> UNLOCK mutex gui-lock from thread kbd. >> >> UNLOCKED mutex gui-lock from thread kbd. >> >> LOCK mutex cpu-locking-lock from thread cpu0. >> >> LOCKED mutex cpu-locking-lock from thread cpu0. >> >> UNLOCK mutex cpu-locking-lock from thread cpu0. >> >> UNLOCKED mutex cpu-locking-lock from thread cpu0. >> >> LOCK mutex cpu-locking-lock from thread cpu0. >> >> LOCKED mutex cpu-locking-lock from thread cpu0. >> >> UNLOCK mutex cpu-locking-lock from thread cpu0. >> >> UNLOCKED mutex cpu-locking-lock from thread cpu0. >> >> LOCK mutex gui-lock from thread cirrus. >> >> LOCKED mutex gui-lock from thread cirrus. >> >> UNLOCK mutex gui-lock from thread cirrus. >> >> UNLOCKED mutex gui-lock from thread cirrus. >> >> LOCK mutex cpu-locking-lock from thread cpu0. >> >> LOCKED mutex cpu-locking-lock from thread cpu0. >> >> UNLOCK mutex cpu-locking-lock from thread cpu0. >> >> UNLOCKED mutex cpu-locking-lock from thread cpu0. >> >> LOCK mutex cpu-locking-lock from thread cpu0. >> >> >> >> and no BIOS info are displayed... is it normal? is the >> >> initialization slower? >> >> >> >> It's very strange... >> >> >> >> >> >> >> >> regards, >> >> fausto >> >> >> >> Quoting Camiel Vanderhoeven <iam...@gm...>: >> >> >> >> > Hello Fausto, >> >> > >> >> > A frozen system in this case probably means that the CPU is trying to >> >> > acquire a lock that is held by the IDE device. Could you try to >> >> > compile the code with HIDE_COUNTER and DEBUG_LOCKS defined to confirm >> >> > that this is the case? >> >> > >> >> > Thanks, >> >> > >> >> > Camiel. >> >> > >> >> > On Fri, Mar 14, 2008 at 8:04 PM, Fausto Saporito >> <fa...@un...> wrote: >> >> >> Hello Camiel, >> >> >> >> >> >> I just updated the cvs, and the build is fine. >> >> >> But I have a new issue with IDE cdrom. I'm using the device (under >> >> >> Windows Vista) and when I try to mound a cdrom, I have : >> >> >> >> >> >> %MOUNT-I-WRITELOCK, volume is write locked >> >> >> >> >> >> and the system is freezed. >> >> >> On the DOS console the counter still runs, but nothing >> happens, and I >> >> >> don't have error messages. >> >> >> >> >> >> Yesterday, before the latest patch, I had the same >> problem, but on the >> >> >> DOS console I had these error messages (looping on the console): >> >> >> >> >> >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: >> >> >> ff-ff-ff-ff-ff-ff .. >> >> >> src: 00-19-3e-36-70-1b >> >> >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: >> >> >> ff-ff-ff-ff-ff-ff .. >> >> >> src: 00-19-3e-36-70-1b >> >> >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: >> >> >> ff-ff-ff-ff-ff-ff .. >> >> >> src: 00-19-3e-36-70-1b >> >> >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: >> >> >> ff-ff-ff-ff-ff-ff .. >> >> >> src: 00-19-3e-36-70-1b >> >> >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: >> >> >> ff-ff-ff-ff-ff-ff .. >> >> >> src: 00-19-3e-36-70-1b >> >> >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: >> >> >> ff-ff-ff-ff-ff-ff .. >> >> >> src: 00-19-3e-36-70-1b >> >> >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: >> >> >> ff-ff-ff-ff-ff-ff .. >> >> >> src: 00-19-3e-36-70-1b >> >> >> >> >> >> the only thing to do is CTRL-C, and when I do it the quit procedure >> >> >> doesn't complete, stopping at >> >> >> >> >> >> Freeing memory in use by system... >> >> >> cpu0 >> >> >> >> >> >> pressing again CTRL-C, the emulator quits. >> >> >> >> >> >> regards, >> >> >> fausto >> >> >> >> >> >> >> >> >> >> >> >> Quoting Camiel Vanderhoeven <iam...@gm...>: >> >> >> >> >> >> > Hello Everyone, >> >> >> > >> >> >> > I've committed a couple of large patches today and yesterday to >> >> >> > improve both multithreading and exception handling. This >> results in >> >> >> > restoration of the functionality of the <break> menu on >> the serial >> >> >> > ports. After these changes, I've run all code through a >> source code >> >> >> > formatter to make the coding style a bit more consistent. >> >> I'd like you >> >> >> > to check out the new code, and let me know if there are >> >> aspects of the >> >> >> > source formatting that you don't like. I'm hoping this >> will improve >> >> >> > readibility of the source code, and will help to develop a set of >> >> >> > guidelines for coding style. >> >> >> > >> >> >> > Thanks! >> >> >> > >> >> >> > Camiel. >> >> >> > >> >> >> > P.S. I've tagged the repository before committing the >> re-formatted >> >> >> > code; if anything has gone horribly wrong, we can revert... >> >> >> > >> >> >> > >> >> >> ------------------------------------------------------------------------- >> >> >> > This SF.net email is sponsored by: Microsoft >> >> >> > Defy all challenges. Microsoft(R) Visual Studio 2008. >> >> >> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> >> >> > _______________________________________________ >> >> >> > Es40-developers mailing list >> >> >> > Es4...@li... >> >> >> > https://lists.sourceforge.net/lists/listinfo/es40-developers >> >> >> > >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> ------------------------------------------------------------------------- >> >> >> This SF.net email is sponsored by: Microsoft >> >> >> Defy all challenges. Microsoft(R) Visual Studio 2008. >> >> >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> >> >> _______________________________________________ >> >> >> Es40-developers mailing list >> >> >> Es4...@li... >> >> >> https://lists.sourceforge.net/lists/listinfo/es40-developers >> >> >> >> >> > >> >> > >> ------------------------------------------------------------------------- >> >> > This SF.net email is sponsored by: Microsoft >> >> > Defy all challenges. Microsoft(R) Visual Studio 2008. >> >> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> >> > _______________________________________________ >> >> > Es40-developers mailing list >> >> > Es4...@li... >> >> > https://lists.sourceforge.net/lists/listinfo/es40-developers >> >> > >> >> >> >> >> >> >> >> >> ------------------------------------------------------------------------- >> >> This SF.net email is sponsored by: Microsoft >> >> Defy all challenges. Microsoft(R) Visual Studio 2008. >> >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> >> _______________________________________________ >> >> Es40-developers mailing list >> >> Es4...@li... >> >> https://lists.sourceforge.net/lists/listinfo/es40-developers >> >> >> > >> > ------------------------------------------------------------------------- >> > This SF.net email is sponsored by: Microsoft >> > Defy all challenges. Microsoft(R) Visual Studio 2008. >> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> > _______________________________________________ >> > Es40-developers mailing list >> > Es4...@li... >> > https://lists.sourceforge.net/lists/listinfo/es40-developers >> > >> >> >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2008. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> _______________________________________________ >> Es40-developers mailing list >> Es4...@li... >> https://lists.sourceforge.net/lists/listinfo/es40-developers >> > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Es40-developers mailing list > Es4...@li... > https://lists.sourceforge.net/lists/listinfo/es40-developers > |
|
From: Camiel V. <iam...@gm...> - 2008-03-14 19:43:52
|
You could try the following: Start the emulator compiled without DEBUG_LOCKS; wait until OpenVMS is fully booted and you're logged in and looking at the DCL prompt. Then send a <break> character on one of the serial ports (in Putty, menu->special Command->Break), and choose option 3 (Save state). Terminate the emulator. Next, start the emulator compiled with DEBUG_LOCKS, send the <break> character again, and choose option 4 (Restore state). An <enter> should bring you back to the DCL prompt. (This doesn't always work; saving the state is a bit tricky, especially for the VGA card, but if it works, it's a big time-saver for debugging) It's probably wise to run the emulator with as minimal a configuration as possible to reproduce the bug, removing the VGA card from the system is almost always a good idea, unless the OS you're running on the emulator requires it. Camiel. On Fri, Mar 14, 2008 at 8:34 PM, Fausto Saporito <fa...@un...> wrote: > it seems quite ok... one char each 2 seconds :-) > I think the startup will take 30/40 mins... > > later, > > > fausto > > Quoting Camiel Vanderhoeven <iam...@gm...>: > > > Hi Fausto, > > > > Could you minimize the DOS window? On my system it's faster that way. > > > > Updating the screen for output takes up a lot of time on Windows... > > > > Camiel. > > > > On Fri, Mar 14, 2008 at 8:30 PM, Fausto Saporito <fa...@un...> wrote: > >> Hello Camiel, > >> > >> I'm actually running under Windows. > >> But still it's looping... maybe there's something strange in the code > >> when I defined DEBUG_LOCKS. > >> > >> Normally in 2 mins I have the alpha prompt... now it's 5/6 mins and > >> always loops. > >> > >> > >> > >> regards, > >> fausto > >> > >> Quoting Camiel Vanderhoeven <iam...@gm...>: > >> > >> > Hi Fausto, > >> > > >> > This adds a lot of extra debugging info, so it will be a bit slower. > >> > If I remember correctly, you're on Linux; you could try doing > >> > > >> > es40 | grep ide > >> > > >> > to minimize the output. > >> > > >> > On Fri, Mar 14, 2008 at 8:23 PM, Fausto Saporito <fa...@un...> wrote: > >> >> Hello Camiel, > >> >> > >> >> I defined the two macros, but now I have (looping on the console): > >> >> > >> >> UNLOCK mutex cpu-locking-lock from thread cpu0. > >> >> UNLOCKED mutex cpu-locking-lock from thread cpu0. > >> >> LOCK mutex gui-lock from thread kbd. > >> >> LOCKED mutex gui-lock from thread kbd. > >> >> UNLOCK mutex gui-lock from thread kbd. > >> >> UNLOCKED mutex gui-lock from thread kbd. > >> >> LOCK mutex cpu-locking-lock from thread cpu0. > >> >> LOCKED mutex cpu-locking-lock from thread cpu0. > >> >> UNLOCK mutex cpu-locking-lock from thread cpu0. > >> >> UNLOCKED mutex cpu-locking-lock from thread cpu0. > >> >> LOCK mutex cpu-locking-lock from thread cpu0. > >> >> LOCKED mutex cpu-locking-lock from thread cpu0. > >> >> UNLOCK mutex cpu-locking-lock from thread cpu0. > >> >> UNLOCKED mutex cpu-locking-lock from thread cpu0. > >> >> LOCK mutex gui-lock from thread cirrus. > >> >> LOCKED mutex gui-lock from thread cirrus. > >> >> UNLOCK mutex gui-lock from thread cirrus. > >> >> UNLOCKED mutex gui-lock from thread cirrus. > >> >> LOCK mutex cpu-locking-lock from thread cpu0. > >> >> LOCKED mutex cpu-locking-lock from thread cpu0. > >> >> UNLOCK mutex cpu-locking-lock from thread cpu0. > >> >> UNLOCKED mutex cpu-locking-lock from thread cpu0. > >> >> LOCK mutex cpu-locking-lock from thread cpu0. > >> >> > >> >> and no BIOS info are displayed... is it normal? is the > >> >> initialization slower? > >> >> > >> >> It's very strange... > >> >> > >> >> > >> >> > >> >> regards, > >> >> fausto > >> >> > >> >> Quoting Camiel Vanderhoeven <iam...@gm...>: > >> >> > >> >> > Hello Fausto, > >> >> > > >> >> > A frozen system in this case probably means that the CPU is trying to > >> >> > acquire a lock that is held by the IDE device. Could you try to > >> >> > compile the code with HIDE_COUNTER and DEBUG_LOCKS defined to confirm > >> >> > that this is the case? > >> >> > > >> >> > Thanks, > >> >> > > >> >> > Camiel. > >> >> > > >> >> > On Fri, Mar 14, 2008 at 8:04 PM, Fausto Saporito > >> <fa...@un...> wrote: > >> >> >> Hello Camiel, > >> >> >> > >> >> >> I just updated the cvs, and the build is fine. > >> >> >> But I have a new issue with IDE cdrom. I'm using the device (under > >> >> >> Windows Vista) and when I try to mound a cdrom, I have : > >> >> >> > >> >> >> %MOUNT-I-WRITELOCK, volume is write locked > >> >> >> > >> >> >> and the system is freezed. > >> >> >> On the DOS console the counter still runs, but nothing > >> happens, and I > >> >> >> don't have error messages. > >> >> >> > >> >> >> Yesterday, before the latest patch, I had the same > >> problem, but on the > >> >> >> DOS console I had these error messages (looping on the console): > >> >> >> > >> >> >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > >> >> >> ff-ff-ff-ff-ff-ff .. > >> >> >> src: 00-19-3e-36-70-1b > >> >> >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > >> >> >> ff-ff-ff-ff-ff-ff .. > >> >> >> src: 00-19-3e-36-70-1b > >> >> >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > >> >> >> ff-ff-ff-ff-ff-ff .. > >> >> >> src: 00-19-3e-36-70-1b > >> >> >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > >> >> >> ff-ff-ff-ff-ff-ff .. > >> >> >> src: 00-19-3e-36-70-1b > >> >> >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > >> >> >> ff-ff-ff-ff-ff-ff .. > >> >> >> src: 00-19-3e-36-70-1b > >> >> >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > >> >> >> ff-ff-ff-ff-ff-ff .. > >> >> >> src: 00-19-3e-36-70-1b > >> >> >> CPacketQueue(rx_queue):add() packet lost! Size = 60.. dst: > >> >> >> ff-ff-ff-ff-ff-ff .. > >> >> >> src: 00-19-3e-36-70-1b > >> >> >> > >> >> >> the only thing to do is CTRL-C, and when I do it the quit procedure > >> >> >> doesn't complete, stopping at > >> >> >> > >> >> >> Freeing memory in use by system... > >> >> >> cpu0 > >> >> >> > >> >> >> pressing again CTRL-C, the emulator quits. > >> >> >> > >> >> >> regards, > >> >> >> fausto > >> >> >> > >> >> >> > >> >> >> > >> >> >> Quoting Camiel Vanderhoeven <iam...@gm...>: > >> >> >> > >> >> >> > Hello Everyone, > >> >> >> > > >> >> >> > I've committed a couple of large patches today and yesterday to > >> >> >> > improve both multithreading and exception handling. This > >> results in > >> >> >> > restoration of the functionality of the <break> menu on > >> the serial > >> >> >> > ports. After these changes, I've run all code through a > >> source code > >> >> >> > formatter to make the coding style a bit more consistent. > >> >> I'd like you > >> >> >> > to check out the new code, and let me know if there are > >> >> aspects of the > >> >> >> > source formatting that you don't like. I'm hoping this > >> will improve > >> >> >> > readibility of the source code, and will help to develop a set of > >> >> >> > guidelines for coding style. > >> >> >> > > >> >> >> > Thanks! > >> >> >> > > >> >> >> > Camiel. > >> >> >> > > >> >> >> > P.S. I've tagged the repository before committing the > >> re-formatted > >> >> >> > code; if anything has gone horribly wrong, we can revert... > >> >> >> > > >> >> >> > > >> >> > >> ------------------------------------------------------------------------- > >> >> >> > This SF.net email is sponsored by: Microsoft > >> >> >> > Defy all challenges. Microsoft(R) Visual Studio 2008. > >> >> >> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > >> >> >> > _______________________________________________ > >> >> >> > Es40-developers mailing list > >> >> >> > Es4...@li... > >> >> >> > https://lists.sourceforge.net/lists/listinfo/es40-developers > >> >> >> > > >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> > >> ------------------------------------------------------------------------- > >> >> >> This SF.net email is sponsored by: Microsoft > >> >> >> Defy all challenges. Microsoft(R) Visual Studio 2008. > >> >> >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > >> >> >> _______________________________________________ > >> >> >> Es40-developers mailing list > >> >> >> Es4...@li... > >> >> >> https://lists.sourceforge.net/lists/listinfo/es40-developers > >> >> >> > >> >> > > >> >> > > >> ------------------------------------------------------------------------- > >> >> > This SF.net email is sponsored by: Microsoft > >> >> > Defy all challenges. Microsoft(R) Visual Studio 2008. > >> >> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > >> >> > _______________________________________________ > >> >> > Es40-developers mailing list > >> >> > Es4...@li... > >> >> > https://lists.sourceforge.net/lists/listinfo/es40-developers > >> >> > > >> >> > >> >> > >> >> > >> >> > >> ------------------------------------------------------------------------- > >> >> This SF.net email is sponsored by: Microsoft > >> >> Defy all challenges. Microsoft(R) Visual Studio 2008. > >> >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > >> >> _______________________________________________ > >> >> Es40-developers mailing list > >> >> Es4...@li... > >> >> https://lists.sourceforge.net/lists/listinfo/es40-developers > >> >> > >> > > >> > ------------------------------------------------------------------------- > >> > This SF.net email is sponsored by: Microsoft > >> > Defy all challenges. Microsoft(R) Visual Studio 2008. > >> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > >> > _______________________________________________ > >> > Es40-developers mailing list > >> > Es4...@li... > >> > https://lists.sourceforge.net/lists/listinfo/es40-developers > >> > > >> > >> > >> > >> ------------------------------------------------------------------------- > >> This SF.net email is sponsored by: Microsoft > >> Defy all challenges. Microsoft(R) Visual Studio 2008. > >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > >> _______________________________________________ > >> Es40-developers mailing list > >> Es4...@li... > >> https://lists.sourceforge.net/lists/listinfo/es40-developers > >> > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Microsoft > > Defy all challenges. Microsoft(R) Visual Studio 2008. > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > _______________________________________________ > > Es40-developers mailing list > > Es4...@li... > > https://lists.sourceforge.net/lists/listinfo/es40-developers > > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Es40-developers mailing list > Es4...@li... > https://lists.sourceforge.net/lists/listinfo/es40-developers > |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X