Re: Busted -STABLE
There is a recent fix to the brooktree driver. -- Michel Talon To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Busted -STABLE
Where? There is a recent fix to the brooktree driver. -- Michel Talon To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Busted -STABLE
On Fri, Oct 27, 2000 at 01:18:37PM +0100, Bap wrote: Where? There is a recent fix to the brooktree driver. -- Michel Talon To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message I have seen that on the freebsd-stable list this morning, i think. -- Michel Talon To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Really odd BTX halted problem booting FreeBSD on VALinux hardware
Danny Braniss ([EMAIL PROTECTED]) wrote: In message [EMAIL PROTECTED]you write: }This is really weird. I have two valinux rackmount boxes, duel cpu's. } }I was testing the PXE stuff and booting one of the boxes regularly. }All of a sudden every time I reboot I get: } i've seen the same, i just reboot it, and it works. sometimes, while the kernel is doing it's init stuff it panics. i haven't seen it fail more than once in a row, so i was thinking maybe some network error that was not dealt properly. btw, the boxes are DELL. He was not seeing a PXE bug, it was a loader issue with the BIOS. The PXE bug you are seeing is with anything build 078 or earlier. Intel has a bug in their rom which they fixed back in March of this year. -- Paul Saab Technical Yahoo [EMAIL PROTECTED] - [EMAIL PROTECTED] - [EMAIL PROTECTED] Do You .. uhh .. Yahoo!? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Really odd BTX halted problem booting FreeBSD on VALinux hardware
On Fri, Oct 27, 2000 at 09:44:28AM -0500, Thomas T. Veldhouse wrote: I am also seeing BTX failures, but only from manual commands. The lsdev command will cause BTX to fail (and halt) when it scans my CDROM/DVD. I am using 4.1.1-RELEASE. I have a ABIT KA7-100 board (which uses the VIA686A chipset for IDE access). I recognize my exact problem. I have a Abit KT7 with a dvdrom, and lsdev crashes the loader. I had not related this to the DVD however. In any case FreeBSD is loded perfectly fine from the DVD as well as the hard disk. Only lsdev crashes the loader. By the way, i always have this annoying problem that the same machine is unable to format floppies under freebsd, while it formats them fine under Linux and Windows. I have been told that other have the same problem on various machines, while one guy with the same mobo said me he does not have it. Also i have seen comments in the CVS tree at ata.c about the ata driver stealing an ioport of the floppy drive. Does somebody know the present status of the question, and if it is valuable to upgrade (i run 4.1, it is at home so upgrades are painful)? -- Michel Talon To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
vm_page_remove() problem..
This keeps happening to one of our multiprocessor servers. About twice a day. panic: vm_page_remove(): page not found in hash mp_lock = 0101; cpuid = 1; lapic.id = 0100 boot() called on cpu#1 syncing disks... 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68 giving up on 67 buffers Uptime: 21h28m53s Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... cpu_reset called on cpu#1 cpu_reset: Stopping other CPUs cpu_reset: Restarting BSP cpu_reset_proxy: Grabbed mp lock for BSP cpu_reset_proxy: Stopped CPU 1 FreeBSD bsd10.nyct.net 4.1.1-STABLE FreeBSD 4.1.1-STABLE #0: Fri Oct 20 15:58:40 EDT 2000 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/NYCT i386 We've tweaked some variables in response to this (maxusers?) but it doesn't seem to do the trick. It happens most when I do something memory intensive (like stopping and restarting apache, and all several-hundred children), but it really does happen quite randomly. My wild uneducated guess is that both processors are calling vm_page_remove() on a page and the one that doesn't happen first ends up panic'ing because it can't find the page anymore. We're in the process of trying it with a non-SMP kernel, but I figure I'd put this out early in any case as it's obviously a bug of some kind. If I really find myself at the end of a rope, I'm going to look to see if it's a hardware problem. Thanks -- Michael Bacarella [EMAIL PROTECTED] ;finger address for public key GPG Key Fingerprint: B4E4 82F5 BCAC AB83 E6F7 B5AA 933E 2A75 79A4 A9C1 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: ipfw security.
[EMAIL PROTECTED] ("Stop here. Start everywhere.") writes:
I thought I would spread this to the mailing list just in case no one
knew about it, and ask whether ipfw does implement all of the mentioned
requirements:
ftp://ftp.isi.edu/in-notes/rfc2979.txt
Well, does ipfw support all of it, and if not, what doesn't it support?
RFC 2979 is informational, not a standards-track document, and it puts
very few specific requirements on an implementation. It's more of a
set of design principles for deployment of firewalls than it is a set
of requirements for firewall software. Like nearly every other piece
of packet filtering code (at least, those that are remotely
configurable) I've ever seen, ipfw is perfectly capable of being used
in accordance with 2979, and perfectly capable of being configured to
violate its every stricture. 2979 is (in my opinion) a good starting
point for network administrators to learn what *not* to do with a
packet filter, but that's about all.
- Lowell Gilbert
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
IPXrouted barfs after upgrade
Hi Just upgraded to recent stable from ~month old stable and: Oct 27 18:18:29 bsd IPXrouted[85]: socket: Protocol not supported Something wrong with IPX ? Nothing in UPDATING though... L. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: HEADS UP! MFC's
There are some things which are broken in -stable that need to be fixed (alpha booting, e.g.). We'll try to leave the world a better place for our efforts. -stable world builds, installs and boots on my pws433 as of earlier today (with dfr's ata fix). -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Really odd BTX halted problem booting FreeBSD on VALinux h
: I think you are specifying the wrong arguments to disklabel; I
: seem to rememebr a -w/-W distinction...
:
:Nope.
:
: In any case, I'm running with a disklabel inside a DOS partition
: on all but one box of mine, and always have been. I installed
: 4.1 on my laptop that way.
:
:Sysinstall can create a disklabel inside of a MBR slice fine. The
:problem is that the disklabel(8) _program_ itself doesn't know how
:to create a virgin disklabel for a MBR slice.
:
:--
:
:John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/
The patchset I put on the lists earlier today will allow disklabel
to install a virgin label on a slice. Did it not get out? As matters
currently stand, disklabel can only edit a preexisting label on a slice.
I'll post it again... included below (this time without the file
descriptor cruft that snuck into my previous posting of the patch). With
the patch you can do this:
# optional dd if you are paranoid
# dd if=/dev/zero of=/dev/da0 bs=32k count=4
fdisk -I da0
disklabel -w -r da0s1 auto
That's much preferable to having to use sysinstall if all you want to
do is initialize a label on a slice.
-Matt
Index: sbin/disklabel/disklabel.c
===
RCS file: /home/ncvs/src/sbin/disklabel/disklabel.c,v
retrieving revision 1.28.2.3
diff -u -r1.28.2.3 disklabel.c
--- sbin/disklabel/disklabel.c 2000/07/01 06:47:46 1.28.2.3
+++ sbin/disklabel/disklabel.c 2000/10/27 19:24:00
@@ -1347,10 +1347,17 @@
warn("cannot open %s", namebuf);
return (NULL);
}
- if (ioctl(f, DIOCGDINFO, lab) 0) {
- warn("ioctl DIOCGDINFO");
- close(f);
- return (NULL);
+
+ /*
+* Try to use the new get-virgin-label ioctl. If it fails,
+* fallback to the old get-disdk-info ioctl.
+*/
+ if (ioctl(f, DIOCGDVIRGIN, lab) 0) {
+ if (ioctl(f, DIOCGDINFO, lab) 0) {
+ warn("ioctl DIOCGDINFO");
+ close(f);
+ return (NULL);
+ }
}
close(f);
lab.d_boot0 = NULL;
Index: sys/kern/subr_diskslice.c
===
RCS file: /home/ncvs/src/sys/kern/subr_diskslice.c,v
retrieving revision 1.82
diff -u -r1.82 subr_diskslice.c
--- sys/kern/subr_diskslice.c 2000/01/28 11:51:08 1.82
+++ sys/kern/subr_diskslice.c 2000/10/27 19:23:28
@@ -366,12 +366,46 @@
int slice;
struct diskslice *sp;
struct diskslices *ssp;
+ struct partition *pp;
slice = dkslice(dev);
ssp = *sspp;
sp = ssp-dss_slices[slice];
lp = sp-ds_label;
switch (cmd) {
+
+ case DIOCGDVIRGIN:
+ lp = (struct disklabel *)data;
+ if (ssp-dss_slices[WHOLE_DISK_SLICE].ds_label) {
+ *lp = *ssp-dss_slices[WHOLE_DISK_SLICE].ds_label;
+ } else {
+ bzero(lp, sizeof(struct disklabel));
+ }
+
+ lp-d_magic = DISKMAGIC;
+ lp-d_magic2 = DISKMAGIC;
+ pp = lp-d_partitions[RAW_PART];
+ pp-p_offset = 0;
+ pp-p_size = sp-ds_size;
+
+ lp-d_npartitions = MAXPARTITIONS;
+ if (lp-d_interleave == 0)
+ lp-d_interleave = 1;
+ if (lp-d_rpm == 0)
+ lp-d_rpm = 3600;
+ if (lp-d_nsectors == 0)
+ lp-d_nsectors = 32;
+ if (lp-d_ntracks == 0)
+ lp-d_ntracks = 64;
+
+ lp-d_bbsize = BBSIZE;
+ lp-d_sbsize = SBSIZE;
+ lp-d_secpercyl = lp-d_nsectors * lp-d_ntracks;
+ lp-d_ncylinders = sp-ds_size / lp-d_secpercyl;
+ lp-d_secperunit = sp-ds_size;
+ lp-d_checksum = 0;
+ lp-d_checksum = dkcksum(lp);
+ return (0);
case DIOCGDINFO:
if (lp == NULL)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Re: HEADS UP! MFC's
On Fri, 27 Oct 2000, Mike Smith wrote: There are some things which are broken in -stable that need to be fixed (alpha booting, e.g.). We'll try to leave the world a better place for our efforts. -stable world builds, installs and boots on my pws433 as of earlier today (with dfr's ata fix). Yes- same here. But what I want to do as the gating item for 4.2 is to make sure that the boot floppies work for all the models that we claim to support. Eh? -matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: HEADS UP! MFC's
He only needed a 3 word answer. Merged From Current. Chris Faulhaber wrote: [ trimming -developers ] On Fri, Oct 27, 2000 at 03:39:30PM -0700, [EMAIL PROTECTED] wrote: What's an MFC? In Windoze it's Microsoft Foundation Class. I gather that is not what it is here. What is MFC? http://www.FreeBSD.org/FAQ/misc.html#AEN4829 and -stable/-developers is not the forum for this question; please try [EMAIL PROTECTED] next time. -- Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Really odd BTX halted problem booting FreeBSD on VALinux h
On 28-Oct-00 Matt Dillon wrote: : I think you are specifying the wrong arguments to disklabel; I : seem to rememebr a -w/-W distinction... : :Nope. : : In any case, I'm running with a disklabel inside a DOS partition : on all but one box of mine, and always have been. I installed : 4.1 on my laptop that way. : :Sysinstall can create a disklabel inside of a MBR slice fine. The :problem is that the disklabel(8) _program_ itself doesn't know how :to create a virgin disklabel for a MBR slice. : :-- : :John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ The patchset I put on the lists earlier today will allow disklabel to install a virgin label on a slice. Did it not get out? As matters currently stand, disklabel can only edit a preexisting label on a slice. If your patch works it looks great to me. I was just referring to our currently checked in code in disklabel(8). :) I'll post it again... included below (this time without the file descriptor cruft that snuck into my previous posting of the patch). With the patch you can do this: I did wonder about the file descriptor patch the first go-round... :) # optional dd if you are paranoid # dd if=/dev/zero of=/dev/da0 bs=32k count=4 fdisk -I da0 disklabel -w -r da0s1 auto That's much preferable to having to use sysinstall if all you want to do is initialize a label on a slice. Yes, this is definitely the desired behavior. -- 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-stable" in the body of the message
Re: HEADS UP! MFC's
Yes, but it looks like the thought police are also on my heals. =-) On 27 Oct, blaine wrote: He only needed a 3 word answer. Merged From Current. Chris Faulhaber wrote: ... On Fri, Oct 27, 2000 at 03:39:30PM -0700, [EMAIL PROTECTED] wrote: ... What is MFC? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Really odd BTX halted problem booting FreeBSD on VALinux h
: # optional dd if you are paranoid : # dd if=/dev/zero of=/dev/da0 bs=32k count=4 : fdisk -I da0 : disklabel -w -r da0s1 auto : : That's much preferable to having to use sysinstall if all you want to : do is initialize a label on a slice. : :Yes, this is definitely the desired behavior. : :-- : :John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ John, can you explain how the MBR bootstraps a slice? Should I make disklabel zero-out the fdisk partition table area in the slice rather then installing the dummy fdisk partition table? That is, for the case where -B is used on a slice (da0s1) verses on the whole-disk (da0)? -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Really odd BTX halted problem booting FreeBSD on VALinux h
On 28-Oct-00 Matt Dillon wrote: : # optional dd if you are paranoid : # dd if=/dev/zero of=/dev/da0 bs=32k count=4 : fdisk -I da0 : disklabel -w -r da0s1 auto : : That's much preferable to having to use sysinstall if all you want to : do is initialize a label on a slice. : :Yes, this is definitely the desired behavior. : :-- : :John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ John, can you explain how the MBR bootstraps a slice? Should I make disklabel zero-out the fdisk partition table area in the slice rather then installing the dummy fdisk partition table? That is, for the case where -B is used on a slice (da0s1) verses on the whole-disk (da0)? Just ignore the slice table within a slice. It is only used when boot1 is splatted over top of the MBR for the dangerously dedicated mode. It is unused and ignored otherwise. -Matt -- 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-stable" in the body of the message
Re: HEADS UP! MFC's
-On [20001027 19:05], Alfred Perlstein ([EMAIL PROTECTED]) wrote: * Jeroen Ruigrok van der Werven [EMAIL PROTECTED] [001027 09:53] wrote: You totally miss the point I was trying to communicate across. While I strive to make sure everything I MFC is tested it can always happen that something for some reason blows up. Some things are just beyond your control. That's understandable, and if things are proceeding as normal then there's no reason for potentially creating panic for the users. No I understand, but given that STABLE should be guarded more than CURRENT when it comes to noticing our userbase of potential ``dangerous' source update times I think the mail I sent out was justified and not trying to cause panic. I see which point of view you are coming from though. However, if there's an 'MFC rush' then I think that's not the right way to go about doing it. With rush I am referring back to 4.1-RELEASE of 4.0-RELEASE MFC's. That wasn't pretty in the least. As well as the last few weeks/months of immediate MFC's. I am just giving people a warning to be careful the next few days in updating their system as I am sure the MFC rushing of some things might occur again. Again, if you are _sure_ that there will be problems then please don't, if you aren't _sure_ then there's no reason to make people fear the next release. I am sure that I am testing things before committing, as well as reading the logs to see what everything is about. I am not even considering major impact changes for MFC. I think the STABLE crowd knows my MFC's by know. -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED]VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl Reality is an illusion, grimmer. The dreamlands are like masks within masks, and Time has no dominion beyond the Shroud... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
PPP Nat Bandwidth Sharing
Hi. I was wondering if this is even possible or I am looking for too much. I use a 56K dialup connection. I am using PPP Nat to share with a LAN. Bandwidth sharing doesn't seem to be too efficient. For example if Machine-1 on the LAN is doing a major download of a compressed file and getting near full speed of 5.6K/sec, if Machine-2 starts web browsing or a download itself..they can barely pull 1K/sec. It would seem to me that it should start throttling the bandwidth back so both machines are getting about 2.8K/sec each evenly. Is this possible? I thought maybe using DUMMNET and the Weight command would work as the example shows on this page - http://www.iet.unipi.it/~luigi/ip_dummynet But it didn't make much difference. Is there a way to efficiently share bandwidth or am I just looking for too much out of this? I am using FreeBSD 4.1.1-STABLE To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
PCI Modems Not Shown As Supported Hardware
I just got done chatting with Warner Losh about PCI modems. He is "pretty sure" that his PCI modem driver made its way into -stable and 4.1.1-R. The supported hardware docs and release notes do not list PCI modems as supported. (Unless I am blind in which case I will toddle along quietly, bumping into things as I go.) If someone can confirm this information then it should be in the proper docs. I will submit a PR to amend the appropriate docs. Thank you, Jason C. Wells To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
sysinstall fails to access cdrom
Hej all, after rebuilding world and kernel /stand/sysinstall fails to access my CDROM device with the following console messages: ata0-slave: too many segments in DMA table acd0: READ_BIG - ILLEGAL REQUEST asc=21 ascq=00 error=02 If I mount the device manually everything works. The old install (4.0-STABLE, 25. May 2000) did not show this problem. The devices are recognized in the dmesg-output as: atapci0: Intel PIIX4 ATA33 controller port 0x2020-0x202f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ad0: 6194MB TOSHIBA MK6411MAT [13424/15/63] at ata0-master using UDMA33 acd0: CDROM TOSHIBA CD-ROM XM-1902B at ata0-slave using WDMA2 Has anybody else this problem? TIA Ralf To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: sysinstall fails to access cdrom
Ralf Meyer wrote: Hej all, after rebuilding world and kernel /stand/sysinstall fails to access my CDROM device with the following console messages: ata0-slave: too many segments in DMA table acd0: READ_BIG - ILLEGAL REQUEST asc=21 ascq=00 error=02 If I mount the device manually everything works. The old install (4.0-STABLE, 25. May 2000) did not show this problem. The devices are recognized in the dmesg-output as: atapci0: Intel PIIX4 ATA33 controller port 0x2020-0x202f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ad0: 6194MB TOSHIBA MK6411MAT [13424/15/63] at ata0-master using UDMA33 acd0: CDROM TOSHIBA CD-ROM XM-1902B at ata0-slave using WDMA2 Has anybody else this problem? Did you cd /usr/src/release/sysinstall and make all and make install it? It isn't built when you did the world and your kernel. Kent TIA Ralf To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
