Re: PCI MSI (was Re: What current Dell Systems are supported/work)
in message [EMAIL PROTECTED], wrote John Baldwin thusly... On Friday 18 January 2008 08:50:31 am John Baldwin wrote: On Friday 18 January 2008 05:30:06 am Parv wrote: There was no page fault or trap 12 message when the panic happened. After some of messages are printed (as in dmesg), kdb is entered ... ioapic0: Assigning PCI IRQ 23 to local APIC 1 msi: Assigning MSI IRQ 256 to local APIC 0 panic: blockabke sleep block (sleep mutex) msi @ /misc/src-6/sys/i386/i386/msi.c:381 cpuid: 0 kdb: stack backtrace kbd_backtrace( c0adc531,0,c0abaafd,c1020c34,c0bab700,...) at ... \ [I skipped from here to the db prompt] ... Tomorrow, rather later today, I will type up the trace output. Please let me know if you would like to see any other output that I could possibly provide. This is good enough for me to see the bug, I'll work on fixing it. There are some locking changes in the x86 interrupt code I need to MFC. Try this patch: ... Thanks much John. Your patch allowed my computer to resume normal operation without disabling MSI via hw.pci.enable_msi*. Lest I forget, mahalo for saving me from typing up the trace output. - Parv -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PCI MSI (was Re: What current Dell Systems are supported/work)
(Dropped Vivek K from recipient list; edited the URLs in my previous message.) in message [EMAIL PROTECTED], wrote John Baldwin thusly... On Thursday 17 January 2008 06:05:17 am Parv wrote: ... Speaking of MSI being on by default in recent 6-STABLE ... well, that caused my ThinkPad T61 (8859-CTO) ... dmesg: http://www103.pair.com/parv/comp/unix/freebsd/thinkpad-t61-8897-cto/sys/dmesg kernel (combined for easy perusal): http://www103.pair.com/parv/comp/unix/freebsd/thinkpad-t61-8897-cto/cf/kern/combined/T61-SMP.debug--combined /boot/device.hints: http://www103.pair.com/parv/comp/unix/freebsd/thinkpad-t61-8897-cto/cf/boot/device.hints ... to go in panic[0] ... [0] I could not save the dump for neither do I have access to serial console, nor could the file system be mounted. Missing also here is a digital camera. If anybody is interested, I could write screen down, and repeat to them. For starters, can you get the output of 'pciconf -lc'? Hi John, You can find pciconf -lc at ... http://www103.pair.com/parv/comp/unix/freebsd/thinkpad-t61-8897-cto/sys/pciconf-lc and pciconf -lv, just in case ... http://www103.pair.com/parv/comp/unix/freebsd/thinkpad-t61-8897-cto/sys/pciconf-lv Secondly, I really will need the kernel panic message. If it is a page fault (trap 12) then write down the faulting virtual address and the faulting IP. If you can scribble down any of the stack trace from DDB that would be helpful as well. There was no page fault or trap 12 message when the panic happened. After some of messages are printed (as in dmesg), kdb is entered ... ioapic0: Assigning PCI IRQ 23 to local APIC 1 msi: Assigning MSI IRQ 256 to local APIC 0 panic: blockabke sleep block (sleep mutex) msi @ /misc/src-6/sys/i386/i386/msi.c:381 cpuid: 0 kdb: stack backtrace kbd_backtrace( c0adc531,0,c0abaafd,c1020c34,c0bab700,...) at ... \ [I skipped from here to the db prompt] . . . Tomorrow, rather later today, I will type up the trace output. Please let me know if you would like to see any other output that I could possibly provide. - Parv -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PCI MSI (was Re: What current Dell Systems are supported/work)
On Friday 18 January 2008 05:30:06 am Parv wrote: (Dropped Vivek K from recipient list; edited the URLs in my previous message.) in message [EMAIL PROTECTED], wrote John Baldwin thusly... On Thursday 17 January 2008 06:05:17 am Parv wrote: ... Speaking of MSI being on by default in recent 6-STABLE ... well, that caused my ThinkPad T61 (8859-CTO) ... dmesg: http://www103.pair.com/parv/comp/unix/freebsd/thinkpad-t61-8897-cto/sys/dmesg kernel (combined for easy perusal): http://www103.pair.com/parv/comp/unix/freebsd/thinkpad-t61-8897-cto/cf/kern/combined/T61-SMP.debug--combined /boot/device.hints: http://www103.pair.com/parv/comp/unix/freebsd/thinkpad-t61-8897-cto/cf/boot/device.hints ... to go in panic[0] ... [0] I could not save the dump for neither do I have access to serial console, nor could the file system be mounted. Missing also here is a digital camera. If anybody is interested, I could write screen down, and repeat to them. For starters, can you get the output of 'pciconf -lc'? Hi John, You can find pciconf -lc at ... http://www103.pair.com/parv/comp/unix/freebsd/thinkpad-t61-8897-cto/sys/pciconf-lc and pciconf -lv, just in case ... http://www103.pair.com/parv/comp/unix/freebsd/thinkpad-t61-8897-cto/sys/pciconf-lv Secondly, I really will need the kernel panic message. If it is a page fault (trap 12) then write down the faulting virtual address and the faulting IP. If you can scribble down any of the stack trace from DDB that would be helpful as well. There was no page fault or trap 12 message when the panic happened. After some of messages are printed (as in dmesg), kdb is entered ... ioapic0: Assigning PCI IRQ 23 to local APIC 1 msi: Assigning MSI IRQ 256 to local APIC 0 panic: blockabke sleep block (sleep mutex) msi @ /misc/src-6/sys/i386/i386/msi.c:381 cpuid: 0 kdb: stack backtrace kbd_backtrace( c0adc531,0,c0abaafd,c1020c34,c0bab700,...) at ... \ [I skipped from here to the db prompt] . . . Tomorrow, rather later today, I will type up the trace output. Please let me know if you would like to see any other output that I could possibly provide. This is good enough for me to see the bug, I'll work on fixing it. There are some locking changes in the x86 interrupt code I need to MFC. -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PCI MSI (was Re: What current Dell Systems are supported/work)
On Friday 18 January 2008 08:50:31 am John Baldwin wrote:
On Friday 18 January 2008 05:30:06 am Parv wrote:
There was no page fault or trap 12 message when the panic happened.
After some of messages are printed (as in dmesg), kdb is entered ...
ioapic0: Assigning PCI IRQ 23 to local APIC 1
msi: Assigning MSI IRQ 256 to local APIC 0
panic: blockabke sleep block (sleep mutex) msi @
/misc/src-6/sys/i386/i386/msi.c:381
cpuid: 0
kdb: stack backtrace
kbd_backtrace( c0adc531,0,c0abaafd,c1020c34,c0bab700,...) at ... \
[I skipped from here to the db prompt]
.
.
.
Tomorrow, rather later today, I will type up the trace output.
Please let me know if you would like to see any other output that I
could possibly provide.
This is good enough for me to see the bug, I'll work on fixing it. There are
some locking changes in the x86 interrupt code I need to MFC.
Try this patch:
Index: amd64/amd64/intr_machdep.c
===
RCS file: /host/cvs/usr/cvs/src/sys/amd64/amd64/intr_machdep.c,v
retrieving revision 1.15.2.5
diff -u -r1.15.2.5 intr_machdep.c
--- amd64/amd64/intr_machdep.c 26 Nov 2007 15:08:35 - 1.15.2.5
+++ amd64/amd64/intr_machdep.c 18 Jan 2008 15:05:08 -
@@ -43,13 +43,14 @@
#include sys/param.h
#include sys/bus.h
#include sys/interrupt.h
-#include sys/lock.h
#include sys/ktr.h
#include sys/kernel.h
+#include sys/lock.h
#include sys/mutex.h
#include sys/proc.h
#include sys/syslog.h
#include sys/systm.h
+#include sys/sx.h
#include machine/clock.h
#include machine/intr_machdep.h
#ifdef DDB
@@ -70,7 +71,8 @@
static int intrcnt_index;
static struct intsrc *interrupt_sources[NUM_IO_INTS];
-static struct mtx intr_table_lock;
+static struct sx intr_table_lock;
+static struct mtx intrcnt_lock;
static STAILQ_HEAD(, pic) pics;
#ifdef SMP
@@ -108,14 +110,14 @@
{
int error;
- mtx_lock_spin(intr_table_lock);
+ sx_xlock(intr_table_lock);
if (intr_pic_registered(pic))
error = EBUSY;
else {
STAILQ_INSERT_TAIL(pics, pic, pics);
error = 0;
}
- mtx_unlock_spin(intr_table_lock);
+ sx_xunlock(intr_table_lock);
return (error);
}
@@ -137,16 +139,16 @@
(mask_fn)isrc-is_pic-pic_enable_source, irq%d:, vector);
if (error)
return (error);
- mtx_lock_spin(intr_table_lock);
+ sx_xlock(intr_table_lock);
if (interrupt_sources[vector] != NULL) {
- mtx_unlock_spin(intr_table_lock);
+ sx_xunlock(intr_table_lock);
intr_event_destroy(isrc-is_event);
return (EEXIST);
}
intrcnt_register(isrc);
interrupt_sources[vector] = isrc;
isrc-is_enabled = 0;
- mtx_unlock_spin(intr_table_lock);
+ sx_xunlock(intr_table_lock);
return (0);
}
@@ -170,19 +172,18 @@
error = intr_event_add_handler(isrc-is_event, name, handler, arg,
intr_priority(flags), flags, cookiep);
if (error == 0) {
+ sx_xlock(intr_table_lock);
intrcnt_updatename(isrc);
- mtx_lock_spin(intr_table_lock);
if (!isrc-is_enabled) {
isrc-is_enabled = 1;
#ifdef SMP
if (assign_cpu)
intr_assign_next_cpu(isrc);
#endif
- mtx_unlock_spin(intr_table_lock);
isrc-is_pic-pic_enable_intr(isrc);
- } else
- mtx_unlock_spin(intr_table_lock);
+ }
isrc-is_pic-pic_enable_source(isrc);
+ sx_xunlock(intr_table_lock);
}
return (error);
}
@@ -306,12 +307,12 @@
#ifndef DEV_ATPIC
atpic_reset();
#endif
- mtx_lock_spin(intr_table_lock);
+ sx_xlock(intr_table_lock);
STAILQ_FOREACH(pic, pics, pics) {
if (pic-pic_resume != NULL)
pic-pic_resume(pic);
}
- mtx_unlock_spin(intr_table_lock);
+ sx_xunlock(intr_table_lock);
}
void
@@ -319,12 +320,12 @@
{
struct pic *pic;
- mtx_lock_spin(intr_table_lock);
+ sx_xlock(intr_table_lock);
STAILQ_FOREACH(pic, pics, pics) {
if (pic-pic_suspend != NULL)
pic-pic_suspend(pic);
}
- mtx_unlock_spin(intr_table_lock);
+ sx_xunlock(intr_table_lock);
}
static void
@@ -347,8 +348,8 @@
{
char straystr[MAXCOMLEN + 1];
- /* mtx_assert(intr_table_lock, MA_OWNED); */
KASSERT(is-is_event != NULL, (%s: isrc with no event, __func__));
+ mtx_lock_spin(intrcnt_lock);
is-is_index = intrcnt_index;
intrcnt_index += 2;
snprintf(straystr, MAXCOMLEN + 1, stray irq%d,
@@ -357,17 +358,18 @@
is-is_count = intrcnt[is-is_index];
PCI MSI (was Re: What current Dell Systems are supported/work)
in message [EMAIL PROTECTED], wrote Vivek Khera thusly... On Jan 10, 2008, at 11:09 AM, John Baldwin wrote: *: This is the default behavior for 7.0, I have not encountered the problem mentioned above on any 1950/2950 boxes so far I have tested. I will enable MSI by default on 6.x now (so will take affect for 6.4). We've also enabled it by default on 6.x at work. Where can one go to read up on what MSI is and how it helps us? Is enabling it just setting a sysctl? Does that have to be done in loader.conf or can it happen later? Speaking of MSI being on by default in recent 6-STABLE ... well, that caused my ThinkPad T61 (8859-CTO) ... dmesg: http://www103.pair.com/parv/comp/unix/freebsd/thinkpad-t61-8859-cto/sys/dmesg kernel (combined for easy perusal): http://www103.pair.com/parv/comp/unix/freebsd/thinkpad-t61-8859-cto/cf/kern/combined/T61-SMP.debug--combined /boot/device.hints: http://www103.pair.com/parv/comp/unix/freebsd/thinkpad-t61-8859-cto/cf/boot/device.hints ... to go in panic[0]. So, for now I have added ... # Since MSI turned on by default on 2008.01.10.21.17.12 UTC, # causes panic so disable MSI. hw.pci.enable_msix=0 hw.pci.enable_msi=0 ... to /boot/loader.conf. [0] I could not save the dump for neither do I have access to serial console, nor could the file system be mounted. Missing also here is a digital camera. If anybody is interested, I could write screen down, and repeat to them. - Parv -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What current Dell Systems are supported/work
Vivek Khera wrote: On Jan 15, 2008, at 1:40 PM, John Baldwin wrote: Where can one go to read up on what MSI is and how it helps us? Is enabling it just setting a sysctl? Does that have to be done in loader.conf or can it happen later? loader.conf (though it is now default on in RELENG_6). hw.pci.msi_enable=1 hw.pci.msix_enable=1 Thanks for the info. But can anyone point me to some documentation on why MSI is good for me? When implemented and used correctly in the hardware and driver, it a lower overhead interrupt mechanism. It also expands the number of interrupt vectors available, making interrupt sharing non-existent (for right now, at least). Thirdly, it vastly simplifies interrupt routing and makes a lot of problems with missing interrupts at the OS/driver level go away. Scott ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What current Dell Systems are supported/work
Vivek Khera wrote: On Jan 15, 2008, at 1:40 PM, John Baldwin wrote: Where can one go to read up on what MSI is and how it helps us? Is enabling it just setting a sysctl? Does that have to be done in loader.conf or can it happen later? loader.conf (though it is now default on in RELENG_6). hw.pci.msi_enable=1 hw.pci.msix_enable=1 Thanks for the info. But can anyone point me to some documentation on why MSI is good for me? When implemented and used correctly in the hardware and driver, it a lower overhead interrupt mechanism. It also expands the number of interrupt vectors available, making interrupt sharing non-existent (for right now, at least). Scott ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What current Dell Systems are supported/work
On Jan 15, 2008, at 1:40 PM, John Baldwin wrote: Where can one go to read up on what MSI is and how it helps us? Is enabling it just setting a sysctl? Does that have to be done in loader.conf or can it happen later? loader.conf (though it is now default on in RELENG_6). hw.pci.msi_enable=1 hw.pci.msix_enable=1 Thanks for the info. But can anyone point me to some documentation on why MSI is good for me? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PCI MSI (was Re: What current Dell Systems are supported/work)
On Thursday 17 January 2008 06:05:17 am Parv wrote: in message [EMAIL PROTECTED], wrote Vivek Khera thusly... On Jan 10, 2008, at 11:09 AM, John Baldwin wrote: *: This is the default behavior for 7.0, I have not encountered the problem mentioned above on any 1950/2950 boxes so far I have tested. I will enable MSI by default on 6.x now (so will take affect for 6.4). We've also enabled it by default on 6.x at work. Where can one go to read up on what MSI is and how it helps us? Is enabling it just setting a sysctl? Does that have to be done in loader.conf or can it happen later? Speaking of MSI being on by default in recent 6-STABLE ... well, that caused my ThinkPad T61 (8859-CTO) ... dmesg: http://www103.pair.com/parv/comp/unix/freebsd/thinkpad-t61-8859-cto/sys/dmesg kernel (combined for easy perusal): http://www103.pair.com/parv/comp/unix/freebsd/thinkpad-t61-8859-cto/cf/kern/combined/T61-SMP.debug--combined /boot/device.hints: http://www103.pair.com/parv/comp/unix/freebsd/thinkpad-t61-8859-cto/cf/boot/device.hints ... to go in panic[0]. So, for now I have added ... # Since MSI turned on by default on 2008.01.10.21.17.12 UTC, # causes panic so disable MSI. hw.pci.enable_msix=0 hw.pci.enable_msi=0 ... to /boot/loader.conf. [0] I could not save the dump for neither do I have access to serial console, nor could the file system be mounted. Missing also here is a digital camera. If anybody is interested, I could write screen down, and repeat to them. For starters, can you get the output of 'pciconf -lc'? Secondly, I really will need the kernel panic message. If it is a page fault (trap 12) then write down the faulting virtual address and the faulting IP. If you can scribble down any of the stack trace from DDB that would be helpful as well. -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What current Dell Systems are supported/work
On Jan 10, 2008, at 11:09 AM, John Baldwin wrote: *: This is the default behavior for 7.0, I have not encountered the problem mentioned above on any 1950/2950 boxes so far I have tested. I will enable MSI by default on 6.x now (so will take affect for 6.4). We've also enabled it by default on 6.x at work. Where can one go to read up on what MSI is and how it helps us? Is enabling it just setting a sysctl? Does that have to be done in loader.conf or can it happen later? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What current Dell Systems are supported/work
On Tuesday 15 January 2008 10:25:14 am Vivek Khera wrote: On Jan 10, 2008, at 11:09 AM, John Baldwin wrote: *: This is the default behavior for 7.0, I have not encountered the problem mentioned above on any 1950/2950 boxes so far I have tested. I will enable MSI by default on 6.x now (so will take affect for 6.4). We've also enabled it by default on 6.x at work. Where can one go to read up on what MSI is and how it helps us? Is enabling it just setting a sysctl? Does that have to be done in loader.conf or can it happen later? loader.conf (though it is now default on in RELENG_6). hw.pci.msi_enable=1 hw.pci.msix_enable=1 -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What current Dell Systems are supported/work
On Wednesday 09 January 2008 07:06:02 pm Xin LI wrote: Richard Bates wrote: Sorry for the repost... I don't think the first one posted.. posted to freebsd.stable, freebsd-current, Freebsd-hardware I checked the hardware in the online documentation manual/hardware It only lists the bits and peices of the machine say the hard drive controller and so forth. but doesn't give you a particular system to look at as a working machine with FreeBSD 6.2 does anybody know if a Dell PowerEdge 1950 • Quad-Core Intel Xeon Processors 5400 series 3.16GHz • 4GB Ram I am looking to attach 2 machines to a SAN to make a constantly up system. Is there a Dell San and San Switch that will work with this version of BSD? Thank you for your help It has been observed that there is some interrupt related issue with certain models of Dell PowerEdge 1950/2950 on 6.2-RELEASE, to be more specific, those which are configured without a RAID controller. The symptom is that server will hang on boot after detected acd0, but this is not reliably reproducible. If you use 'show intrcnt' in ddb do you see an interrupt storm on bce0? We have a local patch at work to fix an interrupt storm on boot with bce(4) that needs further refinement but I don't have any boxes handy to test on. At our company (we deploy hundreds of 1950/2950 online during last year), our important local changes that is made for these boxes include: - backport my bce(4) changes from RELENG_6. - backport MSI support, and enable by default. (*) *: This is the default behavior for 7.0, I have not encountered the problem mentioned above on any 1950/2950 boxes so far I have tested. I will enable MSI by default on 6.x now (so will take affect for 6.4). We've also enabled it by default on 6.x at work. -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What current Dell Systems are supported/work
Richard, I just bought one of these 2450 servers on ebay the other day, it was pretty cheap and still a good server for DNS here is a link http://search.ebay.com/_W0QQsassZlesmilde when I received the server it shipped with PC-BSD installed, I am going to put RELENG_7 on it, but if you read the site there is a link to a dmesg hope this helps Sam Fourman Jr. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What current Dell Systems are supported/work
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Richard Bates wrote: Sorry for the repost... I don't think the first one posted.. posted to freebsd.stable, freebsd-current, Freebsd-hardware I checked the hardware in the online documentation manual/hardware It only lists the bits and peices of the machine say the hard drive controller and so forth. but doesn't give you a particular system to look at as a working machine with FreeBSD 6.2 does anybody know if a Dell PowerEdge 1950 • Quad-Core Intel Xeon Processors 5400 series 3.16GHz • 4GB Ram I am looking to attach 2 machines to a SAN to make a constantly up system. Is there a Dell San and San Switch that will work with this version of BSD? Thank you for your help It has been observed that there is some interrupt related issue with certain models of Dell PowerEdge 1950/2950 on 6.2-RELEASE, to be more specific, those which are configured without a RAID controller. The symptom is that server will hang on boot after detected acd0, but this is not reliably reproducible. At our company (we deploy hundreds of 1950/2950 online during last year), our important local changes that is made for these boxes include: - backport my bce(4) changes from RELENG_6. - backport MSI support, and enable by default. (*) *: This is the default behavior for 7.0, I have not encountered the problem mentioned above on any 1950/2950 boxes so far I have tested. That's said, I would recommend that you deploy 6.3-RELEASE (with proper loader.conf configuration to enable MSI) or 7.0-RELEASE once they are out of the door. I do not have much experience with SAN devices you have mentioned, though, so perhaps it's better to listen someone else's suggestions. Cheers, - -- Xin LI [EMAIL PROTECTED] http://www.delphij.net/ FreeBSD - The Power to Serve! -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) iD4DBQFHhWFpi+vbBBjt66ARAhaLAJdYQHtgCsXYYdgPvWOh0QiLARWmAKCU2sH5 9PLlYsSESqvoMHCekHtJfw== =xIhB -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
What current Dell Systems are supported/work
Sorry for the repost... I don't think the first one posted.. posted to freebsd.stable, freebsd-current, Freebsd-hardware I checked the hardware in the online documentation manual/hardware It only lists the bits and peices of the machine say the hard drive controller and so forth. but doesn't give you a particular system to look at as a working machine with FreeBSD 6.2 does anybody know if a Dell PowerEdge 1950 • Quad-Core Intel Xeon Processors 5400 series 3.16GHz • 4GB Ram I am looking to attach 2 machines to a SAN to make a constantly up system. Is there a Dell San and San Switch that will work with this version of BSD? Thank you for your help ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What current Dell Systems are supported/work
Hi Richard, I run freeBSD 6.2 on a 1950 and the only i had issue i had was with the on board broadcom ethernet, my workaround is detailed here http://www.ifdnrg.com/freebsd_broadcom_dell_1950.htm hope that helps Paul. http://www.ifdnrg.com *web and video services* *Paul Macdonald* Director [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] www.ifdnrg.com http://www.ifdnrg.com *IFDNRG* *Please note new address!* 127 Rose St South Lane, Edinburgh, EH2 4BB +44.131.2257470 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What current Dell Systems are supported/work
On 1/8/08, Richard Bates [EMAIL PROTECTED] wrote: Sorry for the repost... I don't think the first one posted.. posted to freebsd.stable, freebsd-current, Freebsd-hardware I checked the hardware in the online documentation manual/hardware It only lists the bits and peices of the machine say the hard drive controller and so forth. but doesn't give you a particular system to look at as a working machine with FreeBSD 6.2 does anybody know if a Dell PowerEdge 1950 • Quad-Core Intel Xeon Processors 5400 series 3.16GHz • 4GB Ram I am looking to attach 2 machines to a SAN to make a constantly up system. Is there a Dell San and San Switch that will work with this version of BSD? I'm using a newer version of the PE2950, which has the PERC 6/i controller. Older ones use the PERC 5/i, which is supported by 6.2. Dell machines are pretty well supported. Thank you for your help ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] -- Mahnahmahnah! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What current Dell Systems are supported/work
Richard Bates wrote: Sorry for the repost... I don't think the first one posted.. posted to freebsd.stable, freebsd-current, Freebsd-hardware I checked the hardware in the online documentation manual/hardware It only lists the bits and peices of the machine say the hard drive controller and so forth. but doesn't give you a particular system to look at as a working machine with FreeBSD 6.2 does anybody know if a Dell PowerEdge 1950 • Quad-Core Intel Xeon Processors 5400 series 3.16GHz • 4GB Ram We have ~20 PE [12]950 systems here all running 6/2 with a back ported bce driver from RELENG_6. Tom I am looking to attach 2 machines to a SAN to make a constantly up system. Is there a Dell San and San Switch that will work with this version of BSD? Thank you for your help ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
