Re: More ULE bugs fixed.

[Jeff Roberson]

On Fri, 17 Oct 2003, Bruce Evans wrote:

> How would one test if it was an improvement on the 4BSD scheduler?  It
> is not even competitive in my simple tests.

[scripts results deleted]

>
> Summary: SCHED_ULE was more than twice as slow as SCHED_4BSD for the
> obj and depend stages.  These stages have little parallelism.  SCHED_ULE
> was only 19% slower for the all stage.  It apparently misses many
> oppurtunities to actually run useful processes.  This may be related
> to /usr being nfs mounted.  There is lots of idling waiting for nfs
> even in the SCHED_4BSD case.  The system times are smaller for SCHED_ULE,
> but this might not be significant.  E.g., zeroing pages can account
> for several percent of the system time in buildworld, but on unbalanced
> systems that have too much idle time most page zero gets done in idle
> time and doesn't show up in the system time.

At one point ULE was at least as fast as 4BSD and in most cases faster.
This is a regression.  I'll sort it out soon.


>
> Test 1 for fair scheduling related to niceness:
>
>   for i in 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
>   do
>   nice -$i sh -c "while :; do echo -n;done" &
>   done
>   top -o time
>
> [Output deleted].  This shows only a vague correlation between niceness
> and runtime for SCHED_ULE.  However, top -o cpu shows a strong correlation
> between %CPU and niceness.  Apparently, %CPU is very innacurate and/or
> not enough history is kept for long-term scheduling to be fair.
>
> Test 5 for fair scheduling related to niceness:
>
>   for i in -20 -16 -12 -8 -4 0 4 8 12 16 20
>   do
>   nice -$i sh -c "while :; do echo -n;done" &
>   done
>   time top -o cpu
>
> With SCHED_ULE, this now hangs the system, but it worked yesterday.  Today
> it doesn't get as far as running top and it stops the nfs server responding.
> To unhang the system and see what the above does, run a shell at rtprio 0
> and start top before the above, and use top to kill processes (I normally
> use "killall sh" to kill all the shells generated by tests 1-5, but killall
> doesn't work if it is on nfs when the nfs server is not responding).

  661 root 112  -20   900K   608K RUN  0:24 27.80% 27.64% sh
  662 root 114  -16   900K   608K RUN  0:19 12.43% 12.35% sh
  663 root 114  -12   900K   608K RUN  0:15 10.66% 10.60% sh
  664 root 114   -8   900K   608K RUN  0:11  9.38%  9.33% sh
  665 root 115   -4   900K   608K RUN  0:10  7.91%  7.86% sh
  666 root 1150   900K   608K RUN  0:07  6.83%  6.79% sh
  667 root 1154   900K   608K RUN  0:06  5.01%  4.98% sh
  668 root 1158   900K   608K RUN  0:04  3.83%  3.81% sh
  669 root 115   12   900K   608K RUN  0:02  2.21%  2.20% sh
  670 root 115   16   900K   608K RUN  0:01  0.93%  0.93% sh

I think you cvsup'd at a bad time.  I fixed a bug that would have caused
the system to lock up in this case late last night.  On my system it
freezes for a few seconds and then returns.  I can stop that by turning
down the interactivity threshold.

Thanks,
Jeff

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

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

DRM SMPng locking for review

[Eric Anholt]

I've been working on locking of the DRM, based off of the work that was
already done for linux and ported to BSD.  I think the current locking
was wrong, including that it used lockmgr and simplelocks on -stable
when as far as I know it was unnecessary.  Also, I had marked the IRQ
handlers MPSAFE without understanding the issue really, so IRQs could
get missed.  Here's a patch, which I hope someone can review because I
don't trust myself at all.
http://people.freebsd.org/~anholt/dri/files/drm-locking-2.diff

It's against DRI CVS, as I haven't merged to FreeBSD in a while.  You
can get it using the instructions at:
http://dri.sourceforge.net/cgi-bin/moin.cgi/CVS
If you don't want to build the whole tree, you can just:

cd xc
patch -p0 < ~/drm-locking-2.diff
cd programs/Xserver/hw/xfree86/os-support/bsd/drm/kernel
ln -s ../../../shared/drm/kernel/*.[ch] ./

Quick question: If open returns an error, close doesn't get called, does
it?

-- 
Eric Anholt[EMAIL PROTECTED]  
http://people.freebsd.org/~anholt/ [EMAIL PROTECTED]


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

Re: More ULE bugs fixed.

[Bruce Evans]

On Wed, 15 Oct 2003, Jeff Roberson wrote:

> I fixed two bugs that were exposed due to more of the kernel running
> outside of Giant.  ULE had some issues with priority propagation that
> stopped it from working very well.
>
> Things should be much improved.  Feedback, as always, is welcome.  I'd
> like to look into making this the default scheduler for 5.2 if things
> start looking up.  I hope that scares you all into using it more. :-)

How would one test if it was an improvement on the 4BSD scheduler?  It
is not even competitive in my simple tests.

Test for scheduling buildworlds:

cd /usr/src/usr.bin
for i in obj depend all
do
MAKEOBJDIRPREFIX=/somewhere/obj time make -s -j16 $i
done >/tmp/zqz 2>&1

(Run this with an empty /somewhere/obj.  The all stage doesn't quite
finish.)  On an ABIT BP6 system with a 400MHz and a 366MHz CPU, with
/usr (including /usr/src) nfs-mounted (with 100 Mbps ethernet and a
reasonably fast server) and /somewhere/obj ufs1-mounted (on a fairly
slow disk; no soft-updates), this gives the following times:

SCHED_ULE-yesterday, with not so careful setup:
   40.37 real 8.26 user 6.26 sys
  278.90 real59.35 user41.32 sys
  341.82 real   307.38 user69.01 sys
SCHED_ULE-today, run immediately after booting:
   41.51 real 7.97 user 6.42 sys
  306.64 real59.66 user40.68 sys
  346.48 real   305.54 user69.97 sys
SCHED_4BSD-yesterday, with not so careful setup:
  [same as today except the depend step was 10 seconds slower (real)]
SCHED_4BSD-today, run immediately after booting:
   18.89 real 8.01 user 6.66 sys
  128.17 real58.33 user43.61 sys
  291.59 real   308.48 user72.33 sys
SCHED_4BSD-yesterday, with a UP kernel (running on the 366 MHz CPU) with
many local changes and not so careful setup:
   17.39 real 8.28 user 5.49 sys
  130.51 real60.97 user34.63 sys
  390.68 real   310.78 user60.55 sys

Summary: SCHED_ULE was more than twice as slow as SCHED_4BSD for the
obj and depend stages.  These stages have little parallelism.  SCHED_ULE
was only 19% slower for the all stage.  It apparently misses many
oppurtunities to actually run useful processes.  This may be related
to /usr being nfs mounted.  There is lots of idling waiting for nfs
even in the SCHED_4BSD case.  The system times are smaller for SCHED_ULE,
but this might not be significant.  E.g., zeroing pages can account
for several percent of the system time in buildworld, but on unbalanced
systems that have too much idle time most page zero gets done in idle
time and doesn't show up in the system time.

Test 1 for fair scheduling related to niceness:

for i in 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
do
nice -$i sh -c "while :; do echo -n;done" &
done
top -o time

[Output deleted].  This shows only a vague correlation between niceness
and runtime for SCHED_ULE.  However, top -o cpu shows a strong correlation
between %CPU and niceness.  Apparently, %CPU is very innacurate and/or
not enough history is kept for long-term scheduling to be fair.

Test 5 for fair scheduling related to niceness:

for i in -20 -16 -12 -8 -4 0 4 8 12 16 20
do
nice -$i sh -c "while :; do echo -n;done" &
done
time top -o cpu

With SCHED_ULE, this now hangs the system, but it worked yesterday.  Today
it doesn't get as far as running top and it stops the nfs server responding.
To unhang the system and see what the above does, run a shell at rtprio 0
and start top before the above, and use top to kill processes (I normally
use "killall sh" to kill all the shells generated by tests 1-5, but killall
doesn't work if it is on nfs when the nfs server is not responding).

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

Re: Atheros Throughput TEST!

[Marcos Biscaysaqu]

Hi there.

   We are working with a couple atheros wireless card,  we setup a 
Freebsd AP with a  NETGEAR card on mode 11a  mediaopt hostap turbo mode, 
We made a Throughput test with 2 different wireless card DLINK and 
NETGEAR , with a ftp traffic in both ways with no diference between the 
DLINK and NETGEAR card, Very good speed but the Freebsd AP crash after 4 
min.

idea??? help??

throughput Test.

http://202.49.92.224/atheros/TESTFAst.html



Marcos Biscaysaqu wrote:

Hi there.
The Atheros driver new version fix the problem to make work the 
wireless card on mode  11a point-to-point?
thanks

--

Marcos Biscaysaqu

Systems Administrator
ThePacific.Net Ltd.


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

Re: Darwin/OSX Bluetooth code

[Justin C. Walker]

If you don't find it on the darwin site 
(http://developer.apple.com/darwin), it's probably not going to show up 
as an open source project.

Regards,

Justin

On Thursday, October 16, 2003, at 09:00 PM, Maksim Yevmenkin wrote:

Dear Hackers,

Does anyone know if Apple has released Darwin/OSX Bluetooth code to the
public? Quick look at http://www.opensource.apple.com/ did not reveal
anything particularly useful (although i did not try really hard :)
I'm currently thinking about un-Netgraph'ing FreeBSD code to make it 
portable
to other BSD style systems. I'm trying to look at other implementations
and learn as much as i can. In particular i'm trying to figure out how 
to
minimize OS dependent code and what is the right abstractions levels.

thanks,
max
__
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to 
"[EMAIL PROTECTED]"


--
Justin C. Walker, Curmudgeon-At-Large  *
Institute for General Semantics|   If you're not confused,
   |   You're not paying attention
*--*---*
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Darwin/OSX Bluetooth code

[Maksim Yevmenkin]

Dear Hackers,

Does anyone know if Apple has released Darwin/OSX Bluetooth code to the
public? Quick look at http://www.opensource.apple.com/ did not reveal
anything particularly useful (although i did not try really hard :)

I'm currently thinking about un-Netgraph'ing FreeBSD code to make it portable
to other BSD style systems. I'm trying to look at other implementations
and learn as much as i can. In particular i'm trying to figure out how to 
minimize OS dependent code and what is the right abstractions levels.

thanks,
max

__
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Intel 1000/PRO (em) problem

[Michael Nadler]

Check the setting for your RX Int delay.  Try setting it to 0.  It can be changed 
on-the-fly via `sysctl hw.em.rx_int_delay`.
Look at the comments in if_em.c for an explanation.
If that does not solve the problem, contact Intel support -- they have been very helpful to me in the past.


I'm experiencing a problem with the em driver in 5.1-CURRENT for my Intel 1000/Pro fiber Gbit adapter.

The following is recorded in the syslog:

Oct 15 18:17:49 shaolin kernel: em0: watchdog timeout -- resetting
Oct 15 18:30:25 shaolin kernel: em0: watchdog timeout -- resetting
Oct 15 18:30:27 shaolin kernel: em0: Link is Down


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

Re: NVIDIA nForce MCP network driver - now supports CURRENT

[Q]

Actually there are two ways of doing this. One is to use a Wake-On-Lan
Magic Packet(tm), which I have never tested, but I believe should be
taken care of by the systems BIOS. Technically it is possible to have
the device driver set the ACPI state level the machine should be woken
up from, but I haven't investigated if it works. You probably need to
have ACPI enabled for this to work.

These is another feature the hardware appears to support that is
generally called "OnNow" (wake on packet), which allows you to wake the
machine from any arbitrary packet based on a 128byte mask. However up
until now nobody has expressed any interest in either feature.

How do you plan to use such a feature?
Do any other device drivers support it yet?

Seeya...Q


On Fri, 2003-10-17 at 11:29, TAKANO Yuji wrote:

> Hello. My name is TAKANO. from Japan.
> 
> From: Q <[EMAIL PROTECTED]> :
> > To those of you using motherboards based on the NVIDIA nForce chipsets,
> > I have recently added support for CURRENT to my nForce MCP ethernet
> > driver.
> > 
> > The details can be found here:
> > 
> > http://www.onthenet.com.au/~q/nvnet
> 
> With 5-CURRENT Allowed to use NVIDIA nForce MCP network driver
> Thank you.
> 
> 
> This driver Although it seems that it does not correspond to
> WakeUpOnLAN, does it support from now on?
> 
> TAKANO Yuji
> ---
>  Mail and Web : [EMAIL PROTECTED]: http://www.running-dog.net/
>   : [EMAIL PROTECTED]
>   : [EMAIL PROTECTED] : http://www.icmpv6.org/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

ACPI, USB, and the tangled web

[Anish Mistry]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

First off, if you've been following my dabbling in fixing the USB resume 
problem on my laptop you know that I have been plauged by the infamous 
restart on second suspend with a usb device being accessed during the second 
suspend (ie. wiggling mouse).  Yesterday after finally updating to a current 
that boots my system after a couple of weeks without it I suspended the 
system and resumed it to check some ACPI issues had been fixed, but that's 
for another time. After resume I realized I needed my mouse, so I plugged it 
in, dynamically loaded the kernel module and the mouse worked (normal/
previous).  Then I suspend the laptop and was wiggling the mouse while it was 
suspending (bad habit from testing) and the system REBOOTED, and my patches 
weren't even applied!  Strangly enough I had never actually tested this 
situation before, so I had assumed it was my code that was the problem.  
There seems to be some ACPI problem, since I just tested the same procedure 
on with ACPI disabled and there was no reboot.
 http://am-productions.biz/debug/acpidump.txt
 http://am-productions.biz/debug/littleguy.dsdt
 http://am-productions.biz/debug/littleguy.asl
 http://am-productions.biz/debug/dmesg.txt

dmesg attached too.
- -- 
Anish Mistry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQE/j0tUxqA5ziudZT0RAsnDAJ48ehUGVPnMWXgJbmAxPw9zg1p9OACgvy2s
JO25mUFwvByJiUyPPnAvsr8=
=8fK2
-END PGP SIGNATURE-
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Asus A7V8X-X USB problems

[Greg J.]

On Thu, 16 Oct 2003 08:50:01 -0700 (PDT)
Doug White <[EMAIL PROTECTED]> wrote:

> On Wed, 15 Oct 2003, Greg J. wrote:
> 
> > > > > What's attached to the ports?
> > > > Nothing.. if I plug anything in (like a mouse) it freezes my
> > > > system.
> > >
> > > Interesting .. which VIA chipset is it? I have a KT400 at home
> > > that hasn't built current in a while but worked as of a few weeks
> > > ago. I'll have to try a fresh build.
> >
> > KT400 here too.. also, were you able to get 'shutdown -p now' to
> > work? For some reason it times out on me.
> 
> Yeah, it started getting flakey on me after jhb commited some stuff to
> the ACPI tree.  I haven't taken the time to track it down, though.

I just found out that setting this fixes it..

sysctl hw.acpi.disable_on_poweroff=0

So now it's just the USB problem.. which I can live with.. I can use the
ps2 adapter for my usb mouse for the time being.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Help- re-install of 5.1 release leaves bootloader unworkable

[Scott W]

Hey all- hopefully someone can point me in the right direction here.  
After problems with cvsuped 5.1 current, I did a re-install of 5.1 
RELEASE on a system with two IDE drives.  The install appears to go 
well, but on reboot, I'm faced with what appears to be 3(!!) options for 
booting BSD, none of which work.

The system is a dual celeron 366MHz with 768M RAM.
HPT66 IDE controller which has 2 IDE drives plugged into it.
These show up as ad4 and ad5 during the install.
The boot menu shows as:
F1 freebsd
F2 freebsd
F3 Disk 1
none of which work.
If I type:
unload
boot 3(ad1,d)
I get an error 1 lba 0
Other selections result in:
no /boot/loader
I have been able to load the fixit disk, and mount the correct 
partitions, but the only references I've seen to any help with respect 
to re-installing the boot loader are 'installbootloader' which doesn't 
appear to be on this install. 

So...how do I recover this install and remove the 'bad' entries in the 
loader, and point it at the correct disk?

Disk layout is as follows:
ad3s1a /tmp  2G
ad3s1b   swap   2G
ad4s1d /boot   128M
ad4s1a /1G
ad4s1e /var 2G
ad4s2d /usr 10G
ad4s1b /home  5G
Scott

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

reliable panics in arstrategy

[Brooks Davis]

I've got four dual Xeon servers that I can reliably panic under disk
load.  All of them have Promise ATA Raid controlers running in RAID1
mode.  They consistantly panic in arstrategy if I run something like a
CVS checkout of ports.  The panic message and ddb backtrace are below
as is the dmesg.  The kernel is the SMP kernel.  I've tried to obtain a
crash dump, but "call dumpsys" just dumps me right back into the same
panic so I'm hoping this is something you can reproduce.  Please let me
know if you need more information or if I need to try and figure out
some way to run gdb on these boxes.

Thanks,
Brooks

Fatal trap 12: page fault while in kernel mode
cpuid = 0; lapic.id = 
fault virtual address   = 0xa6ea70f4
fault code  = supervisor write, page not present
instruction pointer = 0x8:0xc04dc3b9
stack pointer   = 0x10:0xe0469bc4
frame pointer   = 0x10:0xe0469c54
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 4 (g_down)
kernel: type 12 trap, code=0
Stopped at  arstrategy+0x939:   movl%eax,0x24(%ebx,%ecx,8)
db> where
arstrategy(c7480750,0,c084365f,5c,0) at arstrategy+0x939
g_disk_start(c7470a20,0,c0843c0f,164,a) at g_disk_start+0x1a6
g_io_schedule_down(c29b1000,2,c0843e31,6e,c06036b0) at
g_io_schedule_down+0x1ac
g_down_procbody(0,e0469d48,c0845bd4,314,) at
g_down_procbody+0x48
fork_exit(c06036b0,0,e0469d48) at fork_exit+0xcf
fork_trampoline() at fork_trampoline+0x8
--- trap 0x1, eip = 0, esp = 0xe0469d7c, ebp = 0 ---
db>


Copyright (c) 1992-2003 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 5.1-CURRENT #2: Wed Oct 15 05:44:42 PDT 2003
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP
Preloaded elf kernel "/boot/kernel/kernel" at 0xc0a77000.
Preloaded elf module "/boot/kernel/acpi.ko" at 0xc0a770a8.
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Xeon(TM) CPU 2.40GHz (2392.95-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0xf27  Stepping = 7
  
Features=0xbfebfbff
  Hyperthreading: 2 logical CPUs
real memory  = 1073676288 (1023 MB)
avail memory = 1033580544 (985 MB)
Programming 24 pins in IOAPIC #0
IOAPIC #0 intpin 2 -> irq 0
Programming 24 pins in IOAPIC #1
Programming 24 pins in IOAPIC #2
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
 cpu0 (BSP): apic id:  0, version: 0x00050014, at 0xfee0
 cpu1 (AP):  apic id:  1, version: 0x00050014, at 0xfee0
 cpu2 (AP):  apic id:  6, version: 0x00050014, at 0xfee0
 cpu3 (AP):  apic id:  7, version: 0x00050014, at 0xfee0
 io0 (APIC): apic id:  8, version: 0x00178020, at 0xfec0
 io1 (APIC): apic id:  9, version: 0x00178020, at 0xfec81000
 io2 (APIC): apic id: 10, version: 0x00178020, at 0xfec81400
Pentium Pro MTRR support enabled
ACPI-0660: *** Warning: Type override - [DEB_] had invalid type (Integer) for 
Scope operator, changed to (Scope)
ACPI-0660: *** Warning: Type override - [MLIB] had invalid type (Integer) for 
Scope operator, changed to (Scope)
ACPI-0660: *** Warning: Type override - [DATA] had invalid type (String) for Scope 
operator, changed to (Scope)
ACPI-0660: *** Warning: Type override - [SIO_] had invalid type (String) for Scope 
operator, changed to (Scope)
ACPI-0660: *** Warning: Type override - [LEDP] had invalid type (String) for Scope 
operator, changed to (Scope)
ACPI-0660: *** Warning: Type override - [GPEN] had invalid type (String) for Scope 
operator, changed to (Scope)
ACPI-0660: *** Warning: Type override - [GPST] had invalid type (String) for Scope 
operator, changed to (Scope)
ACPI-0660: *** Warning: Type override - [WUES] had invalid type (String) for Scope 
operator, changed to (Scope)
ACPI-0660: *** Warning: Type override - [WUSE] had invalid type (String) for Scope 
operator, changed to (Scope)
ACPI-0660: *** Warning: Type override - [SBID] had invalid type (String) for Scope 
operator, changed to (Scope)
ACPI-0660: *** Warning: Type override - [SWCE] had invalid type (String) for Scope 
operator, changed to (Scope)
npx0:  on motherboard
npx0: INT 16 interface
acpi0:  on motherboard
ACPI-1287: *** Error: Method execution failed [\\_SB_.PCI0.SBRG.EC0_._REG] (Node 
0xc6993c20), AE_NOT_EXIST
acpi0: Could not initialise SystemIO handler: AE_NOT_EXIST
device_probe_and_attach: acpi0 attach returned 6
pcibios: BIOS version 2.10
Using $PIR table, 19 entries at 0xc00f3060
pcib0:  at pcibus 0 on motherboard
pci0:  on pcib0
IOAPIC #0 intpin 16 -> irq 2
IOAPIC #0 intpin 19 -> irq 16
pci0:  at device 0.1 (no driver attached)
pcib1:  at device 3.0 on pci0
pci2:  on pcib1
pci2:  at device 28.0 (no driver attached)
pcib2:  at device 29.0 on pci2
pci4:  on pcib2
pci2:  at device 30.0 (no driver attached)
pcib3:  at devi

Re: Page faults with today's current

[Arjan van Leeuwen]

On Thursday 16 October 2003 23:00, Jeff Roberson wrote:
> On Thu, 16 Oct 2003, Arjan van Leeuwen wrote:
> > I just cvsupped and installed a new world and kernel (previous kernel was
> > from October 13), and now my machine gets a page fault when I try to run
> > any GTK2 application (Firebird, Gnome 2). Are others seeing this as well?
> >
> > Arjan
>
> If you're running ULE and KSE I just fixed a bug with that.  If not, pleae
> provide a stack trace.  You can manually transcribe one by starting a gtk2
> application from a console with your DISPLAY variable set appropriately.

Yes, I'm using ULE and KSE, but it isn't fixed for me (using rev. 1.65). The 
trace looks like this:

sched_rem(...)  
setrunqueue(...)
sched_wakeup(...)
setrunnable(...)
wakeup(...)
bdone(...)  
bufdone(...)
bufdonebio(...)
biodone(...)
g_dev_done(...)
biodone(...)
g_io_schedule_up(...)
g_up_procbody(...)
fork_exit(...)
fork_trampoline()

Arjan

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

Re: sched_ule.c & SMP error

[Jeff Roberson]

On Thu, 16 Oct 2003, Valentin Chopov wrote:

> I'm getting an error in the sched_ule.c
>
> It looks that sched_add is called with "struct kse" arg. instead of
> "struct thread"

Fixed, thanks.

>
> Thanks,
>
> Val
>
>
> cc -c -O -pipe -march=pentiumpro -Wall -Wredundant-decls -Wnested-externs
> -Wstri
> ct-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual
> -fform
> at-extensions -std=c99  -nostdinc -I-  -I. -I/usr/src/sys
> -I/usr/src/sys/contrib
> /dev/acpica -I/usr/src/sys/contrib/ipfilter -I/usr/src/sys/contrib/dev/ath
> -I/us
> r/src/sys/contrib/dev/ath/freebsd -D_KERNEL -include opt_global.h
> -fno-common -f
> inline-limit=15000 -fno-strict-aliasing  -mno-align-long-strings
> -mpreferred-sta
> ck-boundary=2 -ffreestanding -Werror  /usr/src/sys/kern/sched_ule.c
> /usr/src/sys/kern/sched_ule.c: In function `kseq_move':
> /usr/src/sys/kern/sched_ule.c:465: warning: passing arg 1 of `sched_add'
> from in
> compatible pointer type
> *** Error code 1
>
> Stop in /usr/obj/usr/src/sys/MYKERNEL.
> *** Error code 1
>
> Stop in /usr/src.
> *** Error code 1
>
> Stop in /usr/src.
>
>
> ==
> Valentin S. Chopov, CC[ND]P
> Sys/Net Admin
> SEI Data Inc.
> E-Mail: [EMAIL PROTECTED]
> ==
>
>
> ___
> [EMAIL PROTECTED] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>

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

Re: Page faults with today's current

[Jeff Roberson]

On Thu, 16 Oct 2003, Arjan van Leeuwen wrote:

> I just cvsupped and installed a new world and kernel (previous kernel was from
> October 13), and now my machine gets a page fault when I try to run any GTK2
> application (Firebird, Gnome 2). Are others seeing this as well?
>
> Arjan

If you're running ULE and KSE I just fixed a bug with that.  If not, pleae
provide a stack trace.  You can manually transcribe one by starting a gtk2
application from a console with your DISPLAY variable set appropriately.

Thanks,
Jeff

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

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

Page faults with today's current

[Arjan van Leeuwen]

I just cvsupped and installed a new world and kernel (previous kernel was from 
October 13), and now my machine gets a page fault when I try to run any GTK2 
application (Firebird, Gnome 2). Are others seeing this as well?

Arjan

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

Re: panic: vm_map_wire: lookup failed

[John Hay]

> 
> The latest development source of ntpd started to use setrlimit() before
> using mlockall(). This combination proves fatal on -current. The code
> in ntpd/ntpd.c looks like this:

Ok, I found an easier way to provoke the panic. Just compile the following
program like this:

cc -Wall -O -o vm -lcrypto vm.c

and run as root. The program itself does not use the crypto, but it is
needed to provoke the panic.

# vm.c ##
#include 
#include 

int
main(int argc, char **argv)
{
/*
 * lock the process into memory
 */
if (mlockall(MCL_CURRENT|MCL_FUTURE) < 0)
perror("mlockall()");

return 0;
}
###

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

