Re: vm code
On Sat, 12 Jun 1999, Jonathan Towne wrote: > just wondering about this, because after the new vm code was committed, and i > had done a "make world," i found something that didn't work as it did before, > i'm not totally sure if it's due to the new vm code or not, but, my only > amusement (Quake 1) doesn't run anymore.. The appropriate (or, rather what i > think appropriate information), is included below: > > $ ./quake.x11 -nosound > Added packfile ./id1/pak0.pak (339 files) > Added packfile ./id1/pak1.pak (85 files) > Added packfile ./id1/pak2.pak (81 files) > Added packfile ./id1/pak3.pak (57 files) > snip, seeing as how there is a long list of crap here- > Quake Initialized= > Linux Quake -- Version 1.200 > another snip > now, it starts the game, adding all the models and whatnot > > PackFile: ./id1/pak0.pak : progs/zombie.mdl > PackFile: ./id1/pak0.pak : progs/h_zombie.mdl > [02] > VERSION 1.09 SERVER (39537 CRC) > > [1d][1e][1e][1e][1e][1e][1e][1e][1e][1e][1e][1e][1e][1e][1e][1e][1e][1e][1e][1e][1e][1e][1e][1e][1e][1e][1e][1e][1e][1e][1e][1e][1e][1e][1e][1e][1f] > > [02]Introduction > Error: Stack is missaligned Can you send me a disassembly of that part of the code? If I knew exactly why the stack was considered misaligned, then I could help. > VID_Shutdown > $ > ^-- drops me back to a prompt... thats as far as i get, even when i don't use > my second and third "pakfiles" which are just the teamfortress and headhunters > modifications, respectively. > > my system happens to be a p166, with 32meg of RAM, running a -CURRENT > version, not exactly up-to-date with the kernel, only because i've done a few > more "make installworld's" than i have installed kernels > > FreeBSD woodhull.sciny.net 4.0-CURRENT FreeBSD 4.0-CURRENT #1: > Wed May 26 18:30:27 EST 1999 > jon...@woodhull.sciny.net:/usr/src/sys/compile/WOODHULL i386 > > Hope somebody can help me with this problem.. i haven't found anything > else that has done anything like that, but, I also would rather not ;) > > > -- > Jonathan Towne wrong...@slic.com > Systems Administrator > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: RE: net.inet.tcp.always_keepalive on as default ?
On 8 Jun 1999, Joel Ray Holveck wrote: > >> This wouldn't help the poor sod whose connection gets shot down every > >> eight days while he's not there and doesn't know what hit him. > > If the poor sod hasn't touched his xterm for 8 days, he's either dead > > or he doesn't care if it goes away. > > Again, Matt, with all due respect, please do not post your operational > habits as universals. Somebody who keeps a session to a server around > so they can see syslog messages if there's a problem may have an idle > connection for weeks. If he sees syslog messages, that's not idle. > > In case you still doubt the existance of such a person, I give you a > counterexample. Having just spoken with nemo, I am quite certain that > he is alive and well, and from my dealings with him have no doubt he > would become somewhat miffed if I were to kill off several of his > sessions. > > Cheers, > joelh > > detlev$ finger n...@[deleted] > [[deleted]] > Login: nemo Name: Joel N. Weber II > Directory: /gb/nemo Shell: /usr/local/bin/bash > On since Thu Jun 03 23:49 (EDT) on tty12 days 3 hours idle > On since Wed May 19 14:43 (EDT) on tty227 minutes 34 seconds idle > On since Sun May 30 22:24 (EDT) on tty32 days 1 hour idle > On since Sun May 30 22:27 (EDT) on tty42 days 3 hours idle > On since Mon May 31 00:15 (EDT) on tty52 days 1 hour idle > On since Mon May 31 16:07 (EDT) on tty62 hours 40 minutes idle > On since Fri Jun 04 20:58 (EDT) on tty73 days 1 hour idle > On since Fri Jun 04 22:28 (EDT) on tty13 2 days 3 hours idle > On since Sat Jun 05 17:05 (EDT) on tty14 2 days 1 hour idle > On since Sat Jun 05 15:25 (EDT) on tty15 2 days 2 hours idle > On since Sat Jun 05 21:59 (EDT) on tty16 2 days 3 hours idle > On since Sat Jun 05 22:11 (EDT) on tty17 3 days 2 hours idle > On since Sat Jun 05 00:26 (EDT) on tty18 2 days 12 hours idle > On since Sun Jun 06 19:15 (EDT) on tty19 2 days 1 hour idle > On since Wed May 19 15:57 (EDT) on ttyp0 from xanthine:0.0 >10 days 1 hour idle > On since Wed May 19 15:58 (EDT) on ttyp1 from xanthine:0.0 >10 days 1 hour idle > On since Wed May 19 16:11 (EDT) on ttyp2 from xanthine:0.0 >12 days 23 hours idle > On since Wed May 19 16:45 (EDT) on ttyp3 from xanthine:0.0 >15 days 21 hours idle > On since Wed May 19 17:29 (EDT) on ttyp4 from xanthine:0.0 >9 days 23 hours idle > On since Wed May 19 17:43 (EDT) on ttyp5 from xanthine:0.0 >10 days 2 hours idle > On since Wed May 19 17:44 (EDT) on ttyp6 from xanthine:0.0 >9 days 23 hours idle > On since Wed May 19 18:09 (EDT) on ttyp7 from xanthine:0.0 >15 days 21 hours idle > On since Thu May 20 20:20 (EDT) on ttyp8 from xanthine:0.0 >19 days idle > On since Wed May 19 18:35 (EDT) on ttyp9 from xanthine:0.0 >16 days 22 hours idle > On since Wed May 19 21:54 (EDT) on ttypa from xanthine:0.0 >20 days 2 hours idle > On since Thu May 20 16:06 (EDT) on ttypb from xanthine:0.0 >16 days 2 hours idle > On since Thu May 20 21:05 (EDT) on ttypc from xanthine:0.0 >9 days 10 hours idle > On since Thu May 20 23:51 (EDT) on ttypd from xanthine:0.0 >18 days 20 hours idle > Last login Mon Jun 07 19:22 (EDT) on ttypf from zygorthian-space > New mail received Wed Jun 09 00:29 1999 (EDT) > Unread since Wed Jun 09 00:00 1999 (EDT) > No Plan. > > -- > Joel Ray Holveck - jo...@gnu.org >Fourth law of programming: >Anything that can go wrong wi > sendmail: segmentation violation - core dumped > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: GNU patch gone stale
On Tue, 8 Jun 1999, Andrey A. Chernov wrote: > On Tue, Jun 08, 1999 at 03:20:19PM -0400, Brian Feldman wrote: > > Our GNU patch has gone stale in the tree. Anyone want to upgrade it to 2.5? > > If not, I'll do it myself eventually. Patch 2.1 which we have now is broken > > for > > certain diffs (recently tried with gimp 1.1.5-1.1.6 diffs), while 2.5 works > > fine. > > GNU patch 2.5 already in contrib/patch but there was strong opposition in > core team to make it default when I try to bring it in, please search for > related discussion in FreeBSD mailing lists. Time to reopen that can of worms. It is _not_ appropriate for FreeBSD to be using obsolete versions of anything, especially when found that the old versions are buggy. > > -- > Andrey A. Chernov > http://nagual.pp.ru/~ache/ > MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
GNU patch gone stale
Our GNU patch has gone stale in the tree. Anyone want to upgrade it to 2.5? If not, I'll do it myself eventually. Patch 2.1 which we have now is broken for certain diffs (recently tried with gimp 1.1.5-1.1.6 diffs), while 2.5 works fine. Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Mmap problem in -current?
On 6 Jun 1999, Joel Ray Holveck wrote: > >> I just noticed (kernel&world from friday) that locate always cores > >> dump: > >> $ locate xxx > >> Segmentation fault (core dumped) > >> The problem disappears if I recompile locate without the -DMMAP > >> option. > > Running on the very latest current, it does not work for me. > > By 'it', do you mean that locate does not work, that the failure test > does not work (ie, locate is fine for you), or that the workaround > does not work? Sorry for being ambiguous. By 'it' I meant the test that you showed us. I cannot reproduce it. Have you tried remaking your locate database first? > > Thanks, > joelh > > -- > Joel Ray Holveck - jo...@gnu.org > Fourth law of programming: >Anything that can go wrong wi > sendmail: segmentation violation - core dumped > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Mmap problem in -current?
On Sun, 6 Jun 1999, Jean-Marc Zucconi wrote: > I just noticed (kernel&world from friday) that locate always cores > dump: > $ locate xxx > Segmentation fault (core dumped) > $ gdb -c locate.core /usr/bin/locate > Program terminated with signal 11, Segmentation fault. > (gdb) bt > #0 0x804964b in ___tolower () > #1 0x235000 in ?? () > #2 0x8049166 in ___tolower () > #3 0x8048f93 in ___tolower () > #4 0x80489f5 in ___tolower () > > The problem disappears if I recompile locate without the -DMMAP > option. > > Jean-Marc Running on the very latest current, it does not work for me. > > -- > Jean-Marc ZucconiPGP Key: finger j...@freebsd.org > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: RE: net.inet.tcp.always_keepalive on as default ?
On Sat, 5 Jun 1999, Garrett Wollman wrote: > < > said: > > > FWIW, I think only a fool would want a computer to NOT drop dead > > connections. > > Any "connection" that doesn't respond after 8 $^&! tries spaced FAR apart > > does > > NOT deserve to stay. > > If they are spaced too far apart, it is possible for perfectly > legitimate connections to get shot down as a result of external > periodicities. (Does somebody's router reset every day at 2:45? If > so, better hope no keepalives are scheduled for then!) But remember that the idea is the keepalive would keep trying for a certain amount of time, and this would be finely configureable. > > -GAWollman > > -- > Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the > same > woll...@lcs.mit.edu | O Siem / The fires of freedom > Opinions not those of| Dance in the burning flame > MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: RE: net.inet.tcp.always_keepalive on as default ?
FWIW, I think only a fool would want a computer to NOT drop dead connections. Any "connection" that doesn't respond after 8 $^&! tries spaced FAR apart does NOT deserve to stay. Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: No sound (Ensoniq Audio PCI 1370)
On Tue, 25 May 1999, oZZ!!! wrote: > > On Tue, 25 May 1999, W Gerald Hicks wrote: > > > [snips] > > > device pcm0 at nexus? > > . > > . > > . > > > # cd /dev > > > # rm audio dsp dspW mixer > > > # ./MAKEDEV snd0 > > > > > But play (from ports) can't work... > > > > That should be snd1 for the pcm driver > # cd /dev > # rm audio dsp dspW mixer > # ./MAKEDEV snd1 > # play notify.wav > play: /dev/dsp: Invalid argument > > Whats wrong? What's wrong is that you have _only_ tried using a single program to test your audio system out. > > Rgdz, > Sergey Osokin, > o...@etrust.ru > > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: MTRR support for AMD K6-2?
On Fri, 21 May 1999, Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: > > > > > > Do we have MTRR support for the AMD K6-2, and how's it done (e.g., if I > > > want > > > to allow mtrr support for my Voodoo Banshee) > > > > It's being worked on. The K6 is a problematic device, as it only > > supports two memory ranges, as opposed to the eight the P6 does. > > > > OK - give me a yell once it's ready for testing. I've got the docs and I _DO_ plan on writing the support relatively soon; I have been having busy weekends though. > > > Stephen > -- > The views expressed above are not those of PGS Tensor. > > "We've heard that a million monkeys at a million keyboards could produce > the Complete Works of Shakespeare; now, thanks to the Internet, we know > this is not true."Robert Wilensky, University of California > > > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: FBSDBOOT.EXE
On Wed, 19 May 1999, Luoqi Chen wrote: > > Jonathan Lemon says: > > : > > : Not true. VM86 is also required to support VESA. Also, it is used > > : for reliable memory detection (which is why I want to make it mandatory). > > : No more "My Stinkpad only detected 64M, what do I do now??!" questions. > > > > Actually, even with VM86, the kernel still doesn't correctly detect the > > StinkPad's memory. > > > > --Jerry > > > > name: Jerry Alexandratos || Open-Source software isn't a > > phone: 302.521.1018 || matter of life or death... > > email: jalex...@perspectives.net || ...It's much more important > > || than that! > > It just occurred to me that we might be able to use initial MTRR settings > by BIOS for memory detection (P6 and above, of course). Don't know how > reliable that is. And K6-family processors with newer BIOSes are usually write allocate-enabled and that can be used too. > > -lq > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: ATA and afd (LS-120): got it WORKING!
On Tue, 18 May 1999, Soren Schmidt wrote: > It seems Brian Feldman wrote: > > Yes, I finally got it working! The explanation is in the patch, which I > > should > > not need to explain again :) > > Hmm, Does it not work as is ?? It works on my LS120 drive, and a couble > of others. Besides your hack doesn't find my ZIP drive, and makes it > fail miserably. In that case, I'll fix it to do a strstr or something like that. What's your ZIP drive say? > > If its just that you are unsatisfied with only max 32K transfers, thats > another matter, and stuff for later changes. No, it does not work at all with that maximum set. I'm using the disk to hold an FFS filesystem, and mounting it, BTW. See, in the old driver, it limited the transfer, but it ALSO queued the rest of the transfer. AFD doesn't, and I can tell this because I get random parts of kernel memory interspersed with my files (that's the corruption), so I know all of the buffer is not being filled. You need to queue the rest of the transfer too. > > -S?ren > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
ATA and afd (LS-120): got it WORKING!
Yes, I finally got it working! The explanation is in the patch, which I should
not need to explain again :)
Brian Feldman_ __ ___ ___ ___ ___
gr...@unixhelp.org_ __ ___ | _ ) __| \
FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) |
http://www.freebsd.org _ |___)___/___/
--- src/sys/dev/ata/atapi-fd.c.orig Mon May 17 20:28:16 1999
+++ src/sys/dev/ata/atapi-fd.c Mon May 17 20:42:37 1999
@@ -83,7 +83,7 @@
int32_t afdattach(struct atapi_softc *);
static int32_t afd_sense(struct afd_softc *);
-static void afd_describe(struct afd_softc *);
+static void afd_describe(struct afd_softc *, int8_t *, int8_t *);
static void afd_strategy(struct buf *);
static void afd_start(struct afd_softc *);
static void afd_done(struct atapi_request *);
@@ -96,6 +96,8 @@
afdattach(struct atapi_softc *atp)
{
struct afd_softc *fdp;
+int8_t model_buf[40+1];
+int8_t revision_buf[8+1];
if (afdnlun >= NUNIT) {
printf("afd: too many units\n");
@@ -106,18 +108,22 @@
printf("afd: out of memory\n");
return -1;
}
+
bzero(fdp, sizeof(struct afd_softc));
bufq_init(&fdp->buf_queue);
fdp->atp = atp;
fdp->lun = afdnlun;
fdp->flags = F_MEDIA_CHANGED;
+bpack(atp->atapi_parm->model, model_buf, sizeof(model_buf));
+bpack(atp->atapi_parm->revision, revision_buf, sizeof(revision_buf));
+fdp->maxblks = strcmp(model_buf, "IOMEGA ZIP 100 ATAPI") ? 0 : 64;
if (afd_sense(fdp)) {
free(fdp, M_TEMP);
return -1;
}
-afd_describe(fdp);
+afd_describe(fdp, model_buf, revision_buf);
afdtab[afdnlun++] = fdp;
devstat_add_entry(&fdp->stats, "afd", fdp->lun, DEV_BSIZE,
DEVSTAT_NO_ORDERED_TAGS,
@@ -166,15 +172,10 @@
}
static void
-afd_describe(struct afd_softc *fdp)
+afd_describe(struct afd_softc *fdp, int8_t *model, int8_t *revision)
{
-int8_t model_buf[40+1];
-int8_t revision_buf[8+1];
-
-bpack(fdp->atp->atapi_parm->model, model_buf, sizeof(model_buf));
-bpack(fdp->atp->atapi_parm->revision, revision_buf, sizeof(revision_buf));
printf("afd%d: <%s/%s> rewriteable drive at ata%d as %s\n",
- fdp->lun, model_buf, revision_buf,
+ fdp->lun, model, revision,
fdp->atp->controller->lun,
(fdp->atp->unit == ATA_MASTER) ? "master" : "slave ");
printf("afd%d: %luMB (%u sectors), %u cyls, %u heads, %u S/T, %u B/S\n",
@@ -320,9 +321,14 @@
lba = bp->b_blkno / (fdp->cap.sector_size / DEV_BSIZE);
count = (bp->b_bcount + (fdp->cap.sector_size - 1)) / fdp->cap.sector_size;
-/* Should only be needed for ZIP drives, but better safe than sorry */
-if (count > 64)
- count = 64;
+/*
+ * This should only be needed for ZIP drives, since they lock up if a
+ * transfer of > 64 sectors is attempted. XXX TODO (for SOS): when
+ * this problem is to be worked around, multiple transfers will need
+ * to be queued!
+ */
+if (fdp->maxblks && count > fdp->maxblks)
+ count = fdp->maxblks;
bzero(ccb, sizeof(ccb));
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Re: UPDATE7: ATA/ATAPI driver new version available.
On Mon, 17 May 1999, Soren Schmidt wrote: > Seventh update to the new ATA/ATAPI driver: > > Fixed problems: > > LS120 drives currupted data. > The workaround for drives not supporting upto 64K transfers > has been reworked. It works now both on LS120 & ZIP drives. Thank you!! > > ISA only configs wont compile. > Fixed. > > The ATA driver wont share interrupts. > Fixed. > > The "unwanted interrupt" warning gave wrong controller. > Another lun<>unit messup from the newbus integration. > > Some minor cleanups and rearrangements as well. > > As usual USE AT YOUR OWN RISK!!, this is still pre alpha level code. > Especially the DMA support can hose your disk real bad if anything > goes wrong, again you have been warned :) > Notebook owners should be carefull that their machines dont suspend > as this might cause trouble... > > But please tell me how it works for you! > > Enjoy! > > -S?ren > > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: IDE strangeness
On Mon, 17 May 1999, Soren Schmidt wrote: > It seems Brian Feldman wrote: > > I'm having two problems with IDE nowadays. > > > > 1. ATA doesn't work with LS-120. That's not new. But ATA does seem to crash > > on > >me, and there's no dump() so I can't figure out why. Reply to my own problem: ATA crashed more often than wd, but they both crashed with my old, faulty CPU. My K6-2 350 now works perfectly. > > Good news is that I've gotten ahold of a LS120 drive, so I can test this now. > > Bad news is that it has stopped working on my ZIP drive too :( That's bad, if it used to. LS-120 never worked under ATA, with or without new-bus. But you say Zip always has. > > Something must have been screwed up since the newbus import, either in > my driver (I feel at risk saying that it is not likely), or something else. I'm pretty sure your driver isn't screwed up, as I've tracked most of the changes. > > -S?ren > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: New ATA driver still can't attach to ISA controllers
On Sat, 15 May 1999, Andrew Atrens wrote: > > On Fri, 14 May 1999, Rick Whitesel wrote: > > > I just wanted to say that I really appreciate the work you have/are > > doing. The disk drive performance under IDE is very important for the > > practical use of FreeBSD. > > > > Thank you! > > > I second that - thank you ! Heck, I'll third that! Now my wish list includes spelling correction (settting? heh, I have the patch at home), a d_dump_t, and possibly getting afd working, but that's not very much. This driver's already wonderful, without some of the last things I want, and is so FAST! > > > Andrew. > > -- > +-- > | Andrew Atrens Nortel Networks, Ottawa, Canada. | > | All opinions expressed are my own, not those of any employer. | >--+ > Heller's Law: The first myth of management is that it exists. > Johnson's Corollary: Nobody really knows what is going on >anywhere within the organization. > > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: DMA problems with IBM DeskStar drive
On 14 May 1999, Dag-Erling Smorgrav wrote: > "Alok K. Dhir" writes: > > Look for that setting in the SCSI BIOS > > I think not. I think not too. EIDE drives tend to not mess with SCSI too much... > > DES > -- > Dag-Erling Smorgrav - d...@yes.no > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: DMA problems with IBM DeskStar drive
On Fri, 14 May 1999, Greg Lehey wrote: > On Thursday, 13 May 1999 at 16:02:48 -0400, Brian Feldman wrote: > > That's funny, my system is pretty much the EXACT same as yours, and DMA > > does not > > get enabled for my Seagate 6.4GB UDMA2 drive. > > Did you set the flags? Of course, 0xa0ffa0ff on both controllers. All that has been tried. ATA does work with my UDMA drives, but lacking a dump function is insufficient for my purpouses. > > Greg > -- > See complete headers for address, home page and phone numbers > finger g...@lemis.com for PGP public key > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: DMA problems with IBM DeskStar drive
On Wed, 12 May 1999, Jordan K. Hubbard wrote: > > Try disabling "ultra DMA" in the BIOS, that seems to have worked for > > me on my IBM-DJNA-371800 drive. > > > > (Jordan: We may want to put something in the README about this in 3.2!) > > I'd welcome suggestions as to what the text should look like; I'm > still unclear as to what exactly the problem us. :) > I'd also be interested to know how you plan on describing disabling UDMA, since I don't see that option in my AMIBIOS. > - Jordan > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: DMA problems with IBM DeskStar drive
That's funny, my system is pretty much the EXACT same as yours, and DMA does not get enabled for my Seagate 6.4GB UDMA2 drive. Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: 3DNow! support?
On Mon, 10 May 1999, Doug Rabson wrote: > On Mon, 10 May 1999, Brian Feldman wrote: > > > Is anyone planning on upgrading the binutils gas to a later version so that > > we > > can get 3DNow! support? I'd like to use it, but I can't seem to get binutils > > to work right manually. > > I will update binutils when/if 2.9.2 comes out. Great! I look forward to that. > > -- > Doug Rabson Mail: d...@nlsystems.com > Nonlinear Systems Ltd.Phone: +44 181 442 9037 > > > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
3DNow! support?
Is anyone planning on upgrading the binutils gas to a later version so that we can get 3DNow! support? I'd like to use it, but I can't seem to get binutils to work right manually. Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Doesn't anyone care about the broken sio ??
On Sat, 8 May 1999, Jordan K. Hubbard wrote: > > I mailed a simple way to reproduce the serious brokeness of the > > serial port driver on my system and no one responds. > > > > What does this mean ? > > It means that nobody is probably willing to go bring up a MAME > environment just to test this. You need to isolate it to a more > minimal test case if you want people to jump on what could be a local > problem (some serial hardware is better behaved than others) or a > misbehaving X server (which is masking interrupts for too long; see > mailing list archives on this topic). The more complex your > reproduction case, in other words, the less likely it is that anyone > will respond to it. Hmm, so now you're the second to cite the possibility of X masking interrupts too long, eh? ;) Actually, I use MAME all the time, and this problem does NOT occur (XF86_SVGA on an S3 ViRGE/DX). Oh, user-ppp too of course. If I could have reproduced this problem, I would have replied. > > If you can say "here's a small stand-alone C program which hogs things > to the extent that the serial driver seriously overruns its buffers" > then it's likely that someone will be at least motivated to compile, > run and try it. If it involves running some esoteric application > which requires downloading data of questionable legality on top of it, > it's far less likely that anyone will even bother to look. MAME is a great piece of software, and in and of itself entirely legal; what problem do you have with it? > > - Jordan > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: IDE strangeness
On Thu, 6 May 1999, Lee Cremeans wrote: > On Thu, May 06, 1999 at 10:04:19PM -0400, Brian Feldman wrote: > > > 2. wd supports UDMA on my chipset, but won't enable any kind of DMA on my > >new Seagate, which does UDMA2 fine with ATA > > > > Can you boot -v and give the output of the ATA_INQUIRY line? That should say > which modes are available on the drive. So, any ideas at all? > > -lee > > -- > ++ > | Lee Cremeans -- Manassas, VA, USA (WakkyMouse on WTnet) | > | lcreme...@erols.com | http://wakky.dyndns.org/~lee | > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: IDE strangeness
On Thu, 6 May 1999, Lee Cremeans wrote: > On Thu, May 06, 1999 at 10:04:19PM -0400, Brian Feldman wrote: > > > 2. wd supports UDMA on my chipset, but won't enable any kind of DMA on my > >new Seagate, which does UDMA2 fine with ATA > > > > Can you boot -v and give the output of the ATA_INQUIRY line? That should say > which modes are available on the drive. Here's what I've got: ide_pci0: at device 15.0 on pci0 ide_pci: busmaster 0 status: 84 from port: ffa2 ide_pci: busmaster 1 status: 84 from port: ffaa wdc0 at port 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa0 wd0: wdsetmode() setting transfer mode to 42 wdc0: unit 0 (wd0): , 32-bit, multi-block-16 wd0: 6103MB (12500460 sectors), 13228 cyls, 15 heads, 63 S/T, 512 B/S wd0: ATA INQUIRE valid = 0007, dmamword = 0407, apio = 0003, udma = 0007 wdc0: unit 1 (atapi): , removable, dma, iordy wcd0: drive speed 2067KB/sec, 128KB cache wcd0: supported read types: CD-R, CD-DA wcd0: Audio: play, 16 volume levels wcd0: Mechanism: ejectable tray wcd0: Medium: no/blank disc inside, unlocked wdc0: interrupting at irq 14 wdc1 at port 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa0 wd3: wdsetmode() setting transfer mode to 22 wdc1: unit 1 (wd3): , DMA, 32-bit, multi-block-32 wd3: 1554MB (3183264 sectors), 3158 cyls, 16 heads, 63 S/T, 512 B/S wd3: ATA INQUIRE valid = 0003, dmamword = 0407, apio = 0003, udma = wdc1: unit 0 (atapi): , removable, iordy wfd0: medium type unknown (no disk) wdc1: interrupting at irq 15 > > -lee > > -- > ++ > | Lee Cremeans -- Manassas, VA, USA (WakkyMouse on WTnet) | > | lcreme...@erols.com | http://wakky.dyndns.org/~lee | > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
IDE strangeness
I'm having two problems with IDE nowadays. 1. ATA doesn't work with LS-120. That's not new. But ATA does seem to crash on me, and there's no dump() so I can't figure out why. 2. wd supports UDMA on my chipset, but won't enable any kind of DMA on my new Seagate, which does UDMA2 fine with ATA Any ideas? ide_pci0: at device 15.0 on pci0 wdc0 at port 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa0 wdc0: unit 0 (wd0): , 32-bit, multi-block-16 wd0: 6103MB (12500460 sectors), 13228 cyls, 15 heads, 63 S/T, 512 B/S wdc0: unit 1 (atapi): , removable, dma, iordy wcd0: drive speed 2067KB/sec, 128KB cache wcd0: supported read types: CD-R, CD-DA wcd0: Audio: play, 16 volume levels wcd0: Mechanism: ejectable tray wcd0: Medium: no/blank disc inside, unlocked wdc0: interrupting at irq 14 wdc1 at port 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa0 wdc1: unit 1 (wd3): , DMA, 32-bit, multi-block-32 wd3: 1554MB (3183264 sectors), 3158 cyls, 16 heads, 63 S/T, 512 B/S wdc1: unit 0 (atapi): , removable, iordy wfd0: medium type unknown (no disk) wdc1: interrupting at irq 15 Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Silo overflows and MAME can someone else reproduce this problem ??
On Tue, 4 May 1999, Matthew Thyer wrote: > My usermode ppp works fine normally as I can quite happily download > 4 things at once without a single silo overflow (as I did last night) > even when there is lots of disk activity or X11 activity. > > Note this problem is unrelated to newbus as it occurs both before and > after those commits. Doesn't X turn off interrupts? A lot? ESPECIALLY in things like the DGA code (which you're probably using with xmame, aren't you?)? Hope I'm thinking on the right track... ;) > > Matthew Thyer wrote: > > > > This problem is easily reproducible. > > > > However to do so, you need a ROM image for an arcade game that the > > Multi Arcade Machine Emulator emulates as it wont do it without any > > roms in the directory "/usr/local/lib/mame/roms". > > > > I am using xmame installed from the ports collection > > (/usr/ports/emulators/xmame) on a very recent -CURRENT machine. > > > > If I run xmame *before* I get online with user mode ppp (or while > > I am on the net), the serial ports get hosed and I have to reboot > > or I continually get silo overflows. > > > > This is not right as it happens AFTER I exit xmame !!! > > > > Please can someone else reproduce this problem as I'd hate to think > > its only on the systems I have owned (Pentium 166 and Celeron 300). > > > -- > /===\ > | Work: matthew.th...@dsto.defence.gov.au | Home: thy...@camtech.net.au | > \===/ > "If it is true that our Universe has a zero net value for all conserved > quantities, then it may simply be a fluctuation of the vacuum of some > larger space in which our Universe is imbedded. In answer to the > question of why it happened, I offer the modest proposal that our > Universe is simply one of those things which happen from time to time." > E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: -stable vs -current (was Re: solid NFS patch #6... )
On Fri, 30 Apr 1999, Matthew Dillon wrote: > Well, what it comes down to is the number of developers actively > developing the codebase. We had some truely unfortunate timing with > people leaving and new people coming on, and pieces of the system ( such > as NFS ) that simply were left dangling for a long period of time with > nobody actively locating or fixing bugs. There have been too many critics > and not enough people getting into the guts of the code and fixing things. > ( Of course, I'm *very* biased here in my opinion :-) ). > > What it comes down to is that a whole lot of changes were made between > 2.2.x and 3.0 without enough debugging by the authors. This kinda > resulted > in a partially rotting code base even through the 3.1 release, until a > number of us got sick and tired of it and started actively tracking down > and fixing the bugs. > > I expect the 3.2 release to be a really good release. > > It is true that -current has been, more often then not, more stable then > -stable in the last two months. This is because fixes were being made > to -current more quickly then they could be backported to -stable. Most > of these fixes *have* been backported at this point. There are still a > few that have not that are on my hot list ( and still not addressed, even > with prodding ). There are also a few bug fixes that simply cannot be > backported to stable without some pain ( i.e. require the complete > replacement of a number of subsystems ), and pain is not in the cards > with the 3.2 release so close. > > It is hard enough dealing with two branches of the source tree. I will > personally take my Super Soaker 5000 to anyone suggesting that we have > *three* . Sqirt sqirt sqirt! 5000 is out? YES!!! > > I am hoping that we will be able to accomplish a major synchronization > after the 3.2 release. I personally believe that -current is stable > enough that we should do one big-assed commit to sync -stable up to the > current -current and then continue as per normal. I only wish EGCS > hadn't been incorporated quite yet. At the very least, I want to > sync *my* stuff up ( NFS/VM/VFS/BIO/VN/SWAPPER ). I wholeheartedly agree with this idea! > > -Matt > > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: New ATA drivers problem? (Was: New kernels won't boot)
On Thu, 29 Apr 1999, Soren Schmidt wrote: > It seems Brian Feldman wrote: > > >Ever going to help with my atapi-fd problems? I found examples of the > >corruptions, including lots of NULLs... > > Well, so long as I cannot get my hands on the problem, its real hard > to solve it. I'm trying to get ahold of the same LS120 drive here > but so far I havn't found any, in fact LS120 drives are extremely > rare over here... Basically, this drive is a Digital Research brand; it (its firmware?) is made by Motorola, and supposedly this is all the same as an off-the-shelf Imation drive. > > -S?ren > > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: New ATA drivers problem? (Was: New kernels won't boot)
On Wed, 28 Apr 1999, Soren Schmidt wrote: > > Hi, > > I have three hosts with -current, all with the new ATA in function. > > Booting the same kernel produces different results on all of them wrt > > root file system mounting: > > > > - one reports 'changing root device to wd0s3a' > > - one reports 'changing root device to wd0s3a' followed by 'changing > > root device to wd0a' and continues flawlessly > > - one reports 'changing root device to wd0s3a' followed by 'changing > > root device to wd0a' and panics with 'cannot mount root file system (2), > > err 22' > > > > All motherboards are equipped with the PIIX4 IDE controller. If I need > > to supply the dmesg output and/or configuration, please let me know. All > > three hosts have FreeBSD on the first disk (on different disk locations, > > though). > > Hmm, could you mail me the output of fdisk & disklabel from those tree > machines, with indication of how they behave ?? > > I'm unable to reproduce those errors here, but this might bring the > details I need to figure it out... > > -S?ren Ever going to help with my atapi-fd problems? I found examples of the corruptions, including lots of NULLs... > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: New ATA hangs my machine
On Sat, 24 Apr 1999, Andrzej Bialecki wrote: > Hi, > > I'd love to play with the new IDE drivers, especially that I got an LS-120 Note that wfd is here for those drives.. I'm currently in a sticky situation: wd: works with all drives, does no manner of DMA on my 6.4G Medalist ATA: works with all but LS-120 (for me), does UDMA2 great on my Medalist, but has no dump routine > drive, but... I can't mount my filesystems with it. I'm using today's > sources (kernel config file attached), and it fsck's them just ok, and > then just hangs. Keyboard works, though. If I boot with -v, it reports: > > ad0: invalid primary partition table: no magic > > and of course it just sits there... > > The issue is, however, that old kernel booted just fine. I attached > relevant parts of dmesg with old drivers, and disklabel and fdisk output. > > Any clues? LBA? > > Andrzej Bialecki > > // WebGiro AB, Sweden (http://www.webgiro.com) > // --- > // -- FreeBSD: The Power to Serve. http://www.freebsd.org ---- > // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: does login.conf limitations work ?
On Sat, 24 Apr 1999, Stephane Legrand wrote: > Andrzej Bialecki writes: > > On Fri, 23 Apr 1999, Luigi Rizzo wrote: > > > > > Hi, > > > > > > i was wondering if the limitations that are supposed to be enforced via > > > the login.conf mechanism do really work... > > > > > > In particular, i have tried (on 3.1 something, but don't think that > > > current is much different in this respect) to enforce the daily etc. > > > login times but the system seems to ignore them. > > > > > > I think /etc/login.conf is properly parsed, because if i assign a user > > > to a class that is not defined in login.conf i get complaints, but > > > other than that i am unable to limit login time... > > > > > > Any hints ? > > > > That's also my impression. I glipmsed the whole source tree and I couldn't > > find any place where the limits are enforced. BTW. what entity should > > enforce login time limits? Kernel? Some user-space daemon? > > > > To report a login.conf success, i've used on a 2.2.8 system the > "cputime" ressource limit. I set it to zero and that worked very > well. So may be only some limits are implemented ? > If you'd like to see where the ones which are implemented are implemented, look at the process context-switch routines in the kernel. Not having checked, but guessing, I bet login reads login.conf as a db and uses the values to set rlimits, which is where they would be set. > Stephane Legrand. > > -- > stephane.legr...@wanadoo.fr : http://perso.wanadoo.fr/stephane.legrand/ > FreeBSD Francophone : http://www.freebsd-fr.org/ > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: New ATA driver and crash dumps
On Fri, 23 Apr 1999, Mike Smith wrote: > >Is there any way I can help in getting the atapi-fd driver to work with > > LS-120's? > > Unless it was just recently broken, it works fine (I have one). ATA has never worked with my LS-120. It's a Digital Research/Mitsubishi, and I just can't get it to work right. I get garbled data, that's just it. > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ m...@smith.net.au > \\ The race is long, and in the \\ msm...@freebsd.org > \\ end it's only with yourself. \\ msm...@cdrom.com > > > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: solid NFS patch #6 avail for -current - need testers files)
On Thu, 22 Apr 1999, Luoqi Chen wrote: > > Steve Kargl wrote: > > > > > > > > That's a little foolish since we've still not found all the egcs > > > > > optimizer bugs and whatnot; didn't you guys see the one Luigi found > > > > > the other day for ftpd? Now *that* had to be some obscure debugging > > > > > work! :-) > > > > > > > > Clearly, that goes to show Luigi must have no life... :-) > > > > > > > > > > "Luigi" is an interesting spelling of "Louqi". > > > > To my defense, I thought it was Louqi, but since I have been making > > a lot of mistaken comments lately, I decided to trust what Jordan > > has said... > > > I thought you guys had better things to do other than arguing about how > to spell my name. None of them is correct anyway, it is not even in > alphabets... > > > I just wish april would go away, very, very fast... > > > Here's a challenge to help you get by the rest of the days, figure out > how to write my name, in its original form I was given at birth :-) Hmm... is it cheating to use Hiragana? (^_^) > > > -- > > Daniel C. Sobral(8-DCS) > > d...@newsguy.com > > d...@freebsd.org > > > > "Well, Windows works, using a loose definition of 'works'..." > > > > -lq > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: New ATA driver and crash dumps
On Thu, 22 Apr 1999, Soren Schmidt wrote: > It seems Brian Feldman wrote: > >> Hmm, I have a ZIP here which works, and I have reports from mike that > >> his LS120 works too, so I'm a bit confused here. > >> How does it not work ?? > > > >I get consistent errors reading from it (not hard errors, data errors). The > >md5 checksums I created on the disk using the wd driver do not match the > >varying checksums md5 gives me on the LS-120 with the new ATA. > > Hmm, does it still work with the old driver ?? Yep, flawlessly. > Does it share the channel with another device ?? (ata/atapi??) ata0: master: settting up UDMA2 mode on Aladdin chip OK ad0: ATA-4 disk at ata0 as master ad0: 6103MB (12500460 sectors), 13228 cyls, 15 heads, 63 S/T, 512 B/S ad0: piomode=4, dmamode=2, udmamode=2 ad0: 16 secs/int, 0 depth queue, DMA mode ata1: slave: settting up WDMA2 mode on Aladdin chip OK ad3: ATA-? disk at ata1 as slave ad3: 1554MB (3183264 sectors), 3158 cyls, 16 heads, 63 S/T, 512 B/S ad3: piomode=4, dmamode=2, udmamode=-1 ad3: 16 secs/int, 0 depth queue, DMA mode acd0: CDROM drive at ata0 as slave acd0: drive speed 2067KB/sec, 128KB cache acd0: supported read types: CD-R, CD-DA acd0: Audio: play, 16 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked afd0: rewriteable drive at ata1 as master afd0: 120MB (246528 sectors), 963 cyls, 8 heads, 32 S/T, 512 B/S afd0: Unknown media (0x0) > It sounds like a HW problem of some sort to me.. > Or one that's exacerbated by the new drivers. > -S?ren > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: New ATA driver and crash dumps
On Thu, 22 Apr 1999, Soren Schmidt wrote: > It seems Brian Feldman wrote: > > >This and atapi-fd not working are the only hang-ups I have with using ATA. > >Heck, the benefits even outweigh that since my new UDMA2 hard drive is only > >supported with your wonderful new ATA drivers, not wd! The Aladdin support > >works great. > > Is there any way I can help in getting the atapi-fd driver to work with > >LS-120's? > > Hmm, I have a ZIP here which works, and I have reports from mike that > his LS120 works too, so I'm a bit confused here. > How does it not work ?? I get consistent errors reading from it (not hard errors, data errors). The md5 checksums I created on the disk using the wd driver do not match the varying checksums md5 gives me on the LS-120 with the new ATA. > > -S?ren > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: New ATA driver and crash dumps
On Wed, 21 Apr 1999, Soren Schmidt wrote: > It seems Christopher Masto wrote: > > My machine panicked today for the first time since switching to the > > new ATA drivers, and I noticed that I no longer have crash dumps. > > Is this something that is expected to be put back in soon? > > > > I know S?ren's a busy guy, and I'm glad we have the results of his > > work. I just hope the old drivers don't get killed off until the > > replacement has the same functionality. > > > > Then again, wddump() is only 100 lines of code, so I should probably > > try to fix it myself before whining. > > I know :), it has just not been done yet. It will be done eventually > but I have other areas in the driver I want finish first. This and atapi-fd not working are the only hang-ups I have with using ATA. Heck, the benefits even outweigh that since my new UDMA2 hard drive is only supported with your wonderful new ATA drivers, not wd! The Aladdin support works great. Is there any way I can help in getting the atapi-fd driver to work with LS-120's? > > Also the old wd driver will probably not be killed off entirely, as > its the only one we have that support old ST506/ESDI drives. > > -S?ren > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: new kernel and IPDIVERT
On Mon, 19 Apr 1999, Ilya Naumov wrote: > > i have compiled the latest kernel and encountered a problem with IPDIVERT. > even > with "options IPDIVERT" string in kernel config, kernel says the following: > > IP packet filtering initialized, divert disabled, rule-based forwarding > disabled, logging disabled That's because it's loading the ipfw.ko KLD. > > of course, firewall rules like "add divert natd ..." do not work. everything > is > ok with old kernel (~5 days old). could anyone comment this? I know about it, but don't know how to fix it :( However, for now, you can go over to /usr/src/sys/modules/, edit the Makefile and add what features you want to CFLAGS, and make depend all install clean && shutdown -r now. > > -- > > sincerely, > ilya naumov (at work) > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Parallel ZIP drive hangs machine
On Sun, 18 Apr 1999, Smelly Pooh wrote: > I'm running current as of April 6th and whenever I try to multi-volume tar > directly to my parallel port zip drive using /dev/da0 it hangs when it gets to > the end of the zip. I don't think it's a hardware problem because I've seen > it happen on 2 completely separate machines. This is a known problem, that writes to an end of a block device will cause a lockup. I have no idea if anyone was going to fix this. Did you try using the character device, which is what you SHOULD be using anyway? > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: newbus and modem(s)
On Sun, 18 Apr 1999, Alex Zepeda wrote: > On Mon, 19 Apr 1999, Daniel C. Sobral wrote: > > > I think CAM is a very bad example. We *still* don't have all the > > drivers we had, and that includes at least one reasonably requested > > driver. > > Is that an offer to write the missing drivers? > > > On the other hand, I don't see we losing anything with newbus, which > > is quite a feat given the extent of the changes. Moreover, I have > > seen very few problems reported. Changing the compiler to egcs seems > > to have produced more waves, in fact. > > Plug and Play for at least the sio driver, perhaps just pnp in general for > drivers that were moved to the newbus stuff. > > Is there any documentation explaining what exactly was changed? > > Sure, egcs created problems, but at least the general public was warned > that this was going to be merged soon. But the kernel worked, and C > programs worked usually. > > > > Well, why not make ext2fs the default fs just to shake things up? It's > > > one thing to expect panics and soon, but it's another thing to import code > > > that wasn't ready. > > > > It seems to work on my computer. Why do you say it isn't ready? A > > reality check seems to be in order. It would seem you are peeved > > because some of the very few gliches affected you. > > Why would I say it wasn't ready? Because outside of core (apparently), > nobody was warned/told that this was going to be committed in a few > days/hours/minutes. > > Glitches? What about the sbxvi driver? The apm driver? Sure, I'm > annoyed about one of the glitches affecting me, but I just think if this > code had been aired more publically before merging, all of these problems > could have been easily avoided. I saw this and just had to note something to you. THINK what branch you are using. This is _WHERE_ things are being aired publically, and merged eventually to the STABLE branch. > > And then what about newconfig? To me this just adds more truth to the > whole /. argument that *BSD promotes a closed development model. > > - alex > > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: new-bus breaks both sound drivers
On Sun, 18 Apr 1999, Daniel C. Sobral wrote: > Brian Feldman wrote: > > > > > IPFW works for me...but I'm loading the KLD. > > > > I like having my ipfw rules there BEFORE anything happens, hence before > > rc(5). > > klds can be loaded by the loader. Hence, before /kernel. Thanks for ruining my logic ;) But I really do hate overstuffing Makefile.inc in sys/modules so I can get the options I want. That's why for most things I use the kernel itself and not modules, really. > > -- > Daniel C. Sobral (8-DCS) > d...@newsguy.com > d...@freebsd.org > > "Well, Windows works, using a loose definition of 'works'..." > > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ __ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: new-bus breaks both sound drivers
On Sat, 17 Apr 1999, Jake Burkholder wrote: > > Hmm, you might like to try this patch and see what happens, there is > > a missing old driver wrapper for the pcm stuff. As a result, it's not > > getting run from the isa probe. Regarding the other driver, I'm not > > sure what's going on there as the hooks appear to be present. > > Right on, that patch does it for me. > > pcm0 at port 0x220 irq 5 drq 1 flags 0x15 on isa0 > pcm0: interrupting at irq 5 > > I've got an old SB16 Value, non-pnp. > > mp3s aren't playing quite right with x11amp though, little > skips here and there, they work fine with the old kernel. > mpg123 seems fine, as does the sound in FXTV. > I'll try making the world again. I suggest using the old VoxWare with an old SB16, like I do. I was only trying to use pcm temporarily because sbxvi is broken (fix isa_compat.h). > > IPFW works for me...but I'm loading the KLD. > I like having my ipfw rules there BEFORE anything happens, hence before rc(5). > my panasonic cdrom is no longer probed, it uses the matcd driver. > doesn't show up in dmesg at all, but it does in the visual kernel > config thing. It's so old, I'm not surprised :) > > great work! > > Jake > -- > we are but packets in the internet of life > > > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ __ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: new-bus breaks both sound drivers
Oh, btw, you did break sbxvi. Look carefully at the #if which surrounds it ;) Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: new-bus breaks both sound drivers
On Sun, 18 Apr 1999, Peter Wemm wrote:
> Brian Feldman wrote:
> > On Sat, 17 Apr 1999, Peter Wemm wrote:
> > > Chris Piazza wrote:
> > > > On 17-Apr-99 Brian Feldman wrote:
> > > > > Both sound drivers are broken with the new-bus code. My SB16, in the
> > > > > ol
> d
> > > > > driver, now gets recognized but sbxvi is never looked for. pcm0, the
> > > > > ne
> w
> > > > > driver, never initializes with the new code :(
> > > > >
> > > > > device pcm0 at isa? port? tty irq 5 drq 1 flags 0x16
> > > > >
> > > >
> > > > The pcm0 sounddriver works for me. In fact, the only problem I had
> > > > with
> new
> > > > bus was it is now pcm0 instead of pcm1 ;-).
> > > >
> > > > es0: at device 9.0 on pci0
> > > > pcm0: using I/O space register mapping at 0xd800
> > > > es0: interrupting at irq 4
> > > >
> > > > device pcm0
> > >
> > > On two different systems it works for me using pcm0..
>
> > Here's what's going on with the pcm code. I've got an on-board audio device
> > that should probably eventually be supported, is PnP and detected, but
> > not recognized by the pcm driver. However, my SB16 ALSO fails to be
> > attached.
> > My SB16 is a nice pre-PnP one, which used to work fine with either audio
> > driver. I'll paste my current config and dmesg.
>
> [..]
> > # Luigi's snd code.
> > # You may also wish to enable the pnp controller with this, for pnp
> > # sound cards.
> > #
> > device pcm0
> > device pcm1 at isa? port? tty irq 5 drq 1 flags 0x16
> [..]
>
>
> Hmm, you might like to try this patch and see what happens, there is
> a missing old driver wrapper for the pcm stuff. As a result, it's not
> getting run from the isa probe. Regarding the other driver, I'm not
> sure what's going on there as the hooks appear to be present.
Thank you, that did work :) Now if someone could tell me why I need to
keep seeing
sorry, read DMA channel unavailable
let me know. This seems to be something that I do NOT need to see
from sb_dsp.c :P Other than that, everything's nice and peachy.
No, wait, I forgot. IPFW is _not_ being recognized in the kernel, and
the module is getting loaded instead (ipfw not being initialized?).
>
> Index: i386/isa/isa_compat.h
> ===
> RCS file: /home/ncvs/src/sys/i386/isa/isa_compat.h,v
> retrieving revision 1.1
> diff -u -r1.1 isa_compat.h
> --- isa_compat.h 1999/04/16 21:22:23 1.1
> +++ isa_compat.h 1999/04/17 17:30:34
> @@ -49,6 +49,7 @@
> #include "ze.h"
> #include "zp.h"
> #include "oltr.h"
> +#include "pcm.h"
> #include "pas.h"
> #include "sb.h"
> #include "sbxvi.h"
> @@ -117,6 +118,7 @@
> extern struct isa_driver zedriver;
> extern struct isa_driver zpdriver;
> extern struct isa_driver oltrdriver;
> +extern struct isa_driver pcmdriver;
> extern struct isa_driver pasdriver;
> extern struct isa_driver sbdriver;
> extern struct isa_driver sbxvidriver;
> @@ -320,6 +322,9 @@
>
> #if NOLTR > 0
> { DRIVER_TYPE_MISC, &oltrdriver },
> +#endif
> +#if NPCM > 0
> + { DRIVER_TYPE_MISC, &pcmdriver },
> #endif
> #if NPAS > 0
> { DRIVER_TYPE_MISC, &pasdriver },
>
>
> Cheers,
> -Peter
>
>
Brian Feldman_ __ ___ ___ ___ ___
gr...@unixhelp.org_ __ ___ | _ ) __| \
FreeBSD: The Power to Serve! _ __ | _ __ \ |) |
http://www.freebsd.org _ |___/___/___/
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Re: new-bus breaks both sound drivers
On Sat, 17 Apr 1999, Peter Wemm wrote: > Chris Piazza wrote: > > On 17-Apr-99 Brian Feldman wrote: > > > Both sound drivers are broken with the new-bus code. My SB16, in the old > > > driver, now gets recognized but sbxvi is never looked for. pcm0, the new > > > driver, never initializes with the new code :( > > > > > > device pcm0 at isa? port? tty irq 5 drq 1 flags 0x16 > > > > > > > The pcm0 sounddriver works for me. In fact, the only problem I had with new > > bus was it is now pcm0 instead of pcm1 ;-). > > > > es0: at device 9.0 on pci0 > > pcm0: using I/O space register mapping at 0xd800 > > es0: interrupting at irq 4 > > > > device pcm0 > > On two different systems it works for me using pcm0.. > > This is an ESS clone card: > > Probing for PnP devices: > CSN 1 Vendor ID: ESS1868 [0x68187316] Serial 0x Comp ID: PNPb02f > [0x2fb0 > d041] > ESS1868 (rev 11) > pcm1 (ESS1868 sn 0x) at 0x220-0x22f irq 5 drq 1 on isa > > This is an on-board Crystal SB-like PnP device: > > Probing for PnP devices: > CSN 1 Vendor ID: CSC0b36 [0x360b630e] Serial 0x Comp ID: @@@ > [0x > ] > mss_attach 1 at 0x530 irq 5 dma 1:0 flags 0x10 > pcm1 (CS423x/Yamaha/AD1816 sn 0x) at 0x530-0x537 irq 5 drq 1 > fl > ags 0x10 on isa > > For what it's worth, PnP has for the most part not been changed under > new-bus and is using the old mechanisms. The only significant risk is that > the attach code doesn't like what I've done with the emulation of > isa_device->id_id for "unit numbers". > > I'm sorry, you're going to need to have a bit of a look around and turning > on or inserting some debug code to see what's happening. > > Cheers, > -Peter > > > Here's what's going on with the pcm code. I've got an on-board audio device that should probably eventually be supported, is PnP and detected, but not recognized by the pcm driver. However, my SB16 ALSO fails to be attached. My SB16 is a nice pre-PnP one, which used to work fine with either audio driver. I'll paste my current config and dmesg. # # GENERIC -- Generic machine with WD/AHx/NCR/BTx family disks # # For more information read the handbook part System Administration -> # Configuring the FreeBSD Kernel -> The Configuration File. # The handbook is available in /usr/share/doc/handbook or online as # latest version from the FreeBSD World Wide Web server # http://www.FreeBSD.ORG/> # # An exhaustive list of options and more detailed explanations of the # device lines is present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $Id: GENERIC,v 1.102 1998/01/11 02:16:38 jkh Exp $ machine "i386" cpu "I586_CPU" ident "CUSTOM" maxusers128 makeoptions DEBUG="-g" options "MATH_EMULATE" #Support for x87 emulation options "INET" #InterNETworking options "FFS" #Berkeley Fast Filesystem options "FFS_ROOT" #FFS usable as root device [keep this!] options "CD9660"#ISO 9660 Filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options "UCONSOLE" #Allow users to grab the console options "FAILSAFE" #Be conservative options "USERCONFIG"#boot -c editor options "VISUAL_USERCONFIG" #visual boot -c editor options "NO_F00F_HACK" options "IPFIREWALL" options "IPFIREWALL_DEFAULT_TO_ACCEPT" options "IPFIREWALL_FORWARD" #enable xparent proxy support options "IPDIVERT" options "IPSTEALTH" options "DUMMYNET" options "DDB" options "DDB_UNATTENDED" options "VM86" options "SOFTUPDATES" options "PQ_HUGECACHE" # color for 1024k cache options "ICMP_BANDLIM" options "MSGBUF_SIZE=16384" options "VESA" options "INVARIANTS" options "INVARIANT_SUPPORT" options "CLK_USE_TSC_CALIBRATION" #options"ICMP_BANDLIM_SILENT" #options"CPU_WT_ALLOC" #options"NO_MEMORY_HOLE" config
new-bus breaks both sound drivers
Both sound drivers are broken with the new-bus code. My SB16, in the old driver, now gets recognized but sbxvi is never looked for. pcm0, the new driver, never initializes with the new code :( device pcm0 at isa? port? tty irq 5 drq 1 flags 0x16 #controller snd0 #device sb0 at isa? port 0x220 irq 5 drq 1 #device sbxvi0 at isa? drq 6 #device sbmidi0 at isa? port 0x330 #device opl0 at isa? port 0x388 Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \\__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: swap-related problems
On Wed, 14 Apr 1999, Anthony Kimball wrote: > Quoth Poul-Henning Kamp on Wed, 14 April: > : > : 1. Demonstrate the need. > > Well, it's only needed if you want to be able to reliably execute ANSI > C code according to spec. I personally don't care. I'd be surprised > if core didn't though. I would suspect that it would be deemed worthy > of someone's p2 queue, at least. ACTUALLY it would still break ANSI because the malloc itself would crash the program, instead of touching the memory manually. > > : 2. Implement it > : > : 3. Send patches. > > And I certainly don't care enough to do that!-) > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ __ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: swap-related problems
On Wed, 14 Apr 1999, Poul-Henning Kamp wrote: > In message <14100.61923.427423.153...@avalon.east>, Anthony Kimball writes: > > > >: > All I want is that a program gets NULL from malloc if there is no memory > >: > available. I find that to be a very fundamental thing about malloc. > > > >: Do you have a solution? We don't. > > > >Make an sbrk variant which will pre-allocate backing store. > >setenv MALLOC_PREALLOCATE > > > >Not so hard. > > 1. Demonstrate the need. I'm not doing this, damnit ;) > > 2. Implement it Add another character to the malloc options there already. When something is allocated, touch the first char to be '\0'. Implementation done. > > 3. Send patches. Part of 2. > > -- > Poul-Henning Kamp FreeBSD coreteam member > p...@freebsd.org "Real hackers run -current on their laptop." > FreeBSD -- It will take a long time before progress goes too far! > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ __ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: swap-related problems
On Wed, 14 Apr 1999, Poul-Henning Kamp wrote: > In message <199904141501.laa25...@kot.ne.mediaone.net>, Mikhail Teterin > writes: > >Poul-Henning Kamp once stated: > > > >=malloc() on FreeBSD returns NULL when it cannot allocate the memory > >=asked for. > > > >=If you have an example where this is not the case I would VERY > >=much like to see it. > > > >I believe, a number of examples were given, when the use of the non-NULL > >pointer returned by malloc resulted in the program being killed. > > No, the examples I have seen showed the system killing a (somewhat) > random large process in an attempt to avoid deadlock. > > I guess you can interpret it the way above if you insist on using a > very narrow application oriented focus. > > Ignoring the larger issues is not a modus operandi I subscribe to. > > Anyway, what you're asking for is really resource reservation. > > Sorry FreeBSD doesn't support resource reservation for memory. mlock()? BTW, why can't anyone explain why the old behavior WAS THAT the process would get NULL? Now it's this... > > -- > Poul-Henning Kamp FreeBSD coreteam member > p...@freebsd.org "Real hackers run -current on their laptop." > FreeBSD -- It will take a long time before progress goes too far! > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ __ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: swap-related problems
On Wed, 14 Apr 1999, Poul-Henning Kamp wrote: > In message <199904132245.saa93...@misha.cisco.com>, Mikhail Teterin writes: > >Poul-Henning Kamp once wrote: > > >Well, this is just an implementation detail, is not it? I don't > >mean to critisize, or anything, but such thing as "no available > >memory" is a fairly intuitive... Coming down, again, the malloc > >should return a usable memory if available and NULL if it's not. > >Is not this a "natural" semantics? Why can a program die because > >_another_ program ate up all the rest of the memory? > > You know, this strikes me about as productive a discussion as the > "split infinitive should be outlawed by style(9)" we have every > so often. > > Very very fundamental to UNIX philosophy is the maxim that it is > roots responsibility to configure the system right. > > FreeBSD will defend itself against misconfigurations as best it > can, this includes shooting processes down when things get too > squeezy. > > Think of it as self-defence. > > The real problem is that you system isn't configured for what you > use it for. Fine. Let's have a kernel option for it, because a LOT of us want the old functionality back, and yes it _WAS_ there before. > > -- > Poul-Henning Kamp FreeBSD coreteam member > p...@freebsd.org "Real hackers run -current on their laptop." > FreeBSD -- It will take a long time before progress goes too far! > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
RE: swap-related problems
On Wed, 14 Apr 1999, Alfred Perlstein wrote:
> On Wed, 14 Apr 1999, Ladavac Marino wrote:
>
> > > -Original Message-
> > > From: Mikhail Teterin [SMTP:m...@misha.cisco.com]
> > > Sent: Wednesday, April 14, 1999 12:45 AM
> > > To: curr...@freebsd.org
> > > Subject: Re: swap-related problems
> > >
> > >
> > > Well, this is just an implementation detail, is not it? I don't
> > > mean to critisize, or anything, but such thing as "no available
> > > memory" is a fairly intuitive... Coming down, again, the malloc
> > > should return a usable memory if available and NULL if it's not.
> > > Is not this a "natural" semantics? Why can a program die because
> > > _another_ program ate up all the rest of the memory?
> > >
> > >
> > [ML] This is a common problem for any OS that implements memory
> > overcommit. This means that it is not possible to detect an out-of-swap
> > condition sinchronously as the swap is reserved only when the pages are
> > dirtied and not when brk is grown. This means that you can set brk a
> > gigabyte higher (given that your user limits allow that), and you will
> > not be using swap as long as you do not write to the pages you
> > "allocated" to the process.
> >
> > Another strategy is to reserve the swap space as soon as it is
> > allocated by the program. This strategy is much more conservative and
> > inherently safer, but it needs much more space: for instance, if you
> > have a program with WSS of a gigabyte and you want to system( "date" ),
> > you will need at least 2 gigs of swap because system() does fork() first
> > which means that you get 2 copies of your big program and the system
> > cannot know that in one of the copies an exec() will be shortly
> > forthcoming--thus, it has to reserve the full WSS for the copy because
> > it will potentially write to all pages of its WSS.
>
> An interesting idea would be to mark this process as killable if COW
> causes an out of swap condition. Another interesting application would
> be a fork() call that checks this condition and fails if there is
> potential for overcommit. forkifavail()
>
> Basically anyone doing a system("date"); should be using vfork (yes
> i can see when vfork is not sufficient)
>
> This would sort of be like a soft limit on memory allocation and hint
> to the kernel of which processes are the ones causeing overcommit.
>
> basically at a certain point, sbrk will fail and forked processes
> would be marked killable...
>
> does this make sense?
>
> has the idea of processes running with uid < 10 or just root being
> excempt from this "frantic kill" ?
This isn't really a great idea since it would be changing the Unix
API. However, I agree that processes with exclusive use of the video
hardware should not be killed by the system *COUGH XFree86 COUGH*.
>
> -Alfred
>
> >
> > It would be nice if memory overcommit were configurable (on-off,
> > or per process).
> >
> > /Marino
> >
> >
> > To Unsubscribe: send mail to majord...@freebsd.org
> > with "unsubscribe freebsd-current" in the body of the message
> >
>
> Alfred Perlstein - Admin, coder, and admirer of all things BSD.
> -- There are operating systems, and then there's FreeBSD.
> -- http://www.freebsd.org/4.0-current
>
>
>
> To Unsubscribe: send mail to majord...@freebsd.org
> with "unsubscribe freebsd-current" in the body of the message
>
Brian Feldman_ __ ___ ___ ___ ___
gr...@unixhelp.org_ __ ___ | _ ) __| \
FreeBSD: The Power to Serve! _ __ | _ \__ \ |) |
http://www.freebsd.org _ |___/___/___/
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Re: have live system with NFS client cache problems what do i do?
On Mon, 12 Apr 1999, Stephen McKay wrote:
> On Sunday, 11th April 1999, Brian Feldman wrote:
>
> >This has nothing to do with DOS. In case you didn't get my other hint:
> >{"/home/green"}$ dd if=/dev/zero count=1 2>/dev/null | file -
> >standard input: MS Windows COFF Unknown CPU
>
> Don't ya just hate it when your mail is slow! Sigh...
Yep ;)
You know, I think a much better idea for being in magic(5) would be
a check for lots of NULLs and calling the file "NULL data", rather than
MS Windows COFF Unknown CPU. This identification is a bug in the magic
file, really, since you can't call a short 0x any kind of magic
number!
>
> Stephen.
>
>
> To Unsubscribe: send mail to majord...@freebsd.org
> with "unsubscribe freebsd-current" in the body of the message
>
Brian Feldman_ __ ___ ___ ___ ___
gr...@unixhelp.org_ __ ___ | _ ) __| \
FreeBSD: The Power to Serve! _ __ | _ \__ \ |) |
http://www.freebsd.org _ |___/___/___/
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Re: have live system with NFS client cache problems what do i do?
On Sun, 11 Apr 1999, Matthew Dillon wrote:
> :/usr/obj isn't mounted, i'm just compiling a kernel.
> :
> :no i have no msdos mounted filesystems, i do however have an
> :unmounted win98 partition and a cdrom with joliet extentions mounted
> :however the cdrom only contains mp3s.
> :
> :After doing more data manipulation (copying files around to flush
> :the NFS cache) it seems to reload the data then it finds them ok
> :and tries to link, during the link i get missing references to
> :several symbols, symbol sizes changed etc etc...
> :
> :Just seems like bad data.
> :
> :Now if i just go into the dir on the server and link the kernel
> :it's fine, no problems whatsoever. (compile on local disk)
> :
> :-Alfred
> :
> :PS, i suspect the 3comIII card in the laptop # ep: 3Com 3C509 (buggy)
> :
> :NFS perfomance and stability in 3.1-stable and 4.0 have been surperb lately.
> :one reboot when i was killing a low ram NFS server a few weeks ago and just
> :this today (which could be the NIC) otherwise very impressive.
>
> Ok. This is something to watch, then. The corruption is worrysome. It
> is odd to get this sort of corruption in a client's buffer cache when
> all the file I/O is running over NFS. The real question is : where did
> the corruption come from? The client's IDE drive or something originally
> on the server?
>
> Are there any dos partitions on the server at all? If not, then the
> corruption is occuring on the client. But if the make procedure is not
> accessing (much of) the client's hard drive, where on the client could
> the corruption be coming from?
This has nothing to do with DOS. In case you didn't get my other hint:
{"/home/green"}$ dd if=/dev/zero count=1 2>/dev/null | file -
standard input: MS Windows COFF Unknown CPU
>
> -Matt
> Matthew Dillon
>
>
>
>
> To Unsubscribe: send mail to majord...@freebsd.org
> with "unsubscribe freebsd-current" in the body of the message
>
Brian Feldman_ __ ___ ___ ___ ___
gr...@unixhelp.org_ __ ___ | _ ) __| \
FreeBSD: The Power to Serve! _ __ | _ \__ \ |) |
http://www.freebsd.org _ |___/___/___/
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Re: have live system with NFS client cache problems what do i do?
On Sun, 11 Apr 1999, Matthew Dillon wrote: > :-current as of tuesday night. although the laptop is now moved > :to -current as of today. > : > :i have 192.168.1.44:/usr/src on /usr/src > : > :this is only building the kernel in /usr/src/sys/compile/laptop > : > :server: > :FreeBSD myname.my.domain 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Fri Apr 9 > 11:34:01 PDT 1999 bri...@myname.my.domain:/usr/src/sys/compile/halah i386 > : > :client: > :FreeBSD myname.my.domain 4.0-CURRENT FreeBSD 4.0-CURRENT #1: Sun Apr 11 > 17:46:19 PDT 1999 bri...@myname.my.domain:/usr/src/sys/compile/laptop > i386 > : > :i think it may be easily reproducable. > : > :-Alfred > > This is very odd: > > doing a 'file cd9660_bmap.o' on laptop (NFS client) gives me a > cd9660_bmap.o: MS Windows COFF Unknown CPU > > An MS Windows binary? Do you have any msdos mounts on > the client or server? How is /usr/obj mounted? Hey Matt, 0 leshort 0x MS Windows COFF Unknown CPU ;) > > -Matt > Matthew Dillon > > > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: swap-related problems
On Sun, 11 Apr 1999, Matthew Dillon wrote: > :I use the memory as soon as it's malloced. If it reserves a page, then > :pagefaults it into existence, the VM system knows that that page is now > :allocated. When I malloc the last available page for user use, the VM > :system knows that it's the last page. I dirty it, and there are none > :free. If I malloc(), I want to know that there is no more memory, not > :have my process killed. This is POMA. > : > :Previously, the POLA, a NULL getting returned, WORKED CORRECTLY. It did this > :for a long time. My little test program always showed this, and shows > :that now something was broken. I'll attach it to the end. > > I ran your program. malloc() appears to work properly -- returns NULL > when > the datasize limit is reached. In my case, I set the datasize limit > to 64MB and ran the program. Unset the datasize limit. Now what happens? It used to return NULL, now it gets SIGKILLed. Seriously, about the killing thing, shouldn't we at least have a timer so two things don't get killed? > > ... > mallocs failed at 64956 > > Under 4.0-current. > > :> then one or two processes getting killed. Having N random processes > get > :> malloc() failures can lead to serious instability with processes. > : > :Only bad code doesn't check return values of malloc(). > > You are volunteering to run through the thousands of programs & ports > to make sure that every one checks the return value for malloc()? > > Declarations that don't solve problems are not relevant. It's bad enough > that we have to kill something to handle an out-of-vm situation, we > shouldn't go off and destabilize the rest of the system while we are at > it. > > -Matt > > I don't tend to use untrustworthy code for production things. I doubt there are any unchecked mallocs in something as tested as, say, X11R6.3. There could be.. Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: swap-related problems
On Sun, 11 Apr 1999, Matthew Dillon wrote:
> :It seems that something has broken the good ol' swap behavior. For instance,
> :I have my user-limits set to unlimited and I run something which uses up
> :all RAM. Mallocing never FAILS in the program, as brk() doesn't fail, as etc
> :etc etc. But mallocing continues, all swap space gets used, and both the
> :runaway process and the next biggest gets killed (XF86, of course).
> : Matt, perhaps you can shed light on
> : a. why mallocs still succeed after
> :swap_pager: out of swap space
> :swap_pager_getswapspace: failed
> :is displayed
> : b. why the process continues and gets killed TWICE, or two different
> : processes get killed
> :?
> :
> : Brian Feldman_ __ ___ ___ ___ ___
>
> The thing with the processes getting killed twice or two different
> processes being killed is due to the latency between sending the signal
> to kill the process and the process actually going away. In order to be
> killed, the process must be woken up and allowed to run.
Then let's make sure the kill waits before it does that.
>
> malloc() still succeeds because it isn't actually touching the new memory,
> and so the system doesn't actually reserve the memory as of the time of
> the system call. That is done by the user program later on after malloc()
> returns. malloc()'s limitations are based on the process resources, not
> available memory.
I use the memory as soon as it's malloced. If it reserves a page, then
pagefaults it into existence, the VM system knows that that page is now
allocated. When I malloc the last available page for user use, the VM
system knows that it's the last page. I dirty it, and there are none
free. If I malloc(), I want to know that there is no more memory, not
have my process killed. This is POMA.
Previously, the POLA, a NULL getting returned, WORKED CORRECTLY. It did this
for a long time. My little test program always showed this, and shows
that now something was broken. I'll attach it to the end.
>
> It would not be appropriate to make malloc() fail in this situation
> because
> this would result in N random programs getting malloc() failures rather
> then one or two processes getting killed. Having N random processes get
> malloc() failures can lead to serious instability with processes.
Only bad code doesn't check return values of malloc().
>
> What might help in a situation like this would a way to flag certain
> processes as being 'very important' ... that should only be killed as
> a last resort, even if they have a relatively large RSS.
Yes, I was thinking of something like this for the X server.
>
> -Matt
> Matthew Dillon
>
>
>
Brian Feldman_ __ ___ ___ ___ ___
gr...@unixhelp.org_ __ ___ | _ ) __| \
FreeBSD: The Power to Serve! _ __ | _ \__ \ |) |
http://www.freebsd.org _ |___/___/___/
ts=4
#include
#include
#include
#define SIZE 1024*1024
#ifdef OTHER_VER
const unsigned int junk[] = {
0xdeadbeef,
0xbeeff00d,
0x133751ff,
0xf33db34f
};
#endif
void
main(void) {
int count, yep = 0;
void *stfu[SIZE];
void *mem;
for (count = 0; count < SIZE; count++) {
if ((mem = stfu[count] = malloc(1024))) {
int where;
printf("%p (%i) malloc'd\n", stfu[count], count);
for (where = 0; where < (1024 / sizeof(unsigned));
where++)
((unsigned *)mem)[where] =
#ifdef OTHER_VER
junk[
#endif
where
#ifdef OTHER_VER
% 4]
#endif
;
yep++;
}
else
break;
}
/* free(stfu[yep--]); */
for (count = 0; count < yep; count++) {
int where;
mem = stfu[count];
for (where = 0; where < (1024 / sizeof(unsigned)); where++)
if (((unsigned *)mem)[where] !=
#ifdef OTHER_VER
Re: DoS from local users (fwd)
On Sun, 11 Apr 1999, Kevin Day wrote: > > In message <199904102057.paa27...@home.dragondata.com> Kevin Day writes: > > : i.e. uid 1001 starts 40 processes eating as much cpu as they can. Then uid > > : 1002 starts up one process. Uid 1002's process gets 50% cpu, and uid > > 1001's > > : 40 processes get 50% cpu shared between them. > > > > I've seen some experimental patches in the past that try to do just > > this. However, there are some problems. What if uid 1002's process > > does a sleep. Should the 40 processes that 1001 just get 50% of the > > cpu? Or should there be other limits. It turns into an interesting > > research problem in a hurry. > > > > Warner > > > > I was thinking essentially just processes in the RUN state get applied to > this. If the cpu would otherwise be sitting idle, by all means give it to > someone. But, if two users have processes running, just because one user has > 50 processes doesn't mean it should get 50x the cpu as one user who has one > process running. If a process is in sleep or blocked(select, IO, whatever), > it's taken out of consideration for the cpu, and the full cpu is given to > those processes that actually have work to do. > > > At least, that's my take on it. > > I run into this problem daily, and i get enough user complains of "User x > has 50 processes running, eating as much cpu as they can, my compile just > took 15 minutes". "What was their user name again?" *click xterm click* ps aux | grep ^user | wc -l "Hmm, you're right, fifty processes called 'cpuwaster'." rmuser user "They've been eliminated, thank you for letting us know of problems you have!" It's called "being a sysadmin". If someone's abusing the machine, delete em. > > > Kevin > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
swap-related problems
It seems that something has broken the good ol' swap behavior. For instance, I have my user-limits set to unlimited and I run something which uses up all RAM. Mallocing never FAILS in the program, as brk() doesn't fail, as etc etc etc. But mallocing continues, all swap space gets used, and both the runaway process and the next biggest gets killed (XF86, of course). Matt, perhaps you can shed light on a. why mallocs still succeed after swap_pager: out of swap space swap_pager_getswapspace: failed is displayed b. why the process continues and gets killed TWICE, or two different processes get killed ? Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Libraries with library dependancies
On Sat, 10 Apr 1999, John Polstra wrote: > Brian Feldman wrote: > > > YES! Make the mdXXX symbols all weak, so libmd can be added manually! > > Peter already mentioned why that isn't necessary. I just want to add > a caution to folks out there. Don't go wild with weak symbols. Think > VERY carefully (and get a review) before using them. They should > be treated as an absolute last resort. You can paint yourself into > a corner before you know it, and you won't find out until it's time > to upgrade something and you suddenly realize that none of your old > executables will run any more. > Which is why I do NOT advocate making / shared, but shared libs there would be useful still. > John > --- > John Polstra j...@polstra.com > John D. Polstra & Co., Inc.Seattle, Washington USA > "Self-interest is the aphrodisiac of belief." -- James V. DeLong > > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: DoS from local users (fwd)
On Sat, 10 Apr 1999, Dmitry Valdov wrote: > Hi! > > Once again - HOW I can limit CPU usage by *kernel* ? > Also, I've just tried set maxprocesses 5. > And it helpless. > With 5 processes limit user was able to slow down P2-450 computer. > Switching between windows in X was VERY slow. Mouse movements was slow down > too. > CPU states: 32.3% user, 0.0% nice, 67.2% system, 0.0% interrupt, 0.5% idle > > Please, just try it. If you want to preempt other tasks, make that user's tasks niced!! > > > On Sat, 10 Apr 1999, Brian Feldman wrote: > > > Date: Sat, 10 Apr 1999 09:29:19 -0400 (EDT) > > From: Brian Feldman > > To: Dmitry Valdov > > Cc: ch...@calldei.com, freebsd-current@FreeBSD.ORG, > > freebsd-questi...@freebsd.org > > Subject: Re: DoS from local users (fwd) > > > > On Sat, 10 Apr 1999, Dmitry Valdov wrote: > > > > > > > > > > > On Sat, 10 Apr 1999, Chris Costello wrote: > > > > > > > Date: Sat, 10 Apr 1999 02:05:33 -0500 > > > > From: Chris Costello > > > > Reply-To: ch...@calldei.com > > > > To: Dmitry Valdov > > > > Cc: freebsd-current@FreeBSD.ORG, freebsd-questi...@freebsd.org > > > > Subject: Re: DoS from local users (fwd) > > > > > > > > On Sat, Apr 10, 1999, Dmitry Valdov wrote: > > > > > >You typically want to set a restriction as to how many > > > > > > processes a user can spawn. This is done by editing > > > > > > /etc/login.conf and changing the user's login class, see the man > > > > > > page for 'login.conf'. > > > > > > > > > > > > > > > > I'm about CPU usage, not about many processes. > > > > > See: > > > > > CPU states: 17.8% user, 0.0% nice, 81.7% system, 0.5% interrupt, > > > > > 0.0% > > > > > idle > > > > > on any (tested on P2-45) machine. > > > > > > > > > > CPU is used by SYSTEM, not by USER. So I can't restrict it with > > > > > login.conf > > > > > And load average can be up to 20-40 :( > > > > > > > > > > Please don't redirect me to -questions, it's a kernel problem, not > > > > > just > > > > > config. > > > > > > > >How is it a kernel problem? It's a forkbomb. It spawns many > > > > processes. You can also limit CPU usage with login.conf, I > > > > believe. > > > > > > Hmm. How I can limit CPU usage by SYSTEM? See top's output below. > > > > > > Dmitry. > > > > > > PS. I've just tried it. And I'm right - CPU usage limit can't help. > > > > > > > So? Processes that run a while go down in priority [McKusick95 I believe, > > THE > > book] so they are preempted easily. Look in top and see if they're all at > > the top of the list. I bet they're not! Also, you can set per-user niceness > > levels, and why are you being so liberal giving a standard LUSER 32 > > processes? > > This is a system administration problem. > > > > > > > > > > > To Unsubscribe: send mail to majord...@freebsd.org > > > with "unsubscribe freebsd-current" in the body of the message > > > > > > > Brian Feldman_ __ ___ ___ ___ ___ > > gr...@unixhelp.org_ __ ___ | _ ) __| \ > > FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | > > http://www.freebsd.org _ |___/___/___/ > > > > > > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Libraries with library dependancies
On Sat, 10 Apr 1999, Peter Wemm wrote: > Mark Murray wrote: > > Hi > > > > I've been helping somebody along with getting the new libcrypt going, > > and something has broken recently (post-egcs?), and I'm having a wee > > problem debugging it. > > > > Libcrypt uses routines out of libmd (MD[45]* and SHA*), and a while > > back (pre-egcs), it was possible to have an "LDADD+=-lmd" in libcrypt's > > Makefile and have anything using libcrypt also automagically pick up the > > -lmd dependancy requirement. This no longer seems to work: > > > > cc -O -pipe -I/usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5 > > -I > /usr/obj/usr/src/gnu/usr.bin/perl/miniperl > -I/usr/obj/usr/src/tmp/usr/inc > lude -c > /usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5/minipe > rlmain.c > > cc -O -pipe -I/usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5 > > -I > /usr/obj/usr/src/gnu/usr.bin/perl/miniperl > -I/usr/obj/usr/src/tmp/usr/inc > lude -static -o miniperl miniperlmain.o -lperl -lm -lcrypt >^^^ > > /usr/obj/usr/src/tmp/usr/lib/libcrypt.a(crypt-shs.o): In function > > `crypt_shs' > : > > crypt-shs.o(.text+0x11): undefined reference to `SHA_Init' > > crypt-shs.o(.text+0x1f): undefined reference to `SHA_Update' > > crypt-shs.o(.text+0x3c): undefined reference to `SHA_Update' > > > > The "undefined references" are all in libmd which is listed as above > > in libcrypt's Makefile. > > This is only the case for -static.. Shared libraries have dependency > information, static libraries do not. > > > I would hate to have to hunt down all usages of -lcrypt to add -lmd. > > It would affect ports too, breaking a lot of things that know about -lcrypt > and have never heard of -lmd. > > The way I see it, you've got several choices.. > > 1) add -lmd for the cases where things are compiled static and leave the > rest > > 2) compile libcrypt.a differently to libcrypt.so, ie: add in the md*.o and > sha*.o static binaries into libcrypt by using SRCS+= sha.c in the !PIC case YES! Make the mdXXX symbols all weak, so libmd can be added manually! > > 3) help move ld.so to / so we can link everything dynamic.. :-) ld.so, ld-elf.so.1 SHOULD be in /, and fschg. They're definitely up there in importance with the kernel. This would allow something nice: /stand being a storage location for shared libraries. /stand meaning "standalone", hinting that only the root partition is necessary to run a shared program if necessary... let's move /usr/lib ELF libraries to /stand and keep all a.out and static libs (other than libgcc, foo) in /usr/lib. On the other hand, maybe that's a little radical! > > Cheers, > -Peter > > > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: DoS from local users (fwd)
On Sat, 10 Apr 1999, Dmitry Valdov wrote: > > > On Sat, 10 Apr 1999, Chris Costello wrote: > > > Date: Sat, 10 Apr 1999 02:05:33 -0500 > > From: Chris Costello > > Reply-To: ch...@calldei.com > > To: Dmitry Valdov > > Cc: freebsd-current@FreeBSD.ORG, freebsd-questi...@freebsd.org > > Subject: Re: DoS from local users (fwd) > > > > On Sat, Apr 10, 1999, Dmitry Valdov wrote: > > > >You typically want to set a restriction as to how many > > > > processes a user can spawn. This is done by editing > > > > /etc/login.conf and changing the user's login class, see the man > > > > page for 'login.conf'. > > > > > > > > > > I'm about CPU usage, not about many processes. > > > See: > > > CPU states: 17.8% user, 0.0% nice, 81.7% system, 0.5% interrupt, 0.0% > > > idle > > > on any (tested on P2-45) machine. > > > > > > CPU is used by SYSTEM, not by USER. So I can't restrict it with login.conf > > > And load average can be up to 20-40 :( > > > > > > Please don't redirect me to -questions, it's a kernel problem, not just > > > config. > > > >How is it a kernel problem? It's a forkbomb. It spawns many > > processes. You can also limit CPU usage with login.conf, I > > believe. > > Hmm. How I can limit CPU usage by SYSTEM? See top's output below. > > Dmitry. > > PS. I've just tried it. And I'm right - CPU usage limit can't help. > So? Processes that run a while go down in priority [McKusick95 I believe, THE book] so they are preempted easily. Look in top and see if they're all at the top of the list. I bet they're not! Also, you can set per-user niceness levels, and why are you being so liberal giving a standard LUSER 32 processes? This is a system administration problem. > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: msdosfs problems?
On Fri, 9 Apr 1999, Doug White wrote: > On Thu, 8 Apr 1999, Alex Zepeda wrote: > > > I've got all my mp3s stored on my fat16 partition so I can easily share > > them between Win98 and fbsd. However recently mpg123 has been complaining > > about once valid mp3s: > > > > zippy:~/mp3s#mpg123 -b10240 U2/U2\ -\ Sunday\ Bloody\ Sunday.mp3 > > High Performance MPEG 1.0/2.0/2.5 Audio Player for Layer 1, 2 and 3. > > Version 0.59q (1999/Jan/26). Written and copyrights by Michael Hipp. > > Uses code from various people. See 'README' for more! > > THIS SOFTWARE COMES WITH ABSOLUTELY NO WARRANTY! USE AT YOUR OWN RISK! > > Title : Sunday Bloody SundayArtist: U2 > > Album : Year: 83 > > Comment: Genre: Alternative > > > > Directory: U2/ > > Playing MPEG stream from U2 - Sunday Bloody Sunday.mp3 ... > > MPEG 1.0 layer III, 128 kbit/s, 44100 Hz joint-stereo > > Illegal Audio-MPEG-Header 0x at offset 0x80af. > > Skipped 4170 bytes in input. > > mpg123: Can't rewind stream by 679 bits! > > mpg123 is an ancient player. It won't play most newer MP3s. Use a newer > player, like x11amp or xaudio. In its defense, mpg123 is not ancient, and is the _BEST_ MP3 player. I have no idea what kinda of b0rked up MP3s there are nowadays it won't play. > > Doug White > Internet: dwh...@resnet.uoregon.edu| FreeBSD: The Power to Serve > http://gladstone.uoregon.edu/~dwhite| www.freebsd.org > > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: /sys/boot, egcs vs. gcc, -Os
On Sat, 10 Apr 1999, Bruce Evans wrote: > >But what's wrong with having a specific -= operator? It would make code more > >readable, which is a plus. It would be obvious for people to look for such > >before resorting to substition rules. > > Creeping featurism. Obscure semantics (would it do nothing if the rvalue > is not in the lvalue? What about if the rvalue is added later?). You say "creeping features", I say "something that would have made sense since the beginning". The semantics would be "yes" and "yes", respectively > > Bruce > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: /sys/boot, egcs vs. gcc, -Os
On Fri, 9 Apr 1999, Bruce Evans wrote:
> >> "CC+=-Os" in individual Makefiles works about as well as "CFLAGS+=-Os" for
> >> adding flags. That's not very well. Removing unwanted additions is hard.
>
> >Why don't we have a -= operator in make(1)?
>
> Substitution can replace -= in may cases, e.g.:
>
> CC:= ${CC:S/-Os//}
>
> This is "hard" because it has to be coded in the makefile, while additions
> can be passed to make.
But what's wrong with having a specific -= operator? It would make code more
readable, which is a plus. It would be obvious for people to look for such
before resorting to substition rules.
>
> Bruce
>
>
> To Unsubscribe: send mail to majord...@freebsd.org
> with "unsubscribe freebsd-current" in the body of the message
>
Brian Feldman_ __ ___ ___ ___ ___
gr...@unixhelp.org_ __ ___ | _ ) __| \
FreeBSD: The Power to Serve! _ __ | _ \__ \ |) |
http://www.freebsd.org _ |___/___/___/
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
make world breakage?!?
Am I the only one to get this error?? cc -nostdinc -O -pipe -I/usr/src/usr.sbin/amd/amd/../../../contrib/amd/amd -I. -I/usr/src/usr.sbin/amd/amd -I/usr/src/usr.sbin/amd/amd/../include -I/usr/src/usr.sbin/amd/amd/../../../contrib/amd/include -I/usr/src/usr.sbin/amd/amd/../../../contrib/amd -DHAVE_CONFIG_H -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.sbin/amd/amd/../../../contrib/amd/amd/clock.c /usr/src/usr.sbin/amd/amd/../../../contrib/amd/amd/clock.c:66: redefinition of `struct callout' *** Error code 1 Stop. It's been like this here for days, and noone's reported it. I can't figure out what's wrong with it :( I don't see how it could possibly be including sys/callout.h! *breaks down into sobbing and gibberish* Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: /sys/boot, egcs vs. gcc, -Os
On Thu, 8 Apr 1999, Bruce Evans wrote:
> >> Actually, they don't. Compiler-specific options can be put in ${CC}.
> >> Perhaps they even should be.
> >
> >But in this case, we want "-Os" (egcs) or "-O2" (gcc) only for
> >building boot -- not for everything. It could be parameterized with
> >make macros like "OPT_SMALL" and "OPT_FAST" in the *.mk files, I
> >suppose.
>
> "CC+=-Os" in individual Makefiles works about as well as "CFLAGS+=-Os" for
> adding flags. That's not very well. Removing unwanted additions is hard.
>
> BTW, boot2/Makefile uses "CFLAGS=" to override any previous definition
> of CFLAGS. This may break `make world' by removing -nostdinc.
Why don't we have a -= operator in make(1)?
>
> Bruce
>
>
> To Unsubscribe: send mail to majord...@freebsd.org
> with "unsubscribe freebsd-current" in the body of the message
>
Brian Feldman_ __ ___ ___ ___ ___
gr...@unixhelp.org_ __ ___ | _ ) __| \
FreeBSD: The Power to Serve! _ __ | _ \__ \ |) |
http://www.freebsd.org _ |___/___/___/
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Re: RE: EGCS optimizations
On Tue, 6 Apr 1999, David O'Brien wrote: > > Well what would be the chances of getting the pgcc patches committed? > > I'm quite interested in doing this, BUT only after the dust has settled > on the EGCS import and the Alpha build is fixed. Also the 1.1.2 PGCC > patches aren't available yet. > > jdp and I have another round of bootstraping to fix our current > less-than-optimal exception handling. I want to wait a week or so until > putting the changes into the tree. It's important to note that PGCC is NOWHERE NEAR production quality, last time I tried it, and not proven at all. I express no animosity toward PGCC itself, but unless it's been proven, I'd strongly oppose anything like this. > > -- > -- David(obr...@nuxi.com -or- obr...@freebsd.org) > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: panic: vm_page_bits: illegal base/size 4096/512
On Tue, 6 Apr 1999, Matthew Dillon wrote: > :This occurs when I'm copying from a floppy (MS-DOS) to my home dir which is > :on an FFS file system. Any ideas? Reproduced of course. > : > : Brian Feldman_ __ ___ ___ ___ ___ > : gr...@unixhelp.org_ __ ___ | _ ) __| \ > > Brian, if the contents of the floppy is not sensitive, could you gzip > it up and email it to me mime-encoded so I can reproduce the panic on my > test box? This panic was recently added to catch illegal requests to > set/clear dirty/valid bits in VM pages. I hope no hardware is triggering this, because today I also got a double page fault... I took out 32 mb of RAM I don't think is very good, and I need to see if this system approaches stability. > > -Matt > > > :initial pcb at 23f440 > :panicstr: vm_page_bits: illegal base/size 4096/512 > :panic messages: > > > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
panic: vm_page_bits: illegal base/size 4096/512
This occurs when I'm copying from a floppy (MS-DOS) to my home dir which is
on an FFS file system. Any ideas? Reproduced of course.
Brian Feldman_ __ ___ ___ ___ ___
gr...@unixhelp.org_ __ ___ | _ ) __| \
FreeBSD: The Power to Serve! _ __ | _ \__ \ |) |
http://www.freebsd.org _ |___/___/___/
cript started on Tue Apr 6 10:34:54 1999
{"/home/crash"}# gdb -k kernel.0 vmcore.0
GDB is free software and you are welcome to 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.
GDB 4.16 (i386-unknown-freebsd),
Copyright 1996 Free Software Foundation, Inc...
IdlePTD 2887680
initial pcb at 23f440
panicstr: vm_page_bits: illegal base/size 4096/512
panic messages:
---
panic: vm_page_bits: illegal base/size 4096/512
syncing disks... 21 19 14 11 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10
giving up
dumping to dev 20001, offset 8192
dump 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71
70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45
44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19
18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
---
#0 boot (howto=256) at ../../kern/kern_shutdown.c:287
287 dumppcb.pcb_cr3 = rcr3();
(kgdb) bt
#0 boot (howto=256) at ../../kern/kern_shutdown.c:287
#1 0xc01378a5 in panic () at ../../kern/kern_shutdown.c:448
#2 0xc019f491 in vm_page_bits (base=4096, size=512) at ../../vm/vm_page.c:1449
#3 0xc01a1cc8 in vnode_pager_input_smlfs (object=0xc6f55e0c, m=0xc054f6a0)
at ../../vm/vnode_pager.c:401
#4 0xc01a219f in vnode_pager_generic_getpages (vp=0xc6fc5bc0, m=0xc6e8ccf0,
bytecount=4096, reqpage=0) at ../../vm/vnode_pager.c:625
#5 0xc0f4b183 in ?? ()
#6 0xc01a201a in vnode_pager_getpages (object=0xc6f55e0c, m=0xc6e8ccf0,
count=1, reqpage=0) at vnode_if.h:1067
#7 0xc019633f in vm_fault (map=0xc6efeac0, vaddr=671449088,
fault_type=1 '\001', fault_flags=0) at ../../vm/vm_pager.h:120
#8 0xc01cb10c in trap_pfault (frame=0xc6e8cd98, usermode=0, eva=671449088)
at ../../i386/i386/trap.c:817
#9 0xc01cade7 in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = -1025695744,
tf_esi = 671449088, tf_ebp = -957821440, tf_isp = -957821504,
tf_ebx = 8192, tf_edx = 671453184, tf_ecx = 1024, tf_eax = -957829120,
tf_trapno = 12, tf_err = 0, tf_eip = -1071867086, tf_cs = 8,
tf_eflags = 66070, tf_esp = -957821184, tf_ss = -957821192})
at ../../i386/i386/trap.c:438
#10 0xc01c9b32 in slow_copyin ()
#11 0xc018d5e8 in ffs_write (ap=0xc6e8ceb8)
at ../../ufs/ufs/ufs_readwrite.c:468
#12 0xc01635f9 in vn_write (fp=0xc0e8cac0, uio=0xc6e8cf00, cred=0xc0e32580,
flags=0) at vnode_if.h:331
#13 0xc0142abc in dofilewrite (p=0xc66e2d60, fp=0xc0e8cac0, fd=4,
buf=0x28057000, nbyte=13180, offset=0x, flags=0)
at ../../kern/sys_generic.c:363
#14 0xc01429cb in write (p=0xc66e2d60, uap=0xc6e8cf84)
---Type to continue, or q to quit---
at ../../kern/sys_generic.c:298
#15 0xc01cb70e in syscall (frame={tf_es = 47, tf_ds = 47, tf_edi = 671444992,
tf_esi = 671444992, tf_ebp = -1077946852, tf_isp = -957820972,
tf_ebx = 13180, tf_edx = -1, tf_ecx = 4, tf_eax = 4, tf_trapno = 0,
tf_err = 2, tf_eip = 134522044, tf_cs = 31, tf_eflags = 531,
tf_esp = -1077946992, tf_ss = 47}) at ../../i386/i386/trap.c:1101
#16 0xc01bec4c in Xint0x80_syscall ()
#17 0x80488a6 in ?? ()
#18 0x804849c in ?? ()
#19 0x80480e9 in ?? ()
(kgdb) quit
{"/home/crash"}# ^D
Script done on Tue Apr 6 10:35:07 1999
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
EGCS breaks what(1)
Okay, let me be a little clearer ;) What(1) on the kernel no longer works
because previously, the
char sccs[] = { '@', '(', '#', ')' };
char version[] = blahhhfoo;
Was contiguous. However, nowadays, nice EGCS pads 4 bytes (WHY?!?!) between
those. So it appears "@(#)\0\0\0\0FreeBSD." in the binary. Of course,
strings are null-terminated... :P I don't know why EGCS does this!
Brian Feldman_ __ ___ ___ ___ ___
gr...@unixhelp.org_ __ ___ | _ ) __| \
FreeBSD: The Power to Serve! _ __ | _ \__ \ |) |
http://www.freebsd.org _ |___/___/___/
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Re: different systat -vmstat output when using egcs to compile kernel
^^ !!! > daefr \nisic0 > ir > ^^ !!! > Namei Name-cacheDir-cache prcfr > Calls hits% hits% react > 3831 525 14 1994 52 pdwake > pdpgs > Discs ccd0 ccd1 ccd2 ccd3 da0 da1 da2 intrn > KB/t 0.00 0.00 0.00 0.00 5.07 0.00 0.00 8343 buf > tps 0 0 0 086 0 0 7503 desiredvnodes > MB/s 0.00 0.00 0.00 0.00 0.42 0.00 0.00 1148 numvnodes > 428 freevnodes > > -- > Andreas Klemm http://www.FreeBSD.ORG/~andreas > http://www.freebsd.org/~fsmp/SMP/SMP.html > powered by Symmetric MultiProcessor FreeBSD > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Handbook DocBook cutover complete
On Thu, 1 Apr 1999, Joseph T. Lee wrote: > On Mon, Mar 29, 1999 at 06:34:27AM -0500, Brian Feldman wrote: > > Doc is a nice format, but it's not hypertext. Check out > > ports/palm/pilot_makedoc > > TealDoc's version supports graphics and links. Is it a published format, though? I know TealDoc is $$$, but the format must be open for it to be worth it to us Palm users. > > -- > Joseph nugundam =best=com==/==\=IIGS=/==\=Playstation=/==\=Civic HX CVT=/==\ > #Anime Expo 1998>> www.anime-expo.org/ > > # Redline Games >> www.redlinegames.com/> > # Cal-Animage Epsilon >> www.best.com/~nugundam/epsilon/ > > # EX: The Online World of Anime & Manga >> www.ex.org/ / > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: mount of write protected fd's
On Tue, 30 Mar 1999, Mikhail Teterin wrote: > Boris Staeblow once wrote: > > > mount should detect that a fd is write-protected and mount it "ro" > > although no "mount -r" is given... Isn't it possible to detect the w/p > > status from the fd-controller? > > Actually, the existing behavior is rather horrible. If you forget > to specify ro for a read-only floppy, mount will succeed, but the > kernel will keep complaining. It will also NOT let you umount the > damn thing (even with -f), until you take the floppy out and > write-enable it. Which, sometimes, requires use of duct tape... > > -mi Mount -u -o ro also works. > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Handbook DocBook cutover complete
On Mon, 29 Mar 1999 nclay...@lehman.com wrote: > On Mon, Mar 29, 1999 at 06:01:45AM -0500, Brian Feldman wrote: > > > Word .doc support is in the pipeline as well, probably for the end of > > > this week too (I've now given some money to the evil empire so I can > > > test the output myself). > > > > Why? We can use StarOffice 5.0x, after all. > > * Not if you're on a 2.2-stable system. Don't mock, because I still am, > until I find the time to upgrade. At least, I could never get it to work > solidly for any length of time. I know there have been updates, but > there's only so many times I'm prepared to download it. I meant use StarOffice to test out the Office .docs. > > * People who haven't yet switched to using FreeBSD can get a reasonably > good printed copy of the documentation (at the moment just the Handbook, > but eventually all the docs) on a Windows platform. > > * My accountant likes various bits and pieces to be entered in to their > home grown Access DB. So I needed to get hold of Office anyway (and as > an aside, the ODBC driver for Postgres works very nicely). > > > > Next on the list will be whatever internal format the Palm Pilot > > > uses. > > > I imagine this won't be too useful for the Handbook, but will > > > probably > > > be quite handy for the FAQ. . . > > > > Do you mean the Memo format or the Doc format? I hope you mean Doc... It > > might not even be worth it to do this, since a very nice, fast browser > > (Palmscape) has been around for a while on the Palm, and an offline browser > > called Plucker. > > I don't know yet, I need to get a Pilot :-) I'm open to recommendations, > and/or pointers to specifications for the format. Doc is a nice format, but it's not hypertext. Check out ports/palm/pilot_makedoc > > And if there are any programmers out there looking for something to do, > this could be quite a nice task. > > N > -- > --+==[ Systems Administrator, Year 2000 Test Lab, Lehman Brothers, Inc. ]==+-- > --+==[ 1 Broadgate, London, EC2M 7HA 0171-601-0011 x5514 ]==+-- > --+==[ Year 2000 Testing: It's about time. . . ]==+-- > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Handbook DocBook cutover complete
On Mon, 29 Mar 1999 nclay...@lehman.com wrote: > Kris, > > On Sun, Mar 28, 1999 at 04:40:22PM +0930, Kris Kennaway wrote: > > On Sat, 27 Mar 1999, Nik Clayton wrote: > > > Almost a year ago I started the project to switch the Handbook over > > > from LinuxDoc to DocBook. > > > > Can I ask what the differences and benefits are? > > As it currently stands in the repository, the DocBook Handbook can be > converted to HTML, Postscript, plain text, and Microsoft RTF. A bug > that I'll fix this week is currently preventing PDF generation. > > Word .doc support is in the pipeline as well, probably for the end of > this week too (I've now given some money to the evil empire so I can > test the output myself). Why? We can use StarOffice 5.0x, after all. > > Next on the list will be whatever internal format the Palm Pilot uses. > I imagine this won't be too useful for the Handbook, but will probably > be quite handy for the FAQ. . . Do you mean the Memo format or the Doc format? I hope you mean Doc... It might not even be worth it to do this, since a very nice, fast browser (Palmscape) has been around for a while on the Palm, and an offline browser called Plucker. > > More information at > > http://www.freebsd.org/~nik/primer/index.html > > N > -- > --+==[ Systems Administrator, Year 2000 Test Lab, Lehman Brothers, Inc. ]==+-- > --+==[ 1 Broadgate, London, EC2M 7HA 0171-601-0011 x5514 ]==+-- > --+==[ Year 2000 Testing: It's about time. . . ]==+-- > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: UPDATE4: ATA/ATAPI driver new version available.
On Sun, 28 Mar 1999, Brian Feldman wrote: >I tried this out just as soon as I saw the announcement! Your driver is > really coming along well. I have three basic problems with it: > > 1. A hard reset is necessary to get the CD-ROM drive to work with acd. > > wdc0: unit 1 (atapi): , removable, > dma, iordy > wcd0: drive speed 2067KB/sec, 128KB cache > wcd0: supported read types: CD-R, CD-DA > wcd0: Audio: play, 16 volume levels > wcd0: Mechanism: ejectable tray > wcd0: Medium: no/blank disc inside, unlocked > > > 2. My LS-120 still has no reliability with the driver, as reads are > corrupted extremely often. > > wdc1: unit 0 (atapi): , > removable, iordy > wfd0: medium type unknown (no disk) > > > 3. DMA is ineffective with file-system use. I can read from the raw > device rad0 at 4.5MB/s with a 1mb block size, but when I use iozone > performance > is around 2.5MB/s. Mounting wd shouldn't affect that, should it? I used the > same device special files to mount as before, with ATA_STATIC being used, > and noticed this. Better yet, I'll try this with a corrected fstab then > report back. Didn't think it would help... I corrected fstab, but the slow speed is still there. (And I notice it's time to fix my sig.) > > > Brian Feldman _ __ ___ ___ ___ > gr...@unixhelp.org _ __ ___ | _ ) __| \ >http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | > FreeBSD: The Power to Serve!_ __ ___ _ |___/___/___/ > > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: UPDATE4: ATA/ATAPI driver new version available.
I tried this out just as soon as I saw the announcement! Your driver is really coming along well. I have three basic problems with it: 1. A hard reset is necessary to get the CD-ROM drive to work with acd. wdc0: unit 1 (atapi): , removable, dma, iordy wcd0: drive speed 2067KB/sec, 128KB cache wcd0: supported read types: CD-R, CD-DA wcd0: Audio: play, 16 volume levels wcd0: Mechanism: ejectable tray wcd0: Medium: no/blank disc inside, unlocked 2. My LS-120 still has no reliability with the driver, as reads are corrupted extremely often. wdc1: unit 0 (atapi): , removable, iordy wfd0: medium type unknown (no disk) 3. DMA is ineffective with file-system use. I can read from the raw device rad0 at 4.5MB/s with a 1mb block size, but when I use iozone performance is around 2.5MB/s. Mounting wd shouldn't affect that, should it? I used the same device special files to mount as before, with ATA_STATIC being used, and noticed this. Better yet, I'll try this with a corrected fstab then report back. Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Spontaneous reboots
On Thu, 25 Mar 1999, Ben Smithurst wrote: > Kris Kennaway wrote: > > > Has anyone else been seeing this? What kind of information would help to > > narrow the problem down? > > This has happened a few times on my -stable box, though not very > often. It just happened a few minutes ago, I wasn't doing anything on > the machine, I wasn't even logged in. No core dump or anything. :-( I'd > think nothing of it on a -current box, but it seems a bit worrying that > this sort of thing happens on a supposedly "stable" version. Mind you, > it could be a hardware problem I suppose. It could. Ahem... are you absolutely certain there are no messages in /var/log/messages that happen before the reboot? > > Karl Pielorz wrote: > > > The sort of thing we're looking for is, Which version of FreeBSD > > (I'd assume something -current because you posted to the -current > > mailing list, but how current?), what hardware (i.e. CPU type > > [Intel/AMD/Cyrix]) etc. - how much memory, what types of hard drive > > (SCSI vs. IDE) etc. - if you have any 'weird' hardware in there? > > FreeBSD 3.1-STABLE, Cyrix 6x86 133MHz, 48MB RAM. I don't think I've got > any hardware I'd class as weird. Disk info, > > $ mount > /dev/wd0s2a on / (local, noatime, writes: sync 5 async 17) > /dev/wd0s3c on /home (local, soft-updates, writes: sync 2 async 61) > /dev/wd2s1c on /tmp (local, soft-updates, writes: sync 2 async 31) > /dev/wd2s2e on /usr (local, soft-updates, writes: sync 2 async 86) > /dev/wd2s3e on /var (local, nosuid, soft-updates, writes: sync 318 async 470) > procfs on /proc (local) > $ swapinfo > Device 1K-blocks UsedAvail Capacity Type > /dev/wd2s4b1606500 160522 0%Interleaved > > I'm not sure how recent, the machine had been up for nearly 22 days, and > I think I rebuilt the world soon before that, so it's as of around the > beginning of March. > > Brian Feldman wrote: > > > He should proviide a full dmesg from bootverbose mode. > > OK, I wonder if anyone can spot the problem in this (if indeed there is > something I've broken)... > > Copyright (c) 1992-1999 FreeBSD Inc. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > FreeBSD 3.1-STABLE #104: Tue Mar 2 18:29:08 GMT 1999 > b...@scientia.demon.co.uk:/usr/src/sys/compile/SCIENTIA > Calibrating clock(s) ... i8254 clock: 1193483 Hz > CLK_USE_I8254_CALIBRATION not specified - using default frequency > Timecounter "i8254" frequency 1193182 Hz > CPU: Cyrix 6x86 (486-class CPU) > Origin = "CyrixInstead" DIR=0x2231 Stepping=2 Revision=2 > real memory = 50331648 (49152K bytes) > Physical memory chunk(s): > 0x1000 - 0x0009, 651264 bytes (159 pages) > 0x0020 - 0x02ffdfff, 48226304 bytes (11774 pages) > avail memory = 47013888 (45912K bytes) > Found BIOS32 Service Directory header at 0xf00fad20 > Entry = 0xfb1a0 (0xf00fb1a0) Rev = 0 Len = 1 > PCI BIOS entry at 0xb1d0 > Other BIOS signatures found: > ACPI: > $PnP: 000fbf50 > pci_open(1): mode 1 addr port (0x0cf8) is 0x805c > pci_open(1a): mode1res=0x8000 (0x8000) > pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=70308086) > Probing for devices on PCI bus 0: > found-> vendor=0x8086, dev=0x7030, revid=0x02 > class=06-00-00, hdrtype=0x00, mfdev=0 > subordinatebus=0secondarybus=0 > chip0: rev 0x02 on pci0.0.0 > > PCI Concurrency: enabled > Cache: 256K pipelined-burst secondary; L1 enabled > DRAM: no memory hole, 66 MHz refresh > Read burst timing: x-2-2-2/x-3-3-3 > Write burst timing: x-3-3-3 > RAS-CAS delay: 3 clocks > found-> vendor=0x8086, dev=0x7000, revid=0x01 > class=06-01-00, hdrtype=0x00, mfdev=1 > subordinatebus=0secondarybus=0 > chip1: rev 0x01 on pci0.7.0 > I/O Recovery Timing: 8-bit 2 clocks, 16-bit 1 clocks > Extended BIOS: disabled > Lower BIOS: disabled > Coprocessor IRQ13: enabled > Mouse IRQ12: disabled > Interrupt Routing: A: disabled, B: disabled, C: IRQ11, D: disabled > MB0: IRQ15, MB1: > found-> vendor=0x8086, dev=0x7010, revid=0x00 > class=01-01-80, hdrtype=0x00, mfdev=0 > subordinatebus=0secondarybus=0 > map[0]: type 4, range 32, base f000, size 4 > ide_pci0: rev 0x00 on pci0.7.1 > intel_piix_status: primary master/slave sample = 3, master/slave recovery = 1 > intel_piix_status: primary master fastDMAonly disabled, pre/post enabled, > intel_piix_sta
Re: Spontaneous reboots
On Tue, 23 Mar 1999, Karl Pielorz wrote: > Kris Kennaway wrote: > > > > For about the past week I've been getting spontaneous reboots on my machine. > > As far as I can tell, there's no obvious common connection - most recently > > my > > box was under load at the time, but the time before that all I did was move > > the mouse (shades of Windows :-) and nothing else much was running. > > > > This does only seem to happen when I'm using the machine - after a few > > hours, > > a reboot is pretty much guaranteed (sounds like a resource leak of some kind > > to me). Beyond that, I don't know. My kernel and machine config haven't > > changed recently. > > > > Has anyone else been seeing this? What kind of information would help to > > narrow the problem down? > > The sort of thing we're looking for is, Which version of FreeBSD (I'd assume > something -current because you posted to the -current mailing list, but how > current?), what hardware (i.e. CPU type [Intel/AMD/Cyrix]) etc. - how much > memory, what types of hard drive (SCSI vs. IDE) etc. - if you have any 'weird' > hardware in there? > > Also, you say "when I moved the mouse" - does that mean your machine lives in > X-Windows all the time? - Does it crash when it's not running X etc? What type > of video card does your machine have? > > The more detail you can provide (without going too OTT :-) - The more likely > someone will be able to help :-) I have two boxes here tracking 4.0-current, > and so far (looking for a nice piece of wood to touch), I've not seen any > reboots on either for quite a long time (i.e>months) :) > > -Karl > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > He should proviide a full dmesg from bootverbose mode. One thing I've seen is that K6-2's in write allocated mode have big problems. Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: rfork()
On Mon, 22 Mar 1999, Richard Seaman, Jr. wrote: > On Mon, Mar 22, 1999 at 11:34:25AM +0800, Peter Wemm wrote: > > > Doing clone() in libc that calls rfork(2) and doing all the stack setup > > should be pretty easy.. (Richard has done it already, yes?) > > Its in package at http://lt.tar.com/linuxthreads.tar.gz . If anyone wants > to grab it out of there an put it into shape to commit it, be my guest. > > > On the other > > hand, the linux emulator needs it so there's a counter-argument for making > > it a proper syscall outright. Leaving the rfork(2) stuff unmolested and at > > least resembling it's plan9 origins probably has some merit - adding extra > > arguments would mess that up. > > I) clone syscall > - > The linux emulator needs (and has) a clone syscall: > > int linux_clone(int flags, void *stack) > > The value of an exit signal is passed in the lower 8 bits of the flags > argument, > the linux counterparts to the FreeBSD RF* flags are passed in the balance > of the flags argument. > > I haven't seen or heard of a linux app that calls the clone syscall directly. > I know of two "apps", linuxthreads and the linux version of WINE, that call > the linux glibc version of clone (see below), which is a wrapper for the > syscall. > > The only thing that the linux syscall does, that can't be done easily in > FreeBSD using rfork and an appropriate wrapper to rfork, is pass in the > exit signal. rfork does have a flag to set an exit signal of SIGUSR1, but > it does not conveniently take a parameter to set it more flexibly. OTOH, > the only FreeBSD app I know of that actually sets an exit signal other > that the default SIGCHLD, is the linuxthreads port noted above. > > I'm not sure there is really a need for a "clone" syscall at this point, > but if you wanted it, you could just copy the linux_clone code in > linux_misc.c . You would have to decide if you want the flags parameter > to take the linux flags values, or FreeBSD flags (the emulator has > to take the linux values, obviously). > > My vote: don't bother with a syscall until there's a demonstrated need. > > II) clone in libc > - > Linux glibc has a clone call wrapper for the clone syscall, defined as: > >int clone (int (*fn) (void *arg), void *stack, int flags, void *arg) > > The stack and flags are passed directly to the clone syscall, and > the fn(arg) is the user function the cloned process should execute. > > Its easy enough to implement this in FreeBSD as a wrapper for rfork. > If you want to facilitate porting linux code, you would want the > flags argument to take linux flags, which would then be translated > into their FreeBSD counterparts before rfork is call. This is what > the code in the linuxthreads port does, and you are welcome to commit > it. > > The only issue here is whether people need to port linux code that > calls clone directly. As noted above, the only code I know of that > calls clone directly is WINE and linuxthreads. All the rest of the > code uses pthread_create, which only indirectly calls clone. > > My vote: I haven't seen the need, but if there is one, lets do it. > > III) libc rfork wrapper > --- > > It probably would be nice to have a libc rfork wrapper that grafts a > stack and a user function onto the rfork'd child process. But, it > should probably take FreeBSD flags, and there's no reason to > call it "clone". John Dyson's thr_fork is one such implementation. > Luoqi Chen posted another variation to either -hackers or -current > maybe 6-9 months ago. Matt Dillon just posted yet another variation. > Or, the linuxthreads port has a variation of the clone call that > has the same API as the linux clone call, but takes FreeBSD flags > (see clone.S). > > My vote: its worth doing, but not a top priority. The main issue > is to decide what interface would be most convenient. Its not a > top priority since the code already exists for those (rare) cases > where someone really needs it. And, lets not call it "clone". Let's call it "rfork() with one extra argument" instead then :) I don't see why this is a bad thing. Full backward compatibility is maintained, and it would be easy to implement. > > -- > Richard Seaman, Jr. email: d...@tar.com > 5182 N. Maple Lanephone: 414-367-5450 > Chenequa WI 53058 fax: 414-367-5852 > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: rfork()
On Mon, 22 Mar 1999, Peter Wemm wrote: > Matthew Dillon wrote: > > :Hence the NEW flag RFSTACK. Why would this be a bad thing? This would keep > > :the old behavior and allow much nicer new behavior. I didn't suggest > > :changing the old behavior. This would just greatly simplify things so all > > of > > > > I think Richard Seaman has it right: the stack needs to be passed. > > > > Why don't we simply implement the linux clone()? It sounds to me that > > it would be trivial. > > Doing clone() in libc that calls rfork(2) and doing all the stack setup > should be pretty easy.. (Richard has done it already, yes?) On the other > hand, the linux emulator needs it so there's a counter-argument for making > it a proper syscall outright. Leaving the rfork(2) stuff unmolested and at > least resembling it's plan9 origins probably has some merit - adding extra > arguments would mess that up. If we do varargs, then nothing could notice the difference. It's still backward-compatible, but it would be more powerful. How could that break something? Remember that the traditional int open(const char *, int, int) was changed to int open(const char *, int, ...) without any incompatibilities. > > Cheers, > -Peter > > > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: rfork()
On Sun, 21 Mar 1999, Matthew Dillon wrote: > :> :proc B returns since proc B is going to immediately switch over to a new > :> :stack? > :> > :> The return address for the procedure call is on the stack. If > something > :> munges the stack after the physical rfork occurs but before both > processes > :> can return from the rfork() clib function, then one of the processes > :> attempting to return will pop a bogus return address and seg fault. > : > :What's to stop the RFSTACK from copying the stack itself into the new stack > :that is located elsewhere in RAM and attached to the vm space? Actually, > :rfork() would just set it in the trap frame anyway, so there would be no > :extra user code to do this. > > Why make rfork() a thousand times slower when performance is almost > certainly an issue for the people using it? Since the one of the big > points of using rfork() the way we are using it is to avoid copying > pagetables, descriptor tables, and so forth, we sure don't want to > add any back in! It wouldn't be appreciably slower. The only difference would be when one provides RFSTACK and extra arg stackaddr, which would simplify things for the coder greatly! This would allow the old method to still work, so what's the problem? If anything, it would save _human_ time. > > > :> : Brian Feldman _ __ ___ ___ ___ > :> > : Brian Feldman _ __ ___ ___ ___ > > -Matt > Matthew Dillon > > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Reporting AMD processors (was: CPUT_WT_ALLOC_DISABLE)
On Mon, 22 Mar 1999, Greg Lehey wrote: > On Monday, 22 March 1999 at 0:54:12 +0000, Brian Feldman wrote: > > Does anyone want a CPU_WT_ALLOC_DISABLE and CPU_WT_ALLOC_ENABLE as > > separate > > options? I see a couple changes that should be made to the kernel now: > > > > CPU: AMD-K6(tm) 3D processor (300.69-MHz 586-class CPU) > > Origin = "AuthenticAMD" Id = 0x58c Stepping=12 > > Features=0x8021bf > > > > There should be another line, formatted the same, that ALWAYS reports > > CPU_WT_ALLOC info. This will help in debugging problems with certain > > hardware, > > because on K6-2's I get unreliability with write allocation on. For > > instance, > > I updated my BIOS lately and observed a crash. On boot -v, I noted that > > the BIOS was kind enough to turn on write allocation, but on a CPU that it > > doesn't seem to work well on. > > What's wrong with leaving the message in the -v output? After all, > it's debugging info. What's wrong is that this is info that should really be printed with the rest of the info. When people send PRs with the dmesg it will show what could possibly be wrong, and with this kind of change would show MORE of what could be wrong. > > > I propose an option to turn OFF write allocation instead of just one to > > turn > > it on. I also propose the change in CPU info printouts to (more correct > > spacing > > and extra line): > > > > CPU: AMD-K6(tm) 3D processor (300.69-MHz 586-like CPU) > > Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 > > Features = 0x8021bf > > Write Allocation: Disabled 15-16M Caching Enable: No > > > > The changes would be better spacing, a write allocation line (for whatever > > CPUs are supported, notably the K5, K6, K6-[23]), and changing "class" to > > the more sensible "like" (i.e. a K6 really is 686-class, but being socket 7 > > is 586-like). > > You'd better pass the spacing issue past bde. Certainly it mathes the > other messages. On the whole, I suppose this is reasonable info, but > I wonder if we're not tending towards too much information anyway. I > needed to increase the MSGBUF_SIZE on some machines just to get the > total content of a non-verbose boot. Yeah, I remember System 7's boot having about 1-3 lines, I don't recall exactly. But, having enough output is GOOD! Maybe MSGBUF_SIZE should be increased by default nowadays. > > Greg > -- > See complete headers for address, home page and phone numbers > finger g...@lemis.com for PGP public key > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
CPUT_WT_ALLOC_DISABLE
Does anyone want a CPU_WT_ALLOC_DISABLE and CPU_WT_ALLOC_ENABLE as separate options? I see a couple changes that should be made to the kernel now: CPU: AMD-K6(tm) 3D processor (300.69-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping=12 Features=0x8021bf There should be another line, formatted the same, that ALWAYS reports CPU_WT_ALLOC info. This will help in debugging problems with certain hardware, because on K6-2's I get unreliability with write allocation on. For instance, I updated my BIOS lately and observed a crash. On boot -v, I noted that the BIOS was kind enough to turn on write allocation, but on a CPU that it doesn't seem to work well on. I propose an option to turn OFF write allocation instead of just one to turn it on. I also propose the change in CPU info printouts to (more correct spacing and extra line): CPU: AMD-K6(tm) 3D processor (300.69-MHz 586-like CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 Features = 0x8021bf Write Allocation: Disabled 15-16M Caching Enable: No The changes would be better spacing, a write allocation line (for whatever CPUs are supported, notably the K5, K6, K6-[23]), and changing "class" to the more sensible "like" (i.e. a K6 really is 686-class, but being socket 7 is 586-like). Comments? Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: rfork()
On Sun, 21 Mar 1999, Matthew Dillon wrote: > :> If you are making a subroutine *call* to the rfork() routine, where > :> do you think the return PC address is stored? On the stack. The > :> rfork() routine is going to 'ret' *after* doing the rfork syscall. > :> 'ret' pops the stack. While this in itself is not modifying the > stack, > :> you can still wind up with the situation where process A returns from > :> the rfork and then does something else which overwrites the stack > before > :> process B has a chance to return from the rfork(). > : > :Why does it matter if something munges the stack in proc A though before > :proc B returns since proc B is going to immediately switch over to a new > :stack? > > The return address for the procedure call is on the stack. If something > munges the stack after the physical rfork occurs but before both processes > can return from the rfork() clib function, then one of the processes > attempting to return will pop a bogus return address and seg fault. What's to stop the RFSTACK from copying the stack itself into the new stack that is located elsewhere in RAM and attached to the vm space? Actually, rfork() would just set it in the trap frame anyway, so there would be no extra user code to do this. > > -Matt > Matthew Dillon > > > : Brian Feldman _ __ ___ ___ ___ > > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: rfork()
On Sun, 21 Mar 1999, Matthew Dillon wrote: > :> :the assembly wouldn't be needed. Hmm... actually... if one were to mmap() > a > :> :stack and as soon as the rfork() returned movl newstack,%esp and whatnot, > :> :wouldn't this be a pretty simple solution? > :> > :> No, because one of the processes may overrun the stack before the other > :> one managed to return from rfork(). The child process cannot use the > :> old stack at all. > : > :Why would a simple movl be using the stack? > > If you are making a subroutine *call* to the rfork() routine, where > do you think the return PC address is stored? On the stack. The > rfork() routine is going to 'ret' *after* doing the rfork syscall. > 'ret' pops the stack. While this in itself is not modifying the stack, > you can still wind up with the situation where process A returns from > the rfork and then does something else which overwrites the stack before > process B has a chance to return from the rfork(). Why does it matter if something munges the stack in proc A though before proc B returns since proc B is going to immediately switch over to a new stack? > > This is why, in my assembly example, I was forced to make the syscall > manually rather then call the rfork() library function. > > :> > : Brian Feldman _ __ ___ ___ ___ > > -Matt > > Matthew Dillon > > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: rfork()
On Sun, 21 Mar 1999, Matthew Dillon wrote:
> :Hence the NEW flag RFSTACK. Why would this be a bad thing? This would keep
> :the old behavior and allow much nicer new behavior. I didn't suggest
> :changing the old behavior. This would just greatly simplify things so all of
>
> I think Richard Seaman has it right: the stack needs to be passed.
>
> Why don't we simply implement the linux clone()? It sounds to me that
> it would be trivial.
Let's add another parameter to fork1/rfork():
pid_trfork __P((int, ...)); for userland
struct rfork_args { int flags; caddr_t extra; };
and in the kernel would be:
fork1(p1, flags)
register struct proc *p1;
int flags;
caddr_t extra;
{ foo
}
We, of course, have backward binary and code compatibility outside of the
kernel with the ellipses, and inside the kernel we control it anyway so we
can modify whatever needs to be changed.
>
> :the assembly wouldn't be needed. Hmm... actually... if one were to mmap() a
> :stack and as soon as the rfork() returned movl newstack,%esp and whatnot,
> :wouldn't this be a pretty simple solution?
>
> No, because one of the processes may overrun the stack before the other
> one managed to return from rfork(). The child process cannot use the
> old stack at all.
Why would a simple movl be using the stack?
>
> Matthew Dillon
>
>
>
>
> To Unsubscribe: send mail to majord...@freebsd.org
> with "unsubscribe freebsd-current" in the body of the message
>
Brian Feldman_ __ ___ ___ ___
gr...@unixhelp.org _ __ ___ | _ ) __| \
http://www.freebsd.org/ _ __ ___ | _ \__ \ |) |
FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Re: rfork()
On Sat, 20 Mar 1999, Matthew Dillon wrote: > > :> > rfork(RFMEM) doesn't easily work from C. You need to > :> > create an assembly stub. > :> > > :> > -- > :> > John | Never try to teach a pig to sing, > :> > dy...@iquest.net | it makes one look stupid > :> > jdy...@nc.com | and it irritates the pig. > :> > > :> > :> I've seen about 6 people ask about this because the manual lies about > :> what is done. I asked a while back about it, and John was kind enough > :> to dig up some code that used rfork to properly split the stack should > :> I try to dig it up? > :> > :> In the meantime, can someone commit this or suggest something? > : > :For the suggest something, you realize that with Richard's VM_STACK code it > :should be relatively trivial to make this automatic (suggestion: add > :RFSTACK flag). > : > : Brian Feldman _ __ ___ ___ ___ > : gr...@unixhelp.org_ __ ___ | _ ) __| \ > : http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | > : FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ > > If the goal is to completely share the address space, which > RFMEM does, you can't split anything, not even the stack. It > sure would be useful if there were a standard clib call adequate > for calling rfork() and calling a function in the child w/ a new > stack. Hence the NEW flag RFSTACK. Why would this be a bad thing? This would keep the old behavior and allow much nicer new behavior. I didn't suggest changing the old behavior. This would just greatly simplify things so all of the assembly wouldn't be needed. Hmm... actually... if one were to mmap() a stack and as soon as the rfork() returned movl newstack,%esp and whatnot, wouldn't this be a pretty simple solution? > > -Matt > Matthew Dillon > > > > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: rfork()
On Sun, 21 Mar 1999, Alfred Perlstein wrote: > On Sat, 20 Mar 1999, John S. Dyson wrote: > > > Michael E. Mercer said: > > > Hello, > > > > > > This was posted to freebsd-questions with no reply. > > > I tried this and the child process created a core file. > > > I also tried the other options and they seem to work. > > > Just RFPROC and RFMEM DON'T! > > > > > rfork(RFMEM) doesn't easily work from C. You need to > > create an assembly stub. > > > > -- > > John | Never try to teach a pig to sing, > > dy...@iquest.net | it makes one look stupid > > jdy...@nc.com | and it irritates the pig. > > > > I've seen about 6 people ask about this because the manual lies about > what is done. I asked a while back about it, and John was kind enough > to dig up some code that used rfork to properly split the stack should > I try to dig it up? > > In the meantime, can someone commit this or suggest something? For the suggest something, you realize that with Richard's VM_STACK code it should be relatively trivial to make this automatic (suggestion: add RFSTACK flag). > > thanks, > -Alfred > > Index: rfork.2 > === > RCS file: /home/ncvs/src/lib/libc/sys/rfork.2,v > retrieving revision 1.8 > diff -u -r1.8 rfork.2 > --- rfork.2 1999/01/26 02:38:09 1.8 > +++ rfork.2 1999/03/21 04:49:10 > @@ -54,7 +54,8 @@ > will then inherit all the shared segments the parent process owns. Other > segment > types will be unaffected. Subsequent forks by the parent will then > propagate the shared data and bss between children. The stack segment > -is always split. May be set only with > +is not split and must be allocated manually via an assembler subroutine. > +May be set only with > .Dv RFPROC . > .It RFSIGSHARE > If set, the kernel will force sharing the sigacts structure between the > > > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: fd broken [!!!]
Aye, and my LS-120 works great too :) So, que sera sera. Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ On Sat, 20 Mar 1999, Thomas Dean wrote: > I submitted a PR. > > This is not a show-stopper. I have a system running 2.2.7. fd works > on that one. So, I read/write floppies there. It is a pain, though. > > tomdean > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: fd broken [!!!]
It's been a couple more weeks, anyone now know why fd(4) is broken? It's really not a good thing :( Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ On Tue, 9 Mar 1999, Brian Feldman wrote: > On Sat, 6 Mar 1999, Thomas Dean wrote: > So Does anyone have an idea why the hell fd(4) broke?! > > > I have the same problem on 4.0-current SMP of Mon Feb 15 03:34:29 PST > > 1999. > > > > tomdean > > > > > > To Unsubscribe: send mail to majord...@freebsd.org > > with "unsubscribe freebsd-current" in the body of the message > > > > Brian Feldman _ __ ___ ___ ___ > gr...@unixhelp.org _ __ ___ | _ ) __| \ >http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | > FreeBSD: The Power to Serve!_ __ ___ _ |___/___/___/ > > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: How to add a new bootdevice to the new boot code ???
On Wed, 17 Mar 1999, S?ren Schmidt wrote: > It seems Robert Nordier wrote: > > OK, I'll add it to the bootblocks. > > > > Incidentally, while I'm in there and thinking about it, I'd quite > > like to fix the boot code to boot from LS-120 drives at the same > > time. So if anyone has one of these, and wouldn't mind spending > > some time running a few bits of test code, I'd appreciate it. > > I have a ZIP if that can help you ?? > > > > > However, I'd *still* expect it to pass a major# of 0 rather than > > > > 30. Why? Because a 2.0 kernel knows only 0. And if a 5.0 kernel > > > > knows only 30, it is -- at least -- in a position to know what > > > > 0 meant, and simply substitute one for the other (under the > > > > influence of a kernel configuration option, if necessary). > > > > > > Hmm, wd should give 0 and ad should give 30, no AI please :) > > > > I wasn't actually thinking at all along the lines of "smart" code > > at all: > > > > #ifdef FORCE_FOO > > if (foo == 0) > > foo = 30; > > #endif > > Well, that breaks somewhere else, as the mount code is clever enough > to look at the name of the driver in this case "ad" which doesn't > match the specified #0 ie "wd". > I kindof tried this by having my driver put itself in both the > wd & ad majors in the table, but that doesn't work, because the mount > stuff gets confused on the root name somehow, and fails to mount > root because the names dont match... > > > AFAICS, adopting the separate "wd" and "ad" route entails the > > following: > > > > Update your bootblocks. > > Add a /boot.config statement like "0:ad(0,a)" to make use > > of the driver the default. > > Failure to boot if you inadvertently specify wd out of habit, > > or if you specify ad when booting an earlier system. > > > > So we're introducing three points with good potential for failure. > > Well, what else can we do as long as we potentially need both > drivers in the kernel. I'm pretty sure that if I kill of wd.c > et all, there will be screams of bloody murder again... > been there done that :) Well, since the new ATA doesn't work with my LS-120 yet nor support DMA... ;) I want to see the LS-120 working, so where would I send it to if you were to work on its driver? :) > > > In contrast, the kernel configuration route requires commenting > > or uncommenting a single statement. > > But that doesn't work, at least as the mount code behaves now. > > At any rate, any solution that makes it possible to boot with > a new driver without me having to call it "wd" something all > over the place is acceptable to me... > > -S?ren > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Crash while newfs'ing innocent vinum volume on fresh system.
I don't know what frames 10-12 are supposed to be, but I can give you the short answer on why it crashed: you have INVARIANTS on (good!), so free()ing stuffs memory with 0xdeadc0de. Whatever frame 10 was doing tried to dereference previously freed memory. Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Simple DOS against 3.x locks box solid
On Mon, 15 Mar 1999, Dmitrij Tejblum wrote:
> Matthew Dillon wrote:
> >
> > We'll get a quick fix committed but the lockmgr stuff needs a real
> > going-over... having interrupts using the general lockmgr call is
> > a disaster waiting to happen.
>
> Hmmm. After I looked a bit further, it looks like a bug in the
> scheduler (?). Here is the stack trace:
>
> #9 0xc01ff64e in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = 0,
> tf_esi = 16777216, tf_ebp = -999002708, tf_isp = -999002744,
> tf_ebx = -1071228500, tf_edx = -2, tf_ecx = 0, tf_eax = 0,
> tf_trapno = 12, tf_err = 0, tf_eip = -1072584332, tf_cs = 8,
> tf_eflags = 66050, tf_esp = -999002524, tf_ss = -1071228500})
> at ../../i386/i386/trap.c:438
> #10 0xc011a974 in lockmgr (lkp=0xc02659ac, flags=1, interlkp=0x0, p=0x0)
> at ../../kern/kern_lock.c:217
> #11 0xc01d8c5b in vm_map_lookup (var_map=0xc4746e64, vaddr=3294351360,
> fault_typea=1 '\001', out_entry=0xc4746e68, object=0xc4746e5c,
> pindex=0xc4746e60, out_prot=0xc4746e4b "?\a", wired=0xc4746e44)
> at ../../vm/vm_map.c:2463
> #12 0xc01d4153 in vm_fault (map=0xc02659ac, vaddr=3294351360,
> fault_type=1 '\001', fault_flags=0) at ../../vm/vm_fault.c:197
> #13 0xc01ff9ac in trap_pfault (frame=0xc4746f18, usermode=0, eva=3294351360)
> at ../../i386/i386/trap.c:825
> #14 0xc01ff64e in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = 46137344,
> tf_esi = -1071149988, tf_ebp = -999002244, tf_isp = -999002304,
> tf_ebx = 18341888, tf_edx = -1000615936, tf_ecx = -1005747008,
> tf_eax = 0, tf_trapno = 12, tf_err = 0, tf_eip = -1071650796, tf_cs =
> 8,
> tf_eflags = 65606, tf_esp = -1072552121, tf_ss = -999654400})
> at ../../i386/i386/trap.c:438
> #15 0xc01fe814 in swtch_com ()
> #16 0xc01ff859 in trap (frame={tf_es = 47, tf_ds = 47, tf_edi = 20,
> tf_esi = 136019608, tf_ebp = -1077948228, tf_isp = -999002156,
> tf_ebx = 307, tf_edx = 136220264, tf_ecx = 136630944,
> tf_eax = 135716928, tf_trapno = 7, tf_err = 0, tf_eip = 134536416,
> tf_cs = 31, tf_eflags = 514, tf_esp = -1077948244, tf_ss = 47})
> at ../../i386/i386/trap.c:195
> #17 0xc01f5aa3 in swi_ast_user ()
>
> the trap in swtch_com() (frame #15) is here:
> /* switch address space */<- line 622
> movl%cr3,%ebx
> cmplPCB_CR3(%edx),%ebx<- trap
> je 4f
>
> I don't think this line is supposed to cause a trap...
When it says "switch address space" What exactly do you think it's going to
do? What I mean is, I'm pretty certain this is a good trap =)
The real problem did seem to be the NULL p dereference, as it was obvious
that it could happen in the code.
>
> Dima
>
>
>
>
> To Unsubscribe: send mail to majord...@freebsd.org
> with "unsubscribe freebsd-current" in the body of the message
>
Brian Feldman_ __ ___ ___ ___
gr...@unixhelp.org _ __ ___ | _ ) __| \
http://www.freebsd.org/ _ __ ___ | _ \__ \ |) |
FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Re: bmake/contrib framework for egcs
On Fri, 12 Mar 1999, David O'Brien wrote: > On Fri, Mar 12, 1999 at 02:29:27AM -0800, Jordan K. Hubbard wrote: > > > /foo/src/gnu/lib/libstdc++/../../../contrib/egcs/libio/gen-params > > > > I'd be very curious to see how gen-params is calling c++ and/or cpp in > > this case. > > + c++ -v -O -c dummy.C > Using builtin specs. > gcc version egcs-2.91.63 19990224 (egcs-1.1.2 pre-release-3) > /usr/libexec/cpp -lang-c++ -v -undef -D__GNUC__=2 -D__GNUG__=2 > -D__cplusplus -D__GNUC_MINOR__=91 -Di386 -Dunix -D__ELF__ -D__FreeBSD__=4 > -D__FreeBSD_cc_version=31 -D__i386__ -D__unix__ -D__ELF__ > -D__FreeBSD__=4 -D__FreeBSD_cc_version=31 -D__i386 -D__unix > -Asystem(unix) -Asystem(FreeBSD) -Acpu(i386) -Amachine(i386) > -D__EXCEPTIONS -D__OPTIMIZE__ -D__ELF__ dummy.C /var/tmp/ccO39xXH.ii > GNU CPP version egcs-2.91.63 19990224 (egcs-1.1.2 pre-release-3) (i386 > FreeBSD/ELF) > c++: Internal compiler error: program cpp got fatal signal 11 > + echo gen-params: could not compile dummy.C with c++ -v > gen-params: could not compile dummy.C with c++ -v > + exit 1 > *** Error code 1 > > > gdb on the resulting core file isn't leading me anywhere. > If I use a little X-cut-n-paste and run the `cpp' command manually, it > works fine and I get the expected output from `cpp'. Hmm environment variables? > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: panic: zone: entry not free
On Wed, 10 Mar 1999, Garrett Wollman wrote: > < said: > > > I have to concur. I've never understood the "don't worry be happy" > > point of view on this issue. > > Do you always compile and install all your programs with debugging > symbols? This is the DEVELOPMENT branch of the FreeBSD project, and you know that. > > -GAWollman > > -- > Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the > same > woll...@lcs.mit.edu | O Siem / The fires of freedom > Opinions not those of| Dance in the burning flame > MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: fd broken [!!!]
On Sat, 6 Mar 1999, Thomas Dean wrote: So Does anyone have an idea why the hell fd(4) broke?! > I have the same problem on 4.0-current SMP of Mon Feb 15 03:34:29 PST > 1999. > > tomdean > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: UPDATE3: ATA/ATAPI driver new version available.
On Sun, 7 Mar 1999, S?ren Schmidt wrote: > > Third update to the new ATA/ATAPI driver: > > ZIP drives should now be working, I'm not sure about LS120 drives, > reports on those most welcome! It doesn't lock up like before, but on my LS-120 wdc1: unit 0 (atapi): , removable, iordy it seems to have "corrupt" reads. In addition, much of the time the ATA code now will not boot my system, failing at atapi_transfer: bad command phase. > > Fixed problems: > > Hang on probe on "fantom" devices. > The probe now use a timeout to avoid hangs if no interrupt > is received. > > There has also been more general code clenaups, and some reorgs. > > As usual USE AT YOUR OWN RISK!!, this is still pre alpha level code. > > But please tell me how it works for you! > > Enjoy! > > -S?ren > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
fd broken
On Fri, 5 Mar 1999, Brian Feldman wrote: > It seems that actually, not through my own fault, the fd driver is broken. I > noticed this weeks ago but thought it a fluke since I only had the problem on > one computer. However, on the school FreeBSD box, I also notice the same > problem! The point is that previously, it had stopped working on my home box. Now, it also doesn't work on a different box that had been 3.0 before, and had fd working great. I have not made any modifications to the fd driver. > > fd0: recal failed ST0 70 cyl 0 > fd0: recal failed ST0 70 cyl 0 > fd0: recal failed ST0 70 cyl 0 > fd0: recal failed ST0 70 cyl 0 > fd0c: hard error reading fsbn 16 of 16-31 (No status) > fd0: recal failed ST0 70 cyl 0 > fd0: recal failed ST0 70 cyl 0 > fd0: recal failed ST0 70 cyl 0 > fd0: recal failed ST0 70 cyl 0 > fd0c: hard error reading fsbn 0 (No status) > fd0: recal failed ST0 70 cyl 0 > fd0: recal failed ST0 70 cyl 0 > fd0: recal failed ST0 70 cyl 0 > fd0: recal failed ST0 70 cyl 0 > fd0c: hard error reading fsbn 1 (No status) > > Hope someone knows :( I'll check the recent updates to the driver and see if > one of them is at fault. None of them look like they could be at fault, at least easily. Can someone try using your floppy drive with the latest sources? It doesn't work in two 4.0 machines which have absolutely nothing in common except being 586en. > > Brian Feldman _ __ ___ ___ ___ > gr...@unixhelp.org _ __ ___ | _ ) __| \ >http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | > FreeBSD: The Power to Serve!_ __ ___ _ |___/___/___/ > > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
