Updated patch for PR i386/38223

long time ago, I posted a PR reported that VM86 and VESA combination is unstable under CURRENT source, the PR is http://www.freebsd.org/cgi/query-pr.cgi?pr=i386/38223 The patch is synchronized with current source, here it is: http://opensource.zjonline.com.cn/freebsd/vm86patch.tgz - David Xu

Re: I think KSE-MIII import complete

hey what's the problem.. it rebooted didn't it :-) seriously now, thanks for the information.. I'll try simulate this.. Is this EVERY shutdown? does it happen for reboot? this could be signals .. Goshh I hate signals.. On Sat, 29 Jun 2002, Manfred Antar wrote: At 05:10 PM 6/29/2002 -0700,

Re: I think KSE-MIII import complete

I got the ithread_loop/setrunqueue panic again while building the world normally (no memory pressure). I'm too tired to deal with it tonight but tomorrow morning I'll attach a gdb and track it down. -Matt db db trace

Re: I think KSE-MIII import complete

which panic message? the code here is still FULL of asserts. On Sun, 30 Jun 2002, Matthew Dillon wrote: I got the ithread_loop/setrunqueue panic again while building the world normally (no memory pressure). I'm too tired to deal with it tonight but tomorrow morning I'll attach

Re: [PATCH] Re: Which .info files have been disabled?

Hello everybody, Sorry for taking a tad long with this, here is the second patch set for the GDB info files. I implemented both of David's suggestions, so the third patch is no longer needed and GDBvn.texi can be safely cvs rm-d now, it is generated dynamically at build time. If you want to go

KSE M-III status:

well afte a day I'm releatively happy.. there seem to be 4 bugs showing themselves.. plus one braino I just fixed.. (there was a bug where ps would panic the kernel when it got to a zombie process because it tried to print thread info but ther eis no thread). in addition the following

Re: mozilla and gnome apps won't run after KSE [June 29]

Ithink these may be threaded it's possible the are using signals and they may be broken On Fri, 28 Jun 2002, walt wrote: Following make world make kernel after the KSE update I find that mozilla and any gnome app will suck up 98% of the CPU and will never actually write anything to

Re: [PATCH] Re: Which .info files have been disabled?

Grrr, hit me baby one more time. One of the diffs included a completely gratuitous one-line change which I made yesterday night while I was tired and neglected to correct today. So, the patchset again. (Take three!) -- Regards: Szilveszter ADAM Szombathely Hungary Index: Makefile

Re: make install failed on XFree86-4-client (with 6/10 -current)

Well, this has been happening for about a year on my dev box. It's not gcc 3.1 specific. I've never gotten around to figuring out why it works on some machines. On Sat, 29 Jun 2002 19:41:51 -0700, David O'Brien wrote: On Sat, Jun 29, 2002 at 11:30:48PM +0100, Brian Somers wrote: The problem

alpha tinderbox failure

Sun Jun 30 07:00:07 PDT 2002 cd: can't cd to /home/des/tinderbox/alpha/src To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message

Re: Revised: KSE M-III status:

On Sun, 30 Jun 2002, Julian Elischer wrote: On Sun, 30 Jun 2002, Julian Elischer wrote: Well after 1 day I'm releatively happy.. that's relatively There seem to have been 4 bugs showing themselves.. A machine doing REAL HEAVY work and SWAPPING LIKE CRAZY eventually paniced.

Re: mozilla and gnome apps won't run after KSE [June 29]

Hello, I see no problems with neither GNOME nor Mozilla. Kernel compiled about an hour ago (15:30:13 CEST / GMT+2). Userland last compiled on June 27. On Sun, 2002-06-30 at 10:29, Julian Elischer wrote: Ithink these may be threaded it's possible the are using signals and they may be

Re: mozilla and gnome apps won't run after KSE [June 29]

Hi so far. you are the only person who has reported this.. please let me know if anything changes.. It's now the 'top' item in my list of problems. On Fri, 28 Jun 2002, walt wrote: Following make world make kernel after the KSE update I find that mozilla and any gnome app will suck

