openBSD 3.9 on hp/comapq proliant 8000

classic Classic list List threaded Threaded
16 messages Options
Reply | Threaded
Open this post in threaded view
|

openBSD 3.9 on hp/comapq proliant 8000

Czesław Liebert
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

my h/w is:
hp/comapq proliant 8000:
- - 8x Xeon 550MHz
- - 8GB ram
- - compaq array controller 4250ES
- - 1x intel 82558b lan
- - 1x intel 82559 lan
- - 8x 18GB scsi u160

according to harware support list for i386 found on BSD site, all of
that h/w is supported in version 3.9. it should, but it does not. i
tried 3.8, 3.9 and 4.0b - couldn't get it to run. i used boot floppy B -
according to the manual this one contains proper stuff.

at kernel start the hd0 device is shown properly, but afterwards kernel
does not see the 4250es array controller nor intel lan cards.

any ideas on how to run openBSD on this machine? i hope it can be done
somehow, as i really do not want to switch to another OS, been using
openBSD for years now...

thanks in advance for a quick reply
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFBTG03VOnD+tUq3sRAtFPAJ9eKfjZINazpLxDhALMRsGQZd/k3QCfcfSx
t6096rCDhgUkA7tzETi//eY=
=yKiH
-----END PGP SIGNATURE-----

Reply | Threaded
Open this post in threaded view
|

Re: openBSD 3.9 on hp/comapq proliant 8000

dimitry (Bugzilla)
Czes3aw Liebert wrote:
> my h/w is:
> hp/comapq proliant 8000:
> - 8x Xeon 550MHz
> - 8GB ram
> - compaq array controller 4250ES
> - 1x intel 82558b lan
> - 1x intel 82559 lan
> - 8x 18GB scsi u160

Try to get at least a dmesg and post it here, see:
http://www.openbsd.org/faq/faq4.html#getdmesg

Reply | Threaded
Open this post in threaded view
|

Re: openBSD 3.9 on hp/comapq proliant 8000

Czesław Liebert
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dimitry Andric napisa3(a):
> Try to get at least a dmesg and post it here, see:
> http://www.openbsd.org/faq/faq4.html#getdmesg
>

i get the same result on every kernel i used:

OpenBSD 3.9 (RAMDISK_CD) #1025: Thu Mar  2 02:43:29 MST 2006
    [hidden email]:/usr/src/sys/arch/i386/compile/RAMDISK_CD
