lock panic July 27th current
This occurred when running vmware while simultaneously compiling koffice over an NFS link. I've got dumpdev set now, so I'll get a core on the next crash. barry fxp0: promiscuous mode enabled vmnet1: promiscuous mode enabled lock order reversal 1st 0xc19e8700 pcm0:3:play @ /usr/src/sys/dev/sound/pcm/dsp.c:117 2nd 0xc19e8ac0 pcm0 @ /usr/src/sys/dev/sound/pcm/sound.c:99 lock order reversal 1st 0xcc14eb9c process lock @ /usr/src/sys/vm/vm_glue.c:469 2nd 0xc0cdaf80 lockmgr interlock @ /usr/src/sys/kern/kern_lock.c:239 recursed on non-recursive lock (sleep mutex) process lock @ /usr/src/sys/kern/kern_lock.c:262 first acquired @ /usr/src/sys/kern/kern_exit.c:327 panic: recurse syncing disks... 36 36 panic: Lock (sx) allproc not locked @ /usr/src/sys/kern/kern_proc.c:152. Uptime: 12m21s /dev/vmmon: Module vmmon: unloaded Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... Copyright (c) 1992-2001 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 Jul 27 19:50:06 EDT 2001 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/VAIO Timecounter i8254 frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (645.21-MHz 686-class CPU) Origin = GenuineIntel Id = 0x683 Stepping = 3 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 201261056 (196544K bytes) avail memory = 190930944 (186456K bytes) Preloaded elf kernel kernel at 0xc04a7000. Preloaded elf module ugen.ko at 0xc04a709c. Preloaded elf module ums.ko at 0xc04a7138. Preloaded elf module umass.ko at 0xc04a71d4. Preloaded elf module ipl.ko at 0xc04a7274. Pentium Pro MTRR support enabled Using $PIR table, 7 entries at 0xc00fdf50 apm0: APM BIOS on motherboard apm0: found APM BIOS v1.2, connected at v1.2 npx0: math processor on motherboard npx0: INT 16 interface pcib0: Intel 82443BX (440 BX) host to PCI bridge at pcibus 0 on motherboard pci0: PCI bus on pcib0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: display, VGA at 0.0 (no driver attached) isab0: PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX4 ATA33 controller port 0xfc90-0xfc9f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: Intel 82371AB/EB (PIIX4) USB controller port 0xfca0-0xfcbf irq 9 at device 7.2 on pci0 usb0: Intel 82371AB/EB (PIIX4) USB controller on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhub1: Philips Semiconductors hub, class 9/0, rev 1.10/1.10, addr 2 uhub1: 3 ports with 3 removable, self powered umass0: Sony USB Memory Stick Slot, rev 1.10/1.31, addr 3 ums0: Logitech USB Mouse, rev 1.10/6.20, addr 4, iclass 3/1 ums0: 3 buttons and Z dir. pci0: bridge, PCI-unknown at 7.3 (no driver attached) pci0: serial bus, FireWire at 8.0 (no driver attached) pcm0: Yamaha DS-1E (YMF744) port 0xfc8c-0xfc8f,0xfcc0-0xfcff mem 0xfedf8000-0xfedf irq 9 at device 9.0 on pci0 pci0: simple comms at 10.0 (no driver attached) fxp0: Intel Pro 10/100B/100+ Ethernet port 0xfc40-0xfc7f mem 0xfec0-0xfecf,0xfedf6000-0xfedf6fff irq 9 at device 11.0 on pci0 fxp0: Ethernet address 08:00:46:0d:8b:a9 inphy0: i82555 10/100 media interface on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pci_cfgintr_unique: hard-routed to irq 9 pci_cfgintr: 0:12 INTA routed to irq 9 pcic0: Ricoh RL5C475 PCI-CardBus Bridge irq 9 at device 12.0 on pci0 pcic0: Memory mapped device, will work. pcic0: PCI Memory allocated: 0x4400 pccard0: PC Card bus (classic) on pcic0 orm0: Option ROMs at iomem 0xc-0xc,0xdc000-0xd on isa0 atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model GlidePoint, device ID 0 pmtimer0 on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 sio0 at port 0x3f8-0x3ff irq 4 flags 0x90 on isa0 sio0: type 16550A vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: PNP0303 can't assign resources unknown: PNP0c02 can't assign resources unknown: PNP0c02 can't assign resources unknown: PNP0501 can't assign resources IPsec: Initialized Security Association Processing. IP Filter: v3.4.16 initialized. Default = pass all, Logging = enabled ad0: 11513MB FUJITSU MHK2120AT [23392/16/63] at ata0-master UDMA33 (probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition (probe0:umass-sim0:0:0:0): NOT READY asc:3a,0 (probe0:umass-sim0:0:0:0): Medium not present (probe0:umass-sim0:0:0:0): Unretryable error Mounting root from ufs:/dev/ad0s2a WARNING: / was not properly
Re: Boot time memory issue
Valentin Nechayev wrote: Sun, May 20, 2001 at 19:53:29, barry (Barry Lustig) wrote about Boot time memory issue: Do verbose boot (`boot -v') with large SC_HISTORY_SIZE (1000 at least, 2000 at most), and after boot check for SMAP ... lines at the very beginning of the kernel boot log at /dev/console. (They are not written to log viewable with dmesg.) Another way is to use serial console. With this SMAP lines one can say more concrete diagnosis. Here are the SMAP lines: 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 I was curious whether the memory limitation on the Sony VAIO Z505 machines was an actual hardware limitation or a marketing issue. I just tried adding a 256MB module to my machine. The BIOS seemed to mostly recognize it. It did see 320MB of RAM, but had problems when testing all of it. Current (from a couple of weeks ago) boots, but gives me: Too many holes in the physical address space, giving up and comes up showing 64MB of RAM. Is this something that can be worked around, or have I run up against an actual hardware limit on the machine? /netch To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Boot time memory issue
Mike Smith wrote: Here are the SMAP lines: 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. Any other ideas? barry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Boot time memory issue
I was curious whether the memory limitation on the Sony VAIO Z505 machines was an actual hardware limitation or a marketing issue. I just tried adding a 256MB module to my machine. The BIOS seemed to mostly recognize it. It did see 320MB of RAM, but had problems when testing all of it. Current (from a couple of weeks ago) boots, but gives me: Too many holes in the physical address space, giving up and comes up showing 64MB of RAM. Is this something that can be worked around, or have I run up against an actual hardware limit on the machine? barry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Memory Issue on a Sony Vaio Z505LE
I was curious whether the memory limitation on the Sony VAIO Z505 machines was a hardware limitation. I just tried adding a 256MB module to my machine. The BIOS seem to mostly recognize it. It did see 320MB of RAM, but had problems when testing all of it. FreeBSD current boots but gives me: Too many holes in the physical address space, giving up and comes up with 64MB of RAM. Is this something that can be worked around, or have I run up against an actual hardware limit on the machine? barry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Lucent Orinoco Gold PCCard?
On Mon, 04 Dec 2000, Warner Losh wrote: In message [EMAIL PROTECTED] Wes Peters writes: Dell is selling a Lucent-OEMed card for $139. I don't know if it is a Silver or Gold, though. http://www.comready.com/dlindwwirlan.html is selling what appears to be a lucentOEM'd card for $119. It has 40-bit WEP, so I don't know what metal that makes it (despite having been told the last time this came up). There's no external antenna connector, however. Still not a bad price and with $20 of the price point for taking my whole house wireless. 40-bit WEP means silver. barry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Proper location for certs (Now that openssl is in the base system)
User added certificates used to go in /usr/local/openssl/certs when openssl was a port. What is the correct location for certs now? barry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Possible IPv6-related problem
Can you try the following patch to qmail:
--- ipme.c.~1~ Mon Jun 15 06:53:16 1998
+++ ipme.c Sat Nov 20 18:21:26 1999
@@ -48,7 +48,7 @@
if ((s = socket(AF_INET,SOCK_STREAM,0)) == -1) return -1;
- len = 256;
+ len = 1024;
for (;;) {
if (!stralloc_ready(buf,len)) { close(s); return 0; }
buf.len = 0;
Qmail wasn't iterating through the available interfaces properly and would
overwrite its stack. This patch took care of the problem for me.
barry
On Fri, 14 Jan 2000, Jos Backus wrote:
Fyi: this afternoon, after a make world, kernel build and a reboot I was
seeing the following in my mail log:
2000-01-14 17:09:09.846441500 new msg 15377
2000-01-14 17:09:09.846838500 info msg 15377: bytes 277 from
[EMAIL PROTECTED] in-i
t.com qp 545 uid 666
2000-01-14 17:09:09.858416500 starting delivery 27: msg 15377 to remote
jbackus@ plex
.nl
2000-01-14 17:09:09.858685500 status: local 0/10 remote 1/20
2000-01-14 17:09:09.868815500 delivery 27: failure:
Sorry,_I_couldn't_find_any_h ost_
named_??O?gif2?._(#5.1.2)/
2000-01-14 17:09:09.870004500 status: local 0/10 remote 0/20
2000-01-14 17:09:09.977818500 bounce msg 15377 qp 547
2000-01-14 17:09:09.978254500 end msg 15377
2000-01-14 17:09:10.093495500 new msg 15657
2000-01-14 17:09:10.093829500 info msg 15657: bytes 871 from qp 547 uid
106 2000-01-14 17:09:10.104767500 starting delivery 28: msg 15657 to
remote Jos.Back us@n
l.origin-it.com
2000-01-14 17:09:10.105033500 status: local 0/10 remote 1/20
2000-01-14 17:09:10.114447500 delivery 28: failure:
Sorry,_I_couldn't_find_any_h ost_
named_??O?gif1?0??,._(#5.1.2)/
2000-01-14 17:09:10.115695500 status: local 0/10 remote 0/20
2000-01-14 17:09:10.132110500 bounce msg 15657 qp 549
2000-01-14 17:09:10.132548500 end msg 15657
The strange hostname should have been the name of our local smarthost.
After taking
optionsINET6 #IPv6 communications protocols
optionsIPSEC #IP security
optionsIPSEC_ESP #IP security (crypto; define w/ IPSEC)
optionsIPSEC_IPV6FWD #IP security tunnel for IPv6
optionsIPSEC_DEBUG #debug for IP security
out of the kernel, the problem went away.
I'm assuming this is related to the IPv6 changes because I have these
additional interfaces:
gif0: flags=8010POINTOPOINT,MULTICAST mtu 1280
gif1: flags=8010POINTOPOINT,MULTICAST mtu 1280
and those interface names show up in the garbage. The library call
involved seems to be res_query().
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
