Why does printf(9) hang network?

Why would doing a printf(9) in a device driver (usb, firewire, probably others) cause an obscenely long lockout on /usr/src/sys/kern/uipc_sockbuf.c:148 (sx:so_rcv_sx) ? Printf(9) alone isn't the problem, adding printfs to chown(2) does not cause the problem, but printfs from device drivers do. G

Re: Why does printf(9) hang network?

Robert writes: Why would doing a printf(9) in a device driver (usb, firewire, probably others) cause an obscenely long lockout on /usr/src/sys/kern/uipc_sockbuf.c:148 (sx:so_rcv_sx) ? Printf(9) alone isn't the problem, adding printfs to chown(2) does not cause the problem, but printfs from

witness Re: Why does printf(9) hang network?

I received a suggestion to try witness, so I build a kernel with WITNESS, WITNESS_KDB, KDB, DDB, KDB_TRACE, and DDB_NUMSYM. This is my first attempt to use witness, so if I got something wrong let me know. Didn't quite make it all the way up to a multiuser prompt: Starting syslogd. Starting rpcb

Re: memstick.img is bloated with 7% 2K blocks of nulls

Tim Kientzle wrote: > The current UFS code is designed to leave enough "slack space" to > support future file writes. What if you turned the knob all the way down and had just one cylinder group? I assume that newfs would need to be fixed to allow this, but would anything break? The current limi

quotas an essential feature? (was: svn commit: r218953 - stable/8/usr.sbin/sysinstall)

I promise to enable UFS quotas in GENERIC in one week unless anybody objects now. Huh? I thought GENERIC was supposed to include everything you needed to boot, not every possible feature that someone might desire? But requests to include things required to boot get rejected and nonessential

Re: Keeping /etc/localtime up-to-date

> And while I (think I) recall that the equivalent of /etc/localtime > was implemented in some version of SunOS many years ago as a symlink, > I believe that approach could be problematic for FreeBSD, as it > could impose some unintended requirements on some of the start-up > scripts. I have been

Re: New Boot-Loader

Please note that graphical loaders are not very serial console friendly ;-) Yes! Real computers have RS-232 consoles. And please stick with plain ASCII text. The current bootloader is at best ugly and at worst unusable on some terminals. AFAIK the bootloader doesn't have termcap/terminfo ava

multi-boot bootstrap?

The discussion of a new bootloader reminded me of the following problem: What we need more than a new bootloader is a new bootstrap. With MBR, NetBSD's boot selector MBR works reasonably well. (About as well as can be expected given the limited space available.) You get a menu of partitions ("slic

Re: Keeping /etc/localtime up-to-date

And while I (think I) recall that the equivalent of /etc/localtime was implemented in some version of SunOS many years ago as a symlink, I believe that approach could be problematic for FreeBSD, as it could impose some unintended requirements on some of the start-up scripts. I have been runni

Re: multi-boot bootstrap?

Now, how are you going to multiboot OpenBSD and NetBSD on a PowerPC machine from the same hard disk. I didn't say anything about a requirement for booting multiple OSes from the same disk. I said: Go through all the disks and look for bootable partitions. Extract the GPT partition labels f

Re: ifconfig output: ipv4 netmask format

Paul Schenkeveld writes: Although non-contiguous netmasks are not legal anymore in IPv4, our ifconfig still allows to do something like: # ifconfig em0 inet 10.0.5.2 netmask 255.0.255.0 # ifconfig em0 em0: flags=8843 metric 0 mtu 1500 options=219b ether xx:xx:xx:xx:xx

*printf(9) and PRINTF_BUFR_SIZE

While working on other problems with *printf(9), log(9), etc. I stumbled upon: options PRINTF_BUFR_SIZE=128# Prevent printf output being interspersed. Question 1: Am I correct in thinking that PRINTF_BUFR_SIZE is supposed to prevent this: ada2: 300.000MB/s transfuhub2: 3 ports with 3

Re: *printf(9) and PRINTF_BUFR_SIZE

While working on other problems with *printf(9), log(9), etc. I stumbled upon: options PRINTF_BUFR_SIZE=128 # Prevent printf output being interspersed. Question 1: Am I correct in thinking that PRINTF_BUFR_SIZE is supposed to prevent this: ada2: 300.000MB/s transfuhub2: 3 ports with 3 r

Need an alternative to DELAY()

FreeBSD 8.2 amd64 uniprocessor kernel: siisch1: DISCONNECT requested kernel: siisch1: SIIS reset... kernel: siisch1: siis_sata_connect() calling DELAY(1000) last message repeated 59 times kernel: siisch1: SATA connect time=60ms status=0123 kernel: siisch1: SIIS reset done: devices=0001 k

Re: Need an alternative to DELAY()

FreeBSD 8.2 amd64 uniprocessor kernel: siisch1: DISCONNECT requested kernel: siisch1: SIIS reset... kernel: siisch1: siis_sata_connect() calling DELAY(1000) last message repeated 59 times kernel: siisch1: SATA connect time=60ms status=0123 kernel: siisch1: SIIS reset done: devices=0001

(no subject)

[ Email attempt #3 and counting... ] Alexander Motin wrote: Warner Losh wrote: I don't suppose that your driver could cause the hardware to interrupt after a little time? That would be more resource friendly... Otherwise, 1ms is long enough that a msleep or tsleep would likely work quite ni

Re: Add SUM sysctl

> once you reboot into SUM to install world, you are doomed, BECAUSE > ... > Kernel will bitch (GELI part), about world->kernel mismatch and you > won't be able to install world as you cant decrypt geom providers!! Suggestion 1: Install the new stuff into different disk partition(s), leaving the