Sched_Ule

2003-10-08 Thread Scott Sipe

Hi,

I see some posts from late Sept about people having issues with SCHED_ULE.
I just wanted to add in that I am having the exact same problems.  In
short:

Anything that seems disk intensive: bzip2 (unbzip2ing one big file makes
this happen), making world, building ports, etc makes my X environment
practically unusable.  Mouse stutters, reaction times is very slow, feels
10x more sluggish than normal.  (I'm running KDE if anyone is curious).

I rebuilt my kernel today (running yesterday's world) with SCHED_4BSD
instead, and things are much better.  System is much much more responsive.

If there's any tests I can run, or anyone I should talk to, I'd love to be
of assistance,

thanks much,
Scott
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: pkg_add segfault

2003-03-19 Thread Scott Sipe
pkg_add -r coredumps for me on a system built Mar 18, but not on one built
Mar 3.

Scott


From: Joris Vandalon [EMAIL PROTECTED]

 Hi there,

 it seemd that pkg_add coredumps while doing pkg_add -r $package
 pkg_add $package seems work ok.
 anyone else experiencing the same problem?

 -example-

 [EMAIL PROTECTED] strace]# pkg_add -r lftp
 Segmentation fault (core dumped)
 [EMAIL PROTECTED] strace]#

 -end example-

 Regards,

 Joris

 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: source upgrade broken?

2003-03-17 Thread Scott Sipe
I second that problem.  Tried doing an upgrade yesterday, and it didn't
work--missing libc.so.4 error given during make installworld.

Scott