runningbufspace related lock-ups with md(4)/UFS/SU (PATCH ?)

[Brian Fundakowski Feldman]

I'm having problems where the entire system is locking up when using a MD 
UFS+SoftUpdates partition.  I can simply dd if=/dev/zero of=/mnt/foo and in 
a couple tries it will lock up.  When it locks up, buf_daemon (or if that is 
patched against, syncer) is calling waitrunningbufspace() from a non-B_ASYNC 
buf call.  Because of this, the md(4) ("md0") thread is stuck in "ufs" 
waiting to receive a lock on the vnode that one of the syncer/flusher 
daemons has locked, waiting for bufspace to run down.  The user program 
causing the problem is still stuck in "wdrain" because it's also waiting for 
waitrunningbufspace() to return.  In short, everything wants to try to 
reduce the amount of outstanding buffer space, but nothing moves forward 
while GEOM/md(4)/what have you are waiting for the daemons to let go of the 
vnode so they can write out data.
Does this scenario make sense?  I have fixed it here using the following 
very simple patch, which disables the implicit waitrunningbufspace() calls
so the daemons can't get stuck there.

diff -r1.412 vfs_bio.c
73a74,75
> static struct proc *bufdaemonproc;
>
889c891,893
<   waitrunningbufspace();
---
>   if (curthread->td_proc != bufdaemonproc &&
>   curthread->td_proc != updateproc)
>   waitrunningbufspace();
2038,2039d2041
<
< static struct proc *bufdaemonproc;

