Re: Today's kernel crashes on starting X
In message pine.bsf.3.95.990514121818.24898a-100...@current1.whistle.com, Julian Elischer writes: On Fri, 14 May 1999, Luoqi Chen wrote: This was due to a kludge in mfs implementation. Try change NUMCDEV in kern_conf.c to 255. Are you saying that there is a bug in the mfs implementation and a fix will be commited soon? (and change NUMCDEV until then) Or are you saying, the mfs implementation is now considered correct (but there are some kludges in there) and that changing NUMCDEV in kern_conf.c to 255 is the perminate fix? -- -- David(obr...@nuxi.com -or- obr...@freebsd.org) This is a fundamental problem with mfs' design, mfs steals bdev major 255 for its private use. One thing we could do is to have mfs legally acquire this major number, i.e., setup a devsw structure and register with device conf system. This problem probably would go away after we have a fully functional DEVFS. Actually this problem is the one that makes DEVFS explode.. It does an alias lookup on it's 'dummy' vnode and since teh sytem has been switched to use devfs routines for everything, some of it's assumptions are not longer true.. I don't expect the current DEVFS prototype to be indicative of how our real DEVFS will work. -- 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
Re: cvs commit: src/sys/pci pcisupport.c
Tomoaki NISHIYAMA wrote: From: NAKAGAWA Yoshihisa y-nak...@nwsl.mesh.ad.jp y-nakaga You bought a computer with the super-ultra-new Microsoft (tm) y-nakaga Microsoft Bus (tm), for which you bought the latest and greatest y-nakaga device X. y-nakaga y-nakaga It is extremely vulgar joke. I doubt your character. No, I don't think this is a joke, but a serious situation. We should stick on technical problem if we continue to discuss. I replied to this in private, but, for the record, it was not a joke. -- Daniel C. Sobral(8-DCS) d...@newsguy.com d...@freebsd.org Proof of Trotsky's farsightedness is that _none_ of his predictions have come true yet. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
ftp.nz.freebsd.org
Hi, CLEAR is operating a pretty full mirror of ftp.freebsd.org:/pub/FreeBSD/ at ftp.clear.net.nz:/pub/FreeBSD/. Dan Langille has kindly made ftp.nz.freebsd.org a CNAME to ftp.clear.net.nz to make this easier to find. Just thought I'd mention it -- I haven't done a clean install for a long time, so I don't know whether ftp.nz.freebsd.org is given explicitly as an option for network installs. But if it isn't, it might be good to put it in. Joe To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Skip fail under current, was: Re: VPN betwwen Windows 9x Clients and FreeBSD Firewall
On Tue, 27 Apr 1999, Bob Fayne wrote:
At 05:40 PM 4/27/99, you wrote:
I am looking for a firewall/VPN solution that will allow our company
personnel to connect to the corporate network using there Win95 laptops and
a Dynamic IP address from there ISP, when they are out traveling or working
from home.
Try the SKIP port.
http://skip.incog.com. The 40-bit Win95 client is free, and 56/128 clients
are available from Sun.
It won't compile under current.
freebsd/skip_es.c breaks at
if (suser(p-p_ucred, p-p_acflag )) {
This won't compile, because suser only has one parameter.
Trying blindly to change it to:
if (suser(p-p_ucred)) {
Makes it compile (it has lots of warnings though), but gives a panic when
trying to load skip.ko
Leif Neland
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Re: Skip fail under current, was: Re: VPN betwwen Windows 9x Clients and FreeBSD Firewall
In message pine.bsf.4.05.9905151255160.5798-100...@arnold.neland.dk, Leif Nel
and writes:
It won't compile under current.
freebsd/skip_es.c breaks at
if (suser(p-p_ucred, p-p_acflag )) {
This won't compile, because suser only has one parameter.
Trying blindly to change it to:
if (suser(p-p_ucred)) {
Better yet, read the manpage for suser(9) and change it to:
if (suser(p)) {
--
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
Re: /usr/src/release/Makefile patch
Could you please consider the following patch to
/usr/src/release/Makefile? It may not be entirely correct,
but it allows a 'cd /usr/src/release make release' to
run to completion. In the kernel makefile, 'kernel'
is not a target, ${KERNEL} is, and ${KERNEL} has the value
'GENERIC'.
Sorry, I was swamped with 3.2 stuff. Done!
- Jordan
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
screen panics -current
Well, this is just a quick note to anyone more knowledgable than me. screen 3.7.6 panics a current kernel. -- [gjvc] We're not laughing at you; we're laughing with you. But I'm not laughing. 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: cvs commit: src/sys/pci pcisupport.c
On Sat, 15 May 1999, Daniel C. Sobral wrote: Tomoaki NISHIYAMA wrote: From: NAKAGAWA Yoshihisa y-nak...@nwsl.mesh.ad.jp y-nakaga You bought a computer with the super-ultra-new Microsoft (tm) y-nakaga Microsoft Bus (tm), for which you bought the latest and greatest y-nakaga device X. y-nakaga y-nakaga It is extremely vulgar joke. I doubt your character. No, I don't think this is a joke, but a serious situation. We should stick on technical problem if we continue to discuss. I replied to this in private, but, for the record, it was not a joke. I understand it wasn't a joke, but it *was* funny, and he wasn't abusing things. I don't think it's too fair to jump on him over it (you didn't, Daniel). A little humor is allowed, as long as things are kept in proportion, right? Enough. +--- Chuck Robey | Interests include any kind of voice or data chu...@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). +--- 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
It seems Brian Feldman wrote: 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! Well, thanks for all the flowers, positive feedback like that is what makes this project rolling you know... I've finally got my hands on a LS120 drive yesterday (boy those are rare here) but I havn't had time to hook it up yet though, so there is hope :) And I'll even promise you a dump routine, just not how soon I'll be able to do it, time is sparse currently... -Søren To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Alladdin IDE slow?
It seems Kenneth Wayne Culver wrote: Hmm, this sounds stange, I have a noard here with the Alladin on it on which I did the support for the ata driver, it works just fine for me at least... Actually, I am having the same sort of problem.. With all the flags set properly in the wd driver, I get about 11MBps, with ata, I can only get about 6. Hmm, I get: test# dd if=/dev/rad2 of=/dev/null bs=1m count=100 100+0 records in 100+0 records out 104857600 bytes transferred in 7.936770 secs (13211621 bytes/sec) On this: chip0: AcerLabs M1541 (Aladdin-V) PCI host bridge at device 0.0 on pci0 pcib1: AcerLabs M5243 PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 chip1: AcerLabs M15x3 Power Management Unit at device 3.0 on pci0 isab0: AcerLabs M1533 portable PCI-ISA bridge at device 7.0 on pci0 vga-pci0: S3 ViRGE DX/GX graphics accelerator irq 10 at device 10.0 on pci0 ata-pci0: AcerLabs Aladdin IDE controller irq 0 at device 15.0 on pci0 ta-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 ata0: master: settting up WDMA2 mode on Aladdin chip OK ad0: QUANTUM FIREBALL_TM3840A/A6B.1T00 ATA-? disk at ata0 as master ad0: 3681MB (7539840 sectors), 7480 cyls, 16 heads, 63 S/T, 512 B/S ad0: piomode=4, dmamode=2, udmamode=-1 ad0: 16 secs/int, 0 depth queue, DMA mode ata1: master: settting up UDMA2 mode on Aladdin chip OK ad2: IBM-DTTA-371010/T77OA73A ATA-4 disk at ata1 as master ad2: 9641MB (19746720 sectors), 19590 cyls, 16 heads, 63 S/T, 512 B/S ad2: piomode=4, dmamode=2, udmamode=2 ad2: 16 secs/int, 31 depth queue, DMA mode -Søren To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: de driver problem
As Doug Rabson wrote ... On Mon, 10 May 1999, Wilko Bulte wrote: Yeah. That must be why my 164lx won't netboot. Could well be. My Aspen Alpine refused to with a DE500. A DE435 (10mbit only) worked just dandy. That reminds me. Does your Alpine still work after the new-bus stuff? I wasn't sure I hadn't broken it when I changed the apecs driver. After a buildworld of yesterday's -current and a new kernel things work just fine. As an added bonus the serial console seems to work better. It used to be very slow, looks like that is gone. If you want more info you'll have to wait a bit, I'll be offline for a week. Wilko | / o / / _ Arnhem, The Netherlands- Powered by FreeBSD - |/|/ / / /( (_) BulteWWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: cvs commit: src/sys/pci pcisupport.c
On Thu, 13 May 1999 10:41:23 +0100 (BST), Doug Rabson d...@nlsystems.com said: As I suspected, a massive flamewar has happened while I've been away. I don't think I have anything to add to what has been said (and I certainly don't want to continue a flamewar). Can people please just drop the subject until after Usenix. This kind of flamewar is too upsetting (to me anyway) and just makes it harder to have a useful face-to-face discussion. As I said earlier, I agree with you. About human factor, I think face to face communication is best way to solve problem. But about technical issues, I'd like to reply in public place, because both the message from Julian (*1) and the message from Daniel (*2) showed typical misunderstanding about newconfig. The goal they showed is also the goal of the dynamic configuration of newconfig from the beggining. I'd like to show how it will be achieved by newconifg. Could you permit me to answer technical issues in -hackers as Daniel adviced ? Or, -current is better about the questions which is posted to -current ? Other possibility is newconfig mailig list (anyone can subscribe it and it's archive can be accessed from WWW), or postponement until after Usenix. How do you think? (*1) Date: Wed, 12 May 1999 17:08:10 -0700 (PDT) From: Julian Elischer jul...@whistle.com Subject: Re: cvs commit: src/sys/pci pcisupport.c Message-ID: pine.bsf.3.95.990512165327.22596i-100...@current1.whistle.com (*2) From: Daniel C. Sobral d...@newsguy.com Subject: Re: cvs commit: src/sys/pci pcisupport.c Date: Fri, 14 May 1999 20:46:05 +0900 Message-ID: 373c0cfd.7d9d3...@newsguy.com -- soda To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: de driver problem
On Sat, 15 May 1999, Wilko Bulte wrote: As Doug Rabson wrote ... On Mon, 10 May 1999, Wilko Bulte wrote: Yeah. That must be why my 164lx won't netboot. Could well be. My Aspen Alpine refused to with a DE500. A DE435 (10mbit only) worked just dandy. That reminds me. Does your Alpine still work after the new-bus stuff? I wasn't sure I hadn't broken it when I changed the apecs driver. After a buildworld of yesterday's -current and a new kernel things work just fine. As an added bonus the serial console seems to work better. It used to be very slow, looks like that is gone. If you want more info you'll have to wait a bit, I'll be offline for a week. Thats good. The slow serial sounds like it used to be polling (i.e. sio interrupts weren't getting through). -- 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
Re: cvs commit: src/sys/pci pcisupport.c
On Sat, 15 May 1999, Noriyuki Soda wrote: On Thu, 13 May 1999 10:41:23 +0100 (BST), Doug Rabson d...@nlsystems.com said: As I suspected, a massive flamewar has happened while I've been away. I don't think I have anything to add to what has been said (and I certainly don't want to continue a flamewar). Can people please just drop the subject until after Usenix. This kind of flamewar is too upsetting (to me anyway) and just makes it harder to have a useful face-to-face discussion. As I said earlier, I agree with you. About human factor, I think face to face communication is best way to solve problem. But about technical issues, I'd like to reply in public place, because both the message from Julian (*1) and the message from Daniel (*2) showed typical misunderstanding about newconfig. The goal they showed is also the goal of the dynamic configuration of newconfig from the beggining. I'd like to show how it will be achieved by newconifg. Could you permit me to answer technical issues in -hackers as Daniel adviced ? Or, -current is better about the questions which is posted to -current ? Other possibility is newconfig mailig list (anyone can subscribe it and it's archive can be accessed from WWW), or postponement until after Usenix. I would like to postpone until after Usenix. I'm sure that we will be able to sort out any technical misunderstandings there which will make it possible to have a reasonable public discussion. -- 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
Re: screen panics -current
Well, this is just a quick note to anyone more knowledgable than me. screen 3.7.6 panics a current kernel. -- [gjvc] We're not laughing at you; we're laughing with you. But I'm not laughing. I committed a fix yesterday afternoon, could you cvsup and try again? -lq To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
PR 10570 - patch
I sent in a patch to PR 10570 a couple days ago, after quite a bit of testing (and catching up on email while changing countries..) So, if someone wants to commit the patch.. Thanks (and it took too long, i know..) adrian -- Adrian Chadd adr...@freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: screen panics -current
On Sat, May 15, 1999 at 11:55:42AM +, George Cox wrote: # Well, this is just a quick note to anyone more knowledgable than me. # # screen 3.7.6 panics a current kernel. to add a little bit: when the kernel has SMP enabled. at least here, checked 3 machines. -- -mishania To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: cvs commit: src/sys/pci pcisupport.c
On Sat, 15 May 1999 15:58:01 +0100 (BST), Doug Rabson d...@nlsystems.com said: I would like to postpone until after Usenix. I'm sure that we will be able to sort out any technical misunderstandings there which will make it possible to have a reasonable public discussion. OK, I'll postpone, then. Julian, Daniel, and other folks, is this OK for you? If you'd like to hear the answer now, please request us that we should reply to your question. We'll reply to you in newconfig mailing list (i.e. To: you, Cc: newconfig) to avoid useless flame war. Note that the newconfig mailing list is truly open, anyone who is interested in newconfig approach can access the answer. The address of mailing list: newcon...@jp.freebsd.org The official WWW page: http://www.jp.freebsd.org/newconfig/ The way to subscribe (majordomo): http://www.jp.freebsd.org/newconfig/ml.html The mail archive of newconfig: http://home.jp.freebsd.org/mail-list/newconfig/ The mail archive of newconfig-jp (written in Japanese): http://home.jp.freebsd.org/mail-list/newconfig-jp/index.html.ja.jis (The traffic of newconfig mailing list is not much, because main discussion is currently done in newconfig-jp.) And, Dainel, I'm very sorry that one of us called your serious question joke. I know your question is serious, because what you said is also the goal for me from the beginning of dynamic configuration of newconfig. Perhaps we should answer to you in newconfig mailing list (To: you, cc: newconfig). Is this OK for you? We have answer which satisfy your requirement. -- soda To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
[Fwd: Re: Anybody actually using gigabit ethernet?]
Josef Karthauser wrote: Couldn't it read: tcp_extensions=NO # Switch RFC1323 extensions on? How about: tcp_extensions=NO # Set to Yes to turn on RFC1323 extensions That would match existing style and be a lot more clear. I can submit a PR if anyone thinks that's really necessary... Doug To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Different SCSI probe behavior
This morning, I did an installworld and booted a new -current world and -current kernel (Sources from morning of Fri May 14th). I got the following messages during the SCSI probe: Waiting 10 seconds for SCSI devices to settle aha0: ahafetchtransinfo - Inquire Setup Info Failed (probe20:aha0:0:5:0): CCB 0xc553b450 - timed out (probe20:aha0:0:5:0): CCB 0xc553b450 - timed out aha0: No longer in timeout I'm not sure what to make of this. After a bit of a delay - 30 or so seconds, I don't quite recall how long - the system continued booting, normally the rest of the way, and seems to be functional. Do I need to update something for normal behavior? I've been following freebsd-current and cvs-all, though I might have missed something that would have clued me in. Here are my controllers: ahc0: Adaptec 274X SCSI host adapter at slot 4 on eisa0 ahc0: aic7770 = Rev E, Wide Channel A, SCSI Id=7, 4/255 SCBs aha0 at ports 0x130-0x133 and 0x131-0x134 irq 11 drq 7 on isa0 aha0: AHA-1542C FW Rev. 0.1 (ID=44) SCSI Host Adapter, SCSI ID 7, 16 CCBs Here is my disk information: da3 at ahc0 bus 0 target 4 lun 0 da3: CONNER CFP1060W 1.05GB 2035 Fixed Direct Access SCSI-2 device da3: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled da3: 1013MB (2074880 512 byte sectors: 64H 32S/T 1013C) da1 at ahc0 bus 0 target 3 lun 0 da1: SEAGATE ST410800N 7110 Fixed Direct Access SCSI-2 device da1: 10.000MB/s transfers (10.000MHz, offset 15) da1: 8347MB (17096357 512 byte sectors: 255H 63S/T 1064C) da4 at ahc0 bus 0 target 5 lun 0 da4: CONNER CFP1060W 1.05GB 2035 Fixed Direct Access SCSI-2 device da4: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled da4: 1013MB (2074880 512 byte sectors: 64H 32S/T 1013C) da5 at ahc0 bus 0 target 6 lun 0 da5: CONNER CFP1060W 1.05GB 2035 Fixed Direct Access SCSI-2 device da5: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled da5: 1013MB (2074880 512 byte sectors: 64H 32S/T 1013C) cda0 at aha0 bus 0 target 0 lun 0 da0: FUJITSU M2624F-512 0405 Fixed Direct Access SCSI-2 device da0: 3.333MB/s transfers (3.333MHz, offset 8) da0: 496MB (1015812 512 byte sectors: 64H 32S/T 496C) cd0 at aha0 bus 0 target 5 lun 0 cd0: TOSHIBA CD-ROM XM-3401TA 0283 Removable CD-ROM SCSI-2 device cd0: 3.300MB/s transfers cd0: cd present [261564 x 2048 byte records] da2 at aha0 bus 0 target 2 lun 0 da2: HP C2257 0BC4 Fixed Direct Access SCSI-2 device da2: 3.300MB/s transfers da2: 1910MB (3912172 512 byte sectors: 64H 32S/T 1910C) hanging root device to da0s1a cd9660: Joliet Extension To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Different SCSI probe behavior
On Sat, 15 May 1999, Bret A. Ford wrote: Waiting 10 seconds for SCSI devices to settle aha0: ahafetchtransinfo - Inquire Setup Info Failed (probe20:aha0:0:5:0): CCB 0xc553b450 - timed out (probe20:aha0:0:5:0): CCB 0xc553b450 - timed out aha0: No longer in timeout I'm seeing the same thing, but for 3 of my devices on a chain with 4 devices. It takes quite long, but doesn't appear to do any damage or decrease functionality (so far that is). Do I need to update something for normal behavior? I've been following freebsd-current and cvs-all, though I might have missed something that would have clued me in. I've seen Werner Losch discovering a problem with the aha driver in -stable, and he committed a fix for that. Is it possible for that fix to be MFS ? --- Khetan Gajjar (!kg1779) * khe...@iafrica.com ; khe...@os.org.za http://www.os.org.za/~khetan * Talk/Finger khe...@chain.freebsd.os.org.za FreeBSD enthusiast* http://www2.za.freebsd.org/ Security-wise, NT is a OS with a kick me sign taped to it To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Nt source licenses...
On Fri, 14 May 1999, Garance A Drosehn wrote: At 3:51 PM +0700 5/12/99, Ustimenko Semen wrote: Are we going to get this license? I am interested in NTFS source code a lot... I would be very careful about getting an NT source license if your intention is to write NTFS support for some other operating system. Microsoft is not doing this licensing for the benefit of mankind, they are doing it to attract college-type users to sticking with WinNT over open-source unixes. The last thing we need is some code from WinNT which causes us to be sued by Microsoft... It would probably be very unwise for the project to get get the licence. However, considering that we support loadable filesystem modules, somebody adventurous enough can get the licence and write a (separate distributed, possibly even only as binary) module. Downloading a kld module from the net definately does not taint your mind. --- Garance Alistair Drosehn = g...@eclipse.acs.rpi.edu Senior Systems Programmer(MIME NeXTmail capable) Rensselaer Polytechnic Institute; Troy NYUSA Sander There is no love, no good, no happiness and no future - all these are just illusions. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
``65536-byte tape record bigger than suplied buffer''
Fyi, With today's -current, while trying to restore some files from a recent (about 3 days ago) dump, I'm seeing: /kernel: (sa0:ahc0:0:3:0): 65536-byte tape record bigger than suplied buffer Oh, and mounting swap /tmp mfs rw,nosuid,nodev,-s=32768 0 0 panics the system with a double fault in mount_mfs, but that's another matter. -- Jos Backus _/ _/_/_/ Reliability means never _/ _/ _/ having to say you're sorry. _/ _/_/_/ -- D. J. Bernstein _/ _/ _/_/ jos.bac...@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: ``65536-byte tape record bigger than suplied buffer''
Fyi, With today's -current, while trying to restore some files from a recent (about 3 days ago) dump, I'm seeing: /kernel: (sa0:ahc0:0:3:0): 65536-byte tape record bigger than suplied buffer This is because a bug was fixed that actually now correctly reports the problem. You've made this tape with a 64KB record. You need to give an argument to recover that understands this. Oh, and mounting swap /tmp mfs rw,nosuid,nodev,-s=32768 0 0 panics the system with a double fault in mount_mfs, but that's another matter. I'll say, and I haven't seen that one and I use mfs all the time! To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
No sound (Ensoniq Audio PCI 1370)
Dear people, I get no sound anymore using the system built on Friday. As I saw same earlier reports here about problems with sound that were reported to be fixed, mine might be related to the card being a PCI one - ES1370 based genuine Ensoniq Audio PCI. Below follow dmesg output and kernel configuration. Regards, Marc P.S. Should something like this go into a pr? --- Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #1: Fri May 14 22:01:21 CEST 1999 m...@oranje.my.domain:/usr/src/sys/compile/ORANJE Calibrating clock(s) ... TSC clock: 300727714 Hz, i8254 clock: 1193364 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter i8254 frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method Timecounter TSC frequency 300684204 Hz CPU: AMD-K6tm w/ multimedia extensions (300.68-MHz 586-class CPU) Origin = AuthenticAMD Id = 0x570 Stepping=0 Features=0x8001bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,MMX Data TLB: 128 entries, 2-way associative Instruction TLB: 64 entries, 1-way associative L1 data cache: 32 kbytes, 32 bytes/line, 2 lines/tag, 2-way associative L1 instruction cache: 32 kbytes, 32 bytes/line, 2 lines/tag, 2-way associative Write Allocate Enable Limit: 192M bytes Write Allocate 15-16M bytes: Enable Hardware Write Allocate Control: Disable real memory = 201326592 (196608K bytes) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x002da000 - 0x0bff5fff, 198295552 bytes (48412 pages) sio0: system console avail memory = 193077248 (188552K bytes) Found BIOS32 Service Directory header at 0xc00faf50 Entry = 0xfb410 (0xc00fb410) Rev = 0 Len = 1 PCI BIOS entry at 0xb440 DMI header at 0xc00f5bb0 Version 2.0 Table at 0xf0800, 28 entries, 613 bytes Other BIOS signatures found: ACPI: $PnP: 000fbfb0 Preloaded elf kernel kernel at 0xc02c1000. VESA: information block 56 45 53 41 00 03 00 01 00 01 01 00 00 00 22 00 00 01 40 00 01 62 07 01 00 01 0e 01 00 01 21 01 00 01 00 01 01 01 02 01 03 01 04 01 05 01 06 01 07 01 08 01 09 01 0a 01 0b 01 0c 01 0e 01 0f 01 VESA: 48 mode(s) found Initializing PnP override table Probing for PnP devices: Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 No Plug-n-Play devices were found pci_open(1):mode 1 addr port (0x0cf8) is 0x8000ff08 pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=55971039) npx0: math processor on motherboard npx0: INT 16 interface i586_bzero() bandwidth = 58186896 bytes/sec bzero() bandwidth = 58349865 bytes/sec pcib0: PCI host bus adapter on motherboard found- vendor=0x1039, dev=0x5597, revid=0x02 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 found- vendor=0x1039, dev=0x0008, revid=0x01 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0secondarybus=0 found- vendor=0x1039, dev=0x5513, revid=0xd0 class=01-01-8a, hdrtype=0x00, mfdev=1 subordinatebus=0secondarybus=0 intpin=a, irq=0 map[0]: type 4, range 32, base 01f0, size 3 map[1]: type 4, range 32, base 03f4, size 2 map[2]: type 4, range 32, base 0170, size 3 map[3]: type 4, range 32, base 0374, size 2 map[4]: type 4, range 32, base 4000, size 4 found- vendor=0x1000, dev=0x0001, revid=0x02 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=a, irq=15 map[0]: type 4, range 32, base 6300, size 8 map[1]: type 1, range 32, base e2001000, size 8 found- vendor=0x1274, dev=0x5000, revid=0x00 class=04-01-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=a, irq=11 map[0]: type 4, range 32, base 6400, size 6 found- vendor=0x12d2, dev=0x0018, revid=0x10 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=a, irq=10 map[0]: type 1, range 32, base e000, size 24 map[1]: type 3, range 32, base e100, size 24 pci0: PCI bus on pcib0 i4b_pci_probe: unknown PCI type 1435963449l! chip0: Host to PCI bridge (vendor=1039 device=5597) at device 0.0 on
Re: ``65536-byte tape record bigger than suplied buffer''
On Sat, May 15, 1999 at 12:50:10PM -0700, Matthew Jacob wrote: You've made this tape with a 64KB record. You need to give an argument to recover that understands this. Ahh ``-b 64'', I recall the discussion with Wilko Bulte a few days ago now. Sorry for the false alert :-/ panics the system with a double fault in mount_mfs, but that's another matter. I'll say, and I haven't seen that one and I use mfs all the time! Strange. It's quite repeatable with a make world and kernel of 3 hours ago. I've commented out the fstab entry for now. Maybe I should get a ddb trace... Thanks, -- Jos Backus _/ _/_/_/ Reliability means never _/ _/ _/ having to say you're sorry. _/ _/_/_/ -- D. J. Bernstein _/ _/ _/_/ jos.bac...@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: ``65536-byte tape record bigger than suplied buffer''
On Sat, May 15, 1999 at 12:50:10PM -0700, Matthew Jacob wrote: You've made this tape with a 64KB record. You need to give an argument to recover that understands this. Ahh ``-b 64'', I recall the discussion with Wilko Bulte a few days ago now. Sorry for the false alert :-/ Let me know how it goes... panics the system with a double fault in mount_mfs, but that's another matter. I'll say, and I haven't seen that one and I use mfs all the time! Strange. It's quite repeatable with a make world and kernel of 3 hours ago. I've commented out the fstab entry for now. Maybe I should get a ddb trace... Well, I'll recheck mine... To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: ``65536-byte tape record bigger than suplied buffer''
On Sat, May 15, 1999 at 01:13:27PM -0700, Matthew Jacob wrote: Let me know how it goes... Quite well, thank you :) jos:/home/jos# restore -ivb 64 Verify tape and initialize maps Dump date: Wed May 12 23:36:39 1999 Dumped from: the epoch Level 0 dump of / on jos.bugworks.com:/dev/da2s1a Label: none Extract directories from tape Initialize symbol table. restore ls .: 2 ./ 6028 cdrom/ 384 home@ 16 root/ 2 ../ 34 compat@ 1018 kernel 6045 sbin/ 6124 .kde/ 3 dev/ 181 kernel.ok 4 stand/ 241 .profile 14 dist/ 1027 kernel.old 1022 sys@ 408 COPYRIGHT 6046 dos/6030 mnt/ 31 tmp/ 6029 bin/6019 etc/6047 modules/6016 usr/ 32 boot/ 6059 floppy/ 13 proc/ 6017 var/ restore quit jos:/home/jos# Well, I'll recheck mine... It'd be interesting to see if you (and others) can reproduce this too. -- Jos Backus _/ _/_/_/ Reliability means never _/ _/ _/ having to say you're sorry. _/ _/_/_/ -- D. J. Bernstein _/ _/ _/_/ jos.bac...@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: screen panics -current
On Sat, 15 May 1999, Mikhail A. Sokolov wrote: On Sat, May 15, 1999 at 11:55:42AM +, George Cox wrote: # Well, this is just a quick note to anyone more knowledgable than me. # # screen 3.7.6 panics a current kernel. to add a little bit: when the kernel has SMP enabled. at least here, checked 3 machines. Louqi patched it yesterday evening, try re-cvsup. -Alfred thanks Louqi! To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Nt source licenses...
On Sat, 15 May 1999, Narvi wrote: On Fri, 14 May 1999, Garance A Drosehn wrote: At 3:51 PM +0700 5/12/99, Ustimenko Semen wrote: Are we going to get this license? I am interested in NTFS source code a lot... I would be very careful about getting an NT source license if your intention is to write NTFS support for some other operating system. Microsoft is not doing this licensing for the benefit of mankind, they are doing it to attract college-type users to sticking with WinNT over open-source unixes. The last thing we need is some code from WinNT which causes us to be sued by Microsoft... It would probably be very unwise for the project to get get the licence. However, considering that we support loadable filesystem modules, somebody adventurous enough can get the licence and write a (separate distributed, possibly even only as binary) module. Downloading a kld module from the net definately does not taint your mind. I'm unsure what the fuss is over, don't we have a kld to read NTFS already? Is there really anything special about NT that we NEED to learn that hasn't been done _better_ by Sun, SGI or Digital? :) -Alfred To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: stable snap for smp?
On Fri, 14 May 1999 19:34:43 CDT, Anthony Kimball wrote: If anyone has applied reasonable stress to a recent MP kernel, preferrably with X, VESA, VM86, and found it stable, do please report on your last cvs update time: I, for one, would very much like to isolate a fairly stable post-newbus world. Presumably this would be helpful to other readers as well, it being so much easier to bounce between worlds which are more nearly contemporaneous. I've been running 3.1-STABLE cvsup-ed on Sat May 8 at about 3:30am or thereabouts. It always starts up xdm, and my desktop is KDE, I use exmh and Netscape daily, used doscmd a couple of days ago to burn some EPROMs, used gimp and sane to scan and edit some photos, just completed a buildworld with -j4 of 3.2-STABLE, and always run setiathome (new version 1.1 just released). The system is a dual PII/300, 256Mb RAM, and 256Mb swap across two UW-SCSI disks. The only IDE peripheral is a CD-ROM, and it's still using the old acd/ATAPI driver. Soundblaster AWE64 card works just fine with Luigi's drivers. The only thing I don't have in the kernel is VESA as the machine always fires up xdm. I have the DDB code in as well INVARIANTS turned on. Nothing is dynamically loaded - I always build a custom kernel with everything I need in it to ease debugging and to be sure no module is out-of-date. (I used to be running 4.0-CURRENT but hit the already-mentioned strange lockup with no debug, no dump, and no clue. I had to get some pay-for work done so I backed up to 3.1-STABLE and it seems to be fine since.) Hope this helps. I intend to update to 3.2-STABLE today... -- Parag Patel To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: make world croaks in perl ??
Make buildworld fails here with: ===/gnu/usr.bin/perl/perl find: build: No such file or directory find: build: No such file or directory mkdir: lib/auto: File exists *** Error code 1 Stop. Thordur Ivarsson To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Skip fail under current, was: Re: VPN betwwen Windows 9x Clients and FreeBSD Firewall
Poul-Henning Kamp writes:
It won't compile under current.
freebsd/skip_es.c breaks at
if (suser(p-p_ucred, p-p_acflag )) {
This won't compile, because suser only has one parameter.
Trying blindly to change it to:
if (suser(p-p_ucred)) {
Better yet, read the manpage for suser(9) and change it to:
if (suser(p)) {
Thanks for noticing this. I'll fix it as soon as the ports freeze is over.
For the sake of 3.x systems, I'll change it to this..
#if __FreeBSD_version 45
if (suser(p-p_ucred, p-p_acflag )) {
#else
if (suser(p)) {
#endif
return (EPERM);
}
Poul, thanks for bumping __FreeBSD_version when the suser() changes
went through :-)
-Archie
___
Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Re: Nt source licenses...
It would probably be very unwise for the project to get get the licence. However, considering that we support loadable filesystem modules, somebody adventurous enough can get the licence and write a (separate distributed, possibly even only as binary) module. Downloading a kld module from the net definately does not taint your mind. How has linux come up with thier NTFS support?? JOHN To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: cvs commit: src/sys/pci pcisupport.c
I replied to this in private, but, for the record, it was not a joke. Ok, I see your say. I feel inadequate metaphor and provocation form, so that message seemed vulgar joke. New-bus's goal is meaningful, but not only that one. Also newconfig is same. Difference between these is realization way. But I don't reply that message, I must become to cool. Probably other member of newconfig will reply. I keep quiet in a while. #I'm busy recently, and shocked by suddenly new-bus merge #happening (I think, its process is not fair). I was lost my head. #Also, one of stress cause is language barrier. English is hard #for me. It is my weak point. -- NAKAGAWA, Yoshihisa y-nak...@nwsl.mesh.ad.jp nakag...@jp.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: -current page fault at 0xdeadc0de
I had two systems reboot at nearly the same time. (30 seconds apart), and
are completely unrelated.
These both look like stack damage, actually.
One system was running 2.2.8, and my core file presents me with this:
su-2.02# gdb -k
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.
(kgdb) exec-file kernel.0
(kgdb) symbol-file kernel.0.debug
Reading symbols from kernel.0.debug...done.
(kgdb) core-file vmcore.0
IdlePTD 24a000
current pcb at 202bfc
#0 0x14 in ?? ()
(kgdb) bt
#0 0x14 in ?? ()
#1 0x3404 in ?? ()
Cannot access memory at address 0x7205c76a.
Were things just trashed, or am I doing something wrong?
Looks like a return from a function that's destroyed the stack.
The other system was running -current, and gives me:
...
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0xdeadc0de
fault code = supervisor read, page not present
instruction pointer = 0x8:0xdeadc0de
Jump through vector in freed memory; someone has freed a region of
memory and is still using it, or has freed a region of memory that was
never obtained by malloc.
panic: page fault
syncing disks...
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0xdeadc126
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc018e3d8
Whoops. You need DDB to track this; you're only going to get the trace
for the second fault with gdb, which won't be at all illuminating I
don't think.
...
#0 boot (howto=260) at ../../kern/kern_shutdown.c:288
288 dumppcb.pcb_cr3 = rcr3();
(kgdb) bt
#0 boot (howto=260) at ../../kern/kern_shutdown.c:288
#1 0xc0145755 in panic () at ../../kern/kern_shutdown.c:450
#2 0xc020e9e2 in trap_fatal (frame=0xcb4ad8dc, eva=3735929126)
at ../../i386/i386/trap.c:917
#3 0xc020e695 in trap_pfault (frame=0xcb4ad8dc, usermode=0, eva=3735929126)
at ../../i386/i386/trap.c:810
#4 0xc020e2d7 in trap (frame={tf_fs = 16, tf_es = 16, tf_ds = 16, tf_edi =
0,
tf_esi = 0, tf_ebp = -884287172, tf_isp = -884287224, tf_ebx = 16384,
tf_edx = -559038242, tf_ecx = -1059309536, tf_eax = -1053816960,
tf_trapno = 12, tf_err = 0, tf_eip = -1072110632, tf_cs = 8,
tf_eflags = 66182, tf_esp = -1062703744, tf_ss = -911937724})
at ../../i386/i386/trap.c:436
(kgdb)
Nope, not useful at all really. Look at the first trap message to see
where the first one occurred, that'll at least give you a locality.
Just out of curiosity, are either of these systems running with NCR
controllers?
--
\\ 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
Re: -current page fault at 0xdeadc0de
One system was running 2.2.8, and my core file presents me with this: ... Just out of curiosity, are either of these systems running with NCR controllers? In case you're fishing, I'm running 4 NCR equipped boxes (510 and 575) with FreeBSD 2.2.8-stable right now and have seen *NO* problems whatsoever. I've only *once* had a SCSI error on my system, and that was due to a bug that was somewhere other than the NCR driver. Nate To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
