search for: 1d

...17 91 49 5e 5e bc fe bb 46 88 ac 1b 0.963375 0a a0 ed 01 07 07 bb 46 82 ae 1b 09 0.963387 getbaseinfo: requesting 25 bytes from ser_get_buf_len() 2.048306 getbaseinfo: received 25 bytes from ser_get_buf_len() 2.048343 CommReceive: RecPack: (25 bytes) => a0 04 02 06 1d 0d 03 00 00 00 01 00 17 2.048358 91 49 5e 5e dc fe bb 47 83 ad 1a 09 2.048371 getbaseinfo: requesting 25 bytes from ser_get_buf_len() 3.132287 getbaseinfo: received 25 bytes from ser_get_buf_len() 3.132321 CommReceive: RecPack: (25 bytes) => a0 0a 02 07 1d 0d 03 00...

Hi, I am still trying to assign pci or usbs to a domU. I get to the point where pciback seizes the devices (5 usb and 2 pci). I modified the configuration of the domU with pci = [ ''00:1d.0'' , ''00:1d.1'' , ''00:1d.2'' , ''00:1d.3'' , ''00:1d.7'', ''02:01.0'' , ''02:02.0'' ] but nothing shows up in the domU: [root@web ~]# lsusb [root@web ~]# lspci pcilib: Cannot open /proc/bus/...

...and plug into the card, both the keyboard and mouse work nicely. Any thoughts on how to get the onboard USB working? Thanks, Adam Here are some relevant config details: # grub.conf entry, linux module line module /boot/vmlinuz-2.6.16-xen root=/dev/sdb2 ro pciback.hide= (04:00.0)(05:00.0)(00:1d.0)(00:1d.1)(00:1d.2)(00:1d.3)(00:1d.7)(01:00.0) # "pci" line from domU that gets the GPU: pci = [ ''05:00.0'', ''00:1d.0'', ''00:1d.1'', ''00:1d.2'', ''00:1d.3'', ''00:1d. 7'', ''01:...

...ktrace output. Here are the bytes received, without the other messages: Network UPS Tools - Microsol Solis UPS driver 0.63 (2.7.3.1) CommReceive: RecPack: (25 bytes) => 00 17 91 49 5e 5e bc fe bb 46 88 ac 1b 0a a0 ed 01 07 07 bb 46 82 ae 1b 09 CommReceive: RecPack: (25 bytes) => a0 04 02 06 1d 0d 03 00 00 00 01 00 17 91 49 5e 5e dc fe bb 47 83 ad 1a 09 CommReceive: RecPack: (25 bytes) => a0 0a 02 07 1d 0d 03 00 00 00 01 00 17 91 49 5e 5e e3 fe bb 46 88 ac 1a 0a CommReceive: RecPack: (25 bytes) => a0 f4 01 08 1d 0d 03 00 00 00 01 00 17 91 49 5e 5e d1 fe bb 46 88 ad 02 0b CommReceive...

server:~# dmesg|grep pciback [ 0.000000] Kernel command line: root=/dev/hda1 ro console=tty0 pciback.permissive pciback.hide=(00:1d.00)(00:1d.01)(00:1d.07) [ 0.000000] Unknown boot option `pciback.permissive'': ignoring [ 1.210945] pciback 0000:00:1d.0: seizing device [ 1.211082] pciback 0000:00:1d.1: seizing device [ 1.211215] pciback 0000:00:1d.7: seizing device [ 41.327529] pciback: vpci: 0000:00:1d.0:...

Thanks to the kind person(s) who worked on this. I am using PCI passthrough right now and it works. I hope support is added for VT domains too; That would be extremely useful. So far I have tried a NIC, USB, and PCI Video. The NIC works flawlessly. USB works as long as the devices are present at the time the domain is started. Hotplugging USB devices seems not to work. If I open

