Re: SMP and setrunnable()- scheduler 4bsd

John Baldwin wrote: > This is why HLT is not enabled in SMP by default (or at least was, > it may be turned on now). Given that the clock interrupts are > effectively broadcast to all CPU's one way or another for all > arch's (that I know of), you will never halt more than the interval > between c

Re: failed freebsd 5.1 install

Le Wednesday 09 July 2003 07:56, Greg Kutzbach a écrit : > Motherboard > Intel® VS440FX Motherboard > http://www.intel.com/support/motherboards/desktop/VS440FX/ > 84MB RAM > IBM 40GP Hard drive > removed all PCI cards except video > Running Matrox MGA 4MB video > Pentium Pro 200 > IDE Generic CD Ro

Re: failed freebsd 5.1 install

On Tue, 8 Jul 2003 22:56:52 -0700, Greg Kutzbach <[EMAIL PROTECTED]> wrote: Motherboard Intel® VS440FX Motherboard http://www.intel.com/support/motherboards/desktop/VS440FX/ 84MB RAM IBM 40GP Hard drive removed all PCI cards except video Running Matrox MGA 4MB video Pentium Pro 200 IDE Generic CD

failed freebsd 5.1 install

Motherboard Intel® VS440FX Motherboard http://www.intel.com/support/motherboards/desktop/VS440FX/ 84MB RAM IBM 40GP Hard drive removed all PCI cards except video Running Matrox MGA 4MB video Pentium Pro 200 IDE Generic CD Rom (secondary master) Error** CD Loader 1.01 Building the boot l

PATCH - updated EC driver