-- 
Brian Fundakowski Feldman   \'[ FreeBSD ]''\
  <> [EMAIL PROTECTED]   \  The Power to Serve! \
 Opinions expressed are my own.   \,,\


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

Re: PCcards not working (5.1)

[a]

On Thu, Oct 16, 2003 at 09:32:55AM -0600, M. Warner Losh wrote:
> ...
> : You should use devd instead of pccardd in -current.
> : See devd(8) and devd.conf(8).
> 
> That's one problem, but not the problem.  The problem that he's
> hitting is that he can't get memory to read the card's CIS.  That's
> usually solved with setting hw.cbb.start_memory to a good value.

Hi Warner et al,

What would be a "good value"?

(Sorry if this sounds dumb, but I'm relatively new to FreeBSD, esp. when
it comes to running it on notebooks).

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

Re: IBCS2 compatibility regression in FreeBSD 5??

[Kris Kennaway]

On Thu, Oct 16, 2003 at 09:06:18AM -0400, Paul Mather wrote:
> Does anyone know whether the IBCS2 emulation functionality regressed
> going from FreeBSD 4 to FreeBSD 5?

It's quite possible, because that code is unmaintained.

Kris


pgp0.pgp
Description: PGP signature

Re: hiding e-mail adresses needed badly

[Terry Lambert]

Max Laier wrote:
> Wednesday, October 15, 2003, 1:29:21 PM, you wrote:
> AC> Due to increased activity of SPAM harvesters what are our plans to hide
> AC> our addresses from public WWW? I mean all browseable mailing lists,
> AC> FreeBSD site, CVS via WWW, PRs, ports and docs.
> 
> OT: mail/procmail mail/relaydb mail/spamd mail/bmf ... etc. pp.
> http://www.benzedrine.cx/relaydb.html
> 
> So would you please stop whining and configure your procmail okay.
> What you suggest is "Security Through Obscurity", which does not work!

