Re: panic: softdep_setup_inomapdep: found inode
Hi,
I had another one of these panics. The previous one was with -current
of CVSupped in early January, this one is with -current of February 6.
The panic seems to be triggered when I do a filesystem copy to an
online disk for backup purposes, like this:
newfs /dev/ad2s5e
tunefs -n enable /dev/ad2s5e
fsck /dev/ad2s5e
mount /dev/ad2s5e /mnt
cd /mnt
dump 0uaf - /home/hunter | restore -rf -
See below for details of the panic. BTW, has the infamous bremfree:
bp 0xx not locked during the sync during the panic been fixed
yet?
--
Georg.
hunter# gdb --kernel -symbols=kernel.debug --core=vmcore.17 --exec=kernel.17
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB. Type show warranty for details.
This GDB was configured as i386-unknown-freebsd...Deprecated bfd_read called at
/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb/dbxread.c line 2629
in elfstab_build_psymtabs
Deprecated bfd_read called at
/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb/dbxread.c line 935
in fill_symbuf
IdlePTD at phsyical address 0x0046b000
initial pcb at physical address 0x00373380
panicstr: bremfree: bp 0xd27c5d0c not locked
panic messages:
---
panic: softdep_setup_inomapdep: found inode
syncing disks... panic: bremfree: bp 0xd27c5d0c not locked
Uptime: 1h47m41s
/dev/vmmon: Module vmmon: unloaded
dumping to dev ad0s2b, offset 2000128
dump ata0: resetting devices .. done
1023 1022 1021...
---
#0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:504
504 if (!dodump)
(kgdb) where
#0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:504
#1 0xc01bc2df in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:336
#2 0xc01bc769 in panic (fmt=0xc02f9b82 bremfree: bp %p not locked)
at /usr/src/sys/kern/kern_shutdown.c:646
#3 0xc01ec1b5 in bremfree (bp=0xd27c5d0c) at /usr/src/sys/kern/vfs_bio.c:545
#4 0xc01ee3fd in getblk (vp=0xe5399760, blkno=96, size=16384, slpflag=0,
slptimeo=0) at /usr/src/sys/kern/vfs_bio.c:2220
#5 0xc01ec28c in breadn (vp=0xe5399760, blkno=96, size=16384, rablkno=0x0,
rabsize=0x0, cnt=0, cred=0x0, bpp=0xe54ca8f4)
at /usr/src/sys/kern/vfs_bio.c:603
#6 0xc01ec259 in bread (vp=0xe5399760, blkno=96, size=16384, cred=0x0,
bpp=0xe54ca8f4) at /usr/src/sys/kern/vfs_bio.c:585
#7 0xc027550c in ffs_update (vp=0xe5b028c0, waitfor=0)
at /usr/src/sys/ufs/ffs/ffs_inode.c:101
#8 0xc0282432 in ffs_fsync (ap=0xe54ca968)
at /usr/src/sys/ufs/ffs/ffs_vnops.c:292
#9 0xc0280bee in ffs_sync (mp=0xc61ce200, waitfor=2, cred=0xc2064c00,
td=0xc033f884) at vnode_if.h:441
#10 0xc01f8be9 in sync (td=0xc033f884, uap=0x0)
at /usr/src/sys/kern/vfs_syscalls.c:669
#11 0xc01bbf28 in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:245
#12 0xc01bc769 in panic (fmt=0xc030bec0 softdep_setup_inomapdep: found inode)
at /usr/src/sys/kern/kern_shutdown.c:646
#13 0xc027a026 in softdep_setup_inomapdep (bp=0xd2902014, ip=0xc7ef4d00,
newinum=197060) at /usr/src/sys/ufs/ffs/ffs_softdep.c:1220
#14 0xc02738f0 in ffs_nodealloccg (ip=0xc7ef4d00, cg=18, ipref=196992,
mode=16832) at /usr/src/sys/ufs/ffs/ffs_alloc.c:1408
#15 0xc027294b in ffs_hashalloc (ip=0xc7ef4d00, cg=18, pref=196992,
size=16832, allocator=0xc02736f8 ffs_nodealloccg)
at /usr/src/sys/ufs/ffs/ffs_alloc.c:888
#16 0xc02723dc in ffs_valloc (pvp=0xe5ab4720, mode=16832, cred=0xc7f14d00,
vpp=0xe54caac8) at /usr/src/sys/ufs/ffs/ffs_alloc.c:628
#17 0xc0288dbe in ufs_mkdir (ap=0xe54cac14)
at /usr/src/sys/ufs/ufs/ufs_vnops.c:1382
#18 0xc0289f45 in ufs_vnoperate (ap=0xe54cac14)
at /usr/src/sys/ufs/ufs/ufs_vnops.c:2657
#19 0xc01fc758 in vn_mkdir (path=0x80a6eff ./atria/examples/clearcase/logs,
mode=511, segflg=UIO_USERSPACE, td=0xe5412f04) at vnode_if.h:537
#20 0xc01fc57d in mkdir (td=0xe5412f04, uap=0xe54cad20)
at /usr/src/sys/kern/vfs_syscalls.c:3102
#21 0xc02c106c in syscall (frame={tf_fs = 1179695, tf_es = -1078001617,
tf_ds = -1078001617, tf_edi = 0, tf_esi = 140152896,
tf_ebp = -1077946252, tf_isp = -447959692, tf_ebx = 134901503,
tf_edx = 2, tf_ecx = 2, tf_eax = 136, tf_trapno = 12, tf_err = 2,
tf_eip = 134556851, tf_cs = 31, tf_eflags = 659, tf_esp = -1077946296,
tf_ss = 47}) at /usr/src/sys/i386/i386/trap.c:1034
#22 0xc02b52fd in syscall_with_err_pushed ()
#23 0x804a214 in ?? ()
#24 0x804b183 in ?? ()
#25 0x804b325 in ?? ()
#26 0x804b325
Re: ThinkPad X22 PC-Card slot problem
Sorry for late reply. I didn't have time to test it. From: M. Warner Losh [EMAIL PROTECTED] Date: Thu, 07 Feb 2002 10:04:35 -0700 (MST) Yes. This is the ISA problem. The checks are there to make sure we don't assign addresses that aren't decoded by the bridge. However, the bridge does decode ISA addresses. I need to check into which ISA stuff a little better before making a fix. Revision ChangesPath 1.7 +30 -14src/sys/dev/pci/pci_pci.c This fixed half of the problem, thank you. However, X22's PCICs (yes two PCICs) request to use 0x5000-0x5fff and 0x5000-0x5fff where the bridge does not know. So I still need PCI_ALLOW_UNSUPPORTED_IO_RANGE. pcib1: PCI-PCI bridge at device 1.0 on pci0 pcib1: secondary bus 1 pcib1: subordinate bus 1 pcib1: I/O decode0x3000-0x3fff pcib1: memory decode 0xc010-0xc01f pcib1: prefetched decode 0xe000-0xe7ff pci1: physical bus=1 map[10]: type 3, range 32, base e000, size 27, enabled map[14]: type 4, range 32, base 3000, size 8, enabled map[18]: type 1, range 32, base c010, size 16, enabled found- vendor=0x1002, dev=0x4c59, revid=0x00 bus=1, slot=0, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 intpin=a, irq=11 powerspec 2 supports D0 D1 D2 D3 current D0 : pcic0: Ricoh RL5C476 PCI-CardBus Bridge mem 0x5000-0x5fff irq 11 at device 3.0 on pci2 pcib2: device pcic0 requested unsupported memory range 0x5000-0x5fff ( decoding 0xc020-0xcfff, 0xe800-0xf00f) pcib2: device pcic0 requested decoded memory range 0x5000-0x5fff // Noriaki Mitsunaga // To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Current - Kernel compile missing opt_compat.h - cvsup this morning
Today's make buildkernel seems to break because of a missing opt_compat.h. mkdep -f .depend -a -nostdinc -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@ /dev -I@/../include -I/usr/obj/usr/src/i386/usr/include /usr/src/sys/modules/di gi/digi/../../../dev/digi/digi.c /usr/src/sys/modules/digi/digi/../../../dev/dig i/digi_pci.c /usr/src/sys/modules/digi/digi/../../../dev/digi/digi_isa.c /usr/src/sys/modules/digi/digi/../../../dev/digi/digi.c:38: opt_compat.h: No suc h file or directory mkdep: compile failed *** Error code 1 Stop in /usr/src/sys/modules/digi/digi. *** Error code 1 ed --- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Current - Kernel compile missing opt_compat.h - cvsup thismorning
On Fri, 15 Feb 2002, Edwin Culp wrote: Today's make buildkernel seems to break because of a missing opt_compat.h. mkdep -f .depend -a -nostdinc -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@ /dev -I@/../include -I/usr/obj/usr/src/i386/usr/include /usr/src/sys/modules/di gi/digi/../../../dev/digi/digi.c /usr/src/sys/modules/digi/digi/../../../dev/dig i/digi_pci.c /usr/src/sys/modules/digi/digi/../../../dev/digi/digi_isa.c /usr/src/sys/modules/digi/digi/../../../dev/digi/digi.c:38: opt_compat.h: No suc h file or directory mkdep: compile failed *** Error code 1 Fixed. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ports/34908: libpng port makes bad dynamic library on -CURRENT
Interesting. Is the DF_TEXTREL flag set in DT_FLAGS instead? Is the
library linked w/ -enable-new-dtags? Are the new dtags enabled by
default in the new binutils? Someting in elf32.em?
No. DT_FLAGS entry is not created regardless of whether the
--enable-new-dtags parameter has been passed to the linker. Ld simply
ignores dynamic relocation entries for local symbols while checking
whether either DT_FLAGS or DT_TEXTREL should be created. Attached
patch appears to fix the problem for me and has not caused any
problems on my test box so far but I am not making any claims about
its correctness. Use on your own risk.
Are the new dtags enabled by default in the new binutils?
No, it seems like the new dtags are disabled by default.
Index: bfd/elf32-i386.c
===
RCS file: /usr/ncvs/src/contrib/binutils/bfd/elf32-i386.c,v
retrieving revision 1.11
diff -u -r1.11 elf32-i386.c
--- bfd/elf32-i386.c27 Jan 2002 12:07:38 - 1.11
+++ bfd/elf32-i386.c15 Feb 2002 17:21:54 -
@@ -1506,6 +1506,10 @@
}
else
{
+ asection *s = p-sec-output_section;
+ if (s != NULL (s-flags SEC_READONLY) != 0)
+ info-flags |= DF_TEXTREL;
+
srel = elf_section_data (p-sec)-sreloc;
srel-_raw_size += p-count * sizeof (Elf32_External_Rel);
}
RE: USB detach crashes possibly fixed
On 14-Feb-2002 (08:29:50/GMT) Brian Fundakowski Feldman wrote:
Please try this change (already committed to -CURRENT) and let me
know if crashes due to detaching USB devices specifically have been
eliminated.
I cvsupped on Feb 14, 20:21 CET (GMT+1, Italian time), recompiled
both world kernel (yes, runned mergemaster also :-) and messages
show that device attach and detach (before I got only attach)
...kernel: uscanner0: EPSON Perfection1240, rev 1.00/1.14, addr 2
...kernel: uscanner0: at uhub0 port 1 (addr 2) disconnected
...kernel: uscanner0: detached
_BUT_
I lost /dev/speaker. I don't know if this is related to patch but
with my previous installed build (a bit old, of December 11, 2001)
I have those lines on /etc/usbd.conf:
attach /bin/chmod 666 /dev/${DEVNAME} echo L16cce /dev/speaker
detach echo L16eec /dev/speaker
and I got a small tune on attach but nothing on detach.
Now I am unable to play notes on /dev/speaker. Any hint?
TIA,
Riccardo.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Don't remove sc.0 from hints...
...or strange things happens. When trying to discover why /dev/speaker disappears from my last build (cvsupped on Feb 14, 20:21 CET) I commented sc.0 lines on /boot/device.hints. Big mistake :-) I think some sort of auto-pilot must stop this. Initial boot without sc.0 hint hide all highlight messages, going from Booting [/boot/kernel/kernel]... directly to login: prompt. And playing with vi and scroll back and forward (on console) lead me to an automatic reboot without and message (neither crash nor panic). I just uncommented sc.0 lines and all go right way, pfiuu :-) Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Don't remove sc.0 from hints...
In the last episode (Feb 15), Riccardo Torrini said: ...or strange things happens. When trying to discover why /dev/speaker disappears from my last build (cvsupped on Feb 14, 20:21 CET) I commented sc.0 lines on /boot/device.hints. Big mistake :-) Same thing wrt floppy devices, I think. If you don't have hints lines, they don't get probed. If you find out what killed /dev/speaker, let us know, too :) -- Dan Nelson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
-CURRENT / ATA Drivers SCSI Devices
I noticed a thread on Current several weeks ago about a problem someone was having with the ATA driver(s) in CURRENT and SCSI disk drivers. I have had the same problem recently on FreeBSD / Current with a Dell 410 Precision Workstation that uses an Adaptec AIC-7890 Ultra2/Wide. I re-'cvsup'd' and rebuild everything twice (using and old backup kernel from Current of a month or so ago) and go the same kind of 'panic' as described earlier. I read the thread on the problem, and finally commented out the 'ATA' Drivers in the Kernel config file and rebooted and had no problems at all. There *does* appear to be a problem with the ATA driver(s) in -Current and SCSI device interaction that has developed in the last week or so it seems Glenn Gombert [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Don't remove sc.0 from hints...
On Fri, Feb 15, 2002 at 10:56:17PM +0100, Riccardo Torrini wrote: ...or strange things happens. When trying to discover why /dev/speaker disappears from my last build (cvsupped on Feb 14, 20:21 CET) I commented sc.0 lines on /boot/device.hints. Big mistake :-) I think some sort of auto-pilot must stop this. Initial boot without sc.0 hint hide all highlight messages, going from You only need sc.0 if you are running graphic console. It is not always true and some people are using machines without graphic cards. Additionaly some people use vt as an alternative to sc. How can an auto-pilot know that you need sc? Booting [/boot/kernel/kernel]... directly to login: prompt. And playing with vi and scroll back and forward (on console) lead me to an automatic reboot without and message (neither crash nor panic). I just uncommented sc.0 lines and all go right way, pfiuu :-) You can still manualy add them on the loader prompt or switch to a serial console. -- B.Walter COSMO-Project http://www.cosmo-project.de [EMAIL PROTECTED] Usergroup [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Current/XFree86 w/gnome or kde coredumps.
I had the same problem with the version of XFree86 that is now in the ports collection, I installed an earlier version of XFree86-4.1.) that I had from last Fall last week and it appears to work fine...something that changed recently in XFree86 (or Current) appears to be causing the problem At 07:28 PM 2/14/2002 -0800, Edwin Culp wrote: I just realized that current/XFree86-4.1.0_12,1 core dumps with either kde or gnome. I seems to work fine with twm. It dumps at the same place when starting x with both. (II) XINPUT: Adding extended input device Mouse1 (type: MOUSE) Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/, removing from list! Bus error - core dumped Any suggestions would be appreciated. I haven't rebooted for several days so I don't know when it started. thanks, ed --- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message Glenn Gombert [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Current/XFree86 w/gnome or kde coredumps.
I suspected that because I just upgraded to the latest and greatest:-) unless 4.2 comes back soon. I've found that several other programs like mplayer are also coredumping. I guess my decision is now to go forward to 4.2 or back. Thanks for confirming that I'm not the only one. :-) ed Quoting Glenn Gombert [EMAIL PROTECTED]: I had the same problem with the version of XFree86 that is now in the ports collection, I installed an earlier version of XFree86-4.1.) that I had from last Fall last week and it appears to work fine...something that changed recently in XFree86 (or Current) appears to be causing the problem At 07:28 PM 2/14/2002 -0800, Edwin Culp wrote: I just realized that current/XFree86-4.1.0_12,1 core dumps with either kde or gnome. I seems to work fine with twm. It dumps at the same place when starting x with both. (II) XINPUT: Adding extended input device Mouse1 (type: MOUSE) Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/, removing from list! Bus error - core dumped Any suggestions would be appreciated. I haven't rebooted for several days so I don't know when it started. thanks, ed --- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message Glenn Gombert [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message Never attribute to malice that which is adequately explained by stupidity.:-) --- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Ethernet tunnel device
Hi Terry, On Wed, Feb 13, 2002 at 04:59:41PM -0800, Terry Lambert wrote: There's one difference between vmware and a little hacked up test app. Linux emulation. It certaintly shouldn't matter, but it might be worth compiling the test program on a linux machine and seeing it it leaves the device in a weird state like vmware. Maybe it's losing an open instance in the resource track on close? That seems the most likely culprit... Do you mean in the linux emu case? If so, please see my message stating that I also used a linux emu program to test this. If not, can you please be a bit more detailed? Thanks alot. Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Don't remove sc.0 from hints...
On 15-Feb-2002 (22:17:10/GMT) Dan Nelson wrote: Same thing wrt floppy devices, I think. If you don't have hints lines, they don't get probed. hint.fdc.0.at=isa hint.fdc.0.port=0x3F0 hint.fdc.0.irq=6 hint.fdc.0.drq=2 hint.fd.0.at=fdc0 hint.fd.0.drive=0 May be. Or not. Even with _all_ this lines commented I get the floppy controller detected (but no floppy drive). Anyway... please please please, I want /dev/speaker back :-( Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Why isn't PAM_smb available for FreeBSD?
hi all, I was wondering, after seeing that Linux has pam_smb, why can't FreeBSD have it too. I can get the pam_smb compiling under FreeBSD, from http://www.samba.org, so I was wondering why it isn't in our CVS tree. Thanks, Regards, -- Hiten Pandya -- [EMAIL PROTECTED] __ Do You Yahoo!? Yahoo! Sports - Coverage of the 2002 Olympic Games http://sports.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Why isn't PAM_smb available for FreeBSD?
On Fri, 15 Feb 2002, Hiten Pandya wrote: # hi all, # # I was wondering, after seeing that Linux has pam_smb, why can't # FreeBSD have it too. I can get the pam_smb compiling under FreeBSD, # from http://www.samba.org, so I was wondering why it isn't in our # CVS tree. This probably belongs to -questions more than -current. At any rate, we do have one in the ports collection: security/pam_smb -Joseph To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Why isn't PAM_smb available for FreeBSD?
On Fri, Feb 15, 2002 at 04:26:20PM -0800, Hiten Pandya wrote: hi all, I was wondering, after seeing that Linux has pam_smb, why can't FreeBSD have it too. I can get the pam_smb compiling under FreeBSD, from http://www.samba.org, so I was wondering why it isn't in our CVS tree. See ports/security/pam_smb -- Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The Power To Serve - http://www.FreeBSD.org msg34783/pgp0.pgp Description: PGP signature
Re: Why isn't PAM_smb available for FreeBSD?
--- Chris Faulhaber [EMAIL PROTECTED] wrote: See ports/security/pam_smb --- Joseph Scott [EMAIL PROTECTED] wrote: This probably belongs to -questions more than -current. At any rate, we do have one in the ports collection: security/pam_smb Hi, Thanks for that. :) Regards, -- Hiten __ Do You Yahoo!? Yahoo! Sports - Coverage of the 2002 Olympic Games http://sports.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Ethernet tunnel device
Mark Santcroos wrote: On Wed, Feb 13, 2002 at 04:59:41PM -0800, Terry Lambert wrote: There's one difference between vmware and a little hacked up test app. Linux emulation. It certaintly shouldn't matter, but it might be worth compiling the test program on a linux machine and seeing it it leaves the device in a weird state like vmware. Maybe it's losing an open instance in the resource track on close? That seems the most likely culprit... Do you mean in the linux emu case? If so, please see my message stating that I also used a linux emu program to test this. If not, can you please be a bit more detailed? Yes. I saw your message. It wasn't clear to me that you were simply exiting in the test, instead of actually closing the descriptor. I suspect that vmware just exits, and expects a resource tracking close on exit to free the reference count. If the Linux ABI code has not been updated with all the necessary hand waving (old code was OK, new code is broke ::= that's what's happening), then that could easily cause the problem, whereas a test case that does all the right manual shutdown would not have a problem. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Why isn't PAM_smb available for FreeBSD?
Hiten Pandya wrote: I was wondering, after seeing that Linux has pam_smb, why can't FreeBSD have it too. I can get the pam_smb compiling under FreeBSD, from http://www.samba.org, so I was wondering why it isn't in our CVS tree. Works fine in FreeBSD, but to have a FreeBSD with the NSS, which is required for pam_smb, you have to run -current, since NSS is not supported in -stable or -release. The are NSS patches listed ina PR against 4.4 which should apply cleanly to 4.5, if you wanted to use it in 4.5-release. Didn't you ask this question the other day on -hackers? -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Why isn't PAM_smb available for FreeBSD?
--- Terry Lambert [EMAIL PROTECTED] wrote: Works fine in FreeBSD, but to have a FreeBSD with the NSS, which is required for pam_smb, you have to run -current, since NSS is not supported in -stable or -release. Hi Terry, According to the pam_smb webpage, it states that it works cleanly with FreeBSD 3.x onwards, so I will have to try it out anyway. BTW, what is NSS? The are NSS patches listed ina PR against 4.4 which should apply cleanly to 4.5, if you wanted to use it in 4.5-release. Cool!, Thanks for the tip. :) Didn't you ask this question the other day on -hackers? hmm, nop. :) Regards, -- Hiten -- [EMAIL PROTECTED] __ Do You Yahoo!? Yahoo! Sports - Coverage of the 2002 Olympic Games http://sports.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Ethernet tunnel device
On Fri, Feb 15, 2002 at 07:35:39PM -0800, Terry Lambert wrote: I saw your message. It wasn't clear to me that you were simply exiting in the test, instead of actually closing the descriptor. I suspect that vmware just exits, and expects a resource tracking close on exit to free the reference count. If the Linux ABI code has not been updated with all the necessary hand waving (old code was OK, new code is broke ::= that's what's happening), then that could easily cause the problem, whereas a test case that does all the right manual shutdown would not have a problem. I think there's something else going on. You can hold open a vmnet device by the simple expedient of cat /dev/vmnet0 and when I tested with a Linux cat and killed it with a kill -9 it closed the descriptor properly. Some things I haven't tried, but though might have an effect were using fork or linux threads to create multiple refrences to the device and then closing them oddly. -- Brooks -- Any statement of the form X is the one, true Y is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 msg34788/pgp0.pgp Description: PGP signature
current kernel crashing in ata_raid_attach at boot
This is on a DELL2550. I do not have any ATA hard drives, let alone ata raid drives or, in fact, any raid drives of any kind. I do have an ata CDROM. A Feb 5 -current kernel boots fine. -Matt Matthew Dillon [EMAIL PROTECTED] /boot/kernel/acpi.ko text=0x2ae68 data=0x1618+0x6ec syms=[0x4+0x4df0+0x4+0x66dd] Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Fri Feb 15 21:51:48 PST 2002 [EMAIL PROTECTED]:/usr/obj/FreeBSD/FreeBSD-current/src/sys/DELL2550 Preloaded elf kernel /boot/kernel/kernel at 0xc03c5000. Preloaded elf module /boot/kernel/acpi.ko at 0xc03c50a8. Timecounter i8254 frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (1130.46-MHz 686-class CPU) Origin = GenuineIntel Id = 0x6b1 Stepping = 1 Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 1073676288 (1048512K bytes) avail memory = 1040916480 (1016520K bytes) Changing APIC ID for IO APIC #0 from 0 to 2 on chip Changing APIC ID for IO APIC #1 from 0 to 3 on chip Programming 16 pins in IOAPIC #0 IOAPIC #0 intpin 2 - irq 0 Programming 16 pins in IOAPIC #1 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 2, version: 0x000f0011, at 0xfec0 io1 (APIC): apic id: 3, version: 0x000f0011, at 0xfec01000 Pentium Pro MTRR support enabled Using $PIR table, 8 entries at 0xc00fc270 npx0: math processor on motherboard npx0: INT 16 interface acpi0: DELL PE2550 on motherboard acpi0: power button is handled as a fixed feature programming model. Timecounter ACPI frequency 3579545 Hz acpi_timer0: 32-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 acpi_cpu0: CPU on acpi0 acpi_cpu1: CPU on acpi0 acpi_pcib0: Host-PCI bridge on acpi0 pci0: PCI bus on acpi_pcib0 pci0: display, VGA at device 14.0 (no driver attached) isab0: PCI-ISA bridge port 0x8a0-0x8af at device 15.0 on pci0 isa0: ISA bus on isab0 atapci0: ServerWorks ROSB4 ATA33 controller port 0x8b0-0x8bf at device 15.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 acpi_pcib1: Host-PCI bridge on acpi0 IOAPIC #1 intpin 1 - irq 2 pci1: PCI bus on acpi_pcib1 pci1: network, ethernet at device 8.0 (no driver attached) acpi_pcib2: Host-PCI bridge on acpi0 IOAPIC #1 intpin 0 - irq 5 pci2: PCI bus on acpi_pcib2 pcib3: PCI-PCI bridge at device 2.0 on pci2 IOAPIC #1 intpin 15 - irq 10 IOAPIC #1 intpin 14 - irq 11 pci3: PCI bus on pcib3 ahc0: Adaptec aic7899 Ultra160 SCSI adapter port 0xcc00-0xccff mem 0xfe7ff000-0xfe7f irq 10 at device 4.0 on pci3 aic7899: Ultra160 Wide Channel A, SCSI Id=7, 32/255 SCBs ahc1: Adaptec aic7899 Ultra160 SCSI adapter port 0xc800-0xc8ff mem 0xfe7fe000-0xfe7fefff irq 11 at device 4.1 on pci3 aic7899: Ultra160 Wide Channel B, SCSI Id=7, 32/255 SCBs fxp0: Intel Pro 10/100B/100+ Ethernet port 0xbcc0-0xbcff mem 0xfe50-0xfe5f,0xfe90-0xfe900fff irq 5 at device 4.0 on pci2 fxp0: Ethernet address 00:06:5b:19:be:6f inphy0: i82555 10/100 media interface on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fdc0: enhanced floppy controller (i82077, NE72065 or clone) port 0x3f7,0x3f0-0x3f5 irq 6 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5 drive on fdc0 drive 0 atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A, console sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A fdc: fdc0 already exists; skipping it ata: ata0 already exists; skipping it ata: ata1 already exists; skipping it atkbdc: atkbdc0 already exists; skipping it sio: sio0 already exists; skipping it sio: sio1 already exists; skipping it sc: sc0 already exists; skipping it vga: vga0 already exists; skipping it orm0: Option ROMs at iomem 0xec000-0xe,0xc8000-0xcdfff,0xc-0xc7fff on isa0 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x100 APIC_IO: Testing 8254 interrupt delivery APIC_IO: Broken MP table detected: 8254 is not connected to IOAPIC #0 intpin 2 APIC_IO: routing 8254 via 8259 and IOAPIC #0 intpin 0 Fatal trap 12: page fault while in kernel mode cpuid = 0; lapic.id = 0100 fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0151134 stack pointer = 0x10:0xc03e7d54 frame pointer = 0x10:0xc03e7d64 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0,
followup w/patch... current kernel crashing in ata_raid_attach at boot
:
:This is on a DELL2550. I do not have any ATA hard drives, let alone ata
:raid drives or, in fact, any raid drives of any kind. I do have an ata
:CDROM.
:
:A Feb 5 -current kernel boots fine.
:
: -Matt
: Matthew Dillon
: [EMAIL PROTECTED]
I believe this will fix the problem (I'll leave it to Soren to commit it
or the appropriate fix):
-Matt
Index: ata-raid.c
===
RCS file: /home/ncvs/src/sys/dev/ata/ata-raid.c,v
retrieving revision 1.24
diff -u -r1.24 ata-raid.c
--- ata-raid.c 12 Feb 2002 11:35:15 - 1.24
+++ ata-raid.c 16 Feb 2002 06:12:07 -
@@ -119,6 +119,9 @@
dev_t dev;
int array, disk;
+if (ar_table == NULL) /* no devices to scan */
+ return;
+
for (array = 0; array MAX_ARRAYS; array++) {
if (!(raid = ar_table[array]) || !raid-flags)
continue;
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: current kernel crashing in ata_raid_attach at boot
I made a change recently to make LINT compile because the ata raid was using the symbol ar_attach and I changed it to be atar_attach because ar_attach was already used in the if_ar driver. please check that there isn't a MACRO somewhere that automatically generates an 'ar_attach reference) (would have been satisfied in LINT by the if_ar.c version of ar_attach() and not given errors. (I wouldn't have discovered that) http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/ata/ata-raid.c -- Revision 1.23 / (download) - annotate - [select for diffs], Wed Feb 6 19:35:36 2002 UTC (9 days, 10 hours ago) by julian Branch: MAIN Changes since 1.22: +1 -1 lines Diff to previous 1.22 (colored) Make LINT compile after fruitless attempts to get the authors to fix their code. ata stuff: Change name of ar_attach to not colide with existing ar_attach in if_ar.c. On Fri, 15 Feb 2002, Matthew Dillon wrote: This is on a DELL2550. I do not have any ATA hard drives, let alone ata raid drives or, in fact, any raid drives of any kind. I do have an ata CDROM. A Feb 5 -current kernel boots fine. -Matt Matthew Dillon [EMAIL PROTECTED] /boot/kernel/acpi.ko text=0x2ae68 data=0x1618+0x6ec syms=[0x4+0x4df0+0x4+0x66dd] Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Fri Feb 15 21:51:48 PST 2002 [EMAIL PROTECTED]:/usr/obj/FreeBSD/FreeBSD-current/src/sys/DELL2550 Preloaded elf kernel /boot/kernel/kernel at 0xc03c5000. Preloaded elf module /boot/kernel/acpi.ko at 0xc03c50a8. Timecounter i8254 frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (1130.46-MHz 686-class CPU) Origin = GenuineIntel Id = 0x6b1 Stepping = 1 Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 1073676288 (1048512K bytes) avail memory = 1040916480 (1016520K bytes) Changing APIC ID for IO APIC #0 from 0 to 2 on chip Changing APIC ID for IO APIC #1 from 0 to 3 on chip Programming 16 pins in IOAPIC #0 IOAPIC #0 intpin 2 - irq 0 Programming 16 pins in IOAPIC #1 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 2, version: 0x000f0011, at 0xfec0 io1 (APIC): apic id: 3, version: 0x000f0011, at 0xfec01000 Pentium Pro MTRR support enabled Using $PIR table, 8 entries at 0xc00fc270 npx0: math processor on motherboard npx0: INT 16 interface acpi0: DELL PE2550 on motherboard acpi0: power button is handled as a fixed feature programming model. Timecounter ACPI frequency 3579545 Hz acpi_timer0: 32-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 acpi_cpu0: CPU on acpi0 acpi_cpu1: CPU on acpi0 acpi_pcib0: Host-PCI bridge on acpi0 pci0: PCI bus on acpi_pcib0 pci0: display, VGA at device 14.0 (no driver attached) isab0: PCI-ISA bridge port 0x8a0-0x8af at device 15.0 on pci0 isa0: ISA bus on isab0 atapci0: ServerWorks ROSB4 ATA33 controller port 0x8b0-0x8bf at device 15.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 acpi_pcib1: Host-PCI bridge on acpi0 IOAPIC #1 intpin 1 - irq 2 pci1: PCI bus on acpi_pcib1 pci1: network, ethernet at device 8.0 (no driver attached) acpi_pcib2: Host-PCI bridge on acpi0 IOAPIC #1 intpin 0 - irq 5 pci2: PCI bus on acpi_pcib2 pcib3: PCI-PCI bridge at device 2.0 on pci2 IOAPIC #1 intpin 15 - irq 10 IOAPIC #1 intpin 14 - irq 11 pci3: PCI bus on pcib3 ahc0: Adaptec aic7899 Ultra160 SCSI adapter port 0xcc00-0xccff mem 0xfe7ff000-0xfe7f irq 10 at device 4.0 on pci3 aic7899: Ultra160 Wide Channel A, SCSI Id=7, 32/255 SCBs ahc1: Adaptec aic7899 Ultra160 SCSI adapter port 0xc800-0xc8ff mem 0xfe7fe000-0xfe7fefff irq 11 at device 4.1 on pci3 aic7899: Ultra160 Wide Channel B, SCSI Id=7, 32/255 SCBs fxp0: Intel Pro 10/100B/100+ Ethernet port 0xbcc0-0xbcff mem 0xfe50-0xfe5f,0xfe90-0xfe900fff irq 5 at device 4.0 on pci2 fxp0: Ethernet address 00:06:5b:19:be:6f inphy0: i82555 10/100 media interface on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fdc0: enhanced floppy controller (i82077, NE72065 or clone) port 0x3f7,0x3f0-0x3f5 irq 6 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5 drive on fdc0 drive 0 atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A, console sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A fdc: fdc0 already exists; skipping it ata: ata0 already exists; skipping it ata: ata1 already
