Re: kp_proc and kp_eproc
On Fri, Apr 04, 2003 at 06:36:15PM -0800, Kris Kennaway wrote: On Fri, Apr 04, 2003 at 06:07:12PM -0600, Glenn Johnson wrote: On Fri, Apr 04, 2003 at 03:54:05PM -0800, Julian Elischer wrote: yes.. The entire process structure and it's surrounding enviroment has been through a blender. What do you wnat to do? I would like to learn what I need to do to get the software to compile on FreeBSD-5. I guess the question is, what information do I need to provide? The software in question is OpenPBS (http://www.openpbs.org), so it nothing proprietary. There were a whole bunch of dependency problems that I worked through manually and finally got to the point of the kp_proc failure. Here is a snippet of code that produces the failure: Here are untested patches I made for this a while ago. There's also a port PR somewhere. Thanks, I will give it a try, but probably not until Monday when I get back to work. Since you said you made this a while ago and it is untested, does that mean that you once used PBS and are using something else in its stead. I ask because I would really like to replace it with something else. I have been looking at SGE but it seems the FreeBSD port of that may not be quite ready. -- Glenn Johnson ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Building 5-CURRENT world under 4-STABLE?
Is it supported to be running under a 4-STABLE world and build a 5-CURRENT world? I have a dual-boot laptop with both 4 5 in separate partitions and cross-mounted appropriately. 5-RELEASE seems to occasionally Integer Exception out (seems to be with my wi card in), so I was wondering if it was supported to: cd /current/usr/src make buildworld Thanks, LER -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Building 5-CURRENT world under 4-STABLE?
On Fri, Apr 04, 2003 at 10:12:09AM -0600, Larry Rosenman wrote: Is it supported to be running under a 4-STABLE world and build a 5-CURRENT world? Yes. Kris pgp0.pgp Description: PGP signature
Re: Building 5-CURRENT world under 4-STABLE?
On Fri, Apr 04, 2003 at 08:57:38AM -0800, Kris Kennaway wrote: On Fri, Apr 04, 2003 at 10:12:09AM -0600, Larry Rosenman wrote: Is it supported to be running under a 4-STABLE world and build a 5-CURRENT world? Yes. Currently it is supported, but may not be soon. The issue was brought up with Technical Review Board who are currently in the process of voting on the supported upgrade path matrix (both native and cross arch), and one possibility might be that the only supported upgrade path will be from 4-STABLE to 5.0-RELEASE, and only then to 5.0-CURRENT. Even if this will be ratified, I will still continue to work on a wider update range that will be available in the form of patches. Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age pgp0.pgp Description: PGP signature
Integer Exception/5-CURRENT/cbb related
I just upgraded my laptop's HDD from 20G to 60G, and set it up as a dual boot 4-STABLE and 5-CURRENT. When running under BOTH 5.0-RELEASE and 5.0-CURRENT from today, with my LinkSys WPC11 V3.0 card in, I get random Integer Exception panics. The 5.0-CURRENT dropped me in to DB, and the backtrace pointed to cbb. This is my first experience with 5.0, so I'm not sure what I need to do to get all the pieces for someone to look at it. I'm more than willing to get whatever information y'all need. Thanks, LER -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Building 5-CURRENT world under 4-STABLE?
On Fri, 4 Apr 2003 20:41:14 +0300 Ruslan Ermilov [EMAIL PROTECTED] wrote: RE Currently it is supported, but may not be soon. The RE issue was brought up with Technical Review Board who RE are currently in the process of voting on the supported RE upgrade path matrix (both native and cross arch), and RE one possibility might be that the only supported upgrade RE path will be from 4-STABLE to 5.0-RELEASE, and only then RE to 5.0-CURRENT. I've a feeling that there are a fair number of folks planning on going 4-STABLE to 5-STABLE when it happens. It would be nice if that path were smooth. -- C:WIN | Directable Mirrors The computer obeys and wins.|A Better Way To Focus The Sun You lose and Bill collects. | licenses available - see: | http://www.sohara.org/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Integer Exception/5-CURRENT/cbb related
Ok, I got a panic dump:
Script started on Fri Apr 4 14:25:59 2003
lerlaptop# shutdown -r now?[12`cd /?[K
?[Klerlaptop# k??[Kgdb -k kernel.1 vmcore.1
GNU gdb 5.2.1 (FreeBSD)
Copyright 2002 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-undermydesk-freebsd...
panic: integer divide fault
panic messages:
---
Fatal trap 18: integer divide fault while in kernel mode
instruction pointer = 0x8:0xc0193d12
stack pointer = 0x10:0xd63cecc0
frame pointer = 0x10:0xd63cece0
code segment = base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = interrupt enabled, IOPL = 0
current process = 23 (irq11: cbb0 cbb1+++)
trap number = 18
panic: integer divide fault
syncing disks, buffers remaining... 3798 3798 3797 3797 3797 3797 3797 3797
3797 3797 3797 3797 3797 3797 3797 3797 3797 3797 3797 3797 3797 3797
giving up on 2250 buffers
Uptime: 2m27s
Dumping 503 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
---
Reading symbols from
/usr/obj/usr/src/sys/LERLAPTOP/modules/usr/src/sys/modules/acpi/acpi.ko.deb
ug...done.
Loaded symbols for
/usr/obj/usr/src/sys/LERLAPTOP/modules/usr/src/sys/modules/acpi/acpi.ko.deb
ug
Reading symbols from
/usr/obj/usr/src/sys/LERLAPTOP/modules/usr/src/sys/modules/linux/linux.ko.d
ebug...done.
Loaded symbols for
/usr/obj/usr/src/sys/LERLAPTOP/modules/usr/src/sys/modules/linux/linux.ko.d
ebug
#0 doadump () at /usr/src/sys/kern/kern_shutdown.c:239
239 dumping++;
(kgdb) bt
#0 doadump () at /usr/src/sys/kern/kern_shutdown.c:239
#1 0xc0245b1a in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:371
#2 0xc0245d93 in panic () at /usr/src/sys/kern/kern_shutdown.c:542
#3 0xc039a10e in trap_fatal (frame=0xc14eb130, eva=0)
at /usr/src/sys/i386/i386/trap.c:843
#4 0xc0399c02 in trap (frame=
{tf_fs = -1051852776, tf_es = -1051852784, tf_ds = -700710896, tf_edi
= -1051807440, tf_esi = -1051832832, tf_ebp = -700650272, tf_isp =
-700650324, tf_ebx = -1007012800, tf_edx = -546881536, tf_ecx =
-1069393536, tf_eax = 0, tf_trapno = 18, tf_err = 0, tf_eip = -1072087790,
tf_cs = 8, tf_eflags = 514, tf_esp = -1071394701, tf_ss = 132}) at
/usr/src/sys/i386/i386/trap.c:640
#5 0xc038b318 in calltrap () at {standard input}:96
#6 0xc0234502 in ithread_loop (arg=0xc3f8aa00)
at /usr/src/sys/kern/kern_intr.c:536
#7 0xc0233742 in fork_exit (callout=0xc02343b0 ithread_loop, arg=0x0,
frame=0x0) at /usr/src/sys/kern/kern_fork.c:796
(kgdb) lerlaptop# ^D??exit
Script done on Fri Apr 4 14:26:16 2003
I have the core, and the kernel. DMESG:
Copyright (c) 1992-2003 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 #1: Fri Apr 4 12:04:46 CST 2003
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/LERLAPTOP
Preloaded elf kernel /boot/kernel/kernel at 0xc0573000.
Preloaded elf module /boot/kernel/acpi.ko at 0xc05730a8.
Timecounter i8254 frequency 1193182 Hz
Timecounter TSC frequency 1129573614 Hz
CPU: Intel(R) Pentium(R) III Mobile CPU 1133MHz (1129.57-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 = 527958016 (503 MB)
avail memory = 506736640 (483 MB)
Allocating major#253 to net
Allocating major#252 to g_ctl
Allocating major#251 to pci
Pentium Pro MTRR support enabled
npx0: math processor on motherboard
npx0: INT 16 interface
acpi0: FUJERG on motherboard
ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15
ACPI-0625: *** Info: GPE Block1 defined as GPE16 to GPE31
pcibios: BIOS version 2.10
Using $PIR table, 9 entries at 0xc00fdf30
acpi0: power button is handled as a fixed feature programming model.
Timecounter ACPI-fast frequency 3579545 Hz
acpi_timer0: 24-bit timer at 3.579545MHz port 0xfc08-0xfc0b on acpi0
acpi_cpu0: CPU port 0x530-0x537 on acpi0
pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0
pci0: ACPI PCI bus on pcib0
agp0: Intel 82830M (830M GMCH) SVGA controller mem
0xe000-0xe007,0xe800-0xefff irq 11 at device 2.0 on pci0
agp0: detected 8060k stolen memory
agp0: aperture size is 128M
pci0: display at device 2.1 (no driver attached)
uhci0: Intel 82801CA/CAM (ICH3) USB controller USB-A port 0x18c0-0x18df
irq 11 at device 29.0 on pci0
usb0: Intel 82801CA/CAM (ICH3) USB controller USB-A on uhci0
usb0: USB revision 1.0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1: Intel 82801CA/CAM (ICH3)
Re: LOR on libthr exit (iirc)
In the last episode (Apr 02), Jeff Roberson said: On Wed, 2 Apr 2003, Gordon Tetlow wrote: I think it was a libthr linked app after I killed it: Yeah, this is a problem with the thread single exit and suspend code. I haven't fixed it yet. Thanks for the report. I get the same LOR message on my machine, but it is always immediately followed by a panic. libthr also seems to only work with WITNESS. Without it the machine locks up hard (serial debugger doesn't even respond) when you start any libthr-linked app. Fatal trap 12: page fault while in kernel mode cpuid = 0; lapic.id = 0300 fault virtual address = 0xa0 fault code = supervisor read, page not present instruction pointer = 0x8:0xc03a1f72 stack pointer = 0x10:0xdff75c58 frame pointer = 0x10:0xdff75c84 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 = Idle trap number = 12 panic: page fault cpuid = 0; lapic.id = 0300 Stack backtrace: panic(c03d95fc,c0406ad0,1,1,1) at panic+0x11b trap_fatal(dff75c18,a0,c043d120,c047df20,c40da850) at trap_fatal+0x28d trap_pfault(dff75c18,0,a0,c40d7d88,a0) at trap_pfault+0x17a trap(c40d0018,c40d0010,dff70010,c40d7d88,0) at trap+0x3e5 calltrap() at calltrap+0x5 --- trap 0xc, eip = 0xc03a1f72, esp = 0xdff75c58, ebp = 0xdff75c84 --- cpu_throw(c40d7d20,0,c03f0e89,7a9,c03f140a) at cpu_throw+0x12 thread_suspend_check(0,0,c03f2a5b,68,c40d7d88) at thread_suspend_check+0xd8 userret(c40da850,dff75d48,0,404,3) at userret+0x24b syscall(2f,2f,2f,0,82f8000) at syscall+0x167 Xint0x80_syscall() at Xint0x80_syscall+0x1d --- syscall (0), eip = 0x28250e43, esp = 0xbfafee90, ebp = 0xbfafef2c --- -- Dan Nelson [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mbuf LOR
On Thu, 3 Apr 2003, Andrew Gallatin wrote:
Nate Lawson writes:
I was testing some changes to make fxp MPSAFE and got a LOR in allocating
the mbuf cluster and then finally a panic when trying to dereference the
cluster header. Is the mbuf system MPSAFE? Is it ok to call m_getcl
with a device lock held (but not Giant)?
The lock reversal was: 1. fxp softc lock, 2. Giant.
I think the only place it can be coming from is slab_zalloc().
Does the appended (untested) patch help?
BTW, I don't think that there is any need to get Giant for the zone
allocators in the M_NOWAIT case, but I'm not really familar with the
code, and I don't know if the sparc64 uma_small_alloc needs Giant.
BTW, my MPSAFE driver never sees this, but then again, I never
allocate clusters. I use jumbo frames, and carve out my own recv
buffers, so I'm only allocating mbufs, not clusters.
Drew
Index: uma_core.c
===
RCS file: /home/ncvs/src/sys/vm/uma_core.c,v
retrieving revision 1.51
diff -u -r1.51 uma_core.c
--- uma_core.c26 Mar 2003 18:44:53 - 1.51
+++ uma_core.c3 Apr 2003 18:22:14 -
@@ -703,10 +703,14 @@
wait = ~M_ZERO;
if (booted || (zone-uz_flags UMA_ZFLAG_PRIVALLOC)) {
- mtx_lock(Giant);
- mem = zone-uz_allocf(zone,
- zone-uz_ppera * UMA_SLAB_SIZE, flags, wait);
- mtx_unlock(Giant);
+ if ((wait M_NOWAIT) == 0) {
+ mtx_lock(Giant);
+ mem = zone-uz_allocf(zone,
+ zone-uz_ppera * UMA_SLAB_SIZE, flags, wait);
+ mtx_unlock(Giant);
+ } else {
+ mem = NULL;
+ }
if (mem == NULL) {
ZONE_LOCK(zone);
return (NULL);
You're right about where the problem is (top of stack trace and listing
below). However, your patch causes an immediate panic on boot due to a
NULL deref. I don't think you want it to always return NULL if called
with M_NOWAIT set. :) Other ideas?
slab_zalloc + 0xdf
uma_zone_slab + 0xd8
uma_zalloc_bucket + 0x15d
uma_zalloc_arg + 0x307
malloc
...
m_getcl
(gdb) l *slab_zalloc+0xdf
0xc02f646f is in slab_zalloc (../../../vm/uma_core.c:707).
702 else
703 wait = ~M_ZERO;
704
705 if (booted || (zone-uz_flags UMA_ZFLAG_PRIVALLOC)) {
706 mtx_lock(Giant);
707 mem = zone-uz_allocf(zone,
708 zone-uz_ppera * UMA_SLAB_SIZE, flags, wait);
709 mtx_unlock(Giant);
710 if (mem == NULL) {
711 ZONE_LOCK(zone);
-Nate
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
cbb0: Could not map register memory
I cannot use my cardbus slots on -current. My dmesg is: cbb0: TI1420 PCI-CardBus Bridge mem 0x5000-0x5fff irq 11 at device 0.0 on pci2 cbb0: Could not map register memory device_probe_and_attach: cbb0 attach returned 12 cbb0: TI1420 PCI-CardBus Bridge mem 0x5100-0x51000fff irq 11 at device 0.1 on pci2 cbb0: Could not map register memory device_probe_and_attach: cbb0 attach returned 12 I am running with the following in device.hints: hw.acpi.ec.event_driven=1 hw.cbb.start_memory=0x2000 hw.cbb.debug=1 hw.cardbus.debug=1 hw.cardbus.cis_debug=1 hw.pccard.debug=1 hw.pccard.cis_debug=1 I get the same errors whether or not ACPI is enabled. This is on a IBM T23, 1 ghz, 384 MB ram. -Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cbb0: Could not map register memory
On Fri, 4 Apr 2003 00:05:57 -0800 (PST) Nate Lawson [EMAIL PROTECTED] wrote: I cannot use my cardbus slots on -current. My dmesg is: cbb0: TI1420 PCI-CardBus Bridge mem 0x5000-0x5fff irq 11 at device 0.0 on pci2 cbb0: Could not map register memory device_probe_and_attach: cbb0 attach returned 12 cbb0: TI1420 PCI-CardBus Bridge mem 0x5100-0x51000fff irq 11 at device 0.1 on pci2 cbb0: Could not map register memory device_probe_and_attach: cbb0 attach returned 12 I seem to recall that i had a smililar problem with my Asus L1400. I tried with hw.pci.allow_unsupported_io_range=1 in my /boot/loader.conf hope that helps kind regards Søren Vrist ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
OOOPS - portupgrade/Swapfile/???
Hey guys, Just did a CVSup, and did a portupgrade -rRa. I watched it install libxml update and fontconfig and apache2. I then left it to its things and went to get a coffee On return, I got the login screen for KDE??? So I logged in and tried to run portupgrade -rRa again just to confirm everything was done and it returned me to the login screen. I rebooted into console and ran the same command. I then get repeated application kills due to swap file full...Never had that before. Watching with swapinfo, my 500Mb (256 Mb Ram) swapfile just fills up...on stopping portupgrade, swap file is emptied... Any ideas what is going on? Thanks, Anthony just a quick snip: pr 4 10:52:23 intra241 su: carteran to root on /dev/ttyp6 Apr 4 11:05:01 intra241 kernel: swap_pager: out of swap space Apr 4 11:05:02 intra241 kernel: swap_pager_getswapspace: failed Apr 4 11:05:03 intra241 kernel: pid 589 (kdeinit), uid 1001, was killed: out of swap space Apr 4 11:05:04 intra241 kernel: swap_pager_getswapspace: failed Apr 4 11:05:08 intra241 last message repeated 246 times Apr 4 11:05:08 intra241 kernel: pid 517 (XFree86), uid 0, was killed: out of swap space Apr 4 11:05:16 intra241 kernel: swap_pager_getswapspace: failed Apr 4 11:05:16 intra241 last message repeated 5 times Apr 4 11:05:14 intra241 kdm[508]: Server for display :0 terminated unexpectedly Apr 4 11:05:16 intra241 kernel: swap_pager_getswapspace: failed Apr 4 11:05:20 intra241 last message repeated 173 times Apr 4 11:05:20 intra241 kernel: pid 2746 (kdeinit), uid 1001, was killed: out of swap space Apr 4 11:05:21 intra241 kernel: swap_pager_getswapspace: failed Apr 4 11:05:28 intra241 last message repeated 224 times Apr 4 11:05:28 intra241 kernel: pid 1187 (kmail), uid 1001, was killed: out of swap space Apr 4 11:05:30 intra241 kernel: pid 1187 (kmail), uid 1001, was killed: out of swap space Apr 4 11:05:30 intra241 kernel: swap_pager_getswapspace: failed Apr 4 11:05:34 intra241 last message repeated 129 times Apr 4 11:05:34 intra241 kernel: pid 575 (kdeinit), uid 1001, was killed: out of swap space Apr 4 11:05:34 intra241 kernel: swap_pager_getswapspace: failed Apr 4 11:05:38 intra241 last message repeated 196 times Apr 4 11:05:38 intra241 kernel: pid 561 (kdeinit), uid 1001, was killed: out of swap space Apr 4 11:05:39 intra241 kernel: pid 561 (kdeinit), uid 1001, was killed: out of swap space 1%Apr 4 09:00:00 intra241 newsyslog[2088]: logfile turned over due to size100K Apr 4 09:27:51 intra241 su: carteran to root on /dev/ttyp0 Apr 4 10:01:34 intra241 su: carteran to root on /dev/ttyp1 Apr 4 10:17:23 intra241 su: carteran to root on /dev/ttyp2 Apr 4 10:27:45 intra241 su: carteran to root on /dev/ttyp3 Apr 4 10:41:23 intra241 kernel: pid 15130 (conftest), uid 0: exited on signal 12 (core dumped) Apr 4 10:51:21 intra241 su: carteran to root on /dev/ttyp5 Apr 4 10:52:23 intra241 su: carteran to root on /dev/ttyp6 Apr 4 11:05:01 intra241 kernel: swap_pager: out of swap space Apr 4 11:05:02 intra241 kernel: swap_pager_getswapspace: failed Apr 4 11:05:03 intra241 kernel: pid 589 (kdeinit), uid 1001, was killed: out of swap space Apr 4 11:05:04 intra241 kernel: swap_pager_getswapspace: failed Apr 4 11:05:08 intra241 last message repeated 246 times Apr 4 11:05:08 intra241 kernel: pid 517 (XFree86), uid 0, was killed: out of swap space Apr 4 11:05:16 intra241 kernel: swap_pager_getswapspace: failed Apr 4 11:05:16 intra241 last message repeated 5 times Apr 4 11:05:14 intra241 kdm[508]: Server for display :0 terminated unexpectedly Apr 4 11:05:16 intra241 kernel: swap_pager_getswapspace: failed Apr 4 11:05:20 intra241 last message repeated 173 times ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: OOOPS - portupgrade/Swapfile/???
MoreThis time outside of X11 and KDE...Just in console: Apr 4 11:26:43 intra241 kernel: pid 476 (httpd), uid 80, was killed: out of swap space Apr 4 11:26:43 intra241 kernel: pid 11877 (sort), uid 0, was killed: out of swap space Apr 4 11:26:43 intra241 last message repeated 2 times Apr 4 11:26:44 intra241 kernel: pid 475 (httpd), uid 80, was killed: out of swap space Apr 4 11:26:44 intra241 kernel: swap_pager_getswapspace: failed Apr 4 11:26:44 intra241 kernel: pid 2780 (sort), uid 0, was killed: out of swap space Apr 4 11:26:45 intra241 kernel: swap_pager: out of swap space Apr 4 11:26:45 intra241 kernel: swap_pager_getswapspace: failed Apr 4 11:26:45 intra241 kernel: pid 11914 (sort), uid 0, was killed: out of swap space Apr 4 11:26:45 intra241 kernel: pid 11942 (sort), uid 0, was killed: out of swap space Apr 4 11:26:45 intra241 kernel: pid 11961 (sort), uid 0, was killed: out of swap space Apr 4 11:26:46 intra241 kernel: pid 11998 (sort), uid 0, was killed: out of swap space Apr 4 11:26:46 intra241 kernel: pid 12026 (sort), uid 0, was killed: out of swap space Apr 4 11:26:46 intra241 kernel: pid 12045 (sort), uid 0, was killed: out of swap space Apr 4 11:26:46 intra241 kernel: pid 12082 (sort), uid 0, was killed: out of swap space Apr 4 11:26:47 intra241 kernel: pid 12110 (sort), uid 0, was killed: out of swap space Apr 4 11:26:47 intra241 kernel: pid 12129 (sort), uid 0, was killed: out of swap space Apr 4 11:26:47 intra241 kernel: pid 12166 (sort), uid 0, was killed: out of swap space Apr 4 11:26:47 intra241 kernel: pid 12194 (sort), uid 0, was killed: out of swap space Apr 4 11:26:47 intra241 kernel: pid 12213 (sort), uid 0, was killed: out of swap space Apr 4 11:26:48 intra241 kernel: pid 12250 (sort), uid 0, was killed: out of swap space Apr 4 11:26:48 intra241 kernel: pid 12250 (sort), uid 0, was killed: out of swap space Apr 4 11:26:48 intra241 kernel: pid 12278 (sort), uid 0, was killed: out of swap space Apr 4 11:26:48 intra241 kernel: pid 12297 (sort), uid 0, was killed: out of swap space Apr 4 11:26:48 intra241 kernel: pid 12334 (sort), uid 0, was killed: out of swap space Apr 4 11:26:49 intra241 kernel: pid 10948 (python2.2), uid 91, was killed: out of swap space Apr 4 11:26:49 intra241 kernel: pid 12363 (sort), uid 0, was killed: out of swap space Apr 4 11:26:49 intra241 kernel: pid 12381 (sort), uid 0, was killed: out of swap space Apr 4 11:26:49 intra241 kernel: pid 12418 (sort), uid 0, was killed: out of swap space Apr 4 11:26:49 intra241 kernel: pid 12446 (sort), uid 0, was killed: out of swap space Apr 4 11:26:50 intra241 kernel: pid 12465 (sort), uid 0, was killed: out of swap space Apr 4 11:26:50 intra241 kernel: pid 12502 (sort), uid 0, was killed: out of swap space Apr 4 11:26:50 intra241 kernel: pid 521 (python2.2), uid 91, was killed: out of swap space Apr 4 11:26:51 intra241 kernel: swap_pager: out of swap space Apr 4 11:26:51 intra241 kernel: swap_pager_getswapspace: failed Apr 4 11:26:51 intra241 kernel: pid 12530 (sort), uid 0, was killed: out of swap space Apr 4 11:26:51 intra241 kernel: pid 12550 (sort), uid 0, was killed: out of swap space Apr 4 11:26:51 intra241 kernel: pid 12586 (sort), uid 0, was killed: out of swap space Apr 4 11:26:51 intra241 kernel: pid 12614 (sort), uid 0, was killed: out of swap space Apr 4 11:26:52 intra241 kernel: pid 12633 (sort), uid 0, was killed: out of swap space Apr 4 11:26:52 intra241 kernel: pid 12633 (sort), uid 0, was killed: out of swap space Apr 4 11:26:52 intra241 kernel: pid 2341 (sort), uid 0, was killed: out of swap space Apr 4 11:26:53 intra241 kernel: swap_pager: out of swap space Apr 4 11:26:53 intra241 kernel: swap_pager_getswapspace: failed Apr 4 11:26:54 intra241 kernel: pid 12700 (sort), uid 0, was killed: out of swap space Apr 4 11:26:54 intra241 kernel: pid 12670 (sort), uid 0, was killed: out of swap space Apr 4 11:26:54 intra241 kernel: pid 12719 (sort), uid 0, was killed: out of swap space Apr 4 11:26:54 intra241 kernel: pid 12756 (sort), uid 0, was killed: out of swap space Apr 4 11:26:55 intra241 kernel: pid 12784 (sort), uid 0, was killed: out of swap space Apr 4 11:26:55 intra241 kernel: pid 12803 (sort), uid 0, was killed: out of swap space Apr 4 11:26:55 intra241 kernel: pid 12840 (sort), uid 0, was killed: out of swap space Apr 4 11:26:55 intra241 kernel: pid 12868 (sort), uid 0, was killed: out of swap space Apr 4 11:26:56 intra241 kernel: pid 12887 (sort), uid 0, was killed: out of swap space Apr 4 11:26:56 intra241 kernel: pid 12924 (sort), uid 0, was killed: out of swap space Apr 4 11:26:56 intra241 kernel: pid 12952 (sort), uid 0, was killed: out of swap space Apr 4 11:26:56 intra241 kernel: pid 12971 (sort), uid 0, was killed: out of swap space Apr 4 11:26:56 intra241 kernel: pid 13008 (sort), uid 0, was killed: out of swap space Apr 4 11:26:57 intra241 kernel: pid 13036 (sort), uid 0, was
Re: OOOPS - portupgrade/Swapfile/???
On Fri, 4 Apr 2003 11:56:37 +0200, CARTER Anthony wrote Watching with swapinfo, my 500Mb (256 Mb Ram) swapfile just fills up...on stopping portupgrade, swap file is emptied... I have exactly the same thing, just my machine can cope with it a bit better as I have 512M physical and 1gig swap. It's currently running a portupgrade -rai and doing all the recent gnome commits. The first 6 or 7 upgrades of installed ports went without a hitch but since then at the points where it says Building and Registering installation for I get this: OK? [yes] --- Build of x11/gnomesession started at: Fri, 04 Apr 2003 11:04:52 +0100 --- Building '/usr/ports/x11/gnomesession' make: Max recursion level (500) exceeded.: Resource temporarily unavailable and the physical ram in use just goes up and up and up until it runs out and then the swap space does the same. After a few minutes (luckily before it runs out) it stops. All the ram is free'd and the portupgrade carries on. During this time looking at a top it appears it's due to around ten sort processes doing something or other at the time. This looks more like a portupgrade issue rather than a -CURRENT issue however. Matt. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: OOOPS - portupgrade/Swapfile/???
Did portupgrade get updated then? I am not using gnome... The only thing I can think of is that an update has created a loop within itself, thereby launching subsequent sorts...I get 10 or so sorts, about 20-30 make's, kill them they come back... Anthony On Friday 04 April 2003 12:09, Matt wrote: On Fri, 4 Apr 2003 11:56:37 +0200, CARTER Anthony wrote Watching with swapinfo, my 500Mb (256 Mb Ram) swapfile just fills up...on stopping portupgrade, swap file is emptied... I have exactly the same thing, just my machine can cope with it a bit better as I have 512M physical and 1gig swap. It's currently running a portupgrade -rai and doing all the recent gnome commits. The first 6 or 7 upgrades of installed ports went without a hitch but since then at the points where it says Building and Registering installation for I get this: OK? [yes] --- Build of x11/gnomesession started at: Fri, 04 Apr 2003 11:04:52 +0100 --- Building '/usr/ports/x11/gnomesession' make: Max recursion level (500) exceeded.: Resource temporarily unavailable and the physical ram in use just goes up and up and up until it runs out and then the swap space does the same. After a few minutes (luckily before it runs out) it stops. All the ram is free'd and the portupgrade carries on. During this time looking at a top it appears it's due to around ten sort processes doing something or other at the time. This looks more like a portupgrade issue rather than a -CURRENT issue however. Matt. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: OOOPS - portupgrade/Swapfile/???
On Fri, 4 Apr 2003 12:25:33 +0200, CARTER Anthony wrote Did portupgrade get updated then? I am not using gnome... The only thing I can think of is that an update has created a loop within itself, thereby launching subsequent sorts...I get 10 or so sorts, about 20-30 make's, kill them they come back... Anthony I guess this could be related to the problem Kris Kennaway just reported on ports@ regarding Index Build Failed. Matt. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: OOOPS - portupgrade/Swapfile/???
Can you let me know about this, or forward a copy of the post, or even tell me what you mean by ports@...Is this another mailing list? Thanks, Anthony On Friday 04 April 2003 12:35, Matt wrote: On Fri, 4 Apr 2003 12:25:33 +0200, CARTER Anthony wrote Did portupgrade get updated then? I am not using gnome... The only thing I can think of is that an update has created a loop within itself, thereby launching subsequent sorts...I get 10 or so sorts, about 20-30 make's, kill them they come back... Anthony I guess this could be related to the problem Kris Kennaway just reported on ports@ regarding Index Build Failed. Matt. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: OOOPS - portupgrade/Swapfile/???
On Fri, 4 Apr 2003 13:21:25 +0200, CARTER Anthony wrote Can you let me know about this, or forward a copy of the post, or even tell me what you mean by ports@...Is this another mailing list? Thanks, Anthony Sorry. I always assume people are on the same lists as me :) http://docs.freebsd.org/cgi/getmsg.cgi?fetch=605942+0+current/freebsd-ports and http://docs.freebsd.org/cgi/getmsg.cgi?fetch=620081+0+current/freebsd-ports is what I'm referring to. A circular dependancy in the ports tree. Which would explain the looping during package tool use. Matt. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: OOOPS - portupgrade/Swapfile/???
I can get it to do it with portupgrade -r Mesa...so we can limit it to Mesa and/or one of its dependencies...NO? I don't use gnome, i use KDE. Maybe a library? Anthony P.S. Matt, can you post this to port@ (put me in CC for replies) as I don't want to cross-post. Thanks On Friday 04 April 2003 13:24, Matt wrote: On Fri, 4 Apr 2003 13:21:25 +0200, CARTER Anthony wrote Can you let me know about this, or forward a copy of the post, or even tell me what you mean by ports@...Is this another mailing list? Thanks, Anthony Sorry. I always assume people are on the same lists as me :) http://docs.freebsd.org/cgi/getmsg.cgi?fetch=605942+0+current/freebsd-ports and http://docs.freebsd.org/cgi/getmsg.cgi?fetch=620081+0+current/freebsd-ports is what I'm referring to. A circular dependancy in the ports tree. Which would explain the looping during package tool use. Matt. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: OOOPS - portupgrade/Swapfile/???
CARTER Anthony wrote: I can get it to do it with portupgrade -r Mesa...so we can limit it to Mesa and/or one of its dependencies...NO? This bit me this morning, too. I believe Xft is where the circle happens, at least thats what i had to neuter to get other stuff building. -Wade ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: OOOPS - portupgrade/Swapfile/???
How do you prevent a particular package from updating when doing a large portupgrade, or did you just do one at a time? Anthony On Friday 04 April 2003 13:57, Wade Majors wrote: CARTER Anthony wrote: I can get it to do it with portupgrade -r Mesa...so we can limit it to Mesa and/or one of its dependencies...NO? This bit me this morning, too. I believe Xft is where the circle happens, at least thats what i had to neuter to get other stuff building. -Wade ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: OOOPS - portupgrade/Swapfile/???
On Friday 04 April 2003 13:57, Wade Majors wrote: This bit me this morning, too. I believe Xft is where the circle happens, at least thats what i had to neuter to get other stuff building. It seems you are right: Xft depends on XFree86-4-fontEncodings XFree86-4-fontEncodings depends on XFree86-4-clients XFree86-4-clients depends on Xft :/ -Wade -- Bradley T. Hughes - bhughes at trolltech.com Trolltech AS - Waldemar Thranes gt. 98 N-0175 Oslo, Norway ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: OOOPS - portupgrade/Swapfile/???
On Friday 04 April 2003 14:03, Bradley T Hughes wrote: On Friday 04 April 2003 13:57, Wade Majors wrote: This bit me this morning, too. I believe Xft is where the circle happens, at least thats what i had to neuter to get other stuff building. It seems you are right: Xft depends on XFree86-4-fontEncodings Xft also depends on XFree86-4-fontScalable and XFree86-4-fontScalable depends on XFree86-4-clients... XFree86-4-fontEncodings depends on XFree86-4-clients XFree86-4-clients depends on Xft :/ -- Bradley T. Hughes - bhughes at trolltech.com Trolltech AS - Waldemar Thranes gt. 98 N-0175 Oslo, Norway ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: OOOPS - portupgrade/Swapfile/???
Regarding this issue it has been tracked to the Xft port and noted on the freebsd-ports mailing list. So I guess it'll be fixed shortly. http://docs.freebsd.org/cgi/getmsg.cgi?fetch=629561+0+current/freebsd-ports I would suggest any further conversation regarding it be done on that list as it's a bit off topic for this list. Regards, Matt. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: MPSAFE fxp m_pkthdr not valid
Nate Lawson wrote:
I have gotten fxp running with MPSAFE and did a large scp transfer. It
ran for a few minutes and then paniced. It was trap 12 (page fault) at
address 0x24. Here is where it crashed:
fxp_start+0xcc
0xc0194a4c is in fxp_start (../../../dev/fxp/if_fxp.c:1263).
1258 * been computed and stored in the checksum field
1259 * in the TCP header. The stack should have
1260 * already done this for us.
1261 */
1262
1263if (mb_head-m_pkthdr.csum_flags) {
1264if (mb_head-m_pkthdr.csum_flags CSUM_DELAY_DATA) {
1265txp-tx_cb-ipcb_ip_activation_high =
1266 FXP_IPCB_HARDWAREPARSING_ENABLE;
1267txp-tx_cb-ipcb_ip_schedule =
The deref of mb_head-m_pkthdr is invalid. Note that my fxp_intr function
acquires the fxp lock right away so this shouldn't be a race in fxp.
Since fxp_start() will usually be called by ether_output(), I don't see
how acquiring the lock in fxp_intr() can protect you from such a race.
You need to acquire the lock in fxp_start() before touching the
interface queue, otherwise it may be preempted by an interrupt and this
will lead to a race if fxp_intr() ends up calling fxp_start(). It really
looks like that's what happened.
Cheers,
Maxime
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
(no subject)
-- --- Otto Kucera A-1020 Wien Engerthstrasse 137/6/7 Tel: +43 699 1 942 30 91 [neue Nummer!] Email: [EMAIL PROTECTED] Icq: 65351173 --- And root said rm -rf / ..and there was nothing Your mailserver MUST resolve properly (Fully Qualified Domain Name) or the mail will not go through! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Giant required by uma (was Re: mbuf LOR)
Nate Lawson writes:
You're right about where the problem is (top of stack trace and listing
below). However, your patch causes an immediate panic on boot due to a
NULL deref. I don't think you want it to always return NULL if called
with M_NOWAIT set. :) Other ideas?
I suppose the only alternative is to do it right and remove Giant
from the uma zone alloc code.
From looking at the code for a little while this morning, it looks
like there are 3 allocators that could be called at this point in the
code:
1) page_alloc():
Calls kmem_malloc(). Should be MPSAFE on NOWAIT allocations. Needs
Giant on WAITOK allocations.
2) obj_alloc():
Calls vm_page_alloc() -- that's MPSAFE.
Calls pmap_qenter() -- I've got no freaking clue if that's MPSAFE on
all platforms. I think it is, since kmem_malloc is MPSAFE it
calls pmap_enter(), but I'm not sure.
uma_small_alloc():
i386 - no uma_small_alloc, no problem
alpha - uma_small_alloc is SMP safe
ia64 - uma_small_alloc should be SMP safe, as it seems to be
doing just the moral equivalent of PHYS_TO_K0SEG() to map the memory
into the kernel.
sparc64: I have no idea..
Drew
slab_zalloc + 0xdf
uma_zone_slab + 0xd8
uma_zalloc_bucket + 0x15d
uma_zalloc_arg + 0x307
malloc
...
m_getcl
(gdb) l *slab_zalloc+0xdf
0xc02f646f is in slab_zalloc (../../../vm/uma_core.c:707).
702 else
703 wait = ~M_ZERO;
704
705 if (booted || (zone-uz_flags UMA_ZFLAG_PRIVALLOC)) {
706 mtx_lock(Giant);
707 mem = zone-uz_allocf(zone,
708 zone-uz_ppera * UMA_SLAB_SIZE, flags, wait);
709 mtx_unlock(Giant);
710 if (mem == NULL) {
711 ZONE_LOCK(zone);
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: MPSAFE fxp m_pkthdr not valid
Nate Lawson writes: I have gotten fxp running with MPSAFE and did a large scp transfer. It ran for a few minutes and then paniced. It was trap 12 (page fault) at address 0x24. Here is where it crashed: .. The deref of mb_head-m_pkthdr is invalid. Note that my fxp_intr function acquires the fxp lock right away so this shouldn't be a race in fxp. Where else is the lock acquired? It would be easier to help if we could see a diff.. Drew ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
So then, is fxp working OK again?
Having had the same experiences as others described here recently with the fxp stuff, I'm just wondering if it's safe now to cvsup and try it again. I only have one machine here and if my net interface fails, I'm totally screwed. :-) -- Conrad Sabatier [EMAIL PROTECTED] - In Unix veritas ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: So then, is fxp working OK again?
Conrad Sabatier wrote: Having had the same experiences as others described here recently with the fxp stuff, I'm just wondering if it's safe now to cvsup and try it again. I only have one machine here and if my net interface fails, I'm totally screwed. :-) You can still boot your old kernel from the loader prompt, if such a thing happens. But everything appears normal to me so far. -Wade ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: So then, is fxp working OK again?
On 04-Apr-2003 Wade Majors wrote: Conrad Sabatier wrote: Having had the same experiences as others described here recently with the fxp stuff, I'm just wondering if it's safe now to cvsup and try it again. I only have one machine here and if my net interface fails, I'm totally screwed. :-) You can still boot your old kernel from the loader prompt, if such a thing happens. But everything appears normal to me so far. Yes, except I ran into some problems this last time where, after successfully booting the new kernel in single-user mode, installing world, running mergemaster, rebooting and finding the new kernel didn't work, I couldn't get the old kernel to work, either. :-( Apparently, something had changed just enough somewhere to make the old kernel go kerplooey, too. -- Conrad Sabatier [EMAIL PROTECTED] - In Unix veritas ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: So then, is fxp working OK again?
Conrad Sabatier wrote: Having had the same experiences as others described here recently with the fxp stuff, I'm just wondering if it's safe now to cvsup and try it again. I only have one machine here and if my net interface fails, I'm totally screwed. :-) It should. If it doesn't, I'm interested in knowing it. :-) Cheers, Maxime ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Konsole crash with libthr
It seems Konsole didn't like libthr a bit. And, now that I think about it, neither did licq, though I didn't notice it at the time I was closing the KDE Crash Handler windows. The trace I'm posting below is typical. I had some 20 windows with the same thing, and the error occured at startup. I have two main konsole windows, each with dozens of individual konsole tabs. One of the main windows did not come up at all, and the other one had just a few tabs. So it seems the error only shows up during it's startup, but it does not always happen. On a tentative guess, it might happen because it takes a LONG time for the start up to complete, so some timeout might not be reacting well to be expired (well, the fact that the error is related to wait4 contributed to that hypothesis). 0x29068b53 in wait4 () from /usr/lib/libc.so.5 #0 0x29068b53 in wait4 () from /usr/lib/libc.so.5 #1 0x2905a015 in waitpid () from /usr/lib/libc.so.5 #2 0x290155f5 in _waitpid (wpid=7, status=0x7, options=7) at /usr/src/lib/libthr/thread/thr_syscalls.c:386 #3 0x286d79aa in KCrash::defaultCrashHandler(int) (sig=6) at kcrash.cpp:235 #4 signal handler called #5 0x29068833 in kill () from /usr/lib/libc.so.5 #6 0x2936b4f7 in TEPty::makePty(bool) () from /usr/local/lib/konsole.so #7 0x2936b58a in TEPty::startPgm(char const*, QValueListQCString, char const*) () from /usr/local/lib/konsole.so #8 0x2936bdaa in TEPty::commSetupDoneC() () from /usr/local/lib/konsole.so #9 0x286811b9 in KProcess::start(KProcess::RunMode, KProcess::Communication) ( this=0x81b6c00, runmode=7, comm=NoCommunication) at kprocess.cpp:320 #10 0x2936add6 in TEPty::run(char const*, QStrList, char const*, bool, char const*, char const*) () from /usr/local/lib/konsole.so #11 0x2938f389 in TESession::run() () from /usr/local/lib/konsole.so #12 0x293911d9 in TESession::qt_invoke(int, QUObject*) () from /usr/local/lib/konsole.so #13 0x28a25358 in QObject::activate_signal(QConnectionList*, QUObject*) () from /usr/X11R6/lib/libqt-mt.so.3 #14 0x28cf228d in QSignal::signal(QVariant const) () from /usr/X11R6/lib/libqt-mt.so.3 #15 0x28a3ec38 in QSignal::activate() () from /usr/X11R6/lib/libqt-mt.so.3 #16 0x28a459f3 in QSingleShotTimer::event(QEvent*) () from /usr/X11R6/lib/libqt-mt.so.3 #17 0x289c85e5 in QApplication::internalNotify(QObject*, QEvent*) () from /usr/X11R6/lib/libqt-mt.so.3 #18 0x289c83ab in QApplication::notify(QObject*, QEvent*) () from /usr/X11R6/lib/libqt-mt.so.3 #19 0x2864c1a9 in KApplication::notify(QObject*, QEvent*) (this=0x7, receiver=0x825a000, event=0xbfbff2a0) at kapplication.cpp:453 #20 0x289a48a7 in QEventLoop::activateTimers() () from /usr/X11R6/lib/libqt-mt.so.3 #21 0x28983ba1 in QEventLoop::processEvents(unsigned) () from /usr/X11R6/lib/libqt-mt.so.3 #22 0x289dc000 in QEventLoop::enterLoop() () from /usr/X11R6/lib/libqt-mt.so.3 #23 0x289dbf38 in QEventLoop::exec() () from /usr/X11R6/lib/libqt-mt.so.3 #24 0x289c8771 in QApplication::exec() () from /usr/X11R6/lib/libqt-mt.so.3 #25 0x2937057d in main () from /usr/local/lib/konsole.so #26 0x0804cb1f in launch (argc=3, _name=0x805ba84 konsole, args=0x805bacd , cwd=0x0, envc=0, envs=0x805bad1 , reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x7 Error reading address 0x7: Bad address) at kinit.cpp:547 #27 0x0804d906 in handle_launcher_request (sock=7) at kinit.cpp:1021 #28 0x0804de57 in handle_requests (waitForPid=0) at kinit.cpp:1189 #29 0x0804ef53 in main (argc=3, argv=0xbfbffc78, envp=0x7) at kinit.cpp:1540 #30 0x0804b115 in _start () -- Daniel C. Sobral (8-DCS) Gerencia de Operacoes Divisao de Comunicacao de Dados Coordenacao de Seguranca TCO Fones: 55-61-313-7654/Cel: 55-61-9618-0904 E-mail: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Outros: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Youth is when you blame all your troubles on your parents; maturity is when you learn that everything is the fault of the younger generation. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
panic: lockmgr: locking against myself
As always, whenever I crash before background fsck is finished...
[EMAIL PROTECTED]:/opt/home/dcs$ gdb -k /usr/obj/usr/src/sys/DCS/kernel.debug
/var/crash/vmcore.8
GNU gdb 5.2.1 (FreeBSD)
Copyright 2002 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-undermydesk-freebsd...
panic: lockmgr: locking against myself
panic messages:
---
panic: lockmgr: locking against myself
syncing disks, buffers remaining... 882 882 880 880 880 880 880 880 880
880 880 822 823 822 822 822 822 822 unknown: device timeout
unknown: DMA timeout
824 822 827 822 822 822 822 822 822 822 822 822 822 822 822 822 822 822
822 822 822 822 822
giving up on 710 buffers
Uptime: 4m41s
Dumping 255 MB
ata0: resetting devices ..
done
16 32 48 64 80 96 112 128 144 160 176 192 208 224 240
---
Reading symbols from /boot/kernel/snd_cmi.ko...done.
Loaded symbols for /boot/kernel/snd_cmi.ko
Reading symbols from /boot/kernel/snd_pcm.ko...done.
Loaded symbols for /boot/kernel/snd_pcm.ko
Reading symbols from
/usr/obj/usr/src/sys/DCS/modules/usr/src/sys/modules/acpi/acpi.ko.debug...done.
Loaded symbols for
/usr/obj/usr/src/sys/DCS/modules/usr/src/sys/modules/acpi/acpi.ko.debug
Reading symbols from /boot/kernel/green_saver.ko...done.
Loaded symbols for /boot/kernel/green_saver.ko
Reading symbols from
/usr/obj/usr/src/sys/DCS/modules/usr/src/sys/modules/linux/linux.ko.debug...done.
Loaded symbols for
/usr/obj/usr/src/sys/DCS/modules/usr/src/sys/modules/linux/linux.ko.debug
#0 doadump () at /usr/src/sys/kern/kern_shutdown.c:239
239 dumping++;
(kgdb) bt full
#0 doadump () at /usr/src/sys/kern/kern_shutdown.c:239
No locals.
#1 0xc01ec443 in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:371
No locals.
#2 0xc01ec743 in panic () at /usr/src/sys/kern/kern_shutdown.c:542
td = (struct thread *) 0xc29fc980
bootopt = 256
newpanic = 1
buf = lockmgr: locking against myself, '\0' repeats 224 times
#3 0xc01d0c22 in lockmgr (lkp=0xc77cf97c, flags=34144290,
interlkp=0x220, td=0xc29fc980)
at /usr/src/sys/kern/kern_lock.c:447
error = 0
thr = (struct thread *) 0xc29fc980
extflags = 33554464
lockflags = 34144290
#4 0xc0245f10 in BUF_TIMELOCK (bp=0xc77cf97c, locktype=34144290,
interlock=0x0, wmesg=0x0, catch=0, timo=0)
at buf.h:319
ret = 0
#5 0xc0241528 in flushbuflist (blist=0xc77cf8b0, flags=4,
vp=0xc2ef86d8, slpflag=0, slptimeo=0, errorp=0x0)
at /usr/src/sys/kern/vfs_subr.c:1226
bp = (struct buf *) 0xc77cf97c
nbp = (struct buf *) 0x2090022
found = 1
error = 0
#6 0xc02411d9 in vinvalbuf (vp=0xc2ef86d8, flags=4, cred=0x0, td=0x0,
slpflag=0, slptimeo=0)
at /usr/src/sys/kern/vfs_subr.c:1140
blist = (struct buf *) 0x0
error = 0
object = (struct vm_object *) 0xc038d420
#7 0xc027ef0a in ffs_truncate (vp=0xc2ef86d8, length=0, flags=2048,
cred=0x0, td=0xc29fc980)
at /usr/src/sys/ufs/ffs/ffs_inode.c:273
ovp = (struct vnode *) 0xc2ef86d8
oip = (struct inode *) 0xc2506510
bn = -4595188392983498048
lbn = -4595796903951530429
---Type return to continue, or q return to quit---
lastblock = -3284296585705422848
lastiblock = {7825250020, 4294852608, 4294983680}
indir_lbn = {-3284295173694292736, 0, -3976995127051695744}
oldblks = {-4422543730025529563, -4597468310878027639,
-4603193868120500600, 7560230888,
1545117794085, -407461993958781, 3530282736,
-4603163193464072504, 3265263592, 591635055342,
24892416000, 1425736, 1427344, 3262735212, -941709473941328}
newblks = {-4595796560354146749, -4595830507774119232,
-4595689636071734605, -4602925638822930956,
-3284296118623889348, -4595830507775840915, -4597472472701337599,
-4422543733250063938,
-3284296015545203986, -4597468307654643792, 16109450424,
-3284295792166188672, -4597468310878027194,
-4597197328506420774, -4595797247547378808}
count = -3284296431086600192
blocksreleased = 0
datablocks = 96
fs = (struct fs *) 0xc279d000
bp = (struct buf *) 0xc0210643
needextclean = 0
softdepslowdown = 0
extblocks = 0
offset = -1024489768
size = 0
level = 0
nblocks = -764684924
i = -1024489768
error = 0
allerror = 0
osize = 3224950592
#8 0xc02825c0 in ffs_snapshot (mp=0xc25ecc00, snapfile=---Can't read
userspace from dump, or kernel process---
) at /usr/src/sys/ufs/ffs/ffs_snapshot.c:654
numblks = 262138
blkno = -4595798621938448829
blkp = (ufs2_daddr_t *) 0xc0387108
snapblklist = (ufs2_daddr_t *) 0xc03862a8
error = 5
Re: mbuf LOR
Nate Lawson writes:
You're right about where the problem is (top of stack trace and listing
below). However, your patch causes an immediate panic on boot due to a
NULL deref. I don't think you want it to always return NULL if called
with M_NOWAIT set. :) Other ideas?
The following patch boots passed the basic 'make -j16 buildworld'
test on x86 SMP. As I outlined before, I'm not certain if it is safe
on all platforms.
I'm really eager to see your fxp locking diffs. Even if you're not
comfortable sharing them with the world yet, I'd be interested in
helping out on this.
Drew
Index: vm/uma_core.c
===
RCS file: /home/ncvs/src/sys/vm/uma_core.c,v
retrieving revision 1.51
diff -u -r1.51 uma_core.c
--- vm/uma_core.c 26 Mar 2003 18:44:53 - 1.51
+++ vm/uma_core.c 4 Apr 2003 15:11:34 -
@@ -703,10 +703,15 @@
wait = ~M_ZERO;
if (booted || (zone-uz_flags UMA_ZFLAG_PRIVALLOC)) {
- mtx_lock(Giant);
- mem = zone-uz_allocf(zone,
- zone-uz_ppera * UMA_SLAB_SIZE, flags, wait);
- mtx_unlock(Giant);
+ if ((wait M_NOWAIT) == 0) {
+ mtx_lock(Giant);
+ mem = zone-uz_allocf(zone,
+ zone-uz_ppera * UMA_SLAB_SIZE, flags, wait);
+ mtx_unlock(Giant);
+ } else {
+ mem = zone-uz_allocf(zone,
+ zone-uz_ppera * UMA_SLAB_SIZE, flags, wait);
+ }
if (mem == NULL) {
ZONE_LOCK(zone);
return (NULL);
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: So then, is fxp working OK again?
Conrad Sabatier wrote: Having had the same experiences as others described here recently with the fxp stuff, I'm just wondering if it's safe now to cvsup and try it again. I only have one machine here and if my net interface fails, I'm totally screwed. :-) reinstallkernel and boot-conf kernel.old are your friends. :-) -- Daniel C. Sobral (8-DCS) Gerencia de Operacoes Divisao de Comunicacao de Dados Coordenacao de Seguranca TCO Fones: 55-61-313-7654/Cel: 55-61-9618-0904 E-mail: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Outros: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Vote for ME -- I'm well-tapered, half-cocked, ill-conceived and TAX-DEFERRED! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
CPUTYPE?
I need to buildworld (current) and ports to run on both p3 and athlon-mp. What's a good value for CPUTYPE, or should I just leave it out? Thanks. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
midi problem, an isa device on a pci card
Hello,
I've been fiddling with pci drivers in freebsd for a couple of
months and up to now everything has ok, I did a midi driver for es137x
which was relatively easy because the io was done on the pci bus. I
was very pleased that there were enough resources for a newbie like me
to dive into kernel hacking.
Now I want to do one for the cmi card, but it seems to offer
the midi device on the isa bus, as does a bunch of cards. I'm sure
they did this to confuse me.
Linux seems to be happy just inb,outb in their pci driver,
which seems uncool to me. Also since I can program the mpu to appear
to different locations I think the ISA bus driver can help determine
the best one to use...
Theory of Reality (mostly hand waving, as I've done no code yet)
Drivers:
cmi(pci), my pci sound, it's on board btw.
mpushim(isa), the mpu401 from the tree but hacked to receive
from the pci soundcard driver
How I think should work:
probe cmi,
attach cmi,
do {
enable mpu401 at port region,
probe attach mpushim
while ( ! mpushim attached )
done
Big question mark:
How do I create isa devices from a pci device. Do I search up the
soundcard tree for the pci bus then search down for the isa bus, then
create_child(...mpushim)?
How do I tell the shim before the probe/attach what io region to look
at, do I fiddle with ivars (or some internal structure), do I mess with hints
via kenv(9) [Is there a kenv(9)? ]
I think that these questions equally apply to joysticks.
Thanks,
--Mat
--
Brain: Are you pondering what I'm pondering?
Pinky: I think so, Brain, but if the plural of mouse is mice, wouldn't
the plural of spouse be spice?
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
imon on FreeBSD
I want to use imon inode monitor to watch file activity. Is it possible to do that with FreeBSD? And where can I get a update or a patch for the installation? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Fxp breakage (still)
Following sources still yield unresponsive fxp interface. The same behavious occurs on both of my test boxes (dell 4350 and home-grown athlon xp), each having identical Intel Pro 100+M nics with v4.1.0.9 intel PXE rom. # fgrep -h \*\ \$FreeBSD /usr/src/sys/dev/fxp/* * $FreeBSD: src/sys/dev/fxp/if_fxp.c,v 1.154 2003/04/03 20:39:43 mux Exp $ * $FreeBSD: src/sys/dev/fxp/if_fxpreg.h,v 1.30 2003/04/03 18:39:48 mux Exp $ * $FreeBSD: src/sys/dev/fxp/if_fxpvar.h,v 1.24 2003/04/02 16:47:16 mux Exp $ * $FreeBSD: src/sys/dev/fxp/rcvbundl.h,v 1.1 2001/10/25 05:23:31 jlemon Exp $ Reverting back to kernel sources from 11 April yield functional interface. Robin P. Blanchard Systems Integration Specialist Georgia Center for Continuing Education fon: 706.542.2404 | fax: 706.542.6546 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Anyone had hangs with Radeon, XF86 4.3.0, and DRI on logout?
As the subject says, I'm wondering if anyone out there has experienced hangs on logging out from xdm (or perhaps switching VTs) with Radeon or matrox (perhaps r128, too) cards using the updated DRM in -current and XFree86 4.3.0. If so, I may have a fix, but I'm wondering if this affects FreeBSD. -- Eric Anholt[EMAIL PROTECTED] http://people.freebsd.org/~anholt/ [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Anyone had hangs with Radeon, XF86 4.3.0, and DRI on logout?
Eric Anholt wrote: As the subject says, I'm wondering if anyone out there has experienced hangs on logging out from xdm (or perhaps switching VTs) with Radeon or matrox (perhaps r128, too) cards using the updated DRM in -current and XFree86 4.3.0. If so, I may have a fix, but I'm wondering if this affects FreeBSD. Yes, I had them from 5.0 onwards until -p7. Not only with radeon but also (although not so often) with mga. They don't seem to happen anymore with the Matrox card in -p7 but I can't right now check if it's still problematic with a Radeon (I have swapped cards in hope to workaround that problem.) But since I also had problems with the mga before -p7 and they don't seem to exist anymore now perhaps the problem has gone away? (The problem manifested itself in the X server taking 100% cpu in kernel mode, and trying to kill it, or trying to reboot made the machine freeze solid. It only happened when the X session was terminated / X server was restarted, and occasionally in some xscreensaver hacks, after a while, although I couldn't ascertain this because I usually am not there when xscreensaver is running... ;) --mkb ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: So then, is fxp working OK again?
On 04-Apr-2003 Maxime Henrion wrote: Conrad Sabatier wrote: Having had the same experiences as others described here recently with the fxp stuff, I'm just wondering if it's safe now to cvsup and try it again. I only have one machine here and if my net interface fails, I'm totally screwed. :-) It should. If it doesn't, I'm interested in knowing it. :-) Cheers, Maxime groan Still no go. I'm still getting a panic in bus_dmamem_alloc(). Here's the info I copied down by hand: Fatal trap 12: page fault while in kernel mode fault virtual address = 0x24 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0301639 stack pointer = 0x10:0xc053bd34 frame pointer = 0x10: 0xc053bd48 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 = 0() kernel: type 12 trap, code = 0 Stopped at bus_dmamen_alloc+0x9 movl 0x24(%edx),%eax dbtrace bus_dmamem_alloc(0, c04a8aa0, 1, c04a965c, ) at bus_dmamen_alloc+0x9 acpi_alloc_wakeup_handler(0, 532000, 532020, 532000, 0) at acpi_alloc_wakeup_handler+0xa9 mi_startup() at mi_startup+0x99 begin() at begin+0x2c db Incidentally, I've been getting acpi initialization failures in the last umpteen kernels I've been through, but without panicing the machine. -- Conrad Sabatier [EMAIL PROTECTED] - In Unix veritas ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Anyone had hangs with Radeon, XF86 4.3.0, and DRI on logout?
On Fri, Apr 04, 2003 at 01:30:39PM -0800, Eric Anholt wrote: As the subject says, I'm wondering if anyone out there has experienced hangs on logging out from xdm (or perhaps switching VTs) with Radeon or matrox (perhaps r128, too) cards using the updated DRM in -current and XFree86 4.3.0. If so, I may have a fix, but I'm wondering if this affects FreeBSD. What is the date of the updated DRM you are concerned with? I have a radeon 7500 M7 in my laptop with XFree86 4.3.0 and a kernel from yesterday's sources. I haven't noticed any problems with switch to VTs except for a few second delay in updating X when I switch back. I'm attributing the delay to a ULE quirk. -- Steve ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Inaccessible ad devices
Hello I have 4 IDE disks that I'm going to use for a small RAID. During my testing with the ata(4) software RAID I had created a RAID0 on two of the disks. I then deleted it and tried to create a new array (different interleave) but I had forgotten to unmounted the filesystem on the RAID I just deleted and I got a kernel panic - at least i think that was the sequence of events. The problem is that the RAID configuration was apparently left in a somewhat undefined state so now there is neither a configured RAID (no ar device) or any normal ad devices for the two disks. When I got the panic I was running a older 4.7-RC but I now run -CURRENT from today on it (dual boot). I have the same problem with the missing disks under 4.7-RC and 4.8-RELEASE. I can still create a new RAID on the two remaining disk. Since updating the -CURRENT today I get a panic when creating the array (on ad8 and ad10) but after reboot the array is configured and works. I'm currently trying to create a proper crash dump for this but i'm rather sure this is unreleated to the missing disks. More information (the missing disks are ad4 and and6) : # uname -a FreeBSD ford.nitro.dk 5.0-CURRENT FreeBSD 5.0-CURRENT #1: Fri Apr 4 16:57:56 CEST 2003 [EMAIL PROTECTED]:/usr/obj/data/FreeBSD/CURRENT/sys/GENERIC i386 Part of dmesg (full boot -v at http://simon.nitro.dk/temp/ataraid/dmesg.boot-verbose) : atapci0: VIA 82C686A UDMA66 controller port 0xffa0-0xffaf at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 [CUT] atapci1: Promise PDC20268 UDMA100 controller port 0xcc00-0xcc0f,0xd000-0xd003,0xd400-0xd407,0xd800-0xd803,0xdc00-0xdc07 mem 0xefffc000-0xefff irq 11 at device 13.0 on pci0 ata2: at 0xdc00 on atapci1 ata3: at 0xd400 on atapci1 atapci2: Promise PDC20268 UDMA100 controller port 0xac00-0xac0f,0xb000-0xb003,0xb400-0xb407,0xb800-0xb803,0xbc00-0xbc07 mem 0xefff8000-0xefffbfff irq 12 at device 14.0 on pci0 ata4: at 0xbc00 on atapci2 ata5: at 0xb400 on atapci2 [CUT] ad0: 29314MB IBM-DTLA-307030 [59560/16/63] at ata0-master UDMA66 ad8: 76319MB WDC WD800JB-00CRA1 [155061/16/63] at ata4-master UDMA100 ad10: 76319MB WDC WD800JB-00CRA1 [155061/16/63] at ata5-master UDMA100 Waiting 15 seconds for SCSI devices to settle (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. Opened disk ad4 - 16 Opened disk ad4 - 16 Opened disk ad6 - 16 Opened disk ad6 - 16 Mounting root from ufs:/dev/ad0s3a [CUT] # atacontrol list ATA channel 0: Master: ad0 IBM-DTLA-307030/TX4OA60A ATA/ATAPI rev 5 Slave: no device present ATA channel 1: Master: no device present Slave: no device present ATA channel 2: Master: ad4 WDC WD800JB-00CRA1/17.07W17 ATA/ATAPI rev 5 Slave: no device present ATA channel 3: Master: ad6 WDC WD800JB-00CRA1/17.07W17 ATA/ATAPI rev 5 Slave: no device present ATA channel 4: Master: ad8 WDC WD800JB-00CRA1/17.07W17 ATA/ATAPI rev 5 Slave: no device present ATA channel 5: Master: ad10 WDC WD800JB-00CRA1/17.07W17 ATA/ATAPI rev 5 Slave: no device present # atacontrol status 0 atacontrol: ioctl(ATARAIDSTATUS): Device not configured -- Simon L. Nielsen pgp0.pgp Description: PGP signature
Re: LOR on libthr exit (iirc)
On Fri, Apr 04, 2003 at 04:31:00PM -0600, Dan Nelson wrote: In the last episode (Apr 02), Jeff Roberson said: On Wed, 2 Apr 2003, Gordon Tetlow wrote: I think it was a libthr linked app after I killed it: Yeah, this is a problem with the thread single exit and suspend code. I haven't fixed it yet. Thanks for the report. I get the same LOR message on my machine, but it is always immediately followed by a panic. libthr also seems to only work with WITNESS. Without it the machine locks up hard (serial debugger doesn't even respond) when you start any libthr-linked app. Well, I'm running the SMP config which does have WITNESS in it. -gordon pgp0.pgp Description: PGP signature
kp_proc and kp_eproc
I have some software that compiled fine on FreeBSD-4 but is not compiling on FreeBSD-5. It is looking for kp_proc and kp_eproc. The error I get is: structure has no member named `kp_proc' structure has no member named `kp_eproc' Have those changed from FreeBSD-4? Thanks. -- Glenn Johnson USDA, ARS, SRRC Phone: (504) 286-4252 New Orleans, LA 70124 e-mail: [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kp_proc and kp_eproc
* De: Glenn Johnson [EMAIL PROTECTED] [ Data: 2003-04-04 ] [ Subjecte: kp_proc and kp_eproc ] I have some software that compiled fine on FreeBSD-4 but is not compiling on FreeBSD-5. It is looking for kp_proc and kp_eproc. The error I get is: structure has no member named `kp_proc' structure has no member named `kp_eproc' Have those changed from FreeBSD-4? Yes, kinfo_proc has changed. What do you need to access? I have found that just doing a set of macros helps a lot. -- juli mallett. email: [EMAIL PROTECTED]; aim: bsdflata; efnet: juli; ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kp_proc and kp_eproc
yes.. The entire process structure and it's surrounding enviroment has been through a blender. What do you wnat to do? On Fri, 4 Apr 2003, Glenn Johnson wrote: I have some software that compiled fine on FreeBSD-4 but is not compiling on FreeBSD-5. It is looking for kp_proc and kp_eproc. The error I get is: structure has no member named `kp_proc' structure has no member named `kp_eproc' Have those changed from FreeBSD-4? Thanks. -- Glenn Johnson USDA, ARS, SRRCPhone: (504) 286-4252 New Orleans, LA 70124 e-mail: [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: CPUTYPE?
On Fri, Apr 04, 2003 at 12:50:45PM -0500, Barney Wolff wrote: I need to buildworld (current) and ports to run on both p3 and athlon-mp. What's a good value for CPUTYPE, or should I just leave it out? i686 is the lowest common divisor of those two. Kris pgp0.pgp Description: PGP signature
Re: imon on FreeBSD
On Fri, Apr 04, 2003 at 11:52:15AM +0200, Stephan M?ck wrote: I want to use imon inode monitor to watch file activity. Is it possible to do that with FreeBSD? I don't see imon in the ports collection. However there are other tools like l0pht-watch and fam in ports (I don't know if fam uses kqueue on FreeBSD, so it may not operate efficiently). Kris pgp0.pgp Description: PGP signature
Re: kp_proc and kp_eproc
On Fri, Apr 04, 2003 at 03:54:05PM -0800, Julian Elischer wrote:
yes..
The entire process structure and it's surrounding enviroment has been
through a blender.
What do you wnat to do?
I would like to learn what I need to do to get the software to compile
on FreeBSD-5. I guess the question is, what information do I need to
provide? The software in question is OpenPBS (http://www.openpbs.org),
so it nothing proprietary. There were a whole bunch of dependency
problems that I worked through manually and finally got to the point
of the kp_proc failure. Here is a snippet of code that produces the
failure:
~~
static unsigned long cput_sum(pjob)
job *pjob;
{
static charid[] = cput_sum;
int i;
u_long cputime;
int nps = 0;
cputime = 0;
for (i=0; inproc; i++) {
struct kinfo_proc *pp = proc_tbl[i];
if (!injob(pjob, sess_tbl[i]))
continue;
nps++;
cputime += tvk(pp-kp_proc.p_rtime);
if (pp-kp_proc.p_ru == NULL) {
struct pstats ps;
DBPRT((%s: p_stats 0x%lx\n, id,
(u_long)pp-kp_proc.p_stats))
if (pp-kp_proc.p_stats == NULL)
continue;
if (kvm_read(kd, (u_long)pp-kp_proc.p_stats, ps,
sizeof(ps)) != sizeof(ps)) {
log_err(errno, id, kvm_read(pstats));
continue;
}
cputime += tv(ps.p_ru.ru_utime) +
tv(ps.p_ru.ru_stime) +
tv(ps.p_cru.ru_utime) +
tv(ps.p_cru.ru_stime);
}
else {
struct rusage ru;
DBPRT((%s: p_ru 0x%lx\n, id,
(u_long)pp-kp_proc.p_ru))
if (kvm_read(kd, (u_long)pp-kp_proc.p_ru, ru,
sizeof(ru)) != sizeof(ru)) {
log_err(errno, id, kvm_read(session));
continue;
}
cputime += tv(ru.ru_utime) + tv(ru.ru_stime);
}
DBPRT((%s: ses %d pid %d cputime %d\n, id,
sess_tbl[i], pp-kp_proc.p_pid, cputime))
}
if (nps == 0)
pjob-ji_flags |= MOM_NO_PROC;
return ((unsigned long)((double)cputime * cputfactor));
}
~~
On Fri, 4 Apr 2003, Glenn Johnson wrote:
I have some software that compiled fine on FreeBSD-4 but is not
compiling on FreeBSD-5. It is looking for kp_proc and kp_eproc.
The error I get is:
structure has no member named `kp_proc'
structure has no member named `kp_eproc'
Have those changed from FreeBSD-4?
Thanks.
--
Glenn Johnson
USDA, ARS, SRRC Phone: (504) 286-4252
New Orleans, LA 70124 e-mail: [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: imon on FreeBSD
Kris Kennaway wrote: On Fri, Apr 04, 2003 at 11:52:15AM +0200, Stephan M?ck wrote: I want to use imon inode monitor to watch file activity. Is it possible to do that with FreeBSD? I don't see imon in the ports collection. However there are other tools like l0pht-watch and fam in ports (I don't know if fam uses kqueue on FreeBSD, so it may not operate efficiently). The imon in question is a program that uses a device of the same name, which exists on SGI systems, and now Linux. The correct way to implement this functionality in FreeBSD is definitely kqueue, like Kris said. Actually /dev/imon is really inferior to kqueue in a lot of ways. -- Terry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kp_proc and kp_eproc
On Fri, 4 Apr 2003, Glenn Johnson wrote:
On Fri, Apr 04, 2003 at 03:54:05PM -0800, Julian Elischer wrote:
yes..
The entire process structure and it's surrounding enviroment has been
through a blender.
What do you wnat to do?
I would like to learn what I need to do to get the software to compile
on FreeBSD-5. I guess the question is, what information do I need to
provide? The software in question is OpenPBS (http://www.openpbs.org),
so it nothing proprietary. There were a whole bunch of dependency
problems that I worked through manually and finally got to the point
of the kp_proc failure. Here is a snippet of code that produces the
failure:
~~
you need to start from proc.h.
the proc structure has been exploded into 4 parts
but the kinfo_proc structure still exists. you may need to look at what
'ps' does to make sense of it..
some fields have become subfields and some may require following some
links.
static unsigned long cput_sum(pjob)
job *pjob;
{
static charid[] = cput_sum;
int i;
u_long cputime;
int nps = 0;
cputime = 0;
for (i=0; inproc; i++) {
struct kinfo_proc *pp = proc_tbl[i];
if (!injob(pjob, sess_tbl[i]))
continue;
nps++;
cputime += tvk(pp-kp_proc.p_rtime);
if (pp-kp_proc.p_ru == NULL) {
struct pstats ps;
DBPRT((%s: p_stats 0x%lx\n, id,
(u_long)pp-kp_proc.p_stats))
if (pp-kp_proc.p_stats == NULL)
continue;
if (kvm_read(kd, (u_long)pp-kp_proc.p_stats, ps,
sizeof(ps)) != sizeof(ps)) {
log_err(errno, id, kvm_read(pstats));
continue;
}
cputime += tv(ps.p_ru.ru_utime) +
tv(ps.p_ru.ru_stime) +
tv(ps.p_cru.ru_utime) +
tv(ps.p_cru.ru_stime);
}
else {
struct rusage ru;
DBPRT((%s: p_ru 0x%lx\n, id,
(u_long)pp-kp_proc.p_ru))
if (kvm_read(kd, (u_long)pp-kp_proc.p_ru, ru,
sizeof(ru)) != sizeof(ru)) {
log_err(errno, id, kvm_read(session));
continue;
}
cputime += tv(ru.ru_utime) + tv(ru.ru_stime);
}
DBPRT((%s: ses %d pid %d cputime %d\n, id,
sess_tbl[i], pp-kp_proc.p_pid, cputime))
}
if (nps == 0)
pjob-ji_flags |= MOM_NO_PROC;
return ((unsigned long)((double)cputime * cputfactor));
}
~~
On Fri, 4 Apr 2003, Glenn Johnson wrote:
I have some software that compiled fine on FreeBSD-4 but is not
compiling on FreeBSD-5. It is looking for kp_proc and kp_eproc.
The error I get is:
structure has no member named `kp_proc'
structure has no member named `kp_eproc'
Have those changed from FreeBSD-4?
Thanks.
--
Glenn Johnson
USDA, ARS, SRRCPhone: (504) 286-4252
New Orleans, LA 70124 e-mail: [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
HEADS UP: fxp breakage
Hi all, Robin P. Blanchard wrote: Following sources still yield unresponsive fxp interface. The same behavious occurs on both of my test boxes (dell 4350 and home-grown athlon xp), each having identical Intel Pro 100+M nics with v4.1.0.9 intel PXE rom. # fgrep -h \*\ \$FreeBSD /usr/src/sys/dev/fxp/* * $FreeBSD: src/sys/dev/fxp/if_fxp.c,v 1.154 2003/04/03 20:39:43 mux Exp $ * $FreeBSD: src/sys/dev/fxp/if_fxpreg.h,v 1.30 2003/04/03 18:39:48 mux Exp $ * $FreeBSD: src/sys/dev/fxp/if_fxpvar.h,v 1.24 2003/04/02 16:47:16 mux Exp $ * $FreeBSD: src/sys/dev/fxp/rcvbundl.h,v 1.1 2001/10/25 05:23:31 jlemon Exp $ Could everyone which has problems with the fxp(4) driver mail me some informations ? I'd need the exact symptoms, the output of ifconfig on the interface, the part of pciconf -lv relevant to your fxp card, your kernel configuration file and the output of dmesg. That would be help me a lot to understand what's going on, since I can't reproduce these problems on any of my fxp(4) cards. Since this is a commonly used driver in the FreeBSD community, I've put a kernel module for fxp online, built with the sources prior to the busdma commit. It's at http://people.freebsd.org/~mux/if_fxp.ko.gz. Reverting back to kernel sources from 11 April yield functional interface. 11 April ? Did you make a typo ? Thanks, Maxime ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: So then, is fxp working OK again?
Conrad Sabatier wrote: On 04-Apr-2003 Maxime Henrion wrote: Conrad Sabatier wrote: Having had the same experiences as others described here recently with the fxp stuff, I'm just wondering if it's safe now to cvsup and try it again. I only have one machine here and if my net interface fails, I'm totally screwed. :-) It should. If it doesn't, I'm interested in knowing it. :-) Cheers, Maxime groan Still no go. I'm still getting a panic in bus_dmamem_alloc(). Here's the info I copied down by hand: Fatal trap 12: page fault while in kernel mode fault virtual address = 0x24 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0301639 stack pointer = 0x10:0xc053bd34 frame pointer = 0x10: 0xc053bd48 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 = 0() kernel: type 12 trap, code = 0 Stopped at bus_dmamen_alloc+0x9 movl 0x24(%edx),%eax dbtrace bus_dmamem_alloc(0, c04a8aa0, 1, c04a965c, ) at bus_dmamen_alloc+0x9 acpi_alloc_wakeup_handler(0, 532000, 532020, 532000, 0) at acpi_alloc_wakeup_handler+0xa9 mi_startup() at mi_startup+0x99 begin() at begin+0x2c db Incidentally, I've been getting acpi initialization failures in the last umpteen kernels I've been through, but without panicing the machine. Could you post a complete stack trace? There's no fxp functions in this (incomplete) trace. Are you sure the problem you're having now is fxp related ? Cheers, Maxime ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kp_proc and kp_eproc
On Fri, Apr 04, 2003 at 06:07:12PM -0600, Glenn Johnson wrote:
On Fri, Apr 04, 2003 at 03:54:05PM -0800, Julian Elischer wrote:
yes..
The entire process structure and it's surrounding enviroment has been
through a blender.
What do you wnat to do?
I would like to learn what I need to do to get the software to compile
on FreeBSD-5. I guess the question is, what information do I need to
provide? The software in question is OpenPBS (http://www.openpbs.org),
so it nothing proprietary. There were a whole bunch of dependency
problems that I worked through manually and finally got to the point
of the kp_proc failure. Here is a snippet of code that produces the
failure:
Here are untested patches I made for this a while ago. There's also a
port PR somewhere.
--- src/resmom/freebsd/mom_mach.c.orig Tue Dec 4 16:38:48 2001
+++ src/resmom/freebsd/mom_mach.c Wed Jan 15 21:04:15 2003
@@ -368,11 +368,21 @@
continue;
nps++;
+#if __FreeBSD_version 50
cputime += tvk(pp-kp_proc.p_rtime);
-
- if (pp-kp_proc.p_ru == NULL) {
+#else
+ cputime += tvk(pp-ki_runtime);
+#endif
+
+#if __FreeBSD_version 50
+ if (pp-kp_proc.p_ru == NULL)
+#else
+ if (pp-ki_rusage == NULL)
+#endif
+ {
struct pstats ps;
+#if __FreeBSD_version 50
DBPRT((%s: p_stats 0x%lx\n, id,
(u_long)pp-kp_proc.p_stats))
if (pp-kp_proc.p_stats == NULL)
@@ -387,10 +397,27 @@
tv(ps.p_ru.ru_stime) +
tv(ps.p_cru.ru_utime) +
tv(ps.p_cru.ru_stime);
+#else
+ DBPRT((%s: p_stats 0x%lx\n, id,
+ (u_long)pp-ki_user-u_stats))
+ if (pp-ki_addr-u_stats == NULL)
+ continue;
+
+ if (kvm_read(kd, (u_long)pp-ki_addr-u_stats, ps,
+ sizeof(ps)) != sizeof(ps)) {
+ log_err(errno, id, kvm_read(u_stats));
+ continue;
+ }
+ cputime += tv(ps.p_ru.ru_utime) +
+ tv(ps.p_ru.ru_stime) +
+ tv(ps.p_cru.ru_utime) +
+ tv(ps.p_cru.ru_stime);
+#endif
}
else {
struct rusage ru;
+#if __FreeBSD_version 50
DBPRT((%s: p_ru 0x%lx\n, id,
(u_long)pp-kp_proc.p_ru))
if (kvm_read(kd, (u_long)pp-kp_proc.p_ru, ru,
@@ -402,6 +429,19 @@
}
DBPRT((%s: ses %d pid %d cputime %d\n, id,
sess_tbl[i], pp-kp_proc.p_pid, cputime))
+#else
+ DBPRT((%s: p_ru 0x%lx\n, id,
+ (u_long)pp-ki_rusage))
+ if (kvm_read(kd, (u_long)pp-ki_rusage, ru,
+ sizeof(ru)) != sizeof(ru)) {
+ log_err(errno, id, kvm_read(session));
+ continue;
+ }
+ cputime += tv(ru.ru_utime) + tv(ru.ru_stime);
+ }
+ DBPRT((%s: ses %d pid %d cputime %d\n, id,
+ sess_tbl[i], pp-ki_pid, cputime))
+#endif
}
if (nps == 0)
@@ -429,12 +469,19 @@
if (!injob(pjob, sess_tbl[i]))
continue;
-
+#if __FreeBSD_version 50
memsize += ctob(pp-kp_eproc.e_vm.vm_tsize +
pp-kp_eproc.e_vm.vm_dsize +
pp-kp_eproc.e_vm.vm_ssize);
DBPRT((%s: ses %d pid=%d totmem=%lu\n, id,
sess_tbl[i], pp-kp_proc.p_pid, memsize))
+#else
+ memsize += ctob(pp-ki_tsize +
+ pp-ki_dsize +
+ pp-ki_ssize);
+ DBPRT((%s: ses %d pid=%d totmem=%lu\n, id,
+ sess_tbl[i], pp-ki_pid, memsize))
+#endif
}
return (memsize);
@@ -457,10 +504,17 @@
if (!injob(pjob, sess_tbl[i]))
continue;
+#if __FreeBSD_version 50
memsize += ctob(pp-kp_eproc.e_vm.vm_rssize);
DBPRT((%s: pid=%d ses=%d mem=%d totmem=%d\n, id,
pp-kp_proc.p_pid, sess_tbl[i],
pp-kp_eproc.e_vm.vm_rssize, memsize))
+#else
+ memsize += ctob(pp-ki_rssize);
+ DBPRT((%s: pid=%d ses=%d mem=%d totmem=%d\n, id,
+ pp-ki_pid, sess_tbl[i],
+ pp-ki_rssize,