Cluebat:

Neither does your solution, without having a static IP address
and your own SMTP server with a full time broadband connection.

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

Re: hiding e-mail adresses needed badly

[Terry Lambert]

Steve O'Hara-Smith wrote:
> Peter Schultz <[EMAIL PROTECTED]> wrote:
> > However, since that fateful
> > e-mail I have been viciously attacked by spammers posing as Microsoft
> > security updaters.  These spams include attachments making them all
> > around 150KB in size.  Maybe others of you have seen them?
> 
> Certainly have - they're not spammers it's a worm, called Swen.
> It targets an amazing variety of things, including every email address
> it can get hold of. One of my accounts gets about a hundred a day of
> these *still*. If you get infected it filters your inbox and removes
> attempts to reinfect you so that you don't see it at all.

But you still get to pay to download them.

I got so pissed off, I wrote a program to proactively delete them
out of my mailbox at intervals, without downloading them.

Earthlink often sucks in terms of customer service.  If they would
just designate a couple of common markers as "known SPAM", the
problem would have gone away for me, and a couple million other
people forced to use Earthlink ("forced", because no matter where
I go, Earthlink buys up my damn ISP -- no one talks about *that*
monocoluture being a threat).

Another pain in the ass is that people without direct Internet
connections *somewhere* are stuck with POP3 maildrops going over
quota because of these damn things, which is a denial of service
attack (all messages to you bounce as "over quota", and most of
the mailing list software in the world will auto-unsubscribe you
when that happens).  This is probably the biggest threat to the
Internet yet, since communication in general, and email in
particular, is still *the* killer application for the Internet.

This is an inherent flaw in a store-with-quota+pickup-transiently
model, which is what any POP3/IMAP4 forces their users into, and
that means *any* ISP, even ones that give you full time connections,
when they refuse to let you run your own mail server, either by
explicitly disallowing it, or by not providing you a static IP.  A
non-quotaed maildrop would fix it.  The ISP mail server admins
growing a clue and not transiting executable attachments would fix
it.  And ASMTP would fix it (as long as there wasn't a queue quota).

Again, Earthlink is no help, since they transit these damn
things to the maildrop, against their customer's will, and, for
most of their customers, this means propagating the damn things
further.

Can you imagine if someone wrote one of these things to *actively*
target an ISP with a stupid network topology like Earthlink?  You
could drive the company out of business by chasing all their
subscribers away by denying them the ability to receive communications
from almost anyone else on the Internet.  I'm really surprised these
idiots are unwilling to do anything about saving their business model
from extinction.

In any case, my suggestion is that you write a program to delete off
files with certain sizes from a "list" and/or certain content from a
"head", and find a kind soul you trust to not abuse your password,
which would have to be cleartext somewhere (command line or compiled
in), and have the worms deleted out before they become an issue for
you.

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

Re: panics during installation of -CURRENT on Thinkpad A31p

[Daniel Lang]

Hi Folks,

Daniel Lang wrote on Thu, Oct 16, 2003 at 02:15:56PM +0200:
[..]
> A current snapshot, like 5.1-CURRENT-20031015-JPSNAP
> boots correctly and sysinstall starts. A trap is encountered
> as soon as I try to configure any of the two network interfaces.
> fxp0 and a wi0 are detected. 
> ACPI enabled or not again makes no difference.
> 
> If I try to configure them using DHCP or even manually
> configure them, I get traps like the following:
> [..]
> kernel: type 18 trap, code=0
> stopped at  cbb_intr+0x22: movl %eax,%esi
> db> trace
> cbb_intr(c2114e00,0,c083b22c,230,c4bfd000) at cbb_intr+0x22
> ithread_loop(c4c07980,d7963d48,c083b09e,314,0) at ithread_loop+0x192
> fork_exit(c0623c60,c4c07980,d7963d48) at fork_exit+0xcf
> fork_trampoline() at fork_trampoline+0x8
> --- trap 0x1, eip = 0, esp = 0xd7963d7c, ebp = 0 ---
> 
> This one was encountered while trying to set up fxp0 with DHCP.
[..]

I managed to install the snapshot from CD and provoke
the panics with a manual ifconfig. Thus I could obtain
crash dumps, which I have sort-of analysed.

I've filed a PR with all the details (stack trace with
symbols, analysed some variables, etc): kern/58139
Please check it out:

http://www.freebsd.org/cgi/query-pr.cgi?pr=58139

Thanks for your help.

Best regards,
 Daniel
-- 
IRCnet: Mr-Spock   - Burn them to ashes, then burn the ashes. -  
 Daniel Lang * [EMAIL PROTECTED] * +49 89 289 18532 * http://www.leo.org/~dl/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

sched_ule.c & SMP error

[Valentin Chopov]

I'm getting an error in the sched_ule.c

It looks that sched_add is called with "struct kse" arg. instead of
"struct thread"

Thanks,

Val


cc -c -O -pipe -march=pentiumpro -Wall -Wredundant-decls -Wnested-externs
-Wstri
ct-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual
-fform
at-extensions -std=c99  -nostdinc -I-  -I. -I/usr/src/sys
-I/usr/src/sys/contrib
/dev/acpica -I/usr/src/sys/contrib/ipfilter -I/usr/src/sys/contrib/dev/ath
-I/us
r/src/sys/contrib/dev/ath/freebsd -D_KERNEL -include opt_global.h
-fno-common -f
inline-limit=15000 -fno-strict-aliasing  -mno-align-long-strings
-mpreferred-sta
ck-boundary=2 -ffreestanding -Werror  /usr/src/sys/kern/sched_ule.c
/usr/src/sys/kern/sched_ule.c: In function `kseq_move':
/usr/src/sys/kern/sched_ule.c:465: warning: passing arg 1 of `sched_add'
from in
compatible pointer type
*** Error code 1

Stop in /usr/obj/usr/src/sys/MYKERNEL.
*** Error code 1

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

Stop in /usr/src.


==
Valentin S. Chopov, CC[ND]P
Sys/Net Admin
SEI Data Inc.
E-Mail: [EMAIL PROTECTED]
==


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

Re: PATCH for ATAng

[Kevin Oberman]

> Date: Thu, 16 Oct 2003 23:17:47 +0900
> From: Hiroyuki Aizu <[EMAIL PROTECTED]>
> Sender: [EMAIL PROTECTED]
> 
> This is a multi-part message in MIME format.
> 
> --Multipart_Thu__16_Oct_2003_23_17_47_+0900_0865e200
> Content-Type: text/plain; charset=US-ASCII
> Content-Transfer-Encoding: 7bit
> 
> Hi.
> 
> The original ata_reset() lost ATA-master drive and remove main file system
> after suspend/resume. Of cource it occors panic!
> I think that the ata_reset() in ata-lowlevel.c is bogus and I can not
> understand the code. So I study ATA and rewrite ata_reset() completely.
> 
> New device detect algorism using ata command ATA_IDENTIFY_DEVICE and
> ATA_IDENTIFY_PACKET_DEVICE for judge ATA and ATAPI devices.
> 
> This patch works fine with my TOSHIBA Libretto L5. 
> But not yet test ATAPI devices and ATA-slave channel.
> Maybe there is need to adjust wait DELAY time.
> 
> Please test and replace ata_reset().
> 
> I hope this solve ATAng troubles.

I applied your patch and rebuilt my kernel on my ThinkPad T30 and the
behavior is changed, but not really improved.

Now, instead of hanging after "ata0: resetting devices .."
I now get:
ata0: Resetting devices ..
GEOM: destroy disk ad0 dp=0xc4945d70
ad0: WARNING - removed from configuration
done
ata1: resetting devices ..
ata1: check for dev existence:lsb=00 msb=00
ata1: check for dev existence:lsb=00 msb=00
done

I have only one ATA device which is master on ata0. (ad0).

Thanks for trying.
-- 
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: [EMAIL PROTECTED]   Phone: +1 510 486-8634
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Asus A7V8X-X USB problems

[Doug White]

On Wed, 15 Oct 2003, Greg J. wrote:

> > > > What's attached to the ports?
> > > Nothing.. if I plug anything in (like a mouse) it freezes my system.
> >
> > Interesting .. which VIA chipset is it? I have a KT400 at home that
> > hasn't built current in a while but worked as of a few weeks ago. I'll
> > have to try a fresh build.
>
> KT400 here too.. also, were you able to get 'shutdown -p now' to work?
> For some reason it times out on me.

Yeah, it started getting flakey on me after jhb commited some stuff to the
ACPI tree.  I haven't taken the time to track it down, though.

-- 
Doug White|  FreeBSD: The Power to Serve
[EMAIL PROTECTED]  |  www.FreeBSD.org
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: PCcards not working (5.1)

[a]

> > 
> > Oct 15 09:19:16 beastie pccardd[507]: fatal error: no PC-CARD slots
> > Oct 15 09:19:23 beastie kernel: pccard0: can't alloc memory to read attributes
> > Oct 15 09:19:23 beastie kernel: pccard0: CARD ERROR!
> > Oct 15 09:19:23 beastie kernel: cbb0: PC Card card activation failed
> > 
> > ...
> > ...
> 
> You should use devd instead of pccardd in -current.
> See devd(8) and devd.conf(8).
> 

I tried using "devd" (starting it from the commandline) - same errors
as outlined above. Also tried with a kernel that's based on "OLDCARD" -
again same errors. BTW, the manpage for devd.conf(5) doesn't give any explict
examples/hints - at least in my version...

Just to make sure it's not a HW-problem: I've tried using the same PCcards
under both Linux and FreeBSD 4.8 - no problems at all.

In case it's a problem with the devd.conf - do you have any pointers on 
how to set up a proper config file for devd using the follwing cards
Cisco Aironet 250 (WLAN)
Elsa Airlancer MC11 (WLAN)
Xircom 10/100 (Ethernet)

TIA for your help
-ewald
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

dummynet: warning, refcnt now -1, decreasing

