Re: Periodic
>From: "Andryan" <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Subject: Periodic >Date: Fri, 22 Feb 2002 23:01:11 +0700 > >Hmmpf.. >After I have upgraded to 4.5-STABLE successfully, my periodic output seems >not to be working. >Usually I got daily email, but now not even one.. >I tried to run them manually, no luck. >Anyone got an idea? =/ > Did you mergemaster during the upgrade? Are you still getting other emails? I accidentally blew away my aliases file once during a mergemaster becasue i was a little too quick with my fingers :). Otherwise daily is running fine on my 4.5-Stable boxes.. --Larry _ Join the worlds largest e-mail service with MSN Hotmail. http://www.hotmail.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
frequent page fault panic
Hi, I'm getting the same panic repeatedly on -STABLE. The time length between panic's varies between about half an hour and several days. It doesn't appear to be related to system load. The machine is used as a Desktop - with a few things running. I put some load on the machine (average of around 40.5 or so and lots of swapping) for an hour. The machine was fine. That also makes me doubtful that this hardware related. I have been unable to determine any particular pattern for the occurance of these panics. There doesn't seem to be a trigger that I've noticed. => Fatal trap 12: page fault while in kernel mode fault virtual address = 0xc0bf9953 fault code = supervisor write, page not present instruction pointer = 0x8:0xc02842ff stack pointer = 0x10:0xcca0ff38 frame pointer = 0x10:0xcca0ff44 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 3 current process = 67995 (XFree86) interrupt mask = net trap number = 12 panic: page fault <= => (gdb) bt #0 0xc0131fa2 in dumpsys () #1 0xc0131d6c in boot () #2 0xc01321b9 in panic () #3 0xc01dafac in trap_fatal () #4 0xc01dac41 in trap_pfault () #5 0xc01da793 in trap () #6 0xc02842ff in ?? () #7 0xc02844ae in ?? () #8 0xc0284af1 in ?? () #9 0xc01ddeb3 in intr_mux () #10 0x87401af in ?? () #11 0x8740e35 in ?? () #12 0x8741d5e in ?? () #13 0x878a9b6 in ?? () #14 0x81616c5 in ?? () #15 0x816a4a7 in ?? () #16 0x816851e in ?? () #17 0x878afea in ?? () #18 0x81618e8 in ?? () #19 0x816a524 in ?? () #20 0x816b937 in ?? () #21 0x816ba21 in ?? () #22 0x80ac801 in ?? () #23 0x80bbb19 in ?? () #24 0x806a155 in ?? () <= I'm currently rebuilding my kernel with debug sumbols so I can provide a more meaningful backtrace. I shall try and find out the problem, but my skills are still immature. I can provide dmesg and other information on request. I'm also not subscribed to freebsd-stable, so please keep me in the CC: chain. Thank You -- Dominic To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: frequent page fault panic
What version of X are you using? 3.3.6 or 4.x? -- Matthew Emmerton || [EMAIL PROTECTED] GSI Computer Services || http://www.gsicomp.on.ca On Fri, 22 Feb 2002, Dominic Marks wrote: > Hi, > > I'm getting the same panic repeatedly on -STABLE. The time length > between panic's varies between about half an hour and several days. It > doesn't appear to be related to system load. The machine is used as a > Desktop - with a few things running. I put some load on the machine > (average of around 40.5 or so and lots of swapping) for an hour. The > machine was fine. That also makes me doubtful that this hardware > related. I have been unable to determine any particular pattern for > the occurance of these panics. There doesn't seem to be a trigger that > I've noticed. > > => > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0xc0bf9953 > fault code= supervisor write, page not present > instruction pointer = 0x8:0xc02842ff > stack pointer = 0x10:0xcca0ff38 > frame pointer = 0x10:0xcca0ff44 > code segment = base 0x0, limit 0xf, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 3 > current process = 67995 (XFree86) > interrupt mask= net > trap number = 12 > panic: page fault > <= > > => > (gdb) bt > #0 0xc0131fa2 in dumpsys () > #1 0xc0131d6c in boot () > #2 0xc01321b9 in panic () > #3 0xc01dafac in trap_fatal () > #4 0xc01dac41 in trap_pfault () > #5 0xc01da793 in trap () > #6 0xc02842ff in ?? () > #7 0xc02844ae in ?? () > #8 0xc0284af1 in ?? () > #9 0xc01ddeb3 in intr_mux () > #10 0x87401af in ?? () > #11 0x8740e35 in ?? () > #12 0x8741d5e in ?? () > #13 0x878a9b6 in ?? () > #14 0x81616c5 in ?? () > #15 0x816a4a7 in ?? () > #16 0x816851e in ?? () > #17 0x878afea in ?? () > #18 0x81618e8 in ?? () > #19 0x816a524 in ?? () > #20 0x816b937 in ?? () > #21 0x816ba21 in ?? () > #22 0x80ac801 in ?? () > #23 0x80bbb19 in ?? () > #24 0x806a155 in ?? () > <= > > I'm currently rebuilding my kernel with debug sumbols so I can > provide a more meaningful backtrace. > > I shall try and find out the problem, but my skills are still > immature. I can provide dmesg and other information on request. I'm > also not subscribed to freebsd-stable, so please keep me in the CC: > chain. > > Thank You > -- > Dominic > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: frequent page fault panic
On Fri, Feb 22, 2002 at 01:03:41PM -0500, Matthew Emmerton wrote: > > What version of X are you using? 3.3.6 or 4.x? 4.1 built from ports. > -- > Matthew Emmerton || [EMAIL PROTECTED] > GSI Computer Services || http://www.gsicomp.on.ca > > On Fri, 22 Feb 2002, Dominic Marks wrote: > > > Hi, > > > > I'm getting the same panic repeatedly on -STABLE. The time length > > between panic's varies between about half an hour and several days. It > > doesn't appear to be related to system load. The machine is used as a > > Desktop - with a few things running. I put some load on the machine > > (average of around 40.5 or so and lots of swapping) for an hour. The > > machine was fine. That also makes me doubtful that this hardware > > related. I have been unable to determine any particular pattern for > > the occurance of these panics. There doesn't seem to be a trigger that > > I've noticed. > > > > => > > Fatal trap 12: page fault while in kernel mode > > fault virtual address = 0xc0bf9953 > > fault code = supervisor write, page not present > > instruction pointer = 0x8:0xc02842ff > > stack pointer = 0x10:0xcca0ff38 > > frame pointer = 0x10:0xcca0ff44 > > code segment= base 0x0, limit 0xf, type 0x1b > > = DPL 0, pres 1, def32 1, gran 1 > > processor eflags= interrupt enabled, resume, IOPL = 3 > > current process = 67995 (XFree86) > > interrupt mask = net > > trap number = 12 > > panic: page fault > > <= > > > > => > > (gdb) bt > > #0 0xc0131fa2 in dumpsys () > > #1 0xc0131d6c in boot () > > #2 0xc01321b9 in panic () > > #3 0xc01dafac in trap_fatal () > > #4 0xc01dac41 in trap_pfault () > > #5 0xc01da793 in trap () > > #6 0xc02842ff in ?? () > > #7 0xc02844ae in ?? () > > #8 0xc0284af1 in ?? () > > #9 0xc01ddeb3 in intr_mux () > > #10 0x87401af in ?? () > > #11 0x8740e35 in ?? () > > #12 0x8741d5e in ?? () > > #13 0x878a9b6 in ?? () > > #14 0x81616c5 in ?? () > > #15 0x816a4a7 in ?? () > > #16 0x816851e in ?? () > > #17 0x878afea in ?? () > > #18 0x81618e8 in ?? () > > #19 0x816a524 in ?? () > > #20 0x816b937 in ?? () > > #21 0x816ba21 in ?? () > > #22 0x80ac801 in ?? () > > #23 0x80bbb19 in ?? () > > #24 0x806a155 in ?? () > > <= > > > > I'm currently rebuilding my kernel with debug sumbols so I can > > provide a more meaningful backtrace. > > > > I shall try and find out the problem, but my skills are still > > immature. I can provide dmesg and other information on request. I'm > > also not subscribed to freebsd-stable, so please keep me in the CC: > > chain. > > > > Thank You > > -- > > Dominic > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-stable" in the body of the message > > > -- Dominic To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Periodic-ifying the Daily Security Check
Crist J. Clark <[EMAIL PROTECTED]> types: > Now that 4.5-RELEASE is well past, I am considering MFC'ing the new > periodic(8) structure for doing the daily security checks. The firstURL told me the important thing - that if you haven't changed the scripts, the change would be transparent and you can delete /etc/security. I think putting that directly in the note in UPDATING would be worthwhile. http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Periodic-ifying the Daily Security Check
On Fri, Feb 22, 2002 at 03:57:24PM -0600, Mike Meyer wrote: > Crist J. Clark <[EMAIL PROTECTED]> types: > > Now that 4.5-RELEASE is well past, I am considering MFC'ing the new > > periodic(8) structure for doing the daily security checks. > > The firstURL told me the important thing - that if you haven't changed > the scripts, the change would be transparent and you can delete > /etc/security. I think putting that directly in the note in UPDATING > would be worthwhile. imp just put a URL to the archived HEADS UP mail when he put it in -CURRENT's UPDATING, http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/src/UPDATING?rev=1.186&content-type=text/plain -- Crist J. Clark | [EMAIL PROTECTED] | [EMAIL PROTECTED] http://people.freebsd.org/~cjc/| [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
ZIP drive
I have a IOMEGA ZIP ide drive that I used to be able to access via mtools
or mount_msdos just fine. Now, I can't.
I have a fairly recently built kernel:
FreeBSD 4.4-RC #0: Wed Feb 6 10:49:07 PST 2002
which detects the drive:
afd0: 96MB [96/64/32] at ata1-slave using PIO3
This is different from awhile ago:
afd0: 0MB [0/64/32] at ata1-slave using PIO3
I don't use the drive very often, so I don't know if the change resulted
in not being able to access the drive.
The error occurs on open. If I do open("/dev/afd0a", O_RDONLY), I get
errno of 22 (EINVAL). The 'open' man page says this only results from
an illegal combination flags -- not the case here. No message gets
output to the console so I don't think the hardware is bad. The drive
spins when I do the open call and windows can see it okay.
I checked the web site for bug reports and did not find anything.
Does anyone know what is going on?
Thanks,
Tom Proett
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Re: crashes on 4.5-RELEASE
Looks like I'm not the only one seeing this: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/22494 http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/31710 http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/30952 I suspect these are all the same problem. -jan- -- Jan L. Peterson <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: crashes on 4.5-RELEASE
Just another datapoint... I turned off softupdates. The machine crashed in the xl code. Trace from DDB: xl_newbuf(c15b8000,c15b844c) xl_rxeof(c15b8000) xl_intr(c15b8000,660400,c690a834,1,cdf1fd48) intr_mux(c0e356c0,0,c6900010,10,c0190010) Xresume10() --- interrupt, eip = 0xc02afd22, esp = 0xcdf1fd08, ebp = 0xcdf1fd48 -- vec10(ce0b7000,8,0,0,0)) nfs_getcacheblk(ce0b7000,8,0,cdef1100,ce0b7000) nfs_write(cdf1fe64,c17d45c0,cdef1100,1000,c031cd00) vn_write(c17d45c0,cdf1fed4,c17ae200,0,cdef1100) dofilewrite(cdef1100,c17d45c0,4,8053f60,1000) write(cdef1100,cdf1ff80,1000,6,4) syscall(2f,2f,2f,4,6) Xint0x80_syscall() pretty consistent now... I can make it crash in less than five minutes after booting. -jan- -- Jan L. Peterson <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
crashes on 4.5-RELEASE
Okay, I'm pretty sure this isn't a hardware problem now. I was seeing periodic crashes with 4.5-RELEASE on a new laptop I was building. Various posts on this list convinced me that I had a hardware problem. I tried swapping out the RAM and it seemed to crash less (and in a different place). Crashes after swapping the RAM were always in the xl routines. So, being convinced that I had a hardware problem (mother board or cpu or something like that), I swapped out the *entire machine*. I'm still seeing the crashes. So, I have /usr/ports nfs mounted from another freebsd box. I cd /usr/ports/misc/instant-workstation; make install The machine panics (sometimes right away, sometimes after several minutes). Here's the panic message: Fatal trap 12: page fault while in kernel mode fault virtual address = 0xc0fcec39 fault code = supervisor write, page not present instruction pointer = 0x8:0xc0205243 stack pointer = 0x10:0xcde4fbd0 frame pointer = 0x10:0xcde4fbe4 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 = 80 (nfsiod) interrupt mask = net tty kernel: type 12 trap, code=0 Stopped at nfs_realign+0xdb: incb0(%eax,%edx,1) db> trace nfs_realign(c0ea5200,14,0,1,cdeb0cc0) at nfs_realign+0xdb nfs_receive(c17ca280,cde4fc6c,cde4fc70,0,1) at nfs_receive+0x45d nfs_reply(c17ca280,cde4fdc0,0,20,10) at nfs_reply+0x45 nfs_request(ce0b3c80,c0e5bf00,6,0,c16dcc80) at nfs_request+0x39a nfs_readrpc(ce0b3c80,cde4fdc0,c16dcc80,c68a25b8,cdeb0cc0) at nfs_readrpc+0x538 nfs_doio(c68a25b8,c16dcc80,0) at nfs_doio+0x14b nfssvc_iod(cc379740,cc379740,2,cde4ff80,c37d880) at nfssvc_iod+0x1c2 nfssvc(cc379740,cde4ff80,2,0,bfbffdd8) at nfssvc+0x6f syscall2(2f,2f,2f,bfbffdd8,0) at syscall2+0x1f5 Xint0x80_syscall() at Xint0x80_syscall+0x25 db> FYI, this machine is an HP Omnibook 6000. It has the "xl" ethernet built in and this is the interface I'm using. In this particular case, my entire sequence of events was: boot login su mount /usr/ports (from the nfs server) cd /usr/ports/misc/instant-workstation make clean make install Just had another crash, panic this time was again supervisor read, page not present, but current process was syncer. Traceback shows: malloc(...) initiate_write_inodeblock(...) softdep_disk_io_initiation(...) spec_strategy(...) bwrite(...) vop_stdbwrite(...) vop_defaultop(...) vfs_bio_awrite(...) spec_fsync(...) sched_sync(...) fork_trampoline(...) I do have soft updates turned on on the single / filesystem on this box. Should I turn them off? I would be happy to supply my kernel config file to anyone interested. P.S. I also have the problem with these Omnibooks that if you tell them to "reboot" (or "halt" followed by pressing any key to reboot), they hang in a weird kind of half power on state. The display goes black (the backlight turns off), but if you shine a flashlight on the LCD, you can still see text there. The Power light on the front does not turn off, and the machine still generates plenty of heat, but the cpu cooling fan will not turn itself on. Any suggestions for that? -jan- -- Jan L. Peterson <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: frequent page fault panic
On Fri, Feb 22, 2002 at 05:49:46PM +, Dominic Marks wrote: > Hi, > > I'm getting the same panic repeatedly on -STABLE. The time length > between panic's varies between about half an hour and several days. It > doesn't appear to be related to system load. The machine is used as a > Desktop - with a few things running. I put some load on the machine > (average of around 40.5 or so and lots of swapping) for an hour. The > machine was fine. That also makes me doubtful that this hardware > related. Hardware failures can be very weird and apparently non-deterministic. In the absence of a better explanation, don't be quick to discount them. Kris msg41841/pgp0.pgp Description: PGP signature
Re: Is vmnet broken in 4.5?
Hey Eugene, With the exception that I *can* ping the vmnet1 interface but the ICMP echo replies from FreeBSD never make it back to the VMware hosted OS, and neither side can get the ARP address of the other, I see very much the same symptoms as you. I'm running 4.4-STABLE RC2 (I'm waiting for XFree86-4.2.0 to make it back into ports before I update again, as this version works for me). All my ports and everything in the OS are at the same level (buildworld, buildkernel, portupgrade etc). Everything's working great AFAICS, with the minor exception of this. Cheers, AS > Hi. > > My vmware2 use netgraph bridge to access the network. Under 4.4 all work > fine. But after upgrade to 4.5 I got some trouble. I can't see my FBSD box > under vmware, but all other boxes in network work fine. I can't ping from > FBSD box to vmnet1 address. > > It seems, vmware guest OS can't get arp address of FBSD. > > + > xl0 > 172.17.1.206/16 <--> 172.17/16 (DHCP server, Internet, etc) > | > FBSD 4.5| > ++ > vmnet1 > 172.17.240.241/16 <--> 172.17.5.121/16 (vmware2, win98se) | > -+ > > Some usefull info: > > Win98SE (guest OS) use DHCP server for assigning IP address, DNSes & > default gateway. > > - > box$ ping 172.17.1.206 > PING 172.17.1.206 (172.17.1.206): 56 data bytes > 64 bytes from 172.17.1.206: icmp_seq=0 ttl=64 time=0.162 ms > > - > box$ ping 172.17.240.241 > PING 172.17.240.241 (172.17.240.241): 56 data bytes > ping: sendto: Host is down > > and in the same time we can see next > > box# tcpdump -i xl0 host 172.17.240.241 > tcpdump: listening on xl0 > arp who-has 172.17.240.241 tell 172.17.1.206 > arp who-has 172.17.240.241 tell 172.17.1.206 > . > > - > c:\Program files\FAR> ping 172.17.1.206 > pinging 172.17.1.206 > timeout > ... > timeout > > and in the same time > > box# tcpdump -i vmnet1 host 172.17.5.121 > tcpdump: listening on vmnet1 > 172.17.1.206 > 172.17.5.121: icmp: echo reply > 172.17.1.206 > 172.17.5.121: icmp: echo request > 172.17.1.206 > 172.17.5.121: icmp: echo request > 172.17.1.206 > 172.17.5.121: icmp: echo request > 172.17.1.206 > 172.17.5.121: icmp: echo request > 172.17.1.206 > 172.17.5.121: icmp: echo request > 172.17.1.206 > 172.17.5.121: icmp: echo request > 172.17.5.121 > 172.17.1.206: icmp: echo request > 172.17.1.206 > 172.17.5.121: icmp: echo reply > > > > c:\Program files\FAR> ping 172.17.0.1 > > answer, size=32 bytes, time=21ms, TTL=64 > . > > c:\Program files\FAR> ping www.mtu.ru > > pinging 195.34.32.10 > answer, size=32 bytes, time=157ms, TTL=248 > . > > > > box# uname -a > FreeBSD badger.imedia.ru 4.5-RELEASE FreeBSD 4.5-RELEASE #29: Tue Feb 5 > 11:00:19 MSK 2002 > [EMAIL PROTECTED]:/var/devel/CVSUP/src/sys/compile/BADGER i386 > > box# kldstat > Id Refs AddressSize Name > 1 15 0xc010 2873d0 kernel > 21 0xc0388000 542c snd_es137x.ko > 31 0xc038e000 157b4snd_pcm.ko > 41 0xc0f92000 c3000vinum.ko > 51 0xc1088000 7000 linprocfs.ko > 61 0xc1112000 2000 green_saver.ko > 73 0xc11c 15000linux.ko > 81 0xc1115000 2000 rtc.ko > 101 0xc12b6000 4000 if_tap.ko > 121 0xc13d2000 3000 ng_socket.ko > 133 0xc13d8000 9000 netgraph.ko > 151 0xc13e1000 3000 ng_ether.ko > 161 0xc13e4000 4000 ng_bridge.ko > 171 0xc12aa000 9000 vmmon_up.ko > 181 0xc17de000 8000 cd9660.ko > > box# ifconfig -a > xl0: flags=8943 mtu 1500 > options=3 > inet 172.17.1.206 netmask 0x broadcast 172.17.255.255 > atalk 228.127 range 220-230 phase 2 broadcast 0.255 > ether 00:50:da:cd:b2:0e > media: Ethernet autoselect (100baseTX ) > status: active > lp0: flags=8810 mtu 1500 > lo0: flags=8049 mtu 16384 > inet 127.0.0.1 netmask 0xff00 > atalk 0.0 range 0-0 phase 2 > vmnet1: flags=8843 mtu 1500 > inet 172.17.240.241 netmask 0x broadcast 172.17.255.255 > ether 00:bd:e7:14:00:01 > Opened by PID 41162 > > box# netstat -nr -f inet > Routing tables > > Internet: > DestinationGatewayFlagsRefs Use Netif Expire > default172.17.0.1 UGSc 34 75xl0 > 127.0.0.1 127.0.0.1 UH 3 102683lo0 > 172.17 link#1 UC 110xl0 > 172.17.0.1 0:d0:b7:a9:f:f9UHLW 38 5864104xl0 1193 > 172.17.1.206 0:50:da:cd:b2:eUHLW2 1114lo0 > 172.17.5.121 0:bd:e7:da:d5:31 UHLW1 1336xl0762 > 172.17.120.66 link#1 UHLW1 49xl0 > 172.17.124.5 0:50:8b:69:c3:d5 UHLW0 714xl0 1195 > 172.17.124.209 0:d0:b7:a9:37:c8 UHLW15
Re: crashes on 4.5-RELEASE
> FYI, this machine is an HP Omnibook 6000. It has the "xl" ethernet > built in and this is the interface I'm using. I've had one of these for over a year, and I use the network & NFS fairly heavily. It's very stable for me (only remaining niggles on this platform for me were sound and xl0 post-resume - but these were completely addressed for me by a couple of commits just pre-4.5-RELEASE). > I do have soft updates turned on on the single / filesystem on this > box. Should I turn them off? They don't cause me any problems (in fact quite the opposite, I think), I've been running them for quite some time. Never caused a single funny for me.. > I would be happy to supply my kernel config file to anyone interested. I'd be happy to provide you with mine, this might be quicker :) > P.S. I also have the problem with these Omnibooks that if you tell them > to "reboot" (or "halt" followed by pressing any key to reboot), they > hang in a weird kind of half power on state. The display goes black > (the backlight turns off), but if you shine a flashlight on the LCD, > you can still see text there. The Power light on the front does not > turn off, and the machine still generates plenty of heat, but the cpu > cooling fan will not turn itself on. Any suggestions for that? Ahh yes, everything in this area used to work fine (including 'shutdown -p'), but broke after Warner made the PCI-routing changes for PCCARD. He can reproduce it with his hardware, and it's not a real big thing anyway (plus he's doing some good work *waves*, don't wanna distract him with trifles).. Just 'halt' the machine, and use the little power key in the top-left corner when it says to "Press Any Key". It'll startup clean. Cheers, AS msg41843/pgp0.pgp Description: PGP signature
Re: crashes on 4.5-RELEASE
I have a fbsd file server that doesn't crash. The box that crashes is nfs mounting /usr/ports from the server. My thoughts are that there is some interaction in the nfs code with the xl driver. -jan- -- Jan L. Peterson <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