Re: I think KSE-MIII import complete

: :which panic message? :the code here is still FULL of asserts. : Unexpected ke present. I'm resynching and will run the build test again. If it crunches again I'll do a more detailed check. -Matt To Unsubscribe: send mail to [EMAIL

More on gnome and mozilla (post-KSE)

Dunno if this is important, but I meant to mention it in my initial problem report: the problem with gnome and mozilla chewing up CPU cycles begain just after the make world finished and while the make kernel was still compiling, so whatever this problem is it was not due to changes in the

Re: mozilla and gnome apps won't run after KSE [June 29]

well, that's different :-) any chance to get a ktrace ? On Sun, 30 Jun 2002, Steve Kargl wrote: On Sun, Jun 30, 2002 at 10:39:12AM -0700, Julian Elischer wrote: Hi so far. you are the only person who has reported this.. please let me know if anything changes.. It's now

Re: More on gnome and mozilla (post-KSE)

hmmm well, since the only changes were in the kernel except for libkvm I'm puzzled. If you boot off the old kernel (You still have it right? :-) does it still act the same? On Sun, 30 Jun 2002, walt wrote: Dunno if this is important, but I meant to mention it in my initial problem

Re: mozilla and gnome apps won't run after KSE [June 29]

ty a new libkvm.. also please try the same binary booted off the old non KSE kernel.. (what, you don't still have it?) On Sun, 30 Jun 2002, Julian Elischer wrote: well, that's different :-) any chance to get a ktrace ? On Sun, 30 Jun 2002, Steve Kargl wrote: On Sun, Jun 30, 2002 at

KSE / interrupt panic

Got another one. Different panic, same place. panic: setrunqueue: bad thread state cpuid = 0; lapic.id = 0100 Debugger(panic) Stopped at Debugger+0x46: xchgl %ebx,in_Debugger.0 db trace Debugger(c02ec2ba) at Debugger+0x46 panic(c02ec8a9,c6461d80,c6461d80,c6461d80,c01afa30) at

Re: KSE / interrupt panic

others have seen this one too and the common element is that it's always in setrunqueue() called from an interrupt. it is also often via cv_*SOMETHING*() I Thought we had cleared these up but apparently not :-/ On Sun, 30 Jun 2002, Matthew Dillon wrote: Got another one. Different panic,

Re: KSE / interrupt panic

:others have seen this one too :and the common element is that it's always in :setrunqueue() called from an interrupt. :it is also often via cv_*SOMETHING*() : :I Thought we had cleared these up but apparently not :-/ : There are a bunch of wakeup race conditions in the CV code where

buildworld problems with today's sources

I did the following (on a -STABLE system): cvs co src cd src make MAKEOBJDIRPREFIX=`pwd`/../usr/obj buildworld and got the error below. Any ideas ? Am i doing something wrong ? cheers luigi === gnu/usr.bin/tar rm -f tar addext.o argmatch.o backupfile.o

Re: KSE / interrupt panic

On Sun, 30 Jun 2002, Matthew Dillon wrote: Got another one. Different panic, same place. panic: setrunqueue: bad thread state cpuid = 0; lapic.id = 0100 Debugger(panic) Stopped at Debugger+0x46: xchgl %ebx,in_Debugger.0 db trace Debugger(c02ec2ba) at Debugger+0x46

Re More on gnome and mozilla (post-KSE)

Julian on FreeBSD-CURRENT wrote: On Sun, 30 Jun 2002, walt wrote: Dunno if this is important, but I meant to mention it in my initial problem report: the problem with gnome and mozilla chewing up CPU cycles begain just after the make world finished and while the make kernel was still

Re: mozilla and gnome apps won't run after KSE [June 29]

On Sun, Jun 30, 2002 at 10:39:12AM -0700, Julian Elischer wrote: Hi so far. you are the only person who has reported this.. please let me know if anything changes.. FWIW: I'm running gimp on an alpha running a post KSE kernel. The world is about 2 weeks older on that machine. --

Build world problems in todays sources

I get the following error when trying to rebuild the last couple of days... ../sys/kern/syscalls.master syscall.master : line 55: syscall number out of sync at 7 ... line is: struct rusage * rsuage ) ; } wait4 wait_args int Error code 1 -- Glenn Gombert [EMAIL PROTECTED]

