Displaying 20 results from an estimated 206 matches for "repluging".
Did you mean:
replugging
2019 Aug 08
4
[PATCH v2 0/2] virtio_console: fix replug of virtio console port
This patch series fixes the issue with unplug/replug of a port in virtio
console device, which fails with an error "Error allocating inbufs\n".
Patch 2 makes virtio packed ring code compatible with virtio split ring.
Tested the packed ring code with the qemu virtio 1.1 device code posted
here [1].
Changes from v1[2]
-----
Make virtio packed ring code compatible with split ring -
2019 Aug 13
2
[PATCH v4 0/2] virtio_console: fix replug of virtio console port
This patch series fixes the issue with unplug/replug of a port in virtio
console driver which fails with an error "Error allocating inbufs\n".
Patch 1 updates the next avail index for packed ring code.
Patch 2 makes use of 'virtqueue_detach_unused_buf' function to detach
the unused buffers during port hotunplug time.
Tested the packed ring code with the qemu virtio 1.1 device
2019 Aug 09
5
[PATCH v3 0/2] virtio_console: fix replug of virtio console port
This patch series fixes the issue with unplug/replug of a port in virtio
console driver which fails with an error "Error allocating inbufs\n".
Patch 1 makes use of 'virtqueue_detach_unused_buf' function to detach
the unused buffers during port hotunplug time.
Patch 2 updates the next avail index for packed ring code.
Tested the packed ring code with the qemu virtio 1.1 device
2004 Oct 06
4
TDM400P stop responding
iH
have a TDM400 w/ 1 FXS & 1FXO card. after about a day or so the FXO
stops working. after a reboot i get the following error. to get the
card working again i have to shutdown, physically unplug/replug the
card (reboot only, power off/on does not work) any ideas what may be
going wrong here?
thanks
- hcir
Zaptel Configuration
======================
Channel map:
Channel 01: FXO
2008 Jun 04
2
panic on `zfs export` with UNAVAIL disks
hi list,
initial situation:
SunOS alusol 5.11 snv_86 i86pc i386 i86pc
SunOS Release 5.11 Version snv_86 64-bit
3 USB HDDs on 1 USB hub:
zpool status:
state: ONLINE
NAME STATE READ WRITE CKSUM
usbpool ONLINE 0 0 0
mirror ONLINE 0 0 0
c7t0d0p0 ONLINE 0 0 0
c8t0d0p0
2006 Jun 15
4
devid support for EFI partition improved zfs usibility
Hi, guys,
I have add devid support for EFI, (not putback yet) and test it with a
zfs mirror, now the mirror can recover even a usb harddisk is unplugged
and replugged into a different usb port.
But there is still something need to improve. I''m far from zfs expert,
correct me if I''m wrong.
First, zfs should sense the hotplug event.
I use zfs status to check the status of the
2009 Aug 13
2
UPS disconnects from upsmon after several hours Freebsd 7.2
I have successfully compiled NUT, and have noticed usb weirdness. The
machine disconnected at 10:25 this morning tripplite was claiming 'stale
data'. I noticed it this morning after trying to look at things. I
'replugged' the ups back into the usb port and it was fine. I am running
2.4.1, freebsd, tripplite Su2200XLA. I did notice that the usb cable was a
little wobbly. Any other
2019 Mar 04
5
[PATCH] virtio_console: free unused buffers with virtio port
The commit a7a69ec0d8e4 ("virtio_console: free buffers after reset")
deffered detaching of unused buffer to virtio device unplug time.
This causes unplug/replug of single port in virtio device with an
error "Error allocating inbufs\n". As we don't free the unused buffers
attached with the port. Re-plug the same port tries to allocate new
buffers in virtqueue
2019 Mar 04
5
[PATCH] virtio_console: free unused buffers with virtio port
The commit a7a69ec0d8e4 ("virtio_console: free buffers after reset")
deffered detaching of unused buffer to virtio device unplug time.
This causes unplug/replug of single port in virtio device with an
error "Error allocating inbufs\n". As we don't free the unused buffers
attached with the port. Re-plug the same port tries to allocate new
buffers in virtqueue
2009 Feb 24
4
7.1-R to RELENG_7 upgrade breaks re nic
Hi,
I upgraded my 7.1-RELEASE system to RELENG_7 yesterday and after
booting, re0 works for only a short time, then gives "re0: PHY read
failed" over and over. Does anyone have a suggestion on how to debug?
Thanks,
Steve
2003 Nov 04
3
*, Fritz!PCI and strange behavior
I'm testing * (CVS-09/16/03-02:07:49 with zaprtc 0.0.1) with Fritz!PCI
(chan_capi 0.3.0), and have a couple of funny things - I wonder if anyone
else has seen them:
- Now and then, * just exits. Until now I had lowish-level verbosity on,
so all I saw was 'Executing last minute cleanups'. What can trigger
* exits? (in other words, what should I pay attention to when
attempting to
2014 Oct 14
1
Belkin unk ups
On Tuesday 14 October 2014 08:19:02 Charles Lepple did opine
And Gene did reply:
> usbhid-ups
Added that, but only get this at "sudo service nut start"
gene at coyote:/etc/init.d$ sudo service nut start
* Starting Network UPS Tools
[ OK ]
2006 Jul 13
2
MGE Pulsar Extreme - restart problem
Hello,
looking for replacements for some older Powerware equipment I found the MGE
Pulsar Extreme 1000C and I'm currently testing one with nut-2.0.3 on a
self-brewn i386-linux.
Upto now everything seems to work fine - except I can't get the power outlets
switching on again after mains returns. As this works with Personal
Solution-Pac 2 on W2k I thought that there might be a way to
2007 Jul 01
1
Asterisk strange behaviour
Hi all
I?m a newbie to asterisk and I have install and configure asterisk 1.4.5
I have made some test and have face a strange behaviour
I hava a simple dialplan when a call is receive from PTSN,
[PSTN]
exten => s,1,Answer()
exten => s,2,Playback(intro-sicx) ; Listen to your voice
exten => s,3,Dial(SIP/steph)
exten => s,4,Hangup()
I got the following when a call is
2009 Sep 22
2
rescan usb hd
I have a usb hd that I use for backup. Occasionally it dies.
scsi 6:0:0:0: rejecting I/O to dead device
scsi 6:0:0:0: rejecting I/O to dead device
scsi 6:0:0:0: rejecting I/O to dead device
scsi 6:0:0:0: rejecting I/O to dead device
Buffer I/O error on device sdc1, logical block 0
lost page write due to I/O error on sdc1
EXT2-fs error (device sdc1): read_inode_bitmap: Cannot read inode
bitmap -
2006 Nov 04
1
Calibrating the Battery on an MGE Ellipse Premium 1200
My new MGE Ellipse Premium 1200 is now working fine. I've tested
pulling the plug and the computer shuts down properly and comes back
up when I replug. The only strange behaviour is that when I put the
power back on the battery shows as being at 86%. If it was at 86% it
should have lasted longer. Is there any calibration step I can do? The
only commands the ups seems to support are:
$ upscmd
2005 Jul 02
2
Rebooting not working
Hi!
I've installed NUT 2.0.2 to work with my MGE Protection Center and it
works but for one thing. When I reboot the computer, at startup
upsdrvctl/newhidups can't find the UPS so I have to manually unplug,
replug and start upsdrvctl/upsd every time. I've installed from
sourcecode onto a Gentoo machine. Where should I look for the problem
(USB/hotplug/newhidups/somewhere else)?
2014 Sep 27
2
problems with usb stick after suspend and wake up
Dear all,
(please Cc)
I am running latest kernel (3.17-rc6) and I see corruption of an usb3.0
device usb stick. Strange errors, impossibility to mount.
Repeated unplugging and replugging helps sometimes, in all cases
recovery is necessary.
Is this a know problem, a problem of my system
Debian/sid, uptodate, self-compiled kernel
of the suspend program (that initiates the suspend),
the usb
2019 Aug 08
1
[PATCH v2 1/2] virtio_console: free unused buffers with port delete
On Thu, Aug 08, 2019 at 05:06:05PM +0530, Pankaj Gupta wrote:
> The commit a7a69ec0d8e4 ("virtio_console: free buffers after reset")
> deferred detaching of unused buffer to virtio device unplug time.
>
> This causes unplug/replug of single port in virtio device with an
> error "Error allocating inbufs\n". As we don't free the unused buffers
>
2010 May 14
1
aastra pt 480e phone
hello
i hope i am posting to the right list, i am a totally blind user, and i want
to reprogram my aastra pt 480e phone, my friend used the web configurator,
but i think he programmed thw wrong codes, a few questions, is it possible
to damage the phone by programming it wrong? also, how does one reset it
literally to factory defaults? as unplugging it and replugging it back into
the wall