Re: worklist_remove panic
Peter Wemm [EMAIL PROTECTED] wrote: For some reason, sysinstall or the kernel decided to += 64k on the start address of the swap partition (to avoid swap clobbering the fdisk, bootblocks, etc at the start of the disk), but neglected to remove 64k from the size. This could be undone. Swapping has been fixed long ago to not clobber disklabels (i. e. it doesn't start at the beginning of the swap partition). -- cheers, Jorg .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Boot time memory issue
SMAP type=01 base= len= 0009f800 SMAP type=02 base= 0009f800 len= 0800 SMAP type=02 base= 000e8400 len= 00017c00 SMAP type=01 base= 0010 len= 13ef SMAP type=03 base= 13ff len= f800 SMAP type=04 base= 13fff800 len= 0800 SMAP type=02 base= fff8 len= 0008 Too many holes in the physical address space, giving up Can you try changing the declaration of phys_avail at the top of sys/i386/i386/machdep.c from: vm_offset_t phys_avail[10]; to vm_offset_t phys_avail[100]; Did that and got the same error. I put a printf just before the pa_indx++ in machdep.c and watched it increment by 2's all the way up to 100. How many SMAP lines did it print? All the ones above look legitimate, and there are only 7 of them. What about the values of pa, i and physmap_idx? -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Boot time memory issue
Sat, May 26, 2001 at 22:03:34, barry (Barry Lustig) wrote about Re: Boot time memory issue: SMAP type=01 base= 0010 len= 13ef [...] Did that and got the same error. I put a printf just before the pa_indx++ in machdep.c and watched it increment by 2's all the way up to 100. Any other ideas? This code in machdep.c performs easy memory test for each page and adds it to previous chunk or creates new one. The idea AFAIU is to test declared memory regions for real ones. If you have 100 really different regions in declared two memory regions, something bad happened with your hardware: memory modules are broken, or chipset incorrectly detects them, or yet another problem... You can test its logic by adding following patch or similar one: --- machdep.c.orig Sun May 27 11:12:19 2001 +++ machdep.c Sun May 27 11:13:57 2001 @@ -1785,10 +1785,12 @@ printf(Too many holes in the physical address space, giving up\n); pa_indx--; break; } phys_avail[pa_indx++] = pa; /* start */ + printf( getmemsize: new chunk at %08lx\n, + (unsigned long) pa ); phys_avail[pa_indx] = pa + PAGE_SIZE; /* end */ } physmem++; } } /netch To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: worklist_remove panic
Check your disk label. I got burned a few months back on a fairly old install where I created swap first, then root. This causes the swap partition to start at sector 0, with root straight after. For some reason, sysinstall or the kernel decided to += 64k on the start address of the swap partition (to avoid swap clobbering the fdisk, bootblocks, etc at the start of the disk), but neglected to remove 64k from the size. That seems to be it. They actually overlap by 60 sectors. Grrr... David. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
-current broken ?
=== usr.bin/fetch cc -O -pipe -Wall -pedantic -I/usr/obj/flat/src/i386/usr/include -c /flat/src/usr.bin/fetch/fetch.c gzip -cn /flat/src/usr.bin/fetch/fetch.1 fetch.1.gz /flat/src/usr.bin/fetch/fetch.c: In function `stat_display': /flat/src/usr.bin/fetch/fetch.c:131: warning: ANSI C does not support the `ll' length modifier /flat/src/usr.bin/fetch/fetch.c:134: warning: ANSI C does not support the `ll' length modifier /flat/src/usr.bin/fetch/fetch.c: In function `stat_end': /flat/src/usr.bin/fetch/fetch.c:173: warning: ANSI C does not support the `ll' length modifier /flat/src/usr.bin/fetch/fetch.c: In function `fetch': /flat/src/usr.bin/fetch/fetch.c:301: warning: ANSI C does not support the `ll' length modifier /flat/src/usr.bin/fetch/fetch.c:339: warning: ANSI C does not support the `ll' length modifier /flat/src/usr.bin/fetch/fetch.c:339: warning: ANSI C does not support the `ll' length modifier /flat/src/usr.bin/fetch/fetch.c:358: warning: ANSI C does not support the `ll' length modifier /flat/src/usr.bin/fetch/fetch.c:361: warning: ANSI C does not support the `ll' length modifier /flat/src/usr.bin/fetch/fetch.c:394: warning: ANSI C does not support the `ll' length modifier /flat/src/usr.bin/fetch/fetch.c:394: warning: ANSI C does not support the `ll' length modifier /flat/src/usr.bin/fetch/fetch.c:509: warning: ANSI C does not support the `ll' length modifier /flat/src/usr.bin/fetch/fetch.c:509: warning: ANSI C does not support the `ll' length modifier /flat/src/usr.bin/fetch/fetch.c: In function `main': /flat/src/usr.bin/fetch/fetch.c:757: `vtty' undeclared (first use in this function) /flat/src/usr.bin/fetch/fetch.c:757: (Each undeclared identifier is reported only once /flat/src/usr.bin/fetch/fetch.c:757: for each function it appears in.) *** Error code 1 1 error -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
5.0current
is it possible to use the 5.0-current kernel with releases such as 4.3? I would like to take advantage of the SMP optimizations that are in 5.0current. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 5.0current
On 27.05.2001 04:51:58 +, Matt Bedynek wrote: is it possible to use the 5.0-current kernel with releases such as 4.3? No. I would like to take advantage of the SMP optimizations that are in 5.0current. You would like to upgrade your whole system then. http://www.freebsd.org/doc/en_US.ISO_8859-1/books/handbook/cutting-edge.html /Michael -- Michael Lyngbøl -- michael at lyngbol dot dk TDC Tele Danmark, DataNetworks, IP section To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 5.0current
On Sun, May 27, 2001 at 04:51:58AM -0500, Matt Bedynek wrote: is it possible to use the 5.0-current kernel with releases such as 4.3? I would like to take advantage of the SMP optimizations that are in 5.0current. No. Kris PGP signature
Strange DNS behavior; I'm stumped
Terry, thanks a lot for taking the time to attack my DNS problem. I think, however, that there's something fishy with either my DNS setup or FreeBSD's new nsswitch configuration. # Make your test program do a gethostbyname(), like it does. # # Then take the resulting IP address, and call gethostbyaddr(), # to get the _canonical_ name and IP address of the host you # obtained by name, so that it will give you the A record name # of the host, instead of some CNAMe which may be transient. # # Now watch your modem dial out, because you have not set up # correct in-addr.arpa delegations for all of your local IP # addresses in your DNS server. # # Now look up. See the lightbulb. Hmm. Pardon my blindness, what I don't understand is that 1) My 4.3-RC#0 system does not show that behavior; it's configured the old way with /etc/host.conf. Starting ctwm there does not lead to the resolver doing a remote ns query. 2) The DNS query causing dial out requests an A record for hal9000.schweikhardt.net. and not a reverse lookup for whatever.in-addr.arpa: 19:19:36.504837 IP 74: 213.7.20.247.1025 129.143.1.1.53: 34068+ A? +hal9000.schweikhardt.net. (42) In fact there is no reverse lookup among the first dozen or so packets. 3) The ctwm sources only have one call to gethostbyname(), none for gethostbyaddr, so it's not as anal as one would think. The lines are XmuGetHostname(client, MAXHOSTNAME); hostname = gethostbyname(client); I'm not sure if XmuGetHostname could be the culprit. [Setting up a caching-only server] Before I do that I want to track down what has changed. I still believe that when my DNS works properly with 4.3 it should as well with 5.0 without jumping through this hoop. Regards, Jens -- Jens Schweikhardt http://www.schweikhardt.net/ SIGSIG -- signature too long (core dumped) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Q) lock order reversal
Hi, I've got exactly the same with a 5.0-20010514-CURRENT snapshot from current.freebsd.org. BTW, it is running on a notebook, and the newcard kernel runs very well, nice job ! -- --- -- [EMAIL PROTECTED] --- - Original Message - From: Takeshi Ken Yamada [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Sunday, May 27, 2001 3:42 AM Subject: Q) lock order reversal Hi! With recent -current kernel, I get message below with P3@800Mhz X 2 when booting up. What is wrong? lock order reversal 1st 0xc04d4ac0 mntvnode @ ../../ufs/ffs/ffs_vfsops.c 1007 2nd 0xdb3001ac vnode interlock @ ../../ufs/ffs/ffs_vfsops.c 1016 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
Re: 5.0current
In the last episode (May 27), Matt Bedynek said: is it possible to use the 5.0-current kernel with releases such as 4.3? I would like to take advantage of the SMP optimizations that are in 5.0current. -current is too unstable at the moment to try and use on a production system, and I don't think SMP is any faster than 4.* right now, either. Most of the kernel still requires the Giant lock. -- Dan Nelson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Laptop locks up during pci initialization
I recently purchased a new Toshiba Satellite 2805 laptop, and I'm trying to install -current on it =) When I tried to install from the -current snapshots they all would lockup just after 'pcib0: ...' was printed. So I tried a 4-stable snapshot and that worked perfectly. However, I'm now trying to upgrade to -current, but it still locks up in the kernel when trying to initialize the pci bus. The following are the last lines of a verbose boot just before it locks up: pcib0: Intel 82443BX (440 BX) host to PCI bridge at pcibus 0 on motherboard pci0: physical bus=0 map[10]: type 3, range 32, base e, size 27, enabled found- vendor=0x8086, dev=0x7190, revid=0x03 bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 ( Then three more devices it finds, and then this is the last one: found- vendor=0x8086, dev=0x7112, revid=0x01 bus=0, slot=5, func=2 class=0c-03-00, hdrtype=0x00, mfdev=0 intpin=d, irq=11 When looking at pciconf this last device is my USB UHCI controller, but I don't have it in my kernel: uhci0@pci0:5:2: class=0x0c0300 card=0x chip=0x71128086 rev=0x01 hdr=0x00 Now, when I recompile the kernel without `device pci' it boots fine without any lockups. Is anyone else having similar problems? I looked through the archives but couldn't find anyone else with similar problems. It looks like it's been broken for awhile as I tried current snapshots back to March 1, and they all locked up at the same place. I'll be glad to try any patches to try and get this working. You could try disabling the PCI BIOS calls; set machdep.bios.pci=disable at the loader prompt. Let me know if this helps; I'd want to track this further if it does. Regards, Mike -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
panic: fdrop: count 0
based on source code cvsup'd today:
panic+0xc8
fdrop+0x32
closef+0x9b
close+0x89
syscall+0x645
syscall_with_err_pushd+0x1b
Marc G. Fournier [EMAIL PROTECTED]
Systems Administrator @ hub.org
scrappy@{postgresql|isc}.org ICQ#7615664
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: Laptop locks up during pci initialization
On 27-May-2001 Mike Smith wrote: | You could try disabling the PCI BIOS calls; | | set machdep.bios.pci=disable | | at the loader prompt. Let me know if this helps; I'd want to track this | further if it does. Yes, this works =) Mike -- Mike Heffner [EMAIL PROTECTED] Fredericksburg, VA [EMAIL PROTECTED] http://filebox.vt.edu/users/mheffner PGP signature
Re: panic: fdrop: count 0
Just tried to do a buildworld with a May 24th kernel and it did it there
also ...
On Sun, 27 May 2001, Marc G. Fournier wrote:
based on source code cvsup'd today:
panic+0xc8
fdrop+0x32
closef+0x9b
close+0x89
syscall+0x645
syscall_with_err_pushd+0x1b
Marc G. Fournier [EMAIL PROTECTED]
Systems Administrator @ hub.org
scrappy@{postgresql|isc}.org ICQ#7615664
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Marc G. Fournier [EMAIL PROTECTED]
Systems Administrator @ hub.org
scrappy@{postgresql|isc}.org ICQ#7615664
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Linux_Base port work around for Current?
I am installing current on a new box and I need jkd. That basically means linux emulation. I haven't been able to build it for some time on current. I have used the submitted PR to upgrade it to 7.? and it has worked except I have problems with all other ports that need linux_base. Right now the only solution is the upgrade that I see. Three questions: Does anyone have a better way? Has the PR/patch for ports been changed in the last few weeks? Is there a chance that it will be committed shortly? If I remember, it has been there for a long time. Thanks, ed --- The illiterate of the 21st century will not be those who cannot read and write, but those who cannot learn, unlearn and relearn. --Alvin Toffler To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
make release failure
A make release failed here with: # touch release.8 Making fixit floppy. disklabel: ioctl DIOCWLABEL: Operation not supported by device Warning: Block size restricts cylinders per group to 6. Warning: 1216 sector(s) in last cylinder unallocated /dev/md0c: 2880 sectors in 1 cylinders of 1 tracks, 4096 sectors 1.4MB in 1 cyl groups (6 c/g, 12.00MB/g, 384 i/g) super-block backups (for fsck -b #) at: 32 2556 blocks Filesystem 1K-blocks UsedAvail Capacity iused ifree %iused Mounted on /dev/md0c1363 1297 6695% 266 11670% /mnt *** Filesystem is 1440 K, 66 left *** 4000 bytes/inode, 116 left cp: /usr/src/release/texts/FLOPPIES.TXT: No such file or directory *** Error code 1 Stop in /usr/src/release. *** Error code 1 Stop in /usr/src/release. ... ## John -- John Hay -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Linux_Base port work around for Current?
I am installing current on a new box and I need jkd. That basically means linux emulation. I haven't been able to build it for some time on current. I have used the submitted PR to upgrade it to 7.? and it has worked except I have problems with all other ports that need linux_base. Right now the only solution is the upgrade that I see. Three questions: Does anyone have a better way? Has the PR/patch for ports been changed in the last few weeks? Is there a chance that it will be committed shortly? If I remember, it has been there for a long time. It will stay there until I can upgrade the rest of the Linux ports to work with it, and its too big of a job for me alone. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: make release failure
On Sun, May 27, 2001 at 10:45:59PM +0200, John Hay wrote: This strongly smells like a side-effect of RELNOTESng that removed the 'texts' subdir in favor of generated .txt from .sgml source files Wilko A make release failed here with: # touch release.8 Making fixit floppy. disklabel: ioctl DIOCWLABEL: Operation not supported by device Warning: Block size restricts cylinders per group to 6. Warning: 1216 sector(s) in last cylinder unallocated /dev/md0c: 2880 sectors in 1 cylinders of 1 tracks, 4096 sectors 1.4MB in 1 cyl groups (6 c/g, 12.00MB/g, 384 i/g) super-block backups (for fsck -b #) at: 32 2556 blocks Filesystem 1K-blocks UsedAvail Capacity iused ifree %iused Mounted on /dev/md0c1363 1297 6695% 266 11670% /mnt *** Filesystem is 1440 K, 66 left *** 4000 bytes/inode, 116 left cp: /usr/src/release/texts/FLOPPIES.TXT: No such file or directory *** Error code 1 Stop in /usr/src/release. *** Error code 1 Stop in /usr/src/release. ... ## John -- John Hay -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message ---end of quoted text--- -- | / o / / _ Arnhem, The Netherlandsemail: [EMAIL PROTECTED] |/|/ / / /( (_) BultePowered by FreeBSD/alpha http://www.freebsd.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
latest panic ... procrunnable?
thank god for digital cameras ... current panic was while doing a simple
'make buildworld', no -j option ... based on most recent sources ...
cpid = 0; lapic.id =
instruction pointer = 0x8:0xc0179309
stack pointer = 0x10:0xcb350f60
frame pointer = 0x10:0xcb350f64
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, IOPL - 0
current process = 11 (idle: cpu0)
kernel: type 29 trap, code=0
Stopped at procrunnable+0xd: movl%ebp,%esp
db trace
procrunnable+0xd
idle_proc+0x1e
fork_exit+0xbc
fork_trampoline+0x8
db show pcpu 0
cpuid = 0
curproc = 0xcb346840: pid 11 idle: cpu0
curpcb = 0xcb34f000
npxproc = none
idleproc = 0xcb346840: pid 11 idle: cpu0
db show pcpu 1
cpuid = 1
curproc = 0xccf860e0: pid 37362 cpp0
curpcb = 0xccfe6000
npxproc = none
idleproc = 0xcb346a60: pid 10 idle: cpu1
Marc G. Fournier [EMAIL PROTECTED]
Systems Administrator @ hub.org
scrappy@{postgresql|isc}.org ICQ#7615664
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Bad superblock on file systems ...
anyone having a problem with that with -current kernels? where the kernel
panics, on reboot the superblock is screwed ... I can do a 'mount -a' to
recalculate, then an umount -a and 'fsck -y' to clean the file systems ...
I have softupdates enabled on all file systems except for /, if that
helps?
Marc G. Fournier [EMAIL PROTECTED]
Systems Administrator @ hub.org
scrappy@{postgresql|isc}.org ICQ#7615664
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: 5.0current
In message [EMAIL PROTECTED] Matt Bedynek writes: : is it possible to use the 5.0-current kernel with releases such as 4.3? : I would like to take advantage of the SMP optimizations that are in : 5.0current. Yes and No. The 4.3 binaries run fine, but many kernel interfaces have changed so you'll get lots of interesting problems. ps is the first, and there are likely others. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: recursed on non-recursive lock
On 26-May-01 Michael Harnois wrote: I finally got this much. I hope it helps. lock order reversal 1st 0xc03af0a0 mntvnode @ ../../ufs/ffs/ffs_vnops.c:1007 2nd 0xc8b539cc vnode interlock @ ../../ufs/ffs/ffs_vfsops.c:1016 recursed on non-recursive lock (sleep mutex) vm @ Please try http://www.FreeBSD.org/~jhb/patches/vm.patch it fixes several places where we hold the vm lock across VOP's, etc. -- 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
Re: recursed on non-recursive lock
On Sun, 27 May 2001 17:32:15 -0700 (PDT), John Baldwin [EMAIL PROTECTED] said: Please try http://www.FreeBSD.org/~jhb/patches/vm.patch it fixes several places where we hold the vm lock across VOP's, etc. Does that mean you've upgraded it? The last time I tried it (shortly after you announced it) it didn't apply cleanly. -- Michael D. Harnois[EMAIL PROTECTED] Redeemer Lutheran Church Washburn, Iowa Sed quis custodiet ipsos custodes? -- Juvenal To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: next panic: blockable sleep lock
On Sun, 27 May 2001 21:30:59 +0200, [EMAIL PROTECTED] said: The ui_ref member in struct uidinfo is only 16 bits. This means that a fatal wraparound due to a missing call to uifree() can happen rather quickly. Great! With your patch and the earlier one from Thomas I can build world again. In fact I built world and mozilla+ipv6 simultaneously, a pretty good workout. -- Michael D. Harnois[EMAIL PROTECTED] Redeemer Lutheran Church Washburn, Iowa Sed quis custodiet ipsos custodes? -- Juvenal To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
src/share/man/man9/devfs*.9
dima@hornet% ls -1 share/man/man9/devfs*.9 share/man/man9/devfs_add_devswf.9 share/man/man9/devfs_link.9 share/man/man9/devfs_remove_dev.9 The above man pages are for the old DEVFS written by Julian, and don't apply to the new one (the functions they describe don't exist). Any objections to a `cvs rm` of these? Dima Dorfman [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: make release failure
John Hay [EMAIL PROTECTED] writes: A make release failed here with: # touch release.8 Making fixit floppy. disklabel: ioctl DIOCWLABEL: Operation not supported by device Warning: Block size restricts cylinders per group to 6. Warning: 1216 sector(s) in last cylinder unallocated /dev/md0c: 2880 sectors in 1 cylinders of 1 tracks, 4096 sectors 1.4MB in 1 cyl groups (6 c/g, 12.00MB/g, 384 i/g) super-block backups (for fsck -b #) at: 32 2556 blocks Filesystem 1K-blocks UsedAvail Capacity iused ifree %iused Mount ed on /dev/md0c1363 1297 6695% 266 11670% /mnt *** Filesystem is 1440 K, 66 left *** 4000 bytes/inode, 116 left cp: /usr/src/release/texts/FLOPPIES.TXT: No such file or directory What revision of src/release/Makefile do you have? You want 1.618. *** Error code 1 Stop in /usr/src/release. *** Error code 1 Stop in /usr/src/release. ... ## John -- John Hay -- [EMAIL PROTECTED] 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
Re: freelist corruption
On 2001-May-27 20:36:54 -0700, Kris Kennaway [EMAIL PROTECTED] wrote: I've been getting rather a lot of these tonight..any ideas? May 27 18:52:06 xor /boot/kernel/kernel: Data modified on freelist: word 2 of object 0xc1a60100 size 64 previous type pagedep (0xd6adc0de != 0xdeadc0de) If this isn't an ECC system, it could be a flaky SIMM (or flaky cache). There's a single bit difference. (Though I'd expect more obvious problems if bit 27 was incorrectly reading as zero at a detectable rate). Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: make release failure
A make release failed here with:
#
touch release.8
Making fixit floppy.
disklabel: ioctl DIOCWLABEL: Operation not supported by device
Warning: Block size restricts cylinders per group to 6.
Warning: 1216 sector(s) in last cylinder unallocated
/dev/md0c: 2880 sectors in 1 cylinders of 1 tracks, 4096 sectors
1.4MB in 1 cyl groups (6 c/g, 12.00MB/g, 384 i/g)
super-block backups (for fsck -b #) at:
32
2556 blocks
Filesystem 1K-blocks UsedAvail Capacity iused ifree %iused Mount
ed on
/dev/md0c1363 1297 6695% 266 11670% /mnt
*** Filesystem is 1440 K, 66 left
*** 4000 bytes/inode, 116 left
cp: /usr/src/release/texts/FLOPPIES.TXT: No such file or directory
What revision of src/release/Makefile do you have? You want 1.618.
beast# fgrep '$FreeBSD' /usr/src/release/Makefile
# $FreeBSD: src/release/Makefile,v 1.618 2001/05/25 18:01:31 bmah Exp $
beast# fgrep 'texts/FLOPPIES.TXT' /usr/src/release/Makefile
@cp ${.CURDIR}/texts/FLOPPIES.TXT ${RD}/floppies/README.TXT
John
--
John Hay -- [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: freelist corruption
On Mon, May 28, 2001 at 01:48:33PM +1000, Peter Jeremy wrote: On 2001-May-27 20:36:54 -0700, Kris Kennaway [EMAIL PROTECTED] wrote: I've been getting rather a lot of these tonight..any ideas? May 27 18:52:06 xor /boot/kernel/kernel: Data modified on freelist: word 2 of object 0xc1a60100 size 64 previous type pagedep (0xd6adc0de != 0xdeadc0de) If this isn't an ECC system, it could be a flaky SIMM (or flaky cache). There's a single bit difference. (Though I'd expect more obvious problems if bit 27 was incorrectly reading as zero at a detectable rate). Could be, but I'm not having other problems on this system which I'd attribute to bad memory. Kris PGP signature
Re: make release failure
John Hay [EMAIL PROTECTED] writes:
A make release failed here with:
#
touch release.8
Making fixit floppy.
disklabel: ioctl DIOCWLABEL: Operation not supported by device
Warning: Block size restricts cylinders per group to 6.
Warning: 1216 sector(s) in last cylinder unallocated
/dev/md0c: 2880 sectors in 1 cylinders of 1 tracks, 4096 sectors
1.4MB in 1 cyl groups (6 c/g, 12.00MB/g, 384 i/g)
super-block backups (for fsck -b #) at:
32
2556 blocks
Filesystem 1K-blocks UsedAvail Capacity iused ifree %iused M
ount
ed on
/dev/md0c1363 1297 6695% 266 11670% /
mnt
*** Filesystem is 1440 K, 66 left
*** 4000 bytes/inode, 116 left
cp: /usr/src/release/texts/FLOPPIES.TXT: No such file or directory
What revision of src/release/Makefile do you have? You want 1.618.
beast# fgrep '$FreeBSD' /usr/src/release/Makefile
# $FreeBSD: src/release/Makefile,v 1.618 2001/05/25 18:01:31 bmah Exp $
beast# fgrep 'texts/FLOPPIES.TXT' /usr/src/release/Makefile
@cp ${.CURDIR}/texts/FLOPPIES.TXT ${RD}/floppies/README.TXT
Could you please try the attached, untested patch? I don't know
enough about the release build process to know if it should work, but
I guess it's worth a shot. Bruce Mah (cc'd) should know whether it's
the Right(tm) fix.
Thanks,
Dima Dorfman
[EMAIL PROTECTED]
Index: Makefile
===
RCS file: /stl/src/FreeBSD/src/release/Makefile,v
retrieving revision 1.618
diff -u -r1.618 Makefile
--- Makefile2001/05/25 18:01:31 1.618
+++ Makefile2001/05/28 04:03:26
@@ -694,7 +694,8 @@
@sh -e ${.CURDIR}/scripts/doFS.sh ${RD}/floppies/fixit.flp ${RD} \
${MNT} ${FIXITSIZE} ${RD}/fixitfd ${FIXITINODE} ${FIXITLABEL}
# Do our last minute floppies directory setup in a convenient place.
- @cp ${.CURDIR}/texts/FLOPPIES.TXT ${RD}/floppies/README.TXT
+ @cp ${.CURDIR}/doc/${RELNOTES_LANG}/readme/article.txt \
+ ${RD}/floppies/README.TXT
@(cd ${RD}/floppies; md5 README.TXT *.flp CHECKSUM.MD5)
touch release.9
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: freelist corruption
Peter Jeremy wrote: On 2001-May-27 20:36:54 -0700, Kris Kennaway [EMAIL PROTECTED] wrote: I've been getting rather a lot of these tonight..any ideas? May 27 18:52:06 xor /boot/kernel/kernel: Data modified on freelist: word 2 of object 0xc1a60100 size 64 previous type pagedep (0xd6adc0de != 0xdeadc0de) If this isn't an ECC system I got one of these on my ECC system: May 25 01:16:20 kern.crit Master /boot/kernel/kernel: Data modified on freelist: word 2 of object 0xc1a58dc0 size 52 previous type vfscache (0xd6adc0de != 0xdeadc0de) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
-current is _definitely_ not stable right now
Gang,
I cvs'ed and built world/kernel shortly after jhb's all clear on
thursday, and things went fairly well. I did the same again after rwatson's
mutex commits on friday and things have gone downhill from there. Just
about any heavy system activity locks the system up. That includes things
like building large ports (for example, avifile), buildworld, and trying to
actually run aviplay.
On the avi front, typing 'aviplay' with or without an argument is
guaranteed to instantly wedge the box. I attached a lot of running aviplay
through truss, but I have no way to know if it stopped at or before the
offending instruction. As for the general wonkiness of the system, I have
finally gotten a dump. The backtrace is below, let me know if there is
anything else I can do to help debug.
Doug
(kgdb) where
#0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:478
#1 0xc01cb318 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:321
#2 0xc01cb745 in panic (fmt=0xc0330ce4 mutex %s recursed at %s:%d)
at /usr/src/sys/kern/kern_shutdown.c:600
#3 0xc01c3c9c in _mtx_assert (m=0xc03f44a0, what=9,
file=0xc0332360 /usr/src/sys/kern/kern_synch.c, line=858)
at /usr/src/sys/kern/kern_mutex.c:571
#4 0xc01d4b9d in mi_switch () at /usr/src/sys/kern/kern_synch.c:858
#5 0xc01cb01c in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:262
#6 0xc01cb745 in panic (fmt=0xc0334760 blockable sleep lock (%s) %s @
%s:%d)
at /usr/src/sys/kern/kern_shutdown.c:600
#7 0xc01e60a0 in witness_lock (lock=0xc03f0f60, flags=0,
file=0xc0331123 /usr/src/sys/kern/kern_proc.c, line=146)
at /usr/src/sys/kern/subr_witness.c:489
#8 0xc01d2285 in _sx_slock (sx=0xc03f0f60, file=0xc0331123
/usr/src/sys/kern/kern_proc.c,
line=146) at /usr/src/sys/kern/kern_sx.c:114
#9 0xc01c4e2c in pfind (pid=434) at /usr/src/sys/kern/kern_proc.c:146
#10 0xc01ea3c6 in selwakeup (sip=0xc0e3d404) at
/usr/src/sys/kern/sys_generic.c:1175
#11 0xc01f5c5f in ptcwakeup (tp=0xc0e3d420, flag=1) at
/usr/src/sys/kern/tty_pty.c:317
#12 0xc01f5c36 in ptsstart (tp=0xc0e3d420) at
/usr/src/sys/kern/tty_pty.c:306
#13 0xc01f3074 in ttstart (tp=0xc0e3d420) at /usr/src/sys/kern/tty.c:1409
#14 0xc01f4685 in tputchar (c=107, tp=0xc0e3d420) at
/usr/src/sys/kern/tty.c:2458
#15 0xc01e20cb in putchar (c=107, arg=0xcd115de8) at
/usr/src/sys/kern/subr_prf.c:304
#16 0xc01e234a in kvprintf (fmt=0xc034f881 ernel trap %d with interrupts
disabled\n,
func=0xc01e207c putchar, arg=0xcd115de8, radix=10, ap=0xcd115e00
\f)
at /usr/src/sys/kern/subr_prf.c:487
#17 0xc01e1ff8 in printf (fmt=0xc034f880 kernel trap %d with interrupts
disabled\n)
at /usr/src/sys/kern/subr_prf.c:260
#18 0xc02f6955 in trap (frame={tf_fs = -854523880, tf_es = -1071775728,
tf_ds = -855048176,
tf_edi = 4, tf_esi = -1058806500, tf_ebp = -854499712, tf_isp =
-854499744,
tf_ebx = -855029664, tf_edx = -559038242, tf_ecx = 2, tf_eax =
-559038244,
tf_trapno = 12, tf_err = 0, tf_eip = -1071892410, tf_cs = 8,
tf_eflags = 65670,
tf_esp = -1052624640, tf_ss = -1058806528}) at
/usr/src/sys/i386/i386/trap.c:253
#19 0xc01c3846 in _mtx_lock_sleep (m=0xc0e3e51c, opts=0,
file=0xc0331500 /usr/src/sys/kern/kern_resource.c, line=793)
at /usr/src/sys/kern/kern_mutex.c:380
#20 0xc01ca0cb in uihold (uip=0xc0e3e500) at
/usr/src/sys/kern/kern_resource.c:793
#21 0xc01c86f9 in crdup (cr=0xc1423900) at
/usr/src/sys/kern/kern_prot.c:1349
#22 0xc021cf8c in access (p=0xcd094860, uap=0xcd115f80)
at /usr/src/sys/kern/vfs_syscalls.c:1712
#23 0xc02f841d in syscall (frame={tf_fs = 47, tf_es = 47, tf_ds = 47,
tf_edi = 134665044,
tf_esi = 134676528, tf_ebp = -1077940088, tf_isp = -854499372, tf_ebx
= 134661184,
tf_edx = 134665044, tf_ecx = 134661218, tf_eax = 33, tf_trapno = 12,
tf_err = 2,
tf_eip = 134555356, tf_cs = 31, tf_eflags = 643, tf_esp =
-1077940132, tf_ss = 47})
at /usr/src/sys/i386/i386/trap.c:1172
#24 0xc02e957d in syscall_with_err_pushed ()
#25 0x804a131 in ?? ()
#26 0x804caa1 in ?? ()
#27 0x804e57c in ?? ()
#28 0x804dd54 in ?? ()
#29 0x804e57c in ?? ()
#30 0x804dd54 in ?? ()
#31 0x804e57c in ?? ()
#32 0x804dd54 in ?? ()
#33 0x804e57c in ?? ()
#34 0x804dd54 in ?? ()
#35 0x804c880 in ?? ()
#36 0x804fd4a in ?? ()
#37 0x8048131 in ?? ()
__sysctl(0xbfbff830,0x2,0x28083128,0xbfbff82c,0x0,0x0) = 0 (0x0)
mmap(0x0,32768,0x3,0x1002,-1,0x0)= 671629312 (0x28084000)
geteuid()= 1000 (0x3e8)
getuid() = 1000 (0x3e8)
getegid()= 1000 (0x3e8)
getgid() = 1000 (0x3e8)
access(/usr/local/lib/libqt2-mt.so,0) ERR#2 'No such file or directory'
open(/var/run/ld-elf.so.hints,0,00)= 3 (0x3)
read(0x3,0xbfbff810,0x80)= 128 (0x80)
lseek(3,0x80,0) = 128 (0x80)
read(0x3,0x28088000,0x37)
RE: Bad superblock on file systems ...
I'll add a 'me too'. I've been doing the same workaround with success, but
it's still very frustrating. I can also guarantee a softdep freelist panic
about 1/4 the way into a buildworld. I can provide a trace if anyone is
interested.
Scott
-Original Message-
From: Marc G. Fournier
To: [EMAIL PROTECTED]
Sent: 5/27/01 5:05 PM
Subject: Bad superblock on file systems ...
anyone having a problem with that with -current kernels? where the
kernel
panics, on reboot the superblock is screwed ... I can do a 'mount -a' to
recalculate, then an umount -a and 'fsck -y' to clean the file systems
...
I have softupdates enabled on all file systems except for /, if that
helps?
Marc G. Fournier [EMAIL PROTECTED]
Systems Administrator @ hub.org
scrappy@{postgresql|isc}.org ICQ#7615664
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
softupdates related problem in -current
Another problem I'm having in -current right now is with softupdates. When the system panic'ed the first time, it came up ok and fsck'ed fine with no apparent loss of data. However, during the fsck it complained bitterly about my superblocks, and when it was done and the system booted, the softupdates attribute was missing from the filesystems that had it set. FYI, Doug To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