[Bernd Walter]

I get several of these messages with a recent -current:
Oct 16 17:38:35 cicely6 kernel: dummynet: warning, refcnt now 0, decreasing
Oct 16 17:38:36 cicely6 last message repeated 2 times
Oct 16 17:38:36 cicely6 kernel: dummynet: warning, refcnt now -1, decreasing
Oct 16 17:38:36 cicely6 kernel: dummynet: warning, refcnt now 0, decreasing
Oct 16 17:38:36 cicely6 last message repeated 15 times
Oct 16 17:38:36 cicely6 kernel: dummynet: warning, refcnt now -1, decreasing
Oct 16 17:38:36 cicely6 kernel: dummynet: warning, refcnt now 0, decreasing
Oct 16 17:38:36 cicely6 last message repeated 7 times
Oct 16 17:38:36 cicely6 kernel: dummynet: warning, refcnt now -1, decreasing
Oct 16 17:38:36 cicely6 kernel: dummynet: warning, refcnt now 0, decreasing
Oct 16 17:38:36 cicely6 last message repeated 4 times
Oct 16 17:38:36 cicely6 kernel: dummynet: warning, refcnt now -1, decreasing
Oct 16 17:38:36 cicely6 kernel: dummynet: warning, refcnt now 0, decreasing
Oct 16 17:38:36 cicely6 last message repeated 11 times
Oct 16 17:38:36 cicely6 kernel: dummynet: warning, refcnt now -1, decreasing
Oct 16 17:38:36 cicely6 kernel: dummynet: warning, refcnt now 0, decreasing

-- 
B.Walter   BWCThttp://www.bwct.de
[EMAIL PROTECTED]  [EMAIL PROTECTED]

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

Re: PCcards not working (5.1)

[M. Warner Losh]

In message: <[EMAIL PROTECTED]>
Daniel Eischen <[EMAIL PROTECTED]> writes:
: On Wed, 15 Oct 2003 [EMAIL PROTECTED] wrote:
: 
: > Hi,
: > 
: > I'm running into a problem wrt PCcards under 5.1.
: > 
: > First, here's what I've got:
: > Compaq Evo N610c, 1GB RAM, 40GB HD, latest BIOS
: > SW: FreeBSD 5.1
: > 
: > The problem: The PCCard-slots are recognized upon boot but when I
: > insert a card into any of the two slots I get an error message,
: > telling me that there's no pccard slot present.
: > 
: > (excert from /var/log/messages)
: > 
: > Oct 15 09:19:16 beastie pccardd[507]: fatal error: no PC-CARD slots
: > Oct 15 09:19:23 beastie kernel: pccard0: can't alloc memory to read attributes
: > Oct 15 09:19:23 beastie kernel: pccard0: CARD ERROR!
: > Oct 15 09:19:23 beastie kernel: cbb0: PC Card card activation failed
: > 
: > When I try to start pccardd by hand, even using "pccardd -d" it dies
: > immediately with the same error message.
: 
: You should use devd instead of pccardd in -current.
: See devd(8) and devd.conf(8).

That's one problem, but not the problem.  The problem that he's
hitting is that he can't get memory to read the card's CIS.  That's
usually solved with setting hw.cbb.start_memory to a good value.

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

Re: PATCH for ATAng

[Hidetoshi Shimokawa]

At Thu, 16 Oct 2003 23:17:47 +0900,
Hiroyuki Aizu wrote:
> 
> [1  ]
> Hi.
> 
> The original ata_reset() lost ATA-master drive and remove main file system
> after suspend/resume. Of cource it occors panic!
> I think that the ata_reset() in ata-lowlevel.c is bogus and I can not
> understand the code. So I study ATA and rewrite ata_reset() completely.
> 
> New device detect algorism using ata command ATA_IDENTIFY_DEVICE and
> ATA_IDENTIFY_PACKET_DEVICE for judge ATA and ATAPI devices.
> 
> This patch works fine with my TOSHIBA Libretto L5. 
> But not yet test ATAPI devices and ATA-slave channel.
> Maybe there is need to adjust wait DELAY time.
> 
> Please test and replace ata_reset().
> 
> I hope this solve ATAng troubles.
> 
> --
> Hiroyuki Aizu
> [2 ata-lowlevel.c.diff ]

This patch fixes resume problem of my laptop (Toshiba Tecra).

Thanks,

/\ Hidetoshi Shimokawa
\/  [EMAIL PROTECTED]
PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

PATCH for ATAng

[Hiroyuki Aizu]

Hi.

The original ata_reset() lost ATA-master drive and remove main file system
after suspend/resume. Of cource it occors panic!
I think that the ata_reset() in ata-lowlevel.c is bogus and I can not
understand the code. So I study ATA and rewrite ata_reset() completely.

New device detect algorism using ata command ATA_IDENTIFY_DEVICE and
ATA_IDENTIFY_PACKET_DEVICE for judge ATA and ATAPI devices.

This patch works fine with my TOSHIBA Libretto L5. 
But not yet test ATAPI devices and ATA-slave channel.
Maybe there is need to adjust wait DELAY time.

Please test and replace ata_reset().

I hope this solve ATAng troubles.

--
Hiroyuki Aizu


ata-lowlevel.c.diff
Description: Binary data
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

NVIDIA nForce MCP network driver - now supports CURRENT

[Q]

To those of you using motherboards based on the NVIDIA nForce chipsets,
I have recently added support for CURRENT to my nForce MCP ethernet
driver.

The details can be found here:

http://www.onthenet.com.au/~q/nvnet


-- 

Seeya...Q

   -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  _  /   Quinton Dolan [EMAIL PROTECTED]
  __  __/  /   /   __/   /  /  
 /__  /   _//  / Gold Coast, QLD, Australia
  __/  __/ __/ /   /   -  / Ph: +61 419 729 806
___  /  
_\



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

Intel 1000/PRO (em) problem

[Terrence Koeman]

Hi,

I'm experiencing a problem with the em driver in 5.1-CURRENT for my Intel 1000/Pro 
fiber Gbit adapter.

The following is recorded in the syslog:

Oct 15 18:17:49 shaolin kernel: em0: watchdog timeout -- resetting
Oct 15 18:30:25 shaolin kernel: em0: watchdog timeout -- resetting
Oct 15 18:30:27 shaolin kernel: em0: Link is Down
Oct 15 18:30:27 shaolin kernel: em0: Link is up 1000 Mbps Full Duplex
Oct 15 18:31:14 shaolin kernel: em0: watchdog timeout -- resetting
Oct 15 18:44:35 shaolin kernel: em0: watchdog timeout -- resetting
Oct 15 18:44:37 shaolin kernel: em0: Link is Down
Oct 15 18:44:37 shaolin kernel: em0: Link is up 1000 Mbps Full Duplex
Oct 15 22:13:54 shaolin kernel: em0: watchdog timeout -- resetting
Oct 16 02:18:10 shaolin kernel: em0: watchdog timeout -- resetting
Oct 16 02:28:33 shaolin kernel: em0: watchdog timeout -- resetting
Oct 16 04:51:46 shaolin kernel: em0: watchdog timeout -- resetting
Oct 16 05:58:20 shaolin kernel: em0: watchdog timeout -- resetting
Oct 16 05:58:22 shaolin kernel: em0: Link is Down
Oct 16 05:58:22 shaolin kernel: em0: Link is up 1000 Mbps Full Duplex
Oct 16 08:06:26 shaolin kernel: em0: watchdog timeout -- resetting
Oct 16 12:10:01 shaolin kernel: em0: watchdog timeout -- resetting
Oct 16 12:10:03 shaolin kernel: em0: Link is Down
Oct 16 12:10:04 shaolin kernel: em0: Link is up 1000 Mbps Full Duplex
Oct 16 13:44:00 shaolin kernel: em0: watchdog timeout -- resetting
Oct 16 13:44:02 shaolin kernel: em0: Link is Down
Oct 16 13:44:02 shaolin kernel: em0: Link is up 1000 Mbps Full Duplex
Oct 16 14:25:31 shaolin kernel: em0: watchdog timeout -- resetting
Oct 16 14:27:01 shaolin kernel: em0: watchdog timeout -- resetting
Oct 16 14:28:41 shaolin kernel: em0: watchdog timeout -- resetting
Oct 16 14:28:43 shaolin kernel: em0: Link is Down
Oct 16 14:28:44 shaolin kernel: em0: Link is up 1000 Mbps Full Duplex
Oct 16 14:43:30 shaolin kernel: em0: watchdog timeout -- resetting
Oct 16 14:46:57 shaolin kernel: em0: watchdog timeout -- resetting
Oct 16 14:46:59 shaolin kernel: em0: Link is Down
Oct 16 14:46:59 shaolin kernel: em0: Link is up 1000 Mbps Full Duplex
Oct 16 14:51:17 shaolin kernel: em0: watchdog timeout -- resetting
Oct 16 14:51:43 shaolin kernel: em0: watchdog timeout -- resetting
Oct 16 14:51:45 shaolin kernel: em0: Link is Down
Oct 16 14:51:45 shaolin kernel: em0: Link is up 1000 Mbps Full Duplex
Oct 16 14:53:32 shaolin kernel: em0: watchdog timeout -- resetting
Oct 16 15:15:44 shaolin kernel: em0: watchdog timeout -- resetting
Oct 16 15:28:33 shaolin kernel: em0: watchdog timeout -- resetting

Everytime it does that connectivity is lost for 2-3 minutes.

I have found a similar problem at 
http://lists.freebsd.org/pipermail/freebsd-stable/2003-April/000539.html but that 
problem seems to be solved long ago, and the fix described in the thread doesn't help 
me.

I have tried to use some older drivers, but none would solve the problem.

Does anyone have an idea how to solve this?

Thanks in advance!

dmesg:

