Re: 9.0 release hang in quiescent X
On Aug 17, 2012, at 7:00 PM, Warren Block wbl...@wonkity.com wrote: On Fri, 17 Aug 2012, Gary Aitken wrote: On 08/17/12 14:44, Warren Block wrote: If that stops the lockups, then you could try setting each in turn to a non-zero value (minutes). Leave everything at zero except for the one being tested. But these also seem unlikely, as it's a hardware signal from the video board to the monitor. The suggestion of an X screensaver causing the lockup was excellent. Even if you have no screensavers, there are other things that could be triggered, like xlock. Not sure I understand what you're getting at. By other things that could be triggered what do you mean? e.g. xclock obviously gets triggered at least once per minute; you're suggesting that event could be causinging an update request while blanked out that is causing trouble? Other long-term events that happen might be to blame, not related to screen blanking at all. For example, a cron job. Just as a data point, I had the same thing happen on PC-BSD 9.0. The system would hang after just a couple minutes of inactivity, but would wake up again on keyboard input. Top showed X.org taking 100% of CPU and load averages got up to some seriously ridiculous levels. The workaround I found was to turn off the Dim Screen option in KDE. Never filed a bug report, since I didn't know if it was FreeBSD, PC-BSD or X.org. OK, MCN___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Mounting raw disk backup file.
HI, I had a drive fail recently, it was working fine until I rebooted. After that the partition map was corrupt and I can't mount either partition on the disk. So I made a copy of the whole disk using dd to an old USB drive. There were several IO errors while dd was copying the disk, so I think the disk is starting to go. I can probably fix the partition table using testdisk, but now that I've got this image file I'd rather work with that instead of the physical disk. I've read the Handbook section on using mdconfig, but that assumes the image file is of a filesystem, not a whole disk. I think I've found instructions for how to do it on linux, but if there's a way to mount it on FreeBSD I'd rather do that. So, any suggestions? Here's what file says about the file: mnavarre@pcbsd-1810] /# file /mnt/ada1_backup /mnt/ada1_backup: x86 boot sector; partition 1: ID=0xa5, active, starthead 1, startsector 63, 167766732 sectors; partition 2: ID=0xa5, starthead 254, startsector 167766795, 144809910 sectors, code offset 0x3c, BSD disklabel And just for grins, what fdisk says about the actual disk: mnavarre@pcbsd-1810] /# fdisk ada1 *** Working on device /dev/ada1 *** parameters extracted from in-core disklabel are: cylinders=310098 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=310098 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 167766732 (81917 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 1023/ head 254/ sector 63 The data for partition 2 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 167766795, size 144809910 (70707 Meg), flag 80 (active) beg: cyl 1023/ head 255/ sector 63; end: cyl 1023/ head 254/ sector 63 The data for partition 3 is: UNUSED The data for partition 4 is: UNUSED Thanks, Matt Navarre ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Mounting raw disk backup file.
On Sun, Aug 5, 2012 at 11:28 PM, Michael Sierchio ku...@tenebras.comwrote: On Sun, Aug 5, 2012 at 11:12 PM, Matthew Navarre navarre.matt...@gmail.com wrote: Here's what file says about the file: mnavarre@pcbsd-1810] /# file /mnt/ada1_backup /mnt/ada1_backup: x86 boot sector; partition 1: ID=0xa5, active, starthead 1, startsector 63, 167766732 sectors; partition 2: ID=0xa5, starthead 254, startsector 167766795, 144809910 sectors, code offset 0x3c, BSD disklabel Why did you put it in /mnt? That's customarily used for mounting fileystems. Move it ;-) Heh, the BSD drive with the backup file in on /mnt, the mdconfig node is md1. mdconfig -a -t vnode -f /new-path/ada1_backup note the device that's created (probably md0) you can then operate on /dev/md0 as if it were a disk. In particular, you might want to fix the partition map, the label info, etc. You can then fsck the filesystem (presumably something like /dev/md0s1a or /dev/md0a etc). You'll probably need to tell fsck that it's ufs (i.e. fsck -t ufs /dev/md0a ) you can then mount the fs (mount -t ufs /dev/md0a /mnt ) Thanks, didn't realize that I could use that device node to operate on it like a block device. Of course, the fact that mdconfig makes the system think a file is a block device should have been a clue ;) Now I just need to get the partitions and disklabel figured out. - M OK, MCN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Mounting raw disk backup file.
On Mon, Aug 6, 2012 at 12:08 AM, Polytropon free...@edvax.de wrote: On Sun, 5 Aug 2012 23:12:48 -0700, Matthew Navarre wrote: I can probably fix the partition table using testdisk, but now that I've got this image file I'd rather work with that instead of the physical disk. I've read the Handbook section on using mdconfig, but that assumes the image file is of a filesystem, not a whole disk. I think I've found instructions for how to do it on linux, but if there's a way to mount it on FreeBSD I'd rather do that. It depends on _what_ your disk image (typically created by a dd-like utility to make a 1:1 copy of a whole disk) contains. If there are several slices and partitions, each of them can be accessed like it was a physical disk. Let's assume you have /home/you/ada1.dd which is the copy of your former /dev/ada1 disk. You do: # mdconfig -a -t vnode -u 0 -f /home/you/ada1.dd This results in a file /dev/md0 as well as any partitional qualifier specials that might correspond to the disk the copy has been taken from. You can check that with Yep. Unfortunately the partition table and disklable are screwed, so md1s(1,2) don't appear in dev. Same with ada1, which is the physical disk. The drive has two primary partitions, both of which had a single UFS file system on them. So now I just need to figure out how to fix the partition table and the disklabel and I should be golden getting the data out. That drive is getting replaced, though. # fdisk /dev/md0 and it should print the same partition table as for the real disk. here's the fdisk output for /dev/ada1, which is the real drive: mnavarre@pcbsd-1810] /# fdisk ada1 *** Working on device /dev/ada1 *** parameters extracted from in-core disklabel are: cylinders=310098 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=310098 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 167766732 (81917 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 1023/ head 254/ sector 63 The data for partition 2 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 167766795, size 144809910 (70707 Meg), flag 80 (active) beg: cyl 1023/ head 255/ sector 63; end: cyl 1023/ head 254/ sector 63 The data for partition 3 is: UNUSED The data for partition 4 is: UNUSED Now, the first partition looks sane (size is right, geometry looks right). The second partition, however, looks a bit wrong, since it ends before it starts, but the size is right. And now I've gone and screwed up the disk image file. So, it's math and manpages from here. OK, MCN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Mounting raw disk backup file.
On Mon, Aug 6, 2012 at 2:55 AM, Wojciech Puchar woj...@wojtek.tensor.gdynia.pl wrote: I had a drive fail recently, it was working fine until I rebooted. After that the partition map was corrupt and I can't mount either partition on the disk. So I made a copy of the whole disk using dd to an old USB drive. There were several IO errors while dd was copying the disk, so I think the disk is starting to go. did you use conv=sync,noerror. if not your backup is quite corrupted if errors were uncorrectable. Yep, did that, so I'll lose some data, but that partition is mostly media and some old MacOS (7/8/9) software, so it'd suck to lose it but wouldn't be catastrophic. The first partition on the disk is more important. The ironic thing is that the drives I was going to transfer this data onto and the external hard drive that was going to be hold the backups are on their way. Murphy strikes when you least expect it. So, any suggestions? repair partition table, use mdconfig and then you will get /dev/md0 /dev/md0s1... as with real drive Yep, it's currently the whole repair partition table bit that's giving me problems. Unfortunately, PC disk geometry is not my forte. I'm hoping I can find my log book from the system this drive was transfered from, which should have both the partition map and the alternate superblocks written down. My wife probably put it somewhere safe ;) OK, MCN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Unable to start KDE4 on freebsd 7.4-RELEASE
I updated my FreeBSD box from 6.4 to 7.4 using freebsd-update, got my installed ports in order and updated and installed/updated kde4-4.6.3 and all its dependancies. Xorg works ( i can run twm successfully), but trying to start kde bombs out. It looks like kded is barfing trying to get a a lock on the shared cache. Everything's up to date as of a portsnap fetch this morning. Output from startx follows. Hopefully someone can help, as I'm out of ideas. Thanks, mnavarre. Script started on Sun Jun 5 13:42:25 2011 startx xauth: file /home/mnavarre/.serverauth.59871 does not exist X.Org X Server 1.7.7 Release Date: 2010-05-04 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 7.4-RC3 i386 Current Operating System: FreeBSD reichlieu.lan 7.4-RELEASE FreeBSD 7.4-RELEASE #0: Thu Feb 17 03:51:56 UTC 2011 r...@walker.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 Build Date: 28 May 2011 10:30:45PM Current version of pixman: 0.21.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Sun Jun 5 13:42:25 2011 (==) Using default built-in configuration (30 lines) (EE) Failed to load module fbdev (module does not exist, 0) expected keysym, got XF86TouchpadToggle: line 123 of inet kbuildsycoca4 running... kbuildsycoca4(59915) KConfigGroup::readXdgListEntry: List entry MimeType in .hidden/kommander.desktop is not compliant with XDG standard (missing trailing semicolon). startkde: Starting up... Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) kded(59942)/kdeui (KIconLoader): Unable to find an appropriate lock to guard the shared cache. This *should* be essentially impossible. :( kded(59942)/kdeui (KIconLoader): Unable to perform initial setup, this system probably does not really support process-shared pthreads or semaphores, even though it claims otherwise. QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPainter::begin: Paint device returned engine == 0, type: 2 QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPainter::begin: Paint device returned engine == 0, type: 2 QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPainter::begin: Paint device returned engine == 0, type: 2 QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPainter::begin: Paint device returned engine == 0, type: 2 QPixmap: It is not safe to use pixmaps outside the GUI thread QObject: Cannot create children for a parent that is in a different thread. (Parent is KApplication(0xbfbfe35c), parent's thread is QThread(0x2a322050), current thread is QThread(0x2a322c88) KGlobal::locale() must be called from the main thread before using i18n() in threads. KApplication takes care of this. If not using KApplication, call KGlobal::locale() during initialization. kded(59941): Communication problem with kded , it probably crashed. Error message was: org.freedesktop.DBus.Error.ServiceUnknown : The name org.kde.kded was not provided by any .service files KCrash: Application 'kded4' crashing... KCrash: Attempting to start /usr/local/kde4/lib/kde4/libexec/drkonqi from kdeinit sock_file=/home/mnavarre/.kde4/socket-reichlieu.lan/kdeinit4__0 kcminit(59944)/kdeui (KIconLoader): Unable to find an appropriate lock to guard the shared cache. This *should* be essentially impossible. :( kcminit(59944)/kdeui (KIconLoader): Unable to perform initial setup, this system probably does not really support process-shared pthreads or semaphores, even though it claims otherwise. QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPainter::begin: Paint device returned engine == 0, type: 2 QPixmap: It is not safe to use pixmaps outside
Re: Unable to start KDE4 on freebsd 7.4-RELEASE
On Jun 5, 2011, at 3:17 PM, Antonio Olivares wrote: Mathew, On Sun, Jun 5, 2011 at 3:53 PM, Matthew Navarre mnava...@cox.net wrote: I updated my FreeBSD box from 6.4 to 7.4 using freebsd-update, got my installed ports in order and updated and installed/updated kde4-4.6.3 and all its dependancies. Xorg works ( i can run twm successfully), but trying to start kde bombs out. It looks like kded is barfing trying to get a a lock on the shared cache. Everything's up to date as of a portsnap fetch this morning. Output from startx follows. Hopefully someone can help, as I'm out of ideas. Thanks, mnavarre. Script started on Sun Jun 5 13:42:25 2011 startx xauth: file /home/mnavarre/.serverauth.59871 does not exist X.Org X Server 1.7.7 Release Date: 2010-05-04 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 7.4-RC3 i386 Current Operating System: FreeBSD reichlieu.lan 7.4-RELEASE FreeBSD 7.4-RELEASE #0: Thu Feb 17 03:51:56 UTC 2011 r...@walker.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 Build Date: 28 May 2011 10:30:45PM Current version of pixman: 0.21.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Sun Jun 5 13:42:25 2011 (==) Using default built-in configuration (30 lines) (EE) Failed to load module fbdev (module does not exist, 0) expected keysym, got XF86TouchpadToggle: line 123 of inet kbuildsycoca4 running... kbuildsycoca4(59915) KConfigGroup::readXdgListEntry: List entry MimeType in .hidden/kommander.desktop is not compliant with XDG standard (missing trailing semicolon). startkde: Starting up... Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) kded(59942)/kdeui (KIconLoader): Unable to find an appropriate lock to guard the shared cache. This *should* be essentially impossible. :( kded(59942)/kdeui (KIconLoader): Unable to perform initial setup, this system probably does not really support process-shared pthreads or semaphores, even though it claims otherwise. snip startkde: Shutting down... klauncher: Exiting on signal 1 kde3: not found kde3: not found startkde: Running shutdown scripts... startkde: Done. waiting for X server to shut down Script done on Sun Jun 5 13:42:36 2011___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org I can see that startx might be looking for kde 3, the line : kde3: not found kde3: not found I was wondering about that myself, but KDE has never been installed on this machine until now. I thought I'd gotten all the old KDE cruft rm'ed from $HOME and you have kde 4.6.3 latest and greatest. Question: Do you have exec startkde in ~/.xinitrc or exec /usr/local/kde4/bin/startkde in ~/.xinitrc The kde4 line is in ~/.xinitrc Because the first one is for kde 3 while the next one(above) is for kde 4. If you try to create another user and the user is able to login, then it might be a problem with the old settings? I created a new user with an empty $HOME, added the startkde line to .xinitrc and had the same problem. I did notice that drkonqi is crashing and writing out a .core file, so I'll see if gdb can tell me anything. Thanks, mnavarre Regards, Antonio ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portmanager -s deletes ports?
On May 23, 2007, at 10:19 AM, RW wrote: On Thu, 24 May 2007 00:25:31 +1000 Norberto Meijome [EMAIL PROTECTED] wrote: On Wed, 23 May 2007 09:53:39 +0200 Heinrich Rebehn [EMAIL PROTECTED] wrote: This is weird! A program that is supposed to show the *status* of installed ports should never arbitrarily *remove* ports. I agree that is not clear why it is removing ports without warning. Well, we don't actually know that. I suspect that there was a warning, It shouldn't be removing *anything* without user confirmation. any other behavior is Broken and Wrong. Warnings are irrelevant if you just go ahead and do the dangerous thing you were warning about anyway. but it went to stdout and was eaten by |grep OLD. Portmanger then waited for a y/n response for 5 minutes, and went with the default of deleting the port. From the portmanager(1) man page: -s or --status status of installed ports Says *nothing* about even the possibility of removing installed ports. Just status. If -s is removing installed ports which have been moved/removed from the ports tree without confirmation then it's broken, plain and simple. portmanager also has -s -l *AND* -sl options^Wcommands. -sl has not a thing to do with -s or -l. Broken by design. -sl should by convention be equivalent to -s -l, instead -sl maps to --show-leaves while -s maps to --status and --l maps to log. Lame. And there's no difference between 'switches' (options) and commands (imperatives). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions- [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Random panics on FreeeBSD 6.0
On Jun 16, 2006, at 8:13 PM, Matthew Navarre wrote: On Jun 16, 2006, at 7:17 PM, Micah wrote: Matthew Navarre wrote: I've got an AMD Sempron machine running FreeBSD 6.0 that's been experiencing random panics while trying to build world. In fact it just paniced now, with no activity. The panic message is TPTE at 0xbfc20624 IS ZERO @ VA 0810 bad pte This started last night while I was portupgrading ruby and I got random apps segfaulting, mostly gcc, so I suspected bad memory. I installed new memory today, tried to buildworld. And *BAM* panic: bad pte I'm still guessing that this is a hardware problem, and not software but I'm not sure. If anyone can give me a clue I'd appreciate it. Machine details: AMD Sempron ECS K8M800-M2 mainboard 1 GB Kingston PC-3200. Thanks, Matt First, a quick Google of bad pte turns up some ideas. Try disabling or changing APIC and/or ACPI settings. Make sure your swap partition is error free and has enough room. Google a bit more just on the lists.freebsd.org site for several possibilities. Yeah, I was wondering if it might be something in the BIOS settings. I'll google around and see what I find. I don't know if the first panic was a bad pte error since the machine was running headless. For hardware, you can try memtest86+ to check to make sure the new memory is good. There are other stress tests you can run as well - I usually use the ultimate boot CD for that stuff. Other possible problems are faulty or too small power supply; too much heat on CPU, RAM, or expansion boards; faulty expansion cards and/or components; or faulty hard drive. I kinda wondered if heat might be an issue, since it was kind of tucked away in a spot with bad airflow. I'll try the memtest thing. Is there a way to get the CPU temp in FreeBSD? Meh. let's see if this thing'll actually compile...\ Gahhh! # cd /usr/ports/sysutils/memtest86 # sudo make install *snip* * Usage: * * 1) Insert blank floppy * 2) dd if=/usr/local/share/memtest86/floppy.bin of=/dev/fd0 * 3) Boot the floppy which would be all well and good if this machine actually had a damned floppy drive. C'mon kids. Let's catch up to the late 90's *BAM* savecore: writing core to vmcore.5 *HATE* ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Random panics on FreeeBSD 6.0
On Jun 16, 2006, at 9:33 PM, Micah wrote: Matthew Navarre wrote: On Jun 16, 2006, at 7:17 PM, Micah wrote: Matthew Navarre wrote: I've got an AMD Sempron machine running FreeBSD 6.0 that's been experiencing random panics while trying to build world. In fact it just paniced now, with no activity. The panic message is TPTE at 0xbfc20624 IS ZERO @ VA 0810 bad pte This started last night while I was portupgrading ruby and I got random apps segfaulting, mostly gcc, so I suspected bad memory. I installed new memory today, tried to buildworld. And *BAM* panic: bad pte I'm still guessing that this is a hardware problem, and not software but I'm not sure. If anyone can give me a clue I'd appreciate it. Machine details: AMD Sempron ECS K8M800-M2 mainboard 1 GB Kingston PC-3200. Thanks, Matt First, a quick Google of bad pte turns up some ideas. Try disabling or changing APIC and/or ACPI settings. Make sure your swap partition is error free and has enough room. Google a bit more just on the lists.freebsd.org site for several possibilities. Yeah, I was wondering if it might be something in the BIOS settings. I'll google around and see what I find. I don't know if the first panic was a bad pte error since the machine was running headless. For hardware, you can try memtest86+ to check to make sure the new memory is good. There are other stress tests you can run as well - I usually use the ultimate boot CD for that stuff. Other possible problems are faulty or too small power supply; too much heat on CPU, RAM, or expansion boards; faulty expansion cards and/ or components; or faulty hard drive. I kinda wondered if heat might be an issue, since it was kind of tucked away in a spot with bad airflow. I'll try the memtest thing. Is there a way to get the CPU temp in FreeBSD? As mentioned, mbmon might work, but don't think that CPU is the only generator of heat. I had random reboots due to an overheating graphics card once. A spot thermometer comes in handy at a time like this. Eh. I think it's time to find the receipt and make the computer store fix this POS. I think that's the last time I buy cheap crap hardware. Thanks again, Matt ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Random panics on FreeeBSD 6.0
On Jun 17, 2006, at 3:43 AM, Alex Zbyslaw wrote: Micah wrote: Matthew Navarre wrote: I've got an AMD Sempron machine running FreeBSD 6.0 that's been experiencing random panics while trying to build world. In fact it just paniced now, with no activity. The panic message is TPTE at 0xbfc20624 IS ZERO @ VA 0810 bad pte This started last night while I was portupgrading ruby and I got random apps segfaulting, mostly gcc, so I suspected bad memory. I installed new memory today, tried to buildworld. And *BAM* panic: bad pte I'm still guessing that this is a hardware problem, and not software but I'm not sure. If anyone can give me a clue I'd appreciate it. Yup, looks like a bad memory slot along with a bad stick of RAM. I switched slots and installed a known-good stick of RAM and was able to build world. So I need to get the mainboard replaced, but at least it's not falling over in a stiff breeze. Stupid hardware. Thanks, guys Matt As well as the things mentioned, it could also be a bad memory slot (rather than chip), so try with one chip in one slot; if it still fails, one chip in another slot; if it fails another chip in one slot etc. It could be a combination :-( --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Random panics on FreeeBSD 6.0
I've got an AMD Sempron machine running FreeBSD 6.0 that's been experiencing random panics while trying to build world. In fact it just paniced now, with no activity. The panic message is TPTE at 0xbfc20624 IS ZERO @ VA 0810 bad pte This started last night while I was portupgrading ruby and I got random apps segfaulting, mostly gcc, so I suspected bad memory. I installed new memory today, tried to buildworld. And *BAM* panic: bad pte I'm still guessing that this is a hardware problem, and not software but I'm not sure. If anyone can give me a clue I'd appreciate it. Machine details: AMD Sempron ECS K8M800-M2 mainboard 1 GB Kingston PC-3200. Thanks, Matt ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Random panics on FreeeBSD 6.0
On Jun 16, 2006, at 7:17 PM, Micah wrote: Matthew Navarre wrote: I've got an AMD Sempron machine running FreeBSD 6.0 that's been experiencing random panics while trying to build world. In fact it just paniced now, with no activity. The panic message is TPTE at 0xbfc20624 IS ZERO @ VA 0810 bad pte This started last night while I was portupgrading ruby and I got random apps segfaulting, mostly gcc, so I suspected bad memory. I installed new memory today, tried to buildworld. And *BAM* panic: bad pte I'm still guessing that this is a hardware problem, and not software but I'm not sure. If anyone can give me a clue I'd appreciate it. Machine details: AMD Sempron ECS K8M800-M2 mainboard 1 GB Kingston PC-3200. Thanks, Matt First, a quick Google of bad pte turns up some ideas. Try disabling or changing APIC and/or ACPI settings. Make sure your swap partition is error free and has enough room. Google a bit more just on the lists.freebsd.org site for several possibilities. Yeah, I was wondering if it might be something in the BIOS settings. I'll google around and see what I find. I don't know if the first panic was a bad pte error since the machine was running headless. For hardware, you can try memtest86+ to check to make sure the new memory is good. There are other stress tests you can run as well - I usually use the ultimate boot CD for that stuff. Other possible problems are faulty or too small power supply; too much heat on CPU, RAM, or expansion boards; faulty expansion cards and/or components; or faulty hard drive. I kinda wondered if heat might be an issue, since it was kind of tucked away in a spot with bad airflow. I'll try the memtest thing. Is there a way to get the CPU temp in FreeBSD? Meh. let's see if this thing'll actually compile... Thanks, Micah Matt ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: BSD legal question
On May 18, 2005, at 8:08 PM, Danny Pansters wrote: On Thursday 19 May 2005 04:32, Francisco Reyes wrote: On Thu, 19 May 2005 [EMAIL PROTECTED] wrote: Francisco Reyes wrote: BSD - You can take the code and do as you please. No need to even give back the changes you made. Although you DO need to carry the accreditation. Wasn't that restriction later removed too? That6's the advertising clause which rewuired any advertising material to claim something like Includes stuff from *BSD. That has long been taken out, but there's some projects that still have it. No, the accreditation Francisco was refereing to The acknowledgementment means in source code original license and credits and in binary some cridits for example in the help|about or the man page. Where it's most appropriate (though the legalese doesn't specifically say that because of course it opens up a debate about the definition of appropriate ;-) IANAL Dan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions- [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: BSD legal question
On May 18, 2005, at 8:08 PM, Danny Pansters wrote: On Thursday 19 May 2005 04:32, Francisco Reyes wrote: On Thu, 19 May 2005 [EMAIL PROTECTED] wrote: Francisco Reyes wrote: BSD - You can take the code and do as you please. No need to even give back the changes you made. Although you DO need to carry the accreditation. Wasn't that restriction later removed too? That6's the advertising clause which rewuired any advertising material to claim something like Includes stuff from *BSD. That has long been taken out, but there's some projects that still have it. I believe what Francisco refers to is the requirement to keep the copyright notices intact for the code you modify. (i.e. you can't just find some code under the BSD license, change all the copyright notices and claim you wrote it all) The advertising clause, IIRC(and I may not be) said you couldn't use the names of any copyright holders in advertising products based on the licensed code. The acknowledgementment means in source code original license and credits and in binary some cridits for example in the help|about or the man page. Where it's most appropriate (though the legalese doesn't specifically say that because of course it opens up a debate about the definition of appropriate ;-) IANAL Me neither, brother. If you need *real* legal advice on GPL vs. BSDL issues find a good copyright lawyer, grease up and prepare to be boarded. Cuz' they don't come cheap, generally. Dan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions- [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: BSD legal question
On May 18, 2005, at 10:17 PM, Matthew Navarre wrote: On May 18, 2005, at 8:08 PM, Danny Pansters wrote: On Thursday 19 May 2005 04:32, Francisco Reyes wrote: On Thu, 19 May 2005 [EMAIL PROTECTED] wrote: Francisco Reyes wrote: BSD - You can take the code and do as you please. No need to even give back the changes you made. Although you DO need to carry the accreditation. Wasn't that restriction later removed too? That6's the advertising clause which rewuired any advertising material to claim something like Includes stuff from *BSD. That has long been taken out, but there's some projects that still have it. No, the accreditation Francisco was refereing to DOH! sorry, wrong button. The acknowledgementment means in source code original license and credits and in binary some cridits for example in the help|about or the man page. Where it's most appropriate (though the legalese doesn't specifically say that because of course it opens up a debate about the definition of appropriate ;-) IANAL Dan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions- [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions- [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