cpu0: Intel Pentium III Xeon ("GenuineIntel" 686-class, 2048KB L2 cache)
550 MHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
real mem  = 4026081280 (3931720K)
avail mem = 3669291008 (3583292K)
using 4278 buffers containing 201408512 bytes (196688K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(00) BIOS, date 12/31/99, BIOS32 rev. 0 @ 0xf0000
pcibios0 at bios0: rev 2.1 @ 0xf0000/0x2000
pcibios0: PCI BIOS has 14 Interrupt Routing table entries
pcibios0: PCI Interrupt Router at 000:15:0 ("ServerWorks OSB4" rev 0x00)
pcibios0: PCI bus #0 is the last bus
bios0: ROM list: 0xc0000/0x8000 0xc8000/0x4000 0xcc000/0x800
0xe8000/0x6000! 0xee000/0x2000!
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
ahc0 at pci0 dev 4 function 0 "Adaptec AHA-2940U2 U2" rev 0x00: irq 5
scsibus0 at ahc0: 16 targets
ahc0: target 6 using 8bit transfers
ahc0: target 6 using asynchronous transfers
st0 at scsibus0 targ 6 lun 0: <QUANTUM, DLT7000, 2255> SCSI2
1/sequential removable
st0: drive empty or not ready
"Compaq PCI Hotplug" rev 0x11 at pci0 dev 11 function 0 not configured
"Compaq Netelligent ASMC" rev 0x00 at pci0 dev 12 function 0 not configured
vga1 at pci0 dev 13 function 0 "ATI Mach64 GV" rev 0x7a
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
pcib0 at pci0 dev 15 function 0 "ServerWorks OSB4" rev 0x4d
pciide0 at pci0 dev 15 function 1 vendor "ServerWorks", unknown product
0x0210 rev 0x4a: DMA (unsupported), channel 0 configured to
compatibility, channel 1 configured to compatibility
atapiscsi0 at pciide0 channel 0 drive 0
scsibus1 at atapiscsi0: 2 targets
cd0 at scsibus1 targ 0 lun 0: <COMPAQ, CD-224E, 9.0B> SCSI0 5/cdrom
removable
pciide0: channel 1 ignored (not responding; disabled or no drives?)
vendor "Corrollary", unknown product 0x1117 (class memory subclass RAM,
rev 0x05) at pci0 dev 20 function 0 not configured
vendor "Corrollary", unknown product 0x1117 (class memory subclass RAM,
rev 0x05) at pci0 dev 20 function 1 not configured
pchb0 at pci0 dev 25 function 0 vendor "Compaq", unknown product 0x6010
rev 0x01
pchb1 at pci0 dev 26 function 0 vendor "Compaq", unknown product 0x6010
rev 0x01
pchb2 at pci0 dev 27 function 0 vendor "Compaq", unknown product 0x6010
rev 0x01
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
npx0 at isa0 port 0xf0/16: using exception 16
pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec
biomask ffe5 netmask ffe5 ttymask ffe7
rd0: fixed, 3800 blocks
root on rd0a
rootdev=0x1100 rrootdev=0x2f00 rawdev=0x2f02
fd0: timeout (st0 20<seek_cmplt> cyl 0)
fd0a: soft error reading fsbn 0
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFBUhK3VOnD+tUq3sRAoLJAJ9igmnaCtlQgeRhaVo3isERGR8ovACfQ9nh
YE8qhWyDxkwJ0TW3Q1gqSt4=
=b/BN
-----END PGP SIGNATURE-----

Reply | Threaded
Open this post in threaded view
|

Re: openBSD 3.9 on hp/comapq proliant 8000

Stuart Henderson
On 2006/09/11 13:28, Czes?aw Liebert wrote:
> pcibios0: PCI bus #0 is the last bus

looks like you're missing some busses then, if you have other
PCI slots, you might try swapping cards around because some might
be attached to a working bus. If not or this is no help and you're
up to some hacking the following might help. If not it might save
someone else some time finding the information..

> pchb0 at pci0 dev 25 function 0 vendor "Compaq", unknown product 0x6010 rev 0x01
> pchb1 at pci0 dev 26 function 0 vendor "Compaq", unknown product 0x6010 rev 0x01
> pchb2 at pci0 dev 27 function 0 vendor "Compaq", unknown product 0x6010 rev 0x01

0x6010 is a compaq hotplug pci bridge, the other busses must be
behind this.

FreeBSD sets it up something like the serverworks (rcc) pchb with
busses attached (OpenBSD does this in /usr/src/sys/arch/i386/pci/pchb.c
e.g. around "case PCI_VENDOR_RCC") but bus number is on a different
config register on the compaq, 0xc8 instead of 0x44 -
http://fxr.watson.org/fxr/source/i386/pci/pci_bus.c#L280

Reply | Threaded
Open this post in threaded view
|

Re: openBSD 3.9 on hp/comapq proliant 8000

Czesław Liebert
In reply to this post by Czesław Liebert
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Tom Cosgrove napisa3(a):

> There are two things you could try:
>
> 1. Try a CD (that will have more drivers on it than any of the floppies);
>
> 2. Try a different floppy disk, as it looks like this one is having
>    problems in your server (could even be the floppy disk drive).
>
>
> And I wouldn't bother with 3.9 or earlier at this stage in the release
> cycle: the current snapshot (I think it's September 1 or something
> like that) is effectively a release candidate - even if there are
> more bug fixes made before the release, it will be a very simple
> upgrade to the actual 4.0 release.
>
> Yes, I saw you said "4.0b" but there is no such version :)  I assume
> you mean the 9/1 snapshot, but I can't be certain.
>
> And as I say, really do try a CD boot.

I have also tried the cd boot - wasn't much of a help. The floppy is ok,
i needed to write dmesg to floppy and mounted the drive before inserting
a blank diskette. and yes, by saying 4.0b i really meant the lates
snapshot.
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFBV7j3VOnD+tUq3sRAhi1AJ4ovMw2Lv75z/lMlhdEKY4M5I2zCgCfZ4WX
OG0u42Nszn6qUxihuNMIbxY=
=tuPY
-----END PGP SIGNATURE-----

Reply | Threaded
Open this post in threaded view
|

Re: openBSD 3.9 on hp/comapq proliant 8000

Czesław Liebert
In reply to this post by Stuart Henderson
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Stuart Henderson napisaE(a):

> On 2006/09/11 13:28, Czes?aw Liebert wrote:
>> pcibios0: PCI bus #0 is the last bus
>
> looks like you're missing some busses then, if you have other
> PCI slots, you might try swapping cards around because some might
> be attached to a working bus. If not or this is no help and you're
> up to some hacking the following might help. If not it might save
> someone else some time finding the information..
>
>> pchb0 at pci0 dev 25 function 0 vendor "Compaq", unknown product 0x6010 rev 0x01
>> pchb1 at pci0 dev 26 function 0 vendor "Compaq", unknown product 0x6010 rev 0x01
>> pchb2 at pci0 dev 27 function 0 vendor "Compaq", unknown product 0x6010 rev 0x01
>
> 0x6010 is a compaq hotplug pci bridge, the other busses must be
> behind this.
>
> FreeBSD sets it up something like the serverworks (rcc) pchb with
> busses attached (OpenBSD does this in /usr/src/sys/arch/i386/pci/pchb.c
> e.g. around "case PCI_VENDOR_RCC") but bus number is on a different
> config register on the compaq, 0xc8 instead of 0x44 -
> http://fxr.watson.org/fxr/source/i386/pci/pci_bus.c#L280

i can't get to this point as i can't get openBSD installer to run. as
for freeBSD i tried 6.0, 5.5, 6.1 and they all work just fine on this
machine. but i am not rally into free, thus the question here on the list.

any more ideas?
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFBV943VOnD+tUq3sRAmtHAJ0dTDDu9ORkcixgHYMNcUwleRMWrACfR7im
KLRsOJdS35+h6MGnBOD3mp4=
=BU+u
-----END PGP SIGNATURE-----

Reply | Threaded
Open this post in threaded view
|

Re: openBSD 3.9 on hp/comapq proliant 8000

Stuart Henderson
On 2006/09/11 15:07, Czes??aw Liebert wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Stuart Henderson napisaE(a):
> > On 2006/09/11 13:28, Czes?aw Liebert wrote:
> >> pcibios0: PCI bus #0 is the last bus
> >
> > looks like you're missing some busses then, if you have other
> > PCI slots, you might try swapping cards around because some might
> > be attached to a working bus. If not or this is no help and you're
> > up to some hacking the following might help. If not it might save
> > someone else some time finding the information..
> >
> >> pchb0 at pci0 dev 25 function 0 vendor "Compaq", unknown product 0x6010 rev 0x01
> >> pchb1 at pci0 dev 26 function 0 vendor "Compaq", unknown product 0x6010 rev 0x01
> >> pchb2 at pci0 dev 27 function 0 vendor "Compaq", unknown product 0x6010 rev 0x01
> >
> > 0x6010 is a compaq hotplug pci bridge, the other busses must be
> > behind this.
> >
> > FreeBSD sets it up something like the serverworks (rcc) pchb with
> > busses attached (OpenBSD does this in /usr/src/sys/arch/i386/pci/pchb.c
> > e.g. around "case PCI_VENDOR_RCC") but bus number is on a different
> > config register on the compaq, 0xc8 instead of 0x44 -
> > http://fxr.watson.org/fxr/source/i386/pci/pci_bus.c#L280
>
> i can't get to this point as i can't get openBSD installer to run. as
> for freeBSD i tried 6.0, 5.5, 6.1 and they all work just fine on this
> machine. but i am not rally into free, thus the question here on the list.
>
> any more ideas?

