MBuf use size problem on 4.8-RC

2003-03-24 Thread Slawek Zak
Hi,

netstat -m produces following output on my machine, running 4.8-RC:

21732/22336/96000 mbufs in use (current/peak/max):
21732 mbufs allocated to data
20733/21260/24000 mbuf clusters in use (current/peak/max)
48104 Kbytes allocated to network (8% of mb_map in use)
0 requests for memory denied
0 requests for memory delayed
0 calls to protocol drain routines

I tracked the percentage of mb_map in use. It reached 70% and then
wrapped back to 0%. Why does it happen? A bug?

There seems to be a problem with booting up 4.8-RC on a 4GB machine.
The kernel reaching multiuser mode produces message about
unability of allocating new u_map and panics. This is HyperThreading
enabled machine (2+2logical CPUs). Any ideas?

Thanks. /S

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


Re: HyperThreading not working?

2003-02-27 Thread Slawek Zak
On Wed, Feb 26, 2003 at 02:05:51PM -0500, John Baldwin wrote:
  I'm in the process of installing 5.0-RELEASE-p3 on a Dell PowerEdge
  2600 server. It has two HyperThreading Xeon 2.4Ghz processors, but
  HyperThreading is not working in FreeBSD. I guess that four
  processors should be visible in the system after boot. Yes - I've
  enabled `Logical Processors' in BIOS. BIOS revision is the latest
  available.
  
  Any thoughts? I attach full dmesg and mptable output. Kernel
  config too.
 
 5.0 doesn't support HyperThreading.  The upcoming 5.1 and 4.8 releases
 will support it.

Thanks. I didn't put tag=. in the supfile, but the default 5_0_RELENG.
That's why it didn't work even after cvsup. Now it's all CURRENT,
working stable and blazing fast. Even with SCHED_ULE :)

All the best, /S

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


HyperThreading not working?

2003-02-26 Thread Slawek Zak
Hi,

I'm in the process of installing 5.0-RELEASE-p3 on a Dell PowerEdge
2600 server. It has two HyperThreading Xeon 2.4Ghz processors, but
HyperThreading is not working in FreeBSD. I guess that four
processors should be visible in the system after boot. Yes - I've
enabled `Logical Processors' in BIOS. BIOS revision is the latest
available.

Any thoughts? I attach full dmesg and mptable output. Kernel
config too.

Thanks, /S
machine i386
cpu I686_CPU
ident   W3
maxusers0

#To statically compile in device wiring instead of /boot/device.hints
#hints  GENERIC.hints #Default places to look for devices.

#makeoptionsDEBUG=-g#Build kernel with gdb(1) debug symbols

options INET#InterNETworking
options FFS #Berkeley Fast Filesystem
options SOFTUPDATES #Enable FFS soft updates support
options UFS_ACL #Support for access control lists
options UFS_DIRHASH #Improve performance on big directories
options MD_ROOT #MD is a potential root device
options NFSCLIENT   #Network Filesystem Client
options MSDOSFS #MSDOS Filesystem
options CD9660  #ISO 9660 Filesystem
options PROCFS  #Process filesystem (requires PSEUDOFS)
options PSEUDOFS#Pseudo-filesystem framework
options COMPAT_43   #Compatible with BSD 4.3 [KEEP THIS!]
options COMPAT_FREEBSD4 #Compatible with FreeBSD4
options SCSI_DELAY=7000 #Delay (in ms) before probing SCSI
options KTRACE  #ktrace(1) support
options SYSVSHM #SYSV-style shared memory
options SYSVMSG #SYSV-style message queues
options SYSVSEM #SYSV-style semaphores
options _KPOSIX_PRIORITY_SCHEDULING #Posix P1003_1B real-time extensions
options KBD_INSTALL_CDEV# install a CDEV entry in /dev
# output.  Adds ~215k to driver.

# Debugging for use in -current
#optionsDDB #Enable the kernel debugger
#optionsINVARIANTS  #Enable calls of extra sanity checking
#optionsINVARIANT_SUPPORT   #Extra sanity checks of internal structures, 
required by INVARIANTS
#optionsWITNESS #Enable checks to detect deadlocks and cycles
#optionsWITNESS_SKIPSPIN#Don't run witness on spinlocks for speed

