Re: kern/46619: Installation hangs on IBM Thinkpad T23
Actually, a simpler workaround is to set: hw.eisa_slots=0 in the boot loader. This machine also requires: unset acpi_load in order to boot. -Arun To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
pxeboot on RC1 or later ?
I'm trying to debug a kernel problem with the RC1 install CD (I get a hang) - basically playing with various kernel options and putting debug printfs. pxeboot sounded like just the thing I needed - burning CDs or floppies being too cumbersome for me. I've followed the recipe and get to the point where control passed from pxeboot - /boot/loader and /boot/kernel/kernel has been loaded. However, when I hit: OK boot -v / -- hang -- The spinning slash stops spinning and the console hangs. I have a IBM Thinkpad T23. My question is, has anyone successfully used pxeboot on -current recently, especially on a thinkpad ? If yes, what could I be doing wrong ? Is this related to /boot/device.hints not being loaded ? -Arun To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: pthreads using rfork_thread?
Jamie Burns [EMAIL PROTECTED] writes: Hello, I read somewhere that a pthreads library was being put together for 5.0 that used rfork_thread. Can anyone tell me how this is going? I'm not aware of an official plan to do this, but many months ago, I ported a MxN threading model implementation (NGPT) to FreeBSD. The code is certainly not production quality - but might be a good starting point to start hacking, if you're interested in working on it. Searching for ngpt-1.0.1 freebsd on google should take you to the right place. -Arun To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 5.0-DP2 boot failure on a 440GX motherboard
On Wed, Nov 20, 2002 at 05:35:53PM -0800, Arun Sharma wrote: On Wed, Nov 20, 2002 at 04:36:58PM -0800, Arun Sharma wrote: This is a dual Pentium III motherboard, with 2 x PIII at 850 MHz. 5.0-DP1 worked just fine on this machine. However, with DP2, I get a garbled console (Everything is ok till the Timecounter.. message). Sometimes the CD manages to boot and get into sysinstall, but hangs shortly thereafter. Even the sysinstall output is garbled. boot -v output captured from a serial console attached. I have debugged this some more. I'm able to boot, if I boot from serial console and am careful not to tickle the vga driver too much i.e. interact with the machine over the network or over the serial console. The moment I try to do anything on vga consoles, I get a hang. Another observation: even when booting from the serial console, when the vga driver probes/attaches the hardware, I see garbage written on my vga console. I tested that 11/25 kernel also has this problem. The problem didn't happen with DP1. -Arun To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 5.0-DP2 boot failure on a 440GX motherboard
On Tue, Dec 03, 2002 at 10:59:40PM -0500, Chuck Robey wrote: I have debugged this some more. I'm able to boot, if I boot from serial console and am careful not to tickle the vga driver too much i.e. interact with the machine over the network or over the serial console. The moment I try to do anything on vga consoles, I get a hang. Is this a hard hang, or is the vga output frozen (and keyboard still works, X still works, ssh still works) like I've been reporting? Hard hang. No network, keyboard LED doesn't work either. -Arun To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
5.0-DP2 boot failure on a 440GX motherboard
This is a dual Pentium III motherboard, with 2 x PIII at 850 MHz. 5.0-DP1 worked just fine on this machine. However, with DP2, I get a garbled console (Everything is ok till the Timecounter.. message). Sometimes the CD manages to boot and get into sysinstall, but hangs shortly thereafter. Even the sysinstall output is garbled. Any help would be greatly appreciated. -Arun To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 5.0-DP2 boot failure on a 440GX motherboard
On Wed, Nov 20, 2002 at 04:36:58PM -0800, Arun Sharma wrote: This is a dual Pentium III motherboard, with 2 x PIII at 850 MHz. 5.0-DP1 worked just fine on this machine. However, with DP2, I get a garbled console (Everything is ok till the Timecounter.. message). Sometimes the CD manages to boot and get into sysinstall, but hangs shortly thereafter. Even the sysinstall output is garbled. boot -v output captured from a serial console attached. -Arun OK boot -v SMAP type=01 base= len= 0009f400 SMAP type=02 base= 0009f400 len= 0c00 SMAP type=02 base= 000e8000 len= 00018000 SMAP type=01 base= 0010 len= 1fef SMAP type=03 base= 1fff len= fc00 SMAP type=04 base= 1c00 len= 0400 SMAP type=02 base= fec0 len= 0001 SMAP type=02 base= fee0 len= 1000 SMAP type=02 base= fff8 len= 0008 Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-DP2 #1: Sat Nov 16 13:38:33 GMT 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel /boot/kernel/kernel at 0xc0a68000. Preloaded mfs_root /boot/mfsroot at 0xc0a680b4. Calibrating clock(s) ... TSC clock: 845603651 Hz, i8254 clock: 1193135 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter i8254 frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method Timecounter TSC frequency 845639606 Hz CPU: Pentium III/Pentium III Xeon/Celeron (845.64-MHz 686-class CPU) Origin = GenuineIntel Id = 0x683 Stepping = 3 Features=0x387fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CM OV,PAT,PSE36,PN,MMX,FXSR,SSE real memory = 536805376 (511 MB) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x00a8f000 - 0x1ffe7fff, 525701120 bytes (128345 pages) avail memory = 510541824 (486 MB) bios32: Found BIOS32 Service Directory header at 0xc00f6c20 bios32: Entry = 0xfd7e3 (c00fd7e3) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xfd680+0x430 pnpbios: Found PnP BIOS data at 0xc00f6c50 pnpbios: Entry = f:ad32 Rev = 1.0 Other BIOS signatures found: Initializing GEOMetry subsystem null: null device, zero device random: entropy source mem: memory I/O Pentium Pro MTRR support enabled md0: Preloaded image /boot/mfsroot 4423680 bytes at 0xc062e588 npx0: math processor on motherboard npx0: INT 16 interface pci_open(1):mode 1 addr port (0x0cf8) is 0x8058 pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=71a08086) Using $PIR table, 12 entries at 0xc00fdf00 PCI-Only Interrupts: none Location Bus Device Pin Link IRQs slot 1 0 16A 0x60 3 4 5 7 10 11 12 14 15 slot 1 0 16B 0x65 3 4 5 7 10 11 12 14 15 slot 1 0 16C 0x66 3 4 5 7 10 11 12 14 15 slot 1 0 16D 0x67 3 4 5 7 10 11 12 14 15 slot 2 0 13A 0x61 3 4 5 7 10 11 12 14 15 slot 2 0 13B 0x66 3 4 5 7 10 11 12 14 15 slot 2 0 13C 0x67 3 4 5 7 10 11 12 14 15 slot 2 0 13D 0x65 3 4 5 7 10 11 12 14 15 embedded0 12A 0x63 3 4 5 7 10 11 12 14 15 embedded0 12B 0x63 3 4 5 7 10 11 12 14 15 slot 3 0 11A 0x62 3 4 5 7 10 11 12 14 15 slot 3 0 11B 0x67 3 4 5 7 10 11 12 14 15 slot 3 0 11C 0x65 3 4 5 7 10 11 12 14 15 slot 3 0 11D 0x66 3 4 5 7 10 11 12 14 15 embedded0 14A 0x65 3 4 5 7 10 11 12 14 15 slot 4 09A 0x63 3 4 5 7 10 11 12 14 15 slot 4 09B 0x65 3 4 5 7 10 11 12 14 15 slot 4 09C 0x66 3 4 5 7 10 11 12 14 15 slot 4 09D 0x67 3 4 5 7 10 11 12 14 15 embedded0 18D 0x65 3 4 5 7 10 11 12 14 15 embedded01A 0x65 3 4 5 7 10 11 12 14 15 embedded01B 0x66 3 4 5 7 10 11 12 14 15 embedded01C 0x67 3 4 5 7 10 11 12 14 15 embedded01D 0x64 3 4 5 7 10 11 12 14 15 embedded0 15A 0x65 3 4 5 7 10 11 12 14 15 embedded0 15B 0x66 3 4 5 7 10 11 12 14 15 embedded0 15C 0x67 3 4 5 7 10 11 12 14 15 embedded0 15D 0x64 3 4 5 7 10 11 12 14 15 slot 52554A 0x64 3 4 5 7 10 11 12 14 15 slot 52554B 0x65 3 4 5 7 10 11 12 14 15 slot 52554C 0x66 3 4 5 7 10 11 12 14 15 slot 52554D 0x67 3 4 5 7 10 11 12 14 15 slot 62557A 0x67 3 4 5 7 10 11 12 14 15 slot 62557B 0x64 3 4 5 7 10 11 12 14 15 slot 62557C 0x65 3 4 5 7 10 11 12 14 15 slot 62557D 0x66 3 4 5 7 10 11 12 14 15 pcib0: Intel 82443GX host to PCI bridge at pcibus 0 on motherboard pci0: PCI bus on pcib0 pci0
startx -listen_tcp = core dump
Works fine when I don't specify -listen_tcp. Has anyone seen this ? -Arun To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
panic with -current
This is with the GENERIC kernel. Known problem ? How can I get a -current kernel that boots to multiuser so that I can tinker around with it ? Are there any magic config files that suppress these panics ? db trace _mtx_lock_flags(7069307e,0,c03ff2e0,530) at _mtx_lock_flags+0x3e securelevel_ge(bfbffe00,3,c0291194,c04b0e60,c04b0ca8) at securelevel_ge+0x3c ip_fw_ctl(cad2fcc0,c026213c,0,c2075410,cad2fcac) at ip_fw_ctl+0x30 rip_ctloutput(c2075410,cad2fcc0,cad2fd14,c0d6c540,cad2fcec) at rip_ctloutput+0xe sosetopt(c2075410,cad2fcc0,c2075410,1,0) at sosetopt+0x2c setsockopt(c0d6c540,cad2fd14,5,0,213) at setsockopt+0x8e syscall(2f,2f,2f,8093879,bfbffe73) at syscall+0x233 syscall_with_err_pushed() at syscall_with_err_pushed+0x1b -Arun To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: panic with -current
On Sat, Jul 27, 2002 at 05:15:08PM -0400, John Baldwin wrote: Knowing the actual panic message would help. :) My bad. I was loading the wrong version of a kernel module (ipfw). -Arun To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Lock order reversal with a recent SMP kernel
lock order reversal 1st 0xc9c48d98 sis0 (network driver) @ /usr.current/src/sys/pci/if_sis.c:804 2nd 0xc0328600 allproc (allproc) @ /usr.current/src/sys/kern/kern_fork.c:309 Is this a problem ? -Arun To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Page faults in kernel mode
Running on a dual celeron box. CPU: Pentium II/Pentium II Xeon/Celeron (367.50-MHz 686-class CPU) Origin = GenuineIntel Id = 0x665 Stepping = 5 Features=0x183fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,C real memory = 201326592 (196608K bytes) avail memory = 191365120 (186880K bytes) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 1. While running background fsck alone: fatal trap 12: page fault while in kernel mode cpuid = 1; lapic.id = 0100 fault virtual address = 0xc9d65e90 fault code = supervisor write, page not present instruction pointer = 0x8:0xc01aee6c stack pointer = 0x10:0xcaafe9a4 frame pointer = 0x10:0xcaafe9b0 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 = 155 (syslogd) kernel: type 12 trap, code=0 Stopped at _mtx_lock_flags+0x3e: lock cmpxchgl %edx,0x1c(%ebx) db trace _mtx_lock_flags(c9d65e74,0,c02f31e0,6da,cabb5034) at _mtx_lock_flags+0x3e vref(c9d65e00,cabb5034,0,c02f2f40,98) at vref+0x1d namei(caafec10) at namei+0x17d vn_open_cred(caafec10,caafeb64,1a4,c98fe100,caafecec) at vn_open_cred+0x238 vn_open(caafec10,caafeb64,1a4,c01aeef3,cac6dac8) at vn_open+0x1b open(caadea54,caafed14,3,59,296) at open+0x155 syscall(2f,bfbf002f,bfbf002f,4,2811afa0) at syscall+0x1db syscall_with_err_pushed() at syscall_with_err_pushed+0x1b --- syscall (5, FreeBSD ELF, open), eip = 0x280a8c73, esp = 0xbfbfe78c, ebp = 0- 2. background fsck + two processes running find / panic: blockable sleep lock (sleep mutex) process lock @ /usr.current/src/sys/i1 cpuid = 0; lapic.id = Debugger(panic) Couldn't get any more information on the exact filename from ddb. 3. Running two copies of find / alone: Debugger(c02ea41a) at Debugger+0x46 panic(c02edc20,c02e9380,c02e7400,c030e420,2c7) at panic+0xd1 witness_lock(cb081818,8,c030e420,2c7,1) at witness_lock+0x7f _mtx_lock_flags(cb081818,0,c030e420,2c7,cb081738) at _mtx_lock_flags+0x6a trap_pfault(cb0bb8fc,0,64) at trap_pfault+0x92 trap(c02e0018,cb0b0010,c01a0010,c9d65b74,6a9) at trap+0x32b calltrap() at calltrap+0x5 --- trap 0xc, eip = 0xc01af1bf, esp = 0xcb0bb93c, ebp = 0xcb0bb950 --- _mtx_lock_sleep(c9d65b74,0,c02f31e0,6a9) at _mtx_lock_sleep+0x121 _mtx_lock_flags(c9d65b74,0,c02f31e0,6a9) at _mtx_lock_flags+0x58 vget(c9d65b00,2,cb081738,0,cb081738) at vget+0x28 vfs_cache_lookup(cb0bba74,cb0bbaa0,c01efc94,cb0bba74,cb081738) at vfs_cache_loo9 ufs_vnoperate(cb0bba74) at ufs_vnoperate+0x13 lookup(cb0bbc90,cb081738,cada5400,0,cb081738) at lookup+0x2b2 namei(cb0bbc90,0,cb0bbb20,c01af023,c0327ea0) at namei+0x1df execve(cb081738,cb0bbd14,3,1,297) at execve+0x19a syscall(2f,2f,2f,812e0b6,812e050) at syscall+0x1db syscall_with_err_pushed() at syscall_with_err_pushed+0x1b --- syscall (59, FreeBSD ELF, execve), eip = 0x80a6e80, esp = 0xbfbff9c8, ebp =- This sounds like a variant of (1). 4. More page faults in kernel mode: Fatal trap 12: page fault while in kernel mode cpuid = 1; lapic.id = 0100 fault virtual address = 0xc9d65014 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01f32d3 stack pointer = 0x10:0xc9d54c68 frame pointer = 0x10:0xc9d54c9c 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 = 7 (syncer) Also, in ddb, show map /f prints a never ending list of map objects. Is that normal or is my list corrupted somehow ? -Arun To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: KSE/threads progress report
On 7 Aug 2001 05:07:13 +0200, Daniel Eischen [EMAIL PROTECTED] wrote: At this stage diffs must be pushing close to 1MB (maybe more) (I don't know as I don't know yet how to get p4 to generate diffs :-) Isn't it just `p4 diff` ? The diff produced by the above command is not accepted by patch. I wrote a script sometime back to polish the diff output. Let me know if anyone is interested. Also, p4 diff2 has some extra options, that let you do more. -Arun To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: BP6 motherboard and hangs ...
In muc.lists.freebsd.current, you wrote: Anyone have any experience with the Abit BP6 motherboards? I've been reporting and talking about problems with -CURRENT the past little while, where when I start X, it pretty much dies soon after ... well, this weekend, I needed to make my system Dual-BOOT into W2K Professional Server for some work I'm doing (installing FreeBSD in vmware over w2k to run some server software) and W2K hangs solid also ... I'm starting to wonder if its a motherboard problem and has nothing to do with OS ... Anyone with experience here? I used to run into hanges related to UDMA/66 before I upgraded the BIOS. I think the "RU" bios is the latest one and my BP6 box has been up for 30 days now. -Arun To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Wrong permissions on /dev ?
I upgraded my 4.0-release laptop to 5.0-current today and my xe0 was recognized by the driver and everything was great. There is a minor nit about the permissions on /dev. It was not readable by others. So ps wouldn't work, because it could not open /dev/null. -Arun To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Xircom RealPort 10/100 LAN modem?
In muc.lists.freebsd.questions, you wrote: Does anyone know of support for this PCMCIA card in FreeBSD? I have looked everywhere and can't seem to find it anywhere...not good. I also have a Linksys LANmodem 33.6 10Bast-T PCMCIA NIC. Anyone know if that one is supported? For those interested, I just got my Xircom CE3 10/100 running on today's 5.0-current snapshot. It doesn't work on 4.x yet. -Arun To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
kern/18524 - SMP cpu stats
Can someone responsible for SMP please look at this PR: http://www.FreeBSD.org/cgi/query-pr.cgi?pr=18524 This is necessary for tools like xosview, ktop etc to display per cpu stats. -Arun To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Abit BP6 - UDMA66 and non IBM disks
I have the following disk: ad4: 9787MB WDC AC310200R [19885/16/63] at ata2-master using UDMA33 and am experiencing hangs when I run it with UDMA66. I originally suspected this to be a cooling problem. But uncommenting the hlt instruction and reducing the temperature by 10 deg C, didn't help it. I read the threads from Feb, where it was said that non IBM disks had problems with the UDMA66 code in FreeBSD. Some of you said that the disks worked just fine with other OSes. I'd like to know if there has been a change in status of the UDMA66 code. The specific error messages before the hang: ad4: READ command timeout - resetting ata2: resetting devices hang -Arun To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: KDE 2-preALPHA
In muc.lists.freebsd.current, you wrote: Has anyone had any luck with kde 2-preALPHA on -current. I couldn't get it to recognize QT even after installing the QT snapshot, and ldconfig did wierd things. When I finally found the libs(via a reboot), I still got unresolved symbols. No binaries, but I could compile on 4.0-stable. You need to set $KDEDIR and $QTDIR before you configure. -Arun To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
malloc.conf
After upgrading to 4.0 from source, I had a simple program which called malloc core dump on me. After ktrace'ing it and creating /etc/malloc.conf it was happier. But I can't find malloc.conf anywhere in /usr/src. How does it get created during the build ? -Arun To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: malloc.conf
On Sat, Mar 25, 2000 at 08:55:16PM +0100, Poul-Henning Kamp wrote: Please read the malloc(3) manual page. I did and created malloc.conf as documented there. And things were fine after that. Wouldn't it be better if the build process created a default /etc/malloc.conf ? -Arun To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: malloc.conf
On Sat, Mar 25, 2000 at 09:05:18PM +0100, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Arun Sharma writes: On Sat, Mar 25, 2000 at 08:55:16PM +0100, Poul-Henning Kamp wrote: Please read the malloc(3) manual page. I did and created malloc.conf as documented there. And things were fine after that. Wouldn't it be better if the build process created a default /etc/malloc.conf ? Exactly how did you create it ? Just as it is documented: ln -s 'A' /etc/malloc.conf -Arun To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: malloc.conf
On Sat, Mar 25, 2000 at 12:11:50PM -0800, Jordan K. Hubbard wrote:
I did and created malloc.conf as documented there. And things were
fine after that. Wouldn't it be better if the build process created
a default /etc/malloc.conf ?
It's purely an optional file; one doesn't need to be installed by
default in order for things to behave as expected. Consider it
a debugging feature.
You're right. It works for the default case. I was doing an unsupported
operation: experimenting with rfork and the clone() call from Linuxthreads
port.
However, the mere presence of clone() in the same executable
makes malloc unhappy.
8668 test CALL readlink(0x280f1114,0xbfbff7b8,0x3f)
8668 test NAMI "/etc/malloc.conf"
8668 test RET readlink -1 errno 2 No such file or directory
8668 test CALL sigprocmask(0x1,0x2806,0x28060010)
8668 test RET sigprocmask 0
8668 test CALL sigprocmask(0x3,0x28060010,0)
8668 test RET sigprocmask 0
8668 test PSIG SIGSEGV SIG_DFL
8668 test NAMI "test.core"
The program is:
#include stdio.h
#include unistd.h
#include stdlib.h
#include sys/types.h
#include sys/wait.h
main()
{
int status;
pid_t pid;
void *stack;
stack = malloc(4096);
}
It works fine stand alone. But when linked with some other stuff, it core
dumps. If I create /etc/malloc.conf, it's ok.
-Arun
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: ucontext
On Wed, Mar 22, 2000 at 08:04:37AM -0500, Daniel Eischen wrote: I had them implemented and working for i386, and even had a hacked up libc_r that used them instead of setjmp/longjmp. This was a few months ago under 4.0-current. At the time, I thought they'd be better off implemented as syscalls, but now I'm leaning towards library routines similar to setjmp/longjmp (which make a syscall to change the signal mask). UNIX 98 specifies that setcontext should be callable from signal handlers. http://www.opengroup.org/onlinepubs/007908799/xsh/getcontext.html That pretty much means system calls. Doesn't it ? I was wrong about this being necessary for the JDK. Linux doesn't implement it either (it does have man pages and header files though!) and the JDK runs fine on Linux. I was mislead by the some of these calls, which will always fail on Linux. -Arun To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ucontext
On Wed, Mar 22, 2000 at 02:48:24PM -0500, Daniel Eischen wrote: On Wed, 22 Mar 2000, Arun Sharma wrote: On Wed, Mar 22, 2000 at 08:04:37AM -0500, Daniel Eischen wrote: I had them implemented and working for i386, and even had a hacked up libc_r that used them instead of setjmp/longjmp. This was a few months ago under 4.0-current. At the time, I thought they'd be better off implemented as syscalls, but now I'm leaning towards library routines similar to setjmp/longjmp (which make a syscall to change the signal mask). UNIX 98 specifies that setcontext should be callable from signal handlers. http://www.opengroup.org/onlinepubs/007908799/xsh/getcontext.html That pretty much means system calls. Doesn't it ? I don't know, does it? The reason we don't want it to be a system call is that if the threads library is going to use it to save and restore thread state, we don't want the overhead of a system call. You're right. It doesn't have to be a system call, just to support longjmp'ing or doing setcontext from signal handlers. However, I can think of two situations under which it might have to be a system call: (a) If the user is allowed to modify the system mode context of the processor i.e. things that can be done only in the privileged mode. (b) If one needs to get the context of other blocked processes Neither of the two sound like strong reasons to me. -Arun To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ucontext
On Tue, Sep 07, 1999 at 01:21:59PM +0200, Marcel Moolenaar wrote: Peter Wemm wrote: Before getting too far here, can we consider some other standard interfaces? #include ucontext.h int getcontext(ucontext_t *ucp); int setcontext(const ucontext_t *ucp); void makecontext(ucontext_t *ucp, (void *func)(), int argc, ...); int swapcontext(ucontext_t *oucp, const ucontext_t *ucp); http://www.opengroup.org/onlinepubs/007908799/xsh/ucontext.h.html setjmp,longjmp,sigreturn,etc can all be done with this interface and it can be used for libc_r and future kernel-assisted threading. We're at a point where the discussion, altough meaningful and important, has no direct impact on the sigset_t change. I agree with Peter that we should as well consider the ucontext interface, but prefer to stay focussed on changing sigset_t. So, here's where I shut up and let you discuss the matter further :-) Is anyone working on this ? Porting JDKs to FreeBSD would be a lot easier if these routines are implemented. -Arun To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current lockups
Compiling Mozilla with make -j 2 got -current to lock up, twice in succession. I'm running a fairly recent snapshot (a week or two old) on a Dual celeron box (BP6) with UDMA66 enabled. The kernel had DDB enabled. I was running X, but I didn't see any signs of the kernel attempting to get into the debugger. Has this been fixed ? Is anyone interested in investigating ? I'll post more info if I find anything. Another data point: I had another lockup today. I left the box to do a buildworld and went out for dinner. When I'd returned, the machine had locked up tight, but the orange LED on the disk was on. Now, I don't know if the problem is my WDC 20 GB disk or something else in the ATA driver. I'm running on the RELENG_4 branch as of yesterday night. -Arun To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current lockups
On Mon, Mar 06, 2000 at 08:27:18PM +0100, Dave Boers wrote: Has this been fixed ? Is anyone interested in investigating ? I'll post more info if I find anything. I'm interested in the fix, of course :-) But where to start looking? I've had three lockups so far (none before january 2000) but I didn't find anything that reliably triggered it. The cooling theory sounds the most plausible so far. I'm not over clocking my CPUs (Celeron 366s) and have appropriate cooling installed. But the machine is kept in a small room, with a bunch of other machines and gets a bit warm at times. There has been no reproducible case of locking up. Each one looks different. But most were trigerred by heavy compilation and I/O. One was a lockup overnight with no activity on the system. When it happens, it does not respond to pings or scroll lock. If you'd like to do something about it, working on getting a reproducible hang would be the most beneficial one. -Arun To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
current lockups
Compiling Mozilla with make -j 2 got -current to lock up, twice in succession. I'm running a fairly recent snapshot (a week or two old) on a Dual celeron box (BP6) with UDMA66 enabled. The kernel had DDB enabled. I was running X, but I didn't see any signs of the kernel attempting to get into the debugger. Has this been fixed ? Is anyone interested in investigating ? I'll post more info if I find anything. -Arun To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ABIT BP6, UDMA-66 and wdc AC310200
I have the above hardware combination and here's the dmesg from 4.0-current: atapci0: Intel PIIX4 ATA33 controller port 0xf000-0xf00f at device 7.1 on pci0 atapci1: HighPoint HPT366 ATA66 controller port 0xb400-0xb4ff,0xb000-0xb003,0xac00-0xac07 irq 11 at device 19.0 on pci0 ata2: at 0xac00 on atapci1 atapci2: HighPoint HPT366 ATA66 controller port 0xc000-0xc0ff,0xbc00-0xbc03,0xb800-0xb807 irq 11 at device 19.1 on pci0 ad4: 9787MB WDC AC310200R [19885/16/63] at ata2-master using UDMA33 How do I get my disk to work in UDMA66 mode ? Is it supported with for my disk ? http://www.westerndigital.com/service/FAQ/dtr.html lists my disk as ATA-66. What am I doing wrong ? -Arun To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ABIT BP6, UDMA-66 and wdc AC310200
On Tue, Feb 22, 2000 at 11:54:40AM +0100, Soren Schmidt wrote: It seems Arun Sharma wrote: I have the above hardware combination and here's the dmesg from 4.0-current: atapci0: Intel PIIX4 ATA33 controller port 0xf000-0xf00f at device 7.1 on pci0 atapci1: HighPoint HPT366 ATA66 controller port 0xb400-0xb4ff,0xb000-0xb003,0xac00-0xac07 irq 11 at device 19.0 on pci0 ata2: at 0xac00 on atapci1 atapci2: HighPoint HPT366 ATA66 controller port 0xc000-0xc0ff,0xbc00-0xbc03,0xb800-0xb807 irq 11 at device 19.1 on pci0 ad4: 9787MB WDC AC310200R [19885/16/63] at ata2-master using UDMA33 How do I get my disk to work in UDMA66 mode ? Is it supported with for my disk ? Do you have the prober 80pin cable ?? if so please provide a verbose boot... Thanks, that fixed the problem. Has anyone benchmarked the driver ? A very unscientific benchmark that I ran didn't seem to produce much of a difference between UDMA33 and UDMA66. In both cases, I got roughly 13 MB/s. # dd if=/dev/ad4s2 of=/dev/null bs=40960k count=10 10+0 records in 10+0 records out 419430400 bytes transferred in 30.797045 secs (13619177 bytes/sec) Can anyone point me to some benchmarks and comment about the improvement ? -Arun To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