- Original Message -
From: Robert Garrett [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, March 16, 2003 3:53 AM
Subject: source upgrade broken?


 Gentleman,

 Please correct me if I am wrong but it appears, that the source upgrade
 path from 4.* to 5.0 is broken. I havent played with it much but it
appears thatbuilding the kernel, depends on somethings new to the -current
compiler, and the compiler is dependant on stuff in the 5.-current kernel. I
realize that with all the stuff thats been ripped out of 5.0 and added, that
a clean install is probably the best way to go. I am just curious if it
truly is borked or if it is just me.

 Robert Garrett

 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: Request for info from SiS chipset owners

2003-02-01 Thread Scott Sipe
atapci0: SiS 5591 ATA100 controller port 0xd800-0xd80f at device 0.1 on
pci0

agp0@pci0:0:0:  class=0x06 card=0x chip=0x07301039 rev=0x02
hdr=0x00
atapci0@pci0:0:1:   class=0x010180 card=0x80321043 chip=0x55131039
rev=0xd0 hdr=0x00
isab0@pci0:1:0: class=0x060100 card=0x chip=0x00081039 rev=0x00
hdr=0x00
ohci0@pci0:1:2: class=0x0c0310 card=0x70011039 chip=0x70011039 rev=0x07
hdr=0x00
ohci1@pci0:1:3: class=0x0c0310 card=0x70001039 chip=0x70011039 rev=0x07
hdr=0x00
pcm0@pci0:1:4:  class=0x040100 card=0x80321043 chip=0x70181039 rev=0x02
hdr=0x00
pcib1@pci0:2:0: class=0x060400 card=0x chip=0x00011039 rev=0x00
hdr=0x01
rl0@pci0:9:0:   class=0x02 card=0x80261043 chip=0x813910ec rev=0x10
hdr=0x00
xl0@pci0:13:0:  class=0x02 card=0x100010b7 chip=0x920010b7 rev=0x78
hdr=0x00
wi0@pci0:16:0:  class=0x028000 card=0x41051385 chip=0x38731260 rev=0x01
hdr=0x00
none0@pci1:0:0: class=0x03 card=0x80321043 chip=0x63001039 rev=0x31
hdr=0x00

Scott
- Original Message -
From: Soeren Schmidt [EMAIL PROTECTED]
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Saturday, February 01, 2003 6:02 AM
Subject: Request for info from SiS chipset owners



 I'm currently in the midst of an ATA chipset support mega rewrite/update,
 and the last item on the list is SiS support.

 That where _you_ come into the picture, I need a pciconf -l from your
 SiS based system!

 Just reply to this message with the output from pciconf -l and you
 have helped me sort out the myriads of SiS chipsets out there.

 -Søren

 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



hw.acpi.disable_on_poweroff

2003-01-26 Thread Scott Sipe

This defaulted to 1 ony my Current--is there a reason for this?  I like
being able to press the power putton and have it shutdown properly, or have
shutdown -p power down.

thanks,
Scott


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Undefined symbol __xuname

2003-01-20 Thread Scott Sipe
Running current updated today.  I tried running Fetchmailconf (for the first 
time) and this is the message I get:

Traceback (most recent call last):
  File /usr/local/libexec/fetchmailconf.bin, line 9, in ?
from Tkinter import *
  File /usr/local/lib/python2.2/lib-tk/Tkinter.py, line 35, in ?
import _tkinter # If this fails your Python may not be configured for Tk
ImportError: /usr/local/lib/libtcl83.so.1: Undefined symbol __xuname

I've rebuit fetchmail, python, Tk, Tcl, and py-tkinter, and still get this.  
Apologies if this isn't a current issue.

Any ideas?

thanks,
scott

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: DP2 Fatal Trap

2002-11-22 Thread Scott Sipe
On Friday 22 November 2002 10:57 am, you wrote:
 On 21-Nov-2002 Scott Sipe wrote:
  On Thursday 21 November 2002 04:26 pm, John Baldwin wrote:
  Erm, well, PSE and PGE are already disabled in GENERIC on DP2.  Hmm.
  Can you try doing gdb -k kernel.debug in multiuser under DEBUG and
  see if gdb behaves any better?  Another idea might be to use addr2line
  instead like so:
 
  addr2line -e kernel.debug -f 0xc031f044
 
  in gdb the line I get when I do l * is 'No symbol table is loaded.  Use
  the file command.' -- (multiuser too).  Am I doing something wrong?
 
  addr2line displays:
  getpeername1
  /usr/src/sys/kern/uipc_syscalls.c:1453

 Hmm, that would be:

 if ((error = fgetsock(td, uap-fdes, so, NULL)) != 0)
 goto done2;

 (which is in getpeername1()).

 Hmm.  Unless uap was somehow hosed I don't see how else you could
 be getting a panic (it was a fatal trap 12, right?)

It was a trap 12, and definitely that address...I think something more 
overarching must be going on though.  I'm able to login with /bin/sh (not 
csh/tcsh) and so I've been trying various things--I can't compile a kernel 
because I get bus errors, same with many ports I've been trying to install.  
pkg_adding seems fine.  Any chance this could be acpi related?

Scott


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: DP2 Fatal Trap

2002-11-22 Thread Scott Sipe

Alright, this is pretty frustrating.  I've installed DP2 4 or 5 times now 
(each time reformatting).

The first time the installation program acted really weird and didn't do the 
install correctly.  The second time I had weird random core dump problems so 
that I couldn't even log in.  The third time I think was with the trap 12 
when I started tcsh...now I reinstalled and it SEEMS to be working fine.  At 
least enough that I was able to compile a custom kernel, and compile most of 
the gnome suite from ports too (and then to remove it ;).  There was ONE 
problem I had -- one of the g++ include files (limits) had one line that was 
corrupted and I could fix.
the line was like:

coint name_more; (somethingl ike that)

when it should have been
const int name_more10;

(line 1710 iirc)

so basically it seems like I'm getting random data corruption at random times 
with random results.  fwiw, I'm running stable off the same harddisk as I 
type this.

sorry if this throws a wrench in things again.

Scott