FreeBSD 5.1-CURRENT #12: Mon Oct 13 23:34:55 CEST 2003
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/SHAOLIN
Preloaded elf kernel "/boot/kernel/kernel" at 0xc040d000.
Preloaded elf module "/boot/kernel/acpi.ko" at 0xc040d1cc.
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel Pentium III (601.37-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0x681  Stepping = 1
  
Features=0x383f9ff
real memory  = 1073725440 (1023 MB)
avail memory = 1038782464 (990 MB)
Pentium Pro MTRR support enabled
npx0: [FAST]
npx0:  on motherboard
npx0: INT 16 interface
acpi0:  on motherboard
pcibios: BIOS version 2.10
Using $PIR table, 8 entries at 0xc00f0e80
acpi0: Power Button (fixed)
Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0xe408-0xe40b on acpi0
acpi_cpu0:  on acpi0
acpi_button0:  on acpi0
pcib0:  port 0xcf8-0xcff on acpi0
pci0:  on pcib0
pcib0: slot 9 INTA is routed to irq 12
pcib1:  at device 1.0 on pci0
pci1:  on pcib1
isab0:  at device 4.0 on pci0
isa0:  on isab0
atapci0:  port 0xd800-0xd80f at device 4.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata0: [MPSAFE]
ata1: at 0x170 irq 15 on atapci0
ata1: [MPSAFE]
pci0:  at device 4.2 (no driver attached)
pci0:  at device 4.3 (no driver attached)
pci0:  at device 9.0 (no driver attached)
xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0xd000-0xd07f mem 0xe580-0xe580007f 
at device 10.0 on pci0
pcib0: slot 10 INTA is routed to irq 9
xl0: Ethernet address: 00:04:76:9b:e7:b4
miibus0:  on xl0
xlphy0: <3Com internal media interface> on miibus0
xlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
em0:  mem 
0xe500-0xe501 at device 12.0 on pci0
pcib0: slot 12 INTA is routed to irq 11
em0:  Speed:1000 Mbps  Duplex:Full
fdc0:  port 0x3f7,0x3f2-0x3f5 
irq 6 drq 2 on acpi0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
sio0 port 0x3f8-0x3ff irq 4 on acpi0
sio0: type 16550A
atkbdc0:  port 0x64,0x60 irq 1 on acpi0
orm0:  

Re: kobj.h changes make buildkernel broken

[Doug Rabson]

On Thu, 2003-10-16 at 14:23, Jun Su wrote:
> Seems Tools\makeobjops.awk needs some update.

Sorry about that - I forgot to commit that bit.



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

kobj.h changes make buildkernel broken

[Jun Su]

Seems Tools\makeobjops.awk needs some update.

error log:
%make
cc -c -O -pipe -march=pentium3 -Wall -Wredundant-decls -Wnested-externs 
-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual 
-fformat-extensions -std=c99 -g -nostdinc -I- -I. 
-I/usr/home/junsu/workshop/sys-newpid 
-I/usr/home/junsu/workshop/sys-newpid/contrib/dev/acpica 
-I/usr/home/junsu/workshop/sys-newpid/contrib/ipfilter 
-I/usr/home/junsu/workshop/sys-newpid/contrib/dev/ath 
-I/usr/home/junsu/workshop/sys-newpid/contrib/dev/ath/freebsd -D_KERNEL -include 
opt_global.h -finline-limit=15000 -fno-strict-aliasing -mno-align-long-strings 
-mpreferred-stack-boundary=2 -ffreestanding -Wno-inline 
/usr/home/junsu/workshop/sys-newpid/i386/i386/genassym.c
NM=nm sh /usr/home/junsu/workshop/sys-newpid/kern/genassym.sh genassym.o > assym.s
cc -c -x assembler-with-cpp -DLOCORE -O -pipe -march=pentium3 -Wall -Wredundant-decls 
-Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline 
-Wcast-qual  -fformat-extensions -std=c99 -g -nostdinc -I-  -I. 
-I/usr/home/junsu/workshop/sys-newpid 
-I/usr/home/junsu/workshop/sys-newpid/contrib/dev/acpica 
-I/usr/home/junsu/workshop/sys-newpid/contrib/ipfilter 
-I/usr/home/junsu/workshop/sys-newpid/contrib/dev/ath 
-I/usr/home/junsu/workshop/sys-newpid/contrib/dev/ath/freebsd -D_KERNEL -include 
opt_global.h -fno-common -finline-limit=15000 -fno-strict-aliasing  
-mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Werror 
/usr/home/junsu/workshop/sys-newpid/i386/i386/locore.s
awk -f /usr/home/junsu/workshop/sys-newpid/tools/makeobjops.awk 
/usr/home/junsu/workshop/sys-newpid/kern/device_if.m -c
awk -f /usr/home/junsu/workshop/sys-newpid/tools/makeobjops.awk 
/usr/home/junsu/workshop/sys-newpid/kern/device_if.m -h
awk -f /usr/home/junsu/workshop/sys-newpid/tools/makeobjops.awk 
/usr/home/junsu/workshop/sys-newpid/kern/bus_if.m -h
awk -f /usr/home/junsu/workshop/sys-newpid/tools/makeobjops.awk 
/usr/home/junsu/workshop/sys-newpid/kern/device_if.m -c ;  cc -c -O -pipe 
-march=pentium3 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -fformat-extensions 
-std=c99 -g -nostdinc -I-  -I. -I/usr/home/junsu/workshop/sys-newpid 
-I/usr/home/junsu/workshop/sys-newpid/contrib/dev/acpica 
-I/usr/home/junsu/workshop/sys-newpid/contrib/ipfilter 
-I/usr/home/junsu/workshop/sys-newpid/contrib/dev/ath 
-I/usr/home/junsu/workshop/sys-newpid/contrib/dev/ath/freebsd -D_KERNEL -include 
opt_global.h -fno-common -finline-limit=15000 -fno-strict-aliasing  
-mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Werror  
device_if.c
device_if.c:38: warning: initialization from incompatible pointer type
device_if.c:42: warning: initialization from incompatible pointer type
device_if.c:46: warning: initialization from incompatible pointer type
device_if.c:50: warning: initialization from incompatible pointer type
device_if.c:54: warning: initialization from incompatible pointer type
device_if.c:58: warning: initialization from incompatible pointer type
device_if.c:62: warning: initialization from incompatible pointer type
*** Error code 1
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: IBCS2 compatibility regression in FreeBSD 5??

[Lukas Ertl]

On Thu, 16 Oct 2003, Paul Mather wrote:

> Does anyone know whether the IBCS2 emulation functionality regressed
> going from FreeBSD 4 to FreeBSD 5?  I ask because I have a
> statically-linked SCO binary that works under FreeBSD 4.8-STABLE but
> not under FreeBSD 5.1-RELEASE-p10 (or a version of 5.1-CURRENT).
> (This binary is the statically-linked SCO ADSM V2 client---practically
> the only solution for doing Tivoli TSM backup/archive under FreeBSD.)

I have exactly the same problem - the SCO ADSM client just borks.  I
managed to get around using the Linux client and some nullfs remounts -
ugly, but works more or less.

I've already written IBM, and of course they do not plan to release a
native client :-/.

regards,
le

-- 
Lukas Ertl eMail: [EMAIL PROTECTED]
UNIX Systemadministrator   Tel.:  (+43 1) 4277-14073
Vienna University Computer Center  Fax.:  (+43 1) 4277-9140
University of Vienna   http://mailbox.univie.ac.at/~le/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: hiding e-mail adresses needed badly

[Max Laier]

Hello Andrey,

Wednesday, October 15, 2003, 1:29:21 PM, you wrote:
AC> Due to increased activity of SPAM harvesters what are our plans to hide
AC> our addresses from public WWW? I mean all browseable mailing lists,
AC> FreeBSD site, CVS via WWW, PRs, ports and docs.

AC> As I think, simple  form will be enough to stop
AC> them.

OT: mail/procmail mail/relaydb mail/spamd mail/bmf ... etc. pp.
http://www.benzedrine.cx/relaydb.html

So would you please stop whining and configure your procmail okay.
What you suggest is "Security Through Obscurity", which does not work!

-- 
Best regards,
 Maxmailto:[EMAIL PROTECTED]
^^^SPAM HERE!!! =)

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

[current tinderbox] failure on sparc64/sparc64

[Tinderbox]

TB --- 2003-10-16 11:27:15 - tinderbox 2.2 running on cueball.rtp.FreeBSD.org
TB --- 2003-10-16 11:27:15 - starting CURRENT tinderbox run for sparc64/sparc64
TB --- 2003-10-16 11:27:15 - 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-10-16 11:29:06 - building world
TB --- cd /home/des/tinderbox/CURRENT/sparc64/sparc64/src
TB --- /usr/bin/make -B buildworld
>>> Rebuilding the temporary build tree
>>> stage 1.1: legacy release compatibility shims
>>> stage 1.2: bootstrap tools
>>> stage 2.1: cleaning up the object tree
>>> stage 2.2: rebuilding the object tree
>>> stage 2.3: build tools
>>> stage 3: cross tools
>>> stage 4.1: populating 
>>> /home/des/tinderbox/CURRENT/sparc64/sparc64/obj/sparc64/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/i386/usr/include
>>> stage 4.2: building libraries
>>> stage 4.3: make dependencies
>>> stage 4.4: building everything..
TB --- 2003-10-16 12:23:34 - building generic kernel
TB --- cd /home/des/tinderbox/CURRENT/sparc64/sparc64/src
TB --- /usr/bin/make buildkernel KERNCONF=GENERIC
>>> Kernel build for GENERIC started on Thu Oct 16 12:23:34 GMT 2003
[...]
awk -f 
/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/tools/makeobjops.awk 
/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/kern/device_if.m -c ;  
cc -c -O -pipe  -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -fformat-extensions 
-std=c99 -g -nostdinc -I-  -I. 
-I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys 
-I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/acpica 
-I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/ipfilter 
-I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath 
-I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath/freebsd
 -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 -fno-strict-aliasing 
 -mcmodel=medlow -msoft-float -ffreestanding -Werror  device_if.c