read my first paragraph where I mention swapping cards around.

Reply | Threaded
Open this post in threaded view
|

Re: openBSD 3.9 on hp/comapq proliant 8000

Czesław Liebert
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Stuart Henderson napisaE(a):
>
> read my first paragraph where I mention swapping cards around.
>

i did read it :) swaping PCI slots didn't help (i have only one more
such slot, as the scsi controller uses the "pci 64bit scsi extended
slot" with only two possibilities).

so "hacking" seems to be the only way out of this bush ?
iD8DBQFFBWdY3VOnD+tUq3sRAq+qAJ9I4zEc90tq62tGbVVxBxGDE53H7wCeNGi0
R2WoOmpdejXP/e23c99gFFM=
=bi4W
-----END PGP SIGNATURE-----

Reply | Threaded
Open this post in threaded view
|

panics on amd64 snapshot

Jeff Bromberger
I have a dual core Opteron system that I'm trying to make into a mail server
for my company to replace a 7 year old Linux box that's on its last leg.  I
started off using the 3.9 release of the amd64 system and ran into a few
problems (keyboard and cdrom didn't work).  It was suggested that I move to
the latest snapshot, which I did about a week ago.  That fixed the keyboard
and cdrom problems, so I began configuring the box.  I am only running a few
packages on this machine:  courier imap, postfix, fetchmail, procmail.  In
the past 2-3 days (which is how long the box has actually been active, i.e.
running all the daemons and having mail clients connect to it) I have
experienced two kernel panics.  I thought that the info from the panic would
show up in the dmesg after rebooting, but that data seems to have been
corrupted.  I could only see bits and pieces of the kernel debugger message
from the first panic.  This time around, I'm still sitting in the kernel
debugger so I am able to run a few commands if anybody has any specific
requests.

Trace shows:

panic() at panic+0x12a
amap_wipeout() at amap_wipeout+0x71
uvm_unmap_detach() at uvm_unmap_detach+0x9b
sys_munmap() at sys_munmap+0x145
syscall() at syscall+0x25c
--- syscall (number 73) ---

"ps" shows the active process was imapd.

I am running the bsd.mp kernel from the amd64 snapshot.

To ask a different question, for the hardware that I have, what would be the
most stable port/version that I could run?  Am I better off going with the
3.9 release of the i386 code vs. the current snapshot of the amd64 stuff?
My top priorities for this box are stability first and then security second,
performance is a distant third since it's just a mail server for a small
company.

Thanks,
Jeff

Reply | Threaded
Open this post in threaded view
|

Re: openBSD 3.9 on hp/comapq proliant 8000

Mark Kettenis
In reply to this post by Czesław Liebert
Hi Czeslaw,

Can you try the attached patch?  You'll have to do a make in
sys/dev/pci after you've applied the patch.

Index: dev/pci/pcidevs
===================================================================
RCS file: /cvs/src/sys/dev/pci/pcidevs,v
retrieving revision 1.1139
diff -u -p -r1.1139 pcidevs
--- dev/pci/pcidevs 25 Aug 2006 04:26:29 -0000 1.1139
+++ dev/pci/pcidevs 11 Sep 2006 15:45:17 -0000
@@ -1203,6 +1203,7 @@ product COMPAQ CSA6400 0x409c Smart Arr
 product COMPAQ CSA6400EM 0x409d Smart Array 6400 EM
 product COMPAQ CSA6422 0x409e Smart Array 6422
 product COMPAQ CSA64XX 0x0046 Smart Array 64xx
+product COMPAQ HOTPLUG_PCI 0x6010 Hotplug PCI
 product COMPAQ USB 0x7020 USB
 product COMPAQ FXP 0xa0f0 Netelligent ASMC
 product COMPAQ PCI_ISA_BRIDGE1 0xa0f3 ISA
Index: arch/i386/pci/pchb.c
===================================================================
RCS file: /cvs/src/sys/arch/i386/pci/pchb.c,v
retrieving revision 1.52
diff -u -p -r1.52 pchb.c
--- arch/i386/pci/pchb.c 13 Mar 2006 20:10:49 -0000 1.52
+++ arch/i386/pci/pchb.c 11 Sep 2006 15:45:17 -0000
@@ -220,6 +220,27 @@ pchbattach(parent, self, aux)
  break;
  }
  break;
