Panic during ata_resume (sound)

2003-01-01 Thread Gavin Atkinson

Another panic. Kernel from 19th Dec. Laptop suspended itself (for no
reason), and upon resume got this: (again, laptop could not manage to do
the dump, so this is hand transcribed)

wakeup from sleeping state (slept 00:02:53)
ata0: resetting devices ..
done
ata1: resetting devices ..
done

Fatal trap 12: page fault while in kernel mode
fault virtual address   = 0x0
fault code  = supervisor read, page not present
instruction pointer = 0x8:0xc01fb093
stack pointer   = 0x10:0xc874db48
frame pointer   = 0x10:0xc874db68
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 = 13 (swi6: tty:sio clock)

Stopped at _mtx_lock_flags + 0x43 cmpl  $0xc03d16a0, 0(ebx)

_mtx_lock_flags() at _mtx_lock_flags+0x43
mixer_reinit() at
ds_ps_resume()
bus_generic_resume()
bus_generic_resume()
bus_generic_resume()
bus_generic_resume()
bus_generic_resume()
apm_resume()
apm_processevent()
apm_do_suspend()
apm_timeout()
softclock()
ithread_loop()
fork_exit()
fork_trampoline()

_mtx_lock_flags+0x43 corresponds to the compare of the line
KASSERT(m-mtx_object.lo_class == lock_class_mtx_sleep, 
in kern_mutex.c. It looks like m == NULL.

I can't get any more information sadly, again the machine hung while
trying to reset ther ATA channel for the dump.

Gavin

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



Re: Panic during ata_resume (sound)

2003-01-01 Thread Soeren Schmidt
It seems Gavin Atkinson wrote:

This looks like a problem in the sound system, as the ATA driver 
prints the last 'done' line it has finished its resume code, and
the trace points at the mixer_reinit func...
That the ATA driver then locks in the dump code can have lots
of reasons, difficult to tell from the info provided

 Another panic. Kernel from 19th Dec. Laptop suspended itself (for no
 reason), and upon resume got this: (again, laptop could not manage to do
 the dump, so this is hand transcribed)
 
 wakeup from sleeping state (slept 00:02:53)
 ata0: resetting devices ..
 done
 ata1: resetting devices ..
 done
 
 Fatal trap 12: page fault while in kernel mode
 fault virtual address   = 0x0
 fault code  = supervisor read, page not present
 instruction pointer = 0x8:0xc01fb093
 stack pointer   = 0x10:0xc874db48
 frame pointer   = 0x10:0xc874db68
 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 = 13 (swi6: tty:sio clock)
 
 Stopped at _mtx_lock_flags + 0x43 cmpl  $0xc03d16a0, 0(ebx)
 
 _mtx_lock_flags() at _mtx_lock_flags+0x43
 mixer_reinit() at
 ds_ps_resume()
 bus_generic_resume()
 bus_generic_resume()
 bus_generic_resume()
 bus_generic_resume()
 bus_generic_resume()
 apm_resume()
 apm_processevent()
 apm_do_suspend()
 apm_timeout()
 softclock()
 ithread_loop()
 fork_exit()
 fork_trampoline()
 
 _mtx_lock_flags+0x43 corresponds to the compare of the line
 KASSERT(m-mtx_object.lo_class == lock_class_mtx_sleep, 
 in kern_mutex.c. It looks like m == NULL.
 
 I can't get any more information sadly, again the machine hung while
 trying to reset ther ATA channel for the dump.
 
 Gavin
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-current in the body of the message
 

-Søren

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



5.0-RC2 installation problem? report

2003-01-01 Thread Paulius Bulotas
Hello list,

today I tried to install from 5.0-RC2 cd to my 4-STABLE partition (at
first deleting it). I was unable to create UFS2 fs from disklabel,
because when adding Newfs flags or custom newfs -O 2, the newfs failed
with some error (had to do it manually from fixit).
Then, after selecting Minimal distribution set, everything was extracted
to / and not /mnt, what wasn't what someone would expect ;) Again helped
rescue shell and manually running install.sh from base and crypto dirs
in cd.
Maybe these issues are not new? (as 5.0-RC2 is here for some time).

Except that, everything works (for the moment ;)

Regards,
Paulius Bulotas

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



Re: alpha tinderbox failure

2003-01-01 Thread Mike Barcroft
Dag-Erling Smorgrav [EMAIL PROTECTED] writes:
 === vinum
 Makefile, line 4453: warning: duplicate script for target geom_bsd.o ignored
 cc1: warnings being treated as errors
 /h/des/src/sys/dev/isp/isp_pci.c: In function `tdma_mkfc':
 /h/des/src/sys/dev/isp/isp_pci.c:1543: warning: unsigned int format, different type 
arg (arg 5)
 /h/des/src/sys/dev/isp/isp_pci.c:1543: warning: int format, different type arg (arg 
6)
 /h/des/src/sys/dev/isp/isp_pci.c:1572: warning: unsigned int format, different type 
arg (arg 6)
 /h/des/src/sys/dev/isp/isp_pci.c:1572: warning: unsigned int format, different type 
arg (arg 7)
 *** Error code 1

Proposed fix:

%%%
Index: isp_pci.c
===
RCS file: /work/repo/src/sys/dev/isp/isp_pci.c,v
retrieving revision 1.89
diff -u -r1.89 isp_pci.c
--- isp_pci.c   11 Oct 2002 17:28:01 -  1.89
+++ isp_pci.c   1 Jan 2003 14:56:25 -
@@ -1538,9 +1538,10 @@
cto-rsp.m0.ct_dataseg[cto-ct_seg_count].ds_count =
dm_segs[segcnt].ds_len;
cto-rsp.m0.ct_xfrlen += dm_segs[segcnt].ds_len;
-   isp_prt(isp, ISP_LOGTDEBUG1, isp_send_ctio2: ent0[%d]0x%x:%d,
-   cto-ct_seg_count, dm_segs[segcnt].ds_addr,
-   dm_segs[segcnt].ds_len);
+   isp_prt(isp, ISP_LOGTDEBUG1,
+   isp_send_ctio2: ent0[%d]0x%lx:%lu,
+   cto-ct_seg_count, (unsigned long)dm_segs[segcnt].ds_addr,
+   (unsigned long)dm_segs[segcnt].ds_len);
}
 
while (segcnt  nseg) {
@@ -1567,9 +1568,10 @@
crq-req_dataseg[seg].ds_base = dm_segs[segcnt].ds_addr;
crq-req_dataseg[seg].ds_count = dm_segs[segcnt].ds_len;
isp_prt(isp, ISP_LOGTDEBUG1,
-   isp_send_ctio2: ent%d[%d]%x:%u,
+   isp_send_ctio2: ent%d[%d]%lx:%lu,
cto-ct_header.rqs_entry_count-1, seg,
-   dm_segs[segcnt].ds_addr, dm_segs[segcnt].ds_len);
+   (unsigned long)dm_segs[segcnt].ds_addr,
+   (unsigned long)dm_segs[segcnt].ds_len);
cto-rsp.m0.ct_xfrlen += dm_segs[segcnt].ds_len;
cto-ct_seg_count++;
}
%%%

Best regards,
Mike Barcroft

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



Re: Panic during ata_resume (sound)

2003-01-01 Thread cameron grant
_mtx_lock_flags() at _mtx_lock_flags+0x43
mixer_reinit() at
ds_ps_resume()
bus_generic_resume()
bus_generic_resume()
bus_generic_resume()
bus_generic_resume()
bus_generic_resume()
apm_resume()
apm_processevent()
apm_do_suspend()
apm_timeout()
softclock()
ithread_loop()
fork_exit()
fork_trampoline()


it would be helpful to have more information- dmesg, pcm static/preloaded 
kld/postboot kld, and if postboot, what else was the machine doing 
immediately prior to and during kldloading.  also, had you used the mixer 
at all?

	-cg


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


PXE Installation of RC2

2003-01-01 Thread Sven Hazejager
Hi all,

I'm trying to get FreeBSD 5.0-RC2 installed on a Thinkpad X21 laptop
without floppy or cd-rom drive. I'm booting the installation from PXE.
Note that this procedure works with 4.7, but I haven't found any
specific documentation for a PXE install of 5.0.

On the server:

tftpd: /tftpboot contains pxeboot (from the ISO).

dhcpd root-path points to /usr/local/pxe-5.0

/usr/local/pxe-5.0 contains:

./mfsroot.gz
./kernel
./boot
./boot/loader
./boot/loader.rc

$ cat ./boot/loader.rc
echo Loading kernel...
load /kernel
echo Loading mfsroot...
load -t mfs_root /mfsroot
set vfs.root.mountfrom=ufs:/dev/md0c
autoboot 10

The above works in getting the installation program to run. I'm using an
NFS share of the complete 5.0-RC2 ISO as media source for installation.
The installation program finishes without error, asks for a root password
and such, but after reboot, the created slice is not bootable:

Error loading operating system

I'm using the default DOS MBR.

Any suggestions?

Thanks,

Sven Hazejager

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



Re: Panic during ata_resume (sound)

2003-01-01 Thread Gavin Atkinson
On Wed, 1 Jan 2003, cameron grant wrote:

  _mtx_lock_flags() at _mtx_lock_flags+0x43
  mixer_reinit()
  ds_ps_resume()
  bus_generic_resume()
[snip]

 it would be helpful to have more information- dmesg, pcm static/preloaded
 kld/postboot kld, and if postboot, what else was the machine doing
 immediately prior to and during kldloading.  also, had you used the mixer
 at all?

Sorry - i meant to include more information (and indeed fix the subject
line) but managed to forget in the post new-year haze.

Dmesg is attached. The kernel has no sound support, sound modules are
the only modules loaded from /boot/loader.conf:

snd_pcm_load=YES
snd_ds1_load=YES

Sound and the mixer had not been used at all since the reboot, and nothing
will have had the devices open during the suspend. The machine was not
doing anything special, it runs apache, postgresql and sshd (all dormant),
there was an ssh session active, and dnetc. X was not loaded. Uptime was
probably less than 20 minutes.

Nothing has changed with the laptop config recently, and it has
successfully suspended/resumes hundreds of times before.

Gavin
FreeBSD/i386 bootstrap loader, Revision 1.1
([EMAIL PROTECTED], Wed Dec 18 23:32:24 GMT 2002)
Loading /boot/defaults/loader.conf
/boot/kernel/kernel text=0x2bbb50 data=0x345d8+0x6528c syms=[0x4+0x397c0+0x4+0x45b23]
/boot/kernel/snd_pcm.ko text=0x13708 data=0x2278+0x10a4 syms=[0x4+0x2950+0x4+0x2cd7]
/boot/kernel/snd_ds1.ko text=0x408c data=0x647c syms=[0x4+0xa60+0x4+0xa0a]

Hit [Enter] to boot immediately, or any other key for command prompt.
Booting [/boot/kernel/kernel]...
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 5.0-RC #10: Thu Dec 19 17:54:37 GMT 2002
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/EPSILON
Preloaded elf kernel /boot/kernel/kernel at 0xc0502000.
Preloaded userconfig_script /boot/kernel.conf at 0xc05020a8.
Preloaded elf module /boot/kernel/snd_pcm.ko at 0xc05020f8.
Preloaded elf module /boot/kernel/snd_ds1.ko at 0xc05021a4.
Timecounter i8254  frequency 1193182 Hz
CPU: Pentium III/Pentium III Xeon/Celeron (547.31-MHz 686-class CPU)
  Origin = GenuineIntel  Id = 0x683  Stepping = 3
  
Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE

real memory  = 134086656 (127 MB)
avail memory = 124833792 (119 MB)
Initializing GEOMetry subsystem
Pentium Pro MTRR support enabled
VESA: v2.0, 8192k memory, flags:0x0, mode table:0xc0455ba2 (122)
VESA: S3 Incorporated. M7 BIOS
npx0: math processor on motherboard
npx0: INT 16 interface
Using $PIR table, 9 entries at 0xc00f0190
apm0: APM BIOS on motherboard
apm0: found APM BIOS v1.2, connected at v1.2
pcib0: Intel 82443BX (440 BX) host to PCI bridge at pcibus 0 on motherboard
pci0: PCI bus on pcib0
agp0: Intel 82443BX (440 BX) host to PCI bridge mem 0xe000-0xe7ff at d
evice 0.0 on pci0
pcib1: PCIBIOS PCI-PCI bridge at device 1.0 on pci0
pci1: PCI bus on pcib1
pci1: display, VGA at device 0.0 (no driver attached)
isab0: PCI-ISA bridge at device 5.0 on pci0
isa0: ISA bus on isab0
atapci0: Intel PIIX4 ATA33 controller port 0xfff0-0x at device 5.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
uhci0: Intel 82371AB/EB (PIIX4) USB controller port 0xff80-0xff9f irq 11 at de
vice 5.2 on pci0
usb0: Intel 82371AB/EB (PIIX4) USB controller on uhci0
usb0: USB revision 1.0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
pci0: bridge, PCI-unknown at device 5.3 (no driver attached)
pci0: simple comms at device 7.0 (no driver attached)
pci0: unknown at device 9.0 (no driver attached)
cbb0: ToPIC95B PCI-CardBus Bridge irq 11 at device 11.0 on pci0
cardbus0: CardBus bus on cbb0
pccard0: 16-bit PCCard bus on cbb0
cbb1: ToPIC95B PCI-CardBus Bridge irq 11 at device 11.1 on pci0
cardbus1: CardBus bus on cbb1
pccard1: 16-bit PCCard bus on cbb1
pcm0: Yamaha DS-1E (YMF744) port 0xfefc-0xfeff,0xff00-0xff3f mem 0xefff8000-0x
efff irq 11 at device 12.0 on pci0
orm0: Option ROM at iomem 0xc-0xcbfff on isa0
atkbdc0: Keyboard controller (i8042) at port 0x64,0x60 on isa0
atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
psm0: PS/2 Mouse irq 12 on atkbdc0
psm0: model IntelliMouse, device ID 3
fdc0: Enhanced floppy controller (i82077, NE72065 or clone) at port 0x3f7,0x3f
0-0x3f5 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: 1440-KB 3.5 drive on fdc0 drive 0
pmtimer0 on isa0
ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0
ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/8 bytes threshold
lpt0: Printer on ppbus0
lpt0: Interrupt-driven port
ppi0: Parallel I/O on ppbus0
sc0: System console at flags 0x100 on isa0
sc0: VGA 16 virtual consoles, flags=0x300

Broadcom BCM5703X Gigabit Ethernet patch

2003-01-01 Thread George J.V. Cox
On 24/12 14:20, George J.V. Cox wrote:

 I have a Dell 1655MC blade server. It's a chassis of 6 PCs in a 3U
 case. Each blade has two Broadcom BCM5703 interfaces. Unfortunately,
 its behaviour is rather non-deterministic.

Each blade has 2 BCM5703X chips. At least that's what it says on the
chips themselves. However, at boot time the PCI subsystem IDs appear
to match those of the BCM5702 chip. How confusing. What is even more
confusing is that there appear to be different revisons of the chipsets
in same set of 3 blades we received from Dell. This is also noticable
by one of the blades having MAC addresses which differ in the first 3
octets.

The 1655MC has an internal ethernet switch unit, which has 4 100Mb
uplink ports to the outside world and six downlink ports to the blade
servers. The downlink ports are fixed at 1000baseSX in the switch
configuration and this cannot be changed. Hence, enabling the ten bit
interface and forcing 1000baseSX mode on the host interfaces is the way
to go. No MII bus probing is performed by the kernel and everything
is peachy. Cursory testing shows that TCP transfer rates of about 50
Mbyte/second are possible between hosts in the same chassis. (The only
tuning was to set the net.inet.tcp.sendspace and net.inet.tcp.recvspace
sysctls to 100Kb)

Here's some dmesg output when the patch below is applied:

bge0: Broadcom BCM5703X Gigabit Ethernet mem 0xed01-0xed01 irq 7 at device 
10.0 on pci1
bge0: Ethernet address: 00:06:5b:0e:6d:1c
bge0: PCI subsystem ID is 0x1646
bge1: Broadcom BCM5703X Gigabit Ethernet mem 0xed00-0xed00 irq 10 at device 
11.0 on pci1
bge1: Ethernet address: 00:06:5b:0e:6d:1d
bge1: PCI subsystem ID is 0x1646

Values of 0x0126 and 0x0124 have also been seen.  As I mentioned above, no
MII probing is performed.

# ifconfig bge0
bge0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
options=3rxcsum,txcsum
inet 10.2.10.51 netmask 0x broadcast 10.2.255.255
ether 00:06:5b:0e:6d:1c
media: Ethernet 1000baseSX full-duplex
status: active

The media type and options need not be forcibly set to 1000baseSX and
full-duplex respectively, as they have been above.

Here is my patch against -STABLE which fixes the problem. Resolving
the BCOM_SUBSYSID_UNKNOWN_* IDs to some sensible names is left as an
exercise for the reader. :-) The original PR is i386/46484. I've seen
the same behaviour on -current. Anyone like to hazard a guess if this is
the correct kind of fix or not?

Thanks very much!

best;


gjvc

--- if_bge.c.orig   Tue Dec 31 01:21:41 2002
+++ if_bge.cWed Jan  1 04:51:08 2003
@@ -1519,7 +1519,7 @@
u_int32_t command;
struct ifnet *ifp;
struct bge_softc *sc;
-   u_int32_t hwcfg = 0;
+   u_int32_t hwcfg = 0, pcissid = 0;
u_int32_t mac_addr = 0;
int unit, error = 0, rid;
 
@@ -1701,9 +1701,19 @@
if ((ntohl(hwcfg)  BGE_HWCFG_MEDIA) == BGE_MEDIA_FIBER)
sc-bge_tbi = 1;
 
-   /* The SysKonnect SK-9D41 is a 1000baseSX card. */
-   if ((pci_read_config(dev, BGE_PCI_SUBSYS, 4)  16) == SK_SUBSYSID_9D41)
-   sc-bge_tbi = 1;
+   /* check for 1000baseSX cards detectable via their PCI subsystem IDs */
+   pcissid = (pci_read_config(dev, BGE_PCI_SUBSYS, 4)  16);
+   printf(bge%d: PCI subsystem ID is 0x%08x\n, sc-bge_unit, pcissid);
+
+   switch (pcissid) {
+   case SK_SUBSYSID_9D41:
+   case BCOM_SUBSYSID_UNKNOWN_0x0124:
+   case BCOM_SUBSYSID_UNKNOWN_0x0126:
+   case BCOM_SUBSYSID_UNKNOWN_0x1646:
+   printf(bge%d: 1000baseSX capable; enabling TBI\n, 
+sc-bge_unit);
+   sc-bge_tbi = 1;
+   default:
+   }
 
if (sc-bge_tbi) {
ifmedia_init(sc-bge_ifmedia, IFM_IMASK,
--- if_bgereg.h.origSun Dec 29 10:50:06 2002
+++ if_bgereg.h Wed Jan  1 04:50:56 2003
@@ -1787,6 +1787,10 @@
 #define BCOM_DEVICEID_BCM5702X 0x16A6
 #define BCOM_DEVICEID_BCM5703X 0x16A7
 
+#define BCOM_SUBSYSID_UNKNOWN_0x0124   0x0124
+#define BCOM_SUBSYSID_UNKNOWN_0x0126   0x0126
+#define BCOM_SUBSYSID_UNKNOWN_0x1646   0x1646
+
 /*
  * Alteon AceNIC PCI vendor/device ID.
  */

-- 
[gjvc]

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



RE: SIS 962 chipset, problems ...

2003-01-01 Thread Martin Blapp

Good year everybody

Luigi, I converted your patch to CURRENT, there were only
minor changes to do and it seems to work !

sis0: SiS 900 10/100BaseTX port 0x2000-0x20ff mem 0xec005000-0xec005fff irq 1$
at device 4.0 on pci0
sis0: Ethernet address: 00:00:e2:94:66:99
miibus0: MII bus on sis0
ukphy0: Generic IEEE 802.3u media interface on miibus0
ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto

http://people.freebsd.org/~mbr/patches/ifsis-luigi.diff

and added the Linux way of reading the eeprom. I guess
we should make this the default for accessing the eeprom (for this chipset),
since it is not only the mac address which gets read.

Luigi: Or isn't this neccessary ?

http://people.freebsd.org/~mbr/patches/ifsis-mbr.diff

Martin

Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED]
--
ImproWare AG, UNIXSP  ISP, Zurlindenstrasse 29, 4133 Pratteln, CH
Phone: +41 061 826 93 00: +41 61 826 93 01
PGP: finger -l [EMAIL PROTECTED]
PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E
--



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



Re: PXE Installation of RC2

2003-01-01 Thread Brooks Davis
On Wed, Jan 01, 2003 at 05:47:42PM +0100, Sven Hazejager wrote:
 Hi all,
 
 I'm trying to get FreeBSD 5.0-RC2 installed on a Thinkpad X21 laptop
 without floppy or cd-rom drive. I'm booting the installation from PXE.
 Note that this procedure works with 4.7, but I haven't found any
 specific documentation for a PXE install of 5.0.
 
 On the server:
 
 tftpd: /tftpboot contains pxeboot (from the ISO).
 
 dhcpd root-path points to /usr/local/pxe-5.0
 
 /usr/local/pxe-5.0 contains:
 
 ./mfsroot.gz
 ./kernel
 ./boot
 ./boot/loader
 ./boot/loader.rc
 
 $ cat ./boot/loader.rc
 echo Loading kernel...
 load /kernel
 echo Loading mfsroot...
 load -t mfs_root /mfsroot
 set vfs.root.mountfrom=ufs:/dev/md0c
 autoboot 10

For the archives, this is way too much work.  Instead point tftp and NFS
at the mounted ISO and you're done.

 The above works in getting the installation program to run. I'm using an
 NFS share of the complete 5.0-RC2 ISO as media source for installation.
 The installation program finishes without error, asks for a root password
 and such, but after reboot, the created slice is not bootable:
 
 Error loading operating system
 
 I'm using the default DOS MBR.
 
 Any suggestions?

Unfortunatly, I don't have any real ideas here.  Off hand, this doesn't
sound like the sort of problem PXE could cause.  It's just not involved
with that part of the process.  Are you sure the kernel and loader you
used were the right ones?

-- Brooks

-- 
Any statement of the form X is the one, true Y is FALSE.
PGP fingerprint 655D 519C 26A7 82E7 2529  9BF0 5D8E 8BE9 F238 1AD4



msg49506/pgp0.pgp
Description: PGP signature


Multicast Routing

2003-01-01 Thread Nick H. -- Technical Support Engineer
Anyone have any good how-to's on how to setup a FreeBSD box to do multicast
routing?  Im wanting to setup a FreeBSD gateway that will have a Cable modem
and a DSL modem connected to it.  Any traffic on certain ports I want to go
through (out) one interface (dc0) and the rest to go through the other
interface (dc1) while dc2 is the LAN interface (10.0.0.1).  Any ideas?


Regards,
-Nick Harm Hale
[EMAIL PROTECTED]


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



Re: alpha tinderbox failure

2003-01-01 Thread Matthew Jacob

I already know this- I just hadn't checked it in a change because I was
trying to get one of my alphas current. Sam Leffler brought it to my
attention the other day.

This is for LINT, btw.

Also- is casting to 'long' for bus_addr_t and bus_size_t the best idea?
Shouldn't it be cast to the maximum width integer (long long)?

-matt



On Wed, 1 Jan 2003, Mike Barcroft wrote:

 Dag-Erling Smorgrav [EMAIL PROTECTED] writes:
  === vinum
  Makefile, line 4453: warning: duplicate script for target geom_bsd.o ignored
  cc1: warnings being treated as errors
  /h/des/src/sys/dev/isp/isp_pci.c: In function `tdma_mkfc':
  /h/des/src/sys/dev/isp/isp_pci.c:1543: warning: unsigned int format, different 
type arg (arg 5)
  /h/des/src/sys/dev/isp/isp_pci.c:1543: warning: int format, different type arg 
(arg 6)
  /h/des/src/sys/dev/isp/isp_pci.c:1572: warning: unsigned int format, different 
type arg (arg 6)
  /h/des/src/sys/dev/isp/isp_pci.c:1572: warning: unsigned int format, different 
type arg (arg 7)
  *** Error code 1

 Proposed fix:

 %%%
 Index: isp_pci.c
 ===
 RCS file: /work/repo/src/sys/dev/isp/isp_pci.c,v
 retrieving revision 1.89
 diff -u -r1.89 isp_pci.c
 --- isp_pci.c 11 Oct 2002 17:28:01 -  1.89
 +++ isp_pci.c 1 Jan 2003 14:56:25 -
 @@ -1538,9 +1538,10 @@
   cto-rsp.m0.ct_dataseg[cto-ct_seg_count].ds_count =
   dm_segs[segcnt].ds_len;
   cto-rsp.m0.ct_xfrlen += dm_segs[segcnt].ds_len;
 - isp_prt(isp, ISP_LOGTDEBUG1, isp_send_ctio2: ent0[%d]0x%x:%d,
 - cto-ct_seg_count, dm_segs[segcnt].ds_addr,
 - dm_segs[segcnt].ds_len);
 + isp_prt(isp, ISP_LOGTDEBUG1,
 + isp_send_ctio2: ent0[%d]0x%lx:%lu,
 + cto-ct_seg_count, (unsigned long)dm_segs[segcnt].ds_addr,
 + (unsigned long)dm_segs[segcnt].ds_len);
   }

   while (segcnt  nseg) {
 @@ -1567,9 +1568,10 @@
   crq-req_dataseg[seg].ds_base = dm_segs[segcnt].ds_addr;
   crq-req_dataseg[seg].ds_count = dm_segs[segcnt].ds_len;
   isp_prt(isp, ISP_LOGTDEBUG1,
 - isp_send_ctio2: ent%d[%d]%x:%u,
 + isp_send_ctio2: ent%d[%d]%lx:%lu,
   cto-ct_header.rqs_entry_count-1, seg,
 - dm_segs[segcnt].ds_addr, dm_segs[segcnt].ds_len);
 + (unsigned long)dm_segs[segcnt].ds_addr,
 + (unsigned long)dm_segs[segcnt].ds_len);
   cto-rsp.m0.ct_xfrlen += dm_segs[segcnt].ds_len;
   cto-ct_seg_count++;
   }
 %%%

 Best regards,
 Mike Barcroft



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



