similar to: Bug#723656: xen-hypervisor-4.1-amd64: IPMI serial console hangs

Package: xen-hypervisor-4.1-amd64 Version: 4.1.4-3+deb7u1 Severity: important Dear Maintainer, Just upgraded a Supermicro server (X9SCM-F motherboard) from Squeeze to Wheezy. And now the IPMI serial console no longer work as it used to. It hangs like this: [...] (XEN) Enabled directed EOI with ioapic_ack_old on! (XEN) ENABLING IO-APIC IRQs (XEN) -> Using old ACK method (XEN) Platform timer

I have this happening in Ubuntu precise also. When I upgraded from 12.04.1 to 12.04.4 it looks like my ipmi/serial/hvc0 console stopped working and the last message is: (XEN) Platform timer is 14.318MHz HPET From /etc/default/grub: GRUB_DEFAULT="Xen 4.1-amd64" GRUB_HIDDEN_TIMEOUT=0 GRUB_HIDDEN_TIMEOUT_QUIET=true GRUB_TIMEOUT=10 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo

On 2016-09-17, Alice Wonder <alice at domblogger.net> wrote: > > Okay if it requires DHCP this might be out, I'm currently out of town > watching my brothers (various disabilities) while parents are on much > needed vacation. Don't have easy physical access to the router, would > have to take out stuff in front of it. Was hoping crossover ethernet > would work.

Package: xen-hypervisor-4.1-amd64 Version: 4.1.4-3+deb7u1 Severity: important Dear Maintainer, We are having a problem on several Supermicro servers (I'll include more details on the configuration later) : when booting Linux 3.2 linux-image-3.2.0-4-amd64 (Wheezy) as a DOM0 on Xen 4.1 (xen-hypervisor-4.1-amd64 from Wheezy), the system hangs after : [ 3.716174] scsi1 : ata_piix [

On 09/17/2016 09:15 PM, Keith Keller wrote: > On 2016-09-17, Alice Wonder <alice at domblogger.net> wrote: >> >> Okay if it requires DHCP this might be out, I'm currently out of town >> watching my brothers (various disabilities) while parents are on much >> needed vacation. Don't have easy physical access to the router, would >> have to take out

Is there a little setup display right on the box? Just asking because I have seen that on some boxes. Cheers, Boris. On Sun, Sep 18, 2016 at 12:15 AM, Keith Keller < kkeller at wombat.san-francisco.ca.us> wrote: > On 2016-09-17, Alice Wonder <alice at domblogger.net> wrote: > > > > Okay if it requires DHCP this might be out, I'm currently out of town > >

On Sat, Sep 17, 2016 at 6:25 AM, Alice Wonder <alice at domblogger.net> wrote: > Never used IPMI in my life and while I thought it was cool when I heard > about it, had no plans to. > Under many different names (Sun called it LOM; I forgot IBM's name), this has been out there for a while. And it is IMHO the best way to deal with servers. My normal server installing

Never used IPMI in my life and while I thought it was cool when I heard about it, had no plans to. Just built a home server (while out of town) using a SUPERMICRO MBD-X10SLM+-F-O I put an nVidia 405 based video card in it but it may be bad. When I power it on, I get some beeps but they are different than the no memory beeps (I intentionally powered on w/o memory to hear those) and I think

Hi all, A recent thread inspired me to try getting a proper serial console working on a Supermicro X9SCL motherboard with IPMI. However I find that while I see loader messages and the getty I enabled after boot I don't get any kernel messages which does somewhat limit the utility.. The BMC creates COM3 (/dev/cuau2) which works with getty. I modified /boot/loader.conf like so..

tags 614101 +moreinfo thanks I'm afraid there is not much which can be done with this otherwise. Hints on setting up serial console can be found on the Xen wiki: http://wiki.xen.org/wiki/XenSerialConsole If you can please also try the Wheezy packages. Thanks, Ian.

On Sun, September 18, 2016 19:08, Keith Keller wrote: > > Make sure you do not allow the IPMI's IP to be accessible > on a public network. Either keep the IP on a private network > (better), keep the IP firewalled to only certain IPs, > or change the admin password from the default. In order of importance: 1. ALWAYS change the administrative account credentials from their

On 2016-09-18, Alice Wonder <alice at domblogger.net> wrote: > > But for now via VGA cable it is all working. > > Once I'm back home and this server is set up where it goes, I'll try > playing with non-browser IPMI tools and see what it is all about. Now that you have a console, you can use the *ipmi tools to assign an IP address to the IPMI interface yourself, then

I have a current RELENG_7 running on: http://www.supermicro.com/products/system/4U/7045/SYS-7045B-TR+.cfm with the -3+ IPMI card. I can interact with the BIOS, etc, but no joy once we get past the loader. Anyone have ideas? Attached is the kernel config, and the /var/run/dmesg.boot file. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683

Hi to all I have a supermicro server with LSI 3108 with - 2x300GB SAS spin drive in raid1 (virtual drive 0) - 2x300GB SAS spin drive in raid1 (virtual drive 1) - 2x200GB Intel SSD DC S3710 drives configured as JBOD in LSI bios In the IPMI storage health status eveything looks fine until I boot into Centos 7.1 (unfortunatelly I didn't try other OS, but also I'm not interested in other)

Control: tag -1 +moreinfo On Tue, 2014-05-13 at 08:55 -0700, Mike Egglestone wrote: > After booting into kernel 3.13 dom0, the keyboard no longer works. > All other aspects work, ssh is needed to login to the system to > start working with the domU's. > They keyboard works at the grub menu just fine, and > works normal when booting into the non xen kernel. I think at a minimum

On 11/11/2013 05:38 PM, Andrew J. Schorr wrote: > Hi, > > I hope somebody can help me with this problem. I don't know whether > it's a problem with my configuration or a bug or feature in extlinux. > I am using an IPMI 2.0 serial-over-lan console to connect to a system > with an Intel S3200SHL motherboard. The first line of my extlinux.conf > file looks like this:

Package: xen-hypervisor-3.2-1-amd64 Version: 3.2.1-2 Severity: normal *** Please type your report below this line *** Hi, Recently I've experienced some crashes of Xen domU (also debian Lenny, running same kernel as dom0 (linux-image-2.6.26-xen-amd64)). At xm top that domain appears as running, but hogs all CPUs, because this problem has appeared on two identic servers (Supermicro X7SBi,

On 11/12/2013 01:22 PM, Andrew J. Schorr wrote: > Hi, > > Thanks for your help. > > On Mon, Nov 11, 2013 at 08:00:47PM -0800, H. Peter Anvin wrote: >> There is no reason by Syslinux would reboot the system on a serial >> disconnect. There could be a bug, of course; now, Syslinux 4.05 is >> pretty old so unless you can reproduce this on a current version that

On 09/17/2016 04:11 AM, Mauricio Tavares wrote: > On Sat, Sep 17, 2016 at 6:25 AM, Alice Wonder <alice at domblogger.net> wrote: >> Never used IPMI in my life and while I thought it was cool when I heard >> about it, had no plans to. >> > Under many different names (Sun called it LOM; I forgot IBM's > name), this has been out there for a while. And it

Hi, I hope somebody can help me with this problem. I don't know whether it's a problem with my configuration or a bug or feature in extlinux. I am using an IPMI 2.0 serial-over-lan console to connect to a system with an Intel S3200SHL motherboard. The first line of my extlinux.conf file looks like this: serial 0 57600 0x003 I am using ipmitool to access the console, like so: