Re: Kernel PANICS during "make release"
matusita> super-block backups (for fsck -b #) at: matusita> <<>> matusita> Yes, during a newfs. Console shows following messages: Maybe I'm wrong. Attached "ps" output says no 'newfs' is running but "cp". So, copying "mfsroot.gz" to a directory of floppy image causes kernel hungup... -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current.freebsd.org problems?
> > jhay> For now I just went back to an older kernel that works for me. > > Would you please explain "an older kernel" ? I'm using a kernel as of > Sep/30/2000 and it panics. > > *** > > Note that this (Sep/30/2000) kernel doesn't panic until Oct/13/2000. > Between Oct/14/2000 and Oct/17/2000, "make release" was failed at > buildworld. Oct/18/2000, panic. Oct/19/2000, also panic. > It looks like I spoke too soon. My 2000-10-05 kernel that previously worked also now panics. It must be somewhere when the floppies are made. On the serial console I see: Oct 21 04:44:49 beast /boot/kernel/kernel: /mnt: optimization changed from SPACE to TIME /mnt: bad dir ino 2 at offset 0: mangled entry panic: ufs_dirbad: bad dir cpuid = 0; lapic.id = 0100 boot() called on cpu#0 Does the mangled entry on /mnt mean there is something wrong in the /mnt filesystem? That would be the floppy image. Also it does not reboot after the panic. It just get stuck after printing a lot of "microuptime() went backwards (28431.4508250 -> 28431.2820885)" messages. John -- John Hay -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current.freebsd.org problems?
jhay> It looks like I spoke too soon. My 2000-10-05 kernel that previously jhay> worked also now panics. It must be somewhere when the floppies are jhay> made. Maybe there is a problem in newfs(8). peter 2000/10/16 17:41:37 PDT Modified files: sbin/newfs mkfs.c Log: Implement simple write combining for newfs - this is particularly useful for large scsi disks with WCE = 0. This yields around a 7 times speedup on elapsed newfs time on test disks here. 64k clusters seems to be the sweet spot for scsi disks using our present drivers. Revision ChangesPath 1.30 +38 -1 src/sbin/newfs/mkfs.c When I backout this change, the problem seems disappeared... -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current.freebsd.org problems?
matusita> When I backout this change, the problem seems disappeared...
This is sample shell script to reproduce recent kernel hungup:
#!/bin/sh
dd of=/tmp/image if=/dev/zero count=1440 bs=1k
awk 'BEGIN {printf "%c%c", 85, 170}' | \
dd of=/tmp/image obs=1 seek=510 conv=notrunc
vnconfig -s labels -c /dev/rvn0 /tmp/image
disklabel -Brw /dev/rvn0 fd1440
newfs -i 8 -T fd1440 -o space /dev/rvn0c
mount /dev/vn0c /mnt
cp /etc/rc /mnt
umount /mnt
vnconfig -u /dev/rvn0
exit 0
If you are running recent (at least Sep/30/2000) -current kernel, and
your newfs(8) is newer mkfs.c (rev 1.30) it will hungup as soon as
cp(1) is invoked.
-- -
Makoto `MAR' MATSUSHITA
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Bug in libc_r or broken application?
Just tried installing "ohphone" under FreeBSD-current. "ohphone" is a H323 compatible phone that can be used for Voice over IP, it's available in the FreeBSD ports collection. Just starting the application produces the message "User signal 2". That's it, nothing else, whatever option you supply. Copying libc_r.so.4 from a 4.1.1 machine to the -current machine makes ohphone work. Starting it under gdb I see that it receives a SIGUSR2, for whatever reason does not catch it and fails. Why would an application suddenly receive a SIGUSR2 when it wasn't receiving that signal with the 4.1.1 libc_r? Blaz Zupan, Medinet d.o.o, Linhartova 21, 2000 Maribor, Slovenia E-mail: [EMAIL PROTECTED], Tel: +386-2-320-6320, Fax: +386-2-320-6325 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
strange problem of PPPoE + NAT
I just upgrade one of my server to -current. that server connect to ADSL and act as a gateway. however, after I upgrade that server to -current, all other clients (all windows 98) start acting really strange. clients was unable to connect to more then 60% of web sites. for example, clients can not connect to www.yahoo.com (stucked). but can connect to www.infoseek.com. Clients can login to ftp.aarnet.edu.au but cant do "ls -la" or get (will stucked). Clients can pop receive mail from outside mail server, if and only if mail are in very small size. otherwise it will "stucked" too. This problem was also exist with the server, but after I add "search xx.xx.xx" into resolv.conf, the server then works totaly fine after that. therefor, i try to add the domain name suffix in those windows 98 machine. still doesnt help. sorry about my poor way to explain this problem. but it is just too weir.. dont konw how to explain it :P PLEASE HELP thx in advance! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bug in libc_r or broken application?
On Sat, 21 Oct 2000, Blaz Zupan wrote: > Just tried installing "ohphone" under FreeBSD-current. "ohphone" is a H323 > compatible phone that can be used for Voice over IP, it's available in the > FreeBSD ports collection. Just starting the application produces the message > "User signal 2". That's it, nothing else, whatever option you supply. Copying > libc_r.so.4 from a 4.1.1 machine to the -current machine makes ohphone work. > Starting it under gdb I see that it receives a SIGUSR2, for whatever reason > does not catch it and fails. Why would an application suddenly receive a > SIGUSR2 when it wasn't receiving that signal with the 4.1.1 libc_r? It could be using pthread_kill(tid, SIGUSR2) to send the signal to a thread. If there is no signal handler installed for SIGUSR2, and if the action for the signal is SIG_DFL, then POSIX dictates that pthread_kill() also send the signal to the process. Before the changes I made last week, our threads library failed to do this. If this is the problem, then the fix would be to install a signal handler for SIGUSR2. I'm not sure why ohphone wouldn't have similar problems on other platforms, though. -- Dan Eischen To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Junior Kernel Hacker Task: M_ZERO
I'd be willing to take this task. - Original Message - From: "Poul-Henning Kamp" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, October 20, 2000 9:12 PM Subject: Junior Kernel Hacker Task: M_ZERO [...] > If anybody is looking for a simple task to perform in the FreeBSD > kernel: this is it. > > A quick grep tells me that there are at least 91 files in the src/sys > tree which could use this flag to simplify and optimize the code. [...] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Junior Kernel Hacker Task: M_ZERO
> If anybody is looking for a simple task to perform in the FreeBSD > kernel: this is it. > > A quick grep tells me that there are at least 91 files in the src/sys > tree which could use this flag to simplify and optimize the code. i'll probably start looking at these this week sometime... something to pass the time in class i suppose. -- garrett rooney my pid is inigo montoya. [EMAIL PROTECTED] you kill -9 my parent process. http://electricjellyfish.net/prepare to vi. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: strange problem of PPPoE + NAT
On Sat, Oct 21, 2000 at 11:08:28PM +1000, Idea Receiver wrote: > > I just upgrade one of my server to -current. that server connect to ADSL > and act as a gateway. > > however, after I upgrade that server to -current, all other clients > (all windows 98) start acting really strange. clients was unable to > connect to more then 60% of web sites. for example, clients can not Sounds like a PMTU-D problem. Either change the MTU of the machines behind the gateway to something like 1440, or try /usr/ports/net/tcpmssd. josh -- "Watching those 2 guys [Bush and Gore] debate is like watching Ben Stein read 'The Story of O'" -- Dennis Miller To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Printing lockups in -current / Nutscrape
Hi, this has happened twice now, and I think it's about time to report it. I'm running -current Tue Oct 17 00:02:26 CDT 2000, and have noticed that under this and a -current from a few weeks ago that while printing in netscape, the whole system will lock. no panic, just big-red-button-time.. sorry i can't give any diagnostics, but, like i said, it's a hard lock, and so far, always right in the middle of printing. i am using that print filter that links into ghostscript and allows printing to hp deskjets... [ forget the name, it's been so long. jim -- All opinions expressed are mine, if you| "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" -- [EMAIL PROTECTED] KC5VDJ - HF to 23cm KC5VDJ@NW0I.#NEKS.KS.USA.NOAM HF/VHF: IC-706MkII VHF/UHF/SHF: IC-T81AKPC3+ & PK-232MBXGrid: EM28px -- ET has one helluva sense of humor, always anal-probing right-wing schizos! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
new rc.network6 and rc.firewall6
Hi, I wish to update rc.network6 and introduce rc.firewall6. - ipv6_prefix_* and ipv6_ifconfig_* work for end node - rtsol should be work to only one interface - new variable ipv6_defaultrouter is added - ipv6_firewall_enable, ipv6_firewall_type, ipv6_firewall_script, ipv6_firewall_logging are added to introduce rc.firewall6. I put it on: http://www.imasy.or.jp/~ume/ipv6/FreeBSD/rc.network6.diff http://www.imasy.or.jp/~ume/ipv6/FreeBSD/rc.firewall6 Please review it. -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.imasy.org/~ume/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new rc.network6 and rc.firewall6
> I wish to update rc.network6 and introduce rc.firewall6. H. I must confess that I see /etc as getting rather cluttered these days. Is there no way to perhaps collapse some of the most related functionality into single files and start passing arguments or something? Just a comment.. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new rc.network6 and rc.firewall6
-On [20001021 20:10], Jordan Hubbard ([EMAIL PROTECTED]) wrote: >> I wish to update rc.network6 and introduce rc.firewall6. > >H. I must confess that I see /etc as getting rather cluttered >these days. Is there no way to perhaps collapse some of the most >related functionality into single files and start passing arguments >or something? Just a comment.. The IPv6 systems are so much different in set-up than the IPv4 systems. Collapsing of the functions is not really doable. However, Umemoto-san and me will discuss this, since we [he mostly] have been working on this for the last few months. -- Jeroen Ruigrok van der Werven Network- and systemadministrator <[EMAIL PROTECTED]>VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl I love to doubt as well as know... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Junior Kernel Hacker Task: M_ZERO
On Sat, Oct 21, 2000 at 09:48:47AM -0400, Garrett Rooney wrote: > > If anybody is looking for a simple task to perform in the FreeBSD > > kernel: this is it. > > > > A quick grep tells me that there are at least 91 files in the src/sys > > tree which could use this flag to simplify and optimize the code. > > i'll probably start looking at these this week sometime... > > something to pass the time in class i suppose. Before anyone else starts looking at this, I've collected and cleaned up the patches I've recieved so far and produced a big diff at: http://www.maths.tcd.ie/~dwmalone/thirdtry If you do find more of these remember to make sure the style in which you make the patch matches the surounding code. Also, please submit unified diffs - they are much easier to review for changes like this. If you can, make sure the code compiles before submitting it. Other than style changes, I've included a list of other changes I've made to the submitted patches. David. sys/dev/aic7xxx/aic7xxx_freebsd.c Missing , in call to malloc in the patch. sys/alpha/alpha/busdma_machdep.c sys/ia64/ia64/busdma_machdep.c Replace a sizeof(**mapp) with sizeof(*map) - they are the same but the second makes more sense. (this was in original code) sys/dev/usb/ohci.c sys/dev/usb/uhci.c Fix one bug in patch where xfer would not be zeroed if it came off the free list. sys/i386/include/mutex.h Patch reverted one of jhb's changes. sys/i386/isa/cx.c Changes were in code not used by FreeBSD, so I removed them. (There was also a syntax error in the patch). sys/kern/vfs_cache.c Patch zeroed more memory than original code - stick with original. sys/netinet/ip_dummynet.c Preserve some comments that were removed by patch. sys/netipx/ipx.c sys/netns/ns.c sizeof(*oia) and sizeof(*ia) not obviously the same - stick with original code. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
CURRENT locks up
CURRENT with sources from around this afternoon GMT+2 just locks up. Hardware is an ABIT BP6 mainboard. System boots up normally the first time, except for the rediculous long entropy gathering. Anyway, rebooted the system by means of a reboot command. And I get the following: SMP: AP CPU #1 Launched! SMP: CPU1 start_init: trying /sbin/init apic_initialize(): lint0: 0x00010700 lint1: 0x00010400 TPR: 0x0010 SVR: 0x01ff kernel trap 12 with interrupts disabled kernel trap 12 with interrupts disabled kernel trap 12 with interrupts disabled kernel trap 12 with interrupts disabled kernel trap 12 with interrupts disabled kernel trap 12 with interrupts disabled kernel trap 12 with interrupts disabled kernel trap 12 with interrupts disabled And after this my system just locks up totally. No CTRL-ALT-ESC. no numlock reacting, no nada. I have left the system like that for at least 15 minutes, but if I would even need to leave it like that longer, say like the hour Warner Losch reported, I seriously doubt the usage of all the entropy gathering and related stuff. Booting should be fast like it used to be. Excuse the cranky sound, but I just have spend an afternoon being non-productive for the things I had in store. =( -- Jeroen Ruigrok van der Werven Network- and systemadministrator <[EMAIL PROTECTED]>VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl Practice yourself what you preach... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new rc.network6 and rc.firewall6
Jeroen Ruigrok van der Werven wrote: > > -On [20001021 20:10], Jordan Hubbard ([EMAIL PROTECTED]) wrote: > >> I wish to update rc.network6 and introduce rc.firewall6. > > > >H. I must confess that I see /etc as getting rather cluttered > >these days. Is there no way to perhaps collapse some of the most > >related functionality into single files and start passing arguments > >or something? Just a comment.. > > The IPv6 systems are so much different in set-up than the IPv4 systems. > Collapsing of the functions is not really doable. > > However, Umemoto-san and me will discuss this, since we [he mostly] have > been working on this for the last few months. An /etc/ipv6 directory might be a useful alternative as well. In my mind 3 files is the point at which a directory starts being useful, and adding rc.firewall6 would make it 4. Doug -- "The dead cannot be seduced." - Kai, "Lexx" Do YOU Yahoo!? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CURRENT locks up
Jeroen Ruigrok van der Werven wrote: > > CURRENT with sources from around this afternoon GMT+2 just locks up. > > Hardware is an ABIT BP6 mainboard. > > System boots up normally the first time, except for the rediculous long > entropy gathering. > > Anyway, rebooted the system by means of a reboot command. Rebooting by means of 'shutdown -r now' or even C-A-D will run rc.shutdown which writes out the entropy file and prevents the long boot delay. FYI, Doug -- "The dead cannot be seduced." - Kai, "Lexx" Do YOU Yahoo!? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
FreeBSD watchdog problem worsens...
Umm.. I write this in hope that someone will take a note of a big problem(NO this is not a bug report) namley that the current src tree PCI dir has changed som much so the patch for the watchdog problem with some network cards is not appliable any more. http://www.mcs.net/~locke/vrfix/Either I hope someone will release a new patch page or a more complete network driver so the watchdog problem will end.(Have two different network cards and I have the problem on both of them) Regards Jerker
HEADS UP: -current a bit rocky at the moment..
This is a friendly little heads up that -current seems to be a bit wobbly at the moment. First of all, the WITNESS code now actually does something... and manages to hang the kernel while doing so. So for now you probably don't want WITNESS in your kernel config. Secondly, there have been reports of weirdness on SMP boxes. -- John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
m4 not in build tools for make world
Heya, I don't know if m4 should be in the build tools that are made during make world, but it isn't. And because I had the GNU m4 installed as m4 and not gm4 the building of the boot blocks went belly up (bootblocks crashed on boot). Just my $0.02 DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new rc.network6 and rc.firewall6
> However, Umemoto-san and me will discuss this, since we [he mostly] have > been working on this for the last few months. Sounds good to me. My comments were, just to make it clear again, just food for thought and not out-and-out objections. If even 47 more files in /etc is what it takes to get IPv6 fully supported, then so be it. :) - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
(no subject)
unsubscribe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
-current hangs during boot
Hi there, I've done a very recent week's make world(S) on -current, making and installing world and kernel go fine, but all hang on boot, with no error codes or msgs. When boot, all go fine at the beginning, and stop right after showing the msg: : : /dev/da0s1e: FILESYSTEM CLEAN, SKIPPING CHECK /dev/da0s1e: clean, 92565 free (125 frags, 11555 blocks, 0.1%fragmentation) then no more, I got to power off and on, and reboot using an old working kernel. any idea? -- // Donny To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
newfs/fsck problem (bad superblocks)
Hi, I posted a question concerning fsck yesterday. A number of people replied with the 'bad harddisk' comment. I have followed up some more on the problem, and can now reproduce it on different filesystems. Below, I umount my /usr/obj, newfs it, mount it, unmount it, and then fsck it. The fsck complains about a bad superblock. Also, do not remotely reboot after this if the newly newfs'd filesystem is automounted in /etc/fstab. The boot process will hang waiting for fsck to be run manually. Example: + %umount /usr/obj %newfs /dev/ccd0a Warning: 1616 sector(s) in last cylinder unallocated /dev/ccd0a: 672 sectors in 1628 cylinders of 1 tracks, 4096 sectors 3255.2MB in 102 cyl groups (16 c/g, 32.00MB/g, 4096 i/g) super-block backups (for fsck -b #) at: 32, 65568, 131104, 196640, 262176, 327712, 393248, 458784, 524320, 589856, 655392, 720928, 786464, 852000, 917536, 983072, 1048608, 1114144, 1179680, 1245216, 1310752, 1376288, 1441824, 1507360, 1572896, 1638432, 1703968, 1769504, 1835040, 1900576, 1966112, 2031648, 2097184, 2162720, 2228256, 2293792, 2359328, 2424864, 2490400, 2555936, 2621472, 2687008, 2752544, 2818080, 2883616, 2949152, 3014688, 3080224, 3145760, 3211296, 3276832, 3342368, 3407904, 3473440, 3538976, 3604512, 3670048, 3735584, 3801120, 3866656, 3932192, 3997728, 4063264, 4128800, 4194336, 4259872, 4325408, 4390944, 4456480, 4522016, 4587552, 4653088, 4718624, 4784160, 4849696, 4915232, 4980768, 5046304, 5111840, 5177376, 5242912, 5308448, 5373984, 5439520, 5505056, 5570592, 5636128, 5701664, 5767200, 5832736, 5898272, 5963808, 6029344, 6094880, 6160416, 6225952, 6291488, 6357024, 6422560, 6488096, 6553632, 6619168 %mount /dev/ccd0a /usr/obj %df -m /usr/obj Filesystem 1M-blocks UsedAvail Capacity Mounted on /dev/ccd0a 32010 2944 0%/usr/obj %umount /usr/obj %/sbin/fsck -y /dev/ccd0a ** /dev/ccd0a BAD SUPER BLOCK: VALUES IN SUPER BLOCK DISAGREE WITH THOSE IN FIRST ALTERNATE LOOK FOR ALTERNATE SUPERBLOCKS? yes USING ALTERNATE SUPERBLOCK AT 32 ** Last Mounted on ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 1 files, 1 used, 1638914 free (18 frags, 204862 blocks, 0.0% fragmentation) UPDATE STANDARD SUPERBLOCK? yes * FILE SYSTEM WAS MODIFIED * % + I am wondering about the following patch : peter 2000/10/16 17:41:37 PDT Modified files: sbin/newfs mkfs.c Log: Implement simple write combining for newfs - this is particularly useful for large scsi disks with WCE = 0. This yields around a 7 times speedup on elapsed newfs time on test disks here. 64k clusters seems to be the sweet spot for scsi disks using our present drivers. Revision ChangesPath 1.30 +38 -1 src/sbin/newfs/mkfs.c I will revert this patch tomorrow. I also wonder if this is related to the 'make release' problems. Comments welcome. -John To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: newfs/fsck problem (bad superblocks)
Reverting src/sbin/newfs/mkfs.c to revision 1.29 fixes the problem. With just a quick review of the patch, I'm not sure I understand what forces the last dirty buffer to be written. revert the patch? try to fix it? comments? -John - John W. De Boskey's Original Message - > Hi, > >I posted a question concerning fsck yesterday. A number of > people replied with the 'bad harddisk' comment. > >I have followed up some more on the problem, and can now > reproduce it on different filesystems. > >Below, I umount my /usr/obj, newfs it, mount it, unmount > it, and then fsck it. The fsck complains about a bad superblock. > Also, do not remotely reboot after this if the newly newfs'd > filesystem is automounted in /etc/fstab. The boot process > will hang waiting for fsck to be run manually. > >Example: > > + > %umount /usr/obj > %newfs /dev/ccd0a > Warning: 1616 sector(s) in last cylinder unallocated > /dev/ccd0a: 672 sectors in 1628 cylinders of 1 tracks, 4096 sectors > 3255.2MB in 102 cyl groups (16 c/g, 32.00MB/g, 4096 i/g) > super-block backups (for fsck -b #) at: > 32, 65568, 131104, 196640, 262176, 327712, 393248, 458784, 524320, 589856, > 655392, 720928, 786464, 852000, 917536, 983072, 1048608, 1114144, 1179680, > 1245216, 1310752, 1376288, 1441824, 1507360, 1572896, 1638432, 1703968, > 1769504, 1835040, 1900576, 1966112, 2031648, 2097184, 2162720, 2228256, > 2293792, 2359328, 2424864, 2490400, 2555936, 2621472, 2687008, 2752544, > 2818080, 2883616, 2949152, 3014688, 3080224, 3145760, 3211296, 3276832, > 3342368, 3407904, 3473440, 3538976, 3604512, 3670048, 3735584, 3801120, > 3866656, 3932192, 3997728, 4063264, 4128800, 4194336, 4259872, 4325408, > 4390944, 4456480, 4522016, 4587552, 4653088, 4718624, 4784160, 4849696, > 4915232, 4980768, 5046304, 5111840, 5177376, 5242912, 5308448, 5373984, > 5439520, 5505056, 5570592, 5636128, 5701664, 5767200, 5832736, 5898272, > 5963808, 6029344, 6094880, 6160416, 6225952, 6291488, 6357024, 6422560, > 6488096, 6553632, 6619168 > %mount /dev/ccd0a /usr/obj > %df -m /usr/obj > Filesystem 1M-blocks UsedAvail Capacity Mounted on > /dev/ccd0a 32010 2944 0%/usr/obj > %umount /usr/obj > %/sbin/fsck -y /dev/ccd0a > ** /dev/ccd0a > BAD SUPER BLOCK: VALUES IN SUPER BLOCK DISAGREE WITH THOSE IN FIRST ALTERNATE > > LOOK FOR ALTERNATE SUPERBLOCKS? yes > > USING ALTERNATE SUPERBLOCK AT 32 > ** Last Mounted on > ** Phase 1 - Check Blocks and Sizes > ** Phase 2 - Check Pathnames > ** Phase 3 - Check Connectivity > ** Phase 4 - Check Reference Counts > ** Phase 5 - Check Cyl groups > 1 files, 1 used, 1638914 free (18 frags, 204862 blocks, 0.0% fragmentation) > > UPDATE STANDARD SUPERBLOCK? yes > > > * FILE SYSTEM WAS MODIFIED * > % > + > > > > I am wondering about the following patch : > > peter 2000/10/16 17:41:37 PDT > > Modified files: > sbin/newfs mkfs.c > Log: > Implement simple write combining for newfs - this is particularly useful > for large scsi disks with WCE = 0. This yields around a 7 times speedup > on elapsed newfs time on test disks here. 64k clusters seems to be the > sweet spot for scsi disks using our present drivers. > > Revision ChangesPath > 1.30 +38 -1 src/sbin/newfs/mkfs.c > > > > I will revert this patch tomorrow. I also wonder if this is related > to the 'make release' problems. > > > Comments welcome. > > -John > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
PPP over ATM
I was wondering what the state of PPP over ATM is, if there is at all. And would like to offer my services in it's development if it isn't finished (or started) yet. I inquired on #FreeBSDHelp on EFNet but I didn't get any useful results. I am not sure if this is the correct place to be posting but I figured it could't hurt. Thanks! Brian Smith To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: newfs/fsck problem (bad superblocks)
> I also wonder if this is related to the 'make release' problems. During "make release", src/release/Makefile does create floppies for installation. Copying 'mfsroot.gz' (mfsroot imagefile) to a newly newfs-ed floppy image (mfsroot.flp, 1.44MB size) causes kernel hungup. -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