Firewire: fwohci0: cannot read phy

2003-01-01 Thread Martin Blapp

Hi all,

Does anyone know why my firewire kld does not
attach successfully ? Could this be related to the
same problem I had with the sis900 nic ? Eeprom is shared
between Firewire and NIC.

fwohci0: vendor=1039, dev=7007
fwohci0: 1394 Open Host Controller Interface mem 0xec00-0xec000fff irq 11
at device 2.3 on pci0
fwohci0: PCI bus latency was changing to 250.
fwohci0: OHCI version 1.0 (ROM=1)
fwohci0: No. of Isochronous channel is 4.
fwohci0: EUI64 00:01:24:10:32:0a:c0:30
fwohci0: cannot read phy
fwohci0: Link 1394a available S400, 2 ports, maxrec 2048 bytes.
firewire0: IEEE1394(FireWire) bus on fwohci0
firewire0: BUS reset
firewire0: node_id = 0xc000ffc0, CYCLEMASTER mode
firewire0: 1 nodes, maxhop = 0, cable IRM = 0 (me)
firewire0: unrecoverable error

Chipset is SiS962 with integrated USB, Firewire and NIC.

Martin

Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED]
--
ImproWare AG, UNIXSP  ISP, Zurlindenstrasse 29, 4133 Pratteln, CH
Phone: +41 061 826 93 00: +41 61 826 93 01
PGP: finger -l [EMAIL PROTECTED]
PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E
--


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