Re: Build world problems in todays sources

On 2002-06-30 22:53 +, Glenn Gombert wrote: I get the following error when trying to rebuild the last couple of days... ../sys/kern/syscalls.master syscall.master : line 55: syscall number out of sync at 7 ... line is: struct rusage * rsuage ) ; } wait4 wait_args int Error

Re: KSE / interrupt panic

setrunqueue() call can be simply removed from cv_timedwait_end(), because there is a race in softclock() and callout_stop(), when cv_timedwait_end() losts a race, it means that that thread is already running(wokenup by another thread), when you setrunqueue() it, of course it will panic. in

libufs commit [Was Re: cvs commit: CVSROOT modules src MAINTAINERS src/lib Makefile src/lib/libufs Makefile block.c inode.c libufs.h sblock.c type.c]

* Juli Mallett [EMAIL PROTECTED] escriuréres jmallett2002/06/30 18:45:03 PDT Modified files: .modules .MAINTAINERS lib Makefile Added files: lib/libufs Makefile block.c inode.c libufs.h

Re: KSE / interrupt panic (patch)

Now let me describe where the race is: Thread A: | Thread B: cv_timedwait() | softclock() | cv_timedwait_end()

[] freebsd-current !

Title: ¿ì¸®Ä«µå ¼º¸í Áֹεî·Ï ¹øÈ£ Á÷Àå ÀüÈ­ ÈÞ´ëÆù

Re: KSE / interrupt panic (patch)

thanks.. I was aware of he race but it looks as if I miscaldulated it somehow.. I will look at the source again and confirm your patch. As you say, msleep() is of the same form and has the same problems. On Mon, 1 Jul 2002, David Xu wrote: Now let me describe where the race is: Thread A:

Re: What's the right way to build XFree86-4 now?

At 4:57 PM +0200 6/26/02, Sheldon Hearn wrote: Here's what I did to get XFree86-4 to build with the base system's toolchain in -CURRENT: a) ports/devel/imake-4: Replace files/patch-d and files/patch-xthreads with the attached patch-config::cf::FreeBSD.cf. Add the attached

i386 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

Post-KSE desaster

Everything that links to libc_r is now completely hosed here, this includes all of KDE. Since KDE is a tad too big to make a handy test, here comes ogg123 from the vorbis-tools port: [lofi@kiste]:1:~ gdb ogg123 GNU gdb 5.2.0 (FreeBSD) 20020627 Copyright 2002 Free Software Foundation, Inc.

Re: Post-KSE desaster

On Mon, Jul 01, 2002 at 07:11:31AM +0200, Michael Nottebrock wrote: Program received signal SIGSEGV, Segmentation fault. 0x281cc918 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 (gdb) bt #0 0x281cc918 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 #1

Re: Post-KSE desaster

Bill Huey wrote: Try info threads in gdb and then progressively walking through the thread list with thread N, N being the thread number. (...) Program received signal SIGSEGV, Segmentation fault. 0x281cc918 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 (gdb) info thread

Re: Post-KSE desaster

I see this problem too. Luckily I have my entire KDE and QT system build with debugging symbols... However, the problem is definitely in the libc_r... I get virtually the same dump as Michael. #0 0x28e8d280 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 #1 0x28e8c9a7 in

getting back to current

I've just finished going thru another medical session, this one took about 5 months, and because of the extended time spent away, I'm running 4.5 (I've been running current since 1.1, this feels really odd). I need a little bit of help (or advice, maybe) to get me back to current. I just

Is pcm broken?

Looks like someone broke AC97 rate measurement in -CURRENT -STABLE measures AC97 rate well (about 55900). Current gives about 41000... Hardware is Compaq EXD C600 (-STABLE) and Compaq iPAQ C700 (-CURRENT) Both are i815 equipped with SoundMAX AC97 codec... Sincerely, Maxim M. Kazachek