Re: cron job causes fwrite: broken pipe error, runs fine on command line
Dave, > On Mon, Nov 9, 2009 at 2:19 PM, John Mendenhall wrote: > > I have several openbsd 4.4 boxes, all of which are running > > spamd. I have a cron job which runs a script, which has the > > following commands in it: > > Well, sort is obviously calling fwrite to write on stdout, which > head reads. When head has had enough, it closes its input, > which is from the pipe. fwrite then terminates with an EPIPE > error, which sort is not (seemingly) handling properly. (Looks > like it is calling warn(3) or err(3).) Maybe sort(3) is not complaining > if isatty(fileno(stdout)). Only the source knows for sure. > > The mystery to me is why the error message does not appear > when the pipe is run on a tty. (I can duplicate your error easily). > > To me this looks like normal operation. You seem to be getting > the output you want, right? Yup. So, I guess I can just throw away the standard error, to clean it up a bit. Definitely not a real issue. Just a curiosity that I like solving. I was just wondering why it runs differently in different environments. JohnM -- john mendenhall j...@surfutopia.net surf utopia internet services
Re: cron job causes fwrite: broken pipe error, runs fine on command line
Peter, > John Mendenhall writes: > > oldest spamdb grey entry date timestamp: > > sort: fwrite: Broken pipe > > > Just to eliminate the obvious - how much disk space is available for > temporary files? Could you be on the low side? > - Peter Seems I have plenty. This is happening on all of our machines. Here is one of them: Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/sd0a 2068384 56738 1908228 3%/ /dev/sd0f33028404 2288308 29088676 7%/home /dev/sd0e33027494687292 30688828 2%/mail /dev/sd0h 2052352 6 1949730 0%/tmp /dev/sd0g16514194700424 14988062 4%/usr /dev/sd0d 151562932 4289600 139695186 3%/var JohnM -- john mendenhall j...@surfutopia.net surf utopia internet services
cron job causes fwrite: broken pipe error, runs fine on command line
I have several openbsd 4.4 boxes, all of which are running spamd. I have a cron job which runs a script, which has the following commands in it: - #!/bin/sh PATH=/bin:/sbin:/usr/bin:/usr/sbin export PATH FIELDNUM=6 echo oldest spamdb grey entries: spamdb | grep ^GREY | sort -t \| -k $FIELDNUM -n | head echo echo oldest spamdb grey entry date timestamp: DATEINSECONDS=`spamdb | grep ^GREY | sort -t \| -k $FIELDNUM -n | head -1 | cut -d\| -f$FIELDNUM` date -r $DATEINSECONDS - The purpose of the script is to show me the oldest entries in the spamdb. This is the output (with destination domains replaced with 'domain'): - oldest spamdb grey entries: GREY|189.62.148.55|bd3e9437.virtua.com.br|||1257739194|1257753594|1257753594|1|0 GREY|209.50.235.237|yourhomejob.biz|||1257739196|1257753596|1257753596|2|0 GREY|117.4.19.147|localhost|||1257739199|1257753599|1257753599|1|0 GREY|187.42.168.180|18777208209.telemar.net.br|||1257739199|1257753599|1257753599|1|0 GREY|117.0.122.41|localhost|||1257739200|1257753600|1257753600|1|0 GREY|187.42.168.180|18777208209.telemar.net.br|||1257739200|1257753600|1257753600| +1|0 GREY|187.42.168.180|18777208209.telemar.net.br|||1257739200|1257753600|1257753600 +|1|0 GREY|187.42.168.180|18777208209.telemar.net.br|||1257739201|1257753601|1257753601 +|1|0 GREY|187.42.168.180|18777208209.telemar.net.br|||1257739202|1257753602|125775360 +2|1|0 GREY|124.121.20.135|TVCMVZJBGA|||1257739205|1257753605|1257753605|1|0 sort: fwrite: Broken pipe oldest spamdb grey entry date timestamp: sort: fwrite: Broken pipe Sun Nov 8 19:59:54 PST 2009 - uname -a produces 'OpenBSD yosemite.surfutopia.net 4.4 GENERIC.MP#844 i386' I have read the associated man pages. I have searched the search engines. I was not able to find anything to try to fix this. I am sure this has something to do with terminals or ttys, or something like that. Or it could just be I am dumping the additional data spit out by sort and sort can't handle that, from within cron. I am hoping this is just something stupid I am doing wrong that is easy to fix. Please point me in the direction to find the solution for this issue. Thanks in advance! JohnM -- john mendenhall j...@surfutopia.net surf utopia internet services
Re: Intel Core 2 - round #2
On Thu, 12 Jul 2007, Jason McIntyre wrote: > On Wed, Jul 11, 2007 at 06:21:43PM -0500, Jacob Yocom-Piatt wrote: > > > > the term "rathered" comes to mind. > > > > what does it mean? "Dan Rather"-ed JohnM -- john mendenhall [EMAIL PROTECTED] surf utopia internet services
Re: openbsd 4.0 installed, need to add network interface after install
Brian, > > 1- Check the hardware compatability list to make sure the > > lan card is supported. > > 2- Take a look and make sure the lan card is seated in it's > > slot properly. I have had this happen a few times with > > smaller cards not seating all the way (it's probably because > > of my fat paws). > > 3. Temporarily boot from another operating system's "live CD", e.g. >FreeBSD 6.2 disc 1 (select "fixit" mode to get a shell) > >For a Linux view try Ubuntu 6.06.1, or Fedora 7 for a more >bleeding-edge kernel. These two require you to wait for a graphical >environment to start though. > > These will show you if another OS recognises the card(s) you have. I booted an ultimate boot disk, with several small linux distros on them. None of them found the card. I reseated the card. No go. I tried another card I had, same model. Nothing. I am doing this in a 1U box, so there is a pci 1u riser card. Could it be the riser is bad? Or, could the pci slot itself be bad? What is the best way to test the pci slot? Thanks! JohnM -- john mendenhall [EMAIL PROTECTED] surf utopia internet services
Re: openbsd 4.0 installed, need to add network interface after install
Stuart, > I'm far from a guru, but looking at your dmesg I don't see > a lan card there at all. Here are the first few steps: > > 1- Check the hardware compatability list to make sure the > lan card is supported. > 2- Take a look and make sure the lan card is seated in it's > slot properly. I have had this happen a few times with > smaller cards not seating all the way (it's probably because > of my fat paws). The linksys lne100tx card is listed twice, once as 4.x, and another time with no version. My lne100tx cards are both v5.1. I have tried both. Neither work. No lights on back. Nothing. Is it possible for the pci slot to be bad? > btw, for an add on card, you probably won't see anything in the > systems bios, that is unless bios systems have > gotten much more functional than they were last time I looked. Understood. Thanks so much for your input. JohnM -- john mendenhall [EMAIL PROTECTED] surf utopia internet services
openbsd 4.0 installed, need to add network interface after install
openbsd gurus,
As the saga continues...
I have a newly built server with openbsd 4.0.
During installation, it did not find the onboard
lan interface, which I did not realize until after
the installation had completed.
I made sure the bios was set properly. There
was no LAN option in the BIOS.
I assumed the onboard lan interface was bad.
This has happened before so I added a linksys
lan card in the system.
I rebooted. I checked the BIOS for any LAN options.
Nothing. I booted into openbsd. No interfaces
created.
How do I get the system to discover the network
interface?
I have been searching the net for anything like
this and have not found anything that has worked.
Do I need to reinstall the system?
Or, is there some tool I can use to rediscover the
network interface so it gets setup properly?
Thanks in advance for any pointers you can provide.
JohnM
Here is my current dmesg:
--
OpenBSD 4.0 (GENERIC) #1107: Sat Sep 16 19:15:58 MDT 2006
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: AMD Athlon(tm) ("AuthenticAMD" 686-class, 256KB L2 cache) 1.01 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
real mem = 527986688 (515612K)
avail mem = 473665536 (462564K)
using 4256 buffers containing 26501120 bytes (25880K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(08) BIOS, date 12/24/01, BIOS32 rev. 0 @ 0xfb420,
SMBIOS rev. 2.2 @ 0xf0800 (31
entries)
bios0: VIA Technologies, Inc. VT8361
apm0 at bios0: Power Management spec V1.2
apm0: AC on, battery charge unknown
apm0: flags 70102 dobusy 1 doidle 1
pcibios0 at bios0: rev 2.1 @ 0xf/0xdef4
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfde70/128 (6 entries)
pcibios0: PCI Exclusive IRQs: 10 11
pcibios0: PCI Interrupt Router at 000:07:0 ("VIA VT82C596A ISA" rev 0x00)
pcibios0: PCI bus #1 is the last bus
bios0: ROM list: 0xc/0xc000 0xcc000/0x4000!
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "VIA VT8361 PCI" rev 0x00
ppb0 at pci0 dev 1 function 0 "VIA VT8361 AGP" rev 0x00
pci1 at ppb0 bus 1
vga1 at pci1 dev 0 function 0 "Trident CyberBlade i1" rev 0x00
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
pcib0 at pci0 dev 7 function 0 "VIA VT82C686 ISA" rev 0x40
pciide0 at pci0 dev 7 function 1 "VIA VT82C571 IDE" rev 0x06: ATA100, channel 0
configured to compatibility
, channel 1 configured to compatibility
wd0 at pciide0 channel 0 drive 0:
wd0: 16-sector PIO, LBA48, 117800MB, 241254720 sectors
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5
wd1 at pciide0 channel 1 drive 0:
wd1: 16-sector PIO, LBA48, 114473MB, 234441648 sectors
atapiscsi0 at pciide0 channel 1 drive 1
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: SCSI0 5/cdrom removable
wd1(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
cd0(pciide0:1:1): using PIO mode 4, Ultra-DMA mode 2
uhci0 at pci0 dev 7 function 2 "VIA VT83C572 USB" rev 0x1a: irq 10
usb0 at uhci0: USB revision 1.0
uhub0 at usb0
uhub0: VIA UHCI root hub, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1 at pci0 dev 7 function 3 "VIA VT83C572 USB" rev 0x1a: irq 10
usb1 at uhci1: USB revision 1.0
uhub1 at usb1
uhub1: VIA UHCI root hub, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
viaenv0 at pci0 dev 7 function 4 "VIA VT82C686 SMBus" rev 0x40
isa0 at pcib0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pcppi0 at isa0 port 0x61
midi0 at pcppi0:
spkr0 at pcppi0
npx0 at isa0 port 0xf0/16: using exception 16
pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
pccom0: console
biomask ffed netmask ffed ttymask ffef
pctr: user-level cycle counter enabled
mtrr: Pentium Pro MTRR support
dkcsum: wd0 matches BIOS drive 0x80
dkcsum: wd1 matches BIOS drive 0x81
root on wd0a
rootdev=0x0 rrootdev=0x300 rawdev=0x302
--
--
john mendenhall
[EMAIL PROTECTED]
surf utopia
internet services
Re: openbsd 3.9, openbsd 4.0 install errors, most likely hardware
> > Anyway, how about underclocking your Duron some? Reset the BIOS timings > > and power levels to failsafe? The old K7+VIA Chipset boards were a rough > > crowd. > > This is a custom white box server, all put together. > It is not an HP. > I will try to reset the bios timings and power levels. I reset the bios timings. However, the only choices were optimal and high performance. Same error. I will look for a bios upgrade, if one exists... JohnM -- john mendenhall [EMAIL PROTECTED] surf utopia internet services
Re: openbsd 3.9, openbsd 4.0 install errors, most likely hardware
Brian, > I've seen this before. On old HP gear. Is your HP? Only FreeBSD would > run on the system. NetBSD/OpenBSD dead in the water. Some obscure bug > when the I/O went up (Symbios SCSI). > > One of many reason why I want nothing to do with HP (H-PHUX) ever again. > > Anyway, how about underclocking your Duron some? Reset the BIOS timings > and power levels to failsafe? The old K7+VIA Chipset boards were a rough > crowd. This is a custom white box server, all put together. It is not an HP. I will try to reset the bios timings and power levels. JohnM > On Tue, 12 Jun 2007, John Mendenhall wrote: > > >openbsd gurus, > > > >As my saga continues... > >I have a newly built server on which I am attempting to install > >openbsd 4.0. Problems occurred on install of sets, where comp > >set keeps throwing errors. Suggestion was made that it was probably > >a bad CD. Try a previous CD of an earlier version. I had 3.9 > >available. The logs of the attempts are posted at: > > > > http://www.surfutopia.net/openbsd/ > > > >The logs are separated by the boot log, an install log not > >including the install of the sets, and two passes of the install > >of the sets, all dying in the comp set install. > > > >I have two drives in the server. I only installed on one (wd0). > >I have had the same types of errors when only installing on the > >second (wd1). So, it is most likely not a problem with the > >specific drive. However, the probability could exist. > > > >So, based on these logs, from different openbsd cd versions, > >my hypothesis is there is some weird sort of hardware problem. > >My question is, what tools do you all use to determine where > >the hardware problem could be? > > > >I have already ran the memory through the memtests. There is > >not a problem there. > > > >I am willing to try (almost) anything to play around with > >this. I would like to get the server up and running so I > >can move on to the next one. No time pressure, though. > > > >Thank you in advance for any pointers you can provide. > > > >Thanks! > > > >JohnM -- john mendenhall [EMAIL PROTECTED] surf utopia internet services
Re: openbsd 3.9, openbsd 4.0 install errors, most likely hardware
Peter, > google turns up a few references on various BSD mailing list for the > search string "OpenBSD ffs_valloc: dup alloc". No clear cut > solutions, but the popular suspicion runs in the direction of buggy > (S)ATA controllers or, of course, possibly subtle, hard to trigger > bugs in the operating system's controller support code. Swapping out > motherboards could be unpleasant, but seeing that the error occurs at > pretty much exactly the same spot on the CDs, have you tried swapping > out the CD/DVD drive for a different unit? I tried loading the sets via ftp, same error, same location. JohnM -- john mendenhall [EMAIL PROTECTED] surf utopia internet services
Re: openbsd 3.9, openbsd 4.0 install errors, most likely hardware
> Things to try (in any order you please): > 1. check IDE cables > 2. check whether Master/Slave/CS settings are correct > 3. In case Brian is right, you might want to put CD on the same cable > as hd0, to slow-down IDE. > 4. also check where you disks are connected - to IDE bus or to ATA-133 > controller on the board. Sometimes it does make a difference. > 5. my BIOS was updated to the latest one, as there was some bug about > large hard disks not working correctly (your ones seem to be 120G, so > it is unlikely BIOS is a problem here). > 6. the last step would be to try another harddisk. > > Or (just got this idea) you could simply try ftp install. If CD-rom > reader is bad, boot from CD but install from ftp - this would > definitely rule out the 'bad cd-rom drive' hypothesis :) I just tried the ftp install. Same problem, same location. I have tried another hard disk, same approximate size. Same problem, same location. I am going to look for any bios updates online, if I can find any. I will also be checking the cables, master/slave/cs settings, and cd + hd0 on same cable. As for IDE bus or ATA-133 controller on board, the cables are connected to the std ide0 and ide1 connectors on the motherboard. When you say IDE bus, are you referring to another connector? JohnM -- john mendenhall [EMAIL PROTECTED] surf utopia internet services
Re: openbsd 3.9, openbsd 4.0 install errors, most likely hardware
Maxim, > >set keeps throwing errors. Suggestion was made that it was probably > >a bad CD. Try a previous CD of an earlier version. I had 3.9 > >available. The logs of the attempts are posted at: > > In my case when I had the same problem it was the CD-rom reader that > was bad. Replacing cdrom with DVD drive from my workstation helped. Could that explain the errors I am seeing? It appears the error is on the write, not the read, though I could be wrong. JohnM -- john mendenhall [EMAIL PROTECTED] surf utopia internet services
openbsd 3.9, openbsd 4.0 install errors, most likely hardware
openbsd gurus, As my saga continues... I have a newly built server on which I am attempting to install openbsd 4.0. Problems occurred on install of sets, where comp set keeps throwing errors. Suggestion was made that it was probably a bad CD. Try a previous CD of an earlier version. I had 3.9 available. The logs of the attempts are posted at: http://www.surfutopia.net/openbsd/ The logs are separated by the boot log, an install log not including the install of the sets, and two passes of the install of the sets, all dying in the comp set install. I have two drives in the server. I only installed on one (wd0). I have had the same types of errors when only installing on the second (wd1). So, it is most likely not a problem with the specific drive. However, the probability could exist. So, based on these logs, from different openbsd cd versions, my hypothesis is there is some weird sort of hardware problem. My question is, what tools do you all use to determine where the hardware problem could be? I have already ran the memory through the memtests. There is not a problem there. I am willing to try (almost) anything to play around with this. I would like to get the server up and running so I can move on to the next one. No time pressure, though. Thank you in advance for any pointers you can provide. Thanks! JohnM -- john mendenhall [EMAIL PROTECTED] surf utopia internet services
Re: new openbsd 4.0 server, panic on ufsdirhash
> OK, now I'm clueless why this happens. I didn't see in your verbose > dmesg at all any obvious PCI busses or devices. Yet the normal dmesg > lists your PCI devices. I could be reading the devices wrong, but I > read in your verbose dmesg that it found: > 1: Audio > 2: Realtek Ethernet (probably a PCI device??) > 3: isa0 bus > 4: Keyboard/mouse ports (which I really think they are attached on the > ISA bus, internally on the motherboard) > 5: speaker (again, same as #4, on the ISA bus in the motherboard) > 6: parallel (ditto) > 7: npx0 (I think this is your coprocessor, and I don't know what bus it > is on) > 8: COM/Serial ports (ditto as #4) > 9: Floppy drive (I would think this is on the ISA bus, but I am not > sure) > > Aside from #2, the realtek ethernet, I am not seeing any signs of PCI > detection. But how can it boot off the drive, which is on pciide0 > (from original, normal dmesg in digest #783). That device sure looks > like it's on the PCI bus. I'm lost on this one, I totally expected to > see anything, SOMETHING about the pci bus (wouldn't it be pci0?). I have no idea why that is happening. Strange. > John did state he has another version, and if *THIS* thing fails > horribly bad on trying to get more information, I would try the other > version. ... > > John, please try 4.0 and then doing a source upgrade to 4.1, if this > verbose dmesg doesn't help anybody. Sorry for bringing it up :( This is the 4.0 release. I usually run a release behind. And, I have not ordered a 4.1 yet. I will in the next week or two. I do have v3.9 and earlier releases available. JohnM -- john mendenhall [EMAIL PROTECTED] surf utopia internet services
Re: new openbsd 4.0 server, panic on ufsdirhash
for hme* >>> hme probe returned 0 >>> probing for pcic* >>> pcic probe returned 0 >>> rl probe won rl0 at pci0 dev 10 function 0 "Realtek 8139" rev 0x10: irq 12, address 00:e0:06:f6:bf:3e >>> probing for nsphy* >>> nsphy probe returned 0 >>> probing for nsphyter* >>> nsphyter probe returned 0 >>> probing for qsphy* >>> qsphy probe returned 0 >>> probing for inphy* >>> inphy probe returned 0 >>> probing for iophy* >>> iophy probe returned 0 >>> probing for eephy* >>> eephy probe returned 0 >>> probing for exphy* >>> exphy probe returned 0 >>> probing for rlphy* >>> rlphy probe returned 5 >>> probing for lxtphy* >>> lxtphy probe returned 0 >>> probing for luphy* >>> luphy probe returned 0 >>> probing for mtdphy* >>> mtdphy probe returned 0 >>> probing for icsphy* >>> icsphy probe returned 0 >>> probing for sqphy* >>> sqphy probe returned 0 >>> probing for tqphy* >>> tqphy probe returned 0 >>> probing for ukphy* >>> ukphy probe returned 1 >>> probing for dcphy* >>> dcphy probe returned 0 >>> probing for bmtphy* >>> bmtphy probe returned 0 >>> probing for brgphy* >>> brgphy probe returned 0 >>> probing for xmphy* >>> xmphy probe returned 0 >>> probing for amphy* >>> amphy probe returned 0 >>> probing for acphy* >>> acphy probe returned 0 >>> probing for nsgphy* >>> nsgphy probe returned 0 >>> probing for urlphy* >>> urlphy probe returned 0 >>> probing for rgephy* >>> rgephy probe returned 0 >>> probing for ciphy* >>> ciphy probe returned 0 >>> rlphy probe won rlphy0 at rl0 phy 0: RTL internal PHY >>> probing for isa0 >>> isa probe returned 1 >>> isa probe won isa0 at pcib0 >>> probing for isadma0 >>> probing for isadma0 succeeded isadma0 at isa0 >>> probing for ast0 >>> probing for ast0 failed >>> probing for cy0 >>> probing for cy0 failed >>> probing for pckbc0 >>> probing for pckbc0 succeeded pckbc0 at isa0 port 0x60/5 >>> probing for pckbd* >>> pckbd probe returned 2 >>> probing for pms* >>> pms probe returned 0 >>> probing for pmsi* >>> pmsi probe returned 0 >>> pckbd probe won pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot >>> probing for wskbd* >>> wskbd probe returned 1 >>> wskbd probe won wskbd0 at pckbd0: console keyboard, using wsdisplay0 >>> probing for pckbd* >>> pckbd probe returned 0 >>> probing for pms* >>> pms probe returned 0 >>> probing for pmsi* >>> pmsi probe returned 0 >>> no winning probe >>> probing for vga0 >>> probing for vga0 failed >>> probing for pcdisplay0 >>> probing for pcdisplay0 failed >>> probing for bha0 >>> probing for bha0 failed >>> probing for aic0 >>> probing for aic0 failed >>> probing for aha0 >>> probing for aha0 failed >>> probing for aha1 >>> probing for aha1 failed >>> probing for uha0 >>> probing for uha0 failed >>> probing for wdc0 >>> probing for wdc0 failed >>> probing for wdc1 >>> probing for wdc1 failed >>> probing for lc0 >>> probing for lc0 failed >>> probing for lc1 >>> probing for lc1 failed >>> probing for ne0 >>> probing for ne0 failed >>> probing for ne1 >>> probing for ne1 failed >>> probing for ne2 >>> probing for ne2 failed >>> probing for we0 >>> probing for we0 failed >>> probing for we1 >>> probing for we1 failed >>> probing for ec0 >>> probing for ec0 failed >>> probing for ep0 >>> probing for ep0 failed >>> probing for ep* >>> probing for ep* finished >>> probing for ie0 >>> probing for ie0 failed >>> probing for ex0 >>> probing for ex0 failed >>> probing for le0 >>> probing for le0 failed >>> probing for sm0 >>> probing for sm0 failed >>> probing for mpu* >>> probing for mpu* finished >>> probing for sb0 >>> probing for sb0 failed >>> probing for pas0 >>> probing for pas0 failed >>> probing for pss0 >>> probing for pss0 failed >>> probing for wss0 >>> probing for wss0 failed >>> probing for gus0 >>> probing for gus0 failed >>> probing for pcppi0 >>> probing for pcppi0 succeeded pcppi0 at isa0 port 0x61 >>> probing for midi* >>> midi probe returned 1 >>> probing for spkr0 >>> spkr probe returned 1 >>> midi probe won midi0 at pcppi0: >>> probing for midi* >>> midi probe returned 0 >>> probing for spkr0 >>> spkr probe returned 1 >>> spkr probe won spkr0 at pcppi0 >>> probing for midi* >>> midi probe returned 0 >>> no winning probe >>> probing for lpt0 >>> probing for lpt0 succeeded lpt0 at isa0 port 0x378/4 irq 7 >>> probing for lpt1 >>> probing for lpt1 failed >>> probing for lpt2 >>> probing for lpt2 failed >>> probing for lm0 >>> probing for lm0 failed >>> probing for nsclpcsio* >>> probing for nsclpcsio* finished >>> probing for nsclpcsio* >>> probing for nsclpcsio* finished >>> probing for gscsio* >>> probing for gscsio* finished >>> probing for gscsio* >>> probing for gscsio* finished >>> probing for it0 >>> probing for it0 failed >>> probing for it1 >>> probing for it1 failed >>> probing for it2 >>> probing for it2 failed >>> probing for viasio* >>> probing for viasio* finished >>> probing for viasio* >>> probing for viasio* finished >>> probing for aps0 >>> probing for aps0 failed >>> probing for npx0 >>> probing for npx0 succeeded npx0 at isa0 port 0xf0/16: using exception 16 >>> probing for pccom0 >>> probing for pccom0 succeeded pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo >>> probing for pccom1 >>> probing for pccom1 failed >>> probing for pccom2 >>> probing for pccom2 failed >>> probing for lms0 >>> probing for lms0 failed >>> probing for lms1 >>> probing for lms1 failed >>> probing for mms0 >>> probing for mms0 failed >>> probing for mms1 >>> probing for mms1 failed >>> probing for fdc0 >>> probing for fdc0 succeeded fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 >>> probing for fd* >>> fd probe returned 0 >>> no winning probe >>> probing for fd* >>> fd probe returned 0 >>> no winning probe >>> probing for fd* >>> fd probe returned 0 >>> no winning probe >>> probing for fd* >>> fd probe returned 0 >>> no winning probe >>> probing for isapnp0 >>> probing for isapnp0 failed >>> probing for pcic0 >>> probing for pcic0 failed >>> probing for pcic1 >>> probing for pcic1 failed >>> probing for pcic2 >>> probing for pcic2 failed biomask fb6d netmask fb6d ttymask fbef pctr: user-level cycle counter enabled mtrr: Pentium Pro MTRR support dkcsum: wd0 matches BIOS drive 0x80 dkcsum: wd1 matches BIOS drive 0x81 root on wd0a rootdev=0x0 rrootdev=0x300 rawdev=0x302 - -- john mendenhall [EMAIL PROTECTED] surf utopia internet services
Re: new openbsd 4.0 server, panic on ufsdirhash
> On Wed, May 16, 2007 at 09:30:44AM -0700, John Mendenhall wrote: > > If anyone knows of a tool I can use to determine the ATA > > controller, or any other hw things I need to find out, > > please post any pointers. > > dmesg(8) Well, I posted the dmesg at the beginning of this thread. Here is an excerpt with the ide/ata hardware: - pciide0 at pci0 dev 7 function 1 "VIA VT82C571 IDE" rev 0x06: ATA100, channel 0 configured to compatibility, channel 1 configured to compatibility wd0 at pciide0 channel 0 drive 0: wd0: 16-sector PIO, LBA48, 117800MB, 241254720 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5 wd1 at pciide0 channel 1 drive 0: wd1: 16-sector PIO, LBA48, 114473MB, 234441648 sectors - There may be more. Please let me know if I need to repost it. > > Anyone know how to boot with more messages? > > man boot doesn't show any verbose options. > > Use UKC (boot -c), and the "verbose" command. See boot_config(8). Is this supported when booting from cd? I can only boot from the cd right now. Once it starts copying data, it crashes in the comp set. JohnM -- john mendenhall [EMAIL PROTECTED] surf utopia internet services
Re: new openbsd 4.0 server, panic on ufsdirhash
> I don't know if Open would have any of those tools built in. I don't > have a "ready" openbsd box right now. If anyone knows of a tool I can use to determine the ATA controller, or any other hw things I need to find out, please post any pointers. > Google search for "thunderboot ultimate boot cd" doesn't reveal > anything. it suggested a spelling correction, for thunderboom, which > didn't easily reveal any bootable cd. A link to the ISO and I'd offer > what I can for diagnostics and probing solutions. The ultimate boot cd is something I got off ebay. Not a brand name, but lots of the tools we need for mem testing. > Is there a way to get the kernel to more verbosely announce what it's > probing and configuring, like what FreeBSD's boot loader's "-v" option > will do? Haven't tried, haven't looked anything up. Anyone know how to boot with more messages? man boot doesn't show any verbose options. > We are definately narrowing down the culprit, and I just hope we come > to a solid conclusion. Amen. Thanks! JohnM -- john mendenhall [EMAIL PROTECTED] surf utopia internet services
Re: new openbsd 4.0 server, panic on ufsdirhash
Tim, > John, since you were able to boot the ultimate boot cd and run both > drives completely, I don't think any hardware is the culprit. Your CD > drive, Hard Drive(s), memory, etc all work under that OS. > > My mindset is now leading to some bug that OpenBSD is doing (probably) > with the ATA controller. Probe from the ultimate boot cd to see what > ATA controller it is using, and then find what OpenBSD is finding the > ATA controller to be. A minor model difference could be the culprit > (model 1234 versus model 1234a, for example). I am using the thunderboot ultimate boot cd. Any hints on which tool could get the ata controller the box is using? I can see the ATA-# supported (6,5,4,3,2). Lots of other information. I don't see a model/version number yet. I will keep checking all the tools on here. JohnM -- john mendenhall [EMAIL PROTECTED] surf utopia internet services
Re: log rotation
> If you don't mind a second or two of down time then you can use > something like this in newsyslog.conf as a restart command: > > "apachectl stop;sleep 1;apachctl start;sleep 10;apachectl start" > > The first sleep gives apache a second to finish active requests before > trying to start again. The second sleep and start is to catch the case > where the first start fails because apache is still running. I have a script which does the following: + rotates logs + calls apachectl stop (twice, with sleep 2 after each call) + calls apachectl stop and greps the output to make sure it is stopped (looks for 'not running') + if I don't find not running, pages me + run apachectl startssl This is all in a wrapper script which then calls awstats after a successful rotate and restart. Works for us. JohnM -- john mendenhall [EMAIL PROTECTED] surf utopia internet services
Re: new openbsd 4.0 server, panic on ufsdirhash
On Mon, 14 May 2007, Joachim Schipper wrote: > > We have done a low level disk format using an ultimate > > boot cd. Didn't output any errors. Did this on both > > drives in the system. Took a very long time. > > > > Then, tried to install the OS. Received a panic on > > installing the comp set, ffs_valloc dup alloc. > > Reconfigured to have all install go to one drive. > > Same error, different inode. Tried all on other drive, > > same error, different inode. Kept trying it over and > > over. Always panicked on comp set. Always same error > > of ffs_valloc dup alloc. Always a different inode. > > > > I am unable to copy in the actual error. I just have > > this on a monitor in the room. No console capability. > > > > Same dmesg as before in this thread. I can post again > > if needed. > > > > My question is, to debug this, or fix it, do I need > > to start swapping out cables, hard disks, motherboard, > > etc? Any hints or suggestions are appreciated. > > Running memtest86 is pretty painless, so that's usually a good first > step. Already done that. No errors. See previous thread, subject 'openbsd 4.0 server, new setup, getting panics', dated 5/1-5/3. JohnM -- john mendenhall [EMAIL PROTECTED] surf utopia internet services
Re: new openbsd 4.0 server, panic on ufsdirhash
> Or, perhaps, the drive is just going bad. I would have > expected errors on installing the os if that were the > case. We have done a low level disk format using an ultimate boot cd. Didn't output any errors. Did this on both drives in the system. Took a very long time. Then, tried to install the OS. Received a panic on installing the comp set, ffs_valloc dup alloc. Reconfigured to have all install go to one drive. Same error, different inode. Tried all on other drive, same error, different inode. Kept trying it over and over. Always panicked on comp set. Always same error of ffs_valloc dup alloc. Always a different inode. I am unable to copy in the actual error. I just have this on a monitor in the room. No console capability. Same dmesg as before in this thread. I can post again if needed. My question is, to debug this, or fix it, do I need to start swapping out cables, hard disks, motherboard, etc? Any hints or suggestions are appreciated. Thanks in advance! JohnM -- john mendenhall [EMAIL PROTECTED] surf utopia internet services
Re: new openbsd 4.0 server, panic on ufsdirhash
Tim, > > > - Quote -- > > > Date: Mon, 7 May 2007 10:29:50 -0700 > > > From: "John Mendenhall" <[EMAIL PROTECTED]> > > > To: "Artur Grabowski" <[EMAIL PROTECTED]> > > > CC: misc@openbsd.org > > > Subject: Re: new openbsd 4.0 server, panic on ufsdirhash > > > > > > Artur, > > > > > > We have done a forced fsck on the partition with the > > > error. The problem is, there is no data other than > > > the openbsd install. All I was trying to do was load > > > the source from the openbsd cd into /usr/src. > > > > > > I don't need to restore since this is a new machine. > > > I have not done anything to it. > > > > > > I'll just reinstall the entire thing. Unless someone > > > wants me to try something else. > > > > > > Thanks! > > > > > > JohnM > > > --- /QUOTE > > > > > > John, > > > I've heard, and seen, a lot of odd problems that can't be > > duplicated > > > with the same error when there's either of the following true. > > > > > > 1) overclocked hardware > > > 2) bad system memory > > > > > > I'm doubting your system memory, but I'm curious about your > > > overclocking. > > > > > > I don't think I've followed very carefully what you've already > > tried, > > > and wonder if the mindset has ever drifted away from Hard Drives > > and > > > ATA controllers. > > > > > > Another thread suggested catting /dev/ad0s1 >/dev/null and seeing > > how > > > many errors you get. If you get errors, it might point to what > > can't > > > be read (and maybe can't be written then). You might have to use > > > another tool, but you should get the jist of what I'm trying to > > > suggest. > > > > All hardware is as received, no overclocking is being done. > > > > The system memory was the first issue we had. I have set > > the bios such that the system memory gives no errors on very > > long memtest runs. > > > > Currently, we are running a low level format of the two disks. > > No errors yet, but will run another day or so. > > > > Then, we'll reinstall the os and see how it goes. > > 'cat'ting the drive is simply reading data from the surface and sending > it to the bitbucket, so we can see if we can read the surface of the > drive without errors. > > A low-level format is an interesting twist, and I would like to see if > that helps. I've witnessed myself a drive "with bad blocks" dissapear > after a high-level format. It was the oddest of things, the FS itself > was corrupted and a disk check didn't help the situation. Maybe it was > a glitch, I don't know. I put that drive back into rotation. We'll see how it goes. If I still get errors, I'll try to cat the drive to devnull and see what happens. It would be nice to get disk errors instead of a panic, though. Perhaps anything in a log file, or a console message. But, panic just stops everything and it's difficult to tell what actually happened. Or, perhaps, the drive is just going bad. I would have expected errors on installing the os if that were the case. Thanks! JohnM -- john mendenhall [EMAIL PROTECTED] surf utopia internet services
Re: new openbsd 4.0 server, panic on ufsdirhash
Tim, On Tue, 08 May 2007, Tim Judd wrote: > - Quote -- > Date: Mon, 7 May 2007 10:29:50 -0700 > From: "John Mendenhall" <[EMAIL PROTECTED]> > To: "Artur Grabowski" <[EMAIL PROTECTED]> > CC: misc@openbsd.org > Subject: Re: new openbsd 4.0 server, panic on ufsdirhash > > Artur, > > We have done a forced fsck on the partition with the > error. The problem is, there is no data other than > the openbsd install. All I was trying to do was load > the source from the openbsd cd into /usr/src. > > I don't need to restore since this is a new machine. > I have not done anything to it. > > I'll just reinstall the entire thing. Unless someone > wants me to try something else. > > Thanks! > > JohnM > --- /QUOTE > > John, > I've heard, and seen, a lot of odd problems that can't be duplicated > with the same error when there's either of the following true. > > 1) overclocked hardware > 2) bad system memory > > I'm doubting your system memory, but I'm curious about your > overclocking. > > I don't think I've followed very carefully what you've already tried, > and wonder if the mindset has ever drifted away from Hard Drives and > ATA controllers. > > Another thread suggested catting /dev/ad0s1 >/dev/null and seeing how > many errors you get. If you get errors, it might point to what can't > be read (and maybe can't be written then). You might have to use > another tool, but you should get the jist of what I'm trying to > suggest. All hardware is as received, no overclocking is being done. The system memory was the first issue we had. I have set the bios such that the system memory gives no errors on very long memtest runs. Currently, we are running a low level format of the two disks. No errors yet, but will run another day or so. Then, we'll reinstall the os and see how it goes. Why would I want to cat /dev/ad0s1? Or, are you referring to the actual drive, which is /dev/wd0? > Good luck. Thanks! JohnM -- john mendenhall [EMAIL PROTECTED] surf utopia internet services
Re: new openbsd 4.0 server, panic on ufsdirhash
Artur, > Have you done forced fsck of the partitions? This sounds like a > problem with the data you have on disk. It would be even nicer if you > could update to a newer fsck because it has been updated to deal with > many new strange corner cases we've been seeing. Although, that might > or might not require a fully -current system, I'm not fully aware of > everything that has been going in fsck, but some of the ffs2 support > might have messed things up. > > We've seen one of those panics recently on an important OpenBSD > infrastructure machine and that led to a lot of fsck work (since > fsck didn't catch the particular problem). But on production > machines we deal with filesystem corruption by simply dumping the > filesystem and restoring it from scratch. You might want to try > that as well. We have done a forced fsck on the partition with the error. The problem is, there is no data other than the openbsd install. All I was trying to do was load the source from the openbsd cd into /usr/src. I don't need to restore since this is a new machine. I have not done anything to it. I'll just reinstall the entire thing. Unless someone wants me to try something else. Thanks! JohnM -- john mendenhall [EMAIL PROTECTED] surf utopia internet services
Re: new openbsd 4.0 server, panic on ufsdirhash
I have yet to receive any response to the panics I have been experiencing. Is there something else I need to provide that will get me pointed in the right direction? Are there tools available to test the connection to the hard drive, or to test the hard drive itself? I used format when administering a sun box, which did a halfway decent job of running through the whole disk in analysis mode, which could test without destrying data, and could test while destroying data. What is available for openbsd? Or, can I just use something like the ultimate boot cd and run tests on the hard disks? Thanks in advance! JohnM On Fri, 04 May 2007, John Mendenhall wrote: > > Does this indicate I have a bad drive? Or, does it > > just need fsck run on it? I just installed openbsd 4.0 > > on this box a few days ago. It rebuilt the file systems > > from scratch. Do I need to redo everything? > > > > Or, do I need to start looking at hardware problems with > > the drive or the motherboard? > > > > Please let me know the next step to run that will help > > me get to a stable system. > > I tried viewing the file in error. I could run ls, but > not ls -l. > I went into single user mode and fscked the file system. > I removed the file. I did not get the inode or anything else > before removing it. > > I tried running the copy source command. > cd /usr/src; tar xzf /mnt/src.tar.gz > Another panic. > > panic #3: > - > mode = 0100644, inum = 106368, fs = /usr > panic: ffs_valloc: dup alloc > Stopped at Debugger+0x4: leave > RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC! > DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION! > ddb> > Debugger(d0716864,5080,e9e21b40,d6bb671c,d1265000) at Debugger+0x4 > panic(d06736fc,81a4,19f80,d12650d4,d1267e00) at panic+0x63 > ffs_inode_alloc(d6ab69dc,81a4,d6c141e0,e9e21b94) at ffs_inode_alloc+0x11b > ufs_makeinode(81a4,d6ab8ea0,e9e21e28,e9e21e3c) at ufs_makeinode+0x78 > ufs_create(e9e21d08,d6ab8ea0,d6b33710,d6c141e0,d07171c0) at ufs_create+0x26 > VOP_CREATE(d6ab8ea0,e9e21e28,e9e21e3c,e9e21d58) at VOP_CREATE+0x34 > vn_open(e9e21e18,e02,1a4,d6b33710) at vn_open+0xdf > sys_open(d6b33710,e9e21f68,e9e21f58,0,0) at sys_open+0xdb > syscall() at syscall+0x2ea > --- syscall (number 5) --- > 0x1c00e3e1: > ddb> >PID PPID PGRPUID S FLAGS WAIT COMMAND > 15475 20392 20392 0 3 0x4086 pipewr gzip > *20392 2075 20392 0 7 0x4006 tar > 20997 15943 20997 1000 3 0x4086 ttyin csh > 15943 9609 9609 1000 3 0x184 select sshd > 9609 14206 9609 0 3 0x4084 netio sshd > 14658 1 14658 0 3 0x4086 ttyin getty > 4737 1 4737 0 3 0x4086 ttyin getty > 13556 1 13556 0 3 0x4086 ttyin getty > 30631 1 30631 0 3 0x4086 ttyin getty > 2075 1 2075 1000 3 0x4086 pause csh > 6223 1 6223 0 30x84 select cron > 14206 1 14206 0 30x84 select sshd > 14369 24346 24346 83 3 0x184 poll ntpd > 24346 1 24346 0 30x84 poll ntpd > 1115 7685 7685 73 2 0x184 syslogd > 7685 1 7685 0 30x8c netio syslogd > 13 0 0 0 30x100204 crypto_wa crypto > 12 0 0 0 30x100204 aiodoned aiodoned > 11 0 0 0 30x100204 syncer update > 10 0 0 0 30x100204 cleanercleaner > 9 0 0 0 30x100204 reaper reaper > 8 0 0 0 30x100204 pgdaemon pagedaemon > 7 0 0 0 30x100204 pftm pfpurge > 6 0 0 0 30x100204 wait wskbd_hotkey > 5 0 0 0 30x100204 usbtsk usbtask > 4 0 0 0 30x100204 usbevt usb0 > 3 0 0 0 30x100204 apmev apm0 > 2 0 0 0 30x100204 kmallockmthread > 1 0 1 0 3 0x4084 wait init > 0 -1 0 0 3 0x80204 scheduler swapper > ddb> > - > > So, back to my real question. > Does this indicate a bad
Re: new openbsd 4.0 server, panic on ufsdirhash
gt; mainbus0 (root)
> bios0 at mainbus0: AT/286+(00) BIOS, date 02/08/02, BIOS32 rev. 0 @ 0xfdb30,
> SMBIOS rev. 2.3 @ 0xf0630 (24 entries)
> bios0: ECS M821LR
> apm0 at bios0: Power Management spec V1.2
> apm0: AC on, battery charge unknown
> apm0: flags 30102 dobusy 0 doidle 1
> pcibios0 at bios0: rev 2.1 @ 0xf/0x1
> pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf8860/112 (5 entries)
> pcibios0: PCI Interrupt Router at 000:07:0 ("VIA VT82C686 ISA" rev 0x00)
> pcibios0: PCI bus #1 is the last bus
> bios0: ROM list: 0xc/0xc000 0xcc000/0x5800 0xd1800/0x2800
> cpu0 at mainbus0
> pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
> pchb0 at pci0 dev 0 function 0 "VIA VT8361 PCI" rev 0x00
> ppb0 at pci0 dev 1 function 0 "VIA VT8361 AGP" rev 0x00
> pci1 at ppb0 bus 1
> vga1 at pci1 dev 0 function 0 "Trident CyberBlade i1" rev 0x00
> wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
> wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
> pcib0 at pci0 dev 7 function 0 "VIA VT82C686 ISA" rev 0x40
> pciide0 at pci0 dev 7 function 1 "VIA VT82C571 IDE" rev 0x06: ATA100, channel
> 0 configured to compatibility, channel 1 configured to compatibility
> wd0 at pciide0 channel 0 drive 0:
> wd0: 16-sector PIO, LBA48, 117800MB, 241254720 sectors
> wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5
> wd1 at pciide0 channel 1 drive 0:
> wd1: 16-sector PIO, LBA48, 114473MB, 234441648 sectors
> atapiscsi0 at pciide0 channel 1 drive 1
> scsibus0 at atapiscsi0: 2 targets
> cd0 at scsibus0 targ 0 lun 0: SCSI0 5/cdrom
> removable
> wd1(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
> cd0(pciide0:1:1): using PIO mode 4, Ultra-DMA mode 2
> uhci0 at pci0 dev 7 function 2 "VIA VT83C572 USB" rev 0x16: irq 12
> usb0 at uhci0: USB revision 1.0
> uhub0 at usb0
> uhub0: VIA UHCI root hub, rev 1.00/1.00, addr 1
> uhub0: 2 ports with 2 removable, self powered
> viaenv0 at pci0 dev 7 function 4 "VIA VT82C686 SMBus" rev 0x40
> auvia0 at pci0 dev 7 function 5 "VIA VT82C686 AC97" rev 0x50: irq 10
> ac97: codec id 0x49434511 (ICEnsemble ICE1232)
> ac97: codec features headphone, 18 bit DAC, 18 bit ADC, KS Waves 3D
> audio0 at auvia0
> "VIA VT82C686 Modem" rev 0x30 at pci0 dev 7 function 6 not configured
> rl0 at pci0 dev 10 function 0 "Realtek 8139" rev 0x10: irq 12, address
> 00:e0:06:f6:bf:3e
> rlphy0 at rl0 phy 0: RTL internal PHY
> isa0 at pcib0
> isadma0 at isa0
> pckbc0 at isa0 port 0x60/5
> pckbd0 at pckbc0 (kbd slot)
> pckbc0: using irq 1 for kbd slot
> wskbd0 at pckbd0: console keyboard, using wsdisplay0
> pcppi0 at isa0 port 0x61
> midi0 at pcppi0:
> spkr0 at pcppi0
> lpt0 at isa0 port 0x378/4 irq 7
> npx0 at isa0 port 0xf0/16: using exception 16
> pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
> fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
> biomask fb6d netmask fb6d ttymask fbef
> pctr: user-level cycle counter enabled
> mtrr: Pentium Pro MTRR support
> dkcsum: wd0 matches BIOS drive 0x80
> dkcsum: wd1 matches BIOS drive 0x81
> root on wd0a
> rootdev=0x0 rrootdev=0x300 rawdev=0x302
> WARNING: / was not properly unmounted
> -
--
john mendenhall
[EMAIL PROTECTED]
surf utopia
internet services
new openbsd 4.0 server, panic on ufsdirhash
4.0 (GENERIC) #1107: Sat Sep 16 19:15:58 MDT 2006
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: AMD Duron(tm) Processor ("AuthenticAMD" 686-class, 64KB L2 cache) 1.21
GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,S
SE
real mem = 528052224 (515676K)
avail mem = 473726976 (462624K)
using 4256 buffers containing 26505216 bytes (25884K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(00) BIOS, date 02/08/02, BIOS32 rev. 0 @ 0xfdb30,
SMBIOS rev. 2.3 @ 0xf0630 (24 entries)
bios0: ECS M821LR
apm0 at bios0: Power Management spec V1.2
apm0: AC on, battery charge unknown
apm0: flags 30102 dobusy 0 doidle 1
pcibios0 at bios0: rev 2.1 @ 0xf/0x1
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf8860/112 (5 entries)
pcibios0: PCI Interrupt Router at 000:07:0 ("VIA VT82C686 ISA" rev 0x00)
pcibios0: PCI bus #1 is the last bus
bios0: ROM list: 0xc/0xc000 0xcc000/0x5800 0xd1800/0x2800
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "VIA VT8361 PCI" rev 0x00
ppb0 at pci0 dev 1 function 0 "VIA VT8361 AGP" rev 0x00
pci1 at ppb0 bus 1
vga1 at pci1 dev 0 function 0 "Trident CyberBlade i1" rev 0x00
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
pcib0 at pci0 dev 7 function 0 "VIA VT82C686 ISA" rev 0x40
pciide0 at pci0 dev 7 function 1 "VIA VT82C571 IDE" rev 0x06: ATA100, channel
0 configured to compatibility, channel 1 configured to compatibility
wd0 at pciide0 channel 0 drive 0:
wd0: 16-sector PIO, LBA48, 117800MB, 241254720 sectors
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5
wd1 at pciide0 channel 1 drive 0:
wd1: 16-sector PIO, LBA48, 114473MB, 234441648 sectors
atapiscsi0 at pciide0 channel 1 drive 1
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: SCSI0 5/cdrom
removable
wd1(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
cd0(pciide0:1:1): using PIO mode 4, Ultra-DMA mode 2
uhci0 at pci0 dev 7 function 2 "VIA VT83C572 USB" rev 0x16: irq 12
usb0 at uhci0: USB revision 1.0
uhub0 at usb0
uhub0: VIA UHCI root hub, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
viaenv0 at pci0 dev 7 function 4 "VIA VT82C686 SMBus" rev 0x40
auvia0 at pci0 dev 7 function 5 "VIA VT82C686 AC97" rev 0x50: irq 10
ac97: codec id 0x49434511 (ICEnsemble ICE1232)
ac97: codec features headphone, 18 bit DAC, 18 bit ADC, KS Waves 3D
audio0 at auvia0
"VIA VT82C686 Modem" rev 0x30 at pci0 dev 7 function 6 not configured
rl0 at pci0 dev 10 function 0 "Realtek 8139" rev 0x10: irq 12, address
00:e0:06:f6:bf:3e
rlphy0 at rl0 phy 0: RTL internal PHY
isa0 at pcib0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pcppi0 at isa0 port 0x61
midi0 at pcppi0:
spkr0 at pcppi0
lpt0 at isa0 port 0x378/4 irq 7
npx0 at isa0 port 0xf0/16: using exception 16
pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
biomask fb6d netmask fb6d ttymask fbef
pctr: user-level cycle counter enabled
mtrr: Pentium Pro MTRR support
dkcsum: wd0 matches BIOS drive 0x80
dkcsum: wd1 matches BIOS drive 0x81
root on wd0a
rootdev=0x0 rrootdev=0x300 rawdev=0x302
WARNING: / was not properly unmounted
-
--
john mendenhall
[EMAIL PROTECTED]
surf utopia
internet services
Re: openbsd 4.0 server, new setup, getting panics
> > The symptoms you describe sound like classic hardware problems,
> > however, I see a couple things worthy of note in your dmesg:
> >
> > > -
> > > OpenBSD 4.0 (GENERIC) #1107: Sat Sep 16 19:15:58 MDT 2006
> > > [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
> > > cpu0: AMD Duron(tm) Processor ("AuthenticAMD" 686-class, 64KB L2 cache)
> > > 1.61 GHz
> > > cpu0:
> > > FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
> >
> > No idea why, but I've seen a number of AMD systems of that
> > vintage which were temperamental about their RAM. Wasn't that
> > the RAM was bad...but the system bus timing was off in some
> > way.
> >
> > Curiously, these machines had more-than-usual amounts of clock
> > speed control, and they seemed to settle down by cranking down
> > the clock speed a tad. You won't miss it, really.
>
> I have set the front side bus to be 200, instead of 266 and
> am re-running the memory tests.
I was still getting errors after decreasing the fsb speed.
I modified the bios as follows:
- sdram timing by spd enabled
- auto detect pci clock enabled
- clk spread spectrum enabled
I retested the memory, ran it overnight using memtest86+.
No errors.
I don't know which of the above fixed the problem.
However, it is not causing any memory errors now.
Thanks so much for the pointers.
JohnM
--
john mendenhall
[EMAIL PROTECTED]
surf utopia
internet services
Re: openbsd 4.0 server, new setup, getting panics
I had only one memory stick in there. I swapped it out
with another memory stick, still errors. I swapped it
out with a third, still errors. Possibly all memory is
subpar. It was just what I had laying around. All sticks
could be bad.
> The symptoms you describe sound like classic hardware problems,
> however, I see a couple things worthy of note in your dmesg:
>
> > -
> > OpenBSD 4.0 (GENERIC) #1107: Sat Sep 16 19:15:58 MDT 2006
> > [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
> > cpu0: AMD Duron(tm) Processor ("AuthenticAMD" 686-class, 64KB L2 cache)
> > 1.61 GHz
> > cpu0:
> > FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
>
> No idea why, but I've seen a number of AMD systems of that
> vintage which were temperamental about their RAM. Wasn't that
> the RAM was bad...but the system bus timing was off in some
> way.
>
> Curiously, these machines had more-than-usual amounts of clock
> speed control, and they seemed to settle down by cranking down
> the clock speed a tad. You won't miss it, really.
I have set the front side bus to be 200, instead of 266 and
am re-running the memory tests.
> ...
> > rl0 at pci0 dev 10 function 0 "Realtek 8139" rev 0x10: irq 12, address
> > 00:e0:06:f6:bf:3e
> > rlphy0 at rl0 phy 0: RTL internal PHY
> ...
>
> That looks bad. IRQ12 is used by mouse hardware...
No mouse plugged in or used. Never will be.
JohnM
--
john mendenhall
[EMAIL PROTECTED]
surf utopia
internet services
Re: openbsd 4.0 server, new setup, getting panics
> PS a dmesg would be useful...
Sorry! I forgot the dmesg.
-
OpenBSD 4.0 (GENERIC) #1107: Sat Sep 16 19:15:58 MDT 2006
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: AMD Duron(tm) Processor ("AuthenticAMD" 686-class, 64KB L2 cache) 1.61 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
real mem = 528052224 (515676K)
avail mem = 473726976 (462624K)
using 4256 buffers containing 26505216 bytes (25884K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(00) BIOS, date 02/08/02, BIOS32 rev. 0 @ 0xfdb30,
SMBIOS rev. 2.3 @ 0xf0630 (24 entries)
bios0: ECS M821LR
apm0 at bios0: Power Management spec V1.2
apm0: AC on, battery charge unknown
apm0: flags 30102 dobusy 0 doidle 1
pcibios0 at bios0: rev 2.1 @ 0xf/0x1
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf8860/112 (5 entries)
pcibios0: PCI Interrupt Router at 000:07:0 ("VIA VT82C686 ISA" rev 0x00)
pcibios0: PCI bus #1 is the last bus
bios0: ROM list: 0xc/0xc000 0xcc000/0x5800 0xd1800/0x2800
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "VIA VT8361 PCI" rev 0x00
ppb0 at pci0 dev 1 function 0 "VIA VT8361 AGP" rev 0x00
pci1 at ppb0 bus 1
vga1 at pci1 dev 0 function 0 "Trident CyberBlade i1" rev 0x00
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
pcib0 at pci0 dev 7 function 0 "VIA VT82C686 ISA" rev 0x40
pciide0 at pci0 dev 7 function 1 "VIA VT82C571 IDE" rev 0x06: ATA100, channel 0
configured to compatibility, channel 1 configured to compatibility
wd0 at pciide0 channel 0 drive 0:
wd0: 16-sector PIO, LBA48, 117800MB, 241254720 sectors
wd1 at pciide0 channel 0 drive 1:
wd1: 16-sector PIO, LBA48, 114473MB, 234441648 sectors
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5
wd1(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 5
atapiscsi0 at pciide0 channel 1 drive 1
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: SCSI0 5/cdrom removable
cd0(pciide0:1:1): using PIO mode 4, Ultra-DMA mode 2
uhci0 at pci0 dev 7 function 2 "VIA VT83C572 USB" rev 0x16: irq 12
usb0 at uhci0: USB revision 1.0
uhub0 at usb0
uhub0: VIA UHCI root hub, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1 at pci0 dev 7 function 3 "VIA VT83C572 USB" rev 0x16: irq 12
usb1 at uhci1: USB revision 1.0
uhub1 at usb1
uhub1: VIA UHCI root hub, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
viaenv0 at pci0 dev 7 function 4 "VIA VT82C686 SMBus" rev 0x40
auvia0 at pci0 dev 7 function 5 "VIA VT82C686 AC97" rev 0x50: irq 10
ac97: codec id 0x49434511 (ICEnsemble ICE1232)
ac97: codec features headphone, 18 bit DAC, 18 bit ADC, KS Waves 3D
audio0 at auvia0
rl0 at pci0 dev 10 function 0 "Realtek 8139" rev 0x10: irq 12, address
00:e0:06:f6:bf:3e
rlphy0 at rl0 phy 0: RTL internal PHY
isa0 at pcib0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pcppi0 at isa0 port 0x61
midi0 at pcppi0:
spkr0 at pcppi0
lpt0 at isa0 port 0x378/4 irq 7
npx0 at isa0 port 0xf0/16: using exception 16
pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
biomask fb6d netmask fb6d ttymask fbef
pctr: user-level cycle counter enabled
mtrr: Pentium Pro MTRR support
dkcsum: wd0 matches BIOS drive 0x80
dkcsum: wd1 matches BIOS drive 0x81
root on wd0a
rootdev=0x0 rrootdev=0x300 rawdev=0x302
-
--
john mendenhall
[EMAIL PROTECTED]
surf utopia
internet services
openbsd 4.0 server, new setup, getting panics
OpenBSD Gurus, I just setup a new openbsd 4.0 server. No problems with install. As root, I created a new user on the console. I logged out and logged back in as new user. All okay. I remotely logged in as new user, using ssh. Asked for password, I gave it, it showed the message of the day, then the server panicked. panic: amap_wipeout: corrupt amap (hand copied off console screen) It rebooted. I logged into the server remotely. It worked fine. I started up lynx to start downloading packages. As it loaded the package page (btw, the 4.0 link is missing), it panicked again. panic: uvm_fault (0xd6c09974, ...) -> e kernel page fault trap code = 0 (hand copied off console screen) I have reviewed the patches for 4.0 and see no connection between these problems and the patches. I have searched the net for anything relating to this. I could not find anything relevant. My initial assumption is, there must be a hardware problem. How do I determine where the problem is so I can start diagnosing it? Thanks in advance for any assistance or pointers or search terms to use. JohnM -- john mendenhall [EMAIL PROTECTED] surf utopia internet services
