From ivan.slavkov at gmail.com Wed Mar 4 08:01:48 2009 From: ivan.slavkov at gmail.com (Ivan Slavkov) Date: Wed Mar 4 08:01:55 2009 Subject: dual cpu question Message-ID: <60bb96a10903040729t6f5603bl865b7047960830e7@mail.gmail.com> Hello all! Is there any software way to stop the second processor of two-processor (two quad core Xeon) proliant server with FreeBSD without romoving the proceesor in real? I have dead-locks with the two processors even in 7.1 with the new ULE schessuler. If I use one processor there are no problems. - Ivan From tomaszd at paraklet.net Wed Mar 4 08:45:09 2009 From: tomaszd at paraklet.net (td) Date: Wed Mar 4 08:45:16 2009 Subject: dual cpu question In-Reply-To: <60bb96a10903040729t6f5603bl865b7047960830e7@mail.gmail.com> References: <60bb96a10903040729t6f5603bl865b7047960830e7@mail.gmail.com> Message-ID: <49AEA9C8.8000608@paraklet.net> Ivan Slavkov wrote: > Hello all! > Is there any software way to stop the second processor of two-processor (two > quad core Xeon) proliant server with FreeBSD without romoving the proceesor > in real? I have dead-locks with the two processors even in 7.1 with the new > ULE schessuler. If I use one processor there are no problems. > cant you simply disable it in the bios? > - Ivan -- tomasz dereszynski From mikhollo at cisco.com Wed Mar 4 09:24:47 2009 From: mikhollo at cisco.com (Mike Holloway) Date: Wed Mar 4 09:24:54 2009 Subject: dual cpu question In-Reply-To: <49AEA9C8.8000608@paraklet.net> References: <60bb96a10903040729t6f5603bl865b7047960830e7@mail.gmail.com> <49AEA9C8.8000608@paraklet.net> Message-ID: Possibly use the cputask(2) utility which should be available in 7.1- RELEASE. -mike On Mar 4, 2009, at 10:18 AM, td wrote: > Ivan Slavkov wrote: >> Hello all! >> Is there any software way to stop the second processor of two- >> processor (two >> quad core Xeon) proliant server with FreeBSD without romoving the >> proceesor >> in real? I have dead-locks with the two processors even in 7.1 with >> the new >> ULE schessuler. If I use one processor there are no problems. >> > > cant you simply disable it in the bios? > >> - Ivan > > -- > tomasz dereszynski > _______________________________________________ > freebsd-proliant@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-proliant > To unsubscribe, send any mail to "freebsd-proliant-unsubscribe@freebsd.org > " From ivan.slavkov at gmail.com Wed Mar 4 10:40:02 2009 From: ivan.slavkov at gmail.com (Ivan Slavkov) Date: Wed Mar 4 10:40:09 2009 Subject: dual cpu question In-Reply-To: <6863f0c90903041033mbbeacdt188752e9550b8f51@mail.gmail.com> References: <60bb96a10903040729t6f5603bl865b7047960830e7@mail.gmail.com> <6863f0c90903041033mbbeacdt188752e9550b8f51@mail.gmail.com> Message-ID: <60bb96a10903041039l6c8aa0ag72abd676124e127a@mail.gmail.com> I haven't tried this yet. I will try. The main Idea is to have system with two good-working on FreeBSD. On this stage I cannot have it :( On Wed, Mar 4, 2009 at 8:33 PM, John Cagle wrote: > Why don't you rebuild the kernel without SMP support? Then it will only > use one CPU. > > On Wed, Mar 4, 2009 at 9:29 AM, Ivan Slavkov wrote: > >> Hello all! >> Is there any software way to stop the second processor of two-processor >> (two >> quad core Xeon) proliant server with FreeBSD without romoving the >> proceesor >> in real? I have dead-locks with the two processors even in 7.1 with the >> new >> ULE schessuler. If I use one processor there are no problems. >> >> - Ivan >> _______________________________________________ >> freebsd-proliant@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-proliant >> To unsubscribe, send any mail to " >> freebsd-proliant-unsubscribe@freebsd.org" >> > > From jcagle at gmail.com Wed Mar 4 10:54:37 2009 From: jcagle at gmail.com (John Cagle) Date: Wed Mar 4 10:54:43 2009 Subject: dual cpu question In-Reply-To: <60bb96a10903040729t6f5603bl865b7047960830e7@mail.gmail.com> References: <60bb96a10903040729t6f5603bl865b7047960830e7@mail.gmail.com> Message-ID: <6863f0c90903041033mbbeacdt188752e9550b8f51@mail.gmail.com> Why don't you rebuild the kernel without SMP support? Then it will only use one CPU. On Wed, Mar 4, 2009 at 9:29 AM, Ivan Slavkov wrote: > Hello all! > Is there any software way to stop the second processor of two-processor > (two > quad core Xeon) proliant server with FreeBSD without romoving the > proceesor > in real? I have dead-locks with the two processors even in 7.1 with the new > ULE schessuler. If I use one processor there are no problems. > > - Ivan > _______________________________________________ > freebsd-proliant@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-proliant > To unsubscribe, send any mail to "freebsd-proliant-unsubscribe@freebsd.org > " > From ulf at Alameda.net Wed Mar 4 15:25:11 2009 From: ulf at Alameda.net (Ulf Zimmermann) Date: Wed Mar 4 15:25:17 2009 Subject: dual cpu question In-Reply-To: <60bb96a10903040729t6f5603bl865b7047960830e7@mail.gmail.com> References: <60bb96a10903040729t6f5603bl865b7047960830e7@mail.gmail.com> Message-ID: <20090304225602.GI51533@evil.alameda.net> On Wed, Mar 04, 2009 at 05:29:17PM +0200, Ivan Slavkov wrote: > Hello all! > Is there any software way to stop the second processor of two-processor (two > quad core Xeon) proliant server with FreeBSD without romoving the proceesor > in real? I have dead-locks with the two processors even in 7.1 with the new > ULE schessuler. If I use one processor there are no problems. > > - Ivan You should be able to disable a processor from the bios (F9 prompt). -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-865-0204 You can find my resume at: http://www.Alameda.net/~ulf/resume.html From jcagle at gmail.com Wed Mar 4 15:39:47 2009 From: jcagle at gmail.com (John Cagle) Date: Wed Mar 4 15:39:53 2009 Subject: dual cpu question In-Reply-To: <20090304225602.GI51533@evil.alameda.net> References: <60bb96a10903040729t6f5603bl865b7047960830e7@mail.gmail.com> <20090304225602.GI51533@evil.alameda.net> Message-ID: <6863f0c90903041539v3ced4fe7v35cd45789cc3b5cb@mail.gmail.com> On Wed, Mar 4, 2009 at 4:56 PM, Ulf Zimmermann wrote: > On Wed, Mar 04, 2009 at 05:29:17PM +0200, Ivan Slavkov wrote: > > Hello all! > > Is there any software way to stop the second processor of two-processor > (two > > quad core Xeon) proliant server with FreeBSD without romoving the > proceesor > > in real? I have dead-locks with the two processors even in 7.1 with the > new > > ULE schessuler. If I use one processor there are no problems. > > > > - Ivan > > You should be able to disable a processor from the bios (F9 prompt). > > -- > Regards, Ulf. > > The ProLiant BIOS doesn't offer a processor disable option as far as I know. From ulf at Alameda.net Wed Mar 4 16:31:04 2009 From: ulf at Alameda.net (Ulf Zimmermann) Date: Wed Mar 4 16:31:11 2009 Subject: dual cpu question In-Reply-To: <6863f0c90903041539v3ced4fe7v35cd45789cc3b5cb@mail.gmail.com> References: <60bb96a10903040729t6f5603bl865b7047960830e7@mail.gmail.com> <20090304225602.GI51533@evil.alameda.net> <6863f0c90903041539v3ced4fe7v35cd45789cc3b5cb@mail.gmail.com> Message-ID: <20090305003100.GJ51533@evil.alameda.net> On Wed, Mar 04, 2009 at 05:39:46PM -0600, John Cagle wrote: > On Wed, Mar 4, 2009 at 4:56 PM, Ulf Zimmermann wrote: > > On Wed, Mar 04, 2009 at 05:29:17PM +0200, Ivan Slavkov wrote: > > Hello all! > > Is there any software way to stop the second processor of two-processor > (two > > quad core Xeon) proliant server with FreeBSD without romoving the > proceesor > > in real? I have dead-locks with the two processors even in 7.1 with the > new > > ULE schessuler. If I use one processor there are no problems. > > > > - Ivan > > You should be able to disable a processor from the bios (F9 prompt). > > -- > Regards, Ulf. > > > > The ProLiant BIOS doesn't offer a processor disable option as far as I know. Hmmm, the DL360 g5 I just checked indeed doesn't. Don't remember on which server I last looked for it and it had it. Might have been an older DL58x or a blade. -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-865-0204 You can find my resume at: http://www.Alameda.net/~ulf/resume.html From scrappy at hub.org Fri Mar 27 23:10:45 2009 From: scrappy at hub.org (Marc G. Fournier) Date: Fri Mar 27 23:10:52 2009 Subject: ALT_BREAK_TO... + ILO ... missing something in config ... Message-ID: <20090328024247.Y47574@hub.org> Due to an issue I'm having with 7.x, and trying to track it down, I spent tonight getting my server setup to allow my to break into the debugger when it hangs, and hopefully dump core ... But, although I *think* I've got it all, I'm obviously missing something, as it isn't breaking ... First ... I'm running a proliant server, and when I connect via SSH to ILO on that machine, and type 'vsp', I get a shell as I expect, I can type, etc ... when I reboot the machine, I get the opening splash screen with the 7(?) options (normal boot, single user mode, etc, etc) ... but I get nothing between that and the login prompt ... first sign of a problem, maybe? Next, the easy question ... what is the key stroke to issue when one has ALT_BREAK_TO_DEBUGGER is set in the kernel? I thought it was CR ~ ^b ... is that correct? I'm using putty to connect via ssh, if that makes a difference ... I've also tried using the browser interface into ilo / vsp, same lack of a result ... Beyond adding sio device driver to my kernel, I've also got: options ALT_BREAK_TO_DEBUGGER options KDB options DDB Missing a kernel option maybe? I have the following in /boot/loader.conf: comconsole_speed="9600" console="vidconsole,comconsole" # A comma separated list of console(s) boot_multicons="-D" # -D: Use multiple consoles boot_serial="-h" # -h: Use serial console So ... eithe rI don't have it enabled like I think, or I'm doing the wrong key stroke ... or ... Thx ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664 From danny at cs.huji.ac.il Sat Mar 28 01:36:54 2009 From: danny at cs.huji.ac.il (Danny Braniss) Date: Sat Mar 28 01:37:00 2009 Subject: ALT_BREAK_TO... + ILO ... missing something in config ... In-Reply-To: <20090328024247.Y47574@hub.org> References: <20090328024247.Y47574@hub.org> Message-ID: > > Due to an issue I'm having with 7.x, and trying to track it down, I spent > tonight getting my server setup to allow my to break into the debugger > when it hangs, and hopefully dump core ... > > But, although I *think* I've got it all, I'm obviously missing something, > as it isn't breaking ... > > First ... I'm running a proliant server, and when I connect via SSH to ILO > on that machine, and type 'vsp', I get a shell as I expect, I can type, > etc ... when I reboot the machine, I get the opening splash screen with > the 7(?) options (normal boot, single user mode, etc, etc) ... but I get > nothing between that and the login prompt ... first sign of a problem, > maybe? > not realy, you at least have confirmation that you are talking correctly via the serial port. Till this point boot is using the BIOS routines to talk via the serial port. Later, the kernel tries to use it's routines/knowledge of the serial port. > Next, the easy question ... what is the key stroke to issue when one has > ALT_BREAK_TO_DEBUGGER is set in the kernel? I thought it was CR ~ ^b ... > is that correct? I'm using putty to connect via ssh, if that makes a > difference ... I've also tried using the browser interface into ilo / vsp, > same lack of a result ... unless the serial port is setup as console, check if /boot/device.hints has: hint.sio.0.flags="0x10" escaping to the debugger is not caught. btw, Jeremy Chadwick had a nice explanation, but I lost the URL. > > Beyond adding sio device driver to my kernel, I've also got: > > options ALT_BREAK_TO_DEBUGGER > options KDB > options DDB > > Missing a kernel option maybe? > > I have the following in /boot/loader.conf: > > comconsole_speed="9600" > console="vidconsole,comconsole" # A comma separated list of console(s) > boot_multicons="-D" # -D: Use multiple consoles > boot_serial="-h" # -h: Use serial console > > So ... eithe rI don't have it enabled like I think, or I'm doing the wrong > key stroke ... or ... > > Thx > you are very close!, but each hardware/bios needs a different solution :-( danny From scrappy at hub.org Sat Mar 28 20:45:49 2009 From: scrappy at hub.org (Marc G. Fournier) Date: Sat Mar 28 20:46:02 2009 Subject: ALT_BREAK_TO... + ILO ... missing something in config ... In-Reply-To: References: <20090328024247.Y47574@hub.org> Message-ID: <20090329004504.N2769@hub.org> On Sat, 28 Mar 2009, Danny Braniss wrote: > unless the serial port is setup as console, check if /boot/device.hints > has: > hint.sio.0.flags="0x10" > escaping to the debugger is not caught. > btw, Jeremy Chadwick had a nice explanation, but I lost the URL. That was the missing piece, thank you ... I can now break down into DDB through the VSP ... ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664 From jhay at meraka.org.za Mon Mar 30 00:12:34 2009 From: jhay at meraka.org.za (John Hay) Date: Mon Mar 30 00:12:40 2009 Subject: hpacucli on 7-stable amd64, some progress Message-ID: <20090330071231.GA40323@zibbi.meraka.csir.co.za> Hi, I found that the reason hpacucli did not like amd64 7-stable was because the kernel is missing code to do a 32 bit PCIOCGETCONF ioctl. Here is a first stab at it. It works for me. I can do a "hpacucli controller all show". I also updated the firmware on the MSA20, so that I can put 1TB disks in it and now hpacucli does not want to show me the physical or logical disks behind it anymore. :-( BTW, was hpacucli always so noisy? I got hold of a DL380-G4 only recently, so did not run it on older versions of FreeBSD. Anybody know if there is a chance to get a newer hpacucli? John -- John Hay -- John.Hay@meraka.csir.co.za / jhay@FreeBSD.org --- sys/dev/pci/pci_user.c.orig 2009-02-26 20:54:24.000000000 +0200 +++ sys/dev/pci/pci_user.c 2009-03-29 17:10:45.000000000 +0200 @@ -225,6 +225,49 @@ u_int32_t pi_data; /* data to write or result of read */ }; +#ifdef COMPAT_IA32 +struct pci_conf_old32 { + struct pcisel_old pc_sel; /* bus+slot+function */ + u_int8_t pc_hdr; /* PCI header type */ + u_int16_t pc_subvendor; /* card vendor ID */ + u_int16_t pc_subdevice; /* card device ID, assigned by + card vendor */ + u_int16_t pc_vendor; /* chip vendor ID */ + u_int16_t pc_device; /* chip device ID, assigned by + chip vendor */ + u_int8_t pc_class; /* chip PCI class */ + u_int8_t pc_subclass; /* chip PCI subclass */ + u_int8_t pc_progif; /* chip PCI programming interface */ + u_int8_t pc_revid; /* chip revision ID */ + char pd_name[PCI_MAXNAMELEN + 1]; /* device name */ + u_int32_t pd_unit; /* device unit number (u_long) */ +}; + +struct pci_match_conf_old32 { + struct pcisel_old pc_sel; /* bus+slot+function */ + char pd_name[PCI_MAXNAMELEN + 1]; /* device name */ + u_int32_t pd_unit; /* Unit number (u_long) */ + u_int16_t pc_vendor; /* PCI Vendor ID */ + u_int16_t pc_device; /* PCI Device ID */ + u_int8_t pc_class; /* PCI class */ + pci_getconf_flags_old flags; /* Matching expression */ +}; + +struct pci_conf_io32 { + u_int32_t pat_buf_len; /* pattern buffer length */ + u_int32_t num_patterns; /* number of patterns */ + u_int32_t patterns; /* pattern buffer (struct pci_match_conf_old32 *) */ + u_int32_t match_buf_len; /* match buffer length */ + u_int32_t num_matches; /* number of matches returned */ + u_int32_t matches; /* match buffer (struct pci_conf_old32 *) */ + u_int32_t offset; /* offset into device list */ + u_int32_t generation; /* device list generation */ + pci_getconf_status status; /* request status */ +}; + +#define PCIOCGETCONF_OLD32 _IOWR('p', 1, struct pci_conf_io32) +#endif + #define PCIOCGETCONF_OLD _IOWR('p', 1, struct pci_conf_io) #define PCIOCREAD_OLD _IOWR('p', 2, struct pci_io_old) #define PCIOCWRITE_OLD _IOWR('p', 3, struct pci_io_old) @@ -295,6 +338,69 @@ return(1); } +static int +pci_conf_match_old32(struct pci_match_conf_old32 *matches, int num_matches, + struct pci_conf *match_buf) +{ + int i; + + if ((matches == NULL) || (match_buf == NULL) || (num_matches <= 0)) + return(1); + + for (i = 0; i < num_matches; i++) { + if (match_buf->pc_sel.pc_domain != 0) + continue; + + /* + * I'm not sure why someone would do this...but... + */ + if (matches[i].flags == PCI_GETCONF_NO_MATCH_OLD) + continue; + + /* + * Look at each of the match flags. If it's set, do the + * comparison. If the comparison fails, we don't have a + * match, go on to the next item if there is one. + */ + if (((matches[i].flags & PCI_GETCONF_MATCH_BUS_OLD) != 0) + && (match_buf->pc_sel.pc_bus != matches[i].pc_sel.pc_bus)) + continue; + + if (((matches[i].flags & PCI_GETCONF_MATCH_DEV_OLD) != 0) + && (match_buf->pc_sel.pc_dev != matches[i].pc_sel.pc_dev)) + continue; + + if (((matches[i].flags & PCI_GETCONF_MATCH_FUNC_OLD) != 0) + && (match_buf->pc_sel.pc_func != matches[i].pc_sel.pc_func)) + continue; + + if (((matches[i].flags & PCI_GETCONF_MATCH_VENDOR_OLD) != 0) + && (match_buf->pc_vendor != matches[i].pc_vendor)) + continue; + + if (((matches[i].flags & PCI_GETCONF_MATCH_DEVICE_OLD) != 0) + && (match_buf->pc_device != matches[i].pc_device)) + continue; + + if (((matches[i].flags & PCI_GETCONF_MATCH_CLASS_OLD) != 0) + && (match_buf->pc_class != matches[i].pc_class)) + continue; + + if (((matches[i].flags & PCI_GETCONF_MATCH_UNIT_OLD) != 0) + && ((u_int32_t)match_buf->pd_unit != matches[i].pd_unit)) + continue; + + if (((matches[i].flags & PCI_GETCONF_MATCH_NAME_OLD) != 0) + && (strncmp(matches[i].pd_name, match_buf->pd_name, + sizeof(match_buf->pd_name)) != 0)) + continue; + + return(0); + } + + return(1); +} + #endif static int @@ -314,13 +420,21 @@ size_t confsz, iolen, pbufsz; int error, ionum, i, num_patterns; #ifdef PRE7_COMPAT +#ifdef COMPAT_IA32 + struct pci_conf_io32 *cio32; +#endif struct pci_conf_old conf_old; + struct pci_conf_old32 conf_old32; struct pci_io iodata; struct pci_io_old *io_old; struct pci_match_conf_old *pattern_buf_old; + struct pci_match_conf_old32 *pattern_buf_old32; + cio = NULL; + cio32 = NULL; io_old = NULL; pattern_buf_old = NULL; + pattern_buf_old32 = NULL; if (!(flag & FWRITE) && cmd != PCIOCGETBAR && cmd != PCIOCGETCONF && cmd != PCIOCGETCONF_OLD) @@ -332,11 +446,27 @@ switch(cmd) { #ifdef PRE7_COMPAT + case PCIOCGETCONF_OLD32: + cio32 = (struct pci_conf_io32 *)data; + cio = malloc(sizeof(struct pci_conf_io), M_TEMP, M_WAITOK); + cio->pat_buf_len = cio32->pat_buf_len; + cio->num_patterns = cio32->num_patterns; + cio->patterns = (void *)(uintptr_t)cio32->patterns; + cio->match_buf_len = cio32->match_buf_len; + cio->num_matches = cio32->num_matches; + cio->matches = (void *)(uintptr_t)cio32->matches; + cio->offset = cio32->offset; + cio->generation = cio32->generation; + cio->status = cio32->status; + cio32->num_matches = 0; + /* FALLTHROUGH */ + case PCIOCGETCONF_OLD: /* FALLTHROUGH */ #endif case PCIOCGETCONF: - cio = (struct pci_conf_io *)data; + if (cio == NULL) + cio = (struct pci_conf_io *)data; pattern_buf = NULL; num_patterns = 0; @@ -354,7 +484,7 @@ && (cio->generation != pci_generation)){ cio->status = PCI_GETCONF_LIST_CHANGED; error = 0; - break; + goto getconfexit; } /* @@ -364,7 +494,7 @@ if (cio->offset >= pci_numdevs) { cio->status = PCI_GETCONF_LAST_DEVICE; error = 0; - break; + goto getconfexit; } /* get the head of the device queue */ @@ -377,6 +507,11 @@ * didn't specify a multiple of that size. */ #ifdef PRE7_COMPAT +#ifdef COMPAT_IA32 + if (cmd == PCIOCGETCONF_OLD32) + confsz = sizeof(struct pci_conf_old32); + else +#endif if (cmd == PCIOCGETCONF_OLD) confsz = sizeof(struct pci_conf_old); else @@ -411,6 +546,11 @@ * updated their kernel but not their userland. */ #ifdef PRE7_COMPAT +#ifdef COMPAT_IA32 + if (cmd == PCIOCGETCONF_OLD32) + pbufsz = sizeof(struct pci_match_conf_old32); + else +#endif if (cmd == PCIOCGETCONF_OLD) pbufsz = sizeof(struct pci_match_conf_old); else @@ -420,13 +560,19 @@ /* The user made a mistake, return an error. */ cio->status = PCI_GETCONF_ERROR; error = EINVAL; - break; + goto getconfexit; } /* * Allocate a buffer to hold the patterns. */ #ifdef PRE7_COMPAT + if (cmd == PCIOCGETCONF_OLD32) { + pattern_buf_old32 = malloc(cio->pat_buf_len, + M_TEMP, M_WAITOK); + error = copyin(cio->patterns, + pattern_buf_old32, cio->pat_buf_len); + } else if (cmd == PCIOCGETCONF_OLD) { pattern_buf_old = malloc(cio->pat_buf_len, M_TEMP, M_WAITOK); @@ -452,7 +598,7 @@ */ cio->status = PCI_GETCONF_ERROR; error = EINVAL; - break; + goto getconfexit; } /* @@ -484,7 +630,11 @@ } #ifdef PRE7_COMPAT - if ((cmd == PCIOCGETCONF_OLD && + if ((cmd == PCIOCGETCONF_OLD32 && + (pattern_buf_old32 == NULL || + pci_conf_match_old32(pattern_buf_old32, + num_patterns, &dinfo->conf) == 0)) || + (cmd == PCIOCGETCONF_OLD && (pattern_buf_old == NULL || pci_conf_match_old(pattern_buf_old, num_patterns, &dinfo->conf) == 0)) || @@ -509,6 +659,38 @@ break; #ifdef PRE7_COMPAT + if (cmd == PCIOCGETCONF_OLD32) { + conf_old32.pc_sel.pc_bus = + dinfo->conf.pc_sel.pc_bus; + conf_old32.pc_sel.pc_dev = + dinfo->conf.pc_sel.pc_dev; + conf_old32.pc_sel.pc_func = + dinfo->conf.pc_sel.pc_func; + conf_old32.pc_hdr = dinfo->conf.pc_hdr; + conf_old32.pc_subvendor = + dinfo->conf.pc_subvendor; + conf_old32.pc_subdevice = + dinfo->conf.pc_subdevice; + conf_old32.pc_vendor = + dinfo->conf.pc_vendor; + conf_old32.pc_device = + dinfo->conf.pc_device; + conf_old32.pc_class = + dinfo->conf.pc_class; + conf_old32.pc_subclass = + dinfo->conf.pc_subclass; + conf_old32.pc_progif = + dinfo->conf.pc_progif; + conf_old32.pc_revid = + dinfo->conf.pc_revid; + strncpy(conf_old32.pd_name, + dinfo->conf.pd_name, + sizeof(conf_old32.pd_name)); + conf_old32.pd_name[PCI_MAXNAMELEN] = 0; + conf_old32.pd_unit = + (u_int32_t)dinfo->conf.pd_unit; + confdata = &conf_old32; + } else if (cmd == PCIOCGETCONF_OLD) { conf_old.pc_sel.pc_bus = dinfo->conf.pc_sel.pc_bus; @@ -575,9 +757,22 @@ cio->status = PCI_GETCONF_MORE_DEVS; getconfexit: +#ifdef COMPAT_IA32 + if (cmd == PCIOCGETCONF_OLD32) { + cio32->status = cio->status; + cio32->generation = cio->generation; + cio32->offset = cio->offset; + cio32->num_matches = cio->num_matches; + if (cio != NULL) + free(cio, M_TEMP); + } +#endif + if (pattern_buf != NULL) free(pattern_buf, M_TEMP); #ifdef PRE7_COMPAT + if (pattern_buf_old32 != NULL) + free(pattern_buf_old32, M_TEMP); if (pattern_buf_old != NULL) free(pattern_buf_old, M_TEMP); #endif From won.derick at yahoo.com Mon Mar 30 04:51:15 2009 From: won.derick at yahoo.com (Won De Erick) Date: Mon Mar 30 04:51:22 2009 Subject: hpasm for FreeBSD 7.1 Message-ID: <358227.11973.qm@web45814.mail.sp1.yahoo.com> Hi, I was looking for a system health monitoring and management tool for HPDL 380 G5 that will run on FreeBSD 7.1, and found the below. Unfortunately the tool (hpasm) seems no longer updated to support later versions of FreeBSD. http://people.freebsd.org/~jcagle/#ilo Is there any tool other than this? Thank you very much. Won From hans.r.69 at gmail.com Mon Mar 30 13:59:34 2009 From: hans.r.69 at gmail.com (Hans Roman) Date: Mon Mar 30 13:59:40 2009 Subject: HP Proliant dl g5 Message-ID: <1b59dc600903301333g329c150dx364bfa4f3c7e455a@mail.gmail.com> Hi guys, I wanna know if someone has installed FreeBSD 7.1/7.0 in a HP Proliant dl g5. I've read that someone couldn't install 7.0 in this HP. Could you tell me if you had any troubles? and, which were them? Regards. -- Hans Roman From rainer at ultra-secure.de Mon Mar 30 14:33:01 2009 From: rainer at ultra-secure.de (Rainer Duffner) Date: Mon Mar 30 14:33:08 2009 Subject: HP Proliant dl g5 In-Reply-To: <1b59dc600903301333g329c150dx364bfa4f3c7e455a@mail.gmail.com> References: <1b59dc600903301333g329c150dx364bfa4f3c7e455a@mail.gmail.com> Message-ID: Am 30.03.2009 um 22:33 schrieb Hans Roman: > Hi guys, I wanna know if someone has installed FreeBSD 7.1/7.0 in a HP > Proliant dl g5. I've read that someone couldn't install 7.0 in this > HP. > Could you tell me if you had any troubles? and, which were them? > We run various FreeBSD versions on mostly DL380G3,G4 and G5 (and some blades) I would have to look what the very latest hardware actually is. There was a time before 6.3 where you needed to run 6.3-PRERELEASE to get anything useful out of the hardware. Too bad HP doesn't really support FreeBSD with their insight-agents. Rainer From won.derick at yahoo.com Mon Mar 30 23:09:09 2009 From: won.derick at yahoo.com (won.derick@yahoo.com) Date: Mon Mar 30 23:09:16 2009 Subject: HP Proliant dl g5 Message-ID: <253021.25150.qm@web45803.mail.sp1.yahoo.com> --- On Mon, 3/30/09, Hans Roman wrote: > Hi guys, I wanna know if someone has > installed FreeBSD 7.1/7.0 in a HP > Proliant dl g5. I've read that someone couldn't install 7.0 > in this HP. > Could you tell me if you had any troubles? and, which were > them? I have a DL 380 G5 box, so far no problem encountered with FreeBSD 7.1 during installation. :) Not relevant to the question above, but it should be great if the hpasmd and hpasmcli would work with freebsd 7.1 too. http://people.freebsd.org/~jcagle/#ilo From RCrommentuijn at adimec.nl Tue Mar 31 07:46:12 2009 From: RCrommentuijn at adimec.nl (Rob Crommentuijn) Date: Tue Mar 31 07:46:20 2009 Subject: HP Proliant dl g5 Message-ID: We have FreeBSD 7.1 running on a ML370G5 without any issues during the installations. The install of 6.2 on a DL380G5 and ML370G3 had some issues regarding the geometry of the disks, I had to enable Max Boot in the array controller in order to get the system booting after install. PS I would als like to have insight agents for freebsd and working HPasm, HPAUCLI kind regards, Rob From flo at kasimir.com Tue Mar 31 08:11:43 2009 From: flo at kasimir.com (Florian Smeets) Date: Tue Mar 31 08:11:50 2009 Subject: HP Proliant dl g5 In-Reply-To: <1b59dc600903301333g329c150dx364bfa4f3c7e455a@mail.gmail.com> References: <1b59dc600903301333g329c150dx364bfa4f3c7e455a@mail.gmail.com> Message-ID: <49D22F0B.1080205@kasimir.com> On 30.03.2009 22:33 Uhr, Hans Roman wrote: > Hi guys, I wanna know if someone has installed FreeBSD 7.1/7.0 in a HP > Proliant dl g5. I've read that someone couldn't install 7.0 in this HP. > Could you tell me if you had any troubles? and, which were them? > > Regards. > I recently installed 7.1-RELEASE successfully on the following models: DL320G5p DL360G5 DL380G5 Cheers, Florian From hans.r.69 at gmail.com Tue Mar 31 12:05:31 2009 From: hans.r.69 at gmail.com (Hans Roman) Date: Tue Mar 31 12:05:38 2009 Subject: HP Proliant dl g5 In-Reply-To: <49D22F0B.1080205@kasimir.com> References: <1b59dc600903301333g329c150dx364bfa4f3c7e455a@mail.gmail.com> <49D22F0B.1080205@kasimir.com> Message-ID: <1b59dc600903311205pfcf782by3e4ae2bc9c2bebb6@mail.gmail.com> Hello, thanks for answering, I forgot to write the exact model which is DL 160 G5. I've been reading the archives of this list, and I found that the problem could be the LSI controller, and someone said that it could be installed by removing the LSI, I'm not sure of this, I didn't pay attention to that. Do you have any suggestions? Thanks and regards. -- Hans Roman