# To make an SMP kernel, the next two are needed
options SMP # Symmetric MultiProcessor Kernel
options APIC_IO # Symmetric (APIC) I/O

device  pci

# Floppy drives
device  fdc

# ATA and ATAPI devices
device  ata
device  atadisk # ATA disk drives
device  atapicd # ATAPI CDROM drives
device  atapifd # ATAPI floppy drives
device  atapist # ATAPI tape drives
options ATA_STATIC_ID   #Static device numbering

# SCSI peripherals
device  scbus   # SCSI bus (required)
device  ch  # SCSI media changers
device  da  # Direct Access (disks)
device  sa  # Sequential Access (tape etc)
device  cd  # CD
device  pass# Passthrough device (direct SCSI access)
device  ses # SCSI Environmental Services (and SAF-TE)

# RAID controllers
device  amr # AMI MegaRAID

# atkbdc0 controls both the keyboard and the PS/2 mouse
device  atkbdc  # AT keyboard controller
device  atkbd   # AT keyboard
device  psm # PS/2 mouse

device  vga # VGA video card driver

device  splash  # Splash screen and screen saver support

# syscons is the default console driver, resembling an SCO console
device  sc

# Enable this for the pcvt (VT220 compatible) console driver
#device vt
#optionsXSERVER # support for X server on a vt console
#optionsFAT_CURSOR  # start with block cursor

device  agp # support several AGP chipsets

# Floating point support - do not disable.
device  npx

# Serial (COM) ports
device  sio # 8250, 16[45]50 based serial ports

# PCI Ethernet NICs.
device  em  # Intel PRO/1000 adapter Gigabit Ethernet Card

# Pseudo devices - the number indicates how many units to allocate.
device  random  # Entropy device
device  loop# Network loopback
device  ether   # Ethernet support
device  pty # Pseudo-ttys (telnet etc)

Re: sysinstall + swap partition requirement

2002-11-27 Thread Slawek Zak
On Wed, Nov 27, 2002 at 04:04:08PM +0100, Marcin Dalecki wrote:
 During a fresh install of the DP2 I noticed that sysinstall didn't
 allow me to configure the system *without* any swap paritions.
 
 Well this doesn't make sense, since:
 
 1. The system has perfectly fine 192MB of RAM, thus the installation
 should scceed anyway...
 
 2. I intendid to use SWAP-over-vnode to work around GCC's template 
 compilation
 eats RAM struggle.
 
 I guess this safety check is a leftover from the days where one had 
 typically
 16MB of RAM + 100MB of swap on a system...

I don't know if anything has changed in 5.x, but VM in BSDs in general
doesn't work too well without swap. Swap is useful for system crash
gathering anyway.

/S

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



Adaptec 7899 on-board controller and 4.4-RC

2001-08-21 Thread Slawek Zak

I have 2 such controlers in a Dell 6400. Both did work on 4.3-STABLE,
updated about 4 weeks ago. After upgrade to 4.4-RC none of them is
detected during boot. Did the ahc driver `suffer' some dramatic
changes lately?

/S

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



SCSI breakage

2000-08-01 Thread Slawek Zak

I'm having SCSI parity errors on Tekram 390F controller (CURRENT for
Aug 1, the sym driver). During some heavier disk activity the kernel
reports "Weird command received" and resets the controller after short
period of time. Now I'm running CURRENT for Jul 31 without any
problems...
-- 
hundred-and-one symptoms of being an internet addict:
144. You eagerly await the update of the "Cool Site of the Day."
* Suavek Zak / PGP: finger:[EMAIL PROTECTED]


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



Re: Netscape

2000-07-28 Thread Slawek Zak

Kris Kennaway [EMAIL PROTECTED] writes:

  Are the fixed in Netscape 4.74 bugs not critical for release?
 
 Who knows? I don't know of any changelog for Netscape.

Netscape 4.74 contains a fix for security critical bug in handling of
jpeg images. The bug was found and published on the 25th of July by
Solar Designer.

(as you all probably already know;)
-- 
"I think there is a world market for maybe five computers."
 - Thomas Watson, chairman of IBM, 1943
* Suavek Zak / PGP: finger:[EMAIL PROTECTED]


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