Re: KSE-MIII ready for commit
Jake just checked something in that looks like it may be relevant. On Fri, 28 Jun 2002, David O'Brien wrote: On Fri, Jun 28, 2002 at 11:02:51PM -0700, David O'Brien wrote: Not buildable on sparc64: User error. Now I get: Mounting root from ufs:/dev/ad0a WARNING: / was not properly dismounted panic: trap: memory address not aligned cpuid = 0; Debugger(panic) Stopped at Debugger+0x1c: ta %xcc, 1 db tr panic() at panic+0xf4 trap() at trap+0x4e8 -- memory address not aligned sfar=0xa1 sfsr=0x40029 %o7=0xc01efce4 -- vm_page_sleep_busy() at vm_page_sleep_busy+0x20 pmap_release() at pmap_release+0x90 vmspace_exitfree() at vmspace_exitfree+0x94 vm_waitproc() at vm_waitproc+0x44 wait1() at wait1+0x4e0 wait4() at wait4+0xc syscall() at syscall+0x368 -- syscall (7, FreeBSD ELF, wait4) %o7=0x13a0c0 -- userland() at 0x13be88 user trace: trap %o7=0x13a0c0 pc 0x13be88, sp 0x7fdec71 pc 0x10d064, sp 0x7fded31 pc 0x10cd8c, sp 0x7fdedf1 pc 0x10cbf0, sp 0x7fdeec1 pc 0x10512c, sp 0x7fdef81 pc 0x103c58, sp 0x7fdf141 pc 0x10dc6c, sp 0x7fdf201 pc 0x10db24, sp 0x7fdf2e1 pc 0x1001e4, sp 0x7fdf401 pc 0, sp 0x7fdf4c1 done To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: KSE-MIII ready for commit
You must have something wrong in the MD code that jake added.. I don't do anything in that code or with any allignments none of these functions have been altered.. Jake said he had it going... On Fri, 28 Jun 2002, David O'Brien wrote: On Fri, Jun 28, 2002 at 11:02:51PM -0700, David O'Brien wrote: Not buildable on sparc64: User error. Now I get: Mounting root from ufs:/dev/ad0a WARNING: / was not properly dismounted panic: trap: memory address not aligned cpuid = 0; Debugger(panic) Stopped at Debugger+0x1c: ta %xcc, 1 db tr panic() at panic+0xf4 trap() at trap+0x4e8 -- memory address not aligned sfar=0xa1 sfsr=0x40029 %o7=0xc01efce4 -- vm_page_sleep_busy() at vm_page_sleep_busy+0x20 pmap_release() at pmap_release+0x90 vmspace_exitfree() at vmspace_exitfree+0x94 vm_waitproc() at vm_waitproc+0x44 wait1() at wait1+0x4e0 wait4() at wait4+0xc syscall() at syscall+0x368 -- syscall (7, FreeBSD ELF, wait4) %o7=0x13a0c0 -- userland() at 0x13be88 user trace: trap %o7=0x13a0c0 pc 0x13be88, sp 0x7fdec71 pc 0x10d064, sp 0x7fded31 pc 0x10cd8c, sp 0x7fdedf1 pc 0x10cbf0, sp 0x7fdeec1 pc 0x10512c, sp 0x7fdef81 pc 0x103c58, sp 0x7fdf141 pc 0x10dc6c, sp 0x7fdf201 pc 0x10db24, sp 0x7fdf2e1 pc 0x1001e4, sp 0x7fdf401 pc 0, sp 0x7fdf4c1 done To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: KSE-MIII ready for commit
you are missing kern_thread.c On Fri, 28 Jun 2002, David O'Brien wrote: Not buildable on sparc64: linking kernel.debug procfs_ctl.o: In function `procfs_control': procfs_ctl.o(.text+0x56c): undefined reference to `thread_unsuspend' init_main.o: In function `proc0_init': init_main.o(.text+0x3a8): undefined reference to `threadinit' kern_condvar.o: In function `cv_check_upcall': kern_condvar.o(.text+0xb8): undefined reference to `thread_schedule_upcall' kern_condvar.o: In function `cv_wait_sig': kern_condvar.o(.text+0x56c): undefined reference to `thread_suspend_check' kern_condvar.o: In function `cv_timedwait_sig': kern_condvar.o(.text+0xd18): undefined reference to `thread_suspend_check' kern_exec.o: In function `execve': kern_exec.o(.text+0x80): undefined reference to `thread_single' kern_exit.o: In function `exit1': kern_exit.o(.text+0xc4): undefined reference to `thread_suspend_check' kern_exit.o(.text+0xd8): undefined reference to `thread_single' kern_exit.o(.text+0x110): undefined reference to `thread_single_end' kern_exit.o(.text+0xb38): undefined reference to `thread_exit' kern_exit.o: In function `wait1': kern_exit.o(.text+0x1044): undefined reference to `thread_free' kern_exit.o(.text+0x1068): undefined reference to `thread_reap' kern_fork.o: In function `fork1': kern_fork.o(.text+0x410): undefined reference to `thread_single' kern_fork.o(.text+0x520): undefined reference to `thread_single_end' kern_fork.o(.text+0x5f4): undefined reference to `thread_single_end' kern_fork.o(.text+0xa70): undefined reference to `thread_alloc' kern_proc.o: In function `proc_linkup': kern_proc.o(.text+0x464): undefined reference to `thread_link' kern_proc.o: In function `kse_yield': kern_proc.o(.text+0x4c0): undefined reference to `thread_exit' kern_proc.o: In function `kse_new': kern_proc.o(.text+0x5f0): undefined reference to `thread_schedule_upcall' kern_sig.o: In function `psignal': kern_sig.o(.text+0x2500): undefined reference to `thread_unsuspend' kern_sig.o(.text+0x276c): undefined reference to `thread_unsuspend' kern_synch.o: In function `msleep': kern_synch.o(.text+0x6c8): undefined reference to `thread_schedule_upcall' kern_synch.o(.text+0xa28): undefined reference to `thread_suspend_check' kern_synch.o: In function `setrunnable': kern_synch.o(.text+0x1698): undefined reference to `thread_unsuspend' subr_trap.o: In function `userret': subr_trap.o(.text+0x200): undefined reference to `thread_suspend_check' subr_trap.o(.text+0x240): undefined reference to `thread_userret' trap.o: In function `trap': trap.o(.text+0x32c): undefined reference to `thread_exit' *** Error code 1 Stop in /files/src/sys/sparc64/compile/GENERIC. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: KSE-MIII ready for commit
On Fri, Jun 28, 2002 at 11:39:29PM -0700, Julian Elischer wrote: Jake just checked something in that looks like it may be relevant. Yes it was. `thediff' on sparc64 is solid. Still some ast funkiness on Alpha, but it is not so bad as to make it so someone cannot get work done on Alpha if they are careful. I personally am happy with the state of things on non-i386 platforms. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: KSE-MIII ready for commit
On Fri, 28 Jun 2002, David O'Brien wrote: On Fri, Jun 28, 2002 at 11:39:29PM -0700, Julian Elischer wrote: Jake just checked something in that looks like it may be relevant. Yes it was. `thediff' on sparc64 is solid. Still some ast funkiness on Alpha, but it is not so bad as to make it so someone cannot get work done on Alpha if they are careful. I'm puzzled by that because it works solid for Bernd. My problem is that I have to do a new buildworld test because I suspect that there may be problems withthe new gdb compiling.. If I commit a new kernel now, gdb may break world, so I have to redo a buildworld.. :-/ I personally am happy with the state of things on non-i386 platforms. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: KSE-MIII ready for commit
On Fri, Jun 28, 2002 at 11:55:46PM -0700, David O'Brien wrote: On Fri, Jun 28, 2002 at 11:39:29PM -0700, Julian Elischer wrote: Jake just checked something in that looks like it may be relevant. Yes it was. `thediff' on sparc64 is solid. Still some ast funkiness on Alpha, but it is not so bad as to make it so someone cannot get work done on Alpha if they are careful. Can you describe the ast problems you have. -- B.Walter COSMO-Project http://www.cosmo-project.de [EMAIL PROTECTED] Usergroup [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: KSE-MIII ready for commit
Not buildable on sparc64: linking kernel.debug procfs_ctl.o: In function `procfs_control': procfs_ctl.o(.text+0x56c): undefined reference to `thread_unsuspend' init_main.o: In function `proc0_init': init_main.o(.text+0x3a8): undefined reference to `threadinit' kern_condvar.o: In function `cv_check_upcall': kern_condvar.o(.text+0xb8): undefined reference to `thread_schedule_upcall' kern_condvar.o: In function `cv_wait_sig': kern_condvar.o(.text+0x56c): undefined reference to `thread_suspend_check' kern_condvar.o: In function `cv_timedwait_sig': kern_condvar.o(.text+0xd18): undefined reference to `thread_suspend_check' kern_exec.o: In function `execve': kern_exec.o(.text+0x80): undefined reference to `thread_single' kern_exit.o: In function `exit1': kern_exit.o(.text+0xc4): undefined reference to `thread_suspend_check' kern_exit.o(.text+0xd8): undefined reference to `thread_single' kern_exit.o(.text+0x110): undefined reference to `thread_single_end' kern_exit.o(.text+0xb38): undefined reference to `thread_exit' kern_exit.o: In function `wait1': kern_exit.o(.text+0x1044): undefined reference to `thread_free' kern_exit.o(.text+0x1068): undefined reference to `thread_reap' kern_fork.o: In function `fork1': kern_fork.o(.text+0x410): undefined reference to `thread_single' kern_fork.o(.text+0x520): undefined reference to `thread_single_end' kern_fork.o(.text+0x5f4): undefined reference to `thread_single_end' kern_fork.o(.text+0xa70): undefined reference to `thread_alloc' kern_proc.o: In function `proc_linkup': kern_proc.o(.text+0x464): undefined reference to `thread_link' kern_proc.o: In function `kse_yield': kern_proc.o(.text+0x4c0): undefined reference to `thread_exit' kern_proc.o: In function `kse_new': kern_proc.o(.text+0x5f0): undefined reference to `thread_schedule_upcall' kern_sig.o: In function `psignal': kern_sig.o(.text+0x2500): undefined reference to `thread_unsuspend' kern_sig.o(.text+0x276c): undefined reference to `thread_unsuspend' kern_synch.o: In function `msleep': kern_synch.o(.text+0x6c8): undefined reference to `thread_schedule_upcall' kern_synch.o(.text+0xa28): undefined reference to `thread_suspend_check' kern_synch.o: In function `setrunnable': kern_synch.o(.text+0x1698): undefined reference to `thread_unsuspend' subr_trap.o: In function `userret': subr_trap.o(.text+0x200): undefined reference to `thread_suspend_check' subr_trap.o(.text+0x240): undefined reference to `thread_userret' trap.o: In function `trap': trap.o(.text+0x32c): undefined reference to `thread_exit' *** Error code 1 Stop in /files/src/sys/sparc64/compile/GENERIC. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: KSE-MIII ready for commit
On Fri, Jun 28, 2002 at 11:02:51PM -0700, David O'Brien wrote: Not buildable on sparc64: User error. Now I get: Mounting root from ufs:/dev/ad0a WARNING: / was not properly dismounted panic: trap: memory address not aligned cpuid = 0; Debugger(panic) Stopped at Debugger+0x1c: ta %xcc, 1 db tr panic() at panic+0xf4 trap() at trap+0x4e8 -- memory address not aligned sfar=0xa1 sfsr=0x40029 %o7=0xc01efce4 -- vm_page_sleep_busy() at vm_page_sleep_busy+0x20 pmap_release() at pmap_release+0x90 vmspace_exitfree() at vmspace_exitfree+0x94 vm_waitproc() at vm_waitproc+0x44 wait1() at wait1+0x4e0 wait4() at wait4+0xc syscall() at syscall+0x368 -- syscall (7, FreeBSD ELF, wait4) %o7=0x13a0c0 -- userland() at 0x13be88 user trace: trap %o7=0x13a0c0 pc 0x13be88, sp 0x7fdec71 pc 0x10d064, sp 0x7fded31 pc 0x10cd8c, sp 0x7fdedf1 pc 0x10cbf0, sp 0x7fdeec1 pc 0x10512c, sp 0x7fdef81 pc 0x103c58, sp 0x7fdf141 pc 0x10dc6c, sp 0x7fdf201 pc 0x10db24, sp 0x7fdf2e1 pc 0x1001e4, sp 0x7fdf401 pc 0, sp 0x7fdf4c1 done To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: KSE-MIII ready for commit
On Thu, Jun 27, 2002 at 07:50:39PM -0700, Julian Elischer wrote: Estimated commit time: (assuming current works at that time) will be around 1AM GMT June 29 that will be 6PM here in San Francisco. We need more than 2 days time to test on Alpha and sparc64. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: KSE-MIII ready for commit
I won't be absent after that, just busier. On Thu, 27 Jun 2002, David O'Brien wrote: On Thu, Jun 27, 2002 at 07:50:39PM -0700, Julian Elischer wrote: Estimated commit time: (assuming current works at that time) will be around 1AM GMT June 29 that will be 6PM here in San Francisco. We need more than 2 days time to test on Alpha and sparc64. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: KSE-MIII ready for commit
On Thu, Jun 27, 2002 at 08:18:17PM -0700, Julian Elischer wrote: I won't be absent after that, just busier. ENOPARSE To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: KSE-MIII ready for commit
you said you need more than the two days I said I would be watching for problems over the weekend.. I responded that teh two days is only the time I will have a LOT of time but that even after that time I will still be here in case things explode. On Thu, 27 Jun 2002, David O'Brien wrote: On Thu, Jun 27, 2002 at 08:18:17PM -0700, Julian Elischer wrote: I won't be absent after that, just busier. ENOPARSE To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: KSE-MIII ready for commit
:you said you need more than the two days I said I would be watching :for problems over the weekend.. I responded that :teh two days is only the time I will have a LOT of time but that even :after that time I will still be here in case things explode. : : :On Thu, 27 Jun 2002, David O'Brien wrote: : : On Thu, Jun 27, 2002 at 08:18:17PM -0700, Julian Elischer wrote: : : I won't be absent after that, just busier. : : ENOPARSE I think he means he would like you to give him a little more time before comitting. e.g. like comitting July 1 instead of June 29 (If that's what you mean David, you should just say so). I wouldn't mind a few extra days but I definitely do not want an open-ended delay. I really think KSEIII needs to get into the tree so we can start the next round. I think I've cleared out my -current tree so I can resync sys to your KSE branch and do more KSE testing. Would it be possible for you to synchronize your KSE branch to -current again, as of now, so I can be sure it has all the various things that have gone in of late? -Matt Matthew Dillon [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: KSE-MIII ready for commit
On Thu, Jun 27, 2002 at 09:36:54PM -0700, Matthew Dillon wrote: I think he means he would like you to give him a little more time before comitting. e.g. like comitting July 1 instead of June 29 (If that's what you mean David, you should just say so). Sorry, that is what I meant. I'd like to have a chance to test this on Alpha and sparc64, if no one else has. When I tried the patch during USENIX it wasn't ready on non-i386 platforms. Not looking for a long time, just maybe the July 1 (or 3rd) that you mentioned. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: KSE-MIII ready for commit
ok.. but let me know when you have tested it a bit.. David, ifyou want to test this I really suggest that you grab it with cvsup as a whole rather than doing small patches one at a time... (check my web page for how to do that..) Matt, I just did a sync.. On Thu, 27 Jun 2002, David O'Brien wrote: On Thu, Jun 27, 2002 at 09:36:54PM -0700, Matthew Dillon wrote: I think he means he would like you to give him a little more time before comitting. e.g. like comitting July 1 instead of June 29 (If that's what you mean David, you should just say so). Sorry, that is what I meant. I'd like to have a chance to test this on Alpha and sparc64, if no one else has. When I tried the patch during USENIX it wasn't ready on non-i386 platforms. Not looking for a long time, just maybe the July 1 (or 3rd) that you mentioned. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: KSE-MIII ready for commit
On Thu, 27 Jun 2002, Matthew Dillon wrote: :you said you need more than the two days I said I would be watching :for problems over the weekend.. I responded that :teh two days is only the time I will have a LOT of time but that even :after that time I will still be here in case things explode. : : :On Thu, 27 Jun 2002, David O'Brien wrote: : : On Thu, Jun 27, 2002 at 08:18:17PM -0700, Julian Elischer wrote: : : I won't be absent after that, just busier. : : ENOPARSE I think he means he would like you to give him a little more time before comitting. e.g. like comitting July 1 instead of June 29 (If that's what you mean David, you should just say so). I wouldn't mind a few extra days but I definitely do not want an open-ended delay. I really think KSEIII needs to get into the tree so we can start the next round. hmmm I see.. the only reference I had made to *2* days was the period AFTER the commit. I think I've cleared out my -current tree so I can resync sys to your KSE branch and do more KSE testing. Would it be possible for you to synchronize your KSE branch to -current again, as of now, so I can be sure it has all the various things that have gone in of late? I sync'd twice today so it's no big deal to sync at the moment.. I'll do another one now.. -Matt Matthew Dillon [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