On Friday 22 November 2002 06:48 pm, Terry Lambert wrote:
 Scott Sipe wrote:
  It was a trap 12, and definitely that address...I think something more
  overarching must be going on though.  I'm able to login with /bin/sh (not
  csh/tcsh) and so I've been trying various things--I can't compile a
  kernel because I get bus errors, same with many ports I've been trying to
  install. pkg_adding seems fine.  Any chance this could be acpi related?

 How about this...

 o Are you using a GENERIC kernel?

 o Do you have a timestamp that can be used to check out a
   /usr/src/sys from CVS that will let me build the same
   kernel?

 o Do you have a place I can upload two or more 3/4MB kernel
   files for you to try?

 Let's say the answer to all three questions is yes.

 Assuming I can build you a binary kernel from your sources which
 then fails on your machine, I believe I can fix the problem, and
 give you a new binary kernel that fixes it, if it's the problem I
 think it is.

 That way, we all win: you get a working kernel, and I get to
 convince people that the problem is what I said it was in the
 first place: a CPU bug that has to be specifically worked around.

 -- Terry


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



DP2 Fatal Trap

2002-11-21 Thread Scott Sipe

First install of DP2 went crazy weird (posted earlier).  A minimal install 
(just the minimal distribution) went fine and I could login but didn't really 
try anything more than that.  Now the install went fine, the boot goes fine 
(no errors that I can see) but when I log in I get:

page fault
Fatal Trap 12: Page fault while in kernel mode
fault virtual address   = 0x89
fault code  = supervisor read, page not present
IP  = 0x8:0xc031f044
SP  = 0x10:0xd99a6c98
FP  = 0x10:0xd99a6cc0
Code Segment= base 0x0, limit 0xf, type 0x1b
= DPL0, pres 1, def32 1, gran 1 (-- not 100% 
sure of this line)
Processor eflags= interrupt enabled, resume, IOPL=0
Current Process = 446 (tcsh)
Trap Number = 12
Panic: Page Fault
Syncing disks... panic: bwrite: buffer is not busy???
/page fault

I have 512MB of ram, AthlonXP cpu, and the swap partition was mounted during 
boot.

I posted my STABLE dmesg, I can do it again if it would help, I can't get my 
current dmesg (don't have a serial console unless a palm pilot will work 
somehow)

thanks,
Scott

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: DP2 Fatal Trap

2002-11-21 Thread Scott Sipe
On Thursday 21 November 2002 01:36 pm, John Baldwin wrote:
 Hmm, is this from a GENERIC kernel?

This is from straight from DP2 iso image cd install, X-Developer install, 
first boot after the install finished, generic kernel etc.

Scott

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: DP2 Fatal Trap

2002-11-21 Thread Scott Sipe
On Thursday 21 November 2002 01:58 pm, John Baldwin wrote:
 On 21-Nov-2002 Scott Sipe wrote:
  On Thursday 21 November 2002 01:36 pm, John Baldwin wrote:
  Hmm, is this from a GENERIC kernel?
 
  This is from straight from DP2 iso image cd install, X-Developer install,
  first boot after the install finished, generic kernel etc.

 Ok, generic kernel is the only really important part. :)  Can you
 do me a favor and see if you have a /boot/kernel.GENERIC/kernel.debug
 or a /boot/kernel/kernel.debug?  If so, can you please do
 'gdb -k kernel.debug' and then at the prompt do 'l *instruction pointer'
 where instruction pointer is the second part of the instruction pointer
 from the panic message?  (I.e., w/o the leading '0x8:' part.)

I am able to login as root (sh) in single user mode, but login as root on a 
normal boot dies (starting tcsh from single user mode traps too).

There is a file /boot/kernel/kernel.debug but when I do the gdb command (the 
l) it gives an error about no symbols, use the file command.  I did:
cd /boot/kernek
gdb -k kernel.debug
(in gdb)
l *0xc031f044

sorry if this is a stupid mistake on my part.

Secondly, I'm able to boot ok from the debug kernel.  I did boot DEBUG and I 
can then login as my user (tcsh) ok and can run X successfully.  I imagine I 
can recompile the kernel, would this be useful? (disabling PSE or the PGE 
options?)

Scott

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: DP2 Fatal Trap