If you tested my previous acpi_ec.c patch (or even if you didn't), please test the following one: http://root.org/~nate/freebsd/ec-new.diff I will be committing this is in a few days if any problems that arise are successfully addressed. It fixes numerous races and the broken tsleep approach

Re: /etc/rc: WARNING: domainname(1) is not set.

Mike Makonnen wrote: On Tue, Jul 08, 2003 at 06:26:27PM -0400, Tom Parquette wrote: Hi, I have been getting the message "/etc/rc: WARNING: domainname(1) is not set" every time I boot one of my machines. It is a 5.1-CURRENT system but I have not updated since June 15. I have been ignoring this

Panic on SMP machine.

Hello. While building world I get this panic: Fatal trap 12: page fault while in kernel mode cpuid = 0; lapic.id = fault virtual address = 24 [...] instruction pointer = 0x8:0xc01a405b [...] current process = 23 (irq10: atapi1+) kernel: type 12 trap, code=0 Stopped at

Re: /etc/rc: WARNING: domainname(1) is not set.

On Tue, Jul 08, 2003 at 06:26:27PM -0400, Tom Parquette wrote: > Hi, > I have been getting the message "/etc/rc: WARNING: domainname(1) is not > set" every time I boot one of my machines. > It is a 5.1-CURRENT system but I have not updated since June 15. > > I have been ignoring this for some tim

Re: usb dma patch

On Tue, Jul 08, 2003 at 03:45:24PM -0700, John-Mark Gurney wrote: > Hello, > > I have made usb bus_dma aware. I have only tested this patch so far on > an ohci controller in sparc64. I do have problems with isochronous > transfers, but I don't have an i386 box to test the original code on to > m

Re: /etc/rc: WARNING: domainname(1) is not set.

From: "Tom Parquette" <[EMAIL PROTECTED]> > Hi, > I have been getting the message "/etc/rc: WARNING: domainname(1) is not > set" every time I boot one of my machines. > It is a 5.1-CURRENT system but I have not updated since June 15. > Do you have "hostname" set in /etc/rc.conf? Scot ___

RE: SMP and setrunnable()- scheduler 4bsd

On Tue, 8 Jul 2003, John Baldwin wrote: > > On 08-Jul-2003 Julian Elischer wrote: > > It looks tp me that if we make a thread runnable > > and there is a processor in the idle loop, the idle processor should be > > kicked in some way to make it go get the newly runnable thread. > > > > If the

usb dma patch

Hello, I have made usb bus_dma aware. I have only tested this patch so far on an ohci controller in sparc64. I do have problems with isochronous transfers, but I don't have an i386 box to test the original code on to make sure it isn't my changes. Currently both umass and ums have been tested a

Re: SMP and setrunnable()- scheduler 4bsd

On Tue, 8 Jul 2003, Julian Elischer wrote: > It looks tp me that if we make a thread runnable > and there is a processor in the idle loop, the idle processor should be > kicked in some way to make it go get the newly runnable thread. Is this what's happenning to me an my setiathomes? -- :{ [EM

Re: whats going on with the scheduler?

On Tue, 8 Jul 2003, Doug White wrote: > On Tue, 8 Jul 2003, Andy Farkas wrote: > > > Any other ideas? Why would 3 (niced) cpu intensive processes suddenly get > > reduced cpu time (on a 4 cpu system) when a 4th non-resource intensive > > process gets started? > > Hm.. guess its time to explain how

RE: SMP and setrunnable()- scheduler 4bsd

On 08-Jul-2003 Julian Elischer wrote: > It looks tp me that if we make a thread runnable > and there is a processor in the idle loop, the idle processor should be > kicked in some way to make it go get the newly runnable thread. > > If the processors are halting in the idle loop however, it may t

/etc/rc: WARNING: domainname(1) is not set.

Hi, I have been getting the message "/etc/rc: WARNING: domainname(1) is not set" every time I boot one of my machines. It is a 5.1-CURRENT system but I have not updated since June 15. I have been ignoring this for some time because I have been trying to get DDNS to work. I thought it was related

SMP and setrunnable()- scheduler 4bsd

It looks tp me that if we make a thread runnable and there is a processor in the idle loop, the idle processor should be kicked in some way to make it go get the newly runnable thread. If the processors are halting in the idle loop however, it may take quite a while for the new work to be noticed.

Re: panic with ULE and KSE

A stack trace would be good. and if you can print the contents of the kse structure that choosethread is looking at it would be good too.. (also, how about the exact lin ein choosethread? (I assume you have a dump and are using gdb to examine it..) On Tue, 8 Jul 2003, Wiktor Niesiobedzki wrote:

Re: systematic panic on an SMP machine for 5.1-Release

On Tue, Jul 08, 2003 at 09:47:23PM +0200, Thierry Herbelot wrote: > Le Tuesday 08 July 2003 21:30, Steve Kargl a ?crit : > > On Tue, Jul 08, 2003 at 09:09:20PM +0200, Thierry Herbelot wrote: > > > TfH > > > > > > PS : as I said, the box has a 2GB RAM, so moving around the vmcore is not > > > eas

panic with ULE and KSE

Hi, I receive various panics, when I try to run ksetest, mostly concering page faults in choosethread() (called from mi_switch() in kern_synch.c:524) but also other panics. I use SCHED_ULE (haven't tried 4BSD yet, bot I'm going to). Tried this on two different machines (one build from last week,

Re: systematic panic on an SMP machine for 5.1-Release

On Tue, Jul 08, 2003 at 09:47:23PM +0200, Thierry Herbelot wrote: > Le Tuesday 08 July 2003 21:30, Steve Kargl a ?crit : > > On Tue, Jul 08, 2003 at 09:09:20PM +0200, Thierry Herbelot wrote: > > > TfH > > > > > > PS : as I said, the box has a 2GB RAM, so moving around the vmcore is not > > > easy

LDT entries and WINE and Threads..

I'm looking at this and I think that my interpretation is that WINE, under FreeBSD, blindly allocates LDT entries starting at location 17, without looking to see if they are in use already.. My reason for thinking thios is that the string i386_get_ldt only occurs once in the WINE source, and tha

Re: GEOM panic

Poul-Henning Kamp schrieb: Can you try this patch ? [patch deleted] Thanks for the fast response. Patch works for me - no more panic. -- Daniel ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscrib

Re: GEOM panic

In message <[EMAIL PROTECTED]>, Sean Kelly writes: >On Tue, Jul 08, 2003 at 10:35:47PM +0200, Poul-Henning Kamp wrote: >> >> Can you try this patch ? > >... >> diff -u -r1.28 geom_dump.c >> --- geom_dump.c 11 Jun 2003 06:49:15 - 1.28 >> +++ geom_dump.c 8 Jul 2003 20:00:45 -

Re: GEOM panic

On Tue, Jul 08, 2003 at 10:35:47PM +0200, Poul-Henning Kamp wrote: > > Can you try this patch ? ... > diff -u -r1.28 geom_dump.c > --- geom_dump.c 11 Jun 2003 06:49:15 - 1.28 > +++ geom_dump.c 8 Jul 2003 20:00:45 - ... > @@ -162,6 +164,8 @@ > sbuf_printf(sb,

Re: GEOM panic

Can you try this patch ? Index: geom_dump.c === RCS file: /home/ncvs/src/sys/geom/geom_dump.c,v retrieving revision 1.28 diff -u -r1.28 geom_dump.c --- geom_dump.c 11 Jun 2003 06:49:15 - 1.28 +++ geom_dump.c 8 Jul 2003 20:0

GEOM panic

Hi, I get a reproduceable panic each time I run the command "sysctl -a" Stack backtrace from a panic'd kernel: (kgdb) bt #0 doadump () at ../../../kern/kern_shutdown.c:240 #1 0xc025f6e9 in boot (howto=256) at ../../../kern/kern_shutdown.c:372 #2 0xc025f9e9 in panic () at ../../../kern/kern_sh

Re: systematic panic on an SMP machine for 5.1-Release

> From: Thierry Herbelot <[EMAIL PROTECTED]> > Date: Tue, 8 Jul 2003 21:47:23 +0200 > Sender: [EMAIL PROTECTED] > > PS : is this an indication of bug in the p-III or in the chipset ? > (ISTR these options could be used to get around unnamed errata of > the p-IV) Terry has never been specific (due

Re: systematic panic on an SMP machine for 5.1-Release

Le Tuesday 08 July 2003 21:30, Steve Kargl a écrit : > On Tue, Jul 08, 2003 at 09:09:20PM +0200, Thierry Herbelot wrote: > > TfH > > > > PS : as I said, the box has a 2GB RAM, so moving around the vmcore is not > > easy > > Add "options DISABLE_PSE" and "options DISABLE_PG_G" > to your kernel c

Re: systematic panic on an SMP machine for 5.1-Release

On Tue, Jul 08, 2003 at 09:09:20PM +0200, Thierry Herbelot wrote: > > TfH > > PS : as I said, the box has a 2GB RAM, so moving around the vmcore is not easy > Add "options DISABLE_PSE" and "options DISABLE_PG_G" to your kernel configuration. Report back if you still have a panic. -- St

Re: no password at login

On Tue, 8 Jul 2003, Matthew P. Carlson wrote: > I'm new to FreeBSD, so I hope I'm posting to the right list, and I know > I'm probably leaving out something important out, but oh well. > > I installed FreeBSD 5.1, used cvsup to get freebsd 5.1-current, > recompiled, and now logging in locally does

Re: no password at login

* Tue, 08 Jul 2003 12:10:49 PDT - "Matthew P. Carlson": | I installed FreeBSD 5.1, used cvsup to get freebsd 5.1-current, | recompiled, and now logging in locally doesn't require a password. | Neither does su. Ssh does. Membership of wheel is still verified. Is | it normal not to ask for a password

no password at login

I'm new to FreeBSD, so I hope I'm posting to the right list, and I know I'm probably leaving out something important out, but oh well. I installed FreeBSD 5.1, used cvsup to get freebsd 5.1-current, recompiled, and now logging in locally doesn't require a password. Neither does su. Ssh does. Membe

Re: systematic panic on an SMP machine for 5.1-Release

Le Tuesday 08 July 2003 20:44, Doug White a écrit : > On Tue, 8 Jul 2003, Thierry Herbelot wrote: > > [I just see that this message is at least lacking a "dmesg" output : I'll > > send it tomorrow.] > > A crashdump will be inifintely more useful. > > > #1 0xc030aeb8 in boot () > > #2 0xc030b21f i

Re: HTT on single CPU?

On 08-Jul-2003 Tom Samplonius wrote: > > On Tue, 8 Jul 2003, John Baldwin wrote: > > ... >> > I would need to look a second time, but there is no such BIOS option, and >> > "options HTT" was nuked in 5.1, replaced by machdep.hlt_logical_cpus, >> > which I don't have on my system. >> >> You need

Re: HTT on single CPU?

On Tue, 8 Jul 2003, John Baldwin wrote: ... > > I would need to look a second time, but there is no such BIOS option, and > > "options HTT" was nuked in 5.1, replaced by machdep.hlt_logical_cpus, > > which I don't have on my system. > > You need to enable SMP and APIC_IO in your kernel to use HT

Re: systematic panic on an SMP machine for 5.1-Release

On Tue, 8 Jul 2003, Thierry Herbelot wrote: > [I just see that this message is at least lacking a "dmesg" output : I'll send > it tomorrow.] A crashdump will be inifintely more useful. > #1 0xc030aeb8 in boot () > #2 0xc030b21f in panic () > #3 0xc0164142 in db_panic () Note no location info

Re: Where is P_THREADED?

P_THREADED was renamed P_SA. All files contianing it were also alterred... you must have an old file stashed somewhere. In particular kern_synch.c is out of date. possibly many more.. On Tue, 8 Jul 2003, David Gilbert wrote: > For a couple of days now, I've been trying to advance from 5.1-RELE

Re: whats going on with the scheduler?

On Tue, 8 Jul 2003, Andy Farkas wrote: > Any other ideas? Why would 3 (niced) cpu intensive processes suddenly get > reduced cpu time (on a 4 cpu system) when a 4th non-resource intensive > process gets started? Hm.. guess its time to explain how nice works again. Nice is a relative value. If y

systematic panic on an SMP machine for 5.1-Release

Hello, [I just see that this message is at least lacking a "dmesg" output : I'll send it tomorrow.] This report is about a systematic panic with the dreaded "panic: pmap_enter: attempted pmap_enter on 4MB page" error message. The board is from VMIC

Re: HTT on single CPU?

On Tue, 8 Jul 2003, John Baldwin wrote: > You need to enable SMP and APIC_IO in your kernel to use HTT. Also, > the BIOS setting probably won't make a difference. I have both SMP and APIC_IO options in the kernel. I'll look if I can find a BIOS update. regards, le -- Lukas Ertl

Re: HTT on single CPU?

On 08-Jul-2003 Lukas Ertl wrote: > On Tue, 8 Jul 2003, Marco Wertejuk wrote: > >> Hi Lukas, >> >> | how do I enable Hyperthreading on a box that has just a single CPU? >> >> you just have to enable Hyperthreading in the computers >> BIOS and compile a SMP Kernel with options HTT. > > I would nee

[-CURRENT tinderbox] failure on alpha/alpha

TB --- 2003-07-08 16:00:07 - starting CURRENT tinderbox run for alpha/alpha TB --- 2003-07-08 16:00:07 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/alpha/alpha TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-07-08 16:03:51 - building world TB --- cd /

Re: ULE SMP fixed.

On Tue, 8 Jul 2003, Ian Freislich wrote: > Ian Freislich wrote: > > Jeff Roberson wrote: > > > Squashed the bug that was causing panics with nice processes on SMP ULE. > > > > That is really good news. I will give it a try later today and let > > you know if I still get panics with ULE enabled. >

Re: Where is P_THREADED?

On Tue, Jul 08, 2003 at 11:13:05AM -0400, David Gilbert wrote: > For a couple of days now, I've been trying to advance from 5.1-RELEASE > to -CURRENT. I havn't been able to compile the kernel, however, as > even 'make buildkernel' (after having done a 'make buildworld') fails > looking for a P_THR

Where is P_THREADED?

For a couple of days now, I've been trying to advance from 5.1-RELEASE to -CURRENT. I havn't been able to compile the kernel, however, as even 'make buildkernel' (after having done a 'make buildworld') fails looking for a P_THREADED symbol in kern_synch.c. Since it's not very likely that I can do

RE: Help diagnosing NIS breakage ?

> - Robin P. Blanchard's Original Message - > > > > Still pulling my hair out on this one...Updated to latest > kern/world > > this morning and NIS users are no longer working. > > What -`date` version were you running where things worked > before you did the 1st upgrade? > > Can you

Re: Experiences with ath(4)

> *) Powersavemode seems to be not supported at all (and thus it eats the > battery like a "make world"): > ># ifconfig ath0 powersave on > ifconfig: SIOCS80211: Invalid argument man ath(4) The man page says "not fully", not "not supported at all". I'll fix the man page :) Actually, there are sev

Re: nfs installs of 5.1

[H The mailing list seems not to like email from my home. Here is what I sent to Thierry Herbelot.] Thierry Herbelot writes: > Le Monday 07 July 2003 23:53, M. L. Dodson a écrit : > > > > That certainly makes sense. I might gently suggest to RE, etc > > that they might want to reconsi

Re: pgsql logged in on console - su/PAM problem?

--On Tuesday, July 08, 2003 13:58:19 +0200 Lukas Ertl <[EMAIL PROTECTED]> wrote: Hi, can anyone explain why the pgsql user is logged in on console nowadays? I'm seeing the same thing, and am also interested in making it stop. -- Larry Rosenman http://www.lerctr.org/~ler

Re: ULE SMP fixed.

Ian Freislich wrote: > Jeff Roberson wrote: > > Squashed the bug that was causing panics with nice processes on SMP ULE. > > That is really good news. I will give it a try later today and let > you know if I still get panics with ULE enabled. Well, the uptime says it all: no panics yet which is

Re: whats going on with the scheduler?

On Tue, 8 Jul 2003, Terry Lambert wrote: > Dan Nelson wrote: > > In the last episode (Jul 08), Andy Farkas said: > > > If setiathome is making lots of syscalls, then running the 3 instanses > > > should already show a problem, no? > > > > Not if it's ssh that's holding Giant for longer than it shou

pgsql logged in on console - su/PAM problem?

Hi, can anyone explain why the pgsql user is logged in on console nowadays? # w 1:24PM up 3 days, 22:52, 3 users, load averages: 0.24, 0.40, 0.37 USER TTY FROM LOGIN@ IDLE WHAT pgsqlconsole -Fri02PM 3days - Postgresql is installed fro

Re: whats going on with the scheduler?

On Tue, 8 Jul 2003, Terry Lambert wrote: > It's not clear what your link speed is, but it's possible that > what's happening is that the setiathome processes are stalling > waiting for work units because you are using up your available > network bandwidth. setiathome is a cpu intensive process. I

[-CURRENT tinderbox] failure on sparc64/sparc64

TB --- 2003-07-08 10:47:44 - starting CURRENT tinderbox run for sparc64/sparc64 TB --- 2003-07-08 10:47:44 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/sparc64/sparc64 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-07-08 10:50:11 - building world TB

Re: HTT on single CPU?

On Tue, 8 Jul 2003, Marco Wertejuk wrote: > Hi Lukas, > > | how do I enable Hyperthreading on a box that has just a single CPU? > > you just have to enable Hyperthreading in the computers > BIOS and compile a SMP Kernel with options HTT. I would need to look a second time, but there is no such BI

Re: whats going on with the scheduler?

Dan Nelson wrote: > In the last episode (Jul 08), Andy Farkas said: > > If setiathome is making lots of syscalls, then running the 3 instanses > > should already show a problem, no? > > Not if it's ssh that's holding Giant for longer than it should. The > setiathome processes may be calling some

Re: whats going on with the scheduler?

Andy Farkas wrote: > On 7 Jul 2003, Lanny Baron wrote: > > A load of 3 is pretty high. I think you have more going on. > > Not for my box. Its only running at 75% cpu power. Its got four > processors, so a load of 4 is when its running flat out. And I also said > that the box is idle other than th

[-CURRENT tinderbox] failure on ia64/ia64

TB --- 2003-07-08 09:32:58 - starting CURRENT tinderbox run for ia64/ia64 TB --- 2003-07-08 09:32:58 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/ia64/ia64 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-07-08 09:36:12 - building world TB --- cd /home

Re: HTT on single CPU?

Hi Lukas, | how do I enable Hyperthreading on a box that has just a single CPU? you just have to enable Hyperthreading in the computers BIOS and compile a SMP Kernel with options HTT. -- Mit freundlichen Gruessen, Marco Wertejuk - mwcis.com Consulting & Internet Solutions __

Reproducable panic with ida(4)

My apologies for asking my pet problem to be fixed, but I'll follow through with it anyhow. :-) The ida (Compaq SMART Array and derivatives found in most ProLiant servers) has been triggering a fatal trap for quite some time now. A PR 53245 was filed reporting this issue on June 11 which referenc

Re: /dev/shm

Marcin Dalecki wrote: > Thomas Dickey wrote: > > On Mon, Jul 07, 2003 at 02:23:25PM +0200, Marcin Dalecki wrote: > >>You know that file system name lookup is one of the most > >>expensive system calls under UNIX? > > > > stating the obvious is a clumsy rhetorical ploy (asking for agreement without

HTT on single CPU?

Hi, how do I enable Hyperthreading on a box that has just a single CPU? From dmesg: ---8<--- CPU: Intel(R) Pentium(R) 4 CPU 2.53GHz (2523.99-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf27 Stepping = 7 Features=0xbfebfbff Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 Fr

Re: how to create device nodes when devfs doesn't do it?

On Mon, Jul 07, 2003 at 10:15:27AM -0700, walt wrote: > Karel J. Bosschaart wrote: > >Hi, > > > >After googling and searching in the mailing list archive I still can't > >figure out how to make device nodes in -current when devfs doesn't do this > >automatically. I have an external USB-drive (ex

Re: how to create device nodes when devfs doesn't do it?

On Mon, Jul 07, 2003 at 07:57:59PM +0200, Poul-Henning Kamp wrote: > Can you mail me the output of: > > diskinfo -v da0 > diskinfo -v da0s4 > dd if=/dev/da0 count=63 | uuencode - openbsd.sect0 > dd if=/dev/da0s4 count=16 | uuencode - openbsd.slice4 > > Then I'll try to se

Re: usb mouse on ehci controller doesn't work

On Mon, 7 Jul 2003, Doug White wrote: > On Sun, 6 Jul 2003, Bruce Cran wrote: > > > I swapped the Logitech wireless mouse for a Microsoft Intellimouse optical, > > and this time had slightly more success. If I run moused and tell XFree86 > > to use both /dev/psm0 and /dev/sysmouse, it still dies

Re: Experiences with ath(4)

On Mon, 7 Jul 2003, Sam Leffler wrote: > > *) Powersavemode seems to be not supported at all (and thus it eats the > > battery like a "make world"): > > > ># ifconfig ath0 powersave on > > ifconfig: SIOCS80211: Invalid argument > > man ath(4) The man page says "not fully", not "not supported at a

Re: ULE SMP fixed.

Jeff Roberson wrote: > Squashed the bug that was causing panics with nice processes on SMP ULE. That is really good news. I will give it a try later today and let you know if I still get panics with ULE enabled. Ian ___ [EMAIL PROTECTED] mailing list h