5.0-RC2 informal PR: 90 sec sendmail delay

2003-01-01 Thread Gary W. Swearingen
I've got sendmail configured exactly the same (AFAIK) as my working 4.7
system, with rc.conf having sendmail_enable=NO (only) just to allow
me to send mail via my ISP using the smart host feature.

My PROBLEM: Using either gnus or mail, sent messages sit in
/var/spool/clientmqueue for about 90 before leaving for my ISP.  It
wouldn't be too bad for mail as it returns control instantly, but
gnus hangs up for the 90 seconds where it used to return control
instantly.

Shouldn't the sendmail which listens on port 25 tell the msp_queue
runner to try to process the mail immediately.  It's clearly not just
waiting for the runner to happen upon it in its normal every-30-min
runs.  There seems to be a 90 seconds (or maybe 88) delay in there.

My DNS is working OK, but I've got dynamic IP here, so no real hostname.

Some HISTORY: I installed 5.0-RC2 from ISO-burned CD (checked with MD5
and against ISO image).  Did a hand-merge of my working 4.7 config.
Built XFree86 port (X was hanging; a different PR) and a few other
ports.  Did cvsup with tag . (30dec02) and ade world  kernel using
well-tested steps (which fixed X, BTW).  Rebuilding my sendmail .cf
files and restarting the sendmail daemons didn't help.

