Re: Lots of kernel core dumps
On Monday 24 March 2003 11:18, Daniela wrote: On Sunday 23 March 2003 20:20, Wes Peters wrote: The reason for creating the 5.0 release is to make it easy for more developers and testers to jump onto the 5.x bandwagon by giving them a known (relatively) good starting point. Quite a number of problems have been fixed since 5.0-RELEASE; CURRENT is now generally much more stable, and nobody is going to spend time updating 5.0 which is essentially an early access release. You have to decide for yourself if this machine is too critical to run CURRENT, in which case it's probably best off running STABLE or the latest 4.x release branch, or if you want to update it to CURRENT, follow the CURRENT mailing list, and update again at known stable development points. It looks like right now is pretty good if you want to jump. At any rate, thanks for your tenacity. We really do appreciate the contributions of everyone. Well, it's just a home server. I don't mind a few crashes, but security is important for me. What do you think, should I go back to -stable? FreeBSD is the world's best OS, I want to see it succeeding and I want to help as much as possible. I have two machines at home and run STABLE on my workstation, which is also our 'group server' for the home. I have current on a crash test box that used to be my workstation 6 years ago, a K6/233 I can't imagine not having. If you're similarly hardware-rich, I'd recommend a similar approach. If you have only the one box, I personally would probably run CURRENT and be careful about when to run CVSup. Good luck! -- Where am I, and what am I doing in this handbasket? Wes Peters [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Lots of kernel core dumps
On Tuesday 25 March 2003 08:14, Peter Jeremy wrote: On Mon, Mar 24, 2003 at 08:18:43PM +0100, Daniela wrote: Well, it's just a home server. I don't mind a few crashes, but security is important for me. What do you think, should I go back to -stable? If you're willing to put up with a few crashes _and_ assist with debugging the crashes (eg trying patches) then running -CURRENT would help the Project. One option you could try is to stick with -CURRENT for a month or two and see how it pans out - if you feel it's too painful, downgrade to -STABLE. (I ran -CURRENT on my main workstation for about 3 years - I dropped back to -STABLE midway through last year because -CURRENT happened to strike an extended period of instability and it was causing me too much angst). On the topic of security, you should be aware that -CURRENT is not officially supported and therefore isn't mentioned in security advisories - in general -CURRENT will have security patches applied before -STABLE but you will need to do some detective work if you want to identify the exact time/revision affected. There have also been a couple of instances where security problems only affected -CURRENT. In short, if I keep my eyes open, security isn't bad, right? I'll give -current a try, thanks for your advice. Daniela ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Lots of kernel core dumps
On Mon, Mar 24, 2003 at 08:18:43PM +0100, Daniela wrote: Well, it's just a home server. I don't mind a few crashes, but security is important for me. What do you think, should I go back to -stable? If you're willing to put up with a few crashes _and_ assist with debugging the crashes (eg trying patches) then running -CURRENT would help the Project. One option you could try is to stick with -CURRENT for a month or two and see how it pans out - if you feel it's too painful, downgrade to -STABLE. (I ran -CURRENT on my main workstation for about 3 years - I dropped back to -STABLE midway through last year because -CURRENT happened to strike an extended period of instability and it was causing me too much angst). On the topic of security, you should be aware that -CURRENT is not officially supported and therefore isn't mentioned in security advisories - in general -CURRENT will have security patches applied before -STABLE but you will need to do some detective work if you want to identify the exact time/revision affected. There have also been a couple of instances where security problems only affected -CURRENT. Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Lots of kernel core dumps
On Saturday 22 March 2003 15:10, Daniela wrote: I know, but 5.0-RELEASE was a) A work-in-progress, not a perfect, bug-free release b) A snapshot of 5.0-CURRENT You read the 5.0 Early Adopter's Guide, right? Bugs like this are expected at this stage in the development process, and if you encounter them then you need to either give up on 5.x and go back to 4.x-STABLE, or upgrade to 5.0-CURRENT if they are already fixed there. Kris Yes, I read the Early Adopter's Guide. Is there any way to solve this without upgrading to -current? I want a stable server, of course, but I still want to help the FreeBSD folks to make 5.0 the best release ever. This requires testing to be done. Yes it does, but not on a production machine. We admire your courage and willingness to help, but it's not helping as much as you think. ;^) The reason for creating the 5.0 release is to make it easy for more developers and testers to jump onto the 5.x bandwagon by giving them a known (relatively) good starting point. Quite a number of problems have been fixed since 5.0-RELEASE; CURRENT is now generally much more stable, and nobody is going to spend time updating 5.0 which is essentially an early access release. You have to decide for yourself if this machine is too critical to run CURRENT, in which case it's probably best off running STABLE or the latest 4.x release branch, or if you want to update it to CURRENT, follow the CURRENT mailing list, and update again at known stable development points. It looks like right now is pretty good if you want to jump. At any rate, thanks for your tenacity. We really do appreciate the contributions of everyone. -- Where am I, and what am I doing in this handbasket? Wes Peters [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Lots of kernel core dumps
I know, but 5.0-RELEASE was a) A work-in-progress, not a perfect, bug-free release b) A snapshot of 5.0-CURRENT You read the 5.0 Early Adopter's Guide, right? Bugs like this are expected at this stage in the development process, and if you encounter them then you need to either give up on 5.x and go back to 4.x-STABLE, or upgrade to 5.0-CURRENT if they are already fixed there. Kris Yes, I read the Early Adopter's Guide. Is there any way to solve this without upgrading to -current? I want a stable server, of course, but I still want to help the FreeBSD folks to make 5.0 the best release ever. This requires testing to be done. Daniela To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Lots of kernel core dumps
On Sun, Mar 23, 2003 at 12:10:38AM +0100, Daniela wrote: Yes, I read the Early Adopter's Guide. Is there any way to solve this without upgrading to -current? If you wanted to dig through the CVS commit logs to find the change that fixed this problem (this may be difficult), you could back-port it, but other than that, not really. Kris pgp0.pgp Description: PGP signature
Re: Lots of kernel core dumps
On Sun, 23 Mar 2003 00:10:38 +0100 Daniela [EMAIL PROTECTED] wrote: I know, but 5.0-RELEASE was a) A work-in-progress, not a perfect, bug-free release b) A snapshot of 5.0-CURRENT You read the 5.0 Early Adopter's Guide, right? Bugs like this are expected at this stage in the development process, and if you encounter them then you need to either give up on 5.x and go back to 4.x-STABLE, or upgrade to 5.0-CURRENT if they are already fixed there. Kris Yes, I read the Early Adopter's Guide. Is there any way to solve this without upgrading to -current? I want a stable server, of course, but I still want to help the FreeBSD folks to make 5.0 the best release ever. This requires testing to be done. Daniela current isn't really any less stable than 5.0 release, likely more stable... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Lots of kernel core dumps
Hi all!
I'm getting lots of kernel core dumps on my server.
My RAM is OK, I tested it. Below are more detailed informations.
Any help would be greatly appreciated.
I'm not yet intimate with the kernel, but I'm willing to learn it all.
Thanks in advance.
Daniela
--
# uname -a
FreeBSD CM58-27.liwest.at 5.0-RELEASE-p3 FreeBSD 5.0-RELEASE-p3 #4: Sat Mar 1
18:08:27 CET 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CM58-27
i386
# gdb -k kernel.debug vmcore.1
GNU gdb 5.2.1 (FreeBSD)
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB. Type show warranty for details.
This GDB was configured as i386-undermydesk-freebsd...
panic: bwrite: buffer is not busy???
panic messages:
---
panic: bad pte
syncing disks, buffers remaining... panic: bwrite: buffer is not busy???
Uptime: 4h4m35s
Dumping 511 MB
ata0: resetting devices ..
done
16 32 48[CTRL-C to abort] [CTRL-C to abort] [CTRL-C to abort] 64[CTRL-C to
abort] [CTRL-C to abort] [CTRL-C to abort] 80[CTRL-C to abort] [CTRL-C to
abort] [CTRL-C to abort] [CTRL-C to abort] [CTRL-C to abort] [CTRL-C to
abort] 96[CTRL-C to abort] [CTRL-C to abort] [CTRL-C to abort] [CTRL-C to
abort] [CTRL-C to abort] [CTRL-C to abort] [CTRL-C to abort] [CTRL-C to
abort] [CTRL-C to abort] [CTRL-C to abort] [CTRL-C to abort] [CTRL-C to
abort] 112 128 144[CTRL-C to abort] [CTRL-C to abort] [CTRL-C to abort]
[CTRL-C to abort] 160[CTRL-C to abort] [CTRL-C to abort] [CTRL-C to abort]
[CTRL-C to abort] [CTRL-C to abort] [CTRL-C to abort] [CTRL-C to abort]
176[CTRL-C to abort] [CTRL-C to abort] [CTRL-C to abort] 192[CTRL-C to
abort] [CTRL-C to abort] [CTRL-C to abort] [CTRL-C to abort] [CTRL-C to
abort] [CTRL-C to abort] [CTRL-C to abort] [CTRL-C to abort] [CTRL-C to
abort] 208 224 240 256 272 288 304 320 336 352 368 384 400 416[CTRL-C to
abort] 432 448 464 480 496
---
#0 doadump () at /usr/src/sys/kern/kern_shutdown.c:232
232 dumping++;
(kgdb) where
#0 doadump () at /usr/src/sys/kern/kern_shutdown.c:232
#1 0xc033b5e6 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:364
#2 0xc033b833 in panic () at /usr/src/sys/kern/kern_shutdown.c:517
#3 0xc0379fa2 in bwrite (bp=0xce4d4708) at /usr/src/sys/kern/vfs_bio.c:796
#4 0xc037b55e in vfs_bio_awrite (bp=0xce4d4708)
at /usr/src/sys/kern/vfs_bio.c:1643
#5 0xc0307737 in spec_fsync (ap=0xe0d1cb5c)
at /usr/src/sys/fs/specfs/spec_vnops.c:462
#6 0xc0306ca8 in spec_vnoperate (ap=0x0)
at /usr/src/sys/fs/specfs/spec_vnops.c:126
#7 0xc045fb8d in ffs_sync (mp=0xc40cd800, waitfor=2, cred=0xc150ae80,
td=0xc0584000) at vnode_if.h:612
#8 0xc038d01b in sync (td=0xc0584000, uap=0x0)
at /usr/src/sys/kern/vfs_syscalls.c:138
#9 0xc033b25c in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:273
#10 0xc033b833 in panic () at /usr/src/sys/kern/kern_shutdown.c:517
#11 0xc04b7bbb in pmap_remove_pages (pmap=0xc43a33bc, sva=0, eva=3217031168)
at /usr/src/sys/i386/i386/pmap.c:2937
#12 0xc0326572 in exit1 (td=0xc456f9a0, rv=1) at vm_map.h:228
#13 0xc033ed26 in sigexit () at /usr/src/sys/kern/kern_sig.c:1997
#14 0xc033e97a in postsig (sig=1) at /usr/src/sys/kern/kern_sig.c:1886
#15 0xc035b3da in ast (framep=0xe0d1cd48) at /usr/src/sys/kern/subr_trap.c:254
#16 0xc04ac250 in doreti_ast () at {standard input}:446
---Can't read userspace from dump, or kernel process---
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
Re: Lots of kernel core dumps
Daniela wrote: I'm getting lots of kernel core dumps on my server. My RAM is OK, I tested it. Below are more detailed informations. Any help would be greatly appreciated. I'm not yet intimate with the kernel, but I'm willing to learn it all. Thanks in advance. You posted to -hackers, but this is an older version of -current. This is a known problem. I believe it was fixed on the HEAD branch in the last couple of days (i.e. if you update your -current sources, then the problem should be resolved). See recent discussions about trap 12 and panic in NFS, and older discussions about the same panic in smbfs. If you are already running today's -current, you can always try: options DISABLE_PSE options DISABLE_PG_G These are in GENERIC, so if it isn't in your SM58-27 kernel config file, then it's because you went out of your way to take them out. I mention this possibility because of: panic: bad pte -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Lots of kernel core dumps
On Friday 21 March 2003 22:10, Kris Kennaway wrote: On Fri, Mar 21, 2003 at 08:37:46PM +0100, Daniela wrote: Hi all! I'm getting lots of kernel core dumps on my server. My RAM is OK, I tested it. Below are more detailed informations. Any help would be greatly appreciated. I think this was fixed after 5.0-R..upgrade to -current and try again. Kris I'm running 5.0-RELEASE, not -CURRENT. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Lots of kernel core dumps
On Fri, Mar 21, 2003 at 10:26:01PM +0100, Daniela wrote: On Friday 21 March 2003 22:10, Kris Kennaway wrote: On Fri, Mar 21, 2003 at 08:37:46PM +0100, Daniela wrote: Hi all! I'm getting lots of kernel core dumps on my server. My RAM is OK, I tested it. Below are more detailed informations. Any help would be greatly appreciated. I think this was fixed after 5.0-R..upgrade to -current and try again. Kris I'm running 5.0-RELEASE, not -CURRENT. I know, but 5.0-RELEASE was a) A work-in-progress, not a perfect, bug-free release b) A snapshot of 5.0-CURRENT You read the 5.0 Early Adopter's Guide, right? Bugs like this are expected at this stage in the development process, and if you encounter them then you need to either give up on 5.x and go back to 4.x-STABLE, or upgrade to 5.0-CURRENT if they are already fixed there. Kris pgp0.pgp Description: PGP signature
