PANIC with tonight's -CURRENT
I just upgraded my PIII 750 to tonight's -CURRENT, and it panics right
after creating GEOM disks for da0 and cd0:
Waiting 8 seconds for SCSI devices to settle
GEOM: create disk cd0 dp=0xc5174600
GEOM: create disk da0 dp=0xc516ec50
panic: pmap_zero_page: CMAP3 busy
Here is the stack trace (copied from screen):
Debugger("panic")
Stopped atDebugger+0x54: xchgl %ebx,in_Debugger.0
Debugger(c066ccee,c06c3720,c067b95d,dd194ca0,100) at Debugger+0x54
panic(c067b95d,c0c601b8,dd194cc8,c05f3098,c0c601b8) at panic+0xd5
pmap_zero_page_idle(c0c601b8,0,0,4,0) at pmap_zero_page_idle+0x1c
vm_page_zero_idle(dd194ce8,c5165000,e823,5c7,3cfbc) at
vm_page_zero_idle+0xe8
vm_pagezero(0,dd194d48,3cfd805,83c20100,15890fe2) at vm_pagezero+0x172
fork_exit(c05f31e0,0,dd194d48) at fork_exit+0xb1
fork_trampoline() at fork_trampoline+0x8
--- trap 0x1, eip = 0, esp = 0xdd194d7c, ebp = 0 ---
I leave the machine in DDB in case anyone needs more info. Thanks.
Joe
--
PGP Key : http://www.marcuscom.com/pgp.asc
signature.asc
Description: This is a digitally signed message part
Re: panic: The GEOM class BDE already loaded
On Fri, 10 Oct 2003, Christian Brueffer wrote:
> Date: Fri, 10 Oct 2003 02:08:26 +0200
> From: Christian Brueffer <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: panic: The GEOM class BDE already loaded
>
> Hi,
>
> just got the following panic on my server. The panic occured while trying
> to attach a gbde encrypted disk. geom_bde is compiled into the kernel.
>
The problem seems to be that the kld name is 'geom_bde' but the module
name is 'g_bde' and gbde's main() we search for the kld which in your case
doesn't exist.
Could you please try the attached patch for src/sbin/gbde?
Bye/2
---
Michael Reifenberger, Business Unit Manager SAP-Basis, Plaut Consulting
Comp: [EMAIL PROTECTED] | Priv: [EMAIL PROTECTED]
http://www.plaut.de | http://www.Reifenberger.com
--- gbde.c.orig Fri Oct 10 09:55:15 2003
+++ gbde.c Fri Oct 10 09:55:19 2003
@@ -57,5 +57,6 @@
#include
-#define GBDEMOD "geom_bde"
+#define GBDEKLD "geom_bde"
+#define GBDEMOD "g_bde"
#define KASSERT(foo, bar) do { if(!(foo)) { warn bar ; exit (1); } } while (0)
@@ -673,8 +674,8 @@
usage("Too few arguments\n");
- if ((i = kldfind(GBDEMOD)) < 0) {
+ if ((i = modfind(GBDEMOD)) < 0) {
/* need to load the gbde module */
- if (kldload(GBDEMOD) < 0 || kldfind(GBDEMOD) < 0) {
- usage(GBDEMOD ": Kernel module not available");
+ if (kldload(GBDEKLD) < 0 || kldfind(GBDEKLD) < 0) {
+ usage(GBDEKLD ": Kernel module not available");
}
}
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Seeing system-lockups on recent current
On 10 Oct, Dag-Erling Smørgrav wrote: > Doug White <[EMAIL PROTECTED]> writes: >> On Fri, 10 Oct 2003, Garance A Drosihn wrote: >> > For the past week or so, I have been having a frustrating time >> > with my freebsd-current/i386 system. It is a dual Athlon >> > system. [...] >> It would be useful to isolate exactly what day the problem started >> occuring. > > I experienced similar problems on a dual Athlon system (MSI K7D > Master-L motherboard, AMD 760MPX chipset, dual Athlon MP 2200+) which > is barely a couple of months old. I ended up reverting to RELENG_5_1. > With -CURRENT, both UP and SMP kernels will crash with symptoms which > suggest hardware trouble. With RELENG_5_1, UP is rock solid (knock on > wood) while SMP crashes within minutes of booting. I've run out of > patience with this system, so I'll keep running RELENG_5_1 on it until > someone manages to convince me that -CURRENT will run properly on AMD > hardware (maybe around 5.3 or so...) My Athlon XP 1900+/AMD 761 UP box is happily running a late October 6th version of -current. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
panic: page fault (using ppp ipv6cp)
Hello,
I upgraded my machine to CURRENT of today. It was paniced at while the
ppp process was making the IPv6 tunnel. When I rebooted it several
times, the problem occurred in the same place (currnet process = ppp).
Now I'm using an older kernel(cvsuped October 2). This older kernel
works fine.
My setting of ppp is as follows.
## ppp.conf
default:
set log Phase Chat LCP IPCP CCP tun command
set server /tmp/pppctl "" 0177
allow users yoshi
tun6:
set escape 0xff
set device xxx.xxx.xxx.xxx:6669
set dial
set timeout 0 0
set authname tun
set authkey
enable ipv6cp
disable ipcp
## rc.conf
ppp_enable="YES"
ppp_profile="tun6"
ppp_mode="ddial"
ipv6_enable="YES"
ipv6_network_interfaces="em0"
ipv6_gateway_enable="YES"
ipv6_static_routes="default"
ipv6_route_default="default -interface tun0"
ipv6_prefix_em0="2001:268:304:9b00"
panic message and backtrace:
Fatal trap 12: page fault while in kernel mode
cpuid = 0; lapic.id =
fault virtual address = 0x1
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc058331c
stack pointer = 0x10:0xe5638a24
frame pointer = 0x10:0xe5638a90
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 = 271 (ppp)
panic: from debugger
cpuid = 0; lapic.id =
(kgdb) bt
#0 doadump () at /usr/src/sys/kern/kern_shutdown.c:240
#1 0xc0501d46 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:372
#2 0xc0502198 in panic () at /usr/src/sys/kern/kern_shutdown.c:550
#3 0xc0444232 in db_panic () at /usr/src/sys/ddb/db_command.c:450
#4 0xc0444192 in db_command (last_cmdp=0xc06fede0, cmd_table=0x0,
aux_cmd_tablep=0xc06cfc8c, aux_cmd_tablep_end=0xc06cfc90)
at /usr/src/sys/ddb/db_command.c:346
#5 0xc04442d5 in db_command_loop () at /usr/src/sys/ddb/db_command.c:472
#6 0xc04472f5 in db_trap (type=12, code=0) at /usr/src/sys/ddb/db_trap.c:73
#7 0xc0662ccc in kdb_trap (type=12, code=0, regs=0xe56389e4)
at /usr/src/sys/i386/i386/db_interface.c:171
#8 0xc067cd16 in trap_fatal (frame=0xe56389e4, eva=0)
at /usr/src/sys/i386/i386/trap.c:815
#9 0xc067c9b2 in trap_pfault (frame=0xe56389e4, usermode=0, eva=1)
at /usr/src/sys/i386/i386/trap.c:734
#10 0xc067c50d in trap (frame=
{tf_fs = -969277416, tf_es = -964100080, tf_ds = -446496752, tf_edi = 0, tf_esi
= 56, tf_ebp = -446461296, tf_isp = -446461424, tf_ebx = -969272576, tf_edx = 0,
tf_ecx = -968655616, tf_eax = -968655616, tf_trapno = 12, tf_err = 0, tf_eip =
-1067961572, tf_cs = 8, tf_eflags = 66182, tf_esp = -967892080, tf_ss = -446461340})
at /usr/src/sys/i386/i386/trap.c:419
#11 0xc06646c8 in calltrap () at {standard input}:103
#12 0xc0584bd5 in rt_setgate (rt=0xc6437d00, dst=0xc6307a80, gate=0x0)
at /usr/src/sys/net/route.c:997
#13 0xc0585fef in route_output (m=0xc239d800, so=0xc66b8b00)
at /usr/src/sys/net/rtsock.c:451
#14 0xc0583073 in raw_usend (so=0x0, flags=0, m=0x0, nam=0x0, control=0x0,
td=0xc64f2390) at /usr/src/sys/net/raw_usrreq.c:257
#15 0xc0585865 in rts_send (so=0x0, flags=0, m=0x0, nam=0x0, control=0x0,
td=0x0) at /usr/src/sys/net/rtsock.c:241
#16 0xc0541b8d in sosend (so=0xc66b8b00, addr=0x0, uio=0xe5638c6c,
top=0xc239d800, control=0x0, flags=0, td=0xc64f2390)
at /usr/src/sys/kern/uipc_socket.c:714
#17 0xc0530b97 in soo_write (fp=0x0, uio=0xe5638c6c, active_cred=0xc688e980,
flags=0, td=0xc64f2390) at /usr/src/sys/kern/sys_socket.c:115
#18 0xc052a5c8 in dofilewrite (td=0xc64f2390, fp=0xc66a9154, fd=0,
buf=0xbfbfec80, nbyte=0, offset=0, flags=0) at /usr/src/sys/sys/file.h:249
#19 0xc052a3fe in write (td=0xc64f2390, uap=0xe5638d10)
at /usr/src/sys/kern/sys_generic.c:330
#20 0xc067d100 in syscall (frame=
{tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 2, tf_esi = 2, tf_ebp =
-1077941144, tf_isp = -446460556, tf_ebx = 176, tf_edx = -1077941120,---Type
to continue, or q to quit---
_eax = 4, tf_trapno = 12, tf_err = 2, tf_eip = 673729887, tf_cs = 31, tf_eflags = 531,
tf_esp = -1077941188, tf_ss = 47}) at /usr/src/sys/i386/i386/trap.c:1009
#21 0xc066471d in Xint0x80_syscall () at {standard input}:145
---
Yoshihide Sonoda
E-mail: [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
xl0: watchdog timeout
Since upgrading to -CURRENT last night I have been getting a lot of watchdog timeouts on my xl0 device every time I put it under load: citusc17# grep "watchdog timeout" messages | wc -l 44 Oct 10 02:30:48 citusc17 kernel: xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0xdc00-0xdc7f mem 0xff00-0xff7f irq 11 at device 17.0 on pci0 Oct 10 02:30:48 citusc17 kernel: xl0: Ethernet address: 00:c0:4f:0e:26:15 Oct 10 02:30:48 citusc17 kernel: miibus0: on xl0 Oct 10 02:30:48 citusc17 kernel: xlphy0: <3Com internal media interface> on miibus0 Oct 10 02:30:48 citusc17 kernel: xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Is anyone else seeing this? Kris pgp0.pgp Description: PGP signature
Re: Seeing system-lockups on recent current
Doug White <[EMAIL PROTECTED]> writes: > On Fri, 10 Oct 2003, Garance A Drosihn wrote: > > For the past week or so, I have been having a frustrating time > > with my freebsd-current/i386 system. It is a dual Athlon > > system. [...] > It would be useful to isolate exactly what day the problem started > occuring. I experienced similar problems on a dual Athlon system (MSI K7D Master-L motherboard, AMD 760MPX chipset, dual Athlon MP 2200+) which is barely a couple of months old. I ended up reverting to RELENG_5_1. With -CURRENT, both UP and SMP kernels will crash with symptoms which suggest hardware trouble. With RELENG_5_1, UP is rock solid (knock on wood) while SMP crashes within minutes of booting. I've run out of patience with this system, so I'll keep running RELENG_5_1 on it until someone manages to convince me that -CURRENT will run properly on AMD hardware (maybe around 5.3 or so...) Now, my shiny new 2.4 GHz P4, on the other hand... *drool* DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Why is em nic generating interrupts?
Michael O. Boev wrote: > From: Terry Lambert [mailto:[EMAIL PROTECTED] > > "Michael O. Boev" wrote: > > > I've got a [uniprocessor 5.1-RELEASE] router machine with fxp > > > and em nics. > > > I've built my kernel with the following included: > > > > > > options DEVICE_POLLING > > > options HZ=2500 > > > > > > and enabled polling in /etc/sysctl.conf. > > [ ... ] > > > What's happening? Is polling working in my case? > > > If yes, why is vmstat showing interrupts? I see clearly, > > > that fxp's counter doesn't increase, and em's is constantly growing. > > > > > > Is there anyone who knows for sure that em's polling works? > > > > You may want to ask Luigi; polling is his code. > > > > However, I believe the issue is that polling doesn't start > > until you take an interrupt, and it stops as soon as there is > > no more data to process, and waits for the next interrupt. > > > > If you were to jack your load way up, you would probably see > > an increase in interrupts, then them dropping off dramatically. > To this dare I object, that there is traffic going through this machine, > and fxp0 is NOT generating interrupts, while em IS. So, if the rule above > works, they both have to behave in same ways. This is the third time I've received this message. I guess you feel some urgency about receiving a reply? My answer is this: I did the polling code for a number of the drivers, and though it was committed by someone else, I can guarantee you that it will have interrupts, unless the code was implemented incorreectly, since the code is meant to do this polling only under heavy load. The purpose of going to a polling model is *not* to avoid interrupts, it's to avoid processing data into the input routines when you don't have enough CPU cycles to deal with it before more data comes in. In other words, it's to deal with the situation where you would end up in receiver livelock as a result of taking so many interrupts that you never get an oportunity to process the packets out of the input queue into the per protocol input routines at NETISR, or from the top-of stack (socket buffers) into the user buffers in user space, or run the code in user space to take the data and generate a reply, or in kernel space to send the reply out. In other words, you *only ever* want to do polling when you have sufficient load to make polling worthwhile, and when you do it under low loads, you are actually *wasting* cycles, rather than *saving* them. Polling never *saves* cycles, per se, it only causes incoming data to be dropped (and, presumably, retransmitted) by the other end of the connection. For this, because there is not specific card support for it, and there's no interface entry points to deal with it, even if there were, the DMA engine on the card is *NOT* halted, you *still* eat bus transfer overhead, and it still eats up your PCI bandwidth, and this cost is *incredibly* larger than just interrupt and requeueing overhead. If your FXP is not generating any interrupts at all, i think that the polling code in it is probably broken. Note: I believe this might be one of the ones I modified, since Luigi's code originally only dealt with Gigabit NICs, though I may be mistaken. If so, my statement that it's broken should be considered to be pretty authoritative. 8-). -- Terry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Seeing system-lockups on recent current
At 12:48 PM -0700 10/10/03, Doug White wrote: On Fri, 10 Oct 2003, Garance A Drosihn wrote: For the past week or so, I have been having a frustrating time with my freebsd-current/i386 system. It is a dual Athlon system. It has been running -current just fine since December, with me updating the OS every week or two. I did not update it for most of September, and then went to update it to pick up the recent round of security-related fixes. It would be useful to isolate exactly what day the problem started occuring. That would simplify isolating the offending commit. Use the date specifier in cvsup to checkout specific dates, then build & test. I've done that. As mentioned in the message, I've done complete system rebuilds using snapshots from about Sept 12th to Oct 8th. The problem is that it's tedious do keep doing these rebuilds, when the very act of a buildworld or buildkernel can trigger the system lockup. I really am torn between thinking that it's a change in -current and thinking it must be something about my specific system. Depending on which set of observations I pick, I can make an excellent case for either one being the culprit. So, if no one else *is* seeing this kind of problem, then it's more likely to be my hardware (one way or another). I'll keep trying things. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: BTX Halted (AMD 5x86 133MHz)
On 10-Oct-2003 Dan Nelson wrote: > In the last episode (Oct 10), John Baldwin said: >> On 10-Oct-2003 Giovanni P. Tirloni wrote: >> > I've got the following message while trying to boot 5.1-RELEASE on >> > a AMD 586 133MHz, 24MB and a 850MB hard disk that I was using in >> > another machine: >> > >> > BTX loader 1.00 BTX version is 1.01 >> > Console: internal video/keyboard >> > BIOS drive C: is disk0 >> > BIOS 640kB/23552kB avaiable memory >> > >> > FreeBSD/i386 bootstrap loader, Revision 1.1 >> > ([EMAIL PROTECTED], Thu Jan 5 00:52:26 GMT 2003) >> > Warning -- Unmatched control word: leave >> > | >> >> Does this box work ok with a 4.x release CD? It may be your RAM. >> The Warning message is kind of weird. It seems you were probably in >> the BIOS trying to read some bits off of disk and the BIOS headed off >> to lala-land. > > Could there be a typo or other error in one of /boot/loader's scripts? > "Warning -- Unmatched control word: leave" would be generated by > resolveAbsBranch() in sys/boot/ficl/words.c. Given that no one else has reported such a warning and that some of the registers in his dump had weird values, I would really chalk this up to hardware. -- John Baldwin <[EMAIL PROTECTED]> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Seeing system-lockups on recent current
On Fri, 10 Oct 2003, Garance A Drosihn wrote: > For the past week or so, I have been having a frustrating time > with my freebsd-current/i386 system. It is a dual Athlon > system. It has been running -current just fine since December, > with me updating the OS every week or two. I did not update it > for most of September, and then went to update it to pick up > the recent round of security-related fixes. It would be useful to isolate exactly what day the problem started occuring. That would simplify isolating the offending commit. Use the date specifier in cvsup to checkout specific dates, then build & test. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re[2]: ATA broken as of yesterday?
Hi Bruno Van Den Bossche, you wrote. BVDB> On Thu, 9 Oct 2003 14:36:12 +0200 BVDB> Gabriel Ambuehl <[EMAIL PROTECTED]> wrote: >> A machine I had recompiled with a CVSUP as of yesterday (and again >> today, to no avail) can't mount root from a HPT370 (/dev/ar0s1a) >> RAID 1 array anymore, with the saved old kernel (two weeks or so I >> think) it boots without any trouble. BVDB> I've got the same controller onboard and just cvsupped and rebuild world BVDB> and kernel and everyting seems to be working fine. I don't have my BVDB> root-partition on it and it's configured for striping instead of RAID 1. BVDB> atapci1: port BVDB> 0xcc00-0xccff,0xc800-0xc803,0xc400-0xc407,0xc000-0xc003,0xbc00-0xbc07 BVDB> irq 9 at device 14.0 on pci0 I think my machine didn't even show up atapci1 with the new kernel. But since I'm not currently onsite, it's hard to verify this. I'll see whether I can get another box with the controller together. Regards, Gabriel ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: howto debug acpi_thermal on Dell 2500 servers
Thanks for the info. I did try mbmon, not the x version, but the command line version. It hung. I have hunted for thermal details for 2500 servers on dell's web site but can not find anything that seems to relate! I was hoping that acpi was the answer. Seems like the it's a secret :( , I am not an expert in this area. The acpi stuff looks really cool. Very easy to use in any program (I use nagios for monitoring (see ports)). If anyone knows a detail I don't about this I don't want to flood current unless it's relevant (I think acpi is relevant to curent, but general temp stuff would not be). I will entertain any other ideas in private messages, so please feel free to e-mail me privately. Thanks! Ken - Original Message - From: "Sten" <[EMAIL PROTECTED]> To: "Ken Menzel" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Friday, October 10, 2003 1:48 PM Subject: Re: howto debug acpi_thermal on Dell 2500 servers > On Fri, 10 Oct 2003, Ken Menzel wrote: > > > Hi, > >I am trying to figure out how to use ACPI to get thermal info on > > Dell 2500 servers. I have compiled acpi into the kernel (see below > > for problems with acpi as module with ACPI_DEBUG in make.conf). I > > can't seem to get any addtional info from acpi. Do I need a debug > > kernel? Do I have to have more options in my kernel config? Is > > someone already doing (done?) this and I shouldn't bother to try and > > debug it? > > I do know that on the dell 1550, temperature monitoring is done > with an lm80, which didn't seem to want to play with smbus. > (x)mbmon which opens /dev/io directly is able to get temperature > readings. Might be worth a try. > > -- > Sten Spans > > There is a crack in everything that's how the light gets in. > ___ > [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]"
Seeing system-lockups on recent current
For the past week or so, I have been having a frustrating time with my freebsd-current/i386 system. It is a dual Athlon system. It has been running -current just fine since December, with me updating the OS every week or two. I did not update it for most of September, and then went to update it to pick up the recent round of security-related fixes. My first update run picked up a change which caused system panics. Other people were also seeing that panic, and it wasn't long before updates were committed to current to fix that problem. However, ever since then my -current system has very frequently locked up. Totally locked. The only way to get it back is a hardware reset. I have rebuilt the system at least a dozen times since then. I have built it with snapshots of /usr/src from Sept 12th to Oct 8th (which is what it's running at the moment). I have dropped back to a single-CPU kernel. I turned off X (in /etc/ttys) so that doesn't start up at all. All those attempts to get a reliable 5.x-system have not worked. Sometimes the system will crash in the middle of a buildworld, other times it will crash while it's basically idle and the monitor is turned off. One time it crashed in the middle of an installworld -- right when it was replacing /lib files. Boy was that a headache to recover from! On the same PC, in a different DOS partition, is a 4.x-stable system. If I boot into 4.x, I have no problems. I fire up all the servers that I run, start buildworlds, run cvsup's, and even had all the 5.x partitions mounted and was running a infinite-loop that MD5'd every file in the 5.x system. I had all of that going on at the same time, and the system is fine. While in the 4.x system, I've removed /usr/src on the 5.x system and recreated it, just in case there were some files corrupted in there. And once the problems started, I made a point of always removing all of /usr/obj/usr/src before starting the buildworld, in case there were corrupted files in there. I still have a few things I want to try. And I know it could still be a hardware problem (although it bugs me that it fails so consistently on 5.x and never fails on 4.x). Perhaps it is just some disk-corruption problem that occurred during the first few panics. But I thought I'd at least mention it, and see if anyone else has been having similar problems. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: howto debug acpi_thermal on Dell 2500 servers
On Fri, 10 Oct 2003, Ken Menzel wrote: > Hi, >I am trying to figure out how to use ACPI to get thermal info on > Dell 2500 servers. I have compiled acpi into the kernel (see below > for problems with acpi as module with ACPI_DEBUG in make.conf). I > can't seem to get any addtional info from acpi. Do I need a debug > kernel? Do I have to have more options in my kernel config? Is > someone already doing (done?) this and I shouldn't bother to try and > debug it? I do know that on the dell 1550, temperature monitoring is done with an lm80, which didn't seem to want to play with smbus. (x)mbmon which opens /dev/io directly is able to get temperature readings. Might be worth a try. -- Sten Spans There is a crack in everything that's how the light gets in. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: BTX Halted (AMD 5x86 133MHz)
In the last episode (Oct 10), John Baldwin said: > On 10-Oct-2003 Giovanni P. Tirloni wrote: > > I've got the following message while trying to boot 5.1-RELEASE on > > a AMD 586 133MHz, 24MB and a 850MB hard disk that I was using in > > another machine: > > > > BTX loader 1.00 BTX version is 1.01 > > Console: internal video/keyboard > > BIOS drive C: is disk0 > > BIOS 640kB/23552kB avaiable memory > > > > FreeBSD/i386 bootstrap loader, Revision 1.1 > > ([EMAIL PROTECTED], Thu Jan 5 00:52:26 GMT 2003) > > Warning -- Unmatched control word: leave > > | > > Does this box work ok with a 4.x release CD? It may be your RAM. > The Warning message is kind of weird. It seems you were probably in > the BIOS trying to read some bits off of disk and the BIOS headed off > to lala-land. Could there be a typo or other error in one of /boot/loader's scripts? "Warning -- Unmatched control word: leave" would be generated by resolveAbsBranch() in sys/boot/ficl/words.c. -- 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: BTX Halted (AMD 5x86 133MHz)
On 10-Oct-2003 Giovanni P. Tirloni wrote: > Hi, > > I've got the following message while trying to boot 5.1-RELEASE on a > AMD 586 133MHz, 24MB and a 850MB hard disk that I was using in another > machine: > > BTX loader 1.00 BTX version is 1.01 > Console: internal video/keyboard > BIOS drive C: is disk0 > BIOS 640kB/23552kB avaiable memory > > FreeBSD/i386 bootstrap loader, Revision 1.1 > ([EMAIL PROTECTED], Thu Jan 5 00:52:26 GMT 2003) > Warning -- Unmatched control word: leave > | > int=000d err= efl=00030202 eip= > eax=097c ebx= ecx=0001 edx=1801 > esi= edi= ebp= esp=0402 > cs= ds= es=9eb5 fs= gs= ss=9e42 > cs:eip=00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 > ss:esp=4a 91 00 00 02 02 00 00-08 00 02 02 00 00 07 00 > 00 00 00 00 00 00 7c 00-00 00 54 48 09 00 78 66 > BTX halted > > The AMIBIOS Date is 10/10/94 and the release date is 05/06/96. I don't > think it's possible to update this thing. > > Sometimes the machine keeps rebooting and others it just hangs. Any > workaround? Does this box work ok with a 4.x release CD? It may be your RAM. The Warning message is kind of weird. It seems you were probably in the BIOS trying to read some bits off of disk and the BIOS headed off to lala-land. -- John Baldwin <[EMAIL PROTECTED]> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ata broken on Thinkpad A22m
On Fri, 10 Oct 2003 08:37:41 -0700 (PDT) Brian Buchanan wrote:
> After updating to yesterday's -CURRENT, my IBM Thinkpad A22m stoped
> booting. It hangs at:
>
> GEOM: create disk ad0 dp=0xc3ded670
> ad0: 38154MB [77520/16/63] at ata0-master UDMA33
> ata1: resetting devices ..
> done
>
I had the same problem on my HP XT6050 laptop. This patch solved the problem
for me.
--- ata-queue.c.1.7 Tue Oct 7 16:38:46 2003
+++ ata-queue.c Fri Oct 10 09:28:56 2003
@@ -316,7 +316,7 @@
{
/* clear timeout etc */
request->timeout_handle.callout = NULL;
-#if 0
+
/* call interrupt to try finish up the command */
request->device->channel->hw.interrupt(request->device->channel);
@@ -327,7 +327,6 @@
ata_cmd2str(request));
return;
}
-#endif
/* if this was a DMA request stop the engine to be on the safe side */
if (request->flags & ATA_R_DMA) {
--
Thomas Mueller [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ata broken on Thinkpad A22m
After updating to yesterday's -CURRENT, my IBM Thinkpad A22m stoped booting. It hangs at: GEOM: create disk ad0 dp=0xc3ded670 ad0: 38154MB [77520/16/63] at ata0-master UDMA33 ata1: resetting devices .. done The console is still alive, but the kernel appears to be waiting for an interrupt that will never come. My Thinkpad is known to have a buggy ata controller which (sometimes? all the time?) fails to send interrupts for ata1-slave, and causes various revisions of the kernel to complain in various places. -CURRENT used to complain at boot, and the most recent working kernel I have complains at shutdown. The most recent working kernel, from earlier this week: GEOM: create disk ad0 dp=0xc3ded670 ad0: 38154MB [77520/16/63] at ata0-master UDMA33 acd0: DVDROM at ata1-master PIO4 Mounting root from ufs:/dev/ad0s3a at shutdown: syncing disks, buffers remaining... 3 3 1 1 done Uptime: 2m21s ata1-slave: WARNING - FLUSHCACHE recovered from missing interrupt -- Brian Buchanan, CISSP [EMAIL PROTECTED] -- FreeBSD - The Power to Servehttp://www.freebsd.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ATAng doesn't boot on my notebook - panic
В ср, 08.10.2003, в 12:04, Soren Schmidt пишет: > > Does not help, another panic in ad_attach: > > ARGH, try this instead: Yes, it helps, thank you. > -Søren -- Vladimir B. Grebenschikov <[EMAIL PROTECTED]> SWsoft Inc. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
howto debug acpi_thermal on Dell 2500 servers
Hi, I am trying to figure out how to use ACPI to get thermal info on Dell 2500 servers. I have compiled acpi into the kernel (see below for problems with acpi as module with ACPI_DEBUG in make.conf). I can't seem to get any addtional info from acpi. Do I need a debug kernel? Do I have to have more options in my kernel config? Is someone already doing (done?) this and I shouldn't bother to try and debug it? Thanks, Ken I tried to include any relevant details that I saw in other messages in the archives: I seemed to get more info without ACPI_DEBUG on and the acpi as a KLD. sidenote: kernel would not load the acpi.ko file if I made it with ACPI_DEBUG=1 in make.conf. (See way below) now I am using: device acpi options ACPI_DEBUG I tried adding OPTIONS ACPI_VERBOSE but it gives 'unknown option "ACPI_VERBOSE" ' My loader.conf is as follows: riker# cat /boot/loader.conf hw.acpi.debug=1 hw.acpi.verbose = 1 debug.acpi.layer = "ACPI_ALL_COMPONENTS ACPI_FAN ACPI_THERMAL" debug.acpi.level = "ACPI_LV_WARN ACPI_LV_ERROR ACPI_LV_OBJECTS" sysctl utput --- riker# sysctl -a | grep acpi acpisem17 3K 3K 17 64,128 acpica 1357 175K177K15193 16,64,128,256,512,1024 acpidev44 1K 1K 44 16 debug.acpi.acpi_ca_version: 0x20030619 debug.acpi.layer: ACPI_UTILITIES ACPI_HARDWARE ACPI_EVENTS ACPI_TABLES ACPI_NAMESPACE ACPI_PARSER ACPI_DISPATCHER ACPI_EXECUTER ACPI_RESOURCES ACPI_CA_DEBUGGER ACPI_OS_SERVICES ACPI_CA_DISASSEMBLER ACPI_ALL_COMPONENTS ACPI_EC ACPI_AC_ADAPTER ACPI_THERMAL ACPI_FAN debug.acpi.level: ACPI_LV_ERROR ACPI_LV_WARN ACPI_LV_OBJECTS debug.acpi.semaphore_debug: 0 hw.acpi.supported_sleep_state: S4 S5 hw.acpi.power_button_state: S5 hw.acpi.sleep_button_state: S1 hw.acpi.lid_switch_state: S1 hw.acpi.standby_state: S1 hw.acpi.suspend_state: S3 hw.acpi.sleep_delay: 5 hw.acpi.s4bios: 0 hw.acpi.verbose: 1 hw.acpi.disable_on_poweroff: 1 machdep.acpi_timer_freq: 3579545 machdep.acpi_root: 1039488 riker# Hope you can help: more details below See below for output of dmesg | grep acpi. -- riker# dmesg | grep acpi acpi0: on motherboard acpi0: Power Button (fixed) acpi_cpu0: on acpi0 acpi_cpu1: on acpi0 pcib0: on acpi0 fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio1 port 0x2f8-0x2ff irq 3 on acpi0 ppc0 port 0x778-0x77f,0x378-0x37f irq 7 drq 1 on acpi0 pcib1: on acpi0 pcib3: on acpi0 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 riker#riker# pciconf -lv [EMAIL PROTECTED]:0:0:class=0x06 card=0x chip=0x00081166 rev=0x23 hdr=0x00 vendor = 'Reliance Computer Corp./ServerWorks' device = 'NB6536 (CNB20-HE) Hostbridge & MCH, bus/dev/func 0/0/0' class= bridge subclass = HOST-PCI [EMAIL PROTECTED]:0:1:class=0x06 card=0x chip=0x00081166 rev=0x01 hdr=0x00 vendor = 'Reliance Computer Corp./ServerWorks' device = 'NB6536 (CNB20-HE) Hostbridge & MCH, bus/dev/func 0/0/0' class= bridge subclass = HOST-PCI [EMAIL PROTECTED]:0:2:class=0x06 card=0x chip=0x00061166 rev=0x01 hdr=0x00 vendor = 'Reliance Computer Corp./ServerWorks' device = 'NB6536 (CNB20-HE) Host Bridge, function 2 and function 3' class= bridge subclass = HOST-PCI [EMAIL PROTECTED]:0:3:class=0x06 card=0x chip=0x00061166 rev=0x01 hdr=0x00 vendor = 'Reliance Computer Corp./ServerWorks' device = 'NB6536 (CNB20-HE) Host Bridge, function 2 and function 3' class= bridge subclass = HOST-PCI --- way below problems loading acpi as module with debug Normal boot riker# kldstat Id Refs AddressSize Name 17 0xc040 5aba64 kernel 21 0xc09ac000 4ceacacpi.ko 31 0xc890f000 19000linux.ko riker# buildkernel and installkernel with ACPI_DEBUG=1 %cat /etc/make.conf # -- use.perl generated deltas -- # # Created: Fri Apr 4 09:20:59 2003 # Setting to use base perl from ports: PERL_VER=5.6.1 PERL_VERSION=5.6.1 PERL_ARCH=mach NOPERL=yo NO_PERL=yo NO_PERL_WRAPPER=yo KERNCONF=ICARZ CPUTYPE=i686 CFLAGS= -O -pipe CXXFLAGS+= -fmemoize-lookups -fsave-memoized ACPI_DEBUG=1 result: % %kldstat Id Refs AddressSize Name 15 0xc040 5aba64 kernel 21 0xc88ca000 19000linux.ko %dmesg | grep acpi Preloaded elf module "/boot/kernel/acpi.ko" at 0xc0a351f4. KLD file acpi.ko - could not finalize loading - Ken Menzel ICQ# 9325188 www.icarz.com [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL
Re: kerberos5 ===> kerberos5/lib/libhdb
On Fri, Oct 10, 2003 at 06:44:25PM +0700, Dikshie wrote: > > > ===> kerberos5 > cd /usr/src/kerberos5; /usr/obj/usr/src/make.i386/make buildincludes; > /usr/obj/usr/src/make.i386/make installincludes > ===> kerberos5/doc > ===> kerberos5/lib > ===> kerberos5/lib/libroken > ./make-roken > tmp.h ; if [ -f roken.h ] && cmp -s tmp.h roken.h ; then rm -f tmp.h > ; else rm -f roken.h; mv tmp.h roken.h; fi > ===> kerberos5/lib/libvers > ===> kerberos5/lib/libasn1 > ./asn1_compile > /usr/src/kerberos5/lib/libasn1/../../../crypto/heimdal/lib/asn1/k5.asn1 krb5_asn1 > test -e /usr/obj/usr/src/kerberos5/lib/libasn1/asn1_err.et || ln -sf > /usr/src/kerberos5/lib/libasn1/../../../crypto/heimdal/lib/asn1/asn1_err.et > compile_et asn1_err.et > ===> kerberos5/lib/libhdb > make: don't know how to make hdb_asn1.h. Stop > *** Error code 2 > > Stop in /usr/src/kerberos5/lib. > *** Error code 1 > > thanks ! My g00f ... fixed, thanks! Cheers, -- Jacques Vidrine . NTT/Verio SME . FreeBSD UNIX . Heimdal [EMAIL PROTECTED] . [EMAIL PROTECTED] . [EMAIL PROTECTED] . [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Sched_Ule
Il Ven, 2003-10-10 alle 04:54, Jonathan E Fosburgh ha scritto: > On Thursday 09 October 2003 08:16 pm, Evan Dower wrote: > > How many of the people experiencing SCHED_ULE related problems (primarily > > lagging) are also using nvidia-driver? I know I am, and I'm pretty sure > > Arjan is. Could there be a connection? > > I switched back to the XFree86 nv driver earlier today and still have trouble. > moused is running and it is a PS/2 mouse. Same situation here. -- Rionda aka Matteo Riondato G.U.F.I Staff Member (http://www.gufi.org) BSD-FAQ-it Main Developer (http://www.gufi.org/~rionda) GPG key at: http://www.riondabsd.net/riondagpg.asc Sent from: kaiser.sig11.org running FreeBSD-5.1-CURRENT ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
BTX Halted (AMD 5x86 133MHz)
Hi, I've got the following message while trying to boot 5.1-RELEASE on a AMD 586 133MHz, 24MB and a 850MB hard disk that I was using in another machine: BTX loader 1.00 BTX version is 1.01 Console: internal video/keyboard BIOS drive C: is disk0 BIOS 640kB/23552kB avaiable memory FreeBSD/i386 bootstrap loader, Revision 1.1 ([EMAIL PROTECTED], Thu Jan 5 00:52:26 GMT 2003) Warning -- Unmatched control word: leave | int=000d err= efl=00030202 eip= eax=097c ebx= ecx=0001 edx=1801 esi= edi= ebp= esp=0402 cs= ds= es=9eb5 fs= gs= ss=9e42 cs:eip=00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ss:esp=4a 91 00 00 02 02 00 00-08 00 02 02 00 00 07 00 00 00 00 00 00 00 7c 00-00 00 54 48 09 00 78 66 BTX halted The AMIBIOS Date is 10/10/94 and the release date is 05/06/96. I don't think it's possible to update this thing. Sometimes the machine keeps rebooting and others it just hangs. Any workaround? -- Giovanni P. Tirloni Fingerprint: 8C3F BEC5 79BD 3E9B EDB8 72F4 16E8 BA5E D031 5C26 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ULE Update
Thanks for this update, I've been trying to make a SCHED_ULE enabled kernel work here for a few days now, thinking it would be about time to test it again (last time was ~2 months ago), but ata issues have kept me from booting it successfully. Now I know for sure I can give it atleast another week - maybe both ata and sched issues can be ironed out by then ;) Thanks for your efforts. /Eirik On Fri, 10 Oct 2003 04:01:28 -0400 (EDT) Jeff Roberson <[EMAIL PROTECTED]> wrote: > I have reproduced the lagging mouse issue on my laptop. I tried > moused to no effect. Eventually, I grudgingly installed kde and > immediately started encountering problems with mouse lag. It would > seem that twm was not stressing my machine in the same ways that kde > is. ;-) > > I suspect a problem with IPC. I will know more soon. > > There have also been a few reports of problems related to nice. I was > able to reproduce some awkward behavior but I have nothing conclusive > yet. > > There is still a known issue with hyperthreading. I'm waiting on some > of john baldwin's work to fix this. If you halt logical cpus your > machine will hang. > > Expect some resolution on the ULE problems within a week or so. > Thanks for the detailed bug reports everyone. > > Cheers, > Jeff > > ___ > [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]"
kerberos5 ===> kerberos5/lib/libhdb
===> kerberos5 cd /usr/src/kerberos5; /usr/obj/usr/src/make.i386/make buildincludes; /usr/obj/usr/src/make.i386/make installincludes ===> kerberos5/doc ===> kerberos5/lib ===> kerberos5/lib/libroken ./make-roken > tmp.h ; if [ -f roken.h ] && cmp -s tmp.h roken.h ; then rm -f tmp.h ; else rm -f roken.h; mv tmp.h roken.h; fi ===> kerberos5/lib/libvers ===> kerberos5/lib/libasn1 ./asn1_compile /usr/src/kerberos5/lib/libasn1/../../../crypto/heimdal/lib/asn1/k5.asn1 krb5_asn1 test -e /usr/obj/usr/src/kerberos5/lib/libasn1/asn1_err.et || ln -sf /usr/src/kerberos5/lib/libasn1/../../../crypto/heimdal/lib/asn1/asn1_err.et compile_et asn1_err.et ===> kerberos5/lib/libhdb make: don't know how to make hdb_asn1.h. Stop *** Error code 2 Stop in /usr/src/kerberos5/lib. *** Error code 1 thanks ! -dikshie- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ULE Update
Jeff Roberson wrote: I have reproduced the lagging mouse issue on my laptop. I tried moused to no effect. Eventually, I grudgingly installed kde and immediately started encountering problems with mouse lag. It would seem that twm was not stressing my machine in the same ways that kde is. ;-) I have a Tyan S1832DL with dual PII 350s, 384 MB of ram, Adaptec 2940 scsi controler w/Seagate ST39102LW disk, and a voodoo 3 3000. I've been running ULE for a while now and have noticed that I don't have to be in X to see the scheduling problem, I don't even have to be in multi-user mode to notice. Typing and executing commands in single user mode I can see the scheduling is not fluid. For instance, I can type in and execute the sync command so fast that I'm finished before the characters actually get printed and the prompt returns. I don't think it's ever been more than a one second delay, but sometimes it's been close. I suspect a problem with IPC. I will know more soon. There have also been a few reports of problems related to nice. I was able to reproduce some awkward behavior but I have nothing conclusive yet. There is still a known issue with hyperthreading. I'm waiting on some of john baldwin's work to fix this. If you halt logical cpus your machine will hang. Expect some resolution on the ULE problems within a week or so. Thanks for the detailed bug reports everyone. Your dedication to FreeBSD is outstanding, I always look forward to seeing your name in the cvs reports. Thanks for your efforts, Jeff. Cheers, Jeff Pete... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ULE Update
I have reproduced the lagging mouse issue on my laptop. I tried moused to no effect. Eventually, I grudgingly installed kde and immediately started encountering problems with mouse lag. It would seem that twm was not stressing my machine in the same ways that kde is. ;-) I suspect a problem with IPC. I will know more soon. There have also been a few reports of problems related to nice. I was able to reproduce some awkward behavior but I have nothing conclusive yet. There is still a known issue with hyperthreading. I'm waiting on some of john baldwin's work to fix this. If you halt logical cpus your machine will hang. Expect some resolution on the ULE problems within a week or so. Thanks for the detailed bug reports everyone. Cheers, Jeff ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Sched_Ule
Hi ! I have a Matrox G550. No DRI or other specials. PS/2 mouse. No moused. UP machine. The mouse stutters under compilation load (in X). I'll give moused a try and look whether the behaviour is the same on the console, but I doubt it. I suspect this thing is rendering related. Cheers Peter -- <[EMAIL PROTECTED]> Campus der Max-Planck-Institute Tübingen Netzwerk- und Systemadministration Tel: +49 7071 601 598 Fax: +49 7071 601 616 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Sched_Ule
Evan Dower wrote: How many of the people experiencing SCHED_ULE related problems (primarily lagging) are also using nvidia-driver? I know I am, and I'm pretty sure Arjan is. Could there be a connection? No, I have an ATI Radeon now. The problem seems to appear independently of the video driver used. Arjan -- Evan Dower Undergraduate, Computer Science University of Washington Public key: http://students.washington.edu/evantd/pgp-pub-key.txt Key fingerprint = D321 FA24 4BDA F82D 53A9 5B27 7D15 5A4F 033F 887D ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