...| grep -P "(nouveau|pcieport)" <6>[ 1.020802] pcieport 0000:00:1c.0: AER enabled with IRQ 122 <6>[ 1.020819] pcieport 0000:00:1c.4: AER enabled with IRQ 123 <6>[ 1.020833] pcieport 0000:00:1c.5: AER enabled with IRQ 124 <6>[ 1.020852] pcieport 0000:00:1d.3: AER enabled with IRQ 126 <6>[ 1.020875] pcieport 0000:00:1c.0: Signaling PME with IRQ 122 <6>[ 1.020883] pcieport 0000:00:1c.4: Signaling PME with IRQ 123 <6>[ 1.020890] pcieport 0000:00:1c.5: Signaling PME with IRQ 124 <6>[ 1.020902] pcieport 0000:00:1d.0: Si...

...tdown after a while and so on) but in user.log is lot of lines like these at below (two lines are generated in every second or two) it starts with "klogd: [? ?34.519386] drivers/usb/core/file.c: removing 96 minor" ant then Dec 12 13:48:22 my-server klogd: [11313.651271] uhci_hcd 0000:00:1d.1: reserve dev 2 ep81-INT, period 16, phase 8, 118 us Dec 12 13:48:23 my-server klogd: [11313.903430] uhci_hcd 0000:00:1d.1: release dev 2 ep81-INT, period 16, phase 8, 118 us Dec 12 13:48:23 my-server klogd: [11313.903684] uhci_hcd 0000:00:1d.1: reserve dev 2 ep81-INT, period 16, phase 8, 118 us D...

Hi, I have some errors in dmesg: [ 542.255788] ata1.00: exception Emask 0x0 SAct 0xffffff SErr 0x0 action 0x0 [ 542.255797] ata1.00: irq_stat 0x40000008 [ 542.255805] ata1.00: failed command: READ FPDMA QUEUED [ 542.255821] ata1.00: cmd 60/00:00:1a:b7:7a/04:00:1d:00:00/40 tag 0 ncq 524288 in [ 542.255824] res 41/40:00:a0:b7:7a/00:00:1d:00:00/40 Emask 0x409 (media error) <F> [ 542.255831] ata1.00: status: { DRDY ERR } [ 542.255837] ata1.00: error: { UNC } [ 542.264434] ata1.00: configured for UDMA/133 [ 542.264505] ata1: EH complete [ 54...

...;'m sure, been told a lot of time but i haven''t found any things to solve my problems. Here is it: I wan''t to export a usb port on DomU (CentOS 5) from my Dom0 (Debian Etch). I have only succeded with the pci export but with the next command: "xm create machine pci=00:1d.0" With having many differents syntaxes in the machine configuration file would not work for me. Does anybody know how to do it in the conf file? Or perhaps with a usb export (it would be what i want finally)? Xen version : 3.0.3-1 from Debian stable packages Thanks. Regards. Julien. _...

...gt; > I resolve the problem of network conection loose, but still a dude of how it happend and how it can be fixe. When I check with arping the MAC of sever change, for example rommel at p6:~$ arping 192.168.41.4 ARPING 192.168.41.4 from 192.168.41.6 enp3s0 Unicast reply from 192.168.41.4 [00:1D:09:FF:44:4B] 0.653ms Unicast reply from 192.168.41.4 [6C:92:BF:26:C7:03] 0.683ms Unicast reply from 192.168.41.4 [6C:92:BF:26:C7:03] 0.622ms Unicast reply from 192.168.41.4 [6C:92:BF:26:C7:03] 0.631ms ^CSent 3 probes (1 broadcast(s)) Received 4 response(s) The first answer is with a MAC difere...

Hello, I can see that there is an implementation/emulation of ddi_pathname in DTrace, but I''m a bit confused about the capabilities and invocation of this function. I would like to diplay the path to the block device from bdev_strategy and other io:genunix::start probes. If someone is familiar with ddi_pathname, could you please provide an example invocation? Thanks, Michael This

...he graphics card and all the USB hosts as well: (from dmesg) pciback 0000:00:02.0: seizing device pciback 0000:00:02.1: seizing device pciback 0000:00:1a.0: seizing device pciback 0000:00:1a.1: seizing device pciback 0000:00:1a.7: seizing device pciback 0000:00:1b.0: seizing device pciback 0000:00:1d.0: seizing device pciback 0000:00:1d.1: seizing device pciback 0000:00:1d.2: seizing device pciback 0000:00:1d.7: seizing device 00:02.{0,1} correspond to the graphics card, the rest are USB devices. This is my winxp.hvm: kernel = "/usr/lib/xen/boot/hvmloader" builder=''hvm'...

...4 (rev 02) 00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 02) 00:1a.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 02) 00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 02) 00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 02) 00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 02) 00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 02) 00:1d.7 USB Controll...

