Re: ATAng - copying atapi CD

2003-09-04 Thread Terry Lambert
Bryan Liesner wrote:
 On Wed, 3 Sep 2003, Martin wrote:
  If you notice that your CD-R label looks strange and if you need
  the data, you should backup it fast.
 
 No, we're talking about brand new, factory pressed, audio CDs.

Are they copy protected?

The way you can tell is if you try to do what you are trying to
do, and it fails the way that it's failing, then they are likely
copy protected.

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


Re: ATAng - copying atapi CD

2003-09-04 Thread Terry Lambert
Sean Kelly wrote:
 On Wed, Sep 03, 2003 at 07:11:53AM -0400, Bryan Liesner wrote:
  No, we're talking about brand new, factory pressed, audio CDs.
 
 And on top of that, my Windows XP machine's DVD-ROM was able to raed my
 *commercial audio CDs* perfectly while the CD-RW in the FreeBSD machine was
 only able to read about 95% of the discs before it just got stuck.

What happens if you install the same DVD-ROM drive in your
FreeBSD box, and try that?  Maybe it's your drive?

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


wi0: cardbus card activation failed

2003-09-04 Thread wintran
Hello,
I have same problem as 
http://lists.freebsd.org/pipermail/freebsd-current/2003-August/008948.html,
 but with other PCMCIA card - new Proxim Orinoco.
When I plug it in, I get:

cardbus0: network, ethernet at device 0.0 (no driver attached)
cbb0: CardBus card activation failed

I use kernel from yestereday, pccbb.c ver 1.95.

Tin


-- Created by Email.cz  http://www.email.cz -- Get Your Free Email  


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


DISCUSSION: /dev/fd%d.%d and /dev/{a}cd%d[ac] to be discontinued ?

2003-09-04 Thread Poul-Henning Kamp

I am committing a BURN_BRIDGES patch which puts the density select
devices of the floppy driver and the 'a' and 'c' compat partitions of
the CD drivers on the chopping block for 6-current.

There is no loss of functionality from this, the fdcontrol(8) utility
allows even greater flexibility than the density select devices do
for floppies and the 'a' and 'c' compat parititons can be simulated
with symlinks from userland should any critical application be found
to have hardcoded paths.

The use of device cloning functions in disk drivers under GEOM is
not as such impossible, but it would be quite complicated and I
would rather avoid it unless we have much better killer apps for
it than these two uses.