+ case PCI_VENDOR_COMPAQ:
+ switch (PCI_PRODUCT(pa->pa_id)) {
+ case PCI_PRODUCT_COMPAQ_HOTPLUG_PCI:
+ pbnum = pci_conf_read(pa->pa_pc, pa->pa_tag, 0xc8);
+
+ /*
+ * This host bridge has a second PCI bus.
+ * Configure it.
+ */
+ neednl = 0;
+ pba.pba_busname = "pci";
+ pba.pba_iot = pa->pa_iot;
+ pba.pba_memt = pa->pa_memt;
+ pba.pba_dmat = pa->pa_dmat;
+ pba.pba_bus = pbnum;
+ pba.pba_bridgetag = NULL;
+ pba.pba_pc = pa->pa_pc;
+ printf("\n");
+ config_found(self, &pba, pchb_print);
+ }
+ break;
  case PCI_VENDOR_RCC:
  bdnum = pci_conf_read(pa->pa_pc, pa->pa_tag, 0x44);
  if (bdnum >= (sizeof(rcc_bus_visited) * 8) ||

Reply | Threaded
Open this post in threaded view
|

Re: openBSD 3.9 on hp/comapq proliant 8000

Stuart Henderson
> Can you try the attached patch?  You'll have to do a make in
> sys/dev/pci after you've applied the patch.

It might be worth pointing out: it should be enough to determine
if it works by building a normal kernel on another system and burning
it to CD. You can boot with the boot loader from a normal OpenBSD CD
(a proper one or a burned cd##.iso), swap CDs and boot the new kernel.
It will panic when it tries to mount root but hopefully before then
it will have already listed the missing devices.

If the devices show up it's worth making a ramdisk kernel so you
can install - the normal way is to follow release(8) but you may save
a bit of time if you adapt the raidframe instructions posted here a
couple of days ago.

Yes, there's some work involved, but it's fairly straightforward
and you're the one who wants the system to work :-)

Reply | Threaded
Open this post in threaded view
|

Re: openBSD 3.9 on hp/comapq proliant 8000

Czesław Liebert
In reply to this post by Mark Kettenis
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Mark Kettenis napisaE(a):
> Hi Czeslaw,
>
> Can you try the attached patch?  You'll have to do a make in
> sys/dev/pci after you've applied the patch.


Not really, because i cannot get on with the system as it does not see
my hard disks.
iD8DBQFFBcv8dj0NORdzQIoRAnfLAJ9fdjfER/q+0HtLsYvKRONJECcD2ACfXwtr
wVRlJOIxJYwl0MDEXc12anE=
=T4dV
-----END PGP SIGNATURE-----

Reply | Threaded
Open this post in threaded view
|

Re: openBSD 3.9 on hp/comapq proliant 8000

Joachim Schipper
On Mon, Sep 11, 2006 at 10:50:04PM +0200, Czes??aw Liebert wrote:
> Mark Kettenis napisaE(a):
> > Hi Czeslaw,
> >
> > Can you try the attached patch?  You'll have to do a make in
> > sys/dev/pci after you've applied the patch.
>
> Not really, because i cannot get on with the system as it does not see
> my hard disks.

You can build on a different machine, as already posted here on misc@.
That is no different from building a kernel on the machine itself. If
you have no sacrificial box handy, use qemu - the speed will suck, but
compiling only the kernel should be very doable.

                Joachim

Reply | Threaded
Open this post in threaded view
|

Re: openBSD 3.9 on hp/comapq proliant 8000

Czesław Liebert
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Joachim Schipper napisaE(a):
 > You can build on a different machine, as already posted here on misc@.
> That is no different from building a kernel on the machine itself. If
> you have no sacrificial box handy, use qemu - the speed will suck, but
> compiling only the kernel should be very doable.

this can be done; ill try tommorow morning as now i am at home and the
proliant at work. let u know how it was.

czeslaw
iD8DBQFFBdJbdj0NORdzQIoRAjykAJ4tor1lJNDGLucK5FZAxSFG5DT2XwCgyUwC
fuhGZIo8v2lQFL6KJyrsY8c=
=dRAW
-----END PGP SIGNATURE-----

Reply | Threaded
Open this post in threaded view
|

Re: openBSD 3.9 on hp/comapq proliant 8000

Czesław Liebert
In reply to this post by Czesław Liebert
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

After playing a while with swapping pci busses as for the intel lan
cards i finally came to a point where both those cards and the DEC are
recognized properly by kernel. now the dmesg have changed:

OpenBSD 3.9 (RAMDISK_CD) #1025: Thu Mar  2 02:43:29 MST 2006
    [hidden email]:/usr/src/sys/arch/i386/compile/RAMDISK_CD
cpu0: Intel Pentium III Xeon ("GenuineIntel" 686-class, 2048KB L2 cache)
550 MHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
real mem  = 4026081280 (3931720K)
avail mem = 3669291008 (3583292K)
using 4278 buffers containing 201408512 bytes (196688K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(00) BIOS, date 12/31/99, BIOS32 rev. 0 @ 0xf0000
pcibios0 at bios0: rev 2.1 @ 0xf0000/0x2000
pcibios0: PCI BIOS has 14 Interrupt Routing table entries
pcibios0: PCI Interrupt Router at 000:15:0 ("ServerWorks OSB4" rev 0x00)
pcibios0: PCI bus #2 is the last bus
bios0: ROM list: 0xc0000/0x8000 0xc8000/0x4000 0xcc000/0x800
0xe8000/0x6000! 0xee000/0x2000!
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
ppb0 at pci0 dev 2 function 0 "DEC 21154 PCI-PCI" rev 0x02
pci1 at ppb0 bus 1
fxp0 at pci1 dev 4 function 0 "Intel 8255x" rev 0x05, i82558: irq 11,
address 00:50:8b:6f:c5:fe
inphy0 at fxp0 phy 1: i82555 10/100 PHY, rev. 0
fxp1 at pci1 dev 5 function 0 "Intel 8255x" rev 0x05, i82558: irq 11,
address 00:50:8b:6f:c5:ff
inphy1 at fxp1 phy 1: i82555 10/100 PHY, rev. 0
ppb1 at pci0 dev 3 function 0 "DEC 21154 PCI-PCI" rev 0x05
pci2 at ppb1 bus 2
fxp2 at pci2 dev 4 function 0 "Intel 8255x" rev 0x08, i82559: irq 15,
address 00:02:a5:ad:e6:48
inphy2 at fxp2 phy 1: i82555 10/100 PHY, rev. 4
fxp3 at pci2 dev 5 function 0 "Intel 8255x" rev 0x08, i82559: irq 15,
address 00:02:a5:ad:e6:49
inphy3 at fxp3 phy 1: i82555 10/100 PHY, rev. 4
ahc0 at pci0 dev 4 function 0 "Adaptec AHA-2940U2 U2" rev 0x00: irq 5
scsibus0 at ahc0: 16 targets
ahc0: target 6 using 8bit transfers
ahc0: target 6 using asynchronous transfers
st0 at scsibus0 targ 6 lun 0: <QUANTUM, DLT7000, 2255> SCSI2
1/sequential removable
st0: drive empty or not ready
"Compaq PCI Hotplug" rev 0x11 at pci0 dev 11 function 0 not configured
"Compaq Netelligent ASMC" rev 0x00 at pci0 dev 12 function 0 not configured
vga1 at pci0 dev 13 function 0 "ATI Mach64 GV" rev 0x7a
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
pcib0 at pci0 dev 15 function 0 "ServerWorks OSB4" rev 0x4d
pciide0 at pci0 dev 15 function 1 vendor "ServerWorks", unknown product
0x0210 rev 0x4a: DMA (unsupported), channel 0 configured to
compatibility, channel 1 configured to compatibility
atapiscsi0 at pciide0 channel 0 drive 0
scsibus1 at atapiscsi0: 2 targets
cd0 at scsibus1 targ 0 lun 0: <COMPAQ, CD-224E, 9.0B> SCSI0 5/cdrom
removable
pciide0: no compatibility interrupt for use by channel 1
vendor "Corrollary", unknown product 0x1117 (class memory subclass RAM,
rev 0x05) at pci0 dev 20 function 0 not configured
vendor "Corrollary", unknown product 0x1117 (class memory subclass RAM,
rev 0x05) at pci0 dev 20 function 1 not configured
pchb0 at pci0 dev 25 function 0 vendor "Compaq", unknown product 0x6010
rev 0x01
pchb1 at pci0 dev 26 function 0 vendor "Compaq", unknown product 0x6010
rev 0x01
pchb2 at pci0 dev 27 function 0 vendor "Compaq", unknown product 0x6010
rev 0x01
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
npx0 at isa0 port 0xf0/16: using exception 16
pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec
biomask 77e5 netmask ffe5 ttymask ffe7
rd0: fixed, 3800 blocks
root on rd0a
rootdev=0x1100 rrootdev=0x2f00 rawdev=0x2f02

czeslaw
iD8DBQFFBmE/3VOnD+tUq3sRAhvRAJ9kGppDvTotjSbEPSjVPIXJzy3u4QCdHGaO
IBq4Bsg9uWdMcvh82xD7Vbk=
=nd2Z
-----END PGP SIGNATURE-----

Reply | Threaded
Open this post in threaded view
|

Re: panics on amd64 snapshot

Whyzzi
In reply to this post by Jeff Bromberger
Um.. where is dmesg?

On 11/09/06, Jeff Bromberger <[hidden email]> wrote:

> I have a dual core Opteron system that I'm trying to make into a mail server
> for my company to replace a 7 year old Linux box that's on its last leg.  I
> started off using the 3.9 release of the amd64 system and ran into a few
> problems (keyboard and cdrom didn't work).  It was suggested that I move to
> the latest snapshot, which I did about a week ago.  That fixed the keyboard
> and cdrom problems, so I began configuring the box.  I am only running a few
> packages on this machine:  courier imap, postfix, fetchmail, procmail.  In
> the past 2-3 days (which is how long the box has actually been active, i.e.
> running all the daemons and having mail clients connect to it) I have
> experienced two kernel panics.  I thought that the info from the panic would
> show up in the dmesg after rebooting, but that data seems to have been
> corrupted.  I could only see bits and pieces of the kernel debugger message
> from the first panic.  This time around, I'm still sitting in the kernel
> debugger so I am able to run a few commands if anybody has any specific
> requests.
>
> Trace shows:
>
> panic() at panic+0x12a
> amap_wipeout() at amap_wipeout+0x71
> uvm_unmap_detach() at uvm_unmap_detach+0x9b
> sys_munmap() at sys_munmap+0x145
> syscall() at syscall+0x25c
> --- syscall (number 73) ---
>
> "ps" shows the active process was imapd.
>
> I am running the bsd.mp kernel from the amd64 snapshot.
>
> To ask a different question, for the hardware that I have, what would be the
> most stable port/version that I could run?  Am I better off going with the
> 3.9 release of the i386 code vs. the current snapshot of the amd64 stuff?
> My top priorities for this box are stability first and then security second,
> performance is a distant third since it's just a mail server for a small
> company.
>
> Thanks,
> Jeff