Anybody got any ideas?  Nobody on -questions did.  Should I be looking
for a sendmail forum?

Thanks.

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



Re: 5.0-RC2 informal PR: 90 sec sendmail delay

2003-01-01 Thread Terry Lambert
Gary W. Swearingen wrote:
 
 I've got sendmail configured exactly the same (AFAIK) as my working 4.7
 system, with rc.conf having sendmail_enable=NO (only) just to allow
 me to send mail via my ISP using the smart host feature.

Set HoldExpensive, and make sure the SMTP mailer is marked as
expensive (which it is not, by default).  Make sure you run a
seperate queue run for outbound (sounds like you are).  Then
disable DNS lookups on the internal sendmail process queue run,
which sould be seperate from the outbound mail queue run.  Use
different sendmail.cf files for internal queue run and outbound
queue runs (you need to set the DNS timeouts a *lot* longer on
the outbound, to account for DNS retry delays between inital DNS
request casuing the link up state to be started, and the actual
link being up and capable of processing DNS requests).

It is a *serious mistake* to seperate the link management from
the host OS, and try to make it the responsibility of individual
programs (like sendmail, or a SQUID proxy server, etc.).  We made
that mistake on the InterJet, and were never able to correct it,
after the fact.  Probably the correct thing to do is to add an
EADMIN error code, which administratively denies linkup on the
attempt to connect(2) to an external IP address, and make sure
applications can handle transient connect(2) failures.


 Shouldn't the sendmail which listens on port 25 tell the msp_queue
 runner to try to process the mail immediately.  It's clearly not just
 waiting for the runner to happen upon it in its normal every-30-min
 runs.  There seems to be a 90 seconds (or maybe 88) delay in there.
 
 My DNS is working OK, but I've got dynamic IP here, so no real hostname.