...gt;> is.vector(x) >> #> [1] FALSE >> >> is.null(dim(x)) >> #> [1] TRUE >> > > I don't know of one. I can't think of nontrivial cases where that > distinction matters; do you know of any where base functions act differently > on vectors and 1D arrays? (A trivial example is that dimnames(x) gives > different results for a named vector and an array with dimnames.) I was thinking primarily of completing the set of is.matrix() and is.array(), or generally, how do you say: is `x` a 1d dimensional thing? (I don't have any feel for wh...

...e master. Forcing election. 04/29/1998 12:08:34 ***** Samba name server xxx.xxx.xxx.2 has stopped being a local master browser for workgroup MY.WORKGROUP.NAME on subnet xxx.xxx.xxx.2 ***** register_name_response: server at IP xxx.xxx.xxx.74 rejected our name registration of MY.WORKGROUP.NAME<1d> with error code 6. become_local_master_fail2: failed to register name MY.WORKGROUP.NAME<1d> on subnet xxx.xxx.xxx.2. Failed to become a local master browser. standard_fail_register: Failed to register/refresh name MY.WORKGROUP.NAME<1d> on subnet xxx.xxx.xxx.2 query_name_response: Mu...

On Sat, Jul 7, 2018 at 1:50 PM, Gabe Becker <becker.gabe at gene.com> wrote: > Hadley, > >> >> I was thinking primarily of completing the set of is.matrix() and >> is.array(), or generally, how do you say: is `x` a 1d dimensional >> thing? > > > Can you clarify what you mean by dimensionality sense and specifically 1d > here? What do we call a vector that is not an array? (or matrix) What do we call an object that acts 1-dimensional? (i.e. has length(dim()) %in% c(0, 1)) ? > You can also...

...lspci 00:00.0 Host bridge: Intel Corporation 82945G/GZ/P/PL Memory Controller Hub (rev 02) 00:02.0 VGA compatible controller: Intel Corporation 82945G/GZ Integrated Graphics Controller (rev 02) 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01) 00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 01) 00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 01) 00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 01) 00:1d.3 USB Controll...

...voip200-009d24b0' wanrouter status: wanrouter status Devices currently active: wanpipe1 wanpipe2 wanpipe3 wanpipe4 wanpipe5 wanpipe6 wanpipe7 wanpipe8 Wanpipe Config: Device name | Protocol Map | Adapter | IRQ | Slot/IO | If's | CLK | Baud rate | wanpipe1 | N/A | A101/1D/A102/2D/4/4D/8| 17 | 4 | 1 | N/A | 0 | wanpipe2 | N/A | A101/1D/A102/2D/4/4D/8| 17 | 4 | 1 | N/A | 0 | wanpipe3 | N/A | A101/1D/A102/2D/4/4D/8| 17 | 4 | 1 | N/A | 0 | wanpipe4 | N/A | A101/1D/A102/2D/4/4D/8| 1...

Hi list, I've recently managed to install CentOS 4.4 on an Apple Mac Pro. Functionality-wise everything works great, but when trying to benchmark the system, I don't get stable runtimes, they differ by more than 30%. For example a benchmark run with our PDE solving code takes between 500 and 800 s on the completely unloaded machine. Suspicious kernel output (complete output attached):