As soon as these uses of cloning code has been removed, I will move
the floppy and CD drivers under GEOM, paving the way for the
significant changes to the buf/VM system which some of you have
already heard rumours about.  (more will emerge after BSDcon'03)

And now comes the bit which I would like to offer for discussion:

Should we do this for 5.2 instead ?

By pulling this into 5.2, the divergence between 5-stable and
6-current can be managed much better, and we will be able to backport
much more from 6-current to 5-stable than we would be able to
otherwise.

If we do not do this I fear that it will be close to impossible to
MFC filesystem work in practice.

And let me repeat:  the only loss of functionality is the density
select devices for floppy disks which will have to be done with the
fdcontrol(8) utility instead.

-- 
Poul-Henning Kamp   | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer   | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: [GCC 3.3.1 regression] loop miscompiled.

2003-09-04 Thread Doug Barton
You should really file a PR about this.

Doug

-- 

This .signature sanitized for your protection

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


RE: Multi BOOT

2003-09-04 Thread Abdul Hakeem


Hello,
Does anyone know a way of simultaneously booting FreeBSD with Linux or
Win2K with a dual-processor and dual NIC server ?
I can set the processor affinity on the Win2k, but I am having trouble
configuring the FreeBSD to use a particular processor and a particular
NIC.
Regards,
Abdul Hakeem

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


Re: bktr(4) bufs plus patch

2003-09-04 Thread Michal Mertl
On Wed, 3 Sep 2003, Jens Rehsack wrote:
 Michal Mertl wrote:
  I found 2 bugs and some potential problems in bktr(4) code.
 
  Bug 1:
  Compilation with options BKTR_USE_FREEBSD_SMBUS failes. Error is
  that code tries to use iicbus which isn't defined where it looks for
  it. I added it there and the compilation and detection goes fine. I don't
  know how to actually test it though.
 

 [...]

 Will anyone responsible take notice of this patch and commit it?

  
 
  *** dev/bktr/bktr_reg.h.ori Sun Dec  8 10:40:14 2002
  --- dev/bktr/bktr_reg.h Sun Dec  8 10:40:38 2002
  ***
  *** 448,453 
  --- 448,454 
struct bktr_i2c_softc {
  int bus_owned;
 
  +   device_t iicbus;
  device_t iicbb;
  device_t smbus;
};
  *** dev/bktr/bktr_os.c.ori  Sun Dec  8 10:39:13 2002
  --- dev/bktr/bktr_os.c  Sun Dec  8 10:39:35 2002
  ***
  *** 499,513 
  destroy_dev(bktr-tunerdev);
  destroy_dev(bktr-bktrdev);
 
  -   /* If this is unit 0, then destroy the alias entries too */
  - #if (__FreeBSD_version =50)
  -   if (unit == 0) {
  -   destroy_dev(bktr-vbidev_alias);
  -   destroy_dev(bktr-tunerdev_alias);
  -   destroy_dev(bktr-bktrdev_alias);
  -   }
  - #endif
  -
  /*
   * Deallocate resources.
   */
  --- 499,504 

The destroy_dev calls for aliases have been removed in -current on 9th Dec
2002 (one day after I sent the email). See PR kern/36413. The fix hasn't
been MFCed but there's no need - the code is wrapped in '#if
(__FreeBSD_version = 50)'. The fix for BKTR_USE_FREEBSD_SMBUS hasn't
been commited.

I didn't send-pr but will recheck the status of things over the weekend
and perhaps will do.

To other readers: in my original email
(http://docs.freebsd.org/cgi/getmsg.cgi?fetch=2276+0+archive/2002/freebsd-current/20021215.freebsd-current)
I talked about another problem (limits on the maximum number of devices).
When I reread what I wrote at the time I have to say 'sorry for my
English' :-).

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


Four -CURRENT panics (backtrace included)

2003-09-04 Thread Xin LI/
Hello everyone,

I have encounted several panics in recent kernels. The kernel was compiled right after 
cvsup, so the date will apply to the source code.

panic 1:

beastie# gdb -k kernel.debug /var/crash/vmcore.0
GNU gdb 5.2.1 (FreeBSD)
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB.  Type show warranty for details.
This GDB was configured as i386-undermydesk-freebsd...
panic: sent too much
panic messages:
---
---
Reading symbols from 
/usr/obj/usr/src/sys/BEASTIE/modules/usr/src/sys/modules/acpi/acpi.ko.debug...done.
Loaded symbols for 
/usr/obj/usr/src/sys/BEASTIE/modules/usr/src/sys/modules/acpi/acpi.ko.debug
#0  doadump () at /usr/src/sys/kern/kern_shutdown.c:240
240 dumping++;
(kgdb) where
#0  doadump () at /usr/src/sys/kern/kern_shutdown.c:240
#1  0xc019b6ef in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:372
#2  0xc019ba77 in panic () at /usr/src/sys/kern/kern_shutdown.c:550
#3  0xc022c240 in tcp_input (m=0xc0a3f300, off0=20) at 
/usr/src/sys/netinet/tcp_input.c:2310
#4  0xc0221893 in ip_input (m=0xc0a3f300) at /usr/src/sys/netinet/ip_input.c:950
#5  0xc020cca2 in swi_net (dummy=0x0) at /usr/src/sys/net/netisr.c:236
#6  0xc0189692 in ithread_loop (arg=0xc09f9c00) at /usr/src/sys/kern/kern_intr.c:534
#7  0xc01886bf in fork_exit (callout=0xc0189510 ithread_loop, arg=0x0, frame=0x0)
at /usr/src/sys/kern/kern_fork.c:796
(kgdb) bt full
#0  doadump () at /usr/src/sys/kern/kern_shutdown.c:240
No locals.
#1  0xc019b6ef in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:372
No locals.
#2  0xc019ba77 in panic () at /usr/src/sys/kern/kern_shutdown.c:550
td = (struct thread *) 0xc0a07ab0
bootopt = 256
newpanic = 1
ap = 0xc6242b20 Hf
buf = sent too much, '\0' repeats 242 times
#3  0xc022c240 in tcp_input (m=0xc0a3f300, off0=20) at 
/usr/src/sys/netinet/tcp_input.c:2310
th = (struct tcphdr *) 0xc0c3f834
ip = (struct ip *) 0xc0c3f820
ipov = (struct ipovly *) 0x16bc
inp = (struct inpcb *) 0xc176aab0
optp = (u_char *) 0xc0c3f848 \001\001\b\n
optlen = 12
len = -1460824075
tlen = 0
off = -1460824075
drop_hdrlen = 52
tp = (struct tcpcb *) 0xc189a858
thflags = 5820
so = (struct socket *) 0xc1888700
todrop = -1460824075
acked = -1460824075
ourfinisacked = -1460824075
needoutput = 0
tiwin = 57600
to = {to_flags = 1, to_tsval = 517689, to_tsecr = 169603, to_cc = 0, to_ccecho 
= 0, to_mss = 0, 
  to_requested_s_scale = 0 '\0', to_pad = 0 '\0'}
taop = (struct rmxp_tao *) 0xa8ed97f5
tao_noncached = {tao_cc = 3324259320, tao_ccsent = 3324259328, tao_mssopt = 
10971}
headlocked = 1
next_hop = (struct sockaddr_in *) 0x0
rstreason = -1460824075
---Type return to continue, or q return to quit---
#4  0xc0221893 in ip_input (m=0xc0a3f300) at /usr/src/sys/netinet/ip_input.c:950
ip = (struct ip *) 0xc0c3f820
fp = (struct ipq *) 0xc02efe4d
ia = (struct in_ifaddr *) 0xc1578c00
ifa = (struct ifaddr *) 0x0
i = 0
hlen = 20
checkif = 1
sum = 0
pkt_dst = {s_addr = 126970842}
divert_info = 0
args = {m = 0xc0191c00, oif = 0x0, next_hop = 0x0, rule = 0x0, eh = 0x0, ro = 
0xe000, 
  dst = 0xc0369ff4, flags = 233, f_id = {dst_ip = 3224305229, src_ip = 3324259512, 
dst_port = 7120, 
src_port = 49177, proto = 244 '?, flags = 159 '\237'}, divert_rule = 0, retval = 
3224267492}
#5  0xc020cca2 in swi_net (dummy=0x0) at /usr/src/sys/net/netisr.c:236
ni = (struct netisr *) 0xc0367030
m = (struct mbuf *) 0xc0a3f300
bits = 2147483648
i = 0
#6  0xc0189692 in ithread_loop (arg=0xc09f9c00) at /usr/src/sys/kern/kern_intr.c:534
ithd = (struct ithd *) 0xc09f9c00
ih = (struct intrhand *) 0xc09fdd80
td = (struct thread *) 0xc0a07ab0
p = (struct proc *) 0xc0a06790
#7  0xc01886bf in fork_exit (callout=0xc0189510 ithread_loop, arg=0x0, frame=0x0)
at /usr/src/sys/kern/kern_fork.c:796
p = (struct proc *) 0xc0a06790
td = (struct thread *) 0xc0a07ab0


Panic #2:

beastie# gdb -k kernel.debug /var/crash/vmcore.1
GNU gdb 5.2.1 (FreeBSD)
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.

Re: cvs commit: src/sbin/savecore savecore.8 savecore.c

2003-09-04 Thread Doug Barton
Ok, two days of silence - commit. :)  This is the first step of the
plan I suggested to make savecore behavior conditional in rc.d so that
we can run it safely(?) before swapon.

While the guys mentioned below did help with and review this patch, I'm
responsible for any screwups. :)

Doug


On Thu, 4 Sep 2003, Doug Barton wrote:

 dougb   2003/09/04 03:07:01 PDT

   FreeBSD src repository

   Modified files:
 sbin/savecoresavecore.8 savecore.c
   Log:
   Add a flag that reports the existence of a dump, and does nothing else.

   The immediate purpose for this option is to use it in rc.d so that we
   can make savecore behavior conditional.

   Tremendous assistance with ideas and sanity checking provided by tjr
   and [EMAIL PROTECTED]

   Revision  ChangesPath
   1.20  +12 -0 src/sbin/savecore/savecore.8
   1.64  +20 -4 src/sbin/savecore/savecore.c

 http://www.FreeBSD.org/cgi/cvsweb.cgi/src/sbin/savecore/savecore.8.diff?r1=1.19r2=1.20f=h
 http://www.FreeBSD.org/cgi/cvsweb.cgi/src/sbin/savecore/savecore.c.diff?r1=1.63r2=1.64f=h



-- 

This .signature sanitized for your protection

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


Entropy harvesting: interrupts ethernet point_to_point

2003-09-04 Thread Putinas
Hi all,
on the recent src with custom compiled kernel ( generic minus some stuff
what I don't need ) with firewall compiled in kernel , system infinitely
hangs on boot unless I press ctrl-c at this point:
Entropy harvesting: interrupts ethernet point_to_point
Same things happens on two different computers with nearly similar custom
kernel configuration
Could you tell me, what's causing the problem ?
* If needed I can submit my kernel configuration *

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


Re: config(8) KERNEL setting

2003-09-04 Thread Dag-Erling Smørgrav
John Birrell [EMAIL PROTECTED] writes:
 It would make more sense to me if kern.pre.mk contained this:

 KERNEL?=  kernel
 KERNEL_KO?=   ${KERNEL}
 KODIR?=   /boot/${KERNEL}

 Comments?

I have

Index: kern.pre.mk
===
RCS file: /home/ncvs/src/sys/conf/kern.pre.mk,v
retrieving revision 1.34
diff -u -r1.34 kern.pre.mk
--- kern.pre.mk 22 Aug 2003 15:41:44 -  1.34
+++ kern.pre.mk 29 Aug 2003 21:06:02 -
@@ -9,7 +9,8 @@
 # Can be overridden by makeoptions or /etc/make.conf
 KERNEL_KO?=kernel
 KERNEL?=   kernel
-KODIR?=/boot/${KERNEL}
+KODIR?=/boot/${KERN_IDENT}
+BOOTKODIR?=/boot/${KERNEL}

 M= ${MACHINE_ARCH}
 

and in /boot/loader.conf:

kernel=dwp_smp
#kernel=dwp_up

For old times' sake, I also have /boot/kernel as a symlink to
/boot/dwp_smp.  

I used to have a more extensive patch which created that symlink at
kernel install time so you wouldn't need to modify loader.conf, and
the system would boot whichever kernel you installed last.  I removed
that part because I couldn't be bothered to make it work correctly
with all combinations of make install / make reinstall and
pre-existing /boot/kernel directory or symlink.

DES
-- 
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Entropy harvesting: interrupts ethernet point_to_point

2003-09-04 Thread Dag-Erling Smørgrav
Putinas [EMAIL PROTECTED] writes:
 on the recent src with custom compiled kernel ( generic minus some stuff
 what I don't need ) with firewall compiled in kernel , system infinitely
 hangs on boot unless I press ctrl-c at this point:
 Entropy harvesting: interrupts ethernet point_to_point
 Same things happens on two different computers with nearly similar custom
 kernel configuration
 Could you tell me, what's causing the problem ?

Try adding 'set -x' at the top of /etc/rc (not before the #!/bin/sh
line, though), and you should see what command is executed before the
script hangs.

DES
-- 
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Entropy harvesting: interrupts ethernet point_to_point

2003-09-04 Thread Mark Murray
Putinas writes:
 Hi all,
 on the recent src with custom compiled kernel ( generic minus some stuff
 what I don't need ) with firewall compiled in kernel , system infinitely
 hangs on boot unless I press ctrl-c at this point:
 Entropy harvesting: interrupts ethernet point_to_point
 Same things happens on two different computers with nearly similar custom
 kernel configuration
 Could you tell me, what's causing the problem ?
 * If needed I can submit my kernel configuration *

When it hangs, please press ctrl-T, and report back the status line that
you get in response.

Thanks!

M
--
Mark Murray
iumop ap!sdn w,I idlaH
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: config(8) KERNEL setting

2003-09-04 Thread John Birrell
On Thu, Sep 04, 2003 at 12:31:33PM +0200, Dag-Erling Sm?rgrav wrote:
 I have
 
 Index: kern.pre.mk
 ===
 RCS file: /home/ncvs/src/sys/conf/kern.pre.mk,v
 retrieving revision 1.34
 diff -u -r1.34 kern.pre.mk
 --- kern.pre.mk 22 Aug 2003 15:41:44 -  1.34
 +++ kern.pre.mk 29 Aug 2003 21:06:02 -
 @@ -9,7 +9,8 @@
  # Can be overridden by makeoptions or /etc/make.conf
  KERNEL_KO?=kernel
  KERNEL?=   kernel
 -KODIR?=/boot/${KERNEL}
 +KODIR?=/boot/${KERN_IDENT}
 +BOOTKODIR?=/boot/${KERNEL}
 
  M= ${MACHINE_ARCH}
  
 
 and in /boot/loader.conf:
 
 kernel=dwp_smp
 #kernel=dwp_up

My kernel is intended for netbooting and the loader isn't needed.

It seems what I really should be using is:

makeoptions KERNEL_KO=foo

That gives me what I need.

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


Re: Entropy harvesting: interrupts ethernet point_to_point

2003-09-04 Thread Vaidas Damosevicius

On Thu, 4 Sep 2003, Putinas wrote:

 Hi all,
 on the recent src with custom compiled kernel ( generic minus some stuff
 what I don't need ) with firewall compiled in kernel , system infinitely
 hangs on boot unless I press ctrl-c at this point:
 Entropy harvesting: interrupts ethernet point_to_point
 Same things happens on two different computers with nearly similar custom
 kernel configuration
 Could you tell me, what's causing the problem ?
 * If needed I can submit my kernel configuration *

Strange, but the same problem I had on my Compaq Evo N610C with ACPI
turned on. Without ACPI all works well ...


 Regards,
 Putinas Piliponis


vd

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


Re: ATAng - copying atapi CD

2003-09-04 Thread Bryan Liesner
On Wed, 3 Sep 2003, Terry Lambert wrote:

 Bryan Liesner wrote:
  On Wed, 3 Sep 2003, Martin wrote:
   If you notice that your CD-R label looks strange and if you need
   the data, you should backup it fast.
 
  No, we're talking about brand new, factory pressed, audio CDs.

 Are they copy protected?

 The way you can tell is if you try to do what you are trying to
 do, and it fails the way that it's failing, then they are likely
 copy protected.


Possible, but if they are protected, wouldn't I be prevented from
copying any track, or do they pick a random track or two just to piss
me off?


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


RE: Multi BOOT

2003-09-04 Thread Andre Guibert de Bruet

On Thu, 4 Sep 2003, Abdul Hakeem wrote:



 Hello,
 Does anyone know a way of simultaneously booting FreeBSD with Linux or
 Win2K with a dual-processor and dual NIC server ?
 I can set the processor affinity on the Win2k, but I am having trouble
 configuring the FreeBSD to use a particular processor and a particular
 NIC.

To do server partitioning, you'll have to acquire a Unisys ES7000, IBM
zSeries or comparable system. Standard x86 multi-proc systems (As you
would buy from Dell, for example) do not support this.

You can however run Win2k inside VMware on a FreeBSD machine. This option
is even more flexible than partitioning as it lets you turn the VM off
and reacquire the resources that were tied up by it.

Regards,

 Andre Guibert de Bruet | Enterprise Software Consultant 
 Silicon Landmark, LLC. | http://siliconlandmark.com/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: ATAng - copying atapi CD

2003-09-04 Thread Matthias Andree
Soren Schmidt [EMAIL PROTECTED] writes:

 Can you play those discs in your cd-rw drive ?

Is this a useful test after all? Most drives go down to 1x playing
audio, which is nowhere near 52x or what's current nowadays.

-- 
Matthias Andree

Encrypt your mail: my GnuPG key ID is 0x052E7D95
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Entropy harvesting: interrupts ethernet point_to_point

2003-09-04 Thread Putinas
load: 0.95 cmd: sysctl 110 [running] 2.51m(micro) 12.00s 0% 436k ( here is
output from ctrl-t )

I did like sugested before , hanging point is:
[ -w /dev/random ]
feed_dev_random /entropy
[ -f /entropy -a -r /entropy -a -s /entropy ]
cat /entropy
dd of=/dev/random bs=8k
dd of=/dev/random bs=8k
ps -fauxww
sysctl -a

Actually what I forgot to tell in my previous mail what sysctl -a stoped
working for me, but now I see what this is actually and IS the problem.
if I do sysctl -a from console the last things what its output is:
net.inet.ipf.fr_minttl: 3
net.inet.ipf.fr_minttllog: 1
thats it , here I have to press ctrl-c

and also part of my custom kernel, I tried to commend RANDOM_IP_ID,
PFIL_HOOKS but I got same results :

options INCLUDE_CONFIG_FILE
options IPFIREWALL  #firewall
options IPFIREWALL_VERBOSE  #enable logging to syslogd(8)
options IPFIREWALL_FORWARD  #enable transparent proxy support
options IPFIREWALL_DEFAULT_TO_ACCEPT#allow everything by default
options IPV6FIREWALL#firewall for IPv6
options IPV6FIREWALL_VERBOSE
options IPV6FIREWALL_DEFAULT_TO_ACCEPT
options IPDIVERT#divert sockets
options IPFILTER#ipfilter support
options IPFILTER_LOG#ipfilter logging
options IPSTEALTH   #support for stealth forwarding
options PFIL_HOOKS
options TCPDEBUG
options RANDOM_IP_ID
options TCP_DROP_SYNFIN #drop TCP packets with SYN+FIN
options DUMMYNET
options BRIDGE
options DEVICE_POLLING

- Original Message - 
From: Mark Murray
To: Putinas
Cc: [EMAIL PROTECTED]
Sent: Thursday, September 04, 2003 12:40 PM
Subject: Re: Entropy harvesting: interrupts ethernet point_to_point


Putinas writes:
 Hi all,
 on the recent src with custom compiled kernel ( generic minus some stuff
 what I don't need ) with firewall compiled in kernel , system infinitely
 hangs on boot unless I press ctrl-c at this point:
 Entropy harvesting: interrupts ethernet point_to_point
 Same things happens on two different computers with nearly similar custom
 kernel configuration
 Could you tell me, what's causing the problem ?
 * If needed I can submit my kernel configuration *

When it hangs, please press ctrl-T, and report back the status line that
you get in response.

Thanks!

M
--
Mark Murray
iumop ap!sdn w,I idlaH
___
[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: usb mouse : /dev/ums0 not created ...

2003-09-04 Thread Ivan Georgiev
On Wednesday 03 September 2003 18:15, Mark Dixon wrote:
 Ivan Georgiev wrote:
 Hello,
 
 I am trying to use a USB mouse on 5.1-CURRENT (compiled today from the
  src), but the /dev/ums0 is not created by the device ... Tried with and
  without ACPI - in either case the ums0 is not created.
 
 in dmesg I see:
 
 ...
 device_probe_and_attach: ums0 attach returned 6
 ugen0: setting configuration index 0 failed
 ...
 
 Please, let me know what to do in order to get it working.
 Ivan

 Its not a Microsoft Mouse is it? Mine (a Wheel Mouse Optical)
 occasionally does this but works 9 times out of 10,

 Mark

No, it is not a Microsoft Mouse (wheel, optical, brand creative). It doesn't 
work under Linux either. Although, in linux /dev/input/mouse0 gets created 
... but if I cat /dev/input/mouse0 nothing shows up when I move the mouse. 
The only place where it works is windows ...
Do you think I should try another mouse ?

Thanks,
Ivan

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


Reminder: BSDCon next week in San Mateo!

2003-09-04 Thread Robert Watson

This is just a friendly reminder e-mail that the BSD Conference is taking
place in San Mateo next week, and that if you're planning to attend and
haven't yet registered, you might want to.  Or, just turn up and register
at the door.

There's a really strong lineup of FreeBSD-related papers, especially
relating to new features in the 5-CURRENT development line. I've attached
a list of just some of the interesting things that will be going on there:
they include a number of tutorials relating to development and
administration, technical session presentations relating to the
development of FreeBSD, development of products using FreeBSD, and the
deployment of FreeBSD-based systems.  And, as always, there will be a
variety of invited talks, BoFs and work-in-progress sessions. 

USENIX has extended their early registration pricing, and also (I believe) 
has an online registration discount.  Multi-employee discounts are also
available for companies sending more than one employee.  You can find out
more about the location, schedule of events, etc, at: 

  http://www.usenix.org/events/bsdcon03/

I look forward to seeing you there!

Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
[EMAIL PROTECTED]  Network Associates Laboratories


  Several excellent tutorials including one on developing storage
extensions using GEOM

  Keynote: Computing Fallacies (or, What Is the World Coming To?)

  Reasoning about SMP in FreeBSD

  devd-A Device Configuration Daemon

  ULE: A Modern Scheduler for FreeBSD

  An Automated Binary Security Update System for FreeBSD

  Building a High-performance Computing Cluster Using FreeBSD

  build.sh: Cross-building NetBSD

  Invited Talk: Long Range 802.11 WANs

  BSD Status Reports

  GBDE-GEOM Based Disk Encryption

  Cryptographic Device Support for FreeBSD

  Enhancements to the Fast Filesystem to Support Multi-Terabyte Storage
Systems

  Invited Talk: Social and Technical Implications of Nonproprietary
Software

  Running BSD Kernels as User Processes by Partial Emulation and Rewriting
of Machine Instructions

  A Digital Preservation Network Appliance Based on OpenBSD

  Using FreeBSD to Render Realtime Localized Audio and Video

  Work in Progess Reports (WiPs)

  Tagging Data in the Network Stack: mbuf_tags

  Fast IPSec: A High-Performance IPsec Implementation

  The WHBA Project: Experiences deeply embedding NetBSD

  Invited Talk: Post-Digital Possibilities


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


Text file busy

2003-09-04 Thread Paul Richards
Overwriting a file that's currently executing results in a Text file
busy error.

When did this start happening?

This was something that was fixed way back on FreeBSD but it seems to be
a problem again.

Paul.


intY has scanned this email for all known viruses (www.inty.com)

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


Re: Text file busy

2003-09-04 Thread Sheldon Hearn
On (2003/09/04 14:44), Paul Richards wrote:

 Overwriting a file that's currently executing results in a Text file
 busy error.
 
 When did this start happening?
 
 This was something that was fixed way back on FreeBSD but it seems to be
 a problem again.

Really?  I've never seen it fixed.  I've occasionally hit this problem
upgrading perl and exim for as long as I can remember.

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


Re: Text file busy

2003-09-04 Thread Scott M. Likens
On Thu, 2003-09-04 at 07:44, Paul Richards wrote:
 Overwriting a file that's currently executing results in a Text file
 busy error.
 
 When did this start happening?
 
 This was something that was fixed way back on FreeBSD but it seems to be
 a problem again.
 
 Paul.

this feature has always existed in FreeBSD for as long as I remember.

Of course there are ways to bypass this feature but it's there for
your protection.  You shouldn't be upgrading a program that's in
resident memory.  That's like trying to reinstall X while running in X. 
You're just asking for problems.

turnoff postfix, install the new version and be happy.

Every single 'flavor' of Unix/Unices has always had this feature.  I've
seen it on HP-UX box's on Solaris Servers, Linux, NetBSD, OpenBSD,
FreeBSD.  Maybe you wern't paying attention but, that is one of those
things I think should fall under duh, i shouldn't do that it might make
things crash hard.

Scott.
-- 
I think we ought to be out there doing what we do best - making large
holes in other people's countries. - George Carlin



signature.asc
Description: This is a digitally signed message part
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Text file busy

2003-09-04 Thread Stijn Hoop
On Thu, Sep 04, 2003 at 08:02:50AM -0700, Scott M. Likens wrote:
 That's like trying to reinstall X while running in X. 
 You're just asking for problems.

This has worked for me many times in the past :)

Of course it's on a (essentially) single user desktop, and I do a restart
after portupgrade -frRa finishes...

--Stijn

-- 
I wish there was a knob on the TV to turn up the intelligence.  There's a knob
called `brightness', but it doesn't work.
-- Gallagher


pgp0.pgp
Description: PGP signature


Re: Text file busy

2003-09-04 Thread John Polstra
On 04-Sep-2003 William K. Josephson wrote:
 On Thu, Sep 04, 2003 at 08:02:50AM -0700, Scott M. Likens wrote:
 Every single 'flavor' of Unix/Unices has always had this feature.  I've
 
 No, just recent ones.  One use to be able to page in from the wrong
 binary with rather entertaining results.

What's your idea of recent?  Even Unix V6 had EBUSY.  I ran
into it with regularity back then.

Anything with an errno value of 26 isn't what I'd call recent. :-)
Even the ancient EPIPE is 32.

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


Re: Text file busy

2003-09-04 Thread John Polstra
On 04-Sep-2003 John Polstra wrote:
 On 04-Sep-2003 William K. Josephson wrote:
 On Thu, Sep 04, 2003 at 08:02:50AM -0700, Scott M. Likens wrote:
 Every single 'flavor' of Unix/Unices has always had this feature.  I've
 
 No, just recent ones.  One use to be able to page in from the wrong
 binary with rather entertaining results.
 
 What's your idea of recent?  Even Unix V6 had EBUSY.

Oops, I meant ETXTBSY.

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


Re: wi0: cardbus card activation failed

2003-09-04 Thread M. Warner Losh
In message: [EMAIL PROTECTED]
[EMAIL PROTECTED] writes:
: Hello,
: I have same problem as 
http://lists.freebsd.org/pipermail/freebsd-current/2003-August/008948.html,
:  but with other PCMCIA card - new Proxim Orinoco.
: When I plug it in, I get:
: 
: cardbus0: network, ethernet at device 0.0 (no driver attached)
: cbb0: CardBus card activation failed
: 
: I use kernel from yestereday, pccbb.c ver 1.95.

You need a driver.  This message says that none attached.  Maybe
FreeBSD doesn't support this chip yet?  Maybe it is supported by the
atheros driver (ath).

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


Question about genassym, locore.s and 0-sized arrays (showstopper for an icc compiled kernel)

2003-09-04 Thread Alexander Leidinger
Hi,

I'm in the process of building our kernel with Intels C Compiler (icc).
So far we are able to build a working UP and SMP kernel (not completely
automated). Most of it works just fine (NFS-client is known to not
work).

At the moment I discussing an issue with Intel regarding 0-sized arrays.
gcc seems to be violating the standard and produces code with an array
size of 0, whereas icc produces code where an 0-sized array has the
size 1. This results in different nm output of genassym.o:

gcc generated:
---snip---
 C BC32SELsign
0050 C BC32SELw0
 C BC32SELw1
 C BC32SELw2
 C BC32SELw3
---snip---

icc generated:
---snip---
0001 C BC32SELsign
0050 C BC32SELw0
0001 C BC32SELw1
0001 C BC32SELw2
0001 C BC32SELw3
---snip---

Thus the output of genassym.sh with a icc generated genassym.o is wrong:
---snip---
#define BC32SEL -0x1000100010050
#define BI_ENDCOMMON-0x100010001000c
#define BI_ESYMTAB  -0x1000100010044
#define BI_KERNELNAME   -0x1000100010004
#define BI_KERNEND  -0x1000100010048
#define BI_NFS_DISKLESS -0x1000100010008
#define BI_SIZE -0x1000100010030
---snip---

With a gcc generated genassym.o it looks like:
---snip---
#define BC32SEL 0x50
#define BI_ENDCOMMON0xc
#define BI_ESYMTAB  0x44
#define BI_KERNELNAME   0x4
#define BI_KERNEND  0x48
#define BI_NFS_DISKLESS 0x8
#define BI_SIZE 0x30
---snip---

At least the generated defines are used in locore.s, but is this the
only consumer of this feature? What I need to know is:
 - Do we really depend on 0-sized arrays in the code or is it just a
   genassym.sh issue?
 - If we depend on it: how hard would it be to rewrite it to not depend
   on 0-sized arrays (and does someone volunteer to rewrite it)? It
   would be nice if someone could point me to the source if it isn't
   an easy task, my contact @Intel is willing to convince the
   developers to change icc, but he has to present a persuasive argument
   to development to pursue a solution.
 - If it is a genassym.sh issue: would someone with enough glue please
   provide me with a patch for genassym.sh which either uses a switch
   to understand the icc generated file or is able to detect it on it's
   own (I'm able to provide the output of nm and/or the object file)?
   Or at least describes what needs to be done, so I can try do do it
   myself after refreshing my awk knowledge?

Bye,
Alexander.

-- 
Failure is not an option. It comes bundled with your Microsoft product.

http://www.Leidinger.net   Alexander @ Leidinger.net
  GPG fingerprint = C518 BC70 E67F 143F BE91  3365 79E2 9C60 B006 3FE7
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Question about genassym, locore.s and 0-sized arrays (showstopper for an icc compiled kernel)

2003-09-04 Thread Dan Nelson
In the last episode (Sep 04), Alexander Leidinger said:
 At the moment I discussing an issue with Intel regarding 0-sized
 arrays. gcc seems to be violating the standard and produces code with
 an array size of 0, whereas icc produces code where an 0-sized
 array has the size 1. This results in different nm output of
 genassym.o:
[snip] 
  - If we depend on it: how hard would it be to rewrite it to not depend
on 0-sized arrays (and does someone volunteer to rewrite it)? It
would be nice if someone could point me to the source if it isn't
an easy task, my contact @Intel is willing to convince the
developers to change icc, but he has to present a persuasive
argument to development to pursue a solution.

If you're talking FreeBSD 5, you should be able to simply subsitute a
C99 flexible array member (basically replace [0] with []) and get
the same effect.  0-length arrays are a gcc extension:

http://gcc.gnu.org/onlinedocs/gcc/Zero-Length.html

Under FreeBSD 4.x, you can't use them because gcc 2.95 only supports
the gcc extension.  Intel has added support for a lot of gcc extensions
recently; they may be willing to add this to the list.

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


Re: Entropy harvesting: interrupts ethernet point_to_point

2003-09-04 Thread Doug Barton
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I've seen this problem on my compaq evo n610c as well, but didn't
realize it was affecting other hardware as well. I tried to stir up
interest in getting the acpi problem fixed, but wasn't successful.

Mark, ok with you if I nuke the sysctl -a line in rc.d/initrandom? I
hate to lose that source (no matter how small), but if the can't finish
sysctl -a cancer is spreading...

Doug

- -- 

This .signature sanitized for your protection

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQE/V2i4yIakK9Wy8PsRAj9xAKDln9La1f89JUzxNm4Q9OlQbFD5PgCgyUuO
A8HcT5QFudf0ohwrpDebZTE=
=qrg7
-END PGP SIGNATURE-
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Text file busy

2003-09-04 Thread Mikko Työläjärvi
On Thu, 4 Sep 2003, Scott M. Likens wrote:

 On Thu, 2003-09-04 at 07:44, Paul Richards wrote:
  Overwriting a file that's currently executing results in a Text file
  busy error.
 
  When did this start happening?
 
  This was something that was fixed way back on FreeBSD but it seems to be
  a problem again.
 
  Paul.

 this feature has always existed in FreeBSD for as long as I remember.

 Of course there are ways to bypass this feature but it's there for
 your protection.  You shouldn't be upgrading a program that's in
 resident memory.  That's like trying to reinstall X while running in X.
 You're just asking for problems.

 turnoff postfix, install the new version and be happy.

 Every single 'flavor' of Unix/Unices has always had this feature.  I've
 seen it on HP-UX box's on Solaris Servers, Linux, NetBSD, OpenBSD,
 FreeBSD.  Maybe you wern't paying attention but, that is one of those
 things I think should fall under duh, i shouldn't do that it might make
 things crash hard.

SunOS 4 let you overwrite binaries for running programs, which almost
surely made them crash.  HP-UX has the annoying misfeature that you
cannot even unlink a binary used for paging.

The way to do it is to mv/rm te target before installing the new
version.  AFAIK install(1) will do the right thing.

If you are into foot shooting, you can always overwrite a shared lib,
such as libc.so, and watch (almost) all your programs crash and burn :-)

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


CF cards cannot be initialized after the latest update

2003-09-04 Thread Martin Jessa
Hi.

After my latest upgrade I am unable to use my CF cards.
This is what happens running on following FreeBSD version:
FreeBSD lapdance 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Wed Sep  3 04:46:09 CEST 2003 
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/LAPDANCE  i386

Card out and in again:

ad4: WARNING - removed from configuration
ata2-master: WARNING no status, reselecting device
ata2-master: timeout sending command=e7
ata2-master: error issueing PIO command
ata2: detached
pccard0: Allocation failed for cfe 0
ata2: CL ATA FLASH CARD LEXAR   TIDALWV at port 0x110-0x11f irq 11 function 0 config 
1 on pccard0
ad4: FAILURE - SETFEATURES status=51READY,DSC,ERROR error=4ABORTED
ad4: FAILURE - SETFEATURES status=51READY,DSC,ERROR error=4ABORTED
ad4: FAILURE - SET_MULTI status=51READY,DSC,ERROR error=4ABORTED
GEOM: create disk ad4 dp=0xc34b5170
ad4: 9007199253773098MB 
\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P
 [426376296036596/208/208] at ata2-master PIO0
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Entropy harvesting: interrupts ethernet point_to_point

2003-09-04 Thread Putinas
But I wonder, what sysctl has to do with hardware ?

  - Original Message - 
  From: Doug Barton 
  To: Putinas 
  Cc: [EMAIL PROTECTED] ; Mark Murray 
  Sent: Thursday, September 04, 2003 18:30 PM
  Subject: Re: Entropy harvesting: interrupts ethernet point_to_point 


  -BEGIN PGP SIGNED MESSAGE-
  Hash: SHA1

  I've seen this problem on my compaq evo n610c as well, but didn't
  realize it was affecting other hardware as well. I tried to stir up
  interest in getting the acpi problem fixed, but wasn't successful.

  Mark, ok with you if I nuke the sysctl -a line in rc.d/initrandom? I
  hate to lose that source (no matter how small), but if the can't finish
  sysctl -a cancer is spreading...

  Doug

  - -- 

  This .signature sanitized for your protection

  -BEGIN PGP SIGNATURE-
  Version: GnuPG v1.2.3 (FreeBSD)

  iD8DBQE/V2i4yIakK9Wy8PsRAj9xAKDln9La1f89JUzxNm4Q9OlQbFD5PgCgyUuO
  A8HcT5QFudf0ohwrpDebZTE=
  =qrg7
  -END PGP SIGNATURE-
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Text file busy

2003-09-04 Thread Ruslan Ermilov
On Thu, Sep 04, 2003 at 02:44:13PM +, Paul Richards wrote:
 Overwriting a file that's currently executing results in a Text file
 busy error.
 
 When did this start happening?
 
 This was something that was fixed way back on FreeBSD but it seems to be
 a problem again.
 
cp -f


Cheers,
-- 
Ruslan Ermilov  Sysadmin and DBA,
[EMAIL PROTECTED]   Sunbay Software Ltd,
[EMAIL PROTECTED]   FreeBSD committer


pgp0.pgp
Description: PGP signature


Re: config(8) KERNEL setting

2003-09-04 Thread David O'Brien
On Wed, Sep 03, 2003 at 09:22:09PM -0700, Doug White wrote:
 On Thu, 4 Sep 2003, John Birrell wrote:
 
  however kern.post.mk only uses KERNEL_KO, so even though config(8) has
  set KERNEL for me, that name only gets used for the boot directory.
  There doesn't seem to be any way of getting KERNEL_KO set from the
  kernel config file.
 
 If you change the name of the kernel binary itself, loader won't be able
 to find it.

Depends on what you rename it to -- mine is kernel.ko to stress it
really is just another module.  Our loader finds it fine (as .ko is one
of the supported extentions).
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Compaq desktop does not work without ACPI

2003-09-04 Thread Oleg Polyakov

From: Doug White [EMAIL PROTECTED]

On Wed, 3 Sep 2003, Oleg Polyakov wrote:

 Hm, ATAng went in since 5.1-R, so I wonder if it is having issues 
reading
 from the disk then. How long have you let it sit trying to start init?
 Does it give random disk errors?

 I let it try to start for about an hour three or four times...
 It just sits and does not show anything at all.
 If booted with ACPI there are no disk errors.

Does it work at all with ACPI?  I don't follow you there.
With ACPI it works just fine, exactly as it worked before without ACPI with 
5.1-Release.
I just wanted to say there are no disk errors/warnings at all.

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]
_
Send and receive larger attachments with Hotmail Extra Storage.   
http://join.msn.com/?PAGE=features/es

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


Re: Please test: USB floppies

2003-09-04 Thread Nate Lawson
On Thu, 28 Aug 2003, Harald Schmalzbauer wrote:
 On Thursday 28 August 2003 21:35, Nate Lawson wrote:
  On Tue, 26 Aug 2003, Harald Schmalzbauer wrote:
   On Monday 25 August 2003 23:19, Nate Lawson wrote:
If anyone has a USB floppy drive that is giving them problems, please
let me know.
  
   Hello,
  
   this one needs NO_SYNC I think.
  
   Played a bit some time ago but had no luck (I'm no programmer)
  
   port 1 addr 2: full speed, power 500 mA, config 1, NEC USB
   UF000x(0x0040), NEC(0x0409), rev 1.23

 *SNIP*

 
  Have you tried it again since early August?  Also, what is the exact
  behavior when you try to mount or read it?

 Mounting, reading writing and umounting is working without errors, just these
 warnings.

 Here are the one from today's world:
 umass0: NEC NEC USB UF000x, rev 1.10/1.23, addr 4
 (probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 0 0 0 24 0
 (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
 (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition
 (probe0:umass-sim0:0:0:0): UNIT ATTENTION asc:29,0
 (probe0:umass-sim0:0:0:0): Power on, reset, or bus device reset occurred
 (probe0:umass-sim0:0:0:0): Retrying Command (per Sense Data)
 da0 at umass-sim0 bus 0 target 0 lun 0
 da0: NEC USB UF000x 1.23 Removable Direct Access SCSI-0 device
 da0: 1.000MB/s transfers
 da0: 1MB (2880 512 byte sectors: 64H 32S/T 1C)
 umass0: Unsupported UFI command 0x35
 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x6, scsi status
 == 0x0
 umass0: Unsupported UFI command 0x35
 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x6, scsi status
 == 0x0
 umass0: Unsupported UFI command 0x35
 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x6, scsi status
 == 0x0
 umass0: Unsupported UFI command 0x35
 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x6, scsi status
 == 0x0

While annoying, if your device doesn't hang or fail to operate, it does
not need a quirk.

So far, I have had no reports of USB devices with old quirks actually
failing when their quirks were disabled.  Once again, anything under
DA_OLD_QUIRKS will be removed after the release.

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


Re: Text file busy

2003-09-04 Thread Tim Kientzle
Paul Richards wrote:
Overwriting a file that's currently executing results in a Text file
busy error.
I guess there are folks around who don't know this:

When you execute a program, the program is not simply copied
into memory.  Instead, the kernel keeps the file open and pages the
executable in as necessary.  This is called demand-paging of
executables and it's an old performance optimization that
improves VM operation (executable code never needs to be copied
out to swap; it can just be dumped and paged back in later) and
quickens application startup (only the immediately-required
parts of the application are read into memory immediately).
I'm not certain, but I suspect it first appeared in Unix in
the mid-1970s.
In essence, the file _is_ the executable contents of memory.
Overwriting it is almost always a bad idea; if the
system has to swap in another part of that executable,
the program is almost certain to crash.
This was something that was fixed way back on FreeBSD but it seems to be
a problem again.
Depends on how you're installing the binary.  It has always been
safe to do either of the following:
  * Rename the current executable and then install the new one.
  * Unlink the current executable and then install the new one.
Many tools that claim to overwrite really do the latter, which
causes a certain amount of understandable confusion.  (I'm pretty
sure install does unlink/copy by default and will do rename/copy
if you specify -b.)
True overwriting of in-use executable files (e.g., cat new  old)
is dangerous and should be prohibited.
Tim

P.S. I wonder if demand-paging of executables is still a win for
program startup on modern systems with dynamically-linked executables?
Large reads are a lot more efficient, and it seems that dynamic
linking might cause more startup thrashing.  Hmmm...
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


[Patch] mdmfs currently broken

2003-09-04 Thread Stefan Eßer
Seems that mdmfs stopped working recently (probably because
of GEOM related changes). One possible fix is to label the
md and newfs the thusly created c partition.

This requires running /sbin/disklabel, which didn't have an
entry in paths.h.

Any objections against me committing the follwoing fixes to
-current ?

Should md0c be used as a parameter to mdmfs instead of md0
(and should it be printed in df and mount output) ???

Regards, STefan



Index: include/paths.h
===
RCS file: /usr/cvs/src/include/paths.h,v
retrieving revision 1.24
diff -u -3 -r1.24 paths.h
--- include/paths.h 29 Jun 2003 18:35:36 -  1.24
+++ include/paths.h 4 Sep 2003 18:12:27 -
@@ -58,6 +58,7 @@
 #define_PATH_DEFTAPE   /dev/sa0
 #define_PATH_DEVNULL   /dev/null
 #define_PATH_DEVZERO   /dev/zero
+#define_PATH_DISKLABEL /sbin/disklabel
 #define_PATH_DRUM  /dev/drum
 #define_PATH_ETC   /etc
 #define_PATH_FTPUSERS  /etc/ftpusers
@@ -113,6 +114,8 @@
 #define_PATH_CP/rescue/cp
 #undef _PATH_CSHELL
 #define_PATH_CSHELL/rescue/csh
+#undef _PATH_DISKLABEL
+#define_PATH_DISKLABEL /rescue/disklabel
 #undef _PATH_HALT
 #define_PATH_HALT  /rescue/halt
 #undef _PATH_IFCONFIG
Index: sbin/mdmfs/mdmfs.c
===
RCS file: /usr/cvs/src/sbin/mdmfs/mdmfs.c,v
retrieving revision 1.17
diff -u -3 -r1.17 mdmfs.c
--- sbin/mdmfs/mdmfs.c  5 Aug 2003 15:04:39 -   1.17
+++ sbin/mdmfs/mdmfs.c  4 Sep 2003 18:09:02 -
@@ -77,6 +77,7 @@
 static void do_mount(const char *, const char *);
 static void do_mtptsetup(const char *, struct mtpt_info *);
 static void do_newfs(const char *);
+static void do_disklabel(void);
 static void extract_ugid(const char *, struct mtpt_info *);
 static int  run(int *, const char *, ...) __printflike(2, 3);
 static void usage(void);
@@ -264,6 +265,7 @@
do_mdconfig_attach_au(mdconfig_arg, mdtype);
else
do_mdconfig_attach(mdconfig_arg, mdtype);
+   do_disklabel();
do_newfs(newfs_arg);
do_mount(mount_arg, mtpoint);
do_mtptsetup(mtpoint, mi);
@@ -467,6 +469,19 @@
 }
 
 /*
+ * Write simple disklabel
+ */
+static void
+do_disklabel(void)
+{
+   int rv;
+
+   rv = run(NULL, %s -w /dev/%s%d auto, _PATH_DISKLABEL, mdname, unit);
+   if (rv)
+   errx(1, disklabel exited with error code %d, rv);
+}
+
+/*
  * Put a file system on the memory disk.
  */
 static void
@@ -474,7 +489,7 @@
 {
int rv;
 
-   rv = run(NULL, %s%s /dev/%s%d, _PATH_NEWFS, args, mdname, unit);
+   rv = run(NULL, %s%s /dev/%s%dc, _PATH_NEWFS, args, mdname, unit);
if (rv)
errx(1, newfs exited with error code %d, rv);
 }
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Text file busy

2003-09-04 Thread Matthew Dillon
:
:Tim
:
:P.S. I wonder if demand-paging of executables is still a win for
:program startup on modern systems with dynamically-linked executables?
:Large reads are a lot more efficient, and it seems that dynamic
:linking might cause more startup thrashing.  Hmmm...

Yes, they are a big win 95% of the time.  Don't worry, the kernel will
pre-fault pages that are already cached in memory (to a point), and
the kernel will also cluster pagein operations if actual I/O becomes
necessary.

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


Re: Entropy harvesting: interrupts ethernet point_to_point

2003-09-04 Thread Mark Murray
Doug Barton writes:
 I've seen this problem on my compaq evo n610c as well, but didn't
 realize it was affecting other hardware as well. I tried to stir up
 interest in getting the acpi problem fixed, but wasn't successful.

Hmmm :-(

 Mark, ok with you if I nuke the sysctl -a line in rc.d/initrandom? I
 hate to lose that source (no matter how small), but if the can't finish
 sysctl -a cancer is spreading...

I'd really rather see sysctl fixed, rather than weakening Innocent
Bystanders, but I'm not going to force this issue. So, reluctantly,
yes, if you can't find a better place to hack a fix.

M
--
Mark Murray
iumop ap!sdn w,I idlaH
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


/lib/foo.so.X - /usr/lib/foo.so

2003-09-04 Thread Ruslan Ermilov
On Thu, Sep 04, 2003 at 09:58:39PM +0300, Ruslan Ermilov wrote:
[...]
 The patch is not a problem (attached).  I've been looking at
 how our friends do this.  NetBSD has symlinks in /usr/lib to
 /lib, both to .so and .so.X, and their cc(1) and ld(1) don't
 look things in /lib.  Linux looks things up in both /lib and
 /usr/lib, and does not have symlinks from /usr/lib to /lib.
 
There is a sad typo above: Linux *does* have symlinks from
/usr/lib to /lib, so both use /usr/lib for linking.

 The only reason while I still think we should support both
 /lib and /usr/lib in cc(1) and ld(1) by default is to allow
 our users to have /usr symlinked somethere, otherwise relative
 symlinking from /usr/lib to ../../lib does not work, and we
 are back to that endless thread.
 
Not that I'm completely happy with introducing yet another
variable in bsd.lib.mk, but the attached patch:

- Leaves only one set of .so symlinks in /usr/lib.

  Benefits: all other systems that use both /lib and /usr/lib
  (that I've been able to test) have .so links in /usr/lib
  only, and use them for linking; GCC in ports will like this
  better.

- Uses absolute paths in .so symlinks.

  Benefit: works for people who have their /usr symlinked
  somewhere.

- Works without any more modifications to GCC.  ld(1)
  hacks can go away too.

Please review.


Cheers,
-- 
Ruslan Ermilov  Sysadmin and DBA,
[EMAIL PROTECTED]   Sunbay Software Ltd,
[EMAIL PROTECTED]   FreeBSD committer
Index: Makefile.inc1
===
RCS file: /home/ncvs/src/Makefile.inc1,v
retrieving revision 1.389
diff -u -r1.389 Makefile.inc1
--- Makefile.inc1   1 Sep 2003 06:43:24 -   1.389
+++ Makefile.inc1   4 Sep 2003 19:30:19 -
@@ -227,6 +227,7 @@
 # world stage
 WMAKEENV=  ${CROSSENV} \
DESTDIR=${WORLDTMP} \
+   SHLIBDIRPREFIX=${WORLDTMP} \
INSTALL=sh ${.CURDIR}/tools/install.sh \
PATH=${TMPPATH}
 WMAKE= ${WMAKEENV} ${MAKE} -f Makefile.inc1
Index: share/mk/bsd.lib.mk
===
RCS file: /home/ncvs/src/share/mk/bsd.lib.mk,v
retrieving revision 1.153
diff -u -r1.153 bsd.lib.mk
--- share/mk/bsd.lib.mk 4 Sep 2003 04:29:11 -   1.153
+++ share/mk/bsd.lib.mk 4 Sep 2003 19:34:08 -
@@ -208,9 +208,10 @@
${_INSTALLFLAGS} ${_SHLINSTALLFLAGS} \
${SHLIB_NAME} ${DESTDIR}${SHLIBDIR}
 .if defined(SHLIB_LINK)
-   ln -fs ${SHLIB_NAME} ${DESTDIR}${SHLIBDIR}/${SHLIB_LINK}
-.if (${LIBDIR} != ${SHLIBDIR})
-   ln -fs ${LIBDIR:C|/[^/]+|/..|g:S|^/||}${SHLIBDIR}/${SHLIB_NAME} \
+.if ${SHLIBDIR} == ${LIBDIR}
+   ln -fs ${SHLIB_NAME} ${DESTDIR}${LIBDIR}/${SHLIB_LINK}
+.else
+   ln -fs ${SHLIBDIRPREFIX}${SHLIBDIR}/${SHLIB_NAME} \
${DESTDIR}${LIBDIR}/${SHLIB_LINK}
 .endif
 .endif


pgp0.pgp
Description: PGP signature


Data corruption issue? (Was: NFS writes over a VLAN trunk wedges system)

2003-09-04 Thread Georg-W. Koltermann
Just trying to make sure Bosko takes note of this.  He might have
something to say as DISABLE_PSE appears to fix your problem.

--
Regards,
Georg.

On Do, 2003-09-04 at 00:02, Peter Jeremy wrote:
 I have a system running 5.1-RELEASE-p2 which is an NFS client of
 another FreeBSD (4.x) machine.  When I have the NFS mount via a VLAN
 the system reliably hangs (no response to console, including
 Ctrl-Alt-Esc).  This is a default NFS mount (no options) and I am
 trying to do a buildworld with /usr/{src,obj} NFS mounted.  The VLAN
 is using an Intel fxp NIC.  The kernel has DEVICE_POLLING specified
 but not enabled.
 
 - NFS mount to the same server via normal Ethernet (using a 3Com 905
   NIC) successfully manages buildworld
 - Adding WITNESS and INVARIANTS didn't help (though it lasted longer
   before dying)
 - Enabling device polling didn't help
 - Adding DISABLE_PSE allows it to complete a buildworld
 
 Any suggestions on where to go next?
 
 Peter
 ___
 [EMAIL PROTECTED] mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-current
 To unsubscribe, send any mail to [EMAIL PROTECTED]
-- 
Grüße,
Georg.


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


Re: make buildworld broken in telnetd

2003-09-04 Thread Doug White
On Wed, 3 Sep 2003, Manfred Antar wrote:

 I think 1.152  is broken.
 I did a make world and install world.
 I rebooted and login and sshd couldn't find pam_nologin.so
 and it was right there in /usr/lib. I had to restore the pam libs and sshd and login 
 from
 tape before I could login to the machine.

Nice.  Peter Wemm reverted it last night so it should be okay to resup.

-- 
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: [Patch] mdmfs currently broken

2003-09-04 Thread Poul-Henning Kamp
In message [EMAIL PROTECTED], Stefan =?iso-8859-
1?Q?E=DFer?= writes:
Seems that mdmfs stopped working recently (probably because
of GEOM related changes). One possible fix is to label the
md and newfs the thusly created c partition.

This requires running /sbin/disklabel, which didn't have an
entry in paths.h.

Any objections against me committing the follwoing fixes to
-current ?

Yes, please don't.

We should not revert to putting BSD labels on everything.

I'll find the root cause and fix that instead, it's probably
fall-out from my ioctl change.

-- 
Poul-Henning Kamp   | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer   | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: /lib/foo.so.X - /usr/lib/foo.so

2003-09-04 Thread David O'Brien
On Thu, Sep 04, 2003 at 11:27:15PM +0300, Ruslan Ermilov wrote:
 On Thu, Sep 04, 2003 at 09:58:39PM +0300, Ruslan Ermilov wrote:
 [...]
  The patch is not a problem (attached).  I've been looking at
  how our friends do this.  NetBSD has symlinks in /usr/lib to
  /lib, both to .so and .so.X, and their cc(1) and ld(1) don't
  look things in /lib.  Linux looks things up in both /lib and
  /usr/lib, and does not have symlinks from /usr/lib to /lib.
  
 There is a sad typo above: Linux *does* have symlinks from
 /usr/lib to /lib, so both use /usr/lib for linking.

What version of Linux are you using?  SuSE Enterprise Linux 8, and Red
Hat Enterprise Linux 3 both do not have symlinks for libs from /usr/lib
to /lib.  They use a different machanism:


suse# cat /usr/lib/libc.so
/* GNU ld script
   Use the shared library, but some functions are only in
   the static library, so try that secondarily.  */
GROUP ( /lib/libc.so.6 /usr/lib/libc_nonshared.a )

 
 Not that I'm completely happy with introducing yet another
 variable in bsd.lib.mk, but the attached patch:
 
 - Leaves only one set of .so symlinks in /usr/lib.
 
   Benefits: all other systems that use both /lib and /usr/lib
   (that I've been able to test) have .so links in /usr/lib
   only, and use them for linking; GCC in ports will like this
   better.
 
 - Uses absolute paths in .so symlinks.
 
   Benefit: works for people who have their /usr symlinked
   somewhere.

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


Re: /lib/foo.so.X - /usr/lib/foo.so

2003-09-04 Thread Dan Nelson
In the last episode (Sep 04), David O'Brien said:
 On Thu, Sep 04, 2003 at 11:27:15PM +0300, Ruslan Ermilov wrote:
  On Thu, Sep 04, 2003 at 09:58:39PM +0300, Ruslan Ermilov wrote:
  [...]
   The patch is not a problem (attached).  I've been looking at how
   our friends do this.  NetBSD has symlinks in /usr/lib to /lib,
   both to .so and .so.X, and their cc(1) and ld(1) don't look
   things in /lib.  Linux looks things up in both /lib and /usr/lib,
   and does not have symlinks from /usr/lib to /lib.
   
  There is a sad typo above: Linux *does* have symlinks from /usr/lib
  to /lib, so both use /usr/lib for linking.
 
 What version of Linux are you using?  SuSE Enterprise Linux 8, and
 Red Hat Enterprise Linux 3 both do not have symlinks for libs from
 /usr/lib to /lib.  They use a different machanism:

I haven't updated in a while, but my Debian unstable box has ..

$ find /usr/lib/*.so -type l -ls | grep  /lib | wc -l
24

.. symlinks back to /lib. 

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


ACPI errors on my desktop PC (floppy not found)

2003-09-04 Thread Martin

Hi,

I have more problems to report with the ACPI support and will submit a
PR, if you want. I don't know when this got broken.

Here some pieces of my dmesg:

---

FreeBSD 5.1-CURRENT #0: Thu Sep  4 22:38:56 CEST 2003
[...]
acpi0: ABIT   AWRDACPI on motherboard
pcibios: BIOS version 2.10
Using $PIR table, 8 entries at 0xc00fdef0
acpi0: power button is handled as a fixed feature programming model.
Timecounter ACPI-safe frequency 3579545 Hz quality 1000
ACPI-1287: *** Error: Method execution failed
[\\_SB_.PCI0.ISA_.FDC0._CRS] (Node 0xc29ca6e0),
AE_AML_UNINITIALIZED_LOCAL
ACPI-0175: *** Error: Method execution failed
[\\_SB_.PCI0.ISA_.FDC0._CRS] (Node 0xc29ca6e0),
AE_AML_UNINITIALIZED_LOCAL
can't fetch resources for \\_SB_.PCI0.ISA_.FDC0 -
AE_AML_UNINITIALIZED_LOCAL
[...]
fdc0: cannot reserve I/O port range (1 ports)
orm0: Option ROMs at iomem 0xd1000-0xd27ff,0xc-0xcefff on isa0
fdc0: cannot reserve I/O port range (6 ports)

---

As you can see I recompiled today to confirm that the problem
still exists. This is only about floppy. Everything else is ok.

Martin


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


Re: DISCUSSION: /dev/fd%d.%d and /dev/{a}cd%d[ac] to be discontinued ?

2003-09-04 Thread Poul-Henning Kamp
In message [EMAIL PROTECTED], Andrew Gallatin 
writes:

Can you give a hint as to what you mean by the significant buf/VM
system changes?  Are you talking about removing the vnode detour for
drivers and giving drivers who want it access to the struct file?

Well, there really isn't more than that at this point, we plan to talk
about it at BSDcon03 and try to settle on our strategy for the entire
area, and if we manage that we'll communicate it of course.

-- 
Poul-Henning Kamp   | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer   | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Text file busy

2003-09-04 Thread Wesley Morgan
On Thu, 4 Sep 2003, Scott M. Likens wrote:

 On Thu, 2003-09-04 at 07:44, Paul Richards wrote:
  Overwriting a file that's currently executing results in a Text file
  busy error.
 
  When did this start happening?
 
  This was something that was fixed way back on FreeBSD but it seems to be
  a problem again.
 
  Paul.

 this feature has always existed in FreeBSD for as long as I remember.

 Of course there are ways to bypass this feature but it's there for
 your protection.  You shouldn't be upgrading a program that's in
 resident memory.  That's like trying to reinstall X while running in X.
 You're just asking for problems.

 turnoff postfix, install the new version and be happy.

 Every single 'flavor' of Unix/Unices has always had this feature.  I've
 seen it on HP-UX box's on Solaris Servers, Linux, NetBSD, OpenBSD,
 FreeBSD.  Maybe you wern't paying attention but, that is one of those
 things I think should fall under duh, i shouldn't do that it might make
 things crash hard.

It's also unfortunate that this protection does not seem to extend to
libaries. I've had some in-use X libraries get overwritten with some very
colorful results.

-- 
Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


IBM ServerRaid 5i

2003-09-04 Thread Richard Puga
Sorry to bother you,

 I am trying to find out who mantains the ips RAID driver for FreeBSD.
I have a X225 Series IBM box here with that card in it, I would be
willing/wanting to try and get it
to work before they end up sending me the older 4 series controller and
would like to work with the person who wrote the driver for FreeBSD.

I was told There is an ips driver which claims to support IBM ServeRAID
cards.  The
driver refers to the cards by their codenames, Morpheus and Copperhead.
I
would suggest contacting [EMAIL PROTECTED] and asking there.

Thanks for any help in advance

Richard Puga
[EMAIL PROTECTED]



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


Re: ACPI errors on my desktop PC (floppy not found)

2003-09-04 Thread David O'Brien
On Thu, Sep 04, 2003 at 11:30:49PM +0200, Martin wrote:
 I have more problems to report with the ACPI support and will submit a
 PR, if you want. I don't know when this got broken.
...
 As you can see I recompiled today to confirm that the problem
 still exists. This is only about floppy. Everything else is ok.

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


Re: ACPI errors on my desktop PC (floppy not found)

2003-09-04 Thread Martin
Am Do, 2003-09-04 um 23.56 schrieb David O'Brien:
 Athlon-based?

No.

CPU: Pentium III/Pentium III Xeon/Celeron (501.14-MHz 686-class CPU)
  Origin = GenuineIntel  Id = 0x673  Stepping = 3
Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE

It's an old Abit mainboard, but everything always worked here.

Martin


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


Re: Question about genassym, locore.s and 0-sized arrays (showstopper for an icc compiled kernel)

2003-09-04 Thread Alexander Leidinger
On Thu, 4 Sep 2003 11:28:58 -0500
Dan Nelson [EMAIL PROTECTED] wrote:

 If you're talking FreeBSD 5, you should be able to simply subsitute a
 C99 flexible array member (basically replace [0] with []) and get
 the same effect.  0-length arrays are a gcc extension:
 
 http://gcc.gnu.org/onlinedocs/gcc/Zero-Length.html
 
 Under FreeBSD 4.x, you can't use them because gcc 2.95 only supports
 the gcc extension.  Intel has added support for a lot of gcc extensions
 recently; they may be willing to add this to the list.

Please read my mail again, icc already supports my_array[0], but the
resulting array in the binary has size '1'. The actual showstopper is
the output of genassym.sh. To me it seems it's just a genassym.sh issue,
but I don't really know what's going on in the kernel, so I ask here.

Bye,
Alexander.

-- 
  Weird enough for government work.

http://www.Leidinger.net   Alexander @ Leidinger.net
  GPG fingerprint = C518 BC70 E67F 143F BE91  3365 79E2 9C60 B006 3FE7
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: /lib/foo.so.X - /usr/lib/foo.so

2003-09-04 Thread Mark Kettenis
   Date: Thu, 4 Sep 2003 14:10:50 -0700
   From: David O'Brien [EMAIL PROTECTED]

   On Thu, Sep 04, 2003 at 11:27:15PM +0300, Ruslan Ermilov wrote:
On Thu, Sep 04, 2003 at 09:58:39PM +0300, Ruslan Ermilov wrote:
[...]
 The patch is not a problem (attached).  I've been looking at
 how our friends do this.  NetBSD has symlinks in /usr/lib to
 /lib, both to .so and .so.X, and their cc(1) and ld(1) don't
 look things in /lib.  Linux looks things up in both /lib and
 /usr/lib, and does not have symlinks from /usr/lib to /lib.
 
There is a sad typo above: Linux *does* have symlinks from
/usr/lib to /lib, so both use /usr/lib for linking.

   What version of Linux are you using?  SuSE Enterprise Linux 8, and Red
   Hat Enterprise Linux 3 both do not have symlinks for libs from /usr/lib
   to /lib.  They use a different machanism:


   suse# cat /usr/lib/libc.so
   /* GNU ld script
  Use the shared library, but some functions are only in
  the static library, so try that secondarily.  */
   GROUP ( /lib/libc.so.6 /usr/lib/libc_nonshared.a )

Speaking as a (former) glibc developer (a true convert nowadays):

Well, libc is a special case since there are a few functions that
aren't provided by the shared libc, but are always linked statically.
Linux does this to be compatible with the System V ABI.

The whole thing is actually pointless since most interfaces in libc.so
aren't compatible with the System V ABI, so it's nothing but a
historical fart nowadays.

Anyway, I think you'll see a symlink for /usr/lib/libm.so.  At least
my SuSE Linux 8.2 does have it.

Mark


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


Re: wi0: cardbus card activation failed

2003-09-04 Thread Kenneth D. Merry
On Thu, Sep 04, 2003 at 10:02:10 -0600, M. Warner Losh wrote:
 In message: [EMAIL PROTECTED]
 [EMAIL PROTECTED] writes:
 : Hello,
 : I have same problem as 
 http://lists.freebsd.org/pipermail/freebsd-current/2003-August/008948.html,
 :  but with other PCMCIA card - new Proxim Orinoco.
 : When I plug it in, I get:
 : 
 : cardbus0: network, ethernet at device 0.0 (no driver attached)
 : cbb0: CardBus card activation failed
 : 
 : I use kernel from yestereday, pccbb.c ver 1.95.
 
 You need a driver.  This message says that none attached.  Maybe
 FreeBSD doesn't support this chip yet?  Maybe it is supported by the
 atheros driver (ath).

I have the same problem with my fxp card, although it isn't because I don't
have a driver or I don't have the card attached.

If I pull it out and re-insert it, it probes.

When I boot:

cardbus0: Resource not specified in CIS: id=10, size=2000
cardbus0: network, ethernet at device 0.0 (no driver attached)
cbb0: CardBus card activation failed

After re-inserting it:

fxp0: Intel 82559ER Pro/100 Ethernet port 0x1000-0x103f mem 
0xf602-0xf603,0xf604-0xf6040fff irq 11 at device 0.0 on cardbus0
fxp0: Ethernet address 00:03:47:49:82:2b
miibus0: MII bus on fxp0
inphy0: i82555 10/100 media interface on miibus0
inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto

(This is -current from August 16th.)

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


Re: Question about genassym, locore.s and 0-sized arrays (showstopper for an icc compiled kernel)

2003-09-04 Thread Marcel Moolenaar
On Fri, Sep 05, 2003 at 12:14:11AM +0200, Alexander Leidinger wrote:
 On Thu, 4 Sep 2003 11:28:58 -0500
 Dan Nelson [EMAIL PROTECTED] wrote:
 
  If you're talking FreeBSD 5, you should be able to simply subsitute a
  C99 flexible array member (basically replace [0] with []) and get
  the same effect.  0-length arrays are a gcc extension:
  
  http://gcc.gnu.org/onlinedocs/gcc/Zero-Length.html
  
  Under FreeBSD 4.x, you can't use them because gcc 2.95 only supports
  the gcc extension.  Intel has added support for a lot of gcc extensions
  recently; they may be willing to add this to the list.
 
 Please read my mail again, icc already supports my_array[0], but the
 resulting array in the binary has size '1'. The actual showstopper is
 the output of genassym.sh. To me it seems it's just a genassym.sh issue,
 but I don't really know what's going on in the kernel, so I ask here.

We use the size of the symbol (ie the size of the object identified
by the symbol) to pass around values. This we do by creating arrays.
If we want to export a C constant 'FOOBAR' to assembly and the constant
is defined to be 6, then we create an array for the sign, of which the
size is 1 for negative numbers and 0 otherwise. In this case the array
will be named FOOBARsign and its size is 0. We also create 4 arrays (*w0,
*w1, *w2 and *w3), each with a maximum of 64K and corresponding to the
4 16-bit words that constitutes a single 64-bit entity.
In this case
0006 C FOOBARw0
 C FOOBARw1
 C FOOBARw2
 C FOOBARw3

If the compiler creates arrays of size 1 for arrays we define as a
zero-sized array, you get exactly what you've observed.

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


Re: 5.2-RELEASE TODO

2003-09-04 Thread David O'Brien
On Wed, Sep 03, 2003 at 08:27:17PM -0700, Peter Wemm wrote:
  Sorry, I missed this when I did my scrub yesterday.  I'll fix it now.
  Btw, does X work on it?  Can I compile/install it without hassle?
 
 Yes.  It installs Just Fine.  You wont even notice the difference relative
 to an i386 machine.  X builds/runs.  I dont think the Xserver port packages
 yet though, but it does build.  I think David is working on that.

It packages now. :-)  I've got a package to put on ftp-master if I can
find a good place for it.
 
-- 
-- David  ([EMAIL PROTECTED])
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Question about genassym, locore.s and 0-sized arrays (showstopper for an icc compiled kernel)

2003-09-04 Thread Dan Nelson
In the last episode (Sep 05), Alexander Leidinger said:
 On Thu, 4 Sep 2003 11:28:58 -0500
 Dan Nelson [EMAIL PROTECTED] wrote:
  If you're talking FreeBSD 5, you should be able to simply subsitute
  a C99 flexible array member (basically replace [0] with [])
  and get the same effect.  0-length arrays are a gcc extension:
  
  http://gcc.gnu.org/onlinedocs/gcc/Zero-Length.html
  
  Under FreeBSD 4.x, you can't use them because gcc 2.95 only
  supports the gcc extension.  Intel has added support for a lot of
  gcc extensions recently; they may be willing to add this to the
  list.
 
 Please read my mail again, icc already supports my_array[0], but the
 resulting array in the binary has size '1'. The actual showstopper is
 the output of genassym.sh. To me it seems it's just a genassym.sh
 issue, but I don't really know what's going on in the kernel, so I
 ask here.

Ok, I reread the original message, and it's still a zero-length array
problem, but in a different place.

What it looks like to me is that icc silently converts zero-length
arrays to 1 element when creating the assembly output.  While it's
processing C source, sizeof(my_array) returns 0, but the emitted
assembly says otherwise:

$ cat  test.c
int test0[0];
int test1[1];
int test2[2];
^D
$ gcc -c test.c -S -o test.gcc
$ icc -c test.c -S -o test.icc
$ grep comm test.?cc
test.gcc:   .comm   test0,0,4
test.gcc:   .comm   test1,4,4
test.gcc:   .comm   test2,8,4
test.icc:   .comm test2,8,4
test.icc:   .comm test1,4,4
test.icc:   .comm test0,4,4

So gcc emitted symbols with the same size as in the source file, with
an alignment of 4 bytes (since I'm using ints in this example), but icc
adjusted the test0 symbol to be one int long.  I used ints to make it
more obvious what icc is doing; the effect is the same if you use
chars.

I guess the correct question to be asking is does the ELF format allow
0-length symbols?  If not, then gcc is generating invalid objects, and
genassym will have to be rewritten to not use them (maybe add one to
the array size, and have genassym.sh subtract it).  If it does, then
genassym.c (sys/assym.h actually) is legal code.  If Intel doesn't want
to change icc, we can still work around it, but there may be other code
that will break on icc just like assym.h.

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


Re: ACPI errors on my desktop PC (floppy not found)

2003-09-04 Thread Pawel Worach
Martin wrote:

Hi,

I have more problems to report with the ACPI support and will submit a
PR, if you want. I don't know when this got broken.
Here some pieces of my dmesg:

---

FreeBSD 5.1-CURRENT #0: Thu Sep  4 22:38:56 CEST 2003
[...]
acpi0: ABIT   AWRDACPI on motherboard
 

Take a look at PR kern/48494, there is a patch for the AML there for
the ABIT BP6 board. I belive other ABIT boards have the similar
Store(Local0, Local0) problem. That fixed the floppy problem for me.
   - Pawel

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


Re: Question about genassym, locore.s and 0-sized arrays (showstopper for an icc compiled kernel)

2003-09-04 Thread Marcel Moolenaar
On Thu, Sep 04, 2003 at 05:51:23PM -0500, Dan Nelson wrote:
 
 I guess the correct question to be asking is does the ELF format allow
 0-length symbols?

Of course. What size do you think a label should have otherwise?

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


Re: HEADS UP! ATAng committed

2003-09-04 Thread Lars Eggert
Hi,

Lars Eggert wrote:

Soren Schmidt wrote:

ATAng has just been committed. You need to make world after this update
as atacontrol etc needs to pick up the changes.
Funky boot messages, but the system is usable after. This is with 
today's -current:

atapci0: Intel ICH2 UDMA100 controller port 0xffa0-0xffaf at device 
31.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
...
ad0: 78167MB Maxtor 4D080H4 [158816/16/63] at ata0-master UDMA100
ata1-slave: WARNING - ATA_IDENTIFY recovered from missing interrupt
acd0: CDRW PHILIPS DVD+RW-D28 at ata1-master UDMA33
ad3: WARNING - SETFEATURES recovered from missing interrupt
ad3: WARNING - SETFEATURES recovered from missing interrupt
ad3: WARNING - SET_MULTI recovered from missing interrupt
ad3: WARNING - SETFEATURES recovered from missing interrupt
ad3: 3584MB p p p p p p p p p p p p p p p p p p p p [585/112/112] at 
ata1-slave PIO0
ad3: WARNING - READ_MUL recovered from missing interrupt
ad3: WARNING - READ_MUL recovered from missing interrupt
ad3: WARNING - READ_MUL recovered from missing interrupt

Note that I have no ad3, only ad0 and acd0, which are masters on the 
primary and secondary channels as probed above.
with today's -current (as opposed to 8/27, which was running when I sent 
the previous email), the system panics on boot:

GEOM: create disk ad0 dp=0xc63b9e70
ad0: 78167MB Maxtor 4D080H4 [158816/16/63] at ata0-master UDMA100
acd0: CDRW PHILIPS DVD+RW-D28 at ata1-master UDMA33
ad3: WARNING - SETFEATURES recovered from missing interrupt
ad3: WARNING - SETFEATURES recovered from missing interrupt
ad3: WARNING - SETFEATURES recovered from missing interrupt
GEOM: create disk ad3 dp=0xc64d6170
Fatal trap 18: integer divide fault while in kernel mode
cpuid = 0; lapic.id = 
instruction pointer = 0x8:0xc03067d0
stack pointer   = 0x10:0xc070fc1c
frame pointer   = 0x10:0xc070fcac
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 = 0 (swapper)
kernel: type 18 trap, code=0
Stopped at  __qdivrem+0x3e: divl%ecx,%eax
db
Lars
--
Lars Eggert [EMAIL PROTECTED]   USC Information Sciences Institute


smime.p7s
Description: S/MIME Cryptographic Signature


Re: 5.1-RELEASE-p2 buildworld crash - help!!

2003-09-04 Thread Alexander Portnoy
On Thu, 4 Sep 2003 18:58:42 +0300
ODHIAMBO Washington [EMAIL PROTECTED] wrote:

 This is what Ruslan said of the problem. However, I must admit that
 I haven't done anything about it since I did not quite understand
 what it is he meant I should do ;)
 
 Quoting him verbatim:
 
 
  I've tracked it down to the same problem we were having ealier
  with the libpthread build.  You can either merge the following
  revisions manually, or wait for an official fix to pop up in
  RELENG_5_1:
  
  Makefile.inc1: 1.365, 1.367
  lib/libpthread/support/Makefile.inc: 1.2
 
 
 TIA
 
 
 -Wash
 
 -- 
 Odhiambo Washington   [EMAIL PROTECTED]  The box said 'Requires
 Wananchi Online Ltd.  www.wananchi.com  Windows 95, NT, or better,'
 Tel: +254 2 313985-9  +254 2 313922 so I installed FreeBSD.   
 GSM: +254 72 743223   +254 733 744121   This sig is McQ!  :-)
 
 Don't believe everything you hear or anything you say.
 


There are the patches:


diff -u /usr/src/Makefile.inc1.orig /usr/src/Makefile.inc1
#--
--- /usr/src/Makefile.inc1.orig Fri Sep  5 02:11:23 2003
+++ /usr/src/Makefile.inc1  Fri Sep  5 00:47:07 2003
@@ -791,6 +791,10 @@
 _generic_libs+=kerberos5/lib
 .endif
 
+.if !defined(NOLIBPTHREAD)
+_prebuild_libs+= lib/libc
+.endif
+
 _prebuild_libs+= lib/libcom_err lib/libcrypt lib/libexpat \
lib/libkvm lib/libmd \
lib/libncurses lib/libopie lib/libpam lib/libradius \
#--


diff -u  /usr/src/lib/libpthread/support/Makefile.inc.orig 
/usr/src/lib/libpthread/support/Makefile.inc
#--
--- /usr/src/lib/libpthread/support/Makefile.inc.orig   Fri Sep  5 02:13:29 2003
+++ /usr/src/lib/libpthread/support/Makefile.incFri Sep  5 00:48:10 2003
@@ -6,5 +6,5 @@
 SOBJS+= thr_libc.So
 
 thr_libc.So: thr_support.So
-   ${CC} -nostdlib -L/usr/lib -o ${.TARGET} -Wl,-x,-r ${.ALLSRC} -lc_pic
+   ${CC} -nostdlib -o ${.TARGET} -Wl,-x,-r ${.ALLSRC} -lc_pic
#--

They resolved the problem of buildworld 5.1-RELEASE-p2 on 4.8-RELEASE-p4.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


ips.ko load sequence for IBM ServerRaid 5i

2003-09-04 Thread Richard Puga
I do have the ips driver working with the IBM ServerRaid 5i. However it
only works if I boot
of an IDE drive and load the driver after the kernel is loaded.

What I believe the problem to be is the fact that this Raid card is
just an add in card to a
modified PCI slot  that makes the on board LSI dual channel controller
into a RAID, and
something in the kernel is loading (not the LSI driver its been taken
out) which makes these
2 separate devices act as one through the PCI bus and is the reason it
can only be loaded
after booting.

I believe a quick and dirty fix for this may be to load the ips.ko
module after the kernel has booted
and before init mounts /.

Is there a way to do this via something in /boot/loader (the standard
way in loader.conf loads it too soon)
or perhaps a way to compile isp into the kernel in a way that it would
be probed
at a later time or in a different sequence?

Thanks again in advance

Richard Puga
[EMAIL PROTECTED]


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


Re: Question about genassym, locore.s and 0-sized arrays (showstopper for an icc compiled kernel)

2003-09-04 Thread Marius Strobl
On Thu, Sep 04, 2003 at 03:47:09PM -0700, Marcel Moolenaar wrote:
 
 We use the size of the symbol (ie the size of the object identified
 by the symbol) to pass around values. This we do by creating arrays.
 If we want to export a C constant 'FOOBAR' to assembly and the constant
 is defined to be 6, then we create an array for the sign, of which the
 size is 1 for negative numbers and 0 otherwise. In this case the array
 will be named FOOBARsign and its size is 0. We also create 4 arrays (*w0,
 *w1, *w2 and *w3), each with a maximum of 64K and corresponding to the
 4 16-bit words that constitutes a single 64-bit entity.
 In this case
   0006 C FOOBARw0
    C FOOBARw1
    C FOOBARw2
    C FOOBARw3
 
 If the compiler creates arrays of size 1 for arrays we define as a
 zero-sized array, you get exactly what you've observed.
 

Is this rather complex approach really necessary? I have successfully
generated assyms.s' using genassym.sh(8) from NetBSD and both ICC and
GCC on i386 which have exactly the same values as one generated with
sys/kern/genassym.sh from FreeBSD. The genassym.sh(8) of NetBSD kind
of directly exports the C-constants so it just needs one symbol per
constant and doesn't require zero sized arrays. Given that it's from
NetBSD their approach also should be very MI.

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


Re: Question about genassym, locore.s and 0-sized arrays (showstopper for an icc compiled kernel)

2003-09-04 Thread Marcel Moolenaar
On Fri, Sep 05, 2003 at 02:59:22AM +0200, Marius Strobl wrote:
  
  We use the size of the symbol (ie the size of the object identified
  by the symbol) to pass around values. This we do by creating arrays.
  If we want to export a C constant 'FOOBAR' to assembly and the constant
  is defined to be 6, then we create an array for the sign, of which the
  size is 1 for negative numbers and 0 otherwise. In this case the array
  will be named FOOBARsign and its size is 0. We also create 4 arrays (*w0,
  *w1, *w2 and *w3), each with a maximum of 64K and corresponding to the
  4 16-bit words that constitutes a single 64-bit entity.
  In this case
  0006 C FOOBARw0
   C FOOBARw1
   C FOOBARw2
   C FOOBARw3
  
  If the compiler creates arrays of size 1 for arrays we define as a
  zero-sized array, you get exactly what you've observed.
 
 Is this rather complex approach really necessary?

In theory, yes. In practice, maybe not. If I remember correctly,
the problem we're trying to solve is twofold:
1.  64-bit constants given the limitations of the object format,
which included widths of 32-bit and a.out.
2.  Sign extension or datatype limitations in awk(1)? I'm not
sure about this point. Bruce?

 ... The genassym.sh(8) of NetBSD kind
 of directly exports the C-constants so it just needs one symbol per
 constant and doesn't require zero sized arrays. Given that it's from
 NetBSD their approach also should be very MI.

I wouldn't have a problem using NetBSD's genassym implementation,
provided we understand completely how it differs from ours and to
what extend and how it affects us and provided of course we can
live with whatever it is that's worse of just different from what
we have now.

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


Re: Question about genassym, locore.s and 0-sized arrays (showstopper for an icc compiled kernel)

2003-09-04 Thread Garrett Wollman
On Thu, 4 Sep 2003 18:19:02 -0700, Marcel Moolenaar [EMAIL PROTECTED] said:

 In theory, yes. In practice, maybe not. If I remember correctly,
 the problem we're trying to solve is twofold:

Actually, the problem we were trying to solve is simpler than that.

genassym needs to be able to compute the values of certain constants
from header files which are only accessible to kernel code.  At the
same time, it needs to be able to run as a user process.  One
compilation unit cannot include both Standard headers like stdio.h
and kernel-specific headers like sys/systm.h.  In fact, we muck with
the include path to ensure that Standard headers cannot be included
while compiling kernel source.

Cross-compilation does engender other issues, but that wasn't the
original motivation.

-GAWollman

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


Various problems after latest -CURRENT build. (USB, WI, KSE)

2003-09-04 Thread Mark Sergeant
Hi Guys,

I've noticed a bunch of problems with my latest current build...

1. With device wi in my kernel I was unable to compile at all, had to
take it out and then use a module to get it to work.
2. My USB mouse no longer works, Works fine on my 5.1-RELEASE machine
but nothing as of last nights kernel and world.
3. libkse seems to be causing hangs in various processes including
evolution, once I changed libmap to libc_r everything has run smoothly.

Cheers,
-- 
Mark Sergeant [EMAIL PROTECTED]
SNSOnline Technical Services
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Various problems after latest -CURRENT build. (USB, WI, KSE)

2003-09-04 Thread Daniel Eischen
On Fri, 5 Sep 2003, Mark Sergeant wrote:

 Hi Guys,
 
   I've noticed a bunch of problems with my latest current build...
 
 1. With device wi in my kernel I was unable to compile at all, had to
 take it out and then use a module to get it to work.
 2. My USB mouse no longer works, Works fine on my 5.1-RELEASE machine
 but nothing as of last nights kernel and world.
 3. libkse seems to be causing hangs in various processes including
 evolution, once I changed libmap to libc_r everything has run smoothly.

You can try this patch to src/lib/libpthread/support/Makefile.inc.
That should get libkse working again.  We don't know why this is
needed yet, but someone (kan?) is working on it.

-- 
Dan Eischen

Index: Makefile.inc
===
RCS file: /home/ncvs/src/lib/libpthread/support/Makefile.inc,v
retrieving revision 1.6
diff -u -r1.6 Makefile.inc
--- Makefile.inc2 Sep 2003 19:37:11 -   1.6
+++ Makefile.inc4 Sep 2003 13:42:03 -
@@ -33,5 +33,5 @@
 CLEANFILES+= ${SYSCALL_SRC} ${SYSCALL_OBJ} ${LIBC_OBJS}

 thr_libc.So: ${SYSCALL_OBJ} ${LIBC_OBJS}
-   ${CC} -fPIC -nostdlib -o ${.TARGET} -r ${.ALLSRC}
+   ${CC} -fPIC -nostdlib -o ${.TARGET} -r ${.ALLSRC} -lc_pic


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


Re: Various problems after latest -CURRENT build. (USB, WI, KSE)

2003-09-04 Thread David Xu
Daniel Eischen wrote:

On Fri, 5 Sep 2003, Mark Sergeant wrote:

 

Hi Guys,

	I've noticed a bunch of problems with my latest current build...

1. With device wi in my kernel I was unable to compile at all, had to
take it out and then use a module to get it to work.
2. My USB mouse no longer works, Works fine on my 5.1-RELEASE machine
but nothing as of last nights kernel and world.
3. libkse seems to be causing hangs in various processes including
evolution, once I changed libmap to libc_r everything has run smoothly.
   

You can try this patch to src/lib/libpthread/support/Makefile.inc.
That should get libkse working again.  We don't know why this is
needed yet, but someone (kan?) is working on it.
 

Last time, I tested the patch,  MySQL was still crashed.
Try revert to:
 src/lib/libpthread/Makefile revision 1.47
 src/lib/libpthread/support/Makefile.inc   revision 1.5
David Xu



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


Re: ACPI errors on my desktop PC (floppy not found)

2003-09-04 Thread Nate Lawson
It would help if you would tell me when you last had a working kernel.
The output of acpidump -t -d -o martin.dsdt  martin.asl would also help.

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


Re: Text file busy

2003-09-04 Thread Matthew D. Fuller
On Thu, Sep 04, 2003 at 09:36:31AM -0700 I heard the voice of
Mikko Ty?l?j?rvi, and lo! it spake thus:
 
 If you are into foot shooting, you can always overwrite a shared lib,
 such as libc.so, and watch (almost) all your programs crash and burn :-)

*raise hand*

Yup.  Got the t-shirt.

Nothing like watching your pinkie move in slow motion to depress the
Enter key, while your brain is screaming, NO, I meant *MV*, not cp!!!



-- 
Matthew Fuller (MF4839)   |  [EMAIL PROTECTED]
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/

The only reason I'm burning my candle at both ends, is because I
  haven't figured out how to light the middle yet
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Entropy harvesting: interrupts ethernet point_to_point

2003-09-04 Thread supraexpress
I have never had a problem with sysctl -a on any desktop system that I
have had (Dell, Gateway, custom).



On  4 Sep, Mark Murray wrote:
 Doug Barton writes:
 I've seen this problem on my compaq evo n610c as well, but didn't
 realize it was affecting other hardware as well. I tried to stir up
 interest in getting the acpi problem fixed, but wasn't successful.
 
 Hmmm :-(
 
 Mark, ok with you if I nuke the sysctl -a line in rc.d/initrandom? I
 hate to lose that source (no matter how small), but if the can't finish
 sysctl -a cancer is spreading...
 
 I'd really rather see sysctl fixed, rather than weakening Innocent
 Bystanders, but I'm not going to force this issue. So, reluctantly,
 yes, if you can't find a better place to hack a fix.
 
 M
 --
 Mark Murray
 iumop ap!sdn w,I idlaH
 ___
 [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]