Disable reverse resolution of the interface name, too, then; see
cf/README for details.

I'm not too happy about some of the changes to Sendmail recently,
but I understand, from a marketing perspective, why they are
being made, to compete with DJB's security claims on qmail, and
Weitse's claims on seperation of operation on performance (both
claims are bogus, but it's complicated to explain to potential
customers why that's the case).

-- Terry

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



5.0 : ISA SB16 with ACPI does not work

2003-01-01 Thread Vladimir
Hi, All ! 
 
   

I'm run RELENG_5_0 from 28.12.2002 and ISA SoundBlaster 16 sound 
  
card does not work when acpi.ko turned on. When ACPI disabled, 

sound work fine. Under -STABLE it work without problems too. 
  
BIOS settings was tuned : irq 5 and dma 1,5 used by ISA. 
  
When attempting to play file, kernel print message :
pcm0:play:0: play interrupt timeout, channel dead. 
  
And no sound output at all. 
   
Any ideas ? 
   
   

Dmesg output with acpi turned on : 

   

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 5.0-RC #5: Sat Dec 28 02:01:39 GMT 2002 
   
mvb@Devastator:/usr/src/sys/i386/compile/DEVASTATOR5 
  
Preloaded elf kernel /boot/kernel/kernel at 0xc03f5000. 
 
Preloaded elf module /boot/kernel/snd_sb16.ko at 0xc03f50a8. 

Preloaded elf module /boot/kernel/snd_sbc.ko at 0xc03f5158. 
 
Preloaded elf module /boot/kernel/snd_pcm.ko at 0xc03f5204. 
 
Preloaded elf module /boot/kernel/random.ko at 0xc03f52b0. 
  
Preloaded elf module /boot/kernel/acpi.ko at 0xc03f535c. 

Timecounter i8254  frequency 1193182 Hz 
 
Timecounter TSC  frequency 300683012 Hz 
 
CPU: Pentium II/Pentium II Xeon/Celeron (300.68-MHz 686-class CPU) 

  Origin = GenuineIntel  Id = 0x660  Stepping = 0 
   
   

+Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT
+,PSE36,MMX,FXSR 
 
real memory  = 201314304 (191 MB) 
 
avail memory = 191238144 (182 MB) 
 
