ffs_blkfree: freeing free block (was Re: Panic (pmap))

In message <[EMAIL PROTECTED]>, Matthew Dillon writes: >:(Mind you, we're seeing "freeing free block" panics on a NFS server >:with full disks on 3.4). >: >: David. > >With softupdates turned on? Softupdates has known problems when a >disk runs out of space. No, softupdates is not

Re: ffs_blkfree: freeing free block (was Re: Panic (pmap))

In message <[EMAIL PROTECTED]>, Matthew Dillon writes: >There must still be a bug in there somewhere, unrelated to softupdates. > >Try turning off the vfs.ffs.doreallocblks via sysctl and see if that >stops the crashes, that will help narrow down where to search for the >problem.

Re: ffs_blkfree: freeing free block (was Re: Panic (pmap))

In message <[EMAIL PROTECTED]>, Ian Dowse writes: > >The fix should be relatively straightforward - either the code should >avoid linking new indirection blocks until all allocations succeed, >or it should back out the changes on failure. Here's one patch that seems to

Re: Best NIC for FBSD (was: Buffer Problems and hangs in 4.0-CURRENT..)

In message <[EMAIL PROTECTED]>, Mike Smith writes: >> fxp0: The Intel driver is by far the highest preformance model, >> beats the 3com (second best) hands down with much lower CPU >> overhead. > >Do you actually have any numbers to quantify this? There's nothing in >the driver architecture no

Re: XFree86-3.3.5/kde-1.1.2/Current today.

In message <[EMAIL PROTECTED]>, Edwin Culp writes: > >libraries, I decided as a last resort to substitute the SiS-6326 that worked >flawlessly on 3.3.4. I changed it for a Matrox G200 and ran xf86config and >it worked perfectly with no other changes and everything else the same. >Looks like the S

Re: Can't make installworld :(

In message <[EMAIL PROTECTED]>, Hosta s Red writes: >I can't make installworld for some time with following message: > >vm/vm_object.h -> vm/vm_object.ph >vm/vm_page.h -> vm/vm_page.ph >vm/vm_pageout.h -> vm/vm_pageout.ph >vm/vm_pager.h -> vm/vm_pager.ph >vm/vm_param.h -> vm/vm_param.ph >vm/vm_pro

Re: panic on mount

In message <[EMAIL PROTECTED]>, John Baldwin writes: > >It looks like the mutex is really held since the mtx_assert before >witness_unlock didn't trigger. You can try turning witness off for the time >being as a workaround. I'm not sure why witness would be broken, however. Revision 1.41 of sys

Re: mdmfs mount_mfs compatibility bug?

In message <[EMAIL PROTECTED]>, Jos Backus writes: >> >> This was fixed some time ago, I thought. Are you up to date? > >There was a commit to mdmfs.c in August. >This is with yesterday's -current, sorry, should have mentioned that. The "mount -t mfs" case doesn't work with mdmfs, because mount

Re: mdmfs mount_mfs compatibility bug?

In message <[EMAIL PROTECTED]>, Dima Dorfman writes: > >The problem with this is that in a bikeshed far, far in the past, some >people wanted to me able to call it "mount_md" instead of "mount_mfs". >Of course, we could allow "mfs" and "md", but that seems rather ugly >(what if someone wants "fish

modules/ed/../../dev/if_ed.c:40: opt_ed.h: No such file or directory

Apologies for this - I missed out a file in a commit earlier. Fixed now. Any other (non-module) complaints about opt_ed.h can be cured by rerunning config. Ian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: Multiple NFS server problems with Solaris 8 clients

In message <[EMAIL PROTECTED]>, BSD User writes: >Actually, upon instrumenting some code, it looks like RELEASE-4.4 gets it >mostly right. It ejects a PROG_UNAVAIL call which causes the Solaris 8 >client to back off. The correct message would seem to be PROC_UNAVAIL, >but I would take PROG_UNAVA

Re: vmware fails on -current

In message <[EMAIL PROTECTED]>, "Georg-W. Koltermann" writes : >I also tried to update /compat/linux/dev/vmnet1 to match the >/dev/vmnet1, and that got me just a litte bit farther. I now get >"Could not get address for /dev/vmnet1: Invalid argument >Failed to configure ethernet0." I added some pr

Re: vmware fails on -current

In message <[EMAIL PROTECTED]>, CHOI Junho writes: > >Hmm.. I have experienced another problem(-current of 19 Nov.) with >vmware. When it runs it comes up with the following dialog: > > "Encountered an error while initializing the ethernet address. > You probably have an old vnet driver. Try in

Re: vmware fails on -current

In message <[EMAIL PROTECTED]>, CHOI Junho writes: > >I'll try. Oh, I forget to say I appiled des's linux_ioctl patch. > Ah, that's different then. I assumed from the error that you had revision 1.76 of linux_ioctl.c, but if that patch applied then you don't. Try updating your sources again; revi

Missing stack frames in kgdb/ddb traces

I noticed recently two problems with gdb/ddb traces that involve an interrupt frame (both of these are in i386-specific code, but maybe similar issues exist on other architectures): The first is that kgdb sometimes messes up a stack frame that includes an interrupt, e.g in the trace below, the c

Re: Multiple NFS server problems with Solaris 8 clients

> >The last one is a know problem. There is a (unfinished) patch available to >solve this problem. Thomas Moestl <[EMAIL PROTECTED]> is still working on >some issues of the patch. Please contact him if you like to know more. > >Here is the URL for the patch: > >http://home.teleport.ch/freebsd/user

Re: cvs commit: src/sys/kern subr_diskmbr.c

In message <[EMAIL PROTECTED]>, Peter Wemm writes : >The problem is, that you **are** using fdisk tables, you have no choice. >DD mode included a *broken* fdisk table that specified an illegal geometry. ... >This is why it is called dangerous. BTW, I presume you are aware of the way sysinstall cr

Re: change to ZALLOC(9) man page

In message <[EMAIL PROTECTED]>, Ju lian Elischer writes: >By my reading of the code I would like to make the following changes >to the documentation for the zone(9) man page; Yes! Please do. I must have read that page about 10 times and been annoyed at its misleading information, but I never got

mountd(8) leaving filesystems exported

There are quite a few assumptions in mountd(8) about the layout of the per-filesystem mount(2) `data' struct, which make the code quite ugly. It uses a union to ensure that it supplies a large enough structure to mount(2), but regardless of the filesystem type, it always initialises the UFS versi

Re: mountd(8) leaving filesystems exported

In message <[EMAIL PROTECTED]>, Terry Lambert writes: >> One nasty bug is that the code for un-exporting filesystems checks >> to see if the filesystem is among a list of supported types, but >> the code for exporting doesn't. This list of supported filesystems >> does not include ext2fs or hpfs,

Re: Netatalk broken in current? Lock order reversal?

In message <[EMAIL PROTECTED]>, Emiel Kollof writes: > >Oh, on another note, is someone working at that netatalk breakage? Who >do I have to discipline for that? :-) Could you try the following patch in src/sys/netatalk? The problem was caused by the -fno-common compiler option that was added to

Re: boot floppy problems...

In message , Mike Brancato wr ites: >oh, well. They say something along the lines of >"Disk error: lba is 0x9 (should be 0x10)" >or similar. then it trys to boot the kernel twice using the loader, but >fails with the path 0:fd(0,a)/kernel Hmm, t

Re: boot floppy problems...

In message , Mike Brancato wr ites: >no problem. >keep up the good work. > >mike Ok, it's fixed now. If you'd like to try it, there's an updated version of the kern.flp from today's -CURRENT snapshot at: http://www.maths.tcd.ie/~iedowse/F

Re: Fw: Stop annoying message of lnc

In message <[EMAIL PROTECTED]>, Mike Smith writes: > >I don't quite understand Paul's reasoning, though; it's not actually >useful to unload/reload parts of a device's bus attachment without >unloading/reloading all the downstream parts of the driver. > >I think the fix should probably be commit

Re: growfs

In message <[EMAIL PROTECTED]>, Andrea Campi writes: > >Anyway, that was not my point. If I reboot into single-user, and am thus sure >to have the / fs in a clean, consistent state, should I expect growfs to work >in a safe way? If so, we should document it. I think it is still unlikely to be com

reboot(8) delay between SIGTERM and SIGKILL

I have noticed that reboot(8) sometimes appears not to wait long enough before sending the final SIGKILL to all processes. On a system that has a lot of processes swapped out, some processes such as the X server may get a SIGKILL before they have had a chance to perform their exit cleanup. The p

fsdb broken in -current

The last set of changes to fsck_ffs moved the initialisation of dev_bsize to sblock_init(), but this is not called by fsdb(8) so fsdb dies almost immediately with a floating exception. I'm just going to commit the obvious fix, which is to have fsdb call sblock_init() also. Ian To Unsubscribe: s

Re: kernel core

In message <[EMAIL PROTECTED]>, Warner Losh writes: >: >: Yes, but until such time as we do that we should warn people in UPDATING at >: least. >: > >OK, but you won't like the UPDATING entry. The bug actually looks fairly simple to fix. ffs_reload() isn't checking if the new superblock fields

Re: kernel core

In message <[EMAIL PROTECTED]>, John Baldwin writes: > > >Fair enough, I guess ffs_reload() should just sanity check the values. Any >takers? You could try this (untested). I have to run now, but I can test it later as it's easy enough to reproduce. Ian Index: ffs_vfsops.c

Re: kernel core

In message <[EMAIL PROTECTED]>, Ian Dowse writes: >You could try this (untested). I have to run now, but I can test it >later as it's easy enough to reproduce. Almost, but I missed the fs_contigdirs field, which was the real culprit. An updated patch is below; this seems to st

Re: Strangeness with newsyslog/wtmp

In message <[EMAIL PROTECTED]>, "Thomas D. Dean" write s: >I notice that my /var/log/wtmp has strange renewal times. I don't >know when it was not like this. newsyslog.conf is set to renew this >once per week. What is causing this? -rw-rw-r-- 1 root wheel 27 Apr 15 12:00 /var/log/wtmp.3.gz

Re: wierdness with mountd

In message <[EMAIL PROTECTED]>, John Polstra writes: >In article <[EMAIL PROTECTED]>, >Matthew Jacob <[EMAIL PROTECTED]> wrote: >> May 28 10:21:43 farrago mountd[217]: can't delete exports for /tmp >> May 28 10:21:43 farrago mountd[217]: can't delete exports for /usr/obj > >I've been seeing this

Re: wierdness with mountd

In message <[EMAIL PROTECTED]>, John writes: >Looking in /usr/src/sbin/mountd/mountd.c, under line 930 >shows the following: > >num = getmntinfo(&fsp, MNT_NOWAIT); > >and then runs through a loop 'num' times trying to >delete any export for each entry. Thanks, you're right - this has not

Re: wierdness with mountd

In message <[EMAIL PROTECTED]>, Ian Dowse writes: >error? (untested patch below). I braino'd that patch (error vs. errno), but I have just committed a working version that should stop the mountd warnings. Ian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe

Re: cvs commit: src/sbin/fsck_ffs setup.c

In message <[EMAIL PROTECTED]>, Ian Dowse writes: >iedowse 2001/05/29 13:45:09 PDT > > Modified files: >sbin/fsck_ffssetup.c > Log: > Ignore the new superblock fields fs_pendingblocks and fs_pendinginodes > when comparing with the alternate superb

Re: dirpref and RELENG_4 fsck

In message <[EMAIL PROTECTED]>, Alfred Perlstein wri tes: >> Was it determined that the fsck corruption problems which were seen >> with fsck after the introduction of the dirpref changes do not affect >> RELENG_4? I haven't seen any MFC of changes to the RELENG_4 fsck >> code, and I'm kind of wo

Re: MSDOS filesystem mounting...

In message <[EMAIL PROTECTED]>, Jim Bryant writes: > > 6:20:34pm wahoo(113): mount_msdos /dev/da0s1 /ms-dog >mount_msdos: vfsload(msdos): No such file or directory Try "mount_msdosfs" instead of "mount_msdos". The latter is probably a stale binary left on your system from before the rename that

Load average synchronisation and phantom loads

There are a few PRs and a number of messages in the mailing list archives that describe a problem where the load average occasionally remains at 1.0 or greater even though top(1) reports that the CPU is nearly 100% idle. The PRs I could find in a quick search are kern/21155, kern/23448 and kern/2

Re: disklabel broken again?

In message , Matthew Jacob writ es: > >Sometime in the last few days, disklabel -Brw auto seems to have stopped >working for me on alpha It used to be the thing of: >Now I get: > >dd if=/dev/zero of=/dev/da5 bs=1024k count=10 >... >disklabel -Br

Re: disklabel broken again?

In message <[EMAIL PROTECTED]>, Ian Dowse writes: >In message <Pine.BSF.4.21.0107122138260.61694-10@beppo>, Matthew Jacob wri >t >es: >>dd if=/dev/zero of=/dev/da5 bs=1024k count=10 >>... >>disklabel -Brw da5 auto >>disklabel: No space left on de

Re: Load average synchronisation and phantom loads

In message <[EMAIL PROTECTED]>, Bruce Ev ans writes: > >I think that is far too much variation. 5 seconds is hard-coded into >the computation of the load average (constants in cexp[]), so even a >variation of +-1 ticks breaks the computation slightly. I have not changed the mean inter-sample tim

Re: Load average synchronisation and phantom loads

In message <[EMAIL PROTECTED]>, Bruce Ev ans writes: >On Tue, 17 Jul 2001, Ian Dowse wrote: >> effect in the load calculation, but even for the shorter 5-minute >> timescale, this will average out to typically no more than a few >> percent (i.e the "5 minutes"

Re: NFS client unable to recover from server crash

In message <[EMAIL PROTECTED]>, Maxim Sobolev writes: >I found that after introduction of the new RPC NFS client is no longer >able to recover from server crash (both cluent and server are 5-CURRENT >systems). After a well known `nfs server not responding' message, client >hangs and even though se

Re: NFS client unable to recover from server crash

In message <[EMAIL PROTECTED]>, Matt Dillon writes: > Ian, please don't do this. The whole point of having an uninterruptable > mount is so the client can survive a server reboot or network failure. > Doing this destroys uninterruptable semantics. Firstly, I have no intention of committing

Re: filesystem errors

In message <[EMAIL PROTECTED]>, Michael Harnois writes: >I'm tearing my hair out trying to find a filesystem error that's >causing me a panic: ufsdirhash_checkblock: bad dir inode. > >When I run fsck from a single user boot, it finds no errors. > >When I run it on the same filesystem mounted, it f

Re: filesystem errors

In message <[EMAIL PROTECTED]>, Michael Harnois writes: > >The only result it generated was > >/usr/home/mdharnois off 120 ino 0 reclen 0x188 type 010 namelen 14 name '.fetc >hmail.pid' [368] > >and that file is destroted and recreated every couple of minutes. It's the directory (/usr/home/mdharn

SIGCHLD changes causing fault on nofault entry panics

The panics in exit1() that have been reported on -stable appear to be caused by these commits: REV:1.92.2.4kern_exit.c 2001/07/25 17:21:46 dillon REV:1.72.2.7kern_sig.c 2001/07/25 17:21:46 dillon MFC kern_exit.c 1.131, kern_sig.c 1.125 - b

Re: filesystem errors

In message <[EMAIL PROTECTED]>, Michael Harnois writes: > >I don't have sufficient technical knowledge to know which of you is >right; I would just ask that filesystem corruption caused by >restarting from a hung system not cause a panic . I removed the extra sanity check yesterday, so if you hav

Re: rpc.umtall dumps core on each startup/shutdown

In message <[EMAIL PROTECTED]>, Maxim Sobolev writes: >I found that the rpc.umntall program from time to time starts dumping a core >at each startup/shutdown. Removal of /var/db/mountab helps for certain It seems to be a bug in the rpc library (thank $deity for libefence when tracking down such b

Re: Panic on 8/10 -current: sleeping process owns a mutex

In message <[EMAIL PROTECTED]>, Doug Barton writes: >Immediately prior to the crash I was getting a lot of these on the console: > >Aug 12 01:00:52 Master /boot/kernel/kernel: >/usr/local/src/sys/kern/kern_synch.c:377: sleeping with "mountlist" locke >d from /usr/local/src/sys/kern/vfs_syscalls.c

Re: Panic with latest current/UFS_DIRHASH

In message <[EMAIL PROTECTED]>, Ollivier Robert writes: > >The interesting thing is that I also get that with my old 17th Jul. >kernel... except that the panic message is > >"ufsdirhash_checkblock: bad dir inode" > >It is always in the following part of installworld: That's interesting - the "ba

fsck setting d_ino == 0 (was Re: filesystem errors)

In message <[EMAIL PROTECTED]>, Kirk McKusick writ es: >FFS will never set a directory ino == 0 at a location other >than the first entry in a directory, but fsck will do so to >get rid of an unwanted entry. The readdir routines know to >skip over an ino == 0 entry no matter where in the directory

Re: Panic with latest current/UFS_DIRHASH

In message <[EMAIL PROTECTED]>, Ollivier Robert writes: >According to Ollivier Robert: >> Just upgraded my laptop to the latest current and during installworld, got >> this panic: >> >> panic: ufsdirhash_findslot: 'ka_JP.Shift_JIS' not found Thanks for the bug report - see my other mail to -curr

Re: Kernel Panic from Yesterday's CVSup

In message <[EMAIL PROTECTED]>, John Baldwin writes: >> malloc(48,c0238100,0,c65feb80,0) at malloc+0x2a >> exit1(c65feb80,0,0,c6623f78,c01fc852) at exit1+0x1b1 >> kthread_suspend(0,c0279a40,0,c022d1ec,a2) at kthread_suspend >> ithd_loop(0,c6623fa8) at ithd_loop+0x56 >> fork_exit(c01fc7fc,0,c6623f

Re: panic: lockmgr: draining against myself

In message <[EMAIL PROTECTED]>, ryan beasley writes: > >panic: lockmgr: draining against myself I've just checked in revision 1.426 of vfs_subr.c which may solve this, but I was not able to reproduce it myself. Could you or anybody else who has seen this panic try the above revision to see if it h

Re: Problem with umount and fsid?

In message <[EMAIL PROTECTED]>, Nate Lawson writes: >I get an error when umounting a FAT filesystem on a USB flash drive. It >appears the device is properly unmounted. Is this a case that needs to be >fixed in our fsid code? It happens every time I unmount this device. >laptop# umount /thumb >u

Re: PLIP transmit timeouts -- any solutions?

In message <[EMAIL PROTECTED]>, Christopher Nehren writes: > >--=-7MVWKH2AJ0lqXf3q30++ >Content-Type: text/plain >Content-Transfer-Encoding: quoted-printable > >I currently have a PLIP link to an old laptop running Linux (I tried to >install FreeBSD, but it freezes at the USB detection -- yes, I tr

Re: Fixing -pthreads (Re: ports and -current)

In message <[EMAIL PROTECTED]>, Daniel Eischen writes: >On Wed, 24 Sep 2003, Scott Long wrote: >> PTHREAD_LIBS is a great tool for the /usr/ports mechanism, but doesn't >> mean anything outside of that. > >That just meant it makes it easier to maintain ports so that >they are PTHREAD_LIBS complian

Re: INPCB panic....

In message <[EMAIL PROTECTED]>, Sam Leffler writes: >On Monday 10 November 2003 11:37 am, Larry Rosenman wrote: >> I removed my wi0 card (with DHCLIENT running), and got the following panic >> on a -CURRENT from yesterday: > >Thanks. Working on it... FYI, I've been using the following patch local

Re: cvs commit: src/sbin/umount umount.c

In message <[EMAIL PROTECTED]>, Rudolf Cejka writes: >> If the unmount by file system ID fails, don't warn before retrying >> a non-fsid unmount if the file system ID is all zeros. This is a ... >Hello and thanks for fixing this! I had a plan to report this, but you >were faster :o) I'm interes

Re: kernel panic trying to utilize a da(4)/umass(4) device with ohci(4)

In message <[EMAIL PROTECTED]>, "Brian F. Feldman" writes: >Jeez, it's been broken a year and it's almost 5.2-RELEASE now. Does anyone >have ANY leads on these problems? I know precisely nothing about how my USB >hardware is supposed to work, but this OHCI+EHCI stuff definitely doesn't, >and

Re: NFS -current

In message <[EMAIL PROTECTED]>, Patric Mrawek writes: >On several clients (-DP1, -DP2, 4-stable) mounting a nfs-share >(mount_nfs -i -U -3 server:/nfs /mnt) and then copying data from that >share to the local disk (find -x -d /mnt | cpio -pdumv /local) results >in lost NFS-mount. > >client kernel:

Re: NFS -current

In message <[EMAIL PROTECTED]>, Terry Lambert writes: >Ian Dowse wrote: >> It is normal enough to get the above 'not responding' errors >> occasionally on a busy fileserver, but only if they are almost >> immediately followed by 'is alive again' mes

Re: msgbuf cksum mismatch (read 933e3, calc 93fbe)

In message <[EMAIL PROTECTED]>, Paolo Pisati writes: > >What does it mean? > >It's the first row in my today's kernel. You can safely ignore it. Some BIOSes don't clear the RAM during a reboot, so when booting up, FreeBSD attempts to pick up the kernel message buffer from before the reboot (this c

Re: Heads up: checking in change to ata-card.c

In message <[EMAIL PROTECTED]>, "M. Warner Losh" writes: >Here's a better patch, basesd on wpaul's input. Bill, can you try it >an see if it works for you? If so, i would be better to commit this >one. If not, I'll work with you to fix it. FYI, I have a no-name ("PCMCIA"/"CD-ROM") drive that a

Re: -current panic in suser_cred()

In message <[EMAIL PROTECTED]>, Wesley M organ writes: >At some point between 20 Jun and (by my best guest) 22 Jun there has been >a problem introduced somewhere... How much more vague can you get? :)... >#12 0xc025dab5 in chkiq (ip=0xc3a5c400, change=4294967295, cred=0x0, >flags=0)#13 0xc025b57f

Re: cvs commit: src/sys/i386/i386 pmap.c

In message <[EMAIL PROTECTED]>, "Andrew R. Reite r" writes: >"Too many pages were prefaulted in pmap_object_init_pt, thus > the wrong physical page was entered in the pmap for the virtual > address where the .dynamic section was supposed to be." > > Submitted by: tegge Pointy hat

Re: KSE status report

In message <[EMAIL PROTECTED]>, Ju lian Elischer writes: >The big problem at the moment is that something in the >source tree as a whole, and probably something that came in with KSE >is stopping us from successfully compiling a working libc_r. >(a bit ironic really). Is the new (elm)->

Re: additional queue macro

In message <[EMAIL PROTECTED]>, Jonathan Lemon writes: >Essentially, this provides a traversal of the tailq that is safe >from element removal, while being simple to drop in to those sections >of the code that need updating, as evidenced in the patch below. Note that this of course is not "safe

Re: dump(8) is hosed

In message <[EMAIL PROTECTED]>, Don Lewis writes: > >I was finally finally able to reproduce this by creating a large file >before doing the dump. Dump(8) is *very* hosed. The UFS2 import broke >it's ability to follow multiple levels of indirect blocks. Thanks for tracking this down! One thing

Re: -CURRENT trashes disk label

In message <[EMAIL PROTECTED]>, David Schultz writes: >I just made world on -CURRENT (cvsup a few hours ago), booted >using a new GENERIC kernel and ran mergemaster. Before I >installed world, I mounted the root partition for my more stable >development environment (4.6-RELEASE) to copy my firewa

Re: bdwrite: buffer is not busy

In message <[EMAIL PROTECTED]>, "Andrey A. Chernov" writes: >I see this panic constantly during last month or two, UP machine, no >softupdates. Anybody else saw it too? Any ideas? The "buffer is not busy" panic is usually a secondary panic that occurs while trying to sync the disks after a diffe

Re: NEWCARD support for Linksys Ethernet broken?

In message <[EMAIL PROTECTED]>, "M. Warner Losh" writes: >Used to work for me, but something seems to have busted it in recent >versions of the kernel. So NEWCARD appears to be broken for ata, sio >and ed. Wonderful. These all used to work at one point in the past. I think the "ed" problem is

Re: do we still need ufs/ffs/ffs_softdep_stub.c ?

In message <[EMAIL PROTECTED]>, Luigi Rizzo writes: >Hi, >just got the following panic with today's -current sources and >an oldish config file (one not having "options SOFTUPDATES"): >panic(c026ecc1,c66e1b94,c01ff565,c1cda000,0) at panic+0x7c >softdep_slowdown(c1cda000,0,0,,2) at

Re: Is anyone else having trouble with dump(8) on -current?

[replying to an old message] In message <[EMAIL PROTECTED]>, Alexander Leidi nger writes: >On 7 Mai, Benjamin Lewis wrote: >> | DUMP: slave couldn't reopen disk: Interrupted system call > >Try the attached patch. I also have a similar patch for restore. I don't >like the patch, I think I

Re: Is anyone else having trouble with dump(8) on -current?

In message <[EMAIL PROTECTED]>, Alexander Leiding er writes: >Have a look at Message-ID: <[EMAIL PROTECTED]> >(should be in the archive of audit). Ah, I had forgotten about that -audit thread. >Short: open shouldn't be able to return EINTR in practice... > >My assumptions: > - Bruce hasn't made

Re: Is anyone else having trouble with dump(8) on -current?

In message <[EMAIL PROTECTED]>, Bruce Evans writes: > >I don't know how open() of a disk device can be interrupted by a signal >in practice. Most disk operations don't check for signals. Does the PCATCH tsleep in diskopen() that I mentioned seem a likely candidate? Anyway, below is a simple prog

Re: fsck cannot find superblock

In message <[EMAIL PROTECTED]>, Bruce Evans writes: >> * drop support for 4K block sizes completely, but this breaks >> backwards compatibility > >I use patches like the following for the sanity checks: I think there may be other problems that are triggered by using <8k blocks on -curre

Re: nfs_inactive() bug? -> panic: lockmgr: locking against myself

In message <[EMAIL PROTECTED]>, Don Lewis writes: > >A potentially better solution just occurred to me. It looks like it >would be better if vrele() waited to decrement v_usecount until *after* >the call to VOP_INACTIVE() (and after the call to VI_LOCK()). If that >were done, nfs_inactive() woul

Re: nfs_inactive() bug? -> panic: lockmgr: locking against myself

In message <[EMAIL PROTECTED]>, Don Lewis writes: >After looking at ufs_inactive(), I'd like to add a fourth proposal And I've just remembered a fifth :-) I think the old BSD code had both an `open' count and a reference count. The open count is a count of the real users of the vnode (it is what

Re: nfs_inactive() bug? -> panic: lockmgr: locking against myself

In message <[EMAIL PROTECTED]>, Terry Lambert writes: >Ian Dowse wrote: >> And I've just remembered a fifth :-) I think the old BSD code had >> both an `open' count and a reference count. The open count is a >> count of the real users of the vnode (it is

Re: NFS hang on rmdir(2) with 5.0-current client, server

In message <[EMAIL PROTECTED]>, Robe rt Watson writes: >> > It looks like the client is basically hung waiting for an RPC response. >> > I'd be glad to provide more debugging information if someone can point me >> > in the right direction. >> >> I haven't seen this seen this problem with a 5.0-CU

Re: [ GEOM tests ] disklabel warnings and vinum drives lost

In message <[EMAIL PROTECTED]>, Robe rt Watson writes: >However, here's a patch that makes Vinum use namei() to rely on devfs to >locate requested devices instead of parsing the device name and guessing >the device number (incorrectly with GEOM). Unfortunately, I almost >immediately run into a di

Re: [ GEOM tests ] disklabel warnings and vinum drives lost

[CCs trimmed] >The divide by zero problem seems to be caused by an interaction >between two bugs: GEOM refuses to return the sector size because ... >The next failure I get is: > > Can't write config to /dev/da1s1d, error 45 (EOPNOTSUPP) This turns out to be vinum doing a DIOCWLABEL to ma

Re: [ GEOM tests ] disklabel warnings and vinum drives lost

In message <[EMAIL PROTECTED]>, Poul-Henning Kamp writes: >Make that _three_ bugs: vinum opens devices directly at the cdevsw >level, bypassing in the process the vnodes and specfs. Here is a patch that makes it use vn_open/vn_close/VOP_IOCTL, bringing it much closer to the way ccd(4) does thing

Re: mozilla vs linux emulation in -current?

In message <[EMAIL PROTECTED]>, Peter Wemm writes: >Has anybody else noticed this in -current? Mozilla hangs for a minute or >so at regular intervals.. >16:07:31.896548 216.145.52.172.20167 > 0.0.0.0.16001: S 1175926117:1175926117( Sounds like something I may have broken... Need to sleep now, but

Re: mozilla vs linux emulation in -current?

In message <[EMAIL PROTECTED]>, Ian Dowse writes : >IP, but we were throwing away the modified version). Commit if it >works, and I'll look properly tomorrow. Sorry for the breakage. With the one compile error fixed, this seemed to make `telnet 0.0.0.0' work again, so I wen

Re: Crash again

In message <[EMAIL PROTECTED]>, Vallo Kallaste writes: >The same kernel compiled for purposes of smbfs debugging crashed >again. I had X, make -j2 running and no smbfs mounts. For what it's >worth, the system did hang hard (no interrupts) some minutes before >the aforementioned crash and I had to r

Re: -CURRENT running really slow under vmware2

In message <[EMAIL PROTECTED]>, Jim Pirzyk writes: >I would think we need to at least patch current for this case. Enclosed >is a possible implementation. Comments? I think I tried this before, and puting the option in opt_cpu.h does not work, because not all files that include atomic.h will inc

ELCR in PCI-ISA bridge not getting set on resume

Since starting to use -current with ACPI on a Sony C1 laptop, I noticed that after resume, occasionally IRQ 9 would get stuck and not deliver any interrupts. IRQ 9 is shared by sound, USB and the pccard slot. It turned out that something was not saving the ELCR edge/level control registers in the

Re: kern/42417 cannot probe Olympus digital camera, "C-1"

In message <[EMAIL PROTECTED]>, Nate Lawson wri tes: >I looked at the change and it seems good. Can someone more familiar with >the USB system verify this? Done - I have a C-1 here, so I was able to test it - obviously I haven't accessed the camera from -current in a while! Ian To Unsubscribe:

Re: [acpi-jp 1925] Re: acpid implementation?

In message <[EMAIL PROTECTED]>, Takanori Watanabe writes: >It is obious there will be good if we have a way to catch power >event from userland. > >I have some ideas to implement it. >One way is implement with kqueue(2) and /dev/acpi to >get power events. This way does not require daemons >to wait

Re: [acpi-jp 1933] Re: acpid implementation?

In message <[EMAIL PROTECTED]>, Takanori Watanabe writes: >== >Next way is that make /dev/acpictl node that can open >exclusively and catch the power event by it, like apmd. >== > >This way requires that the event reading proceess should >be only one, so we need another device node to read event.

Re: MD broken in current

In message <[EMAIL PROTECTED]>, Bruce Evans writes: >Better fix mddestroy(). I don't know why it hangs ... I guess it is >because it is called before initialization is completed in mdinit(), >and there aren't enough state checks in mddestroy(). I think moving the line tsleep(sc, PRIBIO,

Re: MD broken in current

In message <[EMAIL PROTECTED]>, Bruce Evans writes: >On Wed, 27 Nov 2002, Ian Dowse wrote: >> I think moving the line >> >> tsleep(sc, PRIBIO, "mdwait", 0); >> >> to just after the following `if' statement may do the trick. If the >

Re: MD broken in current

In message <[EMAIL PROTECTED]>, Hiten Pandya writ es: >Is anyone planning to take this task, because, I think its important >that it is fixed. Or should it be put on the 5.0-todo list? If not, we >should put it in the BUGS section of mdconfig/ or the md(4) manual page. >IMO. I've tested the fix,

Re: unkillable process - 'mdconfig -t vnode' on small file

In message <[EMAIL PROTECTED]>, Michal Mertl writes: >Subject says it all. Fixed in md.c revision 1.74 - this was discussed here a few days ago, but I was just waiting for approval to commit the fix. Ian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the bo

panic: ata_dmasetup: transfer active on this device!

Hi Søren, I get the above panic every few days when resuming, especially if the disk was active while the laptop was suspending - it's easy to reproduce by starting some disk-intensive activity and then hitting the suspend button. I see that IWASAKI-san posted patches for this a few months ago -

Re: backgroud fsck is still locking up system (fwd)

In message <[EMAIL PROTECTED]>, Kirk McKusick wr ites: >Adding a two minute delay before starting background fsck >sounds like a very good idea to me. Please send me your >suggested change. BTW, I've been using a fsck_ffs modificaton for a while now that does something like the disabled kernel I/O

Re: Revision 1.88 of kern_linker.c breaks module loading for diskless

In message <[EMAIL PROTECTED]>, Harti Brandt write s: >the check for rootdev != NODEV introduced in rev 1.88 breaks loading of >kernel modules from an NFS mounted root in diskless configurations. >Dropping in gdb and printing rootdev shows -1 which is, I assume, NODEV. Ah, that would explain a pr

  1   2   >