search for: standi

Hi, I have a Packard Bell Easynote B notebook with CentOS 4.2 on it. I activated the standby option and it seems that entering the standby is OK (in a few seconds the display and hdd are closed, the power led is clipping). But when I try to restart the notebook, the hdd sems like it reads something, but the display remains blank. Also ctrl+alt+backspace or ctrl+alt+del don't have any efect.

Sat, Apr 28, 2018 at 11:06:01AM CEST, jiri at resnulli.us wrote: >Fri, Apr 27, 2018 at 07:06:58PM CEST, sridhar.samudrala at intel.com wrote: [...] >>+ >>+ err = netdev_rx_handler_register(slave_dev, net_failover_handle_frame, >>+ failover_dev); >>+ if (err) { >>+ netdev_err(slave_dev, "can not register failover rx handler (err = %d)\n",

Sat, Apr 28, 2018 at 11:06:01AM CEST, jiri at resnulli.us wrote: >Fri, Apr 27, 2018 at 07:06:58PM CEST, sridhar.samudrala at intel.com wrote: [...] >>+ >>+ err = netdev_rx_handler_register(slave_dev, net_failover_handle_frame, >>+ failover_dev); >>+ if (err) { >>+ netdev_err(slave_dev, "can not register failover rx handler (err = %d)\n",

On Wed, May 02, 2018 at 10:51:12AM -0700, Samudrala, Sridhar wrote: > > > On 5/2/2018 9:15 AM, Jiri Pirko wrote: > > Sat, Apr 28, 2018 at 11:06:01AM CEST, jiri at resnulli.us wrote: > > > Fri, Apr 27, 2018 at 07:06:58PM CEST, sridhar.samudrala at intel.com wrote: > > [...] > > > > > > > > + > > > > + err =

On Wed, May 02, 2018 at 09:50:21AM +0200, Jiri Pirko wrote: > Wed, May 02, 2018 at 02:20:26AM CEST, sridhar.samudrala at intel.com wrote: > >On 4/30/2018 12:20 AM, Jiri Pirko wrote: > >> > >> > > Now I try to change mac of the failover master: > >> > > [root at test1 ~]# ip link set ens3 addr 52:54:00:b2:a7:f3 > >> > > RTNETLINK

...be disabled. > >> How about control the visibility of standby device? >> >> Thanks > standy the always there to guarantee no downtime. > >>> However just for testing purposes, we could add a non-stable >>> interface "x-standby" with the understanding that as any >>> x- prefix it's unstable and will be changed down the road, >>> likely in the next release. >>> >>> >>>> --- >>>> hw/net/virtio-net.c | 2 ++ >>>> include/standard-headers/linux...

...be disabled. > >> How about control the visibility of standby device? >> >> Thanks > standy the always there to guarantee no downtime. > >>> However just for testing purposes, we could add a non-stable >>> interface "x-standby" with the understanding that as any >>> x- prefix it's unstable and will be changed down the road, >>> likely in the next release. >>> >>> >>>> --- >>>> hw/net/virtio-net.c | 2 ++ >>>> include/standard-headers/linux...

...ontrol visibility of the primary device. The problem is legacy guest won't use primary device at all if we do this. How about control the visibility of standby device? Thanks > However just for testing purposes, we could add a non-stable > interface "x-standby" with the understanding that as any > x- prefix it's unstable and will be changed down the road, > likely in the next release. > > >> --- >> hw/net/virtio-net.c | 2 ++ >> include/standard-headers/linux/virtio_net.h | 3 +++ >> 2 files changed, 5 insert...

...ontrol visibility of the primary device. The problem is legacy guest won't use primary device at all if we do this. How about control the visibility of standby device? Thanks > However just for testing purposes, we could add a non-stable > interface "x-standby" with the understanding that as any > x- prefix it's unstable and will be changed down the road, > likely in the next release. > > >> --- >> hw/net/virtio-net.c | 2 ++ >> include/standard-headers/linux/virtio_net.h | 3 +++ >> 2 files changed, 5 insert...

On 5/2/2018 9:15 AM, Jiri Pirko wrote: > Sat, Apr 28, 2018 at 11:06:01AM CEST, jiri at resnulli.us wrote: >> Fri, Apr 27, 2018 at 07:06:58PM CEST, sridhar.samudrala at intel.com wrote: > [...] > > >>> + >>> + err = netdev_rx_handler_register(slave_dev, net_failover_handle_frame, >>> + failover_dev); >>> + if (err) { >>> +

...ensure the legacy guest isn't confused. > How about control the visibility of standby device? > > Thanks standy the always there to guarantee no downtime. > > However just for testing purposes, we could add a non-stable > > interface "x-standby" with the understanding that as any > > x- prefix it's unstable and will be changed down the road, > > likely in the next release. > > > > > > > --- > > > hw/net/virtio-net.c | 2 ++ > > > include/standard-headers/linux/virtio_net.h | 3...

https://bugs.freedesktop.org/show_bug.cgi?id=88946 Bug ID: 88946 Summary: [NVC1] black screen after resuming from hibernate Product: xorg Version: 7.7 (2012.06) Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

[attachments trimmed] Begin forwarded message: > From: eric kreuwels > Subject: UPSC based Windows Client > Date: October 13, 2013 4:43:31 PM EDT > To: nut-upsdev at lists.alioth.debian.org > > > Dear developers > > Last month I wrote WinUPSC, a Windows task tray UPS monitor. WinUPSC re-uses the UPSC logic to poll the UPS. > This initial version was tested

On Jan 12, 2020, at 12:58 PM, Gene Heskett wrote: > > But this doesn't pass the smell test, 3 other machines that are trained > to reboot when power returns and have no ups fitted, were NOT rebooted > as evidenced by their reported uptimes, one of which shows a 144 day > uptime. So why should this have been logged via a -wall bc to every > login it is servicing? >

...t control the visibility of standby device? > > > > > > Thanks > > standy the always there to guarantee no downtime. > > > > > > However just for testing purposes, we could add a non-stable > > > > interface "x-standby" with the understanding that as any > > > > x- prefix it's unstable and will be changed down the road, > > > > likely in the next release. > > > > > > > > > > > > > --- > > > > > hw/net/virtio-net.c | 2 ++ >...

I'm fairly new to VoIP, and brand-new to Asterisk. I am wondering what are the best/least expensive phones or phone adapters to use with Asterisk, both wired and WiFi. I would appreciate any insight or recommendations you may have. Thanks, James arbaughj@myrealbox.com

...;>>> >>>>> Thanks >>>> >>>> standy the always there to guarantee no downtime. >>>> >>>>>> However just for testing purposes, we could add a non-stable >>>>>> interface "x-standby" with the understanding that as any >>>>>> x- prefix it's unstable and will be changed down the road, >>>>>> likely in the next release. >>>>>> >>>>>> >>>>>>> --- >>>>>>> hw/net/virtio-net.c...

...the visibility of standby device? >>>> >>>> Thanks >>> standy the always there to guarantee no downtime. >>> >>>>> However just for testing purposes, we could add a non-stable >>>>> interface "x-standby" with the understanding that as any >>>>> x- prefix it's unstable and will be changed down the road, >>>>> likely in the next release. >>>>> >>>>> >>>>>> --- >>>>>> hw/net/virtio-net.c | 2 ++ &...

...I think most people move devices after they are renamed. > >> > >> So? > >> Si-Wei patch handles the issue that resolves from the fact the net-failover master will be opened before the rename on the net-failover slaves occur. > >> This should happen (to my understanding) regardless of network namespaces. > >> > >> -Liran > > > > My point was that any tool that moves devices after they > > are renamed will be broken by kernel automatically putting > > them in a namespace. > > I?m not sure I follow. How is this re...

On 4/30/2018 12:20 AM, Jiri Pirko wrote: > >>> Now I try to change mac of the failover master: >>> [root at test1 ~]# ip link set ens3 addr 52:54:00:b2:a7:f3 >>> RTNETLINK answers: Operation not supported >>> >>> That I did expect to work. I would expect this would change the mac of >>> the master and both standby and primary slaves.