device_if.c:38: warning: initialization from incompatible pointer type
device_if.c:42: warning: initialization from incompatible pointer type
device_if.c:46: warning: initialization from incompatible pointer type
device_if.c:50: warning: initialization from incompatible pointer type
device_if.c:54: warning: initialization from incompatible pointer type
device_if.c:58: warning: initialization from incompatible pointer type
device_if.c:62: warning: initialization from incompatible pointer type
*** Error code 1

Stop in 
/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/obj/sparc64/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/GENERIC.
*** Error code 1

Stop in /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src.
*** Error code 1

Stop in /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src.
TB --- 2003-10-16 12:25:11 - TB --- /usr/bin/make returned exit code  1 
TB --- 2003-10-16 12:25:11 - TB --- ERROR: failed to build generic kernel
TB --- 2003-10-16 12:25:11 - tinderbox aborted

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

panics during installation of -CURRENT on Thinkpad A31p

[Daniel Lang]

Hi,

I just got a Thinkpad A31p on which I try to install -current.

I've tried several snapshots:

5.1-RELEASE panics during kernel boot, while trying to
create a firewire0 device. ACPI enabled or not makes
no difference.

A current snapshot, like 5.1-CURRENT-20031015-JPSNAP
boots correctly and sysinstall starts. A trap is encountered
as soon as I try to configure any of the two network interfaces.
fxp0 and a wi0 are detected. 
ACPI enabled or not again makes no difference.

If I try to configure them using DHCP or even manually
configure them, I get traps like the following:
[..]
kernel: type 18 trap, code=0
stopped at  cbb_intr+0x22: movl %eax,%esi
db> trace
cbb_intr(c2114e00,0,c083b22c,230,c4bfd000) at cbb_intr+0x22
ithread_loop(c4c07980,d7963d48,c083b09e,314,0) at ithread_loop+0x192
fork_exit(c0623c60,c4c07980,d7963d48) at fork_exit+0xcf
fork_trampoline() at fork_trampoline+0x8
--- trap 0x1, eip = 0, esp = 0xd7963d7c, ebp = 0 ---

This one was encountered while trying to set up fxp0 with DHCP.

4.9-RC2 seems to work flawless on this hardware. I can use
both fxp0 and wi0 interfaces. However I would prefer to run
5.x, and I guess you folks would like to have feedback about
configurations resulting in panics.

Thanks and best regards,
 Daniel
-- 
IRCnet: Mr-Spock- "Do you love yourself ?" - "Yes!" (Isar 12) -  
 Daniel Lang * [EMAIL PROTECTED] * +49 89 289 18532 * http://www.leo.org/~dl/


smime.p7s
Description: S/MIME cryptographic signature

Re: More ULE bugs fixed.

[Eirik Oeverby]

Jeff Roberson wrote:
On Thu, 16 Oct 2003, Eirik Oeverby wrote:


Jeff Roberson wrote:

On Wed, 15 Oct 2003, Eirik Oeverby wrote:



Eirik Oeverby wrote:


Jeff Roberson wrote:



I fixed two bugs that were exposed due to more of the kernel running
outside of Giant.  ULE had some issues with priority propagation that
stopped it from working very well.
Things should be much improved.  Feedback, as always, is welcome.  I'd
like to look into making this the default scheduler for 5.2 if things
start looking up.  I hope that scares you all into using it more. :-)


Hi..
Just tested, so far it seems good. System CPU load is floored (near 0),
system is very responsive, no mouse sluggishness or random
mouse/keyboard input.
Doing a make -j 20 buildworld now (on my 1ghz p3 thinkpad ;), and
running some SQLServer stuff in VMWare. We'll see how it fares.
Hi, just a followup message.
I'm now running the buildworld mentioned above, and the system is pretty
much unusable. It exhibits the same symptoms as I have mentioned before,
mouse jumpiness, bogus mouse input (movement, clicks), and the system is
generally very jerky and unresponsive. This is particularily evident
when doing things like webpage loading/browsing/rendering, but it's
noticeable all the time, no matter what I am doing. As an example, the
last sentence I wote without seeing a single character on screen before
I was finsihed writing it, and it appeared with a lot more typos than I
usually make ;)
I'm running *without* invariants and witness right now, i.e. a kernel
100% equal to the SCHED_4BSD kernel.


Can you confirm the revision of your sys/kern/sched_ule.c file?  How does
SCHED_4BSD respond in this same test?
Yes I can. From file:
__FBSDID("$FreeBSD: src/sys/kern/sched_ule.c,v 1.59 2003/10/15 07:47:06
jeff Exp $");
I am running SCHED_4BSD now, with a make -j 20 buildworld running, and I
do not experience any of the problems. Keyboard and mouse input is
smooth, and though apps run slightly slower due to the massive load on
the system, there is none of the jerkiness I have seen before.
Anything else I can do to help?


Yup, try again. :-)  I found another bug and tuned some parameters of the
scheduler.  The bug was introduced after I did my paper for BSDCon and so
I never ran into it when I was doing serious stress testing.
Hopefully this will be a huge improvement.  I did a make -j16 buildworld
and used mozilla while in kde2.  It was fine unless I tried to scroll
around rapidly in a page full of several megabyte images for many minutes.
It is. Still not perfect, but now it's somewhere around the 4BSD mark I 
would say. Think about 'make buildworld' is that it doesn't get real 
tough before it hits some of the larger directories, like the crypto 
stuff etc., where there are many .c files in one dir - before it gets 
that far, there are at most 2 or 3 cc1 processes going concurrently.
As soon as I get 10-20 of them, things start getting sluggish, but I 
suppose it's hard to avoid that. What disturbs me somewhat, though, is 
that I get some of this sluggishness (and other symptoms i've mentioned 
before) even when i'm running 'nice -n 20 make -j 20 buildworld' .. 
meaning the cc1 processes and all that are running (very) nice. The fact 
that I still have issues even when doing that, would lead me to think 
the problem is somewhere else than in the scheduler..
Now I can't say I'm completely sure if this is also the case with 4BSD - 
I only tested the nice stuff after the last reboot.

But all in all, things are better now than yesterday morning. Kudos!

/Eirik

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

Re: hiding e-mail adresses needed badly

[Nikolay Pavlov]

Hi, Peter.

PS> At this point in time it's downright irresponsible not to hide our 
PS> addresses.

PS> I've been lurking on this list about a month to get caught up with 
PS> -current issues.  Friday was both the first mail I sent to the list,
PS> and the first use of this e-mail address.  The only incoming mail was 
PS> from the FreeBSD lists I subscribed to.  However, since that fateful 
PS> e-mail I have been viciously attacked by spammers posing as Microsoft 
PS> security updaters.  These spams include attachments making them all 
PS> around 150KB in size.  Maybe others of you have seen them?

I receive such messages about three days. It looks like "the latest version
of security update" with  .exe file in attachment, but KAV detect I-Worm.Swen inside.
And another messages looks like "undelivered mail to" addresses at @aol.com,
@freemail.com and others with Exploit.IFrame in attachment.


Thanks, Nikolay.

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

Re: cvsmirror

[Rus Foster]

Hi,
> *default compress
> pports-all
  ^^ is pports a typo in the file?

Rgds

Rus


-- 
w: http://www.jvds.com  | JVDS Hosting
e: [EMAIL PROTECTED]| Reliable, Stable, C-Panel
t: +44 7919 373537  | Web Hosting
t: 1-888-327-6330   | email: [EMAIL PROTECTED]


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

cvsmirror

[陈志坤]

I had set up a cvsmirror,when i cvsup from another place,it appeare the message 
below,how can i slove it?

Here is the message and my cvs-supfile

su-2.05b# cvsup -g -L 2 ports-supfile 
Parsing supfile "ports-supfile"
Connecting to 211.66.128.25
Connected to 211.66.128.25
Server software version: SNAP_16_1h
Negotiating file attribute support
Exchanging collection information
Server message: Unknown collection "ports-all"
Establishing multiplexed-mode data connection
Skipping collection ports-all/cvs
Running
Shutting down connection to server
Finished successfully
su-2.05b# 

cvs-supfile

*default host=211.66.128.25
*default base=/usr
*default prefix=/usr
*default release=cvs tag=.
*default delete use-rel-suffix

*default compress
pports-all


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

Re: hiding e-mail adresses needed badly

[Erik Trulsson]

On Thu, Oct 16, 2003 at 04:43:27AM -0500, Peter Schultz wrote:
> At this point in time it's downright irresponsible not to hide our 
> addresses.
> 
> I've been lurking on this list about a month to get caught up with 
> -current issues.  Friday was both the first mail I sent to the list,
> and the first use of this e-mail address.  The only incoming mail was 
> from the FreeBSD lists I subscribed to.  However, since that fateful 
> e-mail I have been viciously attacked by spammers posing as Microsoft 
> security updaters.  These spams include attachments making them all 
> around 150KB in size.  Maybe others of you have seen them?

I guess you are referring to the W32.Swen worm?  I guess most people
have seen that one by now.

> 
> As far as I can tell, these guys are targeting the FreeBSD lists, 
> exploiting them terribly!  This list's charter states that spam will be 
> blocked.  Please enforce the list charter, with prejudice.

The FreeBSD lists are not targeted specially.
That worm mainly harvests e-mail addresses from newsgroups (and from
files stored on infected computers.)
There are several mail<->news gateways for this list (and other freebsd
lists), so this is probably where it got your mail-address.
Since these gateways are not under the control of FreeBSD.org there
isn't much that can be done about it.
These spams are mainly not sent through the lists so they can't be
blocked there (even though lots and lots of spam is blocked by the
FreeBSD list servers.)