2002-11-21 Thread Scott Sipe
On Thursday 21 November 2002 04:26 pm, John Baldwin wrote:

 Erm, well, PSE and PGE are already disabled in GENERIC on DP2.  Hmm.
 Can you try doing gdb -k kernel.debug in multiuser under DEBUG and
 see if gdb behaves any better?  Another idea might be to use addr2line
 instead like so:

 addr2line -e kernel.debug -f 0xc031f044

in gdb the line I get when I do l * is 'No symbol table is loaded.  Use the 
file command.' -- (multiuser too).  Am I doing something wrong?

addr2line displays:
getpeername1
/usr/src/sys/kern/uipc_syscalls.c:1453

Scott

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



DP2 (and earlier) Problems *addition

2002-11-20 Thread Scott Sipe
Sorry, should have done this with the first email.  The dmesg from my stable 
boot:

(hdd ad0 is the one on which I have current installed)

Copyright (c) 1992-2002 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 4.7-STABLE #2: Sat Nov 16 16:02:19 EST 2002
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/DRAGON
Timecounter i8254  frequency 1193182 Hz
CPU: AMD Athlon(tm) XP  (1338.76-MHz 686-class CPU)
  Origin = AuthenticAMD  Id = 0x662  Stepping = 2
  
Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
  AMD Features=0xc048b19,AMIE,DSP,3DNow!
real memory  = 536805376 (524224K bytes)
avail memory = 517144576 (505024K bytes)
Preloaded elf kernel kernel at 0xc050c000.
Preloaded elf module linux.ko at 0xc050c09c.
Preloaded elf module nvidia.ko at 0xc050c13c.
Pentium Pro MTRR support enabled
md0: Malloc disk
Using $PIR table, 10 entries at 0xc00fded0
npx0: math processor on motherboard
npx0: INT 16 interface
pcib0: Host to PCI bridge on motherboard
pci0: PCI bus on pcib0
pcib1: VIA 8363 (Apollo KT133) PCI-PCI (AGP) bridge at device 1.0 on pci0
pci1: PCI bus on pcib1
nvidia0: GeForce2 GTS mem 0xd000-0xd7ff,0xda00-0xdaff irq 12 
at device 0.0 on pci1
isab0: VIA 82C686 PCI-ISA bridge at device 7.0 on pci0
isa0: ISA bus on isab0
atapci0: VIA 82C686 ATA100 controller port 0xc000-0xc00f at device 7.1 on 
pci0
atapci0: Correcting VIA config for southbridge data corruption bug
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
uhci0: VIA 83C572 USB controller port 0xc400-0xc41f irq 10 at device 7.2 on 
pci0
usb0: VIA 83C572 USB controller on uhci0
usb0: USB revision 1.0
uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
ums0: Logitech USB Mouse, rev 1.10/6.10, addr 2, iclass 3/1
ums0: 4 buttons and Z dir.
pci0: unknown card (vendor=0x1106, dev=0x3057) at 7.4
xl0: 3Com 3c905C-TX Fast Etherlink XL port 0xcc00-0xcc7f mem 
0xdd00-0xdd7f irq 11 at device 11.0 on pci0
xl0: Ethernet address: 00:50:da:8b:64:b7
miibus0: MII bus on xl0
xlphy0: 3c905C 10/100 internal PHY on miibus0
xlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
pcm0: Creative EMU10K1 port 0xd000-0xd01f irq 9 at device 14.0 on pci0
atapci1: CMD 649 ATA100 controller port 
0xe800-0xe80f,0xe400-0xe403,0xe000-0xe007,0xdc00-0xdc03,0xd800-0xd807 irq 10 
at device 16.0 on pci0
ata2: at 0xd800 on atapci1
ata3: at 0xe000 on atapci1
orm0: Option ROM at iomem 0xcc000-0xcc7ff on isa0
atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0
atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0
sc0: System console at flags 0x100 on isa0
sc0: VGA 16 virtual consoles, flags=0x300
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1: configured irq 3 not in bitmap of probed irqs 0
ppc0: parallel port not found.
ad0: 76319MB MAXTOR 4K080H4 [155061/16/63] at ata0-master UDMA100
ad1: 114440MB WDC WD1200JB-75CRA0 [232514/16/63] at ata2-master UDMA100
ad2: 114440MB WDC WD1200JB-75CRA0 [232514/16/63] at ata3-master UDMA100
acd0: DVD-ROM Pioneer DVD-ROM ATAPIModel DVD-106S 0109 at ata1-master PIO4
acd1: CD-RW LITE-ON LTR-32123S at ata1-slave PIO4
Mounting root from ufs:/dev/ad0s1a

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



