Data corruption issue? (Was: NFS writes over a VLAN trunk wedges system)
Just trying to make sure Bosko takes note of this. He might have
something to say as DISABLE_PSE appears to fix your problem.
--
Regards,
Georg.
On Do, 2003-09-04 at 00:02, Peter Jeremy wrote:
I have a system running 5.1-RELEASE-p2 which is an NFS client of
another FreeBSD (4.x) machine. When I have the NFS mount via a VLAN
the system reliably hangs (no response to console, including
Ctrl-Alt-Esc). This is a default NFS mount (no options) and I am
trying to do a buildworld with /usr/{src,obj} NFS mounted. The VLAN
is using an Intel fxp NIC. The kernel has DEVICE_POLLING specified
but not enabled.
- NFS mount to the same server via normal Ethernet (using a 3Com 905
NIC) successfully manages buildworld
- Adding WITNESS and INVARIANTS didn't help (though it lasted longer
before dying)
- Enabling device polling didn't help
- Adding DISABLE_PSE allows it to complete a buildworld
Any suggestions on where to go next?
Peter
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
--
Grüße,
Georg.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
still data corruption with 5.1-R on Intel Pentium 4
There have been threads about data corruption in RAM on P4 and other i386 machines on this list. I also observed the problem, on my laptop with 5.0-R. It seemed to go away with 5.1-R, on the laptop. Recently I upgraded my home PC which is a P4 2.0A from 4.8-R to 5.1-R. No problems at first. Until I ran portsdb -Uu. I got a couple mysterious SIG4 and SIG11. Just to be sure I rebooted and tried again, same result. I rebooted another time, this time with ACPI disabled, and tried again, still the same. Then I rebuilt my kernel with options DISABLE_PSE and DISABLE_PG_G, as suggested by Terry in the old threads: Bingo, everything is fine now, no more SIG4 or SIG11 during portsdb -Uu. It seems the workarounds that we have in 5.1-R are not effective enough. What do you think? -- Regards, Georg. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
spontaneous reboot while dump -0uaLf - /var on a UFS2 FS in5.0-RELEASE
I just did a dump over the network via ftp using the command: put |dump -0uaLf - /var | gzip -1 var.dump.gz /var is a UFS2 FS with soft-updates, and the system is 5.0-RELEASE. I got a short pause, maybe 5 seconds, and then the system rebooted spontaneously. I didn't see any messages, I was in X at that time. I also didn't find anything unusual in the system log, but /var did contain the following file after reboot and BG fsck finished: -r 1 rootwheel 2097152000 25 Feb 10:56 .dump_snapshot I repeated the same dump after the system was back up (after removing the snapshot), and all went well this time. Does this sound like a known problem? -- Regards, Georg. -- Georg-W. Koltermann [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: fxp0 device timeout on 5.0-RELEASE
Am Do, 2003-01-30 um 12.41 schrieb Sergey A. Osokin: 3) Put hw.pci.allow_unsupported_io_range=1 into your /boot/loader.conf.local Thanks, that did the trick. Could we, maybe, add a little note about this to the release notes or errata? Or better yet, how about a big fat warning message if the kernel probes a device at an unsupported address while hw.pci.allow_unsupported_io_range==0? -- Regards, Georg. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
5.0-R: no network connectivity with generic kernel andfirewall_enable=YES
Hi, I couldn't connect to anything on the network with my 5.0-RELEASE, with the generic kernel and rc.conf containing firewall_enable=YES natd_interface=fxp0 natd_interface=fxp0 natd_flags=-t 255.255.255.255 The firewall loaded ok but natd silently vanished. When I tried to start natd manually it complained about divert being an unknown protocol. It seems ipfw can be loaded as a module but divert needs to be compiled into the kernel. Should this be documented, e.g. by a prominent comment in defaults/rc.conf, right by the side of firewall_enable? -- Regards, Georg. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
fxp0 device timeout on 5.0-RELEASE
Hi, on an HP Omnibook 6100 which ran -current about half a year ago successfully, I get fxp0 device timeouts after installing 5.0-R. The network interface does not work at all. arp -an says incomplete for every host that I try to connect. The system now runs 4.7-STABLE with no problems, and as far as I can tell, 5.0 and -stable probe the fxp0 with the same address and irq values. On 5.0 I have to disable ACPI, however, otherwise the system immediately resets after loading the kernel (had to do that with -current half a year ago as well). /var/log/messages attached below. -- Regards, Georg. Jan 30 09:27:25 hunter kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Jan 30 09:27:25 hunter kernel: The Regents of the University of California. All rights reserved. Jan 30 09:27:25 hunter kernel: FreeBSD 5.0-RELEASE #0: Thu Jan 16 22:16:53 GMT 2003 Jan 30 09:27:25 hunter kernel: [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Jan 30 09:27:25 hunter kernel: Preloaded elf kernel /boot/kernel/kernel at 0xc0628000. Jan 30 09:27:25 hunter kernel: Timecounter i8254 frequency 1193182 Hz Jan 30 09:27:25 hunter kernel: Timecounter TSC frequency 1129574593 Hz Jan 30 09:27:25 hunter kernel: CPU: Pentium III/Pentium III Xeon/Celeron (1129.57-MHz 686-class CPU) Jan 30 09:27:25 hunter kernel: Origin = GenuineIntel Id = 0x6b1 Stepping = 1 Jan 30 09:27:25 hunter kernel: Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE Jan 30 09:27:25 hunter kernel: real memory = 1073086464 (1023 MB) Jan 30 09:27:25 hunter kernel: avail memory = 1036148736 (988 MB) Jan 30 09:27:25 hunter kernel: Initializing GEOMetry subsystem Jan 30 09:27:25 hunter kernel: Pentium Pro MTRR support enabled Jan 30 09:27:25 hunter kernel: npx0: math processor on motherboard Jan 30 09:27:25 hunter kernel: npx0: INT 16 interface Jan 30 09:27:25 hunter kernel: Using $PIR table, 14 entries at 0xc00fdee0 Jan 30 09:27:25 hunter kernel: pcib0: Host to PCI bridge at pcibus 0 on motherboard Jan 30 09:27:25 hunter kernel: pci0: PCI bus on pcib0 Jan 30 09:27:25 hunter kernel: agp0: Intel 82830 host to AGP bridge mem 0xe000-0xefff at device 0.0 on pci0 Jan 30 09:27:25 hunter kernel: pcib1: PCIBIOS PCI-PCI bridge at device 1.0 on pci0 Jan 30 09:27:25 hunter kernel: pci1: PCI bus on pcib1 Jan 30 09:27:25 hunter kernel: pci1: display, VGA at device 0.0 (no driver attached) Jan 30 09:27:25 hunter kernel: uhci0: Intel 82801CA/CAM (ICH3) USB controller USB-A port 0x1800-0x181f irq 10 at device 29.0 on pci0 Jan 30 09:27:25 hunter kernel: usb0: Intel 82801CA/CAM (ICH3) USB controller USB-A on uhci0 Jan 30 09:27:25 hunter kernel: usb0: USB revision 1.0 Jan 30 09:27:25 hunter kernel: uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Jan 30 09:27:25 hunter kernel: uhub0: 2 ports with 2 removable, self powered Jan 30 09:27:25 hunter kernel: pcib2: PCIBIOS PCI-PCI bridge at device 30.0 on pci0 Jan 30 09:27:25 hunter kernel: pci2: PCI bus on pcib2 Jan 30 09:27:25 hunter kernel: pci2: simple comms at device 2.0 (no driver attached) Jan 30 09:27:25 hunter kernel: pci2: multimedia, audio at device 3.0 (no driver attached) Jan 30 09:27:25 hunter kernel: cbb0: TI1420 PCI-CardBus Bridge at device 5.0 on pci2 Jan 30 09:27:25 hunter kernel: cardbus0: CardBus bus on cbb0 Jan 30 09:27:25 hunter kernel: pccard0: 16-bit PCCard bus on cbb0 Jan 30 09:27:25 hunter kernel: pci_cfgintr: 2:5 INTA routed to irq 10 Jan 30 09:27:25 hunter kernel: cbb1: TI1420 PCI-CardBus Bridge at device 5.1 on pci2 Jan 30 09:27:25 hunter kernel: cardbus1: CardBus bus on cbb1 Jan 30 09:27:25 hunter kernel: pccard1: 16-bit PCCard bus on cbb1 Jan 30 09:27:25 hunter kernel: pci_cfgintr: 2:5 INTB routed to irq 10 Jan 30 09:27:25 hunter kernel: fxp0: Intel Pro/100 Ethernet port 0x3440-0x347f mem 0xd020-0xd0200fff irq 10 at device 8.0 on pci2 Jan 30 09:27:25 hunter kernel: fxp0: Ethernet address 00:c0:9f:05:9a:1f Jan 30 09:27:25 hunter kernel: inphy0: i82562EM 10/100 media interface on miibus0 Jan 30 09:27:25 hunter kernel: inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Jan 30 09:27:25 hunter kernel: isab0: PCI-ISA bridge at device 31.0 on pci0 Jan 30 09:27:25 hunter kernel: isa0: ISA bus on isab0 Jan 30 09:27:25 hunter kernel: atapci0: Intel ICH3 ATA100 controller port 0x1820-0x182f,0x374-0x377,0x170-0x177,0x3f4-0x3f7,0x1f0-0x1f7 mem 0xd000-0xd3ff at device 31.1 on pci0 Jan 30 09:27:25 hunter kernel: ata0: at 0x1f0 irq 14 on atapci0 Jan 30 09:27:25 hunter kernel: ata1: at 0x170 irq 15 on atapci0 Jan 30 09:27:25 hunter kernel: pci0: serial bus, SMBus at device 31.3 (no driver attached) Jan 30 09:27:25 hunter kernel: orm0: Option ROMs at iomem 0xe-0xe2fff,0xc-0xcdfff on isa0 Jan 30 09:27:25 hunter kernel: pmtimer0 on isa0 Jan 30 09:27:25 hunter kernel: atkbdc0: Keyboard controller (i8042) at port 0x64,0x60 on isa0 Jan 30 09:27:25 hunter kernel: atkbd0: AT Keyboard flags 0x1
Re: install crash on hp omnibook 6100
Am Mi, 2002-08-21 um 21.52 schrieb Andy Sparrow: i'm trying to install current from cd (i took 3 different builds) to my notebook hp omnibook 6100. by booting the kernel after few lines is the machine crashing. i'm not abte to see the reason, everything goes too fast. has anybody similar situation? any ideas why? 4.6 works fine. Hi Tomas, Last time I installed -current on a 6100, having ACPI enabled would reboot the machine. Try disabling it from the boot loader, search the -STABLE archives for the ACPI causes immediate reboot thread. I don't know the current status (I couldn't get an acceptable subset of devices for my primary machine whilst travelling, so sold it on). At least one person with a 6100 persevered further with this, maybe someone else can help you with the current status or better advice? Yes I ran -current on my 6100 for a while. I also reported the immediate reset when booting with ACPI enabled. I haven't been able to further narrow the problem down, and didn't get a reply from the ACPI folks as well. So I ran with ACPI disabled. I switched to 4.6R a while ago because I got tired of -current after a phase of instability. Note that this is not a complaint, it is just that a released version better fits my needs. I may go back to running -current when I have more spare time. -- Regards, Georg. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: fsck hosed?
Yes, I see that as well. Another symptom is that fsck -p now always announces unexpected inconsistencies and drops back to singleuser when it indeed was able to fix the problems, i.e. it marks the filesystem clean and a manual fsck does not report anything unusual. My last cvsup was with date=2002.06.27.22.00.00 (pre-KSE III, post-UFS2). -- Regards, Georg. Am Mo, 2002-07-08 um 06.41 schrieb Peter Wemm: It seems to be aborting the 'process all file systems' loop when it modifies a file system. eg: To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: dump(8) is hosed
Am Mi, 2002-07-03 um 17.31 schrieb David O'Brien: On a 27-June-2002 23:02:00 UTC system (just before ipfw2 went in, pre-KSE3), dump will not complete dumping more than 5GB. At that point it stops responding properly to ^T, which should give DUMP: 47.52% done, finished in 1:19. At the 5GB mark, ^T gives: load: 0.00 cmd: dump 3981 [physstr] 2.11u 43.06s 0% 1536k and never changes. The user and system times never advance. Anybody have any ideas? For me it is broken in a different way. For a small FS like / it works, but dumping my /home, which is 4G, I get DUMP: read error from /dev/ad0s5e: Invalid argument: [sector -1054739789]: count=-1 DUMP: read error from /dev/ad0s5e: Invalid argument: [sector -1054739788]: count=-1 DUMP: read error from /dev/ad0s5e: Invalid argument: [sector -1054739787]: count=-1 DUMP: read error from /dev/ad0s5e: Invalid argument: [sector -1054739786]: count=-1 and on and on. Maybe a 32 bit -- 64 bit mismatch caused by UFS2? My -current is of date=2002.06.27.22.00.00. Using pax(1) for backup now :-( -- Regards, Georg. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
panic: Most recently used by kqueue
Hi, I got this panic with -current of date=2002.06.27.22.00.00. It reminds me of another panic that I had recently with a -current of 25-June, the message of that earlier incident was panic: Most recently used by routetbl. hunter[7]$ gdb -k /boot/kernel/kernel vmcore.26 GNU gdb 4.18 (FreeBSD) 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... (no debugging symbols found)... IdlePTD at physical address 0x005db000 initial pcb at physical address 0x004aa780 panicstr: bremfree: bp 0xd2a1def0 not locked panic messages: --- panic: Most recently used by kqueue syncing disks... panic: bremfree: bp 0xd2a1def0 not locked Uptime: 1h55m19s pfs_vncache_unload(): 3 entries remaining Dumping 1023 MB ata0: resetting devices .. done 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 256 272 288 304 320 336 352 368 384 400 416 432 448 464 480 496 512 528 544 560 576 592 608 624 640 656 672 688 704 720 736 752 768 784 800 816 832 848 864 880 896 912 928 944 960 976 992 1008 --- #0 0xc02637a8 in doadump () (kgdb) where #0 0xc02637a8 in doadump () #1 0xc0263c32 in boot () #2 0xc0263de5 in panic () #3 0xc0295f35 in bremfree () #4 0xc029774e in vfs_bio_awrite () #5 0xc023e560 in spec_fsync () #6 0xc023e147 in spec_vnoperate () #7 0xc03521c1 in ffs_sync () #8 0xc02a46e3 in sync () #9 0xc0263885 in boot () #10 0xc0263de5 in panic () #11 0xc036f588 in mtrash_ctor () #12 0xc036e4e3 in uma_zalloc_arg () #13 0xc025b018 in malloc () #14 0xc03522a8 in ffs_vget () #15 0xc0357069 in ufs_lookup () #16 0xc035c603 in ufs_vnoperate () #17 0xc029a6b5 in vfs_cache_lookup () #18 0xc035c603 in ufs_vnoperate () #19 0xc029e5a8 in lookup () #20 0xc029e048 in namei () #21 0xc02a6a7a in stat () #22 0xc03a18f5 in syscall () #23 0xc039439d in syscall_with_err_pushed () #24 0x8129269 in ?? () #25 0x8128c15 in ?? () #26 0x81291b5 in ?? () #27 0x8151100 in ?? () #28 0x812987b in ?? () #29 0x81293c0 in ?? () #30 0x8128fab in ?? () #31 0x80f8da3 in ?? () #32 0x8129269 in ?? () #33 0x8151100 in ?? () #34 0x812987b in ?? () #35 0x81293c0 in ?? () #36 0x8151100 in ?? () #37 0x812987b in ?? () #38 0x81293c0 in ?? () #39 0x8151100 in ?? () #40 0x812987b in ?? () #41 0x81293c0 in ?? () #42 0x8151100 in ?? () #43 0x812987b in ?? () #44 0x81293c0 in ?? () #45 0x8151100 in ?? () #46 0x812987b in ?? () #47 0x81293c0 in ?? () #48 0x8151100 in ?? () #49 0x812987b in ?? () #50 0x81293c0 in ?? () #51 0x8151100 in ?? () #52 0x812987b in ?? () #53 0x81293c0 in ?? () #54 0x8151100 in ?? () #55 0x812987b in ?? () #56 0x81293c0 in ?? () #57 0x812874d in ?? () #58 0x812666e in ?? () #59 0x811fa4b in ?? () #60 0x81286b3 in ?? () #61 0x812666e in ?? () #62 0x81286b3 in ?? () #63 0x8126543 in ?? () #64 0x81286b3 in ?? () #65 0x81289a1 in ?? () #66 0x812666e in ?? () #67 0x81286b3 in ?? () #68 0x8126543 in ?? () #69 0x81286b3 in ?? () #70 0x81289a1 in ?? () #71 0x812666e in ?? () #72 0x8129806 in ?? () #73 0x81293c0 in ?? () #74 0x8128ddf in ?? () #75 0x8128c92 in ?? () #76 0x81291b5 in ?? () #77 0x8151100 in ?? () #78 0x812987b in ?? () #79 0x81293c0 in ?? () #80 0x8151100 in ?? () #81 0x812987b in ?? () #82 0x81293c0 in ?? () #83 0x8125efc in ?? () #84 0x80dd92e in ?? () #85 0x80d4585 in ?? () #86 0x8127739 in ?? () #87 0x80d387c in ?? () #88 0x812735c in ?? () #89 0x80d382e in ?? () #90 0x80d33b5 in ?? () #91 0x80d34d8 in ?? () #92 0x80d243b in ?? () #93 0x804ecd1 in ?? () (kgdb) Sorry no symbols this time, I had removed makeoptions COPTFLAGS=-gstabs+ from my config when I tried to troubleshoot a stability problem a few days ago. -- Regards, Georg. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
ipfw divert not accepted
hunter# ipfw add 50 divert natd all from any to any via fxp0 ipfw: getsockopt(IP_FW_ADD): Invalid argument hunter# ipfw list 00100 allow ip from any to any via lo0 00200 deny ip from any to 127.0.0.0/8 00300 deny ip from 127.0.0.0/8 to any 65000 allow ip from any to any 65535 deny ip from any to any hunter# ifconfig fxp0 fxp0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet6 fe80::2c0:9fff:fe05:9a1f%fxp0 prefixlen 64 scopeid 0x1 inet 172.17.22.32 netmask 0xff00 broadcast 172.17.22.255 ether 00:c0:9f:05:9a:1f media: Ethernet autoselect (100baseTX full-duplex) status: active hunter# ps ax | grep nat 188 ?? Is 0:00,00 /sbin/natd -t 255.255.255.255 -n fxp0 1059 p1 RV 0:00,00 grep nat (csh) hunter# This is with a -current of date=2002.06.27.22.00.00. -- Regards, Georg. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ipfw divert not accepted
Operator error, sorry for the false alarm. I had removed all of my IPFIREWALL options from my config in an attempt to find the cause of instability. I'm surprised that ipfw(8) did anything useful at all with that kernel. -- Thanks a lot, Georg. Am Mi, 2002-07-03 um 10.48 schrieb Maxim Sobolev: Georg-W. Koltermann wrote: hunter# ipfw add 50 divert natd all from any to any via fxp0 ipfw: getsockopt(IP_FW_ADD): Invalid argument Add option IPFIREWALL_FORWARD into your kernel config. -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
PANIC Most recently used by routetbl
Hi,
panic: Most recently used by routetbl
I get this type of panic withing minutes of uptime with a -current of
25-Jun-2002 around 13:52 GMT-2. Another anomaly is that name resolution
doesn't seem to work reliably, or maybe even TCP in general has a
problem -- it all takes very long if it works at all.
This is still a pre-KSE-III system.
As a workaround I am currently running with a kernel of about 11 Apr in
the same userland, which seems to work.
hunter[4]$ gdb -k kernel.debug vmcore.25
GNU gdb 4.18 (FreeBSD)
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/contrib/gdb/gdb/dbxread.c line 2617 in elfstab_build_psymtabs
Deprecated bfd_read called at /usr/src/contrib/gdb/gdb/dbxread.c line 930 in
fill_symbuf
IdlePTD at physical address 0x00498000
initial pcb at physical address 0x003b3cc0
panicstr: bremfree: bp 0xd2a84230 not locked
panic messages:
---
panic: Most recently used by routetbl
syncing disks... panic: bremfree: bp 0xd2a84230 not locked
Uptime: 24m55s
pfs_vncache_unload(): 2 entries remaining
/dev/vmmon: Module vmmon: unloaded
Dumping 1023 MB
ata0: resetting devices .. done
16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 256 272 288 304 320 336 352 368
384 400 416 432 448 464 480 496 512 528 544 560 576 592 608 624 640 656 672 688 704
720 736 752 768 784 800 816 832 848 864 880 896 912 928 944 960 976 992 1008
---
#0 0xc01cff40 in doadump () at /usr/src/sys/kern/kern_shutdown.c:353
353 }
(kgdb) where
#0 0xc01cff40 in doadump () at /usr/src/sys/kern/kern_shutdown.c:353
#1 0xc01d054b in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:353
#2 0xc01d0767 in panic (fmt=0xc034f0a9 bremfree: bp %p not locked)
at /usr/src/sys/kern/kern_shutdown.c:353
#3 0xc02146a6 in bremfree (bp=0xd2a84230) at /usr/src/sys/kern/vfs_bio.c:1368
#4 0xc021723b in getblk (vp=0xc624e000, blkno=262208, size=8192, slpflag=0,
slptimeo=0) at /usr/src/sys/kern/vfs_bio.c:1368
#5 0xc02147d1 in breadn (vp=0xc624e000, blkno=262208, size=8192, rablkno=0x0,
rabsize=0x0, cnt=0, cred=0x0, bpp=0xe557aa40)
at /usr/src/sys/kern/vfs_bio.c:1368
#6 0xc0214793 in bread (vp=0xc624e000, blkno=262208, size=8192, cred=0x0,
bpp=0xe557aa40) at /usr/src/sys/kern/vfs_bio.c:1368
#7 0xc029cb62 in ffs_update (vp=0xc6658e00, waitfor=0)
at /usr/src/sys/ufs/ffs/ffs_inode.c:441
#8 0xc02b24ba in ffs_fsync (ap=0xe557aab4)
at /usr/src/sys/ufs/ufs/ufs_readwrite.c:596
#9 0xc02b0b9c in VOP_FSYNC (vp=0xc6658e00, cred=0xc21a1f00, waitfor=2,
td=0xc037d6a0) at /usr/src/sys/ufs/ffs/ffs_vfsops.c:813
#10 0xc02afff4 in ffs_sync (mp=0xc60d8600, waitfor=2, cred=0xc21a1f00,
td=0xc037d6a0) at /usr/src/sys/ufs/ffs/ffs_vfsops.c:813
#11 0xc022736c in sync (td=0xc037d6a0, uap=0x0)
at /usr/src/sys/kern/vfs_syscalls.c:584
#12 0xc01d0055 in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:353
#13 0xc01d0767 in panic (fmt=0xc0360748 Most recently used by %s\n)
at /usr/src/sys/kern/kern_shutdown.c:353
#14 0xc02d6f3a in mtrash_ctor (mem=0xc697cc00, size=252, arg=0x0)
at /usr/src/sys/vm/uma_dbg.c:284
#15 0xc02d5765 in uma_zalloc_arg (zone=0xc2179140, udata=0x0, flags=0)
at /usr/src/sys/vm/uma_core.c:663
#16 0xc01c5254 in uma_zalloc (zone=0xc2179140, flags=0)
at /usr/src/sys/kern/kern_malloc.c:555
#17 0xc01c484b in malloc (size=224, type=0xc037e760, flags=0)
at /usr/src/sys/kern/kern_malloc.c:555
#18 0xc01b34d2 in fdcopy (td=0xc62ccd70)
at /usr/src/sys/kern/kern_descrip.c:476
#19 0xc01bb7bd in fork1 (td=0xc62ccd70, flags=20, procp=0xe557acd8)
at /usr/src/sys/kern/kern_fork.c:734
#20 0xc01baea6 in fork (td=0xc62ccd70, uap=0xe557acfc)
at /usr/src/sys/kern/kern_fork.c:734
#21 0xc0310af6 in syscall (frame={tf_fs = 47, tf_es = 47, tf_ds = 47,
tf_edi = 0, tf_esi = 70, tf_ebp = -1077937164, tf_isp = -447238796,
tf_ebx = 678978900, tf_edx = 484, tf_ecx = -33, tf_eax = 2,
tf_trapno = 12, tf_err = 2, tf_eip = 672142263, tf_cs = 31,
tf_eflags = 642, tf_esp = -1077937224, tf_ss = 47})
at /usr/src/sys/i386/i386/trap.c:655
#22 0xc02ff8ed in syscall_with_err_pushed () at /var/tmp//ccMqLVIG.s:128
#23 0x2877f460 in ?? ()
#24 0x2877e79b in ?? ()
#25 0x28776f62 in ?? ()
#26 0x28776e45 in ?? ()
#27 0x287765c1 in ?? ()
#28 0x8055304 in ?? ()
#29 0x805caea in ?? ()
#30 0x805d267 in ?? ()
#31 0x804fdad in ?? ()
(kgdb)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
panic -- trap in atomic_cmpset_int
Hi,
with a -current CVSupped 17 May 22:27 GMT-2:
hunter[4]$ gdb -k kernel.debug vmcore.23
GNU gdb 4.18 (FreeBSD)
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...
IdlePTD at phsyical address 0x00514000
initial pcb at physical address 0x00420b20
panicstr: bwrite: buffer is not busy???
panic messages:
---
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x18
fault code = supervisor write, page not present
instruction pointer = 0x8:0xc01db544
stack pointer = 0x10:0xe3436bb8
frame pointer = 0x10:0xe3436bc0
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 5183 (gnome-spell-compone)
trap number = 12
panic: page fault
syncing disks... panic: bwrite: buffer is not busy???
Uptime: 5h31m35s
pfs_vncache_unload(): 3 entries remaining
/dev/vmmon: Module vmmon: unloaded
Dumping 1023 MB
ata0: resetting devices .. done
16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 256 272 288 304 320 336 352 368
384 400 416 432 448 464 480 496 512 528 544 560 576 592 608 624 640 656 672 688 704
720 736 752 768 784 800 816 832 848 864 880 896 912 928 944 960 976 992 1008
---
#0 0xc01fa1a4 in doadump () at /usr/src/sys/kern/kern_shutdown.c:353
353 }
(kgdb) where
#0 0xc01fa1a4 in doadump () at /usr/src/sys/kern/kern_shutdown.c:353
#1 0xc01fa7d1 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:353
#2 0xc01fa9dd in panic (fmt=0xc03aab0b bwrite: buffer is not busy???)
at /usr/src/sys/kern/kern_shutdown.c:353
#3 0xc0240eac in bwrite (bp=0xd284d130) at /usr/src/sys/kern/vfs_bio.c:1367
#4 0xc0242635 in vfs_bio_awrite (bp=0xd284d130)
at /usr/src/sys/kern/vfs_bio.c:1367
#5 0xc01c8a67 in spec_fsync (ap=0xe3436990)
at /usr/src/sys/fs/specfs/spec_vnops.c:849
#6 0xc01c844e in spec_vnoperate (ap=0xe3436990)
at /usr/src/sys/fs/specfs/spec_vnops.c:849
#7 0xc030b72a in VOP_FSYNC (vp=0xe0e03000, cred=0xd277ff00, waitfor=2,
td=0xc03ea5a0) at /usr/src/sys/ufs/ffs/ffs_vfsops.c:810
#8 0xc030abc1 in ffs_sync (mp=0xe0c25200, waitfor=2, cred=0xd277ff00,
td=0xc03ea5a0) at /usr/src/sys/ufs/ffs/ffs_vfsops.c:810
#9 0xc025424b in sync (td=0xc03ea5a0, uap=0x0)
at /usr/src/sys/kern/vfs_syscalls.c:640
#10 0xc01fa2ab in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:353
#11 0xc01fa9dd in panic (fmt=0xc03c70de %s)
at /usr/src/sys/kern/kern_shutdown.c:353
#12 0xc036d714 in trap_fatal (frame=0xe3436b78, eva=24)
at /usr/src/sys/i386/i386/trap.c:652
#13 0xc036d34b in trap_pfault (frame=0xe3436b78, usermode=0, eva=24)
at /usr/src/sys/i386/i386/trap.c:652
#14 0xc036cd34 in trap (frame={tf_fs = -1071841256, tf_es = -1069481968,
tf_ds = -482213872, tf_edi = 0, tf_esi = -1, tf_ebp = -482120768,
tf_isp = -482120796, tf_ebx = 24, tf_edx = 4, tf_ecx = -482191576,
tf_eax = 4, tf_trapno = 12, tf_err = 2, tf_eip = -1071794876, tf_cs = 8,
tf_eflags = 66182, tf_esp = 4, tf_ss = -482191832})
at /usr/src/sys/i386/i386/trap.c:652
#15 0xc01db544 in atomic_cmpset_int (dst=0x18, exp=4, src=3812775720)
at /usr/src/sys/kern/kern_descrip.c:476
#16 0xc01db043 in atomic_cmpset_ptr (dst=0x18, exp=0x4, src=0xe3425728)
at /usr/src/sys/kern/kern_descrip.c:476
#17 0xc01da276 in fdrop (fp=0xe38be760, td=0xe3425728)
at /usr/src/sys/kern/kern_descrip.c:476
#18 0xc01da240 in closef (fp=0xe38be760, td=0xe3425728)
at /usr/src/sys/kern/kern_descrip.c:476
#19 0xc01d987b in fdfree (td=0xe3425728)
at /usr/src/sys/kern/kern_descrip.c:476
#20 0xc01e03a0 in exit1 (td=0xe3425728, rv=0)
at /usr/src/sys/kern/kern_exit.c:448
#21 0xc01dffc8 in exit1 (td=0xe3425728, rv=-482120456)
at /usr/src/sys/kern/kern_exit.c:448
#22 0xc036da82 in syscall (frame={tf_fs = 47, tf_es = 47, tf_ds = 47,
tf_edi = 0, tf_esi = -1, tf_ebp = -1077939108, tf_isp = -482120332,
tf_ebx = 686673660, tf_edx = 10, tf_ecx = 686673296, tf_eax = 1,
tf_trapno = 12, tf_err = 2, tf_eip = 686276643, tf_cs = 31,
tf_eflags = 658, tf_esp = -1077939152, tf_ss = 47})
at /usr/src/sys/i386/i386/trap.c:652
#23 0xc035c67d in syscall_with_err_pushed () at /var/tmp//ccqhs5l0.s:128
#24 0x804b6fb in ?? ()
(kgdb)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
panic -- trap in mtx_lock_sleep
Hi,
I got the following panic while compiling openoffice. I suspect it was
somehow triggered by the high I/O activity.
Last CVSup was 17 May 22:27 GMT-2.
I'll keep the dump around for a couple of days, so let me know if I
should provide any additional information.
--
Georg.
hunter# cat info.21
Good dump found on device /dev/ad0s2b
Architecture: i386
Architecture version: 1
Dump length: 1073086464B (1023 MB)
Blocksize: 512
Dumptime: Fri Jun 14 14:02:18 2002
Hostname: hunter.muc.macsch.com
Versionstring: FreeBSD 5.0-CURRENT #70: Mon Jun 3 15:00:22 CEST 2002
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/HUNTER
Panicstring: bwrite: buffer is not busy???
Bounds: 21
hunter#
hunter[5]$ gdb -k kernel.debug vmcore.21
GNU gdb 4.18 (FreeBSD)
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...
IdlePTD at phsyical address 0x00514000
initial pcb at physical address 0x00420b20
panicstr: bwrite: buffer is not busy???
panic messages:
---
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x0
fault code = supervisor write, page not present
instruction pointer = 0x8:0xc01eee7f
stack pointer = 0x10:0xe3758be8
frame pointer = 0x10:0xe3758c08
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 1410 (slogin)
trap number = 12
panic: page fault
syncing disks... panic: bwrite: buffer is not busy???
Uptime: 4h58m25s
pfs_vncache_unload(): 2 entries remaining
/dev/vmmon: Module vmmon: unloaded
Dumping 1023 MB
ata0: resetting devices .. ata0-slave: ATA identify retries exceeded
done
16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 256 272 288 304 320 336 352 368
384 400 416 432 448 464 480 496 512 528 544 560 576 592 608 624 640 656 672 688 704
720 736 752 768 784 800 816 832 848 864 880 896 912 928 944 960 976 992 1008
---
#0 0xc01fa1a4 in doadump () at /usr/src/sys/kern/kern_shutdown.c:353
353 }
(kgdb) t
[Current thread is 0 (process 0)]
(kgdb) where
#0 0xc01fa1a4 in doadump () at /usr/src/sys/kern/kern_shutdown.c:353
#1 0xc01fa7d1 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:353
#2 0xc01fa9dd in panic (fmt=0xc03aab0b bwrite: buffer is not busy???)
at /usr/src/sys/kern/kern_shutdown.c:353
#3 0xc0240eac in bwrite (bp=0xd290c844) at /usr/src/sys/kern/vfs_bio.c:1367
#4 0xc0242635 in vfs_bio_awrite (bp=0xd290c844)
at /usr/src/sys/kern/vfs_bio.c:1367
#5 0xc01c8a67 in spec_fsync (ap=0xe37589c0)
at /usr/src/sys/fs/specfs/spec_vnops.c:849
#6 0xc01c844e in spec_vnoperate (ap=0xe37589c0)
at /usr/src/sys/fs/specfs/spec_vnops.c:849
#7 0xc030b72a in VOP_FSYNC (vp=0xe0e03000, cred=0xd277ff00, waitfor=2,
td=0xc03ea5a0) at /usr/src/sys/ufs/ffs/ffs_vfsops.c:810
#8 0xc030abc1 in ffs_sync (mp=0xe0c25200, waitfor=2, cred=0xd277ff00,
td=0xc03ea5a0) at /usr/src/sys/ufs/ffs/ffs_vfsops.c:810
#9 0xc025424b in sync (td=0xc03ea5a0, uap=0x0)
at /usr/src/sys/kern/vfs_syscalls.c:640
#10 0xc01fa2ab in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:353
#11 0xc01fa9dd in panic (fmt=0xc03c70de %s)
at /usr/src/sys/kern/kern_shutdown.c:353
#12 0xc036d714 in trap_fatal (frame=0xe3758ba8, eva=0)
at /usr/src/sys/i386/i386/trap.c:652
#13 0xc036d34b in trap_pfault (frame=0xe3758ba8, usermode=0, eva=0)
at /usr/src/sys/i386/i386/trap.c:652
#14 0xc036cd34 in trap (frame={tf_fs = -481361896, tf_es = -481361904,
tf_ds = -472580080, tf_edi = 0, tf_esi = -1, tf_ebp = -478835704,
tf_isp = -478835756, tf_ebx = -481313712, tf_edx = 0, tf_ecx = 1183,
tf_eax = -481313456, tf_trapno = 12, tf_err = 2, tf_eip = -1071714689,
tf_cs = 8, tf_eflags = 66182, tf_esp = -472555008, tf_ss = -481313456})
at /usr/src/sys/i386/i386/trap.c:652
#15 0xc01eee7f in _mtx_lock_sleep (m=0xe38a74b4, opts=0, file=0x0, line=0)
at /usr/src/sys/kern/kern_mutex.c:574
#16 0xc024e927 in vrele (vp=0xe38a744c) at /usr/src/sys/kern/vfs_subr.c:2030
#17 0xc01d9979 in fdfree (td=0xe34fbd50)
at /usr/src/sys/kern/kern_descrip.c:476
#18 0xc01e03a0 in exit1 (td=0xe34fbd50, rv=-256)
at /usr/src/sys/kern/kern_exit.c:448
#19 0xc01dffc8 in exit1 (td=0xe34fbd50, rv=-478835464)
at /usr/src/sys/kern/kern_exit.c:448
#20 0xc036da82 in syscall (frame={tf_fs = 47, tf_es = 47, tf_ds = 47,
tf_edi = 0, tf_esi = -1, tf_ebp = -1077938808, tf_isp = -478835340,
tf_ebx = 673230588, tf_edx = 10, tf_ecx = 673230224, tf_eax = 1,
tf_trapno = 22, tf_err = 2, tf_eip = 672833571, tf_cs = 31,
tf_eflags = 658, tf_esp = -1077938852, tf_ss =
Panic in softdep_fsync() while running VMWare in background
Hi,
I get this panic sometimes when VMWare is executing in the background
(iconified). It can take a while (a couple of hours) until it happens.
The panic string says buffer not busy, but that seems to be fallout of a
second panic during the panic. The first one seems to be caused by a
trap in softdep_fsync().
Unfortunately it looks like my line numbers are wrong. This is a GCC
3.1 kernel, -current CVSupped on May 17 22:24 GMT+2. I boot kernel and
use kernel.debug only for looking at the dump. These two should be
identical except for the symbol table, right? Or did GCC 3.1 break this
assumption?
Any clue what is causing the panic? Anything else I could provide from
the dump?
--
Regards,
Georg.
(kgdb) where
#0 0xc01fa1a4 in doadump () at /usr/src/sys/kern/kern_shutdown.c:353
#1 0xc01fa7d1 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:353
#2 0xc01fa9dd in panic (fmt=0xc03aab0b bwrite: buffer is not busy???)
at /usr/src/sys/kern/kern_shutdown.c:353
#3 0xc0240eac in bwrite (bp=0xd287585c) at /usr/src/sys/kern/vfs_bio.c:1367
#4 0xc0242635 in vfs_bio_awrite (bp=0xd287585c)
at /usr/src/sys/kern/vfs_bio.c:1367
#5 0xc01c8a67 in spec_fsync (ap=0xe3d88a24)
at /usr/src/sys/fs/specfs/spec_vnops.c:849
#6 0xc01c844e in spec_vnoperate (ap=0xe3d88a24)
at /usr/src/sys/fs/specfs/spec_vnops.c:849
#7 0xc030b72a in VOP_FSYNC (vp=0xe0e03000, cred=0xd277ff00, waitfor=2,
td=0xc03ea5a0) at /usr/src/sys/ufs/ffs/ffs_vfsops.c:810
#8 0xc030abc1 in ffs_sync (mp=0xe0c25600, waitfor=2, cred=0xd277ff00,
td=0xc03ea5a0) at /usr/src/sys/ufs/ffs/ffs_vfsops.c:810
#9 0xc025424b in sync (td=0xc03ea5a0, uap=0x0)
at /usr/src/sys/kern/vfs_syscalls.c:640
#10 0xc01fa2ab in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:353
#11 0xc01fa9dd in panic (fmt=0xc03c70de %s)
at /usr/src/sys/kern/kern_shutdown.c:353
#12 0xc036d714 in trap_fatal (frame=0xe3d88c0c, eva=1845524107)
at /usr/src/sys/i386/i386/trap.c:652
#13 0xc036d34b in trap_pfault (frame=0xe3d88c0c, usermode=0, eva=1845524107)
at /usr/src/sys/i386/i386/trap.c:652
#14 0xc036cd34 in trap (frame={tf_fs = 24, tf_es = 16, tf_ds = 16,
tf_edi = 165662208, tf_esi = 0, tf_ebp = -472347472,
tf_isp = -472347592, tf_ebx = 24, tf_edx = 1845524079, tf_ecx = 4,
tf_eax = -472347496, tf_trapno = 12, tf_err = 0, tf_eip = -1070570113,
tf_cs = 8, tf_eflags = 66182, tf_esp = -1069904279, tf_ss = 843472})
at /usr/src/sys/i386/i386/trap.c:652
#15 0xc030657f in softdep_fsync (vp=0xe42f9c30)
at /usr/src/sys/ufs/ffs/ffs_softdep.c:4603
#16 0xc0258185 in fsync (td=0xe3d7a414, uap=0xe3d88cf8)
at /usr/src/sys/kern/vfs_syscalls.c:640
#17 0xc036da82 in syscall (frame={tf_fs = 47, tf_es = 47, tf_ds = 1342242863,
tf_edi = 165662208, tf_esi = 0, tf_ebp = -1077944332,
tf_isp = -472347276, tf_ebx = 24, tf_edx = 24, tf_ecx = 3, tf_eax = 118,
tf_trapno = 22, tf_err = 2, tf_eip = 685504173, tf_cs = 31,
tf_eflags = 514, tf_esp = -1077944352, tf_ss = 47})
at /usr/src/sys/i386/i386/trap.c:652
#18 0xc035c67d in syscall_with_err_pushed () at /var/tmp//ccqhs5l0.s:128
#19 0x83cccfc in ?? ()
#20 0x83e44d2 in ?? ()
#21 0x83dd07e in ?? ()
#22 0x82cdedb in ?? ()
#23 0x28b9b8ef in ?? ()
#24 0x82bd3bc in ?? ()
#25 0x82bfdc5 in ?? ()
#26 0x28d2c1eb in ?? ()
(kgdb) frame 15
#15 0xc030657f in softdep_fsync (vp=0xe42f9c30)
at /usr/src/sys/ufs/ffs/ffs_softdep.c:4603
4603}
(kgdb) l
4598vp-v_rdev-si_mountpoint !VOP_ISLOCKED(vp, NULL)
4599(error = VFS_SYNC(vp-v_rdev-si_mountpoint, MNT_WAIT, ap-a_cred,
4600 ap-a_td)) != 0)
4601return (error);
4602return (0);
4603}
4604
4605/*
4606 * Flush the dependencies associated with an inodedep.
4607 * Called with splbio blocked.
(kgdb)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: reading kernel dump - post gcc 3.1
Am Mo, 2002-05-27 um 19.52 schrieb David O'Brien: On Mon, May 27, 2002 at 12:23:13PM +0200, Georg-W. Koltermann wrote: Please read bin/38236. I wasn't asking for general directions but for a specific solution to a current -current problem. RTFM specifically the -gstabs+ GCC option. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message Hi David, are you saying that I should compile my _kernel_ with -gstabs+, since this is a problem reading a kernel dump? If so, would you mind adding a short note to UPDATING? -- Thanks, Georg. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: reading kernel dump - post gcc 3.1
Am Sa, 2002-05-25 um 02.30 schrieb Craig Carey: [...] savecore(8) should copy a dump of the crashed kernel to /var/crash and created files kernel.0 and vmcore.0. gdb -k kernel.0 vmcore.0 hunter[13]$ gdb -k kernel.debug vmcore.19 GNU gdb 4.18 (FreeBSD) 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... Dwarf Error: Cannot handle DW_FORM_strp in DWARF reader. kernel symbol `cpuhead' not found. (kgdb) Please read bin/38236. I wasn't asking for general directions but for a specific solution to a current -current problem. -- Thanks, Georg. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
reading kernel dump - post gcc 3.1
Hi, I got a couple of kernel panics recently, some of them buffer not locked. I would like to know how I can get more information out of the dump. The system's gdb does not like the dump format any more, see also bin/38236. There is an advertised workaround in that pr of using gdb52, but I couldn't get that to work (not a core dump: File format not recognized). Am I missing something? How do you guys read your dumps? -- Regards, Georg. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cannot link C++ apps any more (GCC 3.1)
Am Di, 2002-05-21 um 21.35 schrieb Szilveszter Adam: Hello, On Tue, May 21, 2002 at 02:26:57PM +0200, Georg-W. Koltermann wrote: Hi, I am unable to link C++ apps with a recent -current. It seems I would need a new libstdc++ which was not included. My libstdc++.so is a leftover from the previous cvsup. Yes, this is correct. THe libraries libstdc++v3 and libsupc++v3 are not built for the system compiler. You can, however, use ports/lang/gcc31. Ok that works. But, since the system compiler does not include a libstdc++ any more, are there any plans on removing the /usr/bin/c++ and /usr/bin/g++ commands? Seems the are not useful any more, and may conflict with a port which installs these commands. -- Regards, Georg. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
cannot link C++ apps any more (GCC 3.1)
Hi,
I am unable to link C++ apps with a recent -current. It seems I would
need a new libstdc++ which was not included. My libstdc++.so is a
leftover from the previous cvsup.
hunter[205]$ cat gwk.cc
#include iostream
int
main(int argc, const char *argv[]) {
cout Hello, world!\n;
return 0;
}
hunter[206]$ c++ gwk.cc
/var/tmp//ccThjZcK.o: In function `main':
/var/tmp//ccThjZcK.o(.text+0x1e): undefined reference to
`ostream::operator(char const*)'
/var/tmp//ccThjZcK.o(.eh_frame+0x11): undefined reference to
`__gxx_personality_v0'
hunter[207]$
Is there any estimate to when the new libstdc++ will be in -current? Is
there a port (lang/gcc31 ?) that I should use in the meantime?
--
Regards,
Georg.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: Problem with FreeBSD dc driver and Xircom PCMCIA card
Ah, finally someone else sees what I ran into last year. Look for my posting to -current in May 2001, subject dc0 ARP problem with CISCO. At that time, the only advice I got was to hardwire speed detection (which didn't help). My solution then was to switch hardware :-( So I'm afraid this is of no help to you, except for the mee too confirmation. -- Regards, Georg. Am Mi, 2002-03-27 um 21.47 schrieb Gavin Atkinson: [...snip...] It's starting to look promising. I even get a (red) link light on the card, and once an IP is configured, ifconfig can tell if the link exists or not, though cannot establish what the speed of it is (this is into a 100M switch). However, I still have almost no network connectivity with it. An outbound ping loses 100% of packets, and hosts trying to ping it cannot arp it's MAC address. However, once I have forced an entry into the arp table of the second host, I can ping the Xircom card, albeit very slowly (snipped down for clarity): PING epsilon.ury.york.ac.uk (10.0.0.109): 56 data bytes 64 bytes from 10.0.0.109: icmp_seq=211 ttl=64 time=2020.368 ms 64 bytes from 10.0.0.109: icmp_seq=216 ttl=64 time=3030.348 ms 64 bytes from 10.0.0.109: icmp_seq=217 ttl=64 time=2020.406 ms 64 bytes from 10.0.0.109: icmp_seq=223 ttl=64 time=2020.374 ms 64 bytes from 10.0.0.109: icmp_seq=229 ttl=64 time=2020.374 ms 64 bytes from 10.0.0.109: icmp_seq=253 ttl=64 time=7070.335 ms 64 bytes from 10.0.0.109: icmp_seq=255 ttl=64 time=5050.412 ms 64 bytes from 10.0.0.109: icmp_seq=286 ttl=64 time=6060.318 ms 64 bytes from 10.0.0.109: icmp_seq=287 ttl=64 time=5050.348 ms 64 bytes from 10.0.0.109: icmp_seq=288 ttl=64 time=4040.382 ms --- epsilon.ury.york.ac.uk ping statistics --- 311 packets transmitted, 139 packets received, 55% packet loss round-trip min/avg/max/stddev = 614.382/5760.691/9090.237/2161.803 ms Note the large mean time, and the fact that I consistantly lose 55% of packets. Watching the link light, the card seems to receive the packets instantly, buffer three or four, then lose the link. WHen the link comes back, the replies to these packets all get sent back at once. I'm now at a loss as to where to go. I have no idea how to progress with this, as i'm not a kernel hacker. Has anyone seen this before? If it helps, I am using revision 3 of the card (read using pci_read_config(dev, DC_PCI_CFRV, 4) 0xff), and it's on a Toshiba ToPIC 95B cardbus bridge. If anyone can help, i'd be most greatful... Thanks, Gavin 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: HEADS UP: cvs commit: src/sys/conf kern.pre.mk (fwd)
Hi Warner, a simple cast char *baz = (char*)foo; works for me. -- Regards, Georg. At Mon, 25 Feb 2002 21:59:23 -0700 (MST), M. Warner Losh [EMAIL PROTECTED] wrote: In message: [EMAIL PROTECTED] Peter Wemm [EMAIL PROTECTED] writes: : There are a couple of offending files in the kernel still, and some : drivers. The things people are most likely to run into are: usb, inet6, : and some drivers (twe, asr etc). I've fixed a few of the low hanging fruit, but I don't know how to get rid of warnings like: const char *foo = blah; char *baz = foo; when I know they are safe. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
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: [FIXED] /dev/rtc not configured message when starting VMWare2 on -current
Yes, that seems to fix it, although I had a spontaneous system lockup
while I was running with this patch. I have no idea wether the lockup
was connected to that patch; I am running that code again right now
and it does not lockup.
Many thanks to Munehiro and Takanori.
Maybe someone else with a VMWare license could retest and then commit it?
--
Regards,
Georg.
At Sun, 10 Feb 2002 03:01:57 +0900,
Takanori Saneto wrote:
Re: Re: /dev/rtc not configured message when starting VMWare2 on -current
In article [EMAIL PROTECTED],
Munehiro Matsuda [EMAIL PROTECTED] wrote:
I have a hack^Wpatch that should fix your problem.
I think you need to prevent returning the value of uninitialized
variable (``error'') when no error should be returned.
How about following patch? (just added error = 0; line)
Index: rtc.c
===
RCS file: /export/cvsup/cvs/ports/emulators/rtc/files/rtc.c,v
retrieving revision 1.6
diff -u -r1.6 rtc.c
--- rtc.c 16 Sep 2001 07:05:18 - 1.6
+++ rtc.c 9 Feb 2002 17:54:44 -
@@ -266,10 +266,32 @@
{
int error;
+#if __FreeBSD_version = 500023
+dev_t dev;
+struct rtc_softc *sc;
+
+ if (rtc_sc!=NULL)
+ return (EINVAL);
+
+ dev = make_dev(rtc_cdevsw, 0, UID_ROOT, GID_WHEEL, 0644, DEVICE_NAME);
+ if (dev==NULL)
+ return (EINVAL);
+
+ MALLOC(sc, struct rtc_softc*, sizeof(*sc), M_DEVBUF, M_WAITOK);
+ if (sc==NULL)
+ return (EINVAL);
+
+ bzero(sc, sizeof(*sc));
+ rtc_sc = sc;
+ dev-si_drv1 = sc; /* Link together */
+ sc-dev = dev;
+ error = 0;
+#else
error = cdevsw_add(rtc_cdevsw);
if (error)
return error;
+#endif
return error;
}
--
$B$5$M$r(B (SANETO Takanori) // [$BqL#(B] $BK\6H$r$9$k$3$H(B //
$B!(B //Bonjour Chapeau //
URL:mailto:[EMAIL PROTECTED] // [$BK\6H(B] $BqL#$KAv$k$3$H(B //
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
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
/dev/rtc not configured message when starting VMWare2 on -current
Hi, since many weeks I get /dev/rtc: device not configured in -current when I start VMWare2. The VMWare2 port works fine otherwise. Yes, rtc-2001.09.16.1 is installed, and the module is loaded during startup. -- Regards, Georg. 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: Performance of -current vs -stable
At Wed, 06 Feb 2002 23:33:14 -0500 (EST), John Baldwin wrote: [...] I guess. Note that you can use a loader tunable 'debug.witness_watch' to turn witness off from the loader. If it's set to 0 witness won't be used even if it's compiled into the kernel (just a general FYI, witness(4) documents this as well). Nice feature, thanks for the hint. I can't find it documented in witness(4), however: hunter# grep -i watch /usr/src/share/man/man4/witness.4 hunter# CVSup is from Feb 6. -- Regards, Georg. 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
/dev/rtc not configured message when starting VMWare2 on -current
Hi, since many weeks I get /dev/rtc: device not configured in -current when I start VMWare2. The VMWare2 port works fine otherwise. Yes, rtc-2001.09.16.1 is installed, and the module is loaded during startup. -- Regards, Georg. 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
PCCARD not working on HP Omnibook 6100
Hi, I can't get my PCMCIA card to work on my HP Omnibook 6100. -current is from Feb 6. During boot I get: Feb 7 10:14:04 hunter kernel: pcic0: TI PCI-1420 PCI-CardBus Bridge irq 5 at device 5.0 on pci2 Feb 7 10:14:04 hunter kernel: pcic0: PCI Memory allocated: 0xd020 Feb 7 10:14:04 hunter kernel: pcic0: TI12XX PCI Config Reg: [ring enable][speaker enable][pwr save][FUNC pci int + CSC serial isa irq] Feb 7 10:14:04 hunter kernel: pccard0: PC Card bus (classic) on pcic0 Feb 7 10:14:04 hunter kernel: pci_cfgintr_linked: linked (63) to hard-routed irq 10 Feb 7 10:14:04 hunter kernel: pci_cfgintr: 0:30 INTD routed to irq 10 Feb 7 10:14:04 hunter kernel: pcib2: routed slot 5 INTB to irq 10 Feb 7 10:14:04 hunter kernel: pcic1: TI PCI-1420 PCI-CardBus Bridge irq 10 at device 5.1 on pci2 Feb 7 10:14:04 hunter kernel: pcic1: PCI Memory allocated: 0xd0201000 Feb 7 10:14:04 hunter kernel: pcic1: TI12XX PCI Config Reg: [ring enable][speaker enable][pwr save][FUNC pci int + CSC serial isa irq] Feb 7 10:14:04 hunter kernel: pccard1: PC Card bus (classic) on pcic1 Feb 7 10:14:04 hunter kernel: fxp0: Intel Pro/100 Ethernet port 0x3440-0x347f mem 0xd020-0xd0200fff irq 10 at device 8.0 on pci2 Feb 7 10:14:04 hunter kernel: fxp0: Ethernet address 00:c0:9f:05:88:52 Feb 7 10:14:05 hunter kernel: inphy0: i82562EM 10/100 media interface on miibus0 Feb 7 10:14:05 hunter kernel: inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Feb 7 10:14:05 hunter kernel: isab0: PCI-ISA bridge at device 31.0 on pci0 Feb 7 10:14:05 hunter kernel: isa0: ISA bus on isab0 Feb 7 10:14:05 hunter kernel: atapci0: Intel ICH3 ATA100 controller port 0x1820-0x182f,0x374-0x377,0x170-0x177,0x3f4-0x3f7,0x1f0-0x1f7 mem 0xd000-0xd3ff at device 31.1 on pci0 Feb 7 10:14:05 hunter kernel: ata0: at 0x1f0 irq 14 on atapci0 Feb 7 10:14:05 hunter kernel: ata1: at 0x170 irq 15 on atapci0 Feb 7 10:14:05 hunter kernel: pci0: serial bus, SMBus at device 31.3 (no driver attached) Feb 7 10:14:05 hunter kernel: ata: ata0 already exists; skipping it Feb 7 10:14:05 hunter kernel: ata: ata1 already exists; skipping it Feb 7 10:14:05 hunter kernel: pcic: pcic0 already exists; skipping it Feb 7 10:14:05 hunter kernel: pcic: pcic1 already exists; skipping it and later when pccardd starts: Feb 7 10:16:35 hunter kernel: pcib2: device pccard0 requested unsupported memory range 0xd-0xd (decoding 0xd020-0xd02f, 0xf000-0xf00f) Feb 7 10:16:35 hunter kernel: pcib2: device pccard0 requested unsupported memory range 0xd4000-0xd4000 (decoding 0xd020-0xd02f, 0xf000-0xf00f) Feb 7 10:16:35 hunter pccardd[480]: ioctl (PIOCRWMEM): Invalid argument Feb 7 10:16:40 hunter pccardd[480]: No card in database for (null)((null)) Feb 7 10:16:40 hunter pccardd[480]: pccardd started Also, only the upper PCMCIA slots seems to be active. I get a beep and some messages when I remove/insert a card in the upper slot, but with the lower slot nothing happens at all. My card is a Psion Dacom Gold Card modem. -- Regards, Georg. 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
/dev/rtc not configured message when starting VMWare2 on -current
Hi, since many weeks I get /dev/rtc: device not configured in -current when I start VMWare2. The VMWare2 port works fine otherwise. Yes, rtc-2001.09.16.1 is installed, and the module is loaded during startup. -- Regards, Georg. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
/dev/rtc not configured message when starting VMWare2 on -current
Hi, since many weeks I get /dev/rtc: device not configured in -current when I start VMWare2. The VMWare2 port works fine otherwise. Yes, rtc-2001.09.16.1 is installed, and the module is loaded during startup. -- Regards, Georg. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
PCCARD not working on HP Omnibook 6100
Hi, I can't get my PCMCIA card to work on my HP Omnibook 6100. -current is from Feb 6. During boot I get: Feb 7 10:14:04 hunter kernel: pcic0: TI PCI-1420 PCI-CardBus Bridge irq 5 at device 5.0 on pci2 Feb 7 10:14:04 hunter kernel: pcic0: PCI Memory allocated: 0xd020 Feb 7 10:14:04 hunter kernel: pcic0: TI12XX PCI Config Reg: [ring enable][speaker enable][pwr save][FUNC pci int + CSC serial isa irq] Feb 7 10:14:04 hunter kernel: pccard0: PC Card bus (classic) on pcic0 Feb 7 10:14:04 hunter kernel: pci_cfgintr_linked: linked (63) to hard-routed irq 10 Feb 7 10:14:04 hunter kernel: pci_cfgintr: 0:30 INTD routed to irq 10 Feb 7 10:14:04 hunter kernel: pcib2: routed slot 5 INTB to irq 10 Feb 7 10:14:04 hunter kernel: pcic1: TI PCI-1420 PCI-CardBus Bridge irq 10 at device 5.1 on pci2 Feb 7 10:14:04 hunter kernel: pcic1: PCI Memory allocated: 0xd0201000 Feb 7 10:14:04 hunter kernel: pcic1: TI12XX PCI Config Reg: [ring enable][speaker enable][pwr save][FUNC pci int + CSC serial isa irq] Feb 7 10:14:04 hunter kernel: pccard1: PC Card bus (classic) on pcic1 Feb 7 10:14:04 hunter kernel: fxp0: Intel Pro/100 Ethernet port 0x3440-0x347f mem 0xd020-0xd0200fff irq 10 at device 8.0 on pci2 Feb 7 10:14:04 hunter kernel: fxp0: Ethernet address 00:c0:9f:05:88:52 Feb 7 10:14:05 hunter kernel: inphy0: i82562EM 10/100 media interface on miibus0 Feb 7 10:14:05 hunter kernel: inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Feb 7 10:14:05 hunter kernel: isab0: PCI-ISA bridge at device 31.0 on pci0 Feb 7 10:14:05 hunter kernel: isa0: ISA bus on isab0 Feb 7 10:14:05 hunter kernel: atapci0: Intel ICH3 ATA100 controller port 0x1820-0x182f,0x374-0x377,0x170-0x177,0x3f4-0x3f7,0x1f0-0x1f7 mem 0xd000-0xd3ff at device 31.1 on pci0 Feb 7 10:14:05 hunter kernel: ata0: at 0x1f0 irq 14 on atapci0 Feb 7 10:14:05 hunter kernel: ata1: at 0x170 irq 15 on atapci0 Feb 7 10:14:05 hunter kernel: pci0: serial bus, SMBus at device 31.3 (no driver attached) Feb 7 10:14:05 hunter kernel: ata: ata0 already exists; skipping it Feb 7 10:14:05 hunter kernel: ata: ata1 already exists; skipping it Feb 7 10:14:05 hunter kernel: pcic: pcic0 already exists; skipping it Feb 7 10:14:05 hunter kernel: pcic: pcic1 already exists; skipping it and later when pccardd starts: Feb 7 10:16:35 hunter kernel: pcib2: device pccard0 requested unsupported memory range 0xd-0xd (decoding 0xd020-0xd02f, 0xf000-0xf00f) Feb 7 10:16:35 hunter kernel: pcib2: device pccard0 requested unsupported memory range 0xd4000-0xd4000 (decoding 0xd020-0xd02f, 0xf000-0xf00f) Feb 7 10:16:35 hunter pccardd[480]: ioctl (PIOCRWMEM): Invalid argument Feb 7 10:16:40 hunter pccardd[480]: No card in database for (null)((null)) Feb 7 10:16:40 hunter pccardd[480]: pccardd started Also, only the upper PCMCIA slots seems to be active. I get a beep and some messages when I remove/insert a card in the upper slot, but with the lower slot nothing happens at all. My card is a Psion Dacom Gold Card modem. -- Regards, Georg. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Performance of -current vs -stable
At Wed, 06 Feb 2002 23:33:14 -0500 (EST), John Baldwin wrote: [...] I guess. Note that you can use a loader tunable 'debug.witness_watch' to turn witness off from the loader. If it's set to 0 witness won't be used even if it's compiled into the kernel (just a general FYI, witness(4) documents this as well). Nice feature, thanks for the hint. I can't find it documented in witness(4), however: hunter# grep -i watch /usr/src/share/man/man4/witness.4 hunter# CVSup is from Feb 6. -- Regards, Georg. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
panic: softdep_setup_inomapdep: found inode
IdlePTD at phsyical address 0x00487000
initial pcb at physical address 0x003702c0
panicstr: bremfree: bp 0xd3bf08d0 not locked
panic messages:
---
panic: softdep_setup_inomapdep: found inode
syncing disks... panic: bremfree: bp 0xd3bf08d0 not locked
Uptime: 1h49m20s
pccbb0: pccbb_power: CARD_VCC_0V and CARD_VPP_0V [44]
pccbb1: pccbb_power: CARD_VCC_0V and CARD_VPP_0V [44]
/dev/vmmon: Module vmmon: unloaded
dumping to dev ad0s2b, offset 2000128
dump ata0: resetting devices .. done
1023 1022 [...]
---
#0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:492
492 if (!dodump)
(kgdb) t
[Current thread is 0 (process 0)]
(kgdb) where
#0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:492
#1 0xc01bf5ff in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:335
#2 0xc01bfa39 in panic (fmt=0xc02fbec2 bremfree: bp %p not locked)
at /usr/src/sys/kern/kern_shutdown.c:634
#3 0xc01eedb1 in bremfree (bp=0xd3bf08d0) at /usr/src/sys/kern/vfs_bio.c:545
#4 0xc01f0383 in vfs_bio_awrite (bp=0xd3bf08d0)
at /usr/src/sys/kern/vfs_bio.c:1534
#5 0xc01a23d8 in spec_fsync (ap=0xe7c5e88c)
at /usr/src/sys/fs/specfs/spec_vnops.c:404
#6 0xc01a1fc1 in spec_vnoperate (ap=0xe7c5e88c)
at /usr/src/sys/fs/specfs/spec_vnops.c:119
#7 0xc02813bd in ffs_sync (mp=0xc755d600, waitfor=2, cred=0xc2069b00,
td=0xc03ab804) at vnode_if.h:441
#8 0xc01fb461 in sync (td=0xc03ab804, uap=0x0)
at /usr/src/sys/kern/vfs_syscalls.c:657
#9 0xc01bf248 in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:244
#10 0xc01bfa39 in panic (fmt=0xc030dca0 softdep_setup_inomapdep: found inode)
at /usr/src/sys/kern/kern_shutdown.c:634
#11 0xc027a62a in softdep_setup_inomapdep (bp=0xd3c7bce4, ip=0xc8202200,
newinum=503542) at /usr/src/sys/ufs/ffs/ffs_softdep.c:1182
#12 0xc0274014 in ffs_nodealloccg (ip=0xc8202200, cg=46, ipref=503460,
mode=33152) at /usr/src/sys/ufs/ffs/ffs_alloc.c:1391
#13 0xc0273083 in ffs_hashalloc (ip=0xc8202200, cg=46, pref=503460,
---Type return to continue, or q return to quit---
size=33152, allocator=0xc0273e14 ffs_nodealloccg)
at /usr/src/sys/ufs/ffs/ffs_alloc.c:871
#14 0xc0272b10 in ffs_valloc (pvp=0xe78ce120, mode=33152, cred=0xc8084c00,
vpp=0xe7c5e9dc) at /usr/src/sys/ufs/ffs/ffs_alloc.c:611
#15 0xc028a252 in ufs_makeinode (mode=33152, dvp=0xe78ce120, vpp=0xe7c5ec40,
cnp=0xe7c5ec54) at /usr/src/sys/ufs/ufs/ufs_vnops.c:2264
#16 0xc0287ae8 in ufs_create (ap=0xe7c5eb38)
at /usr/src/sys/ufs/ufs/ufs_vnops.c:199
#17 0xc028a5b9 in ufs_vnoperate (ap=0xe7c5eb38)
at /usr/src/sys/ufs/ufs/ufs_vnops.c:2658
#18 0xc0200740 in vn_open_cred (ndp=0xe7c5ec2c, flagp=0xe7c5ebf8, cmode=384,
cred=0xc8084c00) at vnode_if.h:90
#19 0xc02005de in vn_open (ndp=0xe7c5ec2c, flagp=0xe7c5ebf8, cmode=384)
at /usr/src/sys/kern/vfs_vnops.c:86
#20 0xc01fbcbe in open (td=0xe7924404, uap=0xe7c5ed20)
at /usr/src/sys/kern/vfs_syscalls.c:1117
#21 0xc02c1678 in syscall (frame={tf_fs = -1070923729, tf_es = 47, tf_ds = 47,
tf_edi = 0, tf_esi = 134901314, tf_ebp = -1077940792,
tf_isp = -406459020, tf_ebx = 33256, tf_edx = 0, tf_ecx = 135024096,
tf_eax = 5, tf_trapno = 22, tf_err = 2, tf_eip = 134557391, tf_cs = 31,
tf_eflags = 647, tf_esp = -1077940852, tf_ss = 47})
at /usr/src/sys/i386/i386/trap.c:1032
#22 0xc02b58bd in syscall_with_err_pushed ()
---Type return to continue, or q return to quit---
#23 0x804a952 in ?? ()
#24 0x80485d9 in ?? ()
#25 0x8048135 in ?? ()
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
PANIC when connecting USB device
Hi,
I frequently see panics when I connect or disconnect USB devices. It
seems this is fallout from application software not handling the
device correctly, i.e. it only occurs (IIRC) after some application
program had problems with the device, an example being gphoto2 which
is currently unable to talk to my Powershot G2 camera.
Looking at the dump I get the impression that the panic that it shows
is not the original problem, it rather looks like a second panic which
occured while the kernel tried to sync the disks after a first,
invisible panic.
-current is from 1/7/2002.
The dump shows:
(kgdb) core-file vmcore.14
IdlePTD at phsyical address 0x0046f000
initial pcb at physical address 0x0035bc40
panicstr: bremfree: bp 0xd3bf08d0 not locked
panic messages:
---
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0xf
fault code = supervisor write, page not present
instruction pointer = 0x8:0xc026d340
stack pointer = 0x10:0xe300ac44
frame pointer = 0x10:0xe300ac44
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 22 (irq14: ata0)
trap number = 12
panic: page fault
syncing disks... panic: bremfree: bp 0xd3bf08d0 not locked
Uptime: 1h34m50s
pfs_vncache_unload(): 2 entries remaining
/dev/vmmon: Module vmmon: unloaded
dumping to dev ad0s2b, offset 2000128
dump ata0: resetting devices .. done
1023 1022 1021 [--trimmed--] 2 1 0
---
#0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:492
492 if (!dodump)
(kgdb) where
#0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:492
#1 0xc01b4b7b in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:335
#2 0xc01b4fb5 in panic (fmt=0xc02e9f02 bremfree: bp %p not locked)
at /usr/src/sys/kern/kern_shutdown.c:634
#3 0xc01e432d in bremfree (bp=0xd3bf08d0) at /usr/src/sys/kern/vfs_bio.c:545
#4 0xc01e58ff in vfs_bio_awrite (bp=0xd3bf08d0)
at /usr/src/sys/kern/vfs_bio.c:1534
#5 0xc0197954 in spec_fsync (ap=0xe300aaec)
at /usr/src/sys/fs/specfs/spec_vnops.c:404
#6 0xc019753d in spec_vnoperate (ap=0xe300aaec)
at /usr/src/sys/fs/specfs/spec_vnops.c:119
#7 0xc0272e35 in ffs_sync (mp=0xc7550e00, waitfor=2, cred=0xc2069b00,
td=0xc0397184) at vnode_if.h:441
#8 0xc01f09dd in sync (td=0xc0397184, uap=0x0)
at /usr/src/sys/kern/vfs_syscalls.c:657
#9 0xc01b47c4 in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:244
#10 0xc01b4fb5 in panic (fmt=0xc0308f7e %s)
at /usr/src/sys/kern/kern_shutdown.c:634
#11 0xc02b2c0f in trap_fatal (frame=0xe300ac04, eva=15)
at /usr/src/sys/i386/i386/trap.c:842
#12 0xc02b2951 in trap_pfault (frame=0xe300ac04, usermode=0, eva=15)
at /usr/src/sys/i386/i386/trap.c:756
#13 0xc02b24bb in trap (frame={tf_fs = 24, tf_es = -486539248,
---Type return to continue, or q return to quit---
tf_ds = -1070268400, tf_edi = 0, tf_esi = -948659264,
tf_ebp = -486495164, tf_isp = -486495184, tf_ebx = 0, tf_edx = -1,
tf_ecx = -946040064, tf_eax = -951159948, tf_trapno = 12, tf_err = 2,
tf_eip = -1071197376, tf_cs = 8, tf_eflags = 66182, tf_esp = -486495136,
tf_ss = -1071189245}) at /usr/src/sys/i386/i386/trap.c:426
#14 0xc026d340 in free_inodedep (inodedep=0xc79c9300)
at /usr/src/sys/ufs/ffs/ffs_softdep.c:2170
#15 0xc026f303 in handle_written_inodeblock (inodedep=0xc79c9300,
bp=0xd3c1dc8c) at /usr/src/sys/ufs/ffs/ffs_softdep.c:3796
#16 0xc026ebfa in softdep_disk_write_complete (bp=0xd3c1dc8c)
at /usr/src/sys/ufs/ffs/ffs_softdep.c:3442
#17 0xc01e6f91 in bufdone (bp=0xd3c1dc8c) at /usr/src/sys/sys/buf.h:452
#18 0xc01e6e6e in bufdonebio (bp=0xd3c1dc8c)
at /usr/src/sys/kern/vfs_bio.c:2744
#19 0xc0147881 in ad_interrupt (request=0xc7a550c0)
at /usr/src/sys/sys/bio.h:107
#20 0xc013d476 in ata_intr (data=0xc73bd380)
at /usr/src/sys/dev/ata/ata-all.c:587
#21 0xc01a8432 in ithread_loop (arg=0xc73bd300)
at /usr/src/sys/kern/kern_intr.c:533
#22 0xc01a78d8 in fork_exit (callout=0xc01a8304 ithread_loop,
arg=0xc73bd300, frame=0xe300ad48) at /usr/src/sys/kern/kern_fork.c:783
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: endless loop with gettimeofday in mozilla
At Fri, 14 Dec 2001 12:40:21 -0800 (PST), Steven G. Kargl [EMAIL PROTECTED] wrote: Switching to a vty and running truss -p mozilla's pid yields the following endless stream. gettimeofday(0x28254b6c,0x0) = 0 (0x0) sigprocmask(0x3,0x28254bfc,0x0) = 0 (0x0) sigaltstack(0x2825a5e0,0x0) = 0 (0x0) poll(0x8065000,0x2,0x0) = 0 (0x0) sigreturn(0x8058068) = -1077952316 (0xbfbfc0c4) SIGNAL 27 SIGNAL 27 gettimeofday(0x28254b6c,0x0) = 0 (0x0) sigprocmask(0x3,0x28254bfc,0x0) = 0 (0x0) sigaltstack(0x2825a5e0,0x0) = 0 (0x0) poll(0x8065000,0x2,0x0) = 0 (0x0) sigreturn(0x8058068) = -1077952316 (0xbfbfc0c4) SIGNAL 27 SIGNAL 27 Note, this is mozilla built for FreeBSD, not the linux version of mozilla. Steve, this looks similar to what I had with old (FreeBSD) versions of Netscape 4.7x. I worked around the problem by starting netscape with the -synchronous option. -- Regards, Georg. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ACPI causes immediate reboot [Omnibook 6100] ?
Hi,
I finally got around to hook up a serial console and capture the error
message. This is with ACPI_DEBUG enabled in the kernel config, but
ACPI is still loaded as a module, not configured statically.
acpi0: PTLTD EBRSDT on motherboard
ACPI-0294: *** Error: Method execution failed, AE_NOT_EXIST
What surprises me is that the debug.acpi.* settings don't seem to take
effect. Would I need to configure ACPI statically for them to work,
or is this problem just too early in the boot sequence?
And what can I try next?
--
Regards,
Georg.
snipserial console captured during bootsnip
OK show
LINES=24
acpi_load=YES
bootfile=kernel
console=comconsole
currdev=disk1s2a:
debug.acpi.disable=all
debug.acpi.layer=ACPI_HARDWARE
hint.acpi.0.oem=PTLTD
hint.acpi.0.revision=1
hint.acpi.0.rsdt=0x3ff6830a
hint.adv.0.at=isa
hint.aha.0.at=isa
hint.aic.0.at=isa
hint.apm.0.at=nexus
hint.ata.0.at=isa
hint.ata.0.irq=14
hint.ata.0.port=0x1F0
hint.ata.1.at=isa
hint.ata.1.irq=15
hint.ata.1.port=0x170
hint.atkbd.0.at=atkbdc
hint.atkbd.0.flags=0x1
hint.atkbd.0.irq=1
hint.atkbdc.0.at=isa
hint.atkbdc.0.port=0x060
hint.bt.0.at=isa
hint.cs.0.at=isa
hint.cs.0.port=0x300
hint.ed.0.at=isa
hint.ed.0.irq=10
hint.ed.0.maddr=0xd8000
hint.ed.0.port=0x280
hint.fd.0.at=fdc0
hint.fd.0.drive=0
hint.fd.1.at=fdc0
hint.fd.1.drive=1
hint.fdc.0.at=isa
hint.fdc.0.drq=2
hint.fdc.0.irq=6
hint.fdc.0.port=0x3F0
hint.fe.0.at=isa
hint.fe.0.port=0x300
hint.ie.0.at=isa
hint.ie.0.irq=10
hint.ie.0.maddr=0xd
hint.ie.0.port=0x300
hint.le.0.at=isa
hint.le.0.irq=5
hint.le.0.maddr=0xd
hint.le.0.port=0x300
hint.lnc.0.at=isa
hint.lnc.0.drq=0
hint.lnc.0.irq=10
hint.lnc.0.port=0x280
hint.npx.0.at=nexus
hint.npx.0.irq=13
hint.npx.0.port=0x0F0
hint.pcic.0.at=isa
hint.pcic.0.irq=10
hint.pcic.0.maddr=0xd
hint.pcic.0.port=0x3e0
hint.pcic.1.at=isa
hint.pcic.1.disabled=1
hint.pcic.1.irq=11
hint.pcic.1.maddr=0xd4000
hint.pcic.1.port=0x3e2
hint.pmtimer.0.at=isa
hint.ppc.0.at=isa
hint.ppc.0.irq=7
hint.psm.0.at=atkbdc
hint.psm.0.irq=12
hint.sc.0.at=isa
hint.sc.0.flags=0x100
hint.sio.0.at=isa
hint.sio.0.flags=0x10
hint.sio.0.irq=4
hint.sio.0.port=0x3F8
hint.sio.1.at=isa
hint.sio.1.irq=3
hint.sio.1.port=0x2F8
hint.sio.2.at=isa
hint.sio.2.disabled=1
hint.sio.2.irq=5
hint.sio.2.port=0x3E8
hint.sio.3.at=isa
hint.sio.3.disabled=1
hint.sio.3.irq=9
hint.sio.3.port=0x2E8
hint.sn.0.at=isa
hint.sn.0.irq=10
hint.sn.0.port=0x300
hint.vga.0.at=isa
hint.vt.0.at=isa
interpret=OK
kernel=kernel
kernel_options=
kernelname=/boot/kernel/kernel
loaddev=disk1s2a:
module_path=/boot/kernel;/boot/kernel;/boot/modules;/modules
prompt=${interpret}
OK boot
/boot/kernel/acpi.ko text=0x34d9c data=0x1090+0xbf8 syms=[0x4+0x4c80]
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 #39: Sun Dec 16 22:25:29 CET 2001
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/HUNTER
Preloaded elf kernel /boot/kernel/kernel at 0xc0446000.
Preloaded elf module /boot/kernel/snd_maestro3.ko at 0xc04460a8.
Preloaded elf module /boot/kernel/snd_pcm.ko at 0xc044615c.
Preloaded elf module /boot/kernel/acpi.ko at 0xc0446208.
Timecounter i8254 frequency 1193182 Hz
Timecounter TSC frequency 1129576481 Hz
CPU: Pentium III/Pentium III Xeon/Celeron (1129.58-MHz 686-class CPU)
Origin = GenuineIntel Id = 0x6b1 Stepping = 1
Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
real memory = 1073086464 (1047936K bytes)
avail memory = 1040580608 (1016192K bytes)
Pentium Pro MTRR support enabled
Using $PIR table, 14 entries at 0xc00fdee0
apm: Other PM system enabled.
npx0: math processor on motherboard
npx0: INT 16 interface
acpi0: PTLTD EBRSDT on motherboard
ACPI-0294: *** Error: Method execution failed, AE_NOT_EXIST
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
panic: kernel trap doesn't have ucred
Hi,
I get a panic kernel trap doesn't have ucred when I try to install
Linux ORACLE 8.1.7.
The ORACLE installation program is a JAVA application and only seems
to work with the included JRE (the IBM 1.1.8 JRE according to the
LICENSE file).
The JRE is using native Linux threads, and I know I the FreeBSD
linuxulator doesn't completely support Linux threads. It shouldn't
panic, however.
-current was CVSuped on 12/6 at 6 p.m. CET.
Any clues from the stack trace below? Anything else I should provide?
--
Regards,
Georg.
hunter# gdb -k /usr/obj/usr/src/sys/HUNTER/kernel.debug vmcore.5
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...
IdlePTD 4333568
initial pcb at 330560
panicstr: kernel trap doesn't have ucred
panic messages:
---
panic: kernel trap doesn't have ucred
panic: kernel trap doesn't have ucred
Uptime: 9h57m30s
dumping to dev ad0s2b, offset 2000128
dump ata0: resetting devices .. done
1023 1022 1021 1020 (--snip--)
---
#0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:492
492 if (!dodump)
(kgdb) where
#0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:492
#1 0xc019b6e3 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:335
#2 0xc019bb1d in panic (fmt=0xc02dfec0 kernel trap doesn't have ucred)
at /usr/src/sys/kern/kern_shutdown.c:634
#3 0xc0296660 in trap (frame={tf_fs = 24, tf_es = -1070792688, tf_ds = 16,
tf_edi = 0, tf_esi = 256, tf_ebp = -570946320, tf_isp = -570946352,
tf_ebx = 514, tf_edx = -1070159328, tf_ecx = 0, tf_eax = 18,
tf_trapno = 3, tf_err = 0, tf_eip = -1071077920, tf_cs = 8,
tf_eflags = 70, tf_esp = -1070736513, tf_ss = -1070870117})
at /usr/src/sys/i386/i386/trap.c:412
#4 0xc028a5e0 in Debugger (msg=0xc02bd19b panic) at machine/cpufunc.h:63
#5 0xc019bb08 in panic (fmt=0xc02dfec0 kernel trap doesn't have ucred)
at /usr/src/sys/kern/kern_shutdown.c:621
#6 0xc0296660 in trap (frame={tf_fs = -1072168945, tf_es = -1088487377,
tf_ds = -1071120337, tf_edi = -1088422624, tf_esi = 3,
tf_ebp = -1088422712, tf_isp = -570946200, tf_ebx = 17, tf_edx = 16,
tf_ecx = -1088422668, tf_eax = 3, tf_trapno = 9, tf_err = 28,
tf_eip = -1071071377, tf_cs = 8, tf_eflags = 65666, tf_esp = 673044849,
tf_ss = 31}) at /usr/src/sys/i386/i386/trap.c:412
#7 0xc028bf6f in doreti_iret ()
#8 0x281dd9d4 in ?? ()
#9 0x281dc55a in ?? ()
#10 0x2807feca in ?? ()
(kgdb)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: ACPI causes immediate reboot [Omnibook 6100] ?
Hi, I CVSuped yesterday and still see the problem that was discussed in this thread, i.e. immediate reset during kernel initialization when ACPI is enabled on an HP Omnibook 6100. The error message flies by so quickly that I cannot even read it. Has there been any progress towards a solution? What can I do to help? Are there any workarounds, short of disabling ACPI altogether? -- Regards, Georg. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
What happened to current.freebsd.org again?
Hello, since some time again I can't get to ftp://current.freebsd.org to download current snapshots and packages. Is the machine broken again? -- Regards, Georg. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: vmware fails on -current
At Sun, 18 Nov 2001 09:37:12 +0100 (MET), Hellmuth Michaelis wrote: Thought i update my current this morning and ran into two problem with vmware: 1) when starting vmware, vmware.sh aborts with vmware.sh: cannot create /compat/linux/dev/vmnet1: no such device or address Hi Hellmuth, that can be fixed with using /dev/vmnet1 instead of the /compat device in /usr/local/etc/rc.d/vmware.sh. I needed this change since about two months now, IIRC. Since about two weeks this no longer enough, however. I now get Could not open /dev/vmnet1: Device not configured when I start VMWare2. 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 printf's to linux_ioctl.c, and it seems the linux_ioctl_socket() gets a device name which is , i.e. the empty string. I am clueless as to where to go next. 2) after that i tried to recompile/reinstall the vmware2 port and ran into /usr/ports/emulators/vmware2/work/vmware-distrib/vmmon-only/freebsd/ \ hostif.c:177: invalid type argument of `unary *' I didn't get that error, and I am also building from source. Did you CVSUP recently? My VMWare2 Makefile is version 1.41, dated. 2001/11/11 08:36:28. -- Grüße, Georg. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: VMWare2 permission problems on -current as of Sep 26
No, I wan't using linux_kdump, thanks for the education. Today I've installed linux_kdump from the package on jp.current.freebsd.org, and now I get 1207 vmware CALL linux_access(0xbfbff759,0x4) 1207 vmware NAMI /compat/linux/home/hunter/gwk/.Xauthority 1207 vmware NAMI /home/hunter/gwk/.Xauthority 1207 vmware RET linux_access -1 errno 13 Permission denied which looks a little more meaningful (no negative errno any more, and a linux_* syscall is listed). Still needs debugging, which I'll attempt to do when I get a little time. -- Regards, Georg. At Sun, 7 Oct 2001 19:28:35 -0400 (EDT), Robert Watson wrote: On Sun, 7 Oct 2001, Georg-W. Koltermann wrote: [...] I ran the vmware command through ktrace(1) (had to do that as root since it won't trace a SUID program for a normal user), and it does get an error return from an access(2) on .Xauthority: 1207 vmware CALL access(0xbfbff759,0x4) 1207 vmware NAMI /compat/linux/home/hunter/gwk/.Xauthority 1207 vmware NAMI /home/hunter/gwk/.Xauthority 1207 vmware RET access -1 errno -13 Unknown error: -13 It seems I am going to debug the access() call next. I'm a little surprised that they're calling access(). Are you using the linux_kdump from the ports collection, btw? Otherwise the system calls aren't listed right, due to differences in system call number. Robert N M Watson FreeBSD Core Team, TrustedBSD Project [EMAIL PROTECTED] NAI Labs, Safeport Network Services To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: NIS client performance seems very poor under network load
You know, I have been using and NSD, at work on IRIX. I had trouble with it, it sometimes wouldn't sync with the nameserver, or would cease to serve any names until I HUPed it. And, seriously, I don't really understand what it's good for. Bind has been responsible for resolving host names as long as I know. WHY would anyone want to use NIS for hostname resolution? I always configure the resolver to use bind (aka named), and have NIS resolve passwd, group, alias maps etc. if I need that functionality. When I'm worried about network load, I run a local named in caching only mode. Named makes a nice system-wide cache, it is maintained well, so why bother and write another daemon for that? -- Regards, Georg. At Fri, 05 Oct 2001 16:54:05 +0930, Thyer, Matthew [EMAIL PROTECTED] wrote: Andrew Gallatin wrote: Thyer, Matthew writes: So the answer is a name service caching daemon ala nscd on Solaris. Or linux. Apparently, there is an nscd in glibc. Perhaps somebody with motivation could determine if its any good. If so, they could chop it out of glibc, make it into a port add hooks to our libc for it. (I no longer work at Duke or even use NIS, so that motivated person would not be me). To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
VMWare2 permission problems on -current as of Sep 26
Hi, I have applied the KSE patches to vmware2 that were posted on http://www.ripe.net/home/mark/files/vmware2_kse.patch.tgz. I can now build vmware2, but run into a number of permission problems running it: 1. Xlib: connection to :0.0 refused by server Xlib: Client is not authorized to connect to Server Error: Can't open display: :0 Can be worked around by chmod 644 ~/.Xauthority. 2. Cannot open /dev/tty0: permission denied (in a GUI message box). Linux /dev/tty0 seems to refer to FreeBSD /dev/ttyv0, using a chain of two symlinks. chown $USER /dev/ttyv0 doesn't seem to be effective, but chmod 666 /dev/ttyv0 makes the message go away. 3. Active virtual terminal (/dev/tty9) is not valid. Permission denied. (in a GUI message box). Seems to be like the above, Linux tty9 is really FreeBSD ttyv8, and a chown is ineffective but a chmod 666 solves it. 4. Warning: Tried to connect to session manager, Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed on stderr. Don't know if this is a problem or just a warning. 5. Permission error creating lockfiles (vmware-lock.whoever) The directory is owned by me. In summary, it seems as though the vmware binary (which is SUID root) is unable to access any files that are only accessible to the invoking user (like .Xauthority), and also unable to access any files accessible by root (like the /dev nodes). Is there a kind of changed permission policy in the new linuxulator that could cause this? By any chance, would I need to recompile the linux_base port? Is anyone using VMWare2 successfully on a recent -current? -- Regards, Georg. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cardbus nonfunctional in -current as of 9/24
At Sun, 30 Sep 2001 02:57:27 -0600, Warner Losh wrote: Try disabling acpi and let me know what's what. Warner Still the same without acpi. Last night, undocked: Sep 30 20:22:59 hunter /boot/kernel/kernel: pccbb0: TI1225 PCI-CardBus Bridge at device 4.0 on pci0 Sep 30 20:22:59 hunter /boot/kernel/kernel: pccbb0: PCI Memory allocated: 1000 Sep 30 20:22:59 hunter /boot/kernel/kernel: pci_cfgintr_linked: linked (60) to hard-routed irq 11 Sep 30 20:22:59 hunter /boot/kernel/kernel: pci_cfgintr: 0:4 INTA routed to irq 11 Sep 30 20:22:59 hunter /boot/kernel/kernel: cardbus0: Cardbus bus (newcard) on pccbb0 Sep 30 20:22:59 hunter /boot/kernel/kernel: pccard0: 16-bit PCCard bus on pccbb0 Sep 30 20:22:59 hunter /boot/kernel/kernel: pccbb1: TI1225 PCI-CardBus Bridge at device 4.1 on pci0 Sep 30 20:22:59 hunter /boot/kernel/kernel: pccbb1: PCI Memory allocated: 10001000 Sep 30 20:22:59 hunter /boot/kernel/kernel: pci_cfgintr_linked: linked (60) to hard-routed irq 11 Sep 30 20:22:59 hunter /boot/kernel/kernel: pci_cfgintr: 0:4 INTA routed to irq 11 Sep 30 20:22:59 hunter /boot/kernel/kernel: cardbus1: Cardbus bus (newcard) on pccbb1 Sep 30 20:23:00 hunter /boot/kernel/kernel: pccard1: 16-bit PCCard bus on pccbb1 Sep 30 20:23:00 hunter /boot/kernel/kernel: isab0: PCI-ISA bridge at device 7.0 on pci0 Sep 30 20:23:00 hunter /boot/kernel/kernel: isa0: ISA bus on isab0 [...] Sep 30 20:23:00 hunter /boot/kernel/kernel: acd0: DVD-ROM TOSHIBA DVD-ROM SD-C2402 at ata1-master PIO4 Sep 30 20:23:00 hunter /boot/kernel/kernel: Mounting root from ufs:/dev/ad0s4a Sep 30 20:23:00 hunter /boot/kernel/kernel: pccbb0: card inserted: event=0x, state= Sep 30 20:23:00 hunter /boot/kernel/kernel: pccbb0: Unsupported card type detected Sep 30 20:23:00 hunter /boot/kernel/kernel: pccbb1: card inserted: event=0x, state= Sep 30 20:23:00 hunter /boot/kernel/kernel: pccbb1: Unsupported card type detected Sep 30 20:23:00 hunter /boot/kernel/kernel: linprocfs registered Today, docked: Oct 1 09:01:16 hunter /boot/kernel/kernel: pccbb0: TI1225 PCI-CardBus Bridge at device 4.0 on pci0 Oct 1 09:01:16 hunter /boot/kernel/kernel: pccbb0: PCI Memory allocated: 1000 Oct 1 09:01:16 hunter /boot/kernel/kernel: pci_cfgintr_linked: linked (60) to hard-routed irq 11 Oct 1 09:01:16 hunter /boot/kernel/kernel: pci_cfgintr: 0:4 INTA routed to irq 11 Oct 1 09:01:16 hunter /boot/kernel/kernel: cardbus0: Cardbus bus (newcard) on pccbb0 Oct 1 09:01:16 hunter /boot/kernel/kernel: pccard0: 16-bit PCCard bus on pccbb0 Oct 1 09:01:16 hunter /boot/kernel/kernel: pccbb1: TI1225 PCI-CardBus Bridge at device 4.1 on pci0 Oct 1 09:01:16 hunter /boot/kernel/kernel: pccbb1: PCI Memory allocated: 10001000 Oct 1 09:01:16 hunter /boot/kernel/kernel: pci_cfgintr_linked: linked (60) to hard-routed irq 11 Oct 1 09:01:16 hunter /boot/kernel/kernel: pci_cfgintr: 0:4 INTA routed to irq 11 Oct 1 09:01:16 hunter /boot/kernel/kernel: cardbus1: Cardbus bus (newcard) on pccbb1 Oct 1 09:01:16 hunter /boot/kernel/kernel: pccard1: 16-bit PCCard bus on pccbb1 Oct 1 09:01:16 hunter /boot/kernel/kernel: isab0: PCI-ISA bridge at device 7.0 on pci0 Oct 1 09:01:16 hunter /boot/kernel/kernel: isa0: ISA bus on isab0 [...] Oct 1 09:01:17 hunter /boot/kernel/kernel: acd0: DVD-ROM TOSHIBA DVD-ROM SD-C2402 at ata1-master PIO4 Oct 1 09:01:17 hunter /boot/kernel/kernel: Mounting root from ufs:/dev/ad0s4a Oct 1 09:01:17 hunter /boot/kernel/kernel: pccbb0: card inserted: event=0x, state= Oct 1 09:01:17 hunter /boot/kernel/kernel: pccbb0: Unsupported card type detected Oct 1 09:01:17 hunter /boot/kernel/kernel: pccbb1: card inserted: event=0x, state= Oct 1 09:01:17 hunter /boot/kernel/kernel: pccbb1: Unsupported card type detected Oct 1 09:01:17 hunter /boot/kernel/kernel: linprocfs registered [...] Oct 1 09:06:03 hunter su: gwk to root on /dev/ttyp2 Oct 1 09:09:58 hunter /boot/kernel/kernel: cstsevent occures, 0xd0d0d0d0 Oct 1 09:10:33 hunter last message repeated 35 times Oct 1 09:12:34 hunter last message repeated 349 times Oct 1 09:21:11 hunter last message repeated 3687 times Oct 1 09:21:11 hunter su: gwk to root on /dev/ttyp4 Oct 1 09:21:11 hunter /boot/kernel/kernel: cstsevent occures, 0xd0d0d0d0 Oct 1 09:21:18 hunter last message repeated 66 times Oct 1 09:21:19 hunter /boot/kernel/kernel: pccbb0: card inserted: event=0x83e58955, state=403d8308 Oct 1 09:21:19 hunter /boot/kernel/kernel: pccbb0: Unsupported card type detected Oct 1 09:21:20 hunter /boot/kernel/kernel: pccbb0: card inserted: event=0x83e58955, state=403d8308 Oct 1 09:21:20 hunter /boot/kernel/kernel: pccbb0: Unsupported card type detected Oct 1 09:21:22 hunter
ACPI and APM interoperability?
Hi, I'm wondering how I should handle APM now that ACPI has basically taken over power management responsibility. It seems I still need to configure APM so that /dev/apm is there and battery monitoring utilities like the GNOME battery_applet can work. I also was able to suspend and resume my machine (DELL Inspiron 7500) with APM being configured (and ACPI being active by default). Sound is dead after a resume, PCMCIA is dead after a couple of resumes, I have to switch to text mode before suspend or else the LCD will turn pale, but still, the basic functionality is there. APM used to lockup on resume, so this is a definite improvement. Oh, and I'm wondering why a close of the lid only does a mild suspend where the laptop still hums (disk? fan?). I need to do a acpiconf -s3 in order to get it to really suspend. Is this configurable someplace? -- Regards, Georg. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ACPI and APM interoperability?
At Mon, 1 Oct 2001 08:49:10 -0600, Scott Long wrote: On Mon, Oct 01, 2001 at 10:50:17AM +0200, Georg-W. Koltermann wrote: [...] I also was able to suspend and resume my machine (DELL Inspiron 7500) with APM being configured (and ACPI being active by default). Sound is dead after a resume, What sound card? Sep 28 23:38:22 hunter /boot/kernel/kernel: pcm0: ESS Technology Maestro-2E port 0x1400-0x14ff irq 5 at device 8.0 on pci0 -- Regards, Georg. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
cardbus nonfunctional in -current as of 9/24
Hi, the latest current (CVSuped Sep 24) does not like my Cardbus system any more. I have a Dell Inspiron 7500 with a CBEM56G cardbus Ethernet/Modem combo card and an older 16 bit modem card (which hasn't been recognized by cardbus since a while). Last night, when I booted the new -current undocked at home, it said: Sep 27 22:19:57 hunter /boot/kernel/kernel: pccbb0: TI1225 PCI-CardBus Bridge at device 4.0 on pci0 Sep 27 22:19:57 hunter /boot/kernel/kernel: pccbb0: PCI Memory allocated: 1000 Sep 27 22:19:57 hunter /boot/kernel/kernel: acpi_pcib0: matched entry for 0.4.INTA (source \_SB_.PCI0.PX40.LNKA) Sep 27 22:19:57 hunter /boot/kernel/kernel: acpi_pcib0: device is routed to IRQ 11 Sep 27 22:19:57 hunter /boot/kernel/kernel: cardbus0: Cardbus bus (newcard) on pccbb0 Sep 27 22:19:57 hunter /boot/kernel/kernel: pccard0: 16-bit PCCard bus on pccbb0 Sep 27 22:19:57 hunter /boot/kernel/kernel: pccbb1: TI1225 PCI-CardBus Bridge at device 4.1 on pci0 Sep 27 22:19:57 hunter /boot/kernel/kernel: pccbb1: PCI Memory allocated: 10001000 Sep 27 22:19:57 hunter /boot/kernel/kernel: acpi_pcib0: matched entry for 0.4.INTA (source \_SB_.PCI0.PX40.LNKA) Sep 27 22:19:57 hunter /boot/kernel/kernel: acpi_pcib0: device is routed to IRQ 11 Sep 27 22:19:57 hunter /boot/kernel/kernel: cardbus1: Cardbus bus (newcard) on pccbb1 Sep 27 22:19:57 hunter /boot/kernel/kernel: pccard1: 16-bit PCCard bus on pccbb1 Sep 27 22:19:57 hunter /boot/kernel/kernel: isab0: PCI-ISA bridge at device 7.0 on pci0 Sep 27 22:19:57 hunter /boot/kernel/kernel: isa0: ISA bus on isab0 [...] Sep 27 22:19:58 hunter /boot/kernel/kernel: Mounting root from ufs:/dev/ad0s4a Sep 27 22:19:58 hunter /boot/kernel/kernel: pccbb0: card inserted: event=0x, state= Sep 27 22:19:58 hunter /boot/kernel/kernel: pccbb0: Unsupported card type detected Sep 27 22:19:58 hunter /boot/kernel/kernel: pccbb1: card inserted: event=0x, state= Sep 27 22:19:58 hunter /boot/kernel/kernel: pccbb1: Unsupported card type detected Cards would not be recognized and removals or insertions would not do anything. Today when I rebooted docked, it started the same but after a while I got: Sep 28 09:21:31 hunter /boot/kernel/kernel: cstsevent occures, 0xd0d0d0d0 Sep 28 09:22:02 hunter last message repeated 92 times Sep 28 09:22:28 hunter last message repeated 79 times Sep 28 09:22:29 hunter amd[759]: WARNING: automounter going down on signal 15 Sep 28 09:22:32 hunter /boot/kernel/kernel: cstsevent occures, 0xd0d0d0d0 Sep 28 09:23:05 hunter last message repeated 94 times Sep 28 09:24:38 hunter last message repeated 271 times [...] Sep 28 09:39:22 hunter last message repeated 25 times Sep 28 09:39:24 hunter /boot/kernel/kernel: cardbus0: detach_card: no card to detach! Sep 28 09:39:25 hunter /boot/kernel/kernel: pccbb0: pccbb_power: CARD_VCC_0V and CARD_VPP_0V [44] Sep 28 09:39:25 hunter /boot/kernel/kernel: pccbb0: bad Vcc request. ctrl=0x202a2000, status=0x6769735f Sep 28 09:39:25 hunter /boot/kernel/kernel: pccbb_power: CARD_VCC_0V and CARD_VPP_0V [44] Sep 28 09:39:26 hunter /boot/kernel/kernel: cardbus0: detach_card: no card to detach! Sep 28 09:39:26 hunter /boot/kernel/kernel: pccbb0: pccbb_power: CARD_VCC_0V and CARD_VPP_0V [44] Sep 28 09:39:27 hunter /boot/kernel/kernel: cardbus0: detach_card: no card to detach! Sep 28 09:39:27 hunter /boot/kernel/kernel: pccbb0: pccbb_power: CARD_VCC_0V and CARD_VPP_0V [44] Sep 28 09:39:29 hunter /boot/kernel/kernel: cardbus0: detach_card: no card to detach! Sep 28 09:39:29 hunter /boot/kernel/kernel: pccbb0: pccbb_power: CARD_VCC_0V and CARD_VPP_0V [44] Sep 28 09:39:32 hunter /boot/kernel/kernel: cardbus0: detach_card: no card to detach! Sep 28 09:39:32 hunter /boot/kernel/kernel: pccbb0: pccbb_power: CARD_VCC_0V and CARD_VPP_0V [44] ...and on and on, consuming 100% system cpu time. This strange state even survived a reboot (this time with ACPI disabled), and this time it no longer complained about Unsupported card types: Sep 28 09:47:15 hunter /boot/kernel/kernel: pccbb0: TI1225 PCI-CardBus Bridge mem 0x1000-0x1fff at device 4.0 on pci0 Sep 28 09:47:15 hunter /boot/kernel/kernel: pci_cfgintr_linked: linked (60) to hard-routed irq 11 Sep 28 09:47:15 hunter /boot/kernel/kernel: pci_cfgintr: 0:4 INTA routed to irq 11 Sep 28 09:47:15 hunter /boot/kernel/kernel: cardbus0: Cardbus bus (newcard) on pccbb0 Sep 28 09:47:15 hunter /boot/kernel/kernel: pccard0: 16-bit PCCard bus on pccbb0 Sep 28 09:47:15 hunter /boot/kernel/kernel: pccbb1: TI1225 PCI-CardBus Bridge mem 0x10001000-0x10001fff at device 4.1 on pci0 Sep 28 09:47:15 hunter /boot/kernel/kernel: pci_cfgintr_linked: linked (60) to hard-routed irq 11 Sep 28 09:47:15 hunter /boot/kernel/kernel: pci_cfgintr: 0:4 INTA routed to irq 11
amd not loading nfsclient.ko in -current of 9/26
Hi, after upgrading my current a few days ago I find that amd does not work any more: Sep 28 09:47:19 hunter amd[309]: /net: mount: No such file or directory Sep 28 09:47:19 hunter amd[309]: extra mkdirs required for /net Sep 28 09:47:19 hunter amd[309]: amfs_toplvl_mount: mount_amfs_toplvl failed: Operation not supported by device Sep 28 09:47:19 hunter amd[308]: /host: mount: No such file or directory Sep 28 09:47:19 hunter amd[308]: extra mkdirs required for /host Sep 28 09:47:19 hunter amd[308]: amfs_toplvl_mount: mount_amfs_toplvl failed: Operation not supported by device Sep 28 09:47:19 hunter amd[307]: /host: mount (amfs_auto_cont): Operation not supported by device Sep 28 09:47:19 hunter amd[307]: /net: mount (amfs_auto_cont): Operation not supported by device Sep 28 09:47:20 hunter apmd[366]: start ...and changing directory into /host/... does not cause any automount activity. It works ok if I manually mount an nfs file system before starting amd. The manual mount will autoload nfsclient.ko, so I figure amd shoult try to do the same. What do you think? -- Regards, Georg. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Dell laptop cardbus problem
At Sat, 15 Sep 2001 14:43:38 -0500,
Vladimir V. Egorin [EMAIL PROTECTED] wrote:
I have a Dell Latitude CPx with a Xircom RealPort
CardBus Ethernet 10/100+Modem 56 card. The card used
to work on an Aug 1, 2001 -CURRENT. I've cvsup'ed and
built the system yesterday (sep 15) and cannot make the card
work anymore. Any ideas what might be wrong? I am attaching
dmesg and kernel config (NEWCARD). I have the following
in sio.c:
static struct pci_ids pci_ids[] = {
{ 0x0103115d, Xircom Cardbus modem, 0x10 },
{ 0x, NULL, 0 }
};
[...]
sio3: configured irq 9 not in bitmap of probed irqs 0
sio3: irq maps: 0x201 0x201 0x201 0x201
sio3: probe failed test(s): 0 1 2 4 6 7 9
sio3 failed to probe at port 0x2e8-0x2ef irq 9 on isa0
I remember the probe failure. My card needed to be re-initialized to
8 bit CFCR. I'm attaching my current patch which I'm using on an
early August -current.
Warner, how about committing this patch?
--
Regards,
Georg.
sio.c.diff
Re: linux netscape hangs in -current
At Wed, 5 Sep 2001 15:50:31 -0700, Steve Kargl wrote: Linux netscape appears to be having problems with the kernel's linux compatibility module. troutmask:kargl[202] uname -a FreeBSD troutmask.apl.washington.edu 5.0-CURRENT FreeBSD 5.0-CURRENT\ #0: Fri Jul 27 16:04:55 PDT 2001 World built on 27 Jul 01. troutmask:kargl[203] ps | grep comm 82408 v0 R 4:37.11 /usr/local/lib/netscape-linux/communicator-linux-4.77 82413 v0 I 0:00.20 (dns helper) (communicator-lin) troutmask:kargl[204] truss -p 82408 gettimeofday(0x500b012c,0x0) = 2 (0x2) linux_sigreturn(0x500b01ac) = 1 (0x1) SIGNAL 14 SIGNAL 14 gettimeofday(0x500b012c,0x0) = 2 (0x2) linux_sigreturn(0x500b01ac) = 1 (0x1) SIGNAL 14 SIGNAL 14 ad nausem ^C I'm seeing the same with linux netscape 4.78 on a August 6th -current. Netscape starts hanging as soon as I try to load something complicated, e.g. animated gifs, JAVA applet, etc., and I have to kill -9 the process. It seems I can avoid the hang by running netscape -synchronous instead of just netscape. I had learned about the -synchronous flag when I ran into trouble with FreeBSD-netscape / XFree86-4 a while ago: Without the -synchronous flag I would very soon get loads of error popups saying Xlib: unexpected async reply or some such. It seems -synchronous is becoming a magic spell for netscape. -- Regards, Georg. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
cannot print to remote printer
Hi, with current as of June 20 I can no longer print to a remote printer. Syslog says filter 'f' exited (retcode=108). I added a set -x to the filter which is a shell program, and sure enough the last action it does is an exit 0. So the problem must be somewhere in lpd. -- Regards, Georg. -- Who in the world needs 2000 Windows? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Linux JDK 1.3 and hotspot (native threads)
At Mon, 30 Apr 2001 11:59:38 +0200, Georg-W. Koltermann [EMAIL PROTECTED] wrote: On Fri, Apr 27, 2001 at 09:32:58PM -0400, Andrew Gallatin wrote: Georg-W. Koltermann writes: ... In order to get real performance I would like to run either the SUN JDK with -hotspot, or the IBM 1.3 JVM. Both of these use native linux threads. With a recent -current I can successfully execute small JAVA test programs, but when I start a real application (e.g. Together from togethersoft.com), it fails with a core dump. ... Also, are there any non commercial apps that demonstrate the problem? Or at least things that I don't have to sign my life away to get access to? Hi Andrew, I just tried Forte for Java 3.0 Early Access, and it shows the above problem quite easily during startup. I ran it with truss(1), and the last part of the output is: linux_kill(0x15bc,0x20) = 2 (0x2) linux_brk(0x8232000) = 1 (0x1) linux_rt_sigprocmask(0x2,0x0,0xbfbfc73c,0x8) = 4 (0x4) write(4,0xbfbfc728,148) = 3 (0x3) linux_rt_sigprocmask(0x2,0x0,0xbfbfc6a8,0x8) = 4 (0x4) SIGNAL 32 SIGNAL 32 SIGNAL 32 linux_rt_sigsuspend(0xbfbfc6a8,0x8) ERR#4 'Interrupted system call' linux_sigreturn(0xbfbfc3a0) ERR#4 'Interrupted system call' linux_sched_getscheduler(0x15c2) ERR#1 'Operation not permitted' linux_kill(0x15c2,0x20) = 2 (0x2) linux_kill(0x15c2,0x20) = 2 (0x2) getpid() = 0 (0x0) linux_mmap(0xbfbfc9bc) = 1 (0x1) mprotect(0xbfa0e000,0x2000,0x0) = 3 (0x3) linux_mmap(0xbfbfc9bc) = 1 (0x1) linux_sigaltstack(0xbfbfc9f8,0x0)= 2 (0x2) -- System info linux_rt_sigprocmask(0x1,0xbfbfc968,0x0,0x8) = 4 (0x4) linux_sched_getscheduler(0x15b9) ERR#1 'Operation not permitted' Product Version = Forte for Java, CE v. 3.0 (Build 010523) IDE Versioning= IDE/1 spec=1.2.1 impl=010523 Operating System = Linux version 2.2.12 running on i386 Java; VM; Vendor = 1.3.1; Java HotSpot(TM) Client VM 1.3.1-b24; Sun Microsystems Inc. Java Home = /opt/jdk1.3.1/jre System Locale = en_US (f4j_ce) Home Dir; Current Dir = /home/hunter/gwk; /home/hunter/gwk IDE Install; User Dir = /opt/forte30; /home/hunter/gwk/ffjuser30 CLASSPATH = /opt/forte30/lib/patches/openide-compat.jar:/opt/forte30/lib/ext/bsh-1_0-fj.jar:/opt/forte30/lib/ext/cmd.jar:/opt/forte30/lib/ext/cosnaming.jar:/opt/forte30/lib/ext/dd2beans.jar:/opt/forte30/lib/ext/ddl.jar:/opt/forte30/lib/ext/fjscript.jar:/opt/forte30/lib/ext/fscontext.jar:/opt/forte30/lib/ext/idlcompilers.jar:/opt/forte30/lib/ext/jaas.jar:/opt/forte30/lib/ext/jaxp.jar:/opt/forte30/lib/ext/jh.jar:/opt/forte30/lib/ext/jndi.jar:/opt/forte30/lib/ext/ldap.jar:/opt/forte30/lib/ext/ldapbp.jar:/opt/forte30/lib/ext/logger.jar:/opt/forte30/lib/ext/nis.jar:/opt/forte30/lib/ext/openorb-1.0.2.jar:/opt/forte30/lib/ext/oracle.jar:/opt/forte30/lib/ext/parser.jar:/opt/forte30/lib/ext/pbembeddedeval.jar:/opt/forte30/lib/ext/providerutil.jar:/opt/forte30/lib/ext/regexp.jar:/opt/forte30/lib/ext/rmi-ext.jar:/opt/forte30/lib/ext/rmiregistry.jar:/opt/forte30/lib/ext/sax2.jar:/opt/forte30/lib/ext/servlet.jar:/opt/forte30/lib/ext/xerces.jar:/opt/forte30/lib/ext/jdbc20x.zip:/opt/forte30/lib/locale/core_f4j.jar:/opt/forte30/lib/locale/core_f4j_ce.jar:/opt/forte30/lib/locale/openide_f4j.jar:/opt/forte30/lib/core.jar:/opt/forte30/lib/openide-fs.jar:/opt/forte30/lib/openide-nodes.jar:/opt/forte30/lib/openide-util.jar:/opt/forte30/lib/openide.jar:/opt/jdk1.3.1/lib/dt.jar:/opt/jdk1.3.1/lib/htmlconverter.jar:/opt/jdk1.3.1/lib/tools.jar --- linux_rt_sigprocmask(0x2,0x0,0xbfbfc9cc,0x8) = 4 (0x4) Unexpected Signal : 11 occurred at PC=0x806535a Function name=(N/A) Library=(N/A) NOTE: We are unable to locate the function name symbol for the error just occurred. Please refer to release documentation for possible reason and solutions. Current Java thread: Dynamic libraries: Can not get information for pid = 5570 Local Time = Fri Jun 8 23:14:38 2001 Elapsed Time = 2 # # HotSpot Virtual Machine Error : 11 # Error ID : 4F530E43505002CC # Please report this error at # http://java.sun.com/cgi-bin/bugreport.cgi # # Java VM: Java HotSpot(TM) Client VM (1.3.1-b24 mixed mode) # # An error report file has been saved as hs_err_pid5570.log. # Please refer to the file
Re: lockup after resume
On Mon, Apr 09, 2001 at 11:10:54AM +0200, Dag-Erling Smorgrav wrote: Georg-W. Koltermann [EMAIL PROTECTED] writes: I am experiencing a strange lockup with -current as of about a week ago: It will suspend and resume, but after the resume the console is dead and the system hangs after a short while. I'm seeing this too on my laptop. Used to work fine, no longer does. I'll try the latest greatest and see if the problem goes away. DES Dag-Erling, I CVSuped twice since my initial report, and the problem is still there. On the other hand I have a report from David Wolfskill that suspend/resume works fine for him. a) Does suspend/resume now work for you? b) What hardware/firmware do you have (mine is a DELL Inspiron 7500 with BIOS rev A12)? c) David, since it seems to work for you, what hardware/firmware do you have? One surprising observation: If I disable APM in /boot/device.hints, my machine suspends and resumes JUST FINE. The BIOS alone seems to be able to suspend and awake the hardware behind FreeBSD's back. The system only hangs if FreeBSD is involved in the process. -- Regards, Georg. -- Who in the world needs 2000 Windows? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Linux JDK 1.3 and hotspot (native threads)
On Fri, Apr 27, 2001 at 09:32:58PM -0400, Andrew Gallatin wrote: Georg-W. Koltermann writes: ... In order to get real performance I would like to run either the SUN JDK with -hotspot, or the IBM 1.3 JVM. Both of these use native linux threads. With a recent -current I can successfully execute small JAVA test programs, but when I start a real application (e.g. Together from togethersoft.com), it fails with a core dump. ... Can you try the kernel patch in http://www.freebsd.org/cgi/query-pr.cgi?pr=26705 It sounds like this is going to get committed soon, but I'd like to know if it has any affect on your problem. Hi Drew, I tried the patch and found it makes no difference. The current SUN JVM (1.3.0_02) gives the SIG11 as I indicated before. The latest IBM JVM (IBM build cx130-20010329) hangs around and eats up CPU time. It mostly eats system time (usage is about 8% user, 91% system). A normal kill is ineffective, I have to send it a -9 in order to terminate. Also, are there any non commercial apps that demonstrate the problem? Or at least things that I don't have to sign my life away to get access to? Hmm, I don't use any. We are developing a large-scale JAVA servlet application, and that one provokes the SIG11, too. Moneydance, a shareware finance manager that I once evaluated (http://www.seanreilly.com), seems to run ok. If you really want to invest the time, you might go to togethersoft.com and download their product. They will send you an evaluation license as soon as you download the product, without any further request. But it's a big application, and you won't have any use for it unless you develop a large-scale JAVA application. -- Regards, Georg. -- Who in the world needs 2000 Windows? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: lockup after resume
On Thu, Mar 29, 2001 at 07:19:20PM +1000, Bruce Evans wrote: On Wed, 28 Mar 2001, Georg-W. Koltermann wrote: I am experiencing a strange lockup with -current as of about a week ago: It will suspend and resume, but after the resume the console is dead and the system hangs after a short while. When I type on the console after a resume, nothing is shown, neither echo nor command output. If I break into DDB, the output suddenly appears, just above the DDB prompt. I can continue to UNIX, type another command, again nothing visible. Breaking into DDB again shows what I typed, and the output. After a few round-trips of this sort the system locks up solidly. If I'm in X (XFree86-4.0.2) after the resume, the system will respond for a few seconds and then lock up. All this happens with the GENERIC kernel as well as my cardbus kernel. Should I assume the console needs resetting after the resume? How could I try a reset? I can't find anything obvious in vidcontrol(1) or kbdcontrol(1). Assume that the i8254 needs reinitializing. The console driver just uses timeouts for screen updates. Timeouts depend on the i8254 generating interrupts. When you break into ddb, the screen gets updated directly. I did some more debugging last night. I confirmed by a printf() that i8254_restore() actually *IS* being called during the resume. That routine is now in pmtimer.c, it used to be in apm.c in 4.2-R (and with 4.2 resume works fine on my laptop). I added an additional call to i8254_restore() to the end of apm_resume(), and I also called it directly from DDB--no effect. There must be some other problem, I guess. I figure there are a couple of laptop owners running current. Is suspend/resume working for all of you other guys, besides me and Dag-Erling? -- Regards, Georg. -- Who in the world needs 2000 Windows? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Linux JDK 1.3 and hotspot (native threads)
I remember some reports of success running Linux JAVA with native threads on -current. I've tried several times myself, and can't get it to work. The Linux JDK 1.3 (SUN's version) runs fine on -current as well as 4.x as long as I use the classic VM. This version doesn't use native Linux threads. In order to get real performance I would like to run either the SUN JDK with -hotspot, or the IBM 1.3 JVM. Both of these use native linux threads. With a recent -current I can successfully execute small JAVA test programs, but when I start a real application (e.g. Together from togethersoft.com), it fails with a core dump. The SUN JDK 1.3 gives # # HotSpot Virtual Machine Error, Unexpected Signal 11 # Please report this error at # http://java.sun.com/cgi-bin/bugreport.cgi # # Error ID: 4F533F4C494E55580E43505005BC # # Problematic Thread: prio=671556272 tid=0x804f790 nid=0x2940 runnable # and the IBM JDK 1.3 dies with a similar message. Is anybody successfully using a Linux JVM with native threads on -current? Are there any pathes that you needed to apply? -- Regards, Georg. -- Who in the world needs 2000 Windows? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