> 
> It would be best if subscribers could just choose to have their address 
> published or not.  I can understand being so dedicated to the cause that 
> you're willing to take on some spam.  Non-subscribers addresses should 
> definitely not be published.
> 
> Sincerely,
> Pete...
> 
> Wilko Bulte wrote:
> >On Wed, Oct 15, 2003 at 03:29:21PM +0400, Andrey Chernov wrote:
> >
> >
> >I fail to see why this is relevant to -current but OK.. I think that
> >the opportunity to do this has long since passed. Just type your name
> >in Google and see what happens..
> >
> >Wilko
> >
> >
> >>Due to increased activity of SPAM harvesters what are our plans to hide 
> >>our addresses from public WWW? I mean all browseable mailing lists, 
> >>FreeBSD site, CVS via WWW, PRs, ports and docs.

Note that there are many web-archives of the mailing lists. Lots of
them are run by other people.  You need to talk to them too.

> >>
> >>As I think, simple  form will be enough to stop 
> >>them.
> >>

-- 

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

Re: hiding e-mail adresses needed badly

[Steve O'Hara-Smith]

On Thu, 16 Oct 2003 04:43:27 -0500
Peter Schultz <[EMAIL PROTECTED]> wrote:

> However, since that fateful 
> e-mail I have been viciously attacked by spammers posing as Microsoft 
> security updaters.  These spams include attachments making them all 
> around 150KB in size.  Maybe others of you have seen them?

Certainly have - they're not spammers it's a worm, called Swen.
It targets an amazing variety of things, including every email address
it can get hold of. One of my accounts gets about a hundred a day of
these *still*. If you get infected it filters your inbox and removes
attempts to reinfect you so that you don't see it at all.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

RE: FreeBSD 5.1 stability

[Holger Kipp]

Martin Minkus ([EMAIL PROTECTED]) wrote: 
>
>
>Well perhaps I'll hold off making world as I just cvsupped ;)

I have a system here that was last updated approximately 2 days ago,
and it is still working without any problems. Well, it _IS_ an idle
system, though ;-)

>Don't wanna lose any stability...

You _do_ keep the old working kernel and modules, right?

Holger Kipp

>-Original Message-
>From: Garance A Drosihn [mailto:[EMAIL PROTECTED]
>Sent: Thursday, 16 October 2003 03:16
>To: Kris Kennaway; Valery V.Chikalov
>Cc: Martin Minkus; [EMAIL PROTECTED]
>Subject: Re: FreeBSD 5.1 stability
>
> [..]
>I hate to rain on this parade, but that only tells us how reliable 5.x
>was 147 days ago.  5.x remains in a state of flux, and there have been
>many times in the last 147 days where you could cvsup into a very
>unstable system.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: hiding e-mail adresses needed badly

[Peter Schultz]

At this point in time it's downright irresponsible not to hide our 
addresses.

I've been lurking on this list about a month to get caught up with 
-current issues.  Friday was both the first mail I sent to the list,
and the first use of this e-mail address.  The only incoming mail was 
from the FreeBSD lists I subscribed to.  However, since that fateful 
e-mail I have been viciously attacked by spammers posing as Microsoft 
security updaters.  These spams include attachments making them all 
around 150KB in size.  Maybe others of you have seen them?

As far as I can tell, these guys are targeting the FreeBSD lists, 
exploiting them terribly!  This list's charter states that spam will be 
blocked.  Please enforce the list charter, with prejudice.

It would be best if subscribers could just choose to have their address 
published or not.  I can understand being so dedicated to the cause that 
you're willing to take on some spam.  Non-subscribers addresses should 
definitely not be published.

Sincerely,
Pete...
Wilko Bulte wrote:
On Wed, Oct 15, 2003 at 03:29:21PM +0400, Andrey Chernov wrote:

I fail to see why this is relevant to -current but OK.. I think that
the opportunity to do this has long since passed. Just type your name
in Google and see what happens..
Wilko


Due to increased activity of SPAM harvesters what are our plans to hide 
our addresses from public WWW? I mean all browseable mailing lists, 
FreeBSD site, CVS via WWW, PRs, ports and docs.

As I think, simple  form will be enough to stop 
them.

--
Andrey Chernov | http://ache.pp.ru/
---end of quoted text---



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

Re: More ULE bugs fixed.

[Peter Kadau]

Hi !

> Things should be much improved.  Feedback, as always, is welcome. 
Wow ! Smoothly working under a load of approx. 4.
Running gnome2, mozilla, evolution, mplayer and kpdf.
Running portsdb -Uu and a kernel build.
No stuttering mouse, no irritating delays, fast rendering.
That's definitely better than _4BSD.
(UP machine)

Cheers
Peter

-- 
<[EMAIL PROTECTED]>

Campus der Max-Planck-Institute Tübingen
Netzwerk- und Systemadministration

Tel: +49 7071 601 598
Fax: +49 7071 601 616

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

Re: More ULE bugs fixed.

[Jeff Roberson]

On Thu, 16 Oct 2003, Eirik Oeverby wrote:

> Jeff Roberson wrote:
> > On Wed, 15 Oct 2003, Eirik Oeverby wrote:
> >
> >
> >>Eirik Oeverby wrote:
> >>
> >>>Jeff Roberson wrote:
> >>>
> >>>
> I fixed two bugs that were exposed due to more of the kernel running
> outside of Giant.  ULE had some issues with priority propagation that
> stopped it from working very well.
> 
> Things should be much improved.  Feedback, as always, is welcome.  I'd
> like to look into making this the default scheduler for 5.2 if things
> start looking up.  I hope that scares you all into using it more. :-)
> >>>
> >>>
> >>>Hi..
> >>>Just tested, so far it seems good. System CPU load is floored (near 0),
> >>>system is very responsive, no mouse sluggishness or random
> >>>mouse/keyboard input.
> >>>Doing a make -j 20 buildworld now (on my 1ghz p3 thinkpad ;), and
> >>>running some SQLServer stuff in VMWare. We'll see how it fares.
> >>
> >>Hi, just a followup message.
> >>I'm now running the buildworld mentioned above, and the system is pretty
> >>much unusable. It exhibits the same symptoms as I have mentioned before,
> >>mouse jumpiness, bogus mouse input (movement, clicks), and the system is
> >>generally very jerky and unresponsive. This is particularily evident
> >>when doing things like webpage loading/browsing/rendering, but it's
> >>noticeable all the time, no matter what I am doing. As an example, the
> >>last sentence I wote without seeing a single character on screen before
> >>I was finsihed writing it, and it appeared with a lot more typos than I
> >>usually make ;)
> >>
> >>I'm running *without* invariants and witness right now, i.e. a kernel
> >>100% equal to the SCHED_4BSD kernel.
> >
> >
> > Can you confirm the revision of your sys/kern/sched_ule.c file?  How does
> > SCHED_4BSD respond in this same test?
>
> Yes I can. From file:
> __FBSDID("$FreeBSD: src/sys/kern/sched_ule.c,v 1.59 2003/10/15 07:47:06
> jeff Exp $");
> I am running SCHED_4BSD now, with a make -j 20 buildworld running, and I
> do not experience any of the problems. Keyboard and mouse input is
> smooth, and though apps run slightly slower due to the massive load on
> the system, there is none of the jerkiness I have seen before.
>
> Anything else I can do to help?

Yup, try again. :-)  I found another bug and tuned some parameters of the
scheduler.  The bug was introduced after I did my paper for BSDCon and so
I never ran into it when I was doing serious stress testing.

Hopefully this will be a huge improvement.  I did a make -j16 buildworld
and used mozilla while in kde2.  It was fine unless I tried to scroll
around rapidly in a page full of several megabyte images for many minutes.

>
> /Eirik
>
> > Thanks,
> > Jeff
> >
> >
> >>Best regards,
> >>/Eirik
> >>
> >>
> >>___
> >>[EMAIL PROTECTED] mailing list
> >>http://lists.freebsd.org/mailman/listinfo/freebsd-current
> >>To unsubscribe, send any mail to "[EMAIL PROTECTED]"
> >>
> >
> >
> > ___
> > [EMAIL PROTECTED] mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-current
> > To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>
>

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

Re: More ULE bugs fixed.

[Eirik Oeverby]

Jeff Roberson wrote:
On Wed, 15 Oct 2003, Eirik Oeverby wrote:


Eirik Oeverby wrote:

Jeff Roberson wrote:


I fixed two bugs that were exposed due to more of the kernel running
outside of Giant.  ULE had some issues with priority propagation that
stopped it from working very well.
Things should be much improved.  Feedback, as always, is welcome.  I'd
like to look into making this the default scheduler for 5.2 if things
start looking up.  I hope that scares you all into using it more. :-)


Hi..
Just tested, so far it seems good. System CPU load is floored (near 0),
system is very responsive, no mouse sluggishness or random
mouse/keyboard input.
Doing a make -j 20 buildworld now (on my 1ghz p3 thinkpad ;), and
running some SQLServer stuff in VMWare. We'll see how it fares.
Hi, just a followup message.
I'm now running the buildworld mentioned above, and the system is pretty
much unusable. It exhibits the same symptoms as I have mentioned before,
mouse jumpiness, bogus mouse input (movement, clicks), and the system is
generally very jerky and unresponsive. This is particularily evident
when doing things like webpage loading/browsing/rendering, but it's
noticeable all the time, no matter what I am doing. As an example, the
last sentence I wote without seeing a single character on screen before
I was finsihed writing it, and it appeared with a lot more typos than I
usually make ;)
I'm running *without* invariants and witness right now, i.e. a kernel
100% equal to the SCHED_4BSD kernel.


Can you confirm the revision of your sys/kern/sched_ule.c file?  How does
SCHED_4BSD respond in this same test?
Yes I can. From file:
__FBSDID("$FreeBSD: src/sys/kern/sched_ule.c,v 1.59 2003/10/15 07:47:06 
jeff Exp $");
I am running SCHED_4BSD now, with a make -j 20 buildworld running, and I 
do not experience any of the problems. Keyboard and mouse input is 
smooth, and though apps run slightly slower due to the massive load on 
the system, there is none of the jerkiness I have seen before.

Anything else I can do to help?

/Eirik

Thanks,
Jeff

Best regards,
/Eirik
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


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


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