Initializing GEOMetry subsystemPentium Pro MTRR support enabled 
  
npx0: math processor on motherboard 
 
npx0: INT 16 interface 

acpi0: ASUS   P2B-Bon motherboard 
   
ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15 
  
Using $PIR table, 5 entries at 0xc00f0d10 
 
acpi0: power button is handled as a fixed feature programming model. 
  
Timecounter ACPI-safe  frequency 3579545 Hz 
 
acpi_timer0: 24-bit timer at 3.579545MHz port 0xe408-0xe40b on acpi0 

acpi_cpu0: CPU on acpi0 
 
acpi_button0: Power Button on acpi0 
 
pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 
   
pci0: ACPI PCI bus on pcib0 
 
pcib1: PCIBIOS PCI-PCI bridge at device 1.0 on pci0 
 
pci1: PCI bus on pcib1 
  
isab0: PCI-ISA bridge at device 4.0 on pci0 
 
isa0: ISA bus on isab0 
  
atapci0: Intel PIIX4 ATA33 controller port 0xd800-0xd80f at device 4.1 on 
pci0
ata0: at 0x1f0 irq 14 on atapci0 
  
ata1: at 0x170 irq 15 on atapci0 
  
pci0: serial bus, USB at device 4.2 (no driver attached) 

pci0: bridge, PCI-unknown at device 4.3 (no driver attached) 

pci0: display, VGA at device 10.0 (no driver attached) 
  
fdc0: Enhanced floppy controller (i82077, NE72065 or clone) port 

+0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0 
   
fdc0: FIFO enabled, 8 bytes threshold 
 
sio0 port 0x3f8-0x3ff irq 4 on acpi0
sio0: type 16550A 
 
sio1 port 0x2f8-0x2ff irq 3 on acpi0 
  
sio1: type 16550A 
  

Re: 5.0-RC2 informal PR: 90 sec sendmail delay

2003-01-01 Thread Claus Assmann
On Wed, Jan 01, 2003, Terry Lambert wrote:

 I'm not too happy about some of the changes to Sendmail recently,

Which? And why?

If there are problems, the authors would like to hear
about it directly, instead of reading it in some mailing
list by accident...

 but I understand, from a marketing perspective, why they are
 being made, to compete with DJB's security claims on qmail, and
 Weitse's claims on seperation of operation on performance (both
 claims are bogus, but it's complicated to explain to potential
 customers why that's the case).

We are not making changes from a marketing perspective.

If you are referring to the separation of sendmail into MTA and
MSP: this was necessary to get rid of sendmail being set-user-ID
root, which is a security risk (as you will probably agree, this
isn't marketing, this is real, e.g., sendmail was abused in some
cases to exploit bugs in the OS).


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



Re: 5.0-RC2 informal PR: X hangups using radeon driver

2003-01-01 Thread Nick H. -- Technical Support Engineer
Hello,

You may wish to run xfree86cfg again and step through the setup.  When it
asks you for a video card, select any ATI card (we'll change this later) and
continue on through the setup of X.  Once you have the config saved, go into
the config and change the driver from ati to radeon and that should load
the radeon drivers.  I am running both RC1 and RC2 (as well as 2 5.0-CURRENT
machines cvsup'd from RC2) all of which are running X and KDE (they're
workstations for friends) and Im not having any issues using a radeon 7500
(or 7000-powered by ati) and the rest are authentic ATI cards.  If you have
any questions, lemmie know.


Regards,
-Nick Harm Hale
[EMAIL PROTECTED]




- Original Message -
From: Gary W. Swearingen [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, January 01, 2003 2:14 PM
Subject: 5.0-RC2 informal PR: X hangups using radeon driver


 I downloaded a 5.0-RC2 ISO, checked the MD5 against a different mirror's
 MD5, burned a CD, diff'ed the CD against the ISO, and installed the OS.
 My first try using the full-GUI X installer failed gracefully (I forget
 the details).  The other two X installers didn't offer to support my
 video card, so I tried the full-GUI one again.  It offered something
 called ati.  I'm not sure why it said ati rather than what my old
 XF86Config used radeon, but it seemed close enough.  IIRC, it wasn't
 and I copied over my old XF86Config.  Starting X several times after
 reboots, it would hang up after 30-120 (?) seconds of use.  Sometimes
 ctrl-alt-bs would kill X and sometimes it would require a hard reboot.

 I did portupgrade -R XFree86 (after installing my old make.conf which
 has CFLAGS= -O -pipe and CPUTYPE=k6-2) and still had the problem.

 I then did a source cvsup (tag=.) and rebuilt world and kernel using
 well-tested steps.  X has not since hung up in about two days (several
 hours of activity).

 CPU : AMD K6-2 500MHz with 128 MB RAM.
 Video : Hightech Information Systems' Excalibur (Radeon 7000 with
TV-OUT)

 FreeBSD boot msg: pci1: ATI model 5159 graphics accelerator at 0.0
 XFree86 4.2.0 says: ATI Radeon VE QY rev 0 (AGP); framebuffer bpp 32;
 ChipID = 0x5159; VideoRAM=65536kB; 64-bit DDR SDRAM


 I have a free partition to do some debugging if there's something I can
 do in a few hours.  I'm no C hacker, but am willing to mess with a
 debugger a bit.  I know how to set up for crash dumps, but that's
 probably not much help here.  Maybe the fact that it works after a cvsup
 means -RC3 will not hang up, but that's just guessing; maybe my
 CPUTYPE=K6-2 fixed it.


 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



Matt Dillon E-Mail mode for fmt(1)...

2003-01-01 Thread Juli Mallett
Well, I know that after the recentish trolls and the regular
mails from Matt, I'm not the only one jealous of his email
formatting.  Rather than continue to tell people to use fmt
piped to sed(1) to achieve the desired result, I added the
appropriate behaviour to fmt(1).  It tries its damnedest to
get it right, and will even yell at you if you chose dumb
max and goal lengths.  In my testing it seems to generate
appropriate formatting, so here's the URL for testing:

http://people.freebsd.org/~jmallett/dillon.diff

Thanx,
juli.

PS: This email wasn't formatted with fmt -e, and I tried to
use the local style of fmt(1).  I apologise for both of those,
and for this entire message, in advance.
-- 
Juli Mallett [EMAIL PROTECTED]
AIM: BSDFlata IRC: juli@EFnet#flata
OpenDarwin, Mono, FreeBSD Developer.
ircd-hybrid Developer, EFnet addict.
FreeBSD on MIPS-Anything on FreeBSD.

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



Vaio ACPI and PCCARD problems

2003-01-01 Thread Pete Carah
This is a Vaio R505ES.  Looks as if acpi is both totally necessary
and doesn't work right.

In my last 2 compiles (since about 12/20) I get a lock-order-reversal
panic during boot, after init starts.  continue in ddb makes
things appear to work right.  If this was fixed since 12/23 I
apologize for the complaint; I cvsup'd today but am currently
building the result so haven't tried it.

Things have improved greatly; I can now use the cdr/dvd drive
via firewire, in current only; still fails to allocate an interrupt
under stable.

X (with 830 driver using XFree86 HEAD) works OK in stable but
the server cores immediately after the pci probes (before the
specific device probes) in current.  (using the same XF86Config
that works in stable.) This appears to be either a system header 
file problem or compiler problem as it only happens when the server 
was compiled under current.  The same source code compiled under 
stable works in stable, and brings up xdm in current, but fails pam 
(complains of a faulty module) under current (that is somewhat, but not 
too, surprising).  (I normally use xdm/kdm rather than startx).
There are some more-or-less severe problems during server resets 
and other reversions to text mode, but generally things are usable.
I can't get kdm to work at all with this server in either stable
or current.

umass works in both current and stable for an external device
but the memory-stick slot only works in current (I think this
is an irq problem in stable).

psm doesn't work (fails probe too).  Complains about unable to 
allocate irq.

pcm appears to not work, though dmesg indicates it probes OK.
wavplay of a file that should last a minute gives the normal
printout of the header, then says it is starting; it goes silently
about a second and quits apparently normally.  I'm not getting
the hang messages that some others are complaining about.

Putting pccard code in the kernel (either oldcard or newcard)
causes a hang after trying /sbin/init.  Looking in ddb at the
hang gives the appearance that something is asserting irq9 (I
suspect cbb1 but can't be sure since for some reason acpi allocates
irq9 to almost everything in the system) and the interrupt code 
isn't clearing the pending irq for some reason.  Part of my
suspicion here has to do with 0 results for the debug printouts
in pccard; looking at the code this shouldn't happen.  (though
I'd think just reading those registers should clear at least
some interrupts.)

