Re: Help diagnosing system hangs?
Nikolas Britton <[EMAIL PROTECTED]> wrote: > On 8/23/05, Eric Rescorla <[EMAIL PROTECTED]> wrote: > > I've recently been experiencing frequent hangs with FreeBSD 5.3-RELEASE-p20. > > Strangely, this didn't appear to happen with 5.3-RELEASE or before > > a few months ago. > > > > My platform is a P4-2.8 GHz (dmesg appended at end). > > > > The behavior is that X freezes (sorry, I can't say if the clock is still > > working because I forgot to check) and sshing into the box hangs. A > > hard reboot clears things and the box starts normally, except that it > > fscks as expected. Nothing appears in /var/log/messages, etc. > > > > Because this problem started fairly recently, my one guess is that this > > is somehow related to the hyperthreading fix in SA-05:09. This processor > > allegedly has hyperthreading but I'm running GENERIC. Any possibility > > this could be responsible for hanging somehow? > > Have you ruled out hardware problems, what makes you think it's > FreeBSD? Is this problem random? etc. (1) No, I haven't ruled out hardware problems. However, I have a nearly identical machine that started acting up in the same way in the same time frame, which is why I'm suspecting the OS. Meant to mention this but got bogged down in detail. Sorry! (2) It does appear to be random, yes. Thanks, -Ekr ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Help diagnosing system hangs?
I've recently been experiencing frequent hangs with FreeBSD 5.3-RELEASE-p20. Strangely, this didn't appear to happen with 5.3-RELEASE or before a few months ago. My platform is a P4-2.8 GHz (dmesg appended at end). The behavior is that X freezes (sorry, I can't say if the clock is still working because I forgot to check) and sshing into the box hangs. A hard reboot clears things and the box starts normally, except that it fscks as expected. Nothing appears in /var/log/messages, etc. Because this problem started fairly recently, my one guess is that this is somehow related to the hyperthreading fix in SA-05:09. This processor allegedly has hyperthreading but I'm running GENERIC. Any possibility this could be responsible for hanging somehow? If this isn't a likely culprit, I'm assuming that the next step is to try to debug the hang with DDB. There's one added difficulty here which is that I'm using a Matrox P650 and for some reason the X drivers are screwy so that once you've entered X any attempt to use the virtual consoles just gets you a blank screen. So, while I've rebuilt the kernel with DDB, I suspect that I won't actually be able to force the system console into debugging mode. I assume that this means I need a serial console but based on the Handbook serial console section it looks like I can't use a serial console along with the normal console, and since I want to use X, that would be bad. Am I misreading this? Any help FreeBSDers can offer would be much appreciated. Best, -Ekr Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-RELEASE-p20 #0: Wed Jul 27 05:56:48 PDT 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz (2798.67-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf25 Stepping = 5 Features=0xbfebfbff Hyperthreading: 2 logical CPUs real memory = 1072889856 (1023 MB) avail memory = 1040326656 (992 MB) ioapic0 irqs 0-23 on motherboard npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: port 0x530-0x537 on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xf400-0xf7ff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pcib1: could not get PCI interrupt routing table for \\_SB_.PCI0.P0P1 - AE_NOT_FOUND pci1: on pcib1 pci1: at device 0.0 (no driver attached) pcib2: at device 3.0 on pci0 pci2: on pcib2 em0: port 0xcf80-0xcf9f mem 0xfe9e-0xfe9f irq 18 at device 1.0 on pci2 em0: Ethernet address: 00:0e:a6:1c:7e:4d em0: Speed:N/A Duplex:N/A uhci0: port 0xef00-0xef1f irq 16 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xef20-0xef3f irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xef40-0xef5f irq 18 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered uhci3: port 0xef80-0xef9f irq 16 at device 29.3 on pci0 uhci3: [GIANT-LOCKED] usb3: on uhci3 usb3: USB revision 1.0 uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered pci0: at device 29.7 (no driver attached) pcib3: at device 30.0 on pci0 pci3: on pcib3 fwohci0: port 0xdc00-0xdc7f mem 0xfeaff800-0xfeaf irq 20 at device 3.0 on pci3 fwohci0: OHCI version 1.0 (ROM=1) fwohci0: No. of Isochronous channels is 8. fwohci0: EUI64 00:e0:18:00:00:4b:c3:e5 fwohci0: Phy 1394a available S400, 3 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:e0:18:4b:c3:e5 fwe0: Ethernet address: 02:e0:18:4b:c3:e5 fwe0: if_start running deferred for Giant sbp0: on firewire0 fwohci0: Initiate bus reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) em1: port 0xdf00-0xdf3f mem 0xfea8-0xfea9,0xfeaa-0xfeab irq 20 at device 12.0 on pci3 em1: Ethernet address: 00:0e:0c:05:0d:95 em1: Speed:N/A Duplex:N/A isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0xfc00-0xfc0f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 atapci1: port 0xef60-0xef6f,0xefa8-0xefab,0xefa0-0xefa7,0xefac-0xefaf,0xefe0-0x
Re: Missing /etc/periodic.daily processes in /proc
Eric Rescorla <[EMAIL PROTECTED]> wrote: > FreeBSD Version: FreeBSD 4.9-STABLE #2 > Platform: x86 > > I recently ran chkrootkit and it complained about processes that were in > ps but not in /proc. Usually these are just transient processed but in > this case I investigated and found something weird. Oh, one more thing: The files actually exist in /proc and look to be populated with reasonable stuff. E.g. [65] ls /proc/11253 cmdline ctl dbregs etype filefpregs map mem notenotepg regsrlimit status -Ekr ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Missing /etc/periodic.daily processes in /proc
FreeBSD Version:FreeBSD 4.9-STABLE #2 Platform: x86 I recently ran chkrootkit and it complained about processes that were in ps but not in /proc. Usually these are just transient processed but in this case I investigated and found something weird. Here's a sample output: PID 11252: not in readdir output PID 11253: not in readdir output PID 11254: not in readdir output Strangely, ls shows something different [56] ls /proc | grep 1125 11252 Even more strangely, which processes are implicated moves around, but they always claim to be running out of /etc/periodic, e.g. root11252 0.0 0.0 672 176 ?? I10Dec04 0:00.00 /bin/sh - /usr/sbin/periodic security root11253 0.0 0.0 648 168 ?? I10Dec04 0:00.00 /bin/sh - /usr/sbin/periodic security root11254 0.0 0.0 648 168 ?? I10Dec04 0:00.00 /bin/sh - /etc/periodic/security/100.chksetuid Note the old dates here: I've got a filesystem on a removable drive that didn't detach cleanly and now some attempts to grovel through the filesystem tables (e.g. df) hang badly. I can obviously reboot to clear this error but I wondered if there was any more investigation I should do before I destroy the "evidence". Does this look familiar to anyone? Thanks, -Ekr ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Creative Extigy with FreeBSD 4.9?
I've got a 4.9 machine which I'd like to interface to my Creative Extigy external amp for playing MP3s and the like. For obvious reasons, I'd like to have that connection be digital. After some research, it looks like there are two choices: (1) SPDIF I've got an Asus P4C-800E mainboard with a built-in interface that dmesg reports as: pcm0: port 0xee80-0xeebf,0xe800-0xe8ff mem 0xfebff400-0xf ebff4ff,0xfebff800-0xfebff9ff irq 5 at device 31.5 on pci0 pcm0: The card has an SPDIF output, but I'm not sure how to get mplayer (or anything else) to actually use it. I've installed mplayer out of ports and from reading the not very clear documentation, it looks like "-ac hwac3" should do the trick, but what I get when I try that is: == Forced audio codec: hwac3 *** Try to upgrade /users/ekr/.mplayer/codecs.conf from etc/codecs.conf *** If it still does not work, read DOCS/codecs.html! Cannot find codec for audio format 0x55. == (2) USB The Extigy has a USB plug in the front so I would think I could use uaudio, but it's even more unclear to me how that works. When I plugged it in, nothing interesting happened (i.e. nothing on the console or syslog suggesting that it even saw the device). usbd is running. Any suggestions here would be great! Thanks, -Ekr ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Plan 9 style backup utility for FreeBSD?
I'm finally getting to the point where my disk capacity massively outruns my tape capacity, so I'm thinking of converting to removable disk-only backup. I could just use Amanda to backup to disk, but I'm intrigued by Plan 9's archival filesystem where backups from (say Jan 1, 1999) would go in /1999/1/1 and you could just find the files directly rather than grovelling through dump files. Is there some standard tool for doing this on FreeBSD? You can't just do a direct copy cause this results in major disk space wastage so I'm imagining you need to use hard links or something to keep the size down. Thanks, -Ekr ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