DP2 (and earlier) Problems

2002-11-19 Thread Scott Sipe
1) I burned the ISO image.  Booted from the CD.  When installing, if I try to 
do a network install of some part, it asks me the interface, I select xl0, my 
3com card.  It asks for IPV6, I say no, it asks for dhcp, I say yes--but 
nothing happens (none of the values fill in).  I'm guessing this is related 
to my problem 2. (though dhcp did work later in the installation after some 
parts of the installation had been performed off the cd).

2) Lots and lots of core dumps on first boot.  I just now installed off the 
CD, on the first boot up, got a lot of core dumps (too many for me to see 
them all), one error I remember was sendmail not being to find execve in 
some library (sorry for lack of details).  I had similar problems with DP1 
which I tried last week--I would for instance cvsup and it would keep 
replacing files that I KNOW are up to date--it's like for some reason current 
is acting as if my hard disk is going bad or is getting corrupt data off it.  
A program might work one minute, and on the next reboot not.  I have no idea 
how to troubleshoot this further.  I know my hardware is good, I'm running 
stable right now off the same harddisk.

I tried to get a dmesg, but after I type a login name getty dies.  Basically 
everything that tries to run, dies.

Advice on how to continue?

Scott

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Arla Port

2002-04-22 Thread Scott Sipe


Hi, I'm having trouble compiling the Arla (AFS) port on CURRENT, it looks 
like certain structures have changed.  Is anyone running Arla on current?

If it would be the right thing to do, I can post the errors here.

Scott

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Build Error

2002-03-31 Thread Scott Sipe

When doing buildworld on current from a couple hours ago.  This is an alpha, 
if that makes a difference.  This is my first time compiling current 
(currently running stable), so apologies if this is something that is my 
fault.

The error:
START
=== sbin/savecore
make: don't know how to make savekerneldump.c. Stop
*** Error code 2

Stop in /usr/src/sbin.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1
/STOP

The Makefile (which doesn't seem ok):
START
# $FreeBSD: src/sbin/savecore/Makefile,v 1.8 2002/03/31 22:26:56 phk Exp $
PROG=   savekerneldump
WARNS=  4
NOMAN=  sorry, not yet.
LDADD=  -lmd

.include bsd.prog.mk
/STOP

I tried making it similar to the Makefile for savecore from STABLE, but it 
still wouldn't compile (undefined consts/defines I believe).

thanks,
Scott

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Status of NetBSD rc.d implementation

2002-03-28 Thread Scott Sipe


Hi, I've seen this project mentioned (several times) recently, yet the only 
references I can find to it seem to have had no updates in months.  Is there 
any news here, or ongoing work?

I remember I read about the NetBSD rc awhile back and it sounded quite cool.  
I've never worked on anything like this before, but I'd be interested in 
seeing if there was anything I could do to help out..

thanks,
Scott

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Alpha Build

2002-03-25 Thread Scott Sipe


Hi, I have a chance to pick up an Alpha machine which I would use for FreeBSD 
testing.

There are 4 AlphaStation 600's from which I could pick, 2 of them have 'TGA 
graphics cards', 2 have normal graphics cards and can run X.  Seeing as 
right now I know next to nothing about Alpha's, would it be better to pick 
one or the other, or, would one or the other be better for freeBSD testing?

thanks much,
Scott

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message