No Subject
subscribe freebsd-current To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
XFree86 4.0.2
How should I install XFree86 4.0.2 on a system running a -current snapshot from January 20? I tried downloading the binaries from xfree86.org, but Xinstall.sh complained that my extract file was bad (it wasn't), and when I ran 'sh Xinstall.sh -check' it told me that "binaries are not available for this version" of FreeBSD, namely 5.x, despite the fact that I downloaded the binaries from a directory labeled "FreeBSD 5.x". So I tried the ports, and it built fine for a long time, and then after about 35300 lines of output to the screen, ran into make: don't know how to make ../../../fonts/encodings/encodings.dir. Stop *** Error code 2 Stop in /usr/ports/x11/XFree86-4/work/xc/fonts/bdf. This system is a fresh install, except for a custom kernel and some rc.conf changes. Any suggestions other than waiting until cardbus support _finally_ gets in to -stable so I can stop trying to run -current? Thanks, -David To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: excessive paranoia in syslogd(8)?
On Sat, Jan 20, 2001 at 11:39:37PM -0600, Steve Price wrote: > On Sat, Jan 20, 2001 at 09:20:39PM -0800, Crist J. Clark wrote: > # > # You can write to the /dev/log (usually symlinked to /var/run/log) > # socket with '-s' set. > # > # If you want to or need to use network sockets, > # > # # syslogd -a localhost > # > # Should provide the behavior you want. As you noted this is not the > # same as '-s'. It is a feature and not a bug. > > I'm still deciding on that... Here's what I see: > > steve@test1(~)$ telnet localhost 514 > Trying 127.0.0.1... > Connected to localhost. > Escape character is '^]'. > Connection closed by foreign host. > steve@test1(/tmp/tard)$ > > steve@bonsai(~)$ telnet 192.168.21.28 514 > Trying 192.168.21.28... > Connected to 192.168.21.28. > Escape character is '^]'. > Connection closed by foreign host. > > And here is what I see in syslogd: > > test1# syslogd -d -a localhost > ... > logmsg: pri 45, flags 0, from test1, msg Jan 20 23:34:52 rshd[53675]: > connection from 127.0.0.1 on illegal port 1186 > Logging to CONSOLE /dev/console > Logging to FILE /var/log/messages > Logging to USERS > logmsg: pri 45, flags 0, from test1, msg Jan 20 23:34:54 rshd[53676]: > connection from 192.168.21.1 on illegal port 2855 > Logging to CONSOLE /dev/console > Logging to FILE /var/log/messages > Logging to USERS It looks like syslogd(8) is working fine from this. Is something with syslogd(8) not working? 'tail /var/log/messages' aren't those messages there? -- Crist J. Clark [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
loader / loader.old install behaviour suggestion
Hi, After /boot/loader is moved to /boot/loader.old, the install of the new /boot/loader can fail for whatever reason, leaving a computer that cannot automatically bootup, since someone has to type in /boot/loader.old at the boot prompt. I suggest that if the boot process can't find /boot/loader it tries /boot/loader.old before failing, or if the install process fails to install the new /boot/loader that the move of /boot/loader to /boot/loader.old is undone. Just my 2 cents, since i was just hit by this problem. Thanks Kelvin Farmer To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
sys/time.h w/ timespec stuff
Hey all, I've lately been trying to dig into why OpenPackages make(1) currently doesn't compile on FreeBSD but does on OpenBSD. There is a (very slight) difference between their sys/time.h headers. The timespec* stuff is hidden behind the _KERNEL aura on FreeBSD, but not on OpenBSD. This is manifested in OpenBSD's make source, which uses timespec for a few things. So now, maybe someone can answer my question: why is timespec _KERNEL? -- wca PGP signature
Re: excessive paranoia in syslogd(8)?
Steve Price <[EMAIL PROTECTED]> writes: > Aha! I must have read that manpage a dozen times and I didn't catch > on, but if I do this it works like I would expect even with '-s'. ...and even with -ss, which you might as well use unless you intend to log *to* remote hosts, or are sufficiently paranoid to want to log attempts *from* remote hosts to log *to* your box. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: excessive paranoia in syslogd(8)?
On Sun, Jan 21, 2001 at 06:29:02AM +0100, Dag-Erling Smorgrav wrote:
# Steve Price <[EMAIL PROTECTED]> writes:
# > Is it just me or does 'syslogd -s' exhibit just a little bit too
# > much paranoia about allowing socket connections? I was futzing
# > with a Perl script that needed to syslog(3) some stuff and after
# > much hair pulling I realized that 'syslogd -s' didn't even allow
# > connections from localhost.
#
# RTFM ('perldoc Sys::Syslog' in this case, pay special attention to
# setlogsock())
Aha! I must have read that manpage a dozen times and I didn't catch
on, but if I do this it works like I would expect even with '-s'.
#!/usr/bin/perl -w
use Sys::Syslog qw(:DEFAULT setlogsock);
setlogsock('unix');
openlog('foo', 'cons,ndelay,pid', 'local0');
syslog('emerg', 'emerg message');
closelog();
Thanks! :)
-steve
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: excessive paranoia in syslogd(8)?
On Sat, Jan 20, 2001 at 09:20:39PM -0800, Crist J. Clark wrote: # # You can write to the /dev/log (usually symlinked to /var/run/log) # socket with '-s' set. # # If you want to or need to use network sockets, # # # syslogd -a localhost # # Should provide the behavior you want. As you noted this is not the # same as '-s'. It is a feature and not a bug. I'm still deciding on that... Here's what I see: steve@test1(~)$ telnet localhost 514 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. Connection closed by foreign host. steve@test1(/tmp/tard)$ steve@bonsai(~)$ telnet 192.168.21.28 514 Trying 192.168.21.28... Connected to 192.168.21.28. Escape character is '^]'. Connection closed by foreign host. And here is what I see in syslogd: test1# syslogd -d -a localhost ... logmsg: pri 45, flags 0, from test1, msg Jan 20 23:34:52 rshd[53675]: connection from 127.0.0.1 on illegal port 1186 Logging to CONSOLE /dev/console Logging to FILE /var/log/messages Logging to USERS logmsg: pri 45, flags 0, from test1, msg Jan 20 23:34:54 rshd[53676]: connection from 192.168.21.1 on illegal port 2855 Logging to CONSOLE /dev/console Logging to FILE /var/log/messages Logging to USERS ??? -steve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: excessive paranoia in syslogd(8)?
Steve Price <[EMAIL PROTECTED]> writes:
> Is it just me or does 'syslogd -s' exhibit just a little bit too
> much paranoia about allowing socket connections? I was futzing
> with a Perl script that needed to syslog(3) some stuff and after
> much hair pulling I realized that 'syslogd -s' didn't even allow
> connections from localhost.
RTFM ('perldoc Sys::Syslog' in this case, pay special attention to
setlogsock())
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: excessive paranoia in syslogd(8)?
On Sat, Jan 20, 2001 at 10:49:44PM -0600, Steve Price wrote: > Is it just me or does 'syslogd -s' exhibit just a little bit too > much paranoia about allowing socket connections? I was futzing > with a Perl script that needed to syslog(3) some stuff and after > much hair pulling I realized that 'syslogd -s' didn't even allow > connections from localhost. Apparently Perl opens a socket > connection to syslog and with the '-s' syslogd doesn't read from > socket connections either from localhost or from hosts specified > with -a. This is a bad thing IMHO. Either I open syslogd up to > all socket connections (including from localhost) or I can't use > syslog from Perl. You can write to the /dev/log (usually symlinked to /var/run/log) socket with '-s' set. If you want to or need to use network sockets, # syslogd -a localhost Should provide the behavior you want. As you noted this is not the same as '-s'. It is a feature and not a bug. -- Crist J. Clark [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
excessive paranoia in syslogd(8)?
Is it just me or does 'syslogd -s' exhibit just a little bit too much paranoia about allowing socket connections? I was futzing with a Perl script that needed to syslog(3) some stuff and after much hair pulling I realized that 'syslogd -s' didn't even allow connections from localhost. Apparently Perl opens a socket connection to syslog and with the '-s' syslogd doesn't read from socket connections either from localhost or from hosts specified with -a. This is a bad thing IMHO. Either I open syslogd up to all socket connections (including from localhost) or I can't use syslog from Perl. -steve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bin/24444: syslogd(8) does not update hostname
"Crist J. Clark" <[EMAIL PROTECTED]> writes: > How about just logging a sethostname(3) call? Still doesn't help. There are (at least) two different ways of setting the hostname, one being a syscall and the other being a sysctl. One could of course have the kernel print a message to the console about it, syslogd(8) would pick that up. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current hangs...
I'll confirm a hang on both alpha && i386 (both SCSI, qlogic && ahc resp). The i386 was SMP. The Qlogic wasn't. Both were hung with phk's make -j 256 foolery. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current hangs...
On Sat, 20 Jan 2001, John Baldwin wrote: > > On 20-Jan-01 The Hermit Hacker wrote: > > On Sat, 20 Jan 2001, Mark Murray wrote: > > > >> > > >> > on a 2xPII/350, 256M, two scsi disks on ahc, and ccd I have three times > >> > now hung the machine so that only reset got any attention simply by > >> >make -j 128 world > >> > >> Do you have an easy way to narrow it down to CCD by doing the same > >> thing but without ccd involvement? > > > > I don't have CCD, and got home last night from the office and mine was > > hung also, on a kernel from the day before ... being in X, pretty much > > nothing I could do to try and debug it ... new laptop gets in this week, > > so will be setting up the whole serial console debugging env ... > > Is it SMP, and does it have multiple SCSI disks hanging off of the same device? yes and yes ... ahc1: port 0xcc00-0xccff mem 0xef10-0xef100fff irq 17 at device 13.0 on pci0 da0 at ahc1 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled da0: 6208MB (12715920 512 byte sectors: 255H 63S/T 791C) da1 at ahc1 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled da1: 8727MB (17873040 512 byte sectors: 255H 63S/T 1112C) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bin/24444: syslogd(8) does not update hostname
On Fri, Jan 19, 2001 at 11:09:24PM +0100, Dag-Erling Smorgrav wrote:
> "Crist J. Clark" <[EMAIL PROTECTED]> writes:
> > On Fri, Jan 19, 2001 at 12:32:53PM +0100, Dag-Erling Smorgrav wrote:
> > > It should also log a message if the hostname changes.
> > Should that be a responsibility of syslogd(8) or hostname(1)?
>
> I meant syslogd(8), but putting it in hostname(1) might makes sense,
> except that hostname(1) is not the only way to set the hostname
> ('sysctl -w kern.hostname=foo' is another)
How about just logging a sethostname(3) call?
But anyway, syslogd(8) does not track the state of any other system
parameters, I think asking syslogd(8) to notice a change in the
hostname on its own in a real-time fashion is beyond its scope.
That said, I agree that syslogd(8) making a note when its own idea of
the hostname changes would be useful. If one is analyzing logs, an
entry indicating that messages from a given machine no longer will be
labeled as coming from 'foo' but 'foobar' would be very helpful.
Patches, patches, patches:
--- usr.sbin/syslogd/syslogd.c 2001/01/18 08:06:34 1.1
+++ usr.sbin/syslogd/syslogd.c 2001/01/21 00:55:53 1.3
@@ -318,7 +318,7 @@
struct sockaddr_un sunx, fromunix;
struct sockaddr_storage frominet;
FILE *fp;
- char *p, *hname, line[MAXLINE + 1];
+ char *hname, line[MAXLINE + 1];
struct timeval tv, *tvp;
struct sigaction sact;
sigset_t mask;
@@ -395,12 +395,6 @@
consfile.f_type = F_CONSOLE;
(void)strcpy(consfile.f_un.f_fname, ctty + sizeof _PATH_DEV - 1);
- (void)gethostname(LocalHostName, sizeof(LocalHostName));
- if ((p = strchr(LocalHostName, '.')) != NULL) {
- *p++ = '\0';
- LocalDomain = p;
- } else
- LocalDomain = "";
(void)strcpy(bootfile, getbootfile());
(void)signal(SIGTERM, die);
(void)signal(SIGINT, Debug ? die : SIG_IGN);
@@ -1340,10 +1334,23 @@
char cline[LINE_MAX];
char prog[NAME_MAX+1];
char host[MAXHOSTNAMELEN+1];
+ char oldLocalHostName[MAXHOSTNAMELEN+1];
+ char hostMsg[2*(MAXHOSTNAMELEN+1)+40];
dprintf("init\n");
/*
+* Load hostname (may have changed)
+*/
+ strncpy(oldLocalHostName, LocalHostName, sizeof(LocalHostName));
+ (void)gethostname(LocalHostName, sizeof(LocalHostName));
+ if ((p = strchr(LocalHostName, '.')) != NULL) {
+ *p++ = '\0';
+ LocalDomain = p;
+ } else
+ LocalDomain = "";
+
+ /*
* Close all open log files.
*/
Initialized = 0;
@@ -1492,6 +1499,17 @@
logmsg(LOG_SYSLOG|LOG_INFO, "syslogd: restart", LocalHostName, ADDDATE);
dprintf("syslogd: restarted\n");
+ /*
+* Log a change in hostname, but only on a restart
+*/
+ if ((signo != 0) &&
+ (strncmp(oldLocalHostName, LocalHostName, sizeof(LocalHostName)) != 0)) {
+ snprintf(hostMsg, sizeof(hostMsg),
+"syslogd: hostname changed, \"%s\" to \"%s\"",
+oldLocalHostName, LocalHostName);
+ logmsg(LOG_SYSLOG|LOG_INFO, hostMsg, LocalHostName, ADDDATE);
+ dprintf("%s\n", hostMsg);
+ }
}
/*
--
Crist J. Clark [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: current hangs...
On 20-Jan-01 Poul-Henning Kamp wrote: > In message <[EMAIL PROTECTED]>, John Baldwin writes: >> >>On 20-Jan-01 The Hermit Hacker wrote: >>> On Sat, 20 Jan 2001, Mark Murray wrote: >>> > > on a 2xPII/350, 256M, two scsi disks on ahc, and ccd I have three times > now hung the machine so that only reset got any attention simply by >make -j 128 world Do you have an easy way to narrow it down to CCD by doing the same thing but without ccd involvement? >>> >>> I don't have CCD, and got home last night from the office and mine was >>> hung also, on a kernel from the day before ... being in X, pretty much >>> nothing I could do to try and debug it ... new laptop gets in this week, >>> so will be setting up the whole serial console debugging env ... >> >>Is it SMP, and does it have multiple SCSI disks hanging off of the same >>device? > > SMP, one scsi disk on each controller, /usr and /home ccd'ed. Is there any code dealing with disk I/O in the kernel that does the equivalent of this: while (!io_done) /* spin */ ; That assumes an interrupt will set io_done? Using DELAY() in places might explain this. If the kernel is spining, then it is probably holding Giant, which prevents Ctrl-Alt-Esc (keyboard ithread blocks on Giant) not to mention we aren't doing a task switch to it anyways. Also, NMI's would be blocked by trap() being broken. I have a patch for trap() btw that tells it to not bother with Giant for NMI's. I haven't tested it yet though. -- John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current hangs...
In message <[EMAIL PROTECTED]>, John Baldwin writes: > >On 20-Jan-01 The Hermit Hacker wrote: >> On Sat, 20 Jan 2001, Mark Murray wrote: >> >>> > >>> > on a 2xPII/350, 256M, two scsi disks on ahc, and ccd I have three times >>> > now hung the machine so that only reset got any attention simply by >>> >make -j 128 world >>> >>> Do you have an easy way to narrow it down to CCD by doing the same >>> thing but without ccd involvement? >> >> I don't have CCD, and got home last night from the office and mine was >> hung also, on a kernel from the day before ... being in X, pretty much >> nothing I could do to try and debug it ... new laptop gets in this week, >> so will be setting up the whole serial console debugging env ... > >Is it SMP, and does it have multiple SCSI disks hanging off of the same device? SMP, one scsi disk on each controller, /usr and /home ccd'ed. dmesg: Booting [/boot/kernel/kernel]... stray irq 7 Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Fri Jan 19 23:21:40 CET 2001 [EMAIL PROTECTED]:/usr/src/sys/compile/SMP Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Pentium II Xeon/Celeron (333.06-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x651 Stepping = 1 Features=0x183fbff real memory = 268435456 (262144K bytes) avail memory = 258048000 (252000K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 Preloaded elf kernel "kernel" at 0xc031b000. Pentium Pro MTRR support enabled Using $PIR table, 9 entries at 0xc00fdf20 npx0: on motherboard npx0: INT 16 interface pcib0: at pcibus 0 on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 isab0: at device 2.0 on pci0 isa0: on isab0 atapci0: at device 2.1 on pci0 atapci0: Busmastering DMA not supported pci0: at 2.2 (no driver attached) Timecounter "PIIX" frequency 3579545 Hz pci0: at 2.3 (no driver attached) fxp0: port 0xfcc0-0xfcdf mem 0xfed0-0xfedf,0xfecdf000-0xfecd irq 19 at device 3.0 on pci0 fxp0: Ethernet address 00:a0:c9:82:bb:30 ahc0: port 0xf800-0xf8ff mem 0xfecff000-0xfecf irq 17 at device 9.0 on pci0 aic7895: Wide Channel A, SCSI Id=7, 32/255 SCBs ahc1: port 0xf400-0xf4ff mem 0xfecfe000-0xfecfefff irq 17 at device 9.1 on pci0 aic7895: Wide Channel B, SCSI Id=7, 32/255 SCBs pci0: at 13.0 (no driver attached) atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppi0: on ppbus0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x100> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A, console sio1: configured irq 3 not in bitmap of probed irqs 0 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via IOAPIC #0 intpin 2 Waiting 2 seconds for SCSI devices to settle Mounting root from ufs:/dev/da0s1a da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) da1 at ahc1 bus 0 target 0 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled da1: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) WARNING: / was not properly dismounted SMP: AP CPU #1 Launched! ccd0-3: Concatenated disk drivers swapon: adding /dev/da1s1b as swap device swapon: adding /dev/da0s1b as swap device Automatic boot in progress... -- 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. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pcm status
On 20-Jan-01 Donald J . Maddox wrote: > This is directly traceable to entropy harvesting by /dev/*random. > I know it's not an option if you need to use ssh, but not loading > random.ko will fix the sound problems when moving the mouse or > typing. It doesn't fix the 'hwptr went backwards' messages, though. The entropy stuff only kicks in on the keyboard and mouse. It can't really help the hwptr backwards stuff, as that is due to the additional overhead in the current interrupt path as well as asynchronous handling of interrupts. -- John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current hangs...
On 20-Jan-01 The Hermit Hacker wrote: > On Sat, 20 Jan 2001, Mark Murray wrote: > >> > >> > on a 2xPII/350, 256M, two scsi disks on ahc, and ccd I have three times >> > now hung the machine so that only reset got any attention simply by >> >make -j 128 world >> >> Do you have an easy way to narrow it down to CCD by doing the same >> thing but without ccd involvement? > > I don't have CCD, and got home last night from the office and mine was > hung also, on a kernel from the day before ... being in X, pretty much > nothing I could do to try and debug it ... new laptop gets in this week, > so will be setting up the whole serial console debugging env ... Is it SMP, and does it have multiple SCSI disks hanging off of the same device? -- John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current hangs...
On Sat, 20 Jan 2001, Mark Murray wrote: > > > > on a 2xPII/350, 256M, two scsi disks on ahc, and ccd I have three times > > now hung the machine so that only reset got any attention simply by > > make -j 128 world > > Do you have an easy way to narrow it down to CCD by doing the same > thing but without ccd involvement? I don't have CCD, and got home last night from the office and mine was hung also, on a kernel from the day before ... being in X, pretty much nothing I could do to try and debug it ... new laptop gets in this week, so will be setting up the whole serial console debugging env ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current hangs...
I have a recent -current that hangs in 'make -j36 world'. I am now running a UP kernel of the same date: # uname -a FreeBSD celebris 5.0-CURRENT FreeBSD 5.0-CURRENT #0: \ Mon Jan 15 18:42:30 PST 2001 \ root@celebris:/usr/src/sys/compile/CELEBRIS i386 dmesg attached. tomdean dmesg from a UP kernel === 96 blocks, 0.3% fragmentation) IP Filter: already initialized de0: enabling BNC port Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Mon Jan 15 18:42:30 PST 2001 root@celebris:/usr/src/sys/compile/CELEBRIS Timecounter "i8254" frequency 1193029 Hz Timecounter "TSC" frequency 131996485 Hz CPU: Pentium/P54C (132.00-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping = 5 Features=0x3bf real memory = 100663296 (98304K bytes) avail memory = 94597120 (92380K bytes) Preloaded elf kernel "kernel" at 0xc0334000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc033409c. Intel Pentium detected, installing workaround for F00F bug npx0: on motherboard npx0: INT 16 interface pcib0: at pcibus 0 on motherboard pci0: on pcib0 ncr0: port 0xec00-0xecff mem 0xfedfbf00-0xfedfbfff irq 11 at device 1.0 on pci0 isab0: at device 2.0 on pci0 isa0: on isab0 pci0: at 6.0 (no driver attached) sis0: port 0xe800-0xe8ff mem 0xfedfa000-0xfedfafff irq 10 at device 7.0 on pci0 sis0: Ethernet address: 00:a0:cc:74:63:b4 miibus0: on sis0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto de0: port 0xe480-0xe4ff mem 0xfedfbe80-0xfedfbeff irq 15 at device 8.0 on pci0 de0: DEC DE450-CA 21041 [10Mb/s] pass 1.1 de0: address 00:00:f8:02:76:db atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode lpt0: on ppbus0 lpt0: Interrupt-driven port sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: can't assign resources unknown: can't assign resources unknown: <16550 compatible COM device> can't assign resources unknown: <16550 compatible COM device> can't assign resources unknown: can't assign resources unknown: can't assign resources IP Filter: v3.4.13 initialized. Default = pass all, Logging = enabled Waiting 10 seconds for SCSI devices to settle Mounting root from ufs:/dev/da1s1a da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 8) da0: 1042MB (2134305 512 byte sectors: 255H 63S/T 132C) cd0 at ncr0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 4.237MB/s transfers (4.237MHz, offset 8) cd0: cd present [326227 x 2048 byte records] da2 at ncr0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled da2: 3090MB (6328861 512 byte sectors: 255H 63S/T 393C) da1 at ncr0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled da1: 8748MB (17916240 512 byte sectors: 255H 63S/T 1115C) IP Filter: already initialized de0: enabling BNC port stray irq 7 stray irq 7 stray irq 7 stray irq 7 got 5 stray irq 7's: not logging anymore pid 27080 (communicator-4.7), uid 1001: exited on signal 10 (core dumped) microuptime() went backwards (272675.344496 -> 272675.-694570216) microuptime() went backwards (287740.708251 -> 287740.-694206432) pid 61804 (m6811-elf-gdb), uid 1001: exited on signal 11 (core dumped) pid 61824 (m6811-elf-gdb), uid 1001: exited on signal 11 (core dumped) pid 61834 (m6811-elf-gdb), uid 1001: exited on signal 11 (core dumped) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pcm status
OK, please try this, then; change the HARVEST_RING_SIZE in sys/dev/random/yarrow.h to a smaller power-of-2 (256 or 128 would be good), and let me know how that helps-or-not. Thanks! M > If it helps at all, it's marginal. I still get skips. > > On Sat, Jan 20, 2001 at 05:36:08PM +0200, Mark Murray wrote: > > > This is directly traceable to entropy harvesting by /dev/*random. > > > I know it's not an option if you need to use ssh, but not loading > > > random.ko will fix the sound problems when moving the mouse or > > > typing. It doesn't fix the 'hwptr went backwards' messages, though. > > > > Please tell me if > > > > sysctl -w kern.random.yarrow.bins=2 > > makes a difference for you. > > > > Thanks! > > > > M > > -- > > Mark Murray > > Warning: this .sig is umop ap!sdn > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-current" in the body of the message > -- Mark Murray Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pcm status
If it helps at all, it's marginal. I still get skips. On Sat, Jan 20, 2001 at 05:36:08PM +0200, Mark Murray wrote: > > This is directly traceable to entropy harvesting by /dev/*random. > > I know it's not an option if you need to use ssh, but not loading > > random.ko will fix the sound problems when moving the mouse or > > typing. It doesn't fix the 'hwptr went backwards' messages, though. > > Please tell me if > > sysctl -w kern.random.yarrow.bins=2 > makes a difference for you. > > Thanks! > > M > -- > Mark Murray > Warning: this .sig is umop ap!sdn > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pcm status
> This is directly traceable to entropy harvesting by /dev/*random. > I know it's not an option if you need to use ssh, but not loading > random.ko will fix the sound problems when moving the mouse or > typing. It doesn't fix the 'hwptr went backwards' messages, though. Please tell me if sysctl -w kern.random.yarrow.bins=2 makes a difference for you. Thanks! M -- Mark Murray Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current hangs...
Mark Murray <[EMAIL PROTECTED]> types: > > on a 2xPII/350, 256M, two scsi disks on ahc, and ccd I have three times > > now hung the machine so that only reset got any attention simply by > > make -j 128 world > > Do you have an easy way to narrow it down to CCD by doing the same > thing but without ccd involvement? I don't think it's ccd. I get similar hangs with "make -j 20 buildworld" on a 2xPII-Xeon/450, 256M, two scsi disks on ahc without ccd. I think more likely it's related to the problems that sos is currently having/investigating.
Re: current hangs...
In message <[EMAIL PROTECTED]>, Mark Murray writes: >> >> on a 2xPII/350, 256M, two scsi disks on ahc, and ccd I have three times >> now hung the machine so that only reset got any attention simply by >> make -j 128 world > >Do you have an easy way to narrow it down to CCD by doing the same >thing but without ccd involvement? No, /usr is on ccd on this one :-( -- 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. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pcm status
This is directly traceable to entropy harvesting by /dev/*random. I know it's not an option if you need to use ssh, but not loading random.ko will fix the sound problems when moving the mouse or typing. It doesn't fix the 'hwptr went backwards' messages, though. On Fri, Jan 19, 2001 at 11:42:32PM -0700, Warner Losh wrote: > In message <[EMAIL PROTECTED]> Sean Kelly writes: > : I did not have this behavior in -STABLE, but now I do since I upgraded > : to -CURRENT. > > -current's interrupt latency is horrible these days, which seems to > manifest itself in problem with the sound driver. I have a -current > laptop and get all kinds of artifacts on it. I have a laptop that is > running -stable and has 1/3 the power of the -current laptop and plays > w/o a hitch. > > Warner > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sysinstall move and make release on FreeBSD-stable
>What are you talking about? pkg_add -r pkgname, that's all it takes. *hides head in shame* OK so I'm a sucker for the graphical interface =) DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sysinstall move and make release on FreeBSD-stable
"Rogier R. Mulhuijzen" wrote: > > >3) Most of what FreeBSD installs is not required for day-to-day for most > >users. Since many users use sysinstall to some extent as a system > >managing tool, sysinstall is actually quite more oftenly used than many. > > It's currently the best way to install packages IMHO. With the automatic > dependancy resolving and downloading from FTP. The latter pkg_add offers, > but it's a bother having to find the URLs. What are you talking about? pkg_add -r pkgname, that's all it takes. -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] "There is no spoon." -- Kiki To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sysinstall move and make release on FreeBSD-stable
>3) Most of what FreeBSD installs is not required for day-to-day for most >users. Since many users use sysinstall to some extent as a system >managing tool, sysinstall is actually quite more oftenly used than many. It's currently the best way to install packages IMHO. With the automatic dependancy resolving and downloading from FTP. The latter pkg_add offers, but it's a bother having to find the URLs. DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current hangs...
> > on a 2xPII/350, 256M, two scsi disks on ahc, and ccd I have three times > now hung the machine so that only reset got any attention simply by > make -j 128 world Do you have an easy way to narrow it down to CCD by doing the same thing but without ccd involvement? M -- Mark Murray Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sysinstall move and make release on FreeBSD-stable
Maxim Sobolev wrote: > > Slightly OT, but could we have a flag to disable building sysinstall during make > world? It's hardly a tool that is required for day-to-day operation, so in most > cases it will only waste considerable amount of root partitition. 1) Now sysinstall is /usr/sbin, and it is hardly all that big anyway. 2) It wouldn't waste any more space anyway, since it would be *replacing* what is already installed. 3) Most of what FreeBSD installs is not required for day-to-day for most users. Since many users use sysinstall to some extent as a system managing tool, sysinstall is actually quite more oftenly used than many. -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] "There is no spoon." -- Kiki To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: syslogd(8) does not update hostname
> On Sat, Jan 20, 2001 at 11:24:16AM +0200, Mark Murray wrote: > > I don't agree with this change. > > > > hostname != name-that-IP-address-resolves-to. > > Dunno what you are talking about. That has nothing directly to do with > this. No one is talking about forcing you to change your hostname. The > patch just allows syslogd(8) to take note if the hostname were to > change. D'uh. Bad crack I'm on. :-) M -- Mark Murray Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: syslogd(8) does not update hostname
On Sat, Jan 20, 2001 at 11:24:16AM +0200, Mark Murray wrote: > I don't agree with this change. > > hostname != name-that-IP-address-resolves-to. Dunno what you are talking about. That has nothing directly to do with this. No one is talking about forcing you to change your hostname. The patch just allows syslogd(8) to take note if the hostname were to change. -- Crist J. Clark [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
current hangs...
on a 2xPII/350, 256M, two scsi disks on ahc, and ccd I have three times now hung the machine so that only reset got any attention simply by make -j 128 world -- 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. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: syslogd(8) does not update hostname
I don't agree with this change.
hostname != name-that-IP-address-resolves-to.
I can see how loggin the IP address (or some manifestation thereof) to
a central logger, but this is too strong.
Example: My laptop has a hostname set for my home network, and I connect
it to my work network and DHCP an IP address there. I would be HOPPING
mad if that caused my hostname and VPN to break.
M
> >Submitter-Id: current-users
> >Originator: Crist J. Clark
> >Organization:
> >Confidential: no
> >Synopsis: syslogd(8) does not update hostname
> >Severity: non-critical
> >Priority: medium
> >Category: bin
> >Release:FreeBSD 5.0-CURRENT i386
> >Class: sw-bug
> >Environment:
>
> All standard FreeBSD distributions. The code discussed is from
> 5.0-CURRENT, but should trivially merge back to -STABLE.
>
> >Description:
>
> Many tools and progams within FreeBSD date back to a time when
> it was expected that a machines IP and hostname seldom, if ever,
> changed. Even when a IP and hostname were received at boot, it rarely
> changed until shutdown. With many users using protocols like DHCP
> where IP and hostname change with time, many tools do not deal well
> with this behavior.
>
> One of these tools is syslogd(8). syslogd(8) is typically
> started at boot time and runs until shutdown. However, syslogd(8)
> loads the hostname at startup and syslogd(8)'s idea of the hostname
> can never change while it is running.
>
> One might expect that a SIGHUP would cause syslogd(8) to load
> the new hostname since a SIGHUP can cause syslogd(8) to re-read its
> configuration file and re-open the log files, but it does not.
>
> The fact that the hostname does not change can cause confusion
> in the log files. It could be especially troublesome when a machine is
> logging to a central loghost. At any given time, the names in the log
> files may not have any correspondence to the names the hosts currently
> have. There are even issues on a host that gets its IP and hostname
> via DHCP at boot and the name never changes. syslogd(8) is started
> before any network services are initialized in /etc/rc.
>
> I propose that syslogd(8) should reload the hostname with a
> SIGHUP. I cannot think of any reason that one should not update the
> hostname, but as I pointed out, there are reasons why one would want
> that behavior.
>
> >How-To-Repeat:
>
> # hostname -s
> bubbles
> # hostname bubbles-test.domain.org
> # kill -HUP `cat /var/run/syslog.pid`
> # logger -p user.notice "hostname test"
> # tail -4 /var/log/messages
> Jan 17 21:45:00 bubbles /boot/kernel/kernel: acd0: CDROM at
>ata0-slave using BIOSPIO
> Jan 17 21:45:00 bubbles /boot/kernel/kernel: Mounting root from ufs:/dev/ad0s1a
> Jan 18 00:41:14 bubbles su: cjc to root on /dev/ttyp0
> Jan 18 00:58:34 bubbles cjc: hostname test
>
> >Fix:
>
> I do not see any reason we cannot move the code that gets the
> hostname from the main() function into init(). init() is called when
> to "reload" settings. The hostname is never used in main() before
> init() is called. The patch is against -CURRENT and my box has not
> exploded yet.
>
> Here is what the above test looks like with the change in
> place.
>
> # hostname -s
> bubbles
> # hostname bubbles-test.cjclark.org
> # kill -HUP `cat /var/run/syslog.pid `
> # logger -p user.notice "syslogd hostname test"
> # hostname bubbles.cjclark.org
> # kill -HUP `cat /var/run/syslog.pid `
> # logger -p user.notice "syslogd hostname test"
> # tail -4 /var/log/messages
> Jan 18 13:36:58 bubbles su: BAD SU cjc to root on /dev/ttyp0
> Jan 18 13:37:03 bubbles su: cjc to root on /dev/ttyp0
> Jan 18 13:38:40 bubbles-test cjc: syslogd hostname test
> Jan 18 13:39:11 bubbles cjc: syslogd hostname test
>
>
> --- syslogd.c 2001/01/18 08:06:34
> +++ syslogd.c 2001/01/18 08:09:23
> @@ -395,12 +395,6 @@
>
> consfile.f_type = F_CONSOLE;
> (void)strcpy(consfile.f_un.f_fname, ctty + sizeof _PATH_DEV - 1);
> - (void)gethostname(LocalHostName, sizeof(LocalHostName));
> - if ((p = strchr(LocalHostName, '.')) != NULL) {
> - *p++ = '\0';
> - LocalDomain = p;
> - } else
> - LocalDomain = "";
> (void)strcpy(bootfile, getbootfile());
> (void)signal(SIGTERM, die);
> (void)signal(SIGINT, Debug ? die : SIG_IGN);
> @@ -1342,6 +1336,16 @@
> char host[MAXHOSTNAMELEN+1];
>
> dprintf("init\n");
> +
> + /*
> +* Load hostname (may have changed)
> +*/
> + (void)gethostname(LocalHostName, sizeof(LocalHostName));
> + if ((p = strchr(LocalHostName, '.')) != NULL) {
> + *p++ = '\0';
> + LocalDomain = p;
> + } else
> + LocalDomain = "";
>
>
