search for: standis

Displaying 20 results from an estimated 29 matches for "standis".

Did you mean: stands
2006 Feb 09
0
Standy (suspend to RAM) problem
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.
2018 May 02
4
[PATCH net-next v9 2/4] net: Introduce generic failover module
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",
2018 May 02
4
[PATCH net-next v9 2/4] net: Introduce generic failover module
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",
2018 May 02
1
[PATCH net-next v9 2/4] net: Introduce generic failover module
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 =
2018 May 02
1
[PATCH net-next v9 3/4] virtio_net: Extend virtio to use VF datapath when available
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
2018 Jun 12
2
[Qemu-devel] [PATCH] qemu: Introduce VIRTIO_NET_F_STANDBY feature bit to virtio_net
On 6/11/2018 7:17 PM, Michael S. Tsirkin wrote: > On Tue, Jun 12, 2018 at 09:54:44AM +0800, Jason Wang wrote: >> >> On 2018?06?12? 01:26, Michael S. Tsirkin wrote: >>> On Mon, May 07, 2018 at 04:09:54PM -0700, Sridhar Samudrala wrote: >>>> This feature bit can be used by hypervisor to indicate virtio_net device to >>>> act as a standby for another
2018 Jun 12
2
[Qemu-devel] [PATCH] qemu: Introduce VIRTIO_NET_F_STANDBY feature bit to virtio_net
On 6/11/2018 7:17 PM, Michael S. Tsirkin wrote: > On Tue, Jun 12, 2018 at 09:54:44AM +0800, Jason Wang wrote: >> >> On 2018?06?12? 01:26, Michael S. Tsirkin wrote: >>> On Mon, May 07, 2018 at 04:09:54PM -0700, Sridhar Samudrala wrote: >>>> This feature bit can be used by hypervisor to indicate virtio_net device to >>>> act as a standby for another
2018 Jun 12
2
[Qemu-devel] [PATCH] qemu: Introduce VIRTIO_NET_F_STANDBY feature bit to virtio_net
On 2018?06?12? 01:26, Michael S. Tsirkin wrote: > On Mon, May 07, 2018 at 04:09:54PM -0700, Sridhar Samudrala wrote: >> This feature bit can be used by hypervisor to indicate virtio_net device to >> act as a standby for another device with the same MAC address. >> >> I tested this with a small change to the patch to mark the STANDBY feature 'true' >> by
2018 Jun 12
2
[Qemu-devel] [PATCH] qemu: Introduce VIRTIO_NET_F_STANDBY feature bit to virtio_net
On 2018?06?12? 01:26, Michael S. Tsirkin wrote: > On Mon, May 07, 2018 at 04:09:54PM -0700, Sridhar Samudrala wrote: >> This feature bit can be used by hypervisor to indicate virtio_net device to >> act as a standby for another device with the same MAC address. >> >> I tested this with a small change to the patch to mark the STANDBY feature 'true' >> by
2018 May 02
0
[PATCH net-next v9 2/4] net: Introduce generic failover module
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) { >>> +
2018 Jun 12
0
[Qemu-devel] [PATCH] qemu: Introduce VIRTIO_NET_F_STANDBY feature bit to virtio_net
On Tue, Jun 12, 2018 at 09:54:44AM +0800, Jason Wang wrote: > > > On 2018?06?12? 01:26, Michael S. Tsirkin wrote: > > On Mon, May 07, 2018 at 04:09:54PM -0700, Sridhar Samudrala wrote: > > > This feature bit can be used by hypervisor to indicate virtio_net device to > > > act as a standby for another device with the same MAC address. > > > > >
2015 Feb 03
15
[Bug 88946] New: [NVC1] black screen after resuming from hibernate
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
2013 Oct 14
3
UPSC based Windows Client
[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
2020 Jan 14
1
nut on armhf, r-pi4b IOW
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? >
2018 Jun 12
0
[Qemu-devel] [PATCH] qemu: Introduce VIRTIO_NET_F_STANDBY feature bit to virtio_net
On Mon, Jun 11, 2018 at 10:02:45PM -0700, Samudrala, Sridhar wrote: > On 6/11/2018 7:17 PM, Michael S. Tsirkin wrote: > > On Tue, Jun 12, 2018 at 09:54:44AM +0800, Jason Wang wrote: > > > > > > On 2018?06?12? 01:26, Michael S. Tsirkin wrote: > > > > On Mon, May 07, 2018 at 04:09:54PM -0700, Sridhar Samudrala wrote: > > > > > This feature bit
2004 Apr 14
3
VoIP Phone Recommendations
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
2018 Jun 14
0
[virtio-dev] Re: [Qemu-devel] [PATCH] qemu: Introduce VIRTIO_NET_F_STANDBY feature bit to virtio_net
On Tue, Jun 12, 2018 at 5:08 PM, Samudrala, Sridhar <sridhar.samudrala at intel.com> wrote: > On 6/12/2018 4:34 AM, Michael S. Tsirkin wrote: >> >> On Mon, Jun 11, 2018 at 10:02:45PM -0700, Samudrala, Sridhar wrote: >>> >>> On 6/11/2018 7:17 PM, Michael S. Tsirkin wrote: >>>> >>>> On Tue, Jun 12, 2018 at 09:54:44AM +0800, Jason Wang
2018 Jun 13
3
[virtio-dev] Re: [Qemu-devel] [PATCH] qemu: Introduce VIRTIO_NET_F_STANDBY feature bit to virtio_net
On 6/12/2018 4:34 AM, Michael S. Tsirkin wrote: > On Mon, Jun 11, 2018 at 10:02:45PM -0700, Samudrala, Sridhar wrote: >> On 6/11/2018 7:17 PM, Michael S. Tsirkin wrote: >>> On Tue, Jun 12, 2018 at 09:54:44AM +0800, Jason Wang wrote: >>>> On 2018?06?12? 01:26, Michael S. Tsirkin wrote: >>>>> On Mon, May 07, 2018 at 04:09:54PM -0700, Sridhar Samudrala
2019 Mar 21
0
[summary] virtio network device failover writeup
On Thu, Mar 21, 2019 at 04:16:14PM +0200, Liran Alon wrote: > > > > On 21 Mar 2019, at 15:51, Michael S. Tsirkin <mst at redhat.com> wrote: > > > > On Thu, Mar 21, 2019 at 03:24:39PM +0200, Liran Alon wrote: > >> > >> > >>> On 21 Mar 2019, at 15:12, Michael S. Tsirkin <mst at redhat.com> wrote: > >>> >
2018 May 02
3
[PATCH net-next v9 3/4] virtio_net: Extend virtio to use VF datapath when available
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.