I have an asl dump (without acpi_load=no) on my home server;
http://pelican.altadena.net/~pete/r505es.asl

In particular, the _OS_ test is strange; it checks 2-character 
substrings of the OS string for some reason; this obfuscates what 
it is testing for.

The strange thing is that only irq 9 is used for floating values
though 10,11,5 and I think 13 are all free.

I don't have a dmesg for the hang case due to lack of 
another usable computer with serial port at the moment;
without pccard code, it is:

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 5.0-CURRENT #8: Sun Dec 29 22:26:31 EST 2002
[EMAIL PROTECTED]:/d/obj-c/usr/src/sys/PORT2
Preloaded elf kernel /boot/kernel/kernel at 0xc04fc000.
Preloaded elf module /boot/kernel/snd_ich.ko at 0xc04fc0a8.
Preloaded elf module /boot/kernel/snd_pcm.ko at 0xc04fc154.
Preloaded elf module /boot/kernel/uscanner.ko at 0xc04fc200.
Preloaded elf module /boot/kernel/firewire.ko at 0xc04fc2b0.
Preloaded elf module /boot/kernel/sbp.ko at 0xc04fc360.
Preloaded elf module /boot/kernel/acpi.ko at 0xc04fc408.
Calibrating clock(s) ... TSC clock: 1193125501 Hz, i8254 clock: 1193204 Hz
CLK_USE_I8254_CALIBRATION not specified - using default frequency
Timecounter i8254  frequency 1193182 Hz
CLK_USE_TSC_CALIBRATION not specified - using old calibration method
Timecounter TSC  frequency 1193109027 Hz
CPU: Pentium III/Pentium III Xeon/Celeron (1193.11-MHz 686-class CPU)
  Origin = GenuineIntel  Id = 0x6b1  Stepping = 1
  
Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
real memory  = 535298048 (510 MB)
Physical memory chunk(s):
0x1000 - 0x0009dfff, 643072 bytes (157 pages)
0x00523000 - 0x1fce, 528273408 bytes (128973 pages)
0x1fd0 - 0x1fe77fff, 1540096 bytes (376 pages)
avail memory = 514494464 (490 MB)
bios32: Found BIOS32 Service Directory header at 0xc00f6bb0
bios32: Entry = 0xfd871 (c00fd871)  Rev = 0  Len = 1
pcibios: PCI BIOS entry at 0xfd870+0x13a
pnpbios: Found PnP BIOS data at 0xc00f6be0
pnpbios: Entry = f:8816  Rev = 1.0
Other BIOS signatures found:
Initializing GEOMetry subsystem
random: entropy source
mem: memory  I/O
Pentium Pro MTRR support enabled
null: null device, zero device
npx0: math processor on motherboard
npx0: INT 16 interface
acpi0: SONY   C1   on motherboard

sound debugging

2003-01-01 Thread David Yeske
So right now there is no clean way to debug sound in FreeBSD.

I modified my system running current so that I now have a PCM_DEBUG option.

I set up oid's in the same way that many usb drivers do with DPRINTF / DPRINTFN.

So I now have hw.snd.drivername.debug oid's.

Is the method used for usb debugging the best way.  I am referring to the usage of 
USB_DEBUG
which creates opt_usb.h.  When USB_DEBUG is defined than the DPRINTF / DPRINTFN macros 
become
defined with some sysctl's.  If debugging is not defined do the DPRINTF / DPRINTFN 
lines go into
the drivers once compiled and slow it down or bloat it?

Regards,
David Yeske


















__
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com

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



rshd and/or pan_setenv() broken

2003-01-01 Thread Bruce Evans
rshd now gets killed by signal 11 in pam_putenv() when
pam_setenv(HOME, ...) is called for rsh localhost ls.
The registers for pamh-env and i are both 0 in free(pamh-env[i]),
although this can't happen since pamh-env[0] must have been accessed
in openpam_findenv() to get to the free().

rsh localhost and rlogin localhost still work.  A statically
linked rshd from last June still works.

Bruce


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



Re: rshd and/or pan_setenv() broken

2003-01-01 Thread Mikko Työläjärvi

See http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/46628.

$.02,
/Mikko

On Thu, 2 Jan 2003, Bruce Evans wrote:

 rshd now gets killed by signal 11 in pam_putenv() when
 pam_setenv(HOME, ...) is called for rsh localhost ls.
 The registers for pamh-env and i are both 0 in free(pamh-env[i]),
 although this can't happen since pamh-env[0] must have been accessed
 in openpam_findenv() to get to the free().

 rsh localhost and rlogin localhost still work.  A statically
 linked rshd from last June still works.

 Bruce


 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: 5.0-RC2 informal PR: 90 sec sendmail delay

2003-01-01 Thread Terry Lambert
Claus Assmann wrote:
 On Wed, Jan 01, 2003, Terry Lambert wrote:
  I'm not too happy about some of the changes to Sendmail recently,
 
 Which? And why?
 
 If there are problems, the authors would like to hear
 about it directly, instead of reading it in some mailing
 list by accident...

It's an editorial complaint.  I don't like the breaking the
program into seperate programs by function.  IMO, DJB is wrong,
and this does nothing to enhance security.  The result of doing
this in FreeBSD has been to greatly complicate rc scripts, with
the result that sendmail is much less of an unpluggable component
that can be replaced with something else, easily, and with little
system impact.

I understand the security reasoning, based on having to compete
with qmail and other packages that claim this seperation magically
fixes all security issues.  But it's just a propaganda move, and
it's not technically justified.

Similarly, the interior seperation, which is what resulted in the
DNS lookup that brought up the link in this current discussion
thread, fails via a timeout before the lookup is done, and so the
transfer fails.  Whistle had to address this problem for Ricoh,
with the InterJet, as well, since a linkup could take sufficient
time that the timeout would fire, and the mail would never end up
getting sent (it would get aged into the queue as can't lookup
destination host).


  but I understand, from a marketing perspective, why they are
  being made, to compete with DJB's security claims on qmail, and
  Weitse's claims on seperation of operation on performance (both
  claims are bogus, but it's complicated to explain to potential
  customers why that's the case).
 
 We are not making changes from a marketing perspective.
 
 If you are referring to the separation of sendmail into MTA and
 MSP: this was necessary to get rid of sendmail being set-user-ID
 root, which is a security risk (as you will probably agree, this
 isn't marketing, this is real, e.g., sendmail was abused in some
 cases to exploit bugs in the OS).

Nope. I don't agree.  I think the change makes things harder, and
I don't see a difference in the volume of security advisories (e.g.
not a lot of advisories warning about people being able to obtain
the $MAILUSER identity through some buffer overflow, rather than
root).

At one point, sendmail was getting a lot of crap in the trade press
over running suid root... but, IMO, that's all it was: crap.  It was
just a hook that people could hang marketing arguments against
sendmail on, to FUD people into using a different product.  Any
reaction to FUD is a marketing reaction, unless there's provable
technical merit in the decision.

And one result is a FreeBSD where it's harder to pull sendmail out
and replace it (also a marketing win, from a sendmail perspective).
Personally, I use sendmail, so yanking it out is not high on my list
of things to do, but it's now harder to have base mail functionality
without parts of sendmail sticking around.

-- Terry


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



Crossbuilding -current from -stable fails in boot2

2003-01-01 Thread Richard Perini

When crossbuilding -current on a -stable machine, sys/boot/i386/boot2
fails during a make buildworld, the culprit appears to be  cpp on 
4-stable not grokking some of the CFLAGS arguments while cpp'ing boot1.s.  

A patch to fix the Makefile is below, not sure if its the desired way 
to fix?  If it is, could I ask that someone commit it please?

--
Richard Perini   Internet:  [EMAIL PROTECTED]
Corinthian Engineering Pty Ltd   PHONE:   +61 2 9906 4333
Sydney, AustraliaFAX: +61 2 9906 2464


--- Makefile.ORIG   Thu Jan  2 16:35:34 2003
+++ MakefileThu Jan  2 16:45:46 2003
@@ -45,6 +45,11 @@
-Wmissing-declarations -Wmissing-prototypes -Wnested-externs \
-Wpointer-arith -Wshadow -Wstrict-prototypes -Wwrite-strings
 
+CPPFLAGS= -D${BOOT2_UFS} \
+   -I${.CURDIR}/../../common \
+   -I${.CURDIR}/../btx/lib -I. \
+   -Wall
+
 LDFLAGS=-nostdlib -static -N --gc-sections
 
 all: boot1 boot2
@@ -56,7 +61,7 @@
${LD} ${LDFLAGS} -e start -Ttext ${ORG1} -o ${.TARGET} boot1.o
 
 boot1.o: boot1.s
-   ${CPP} ${CFLAGS} ${.IMPSRC} | \
+   ${CPP} ${CPPFLAGS} ${.IMPSRC} | \
${AS} ${AFLAGS} --defsym FLAGS=${B1FLAGS} -o ${.TARGET}
 
 boot2.o: boot2.c ${.CURDIR}/../../common/ufsread.c

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



Re: 5.0-RC2 informal PR: X hangups using radeon driver

2003-01-01 Thread Eric Anholt
On Wed, 2003-01-01 at 12:14, Gary W. Swearingen wrote:
 I downloaded a 5.0-RC2 ISO, checked the MD5 against a different mirror's
 MD5, burned a CD, diff'ed the CD against the ISO, and installed the OS.
 My first try using the full-GUI X installer failed gracefully (I forget
 the details).  The other two X installers didn't offer to support my
 video card, so I tried the full-GUI one again.  It offered something
 called ati.  I'm not sure why it said ati rather than what my old
 XF86Config used radeon, but it seemed close enough.  IIRC, it wasn't

The 'ati' driver detects what type of ATI card you have and loads the
appropriate driver (radeon, r128, atimisc).

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


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



Re: rshd and/or pan_setenv() broken

2003-01-01 Thread Bruce Evans
On Wed, 1 Jan 2003, [ISO-8859-1] Mikko Työläjärvi wrote:

 See http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/46628.

Thanks.  I vaguely remembered a bug report about pam_*env() but not
one about rshd.

Bruce


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



Re: 5.0-RC2 informal PR: 90 sec sendmail delay

2003-01-01 Thread sthaug
  If there are problems, the authors would like to hear
  about it directly, instead of reading it in some mailing
  list by accident...
 
 It's an editorial complaint.  I don't like the breaking the
 program into seperate programs by function.  IMO, DJB is wrong,
 and this does nothing to enhance security.

It's not only DJB. Take a look at Postfix, which also has a good
reputation for security. Postfix consists of separate programs
with well defined privileges. Wietse Venema has been quite clear
that such a separation was the only way he could guarantee the
security of Postfix.

Steinar Haug, Nethelp consulting, [EMAIL PROTECTED]

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



Re: Slightly OT: Reasons to upgrade?

2003-01-01 Thread Giorgos Keramidas
On 2002-12-31 09:40, Joe Laughlin [EMAIL PROTECTED] wrote:
 Currently, I'm running STABLE on my machine, which serves as both a
 desktop and a server.  It seems to work great and everything.  Does
 everything I need it to do.

 Is there any compelling reason for me to upgrade to 5.0 next year?  I've
 read over the list of anticipated new features and there's nothing there
 that seems needed for me.

There is no push to upgrade.  I know a couple of people here who
still use FreeBSD 3.X versions regularly, because they feel more
comfortable with it and have applications that they cannot easily
migrate to 4.X.


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