search for: 00

Hi. My Belkin UPS F6C1100-UNV works fine with megatec_usb version 1.6 (2.4.1). However, it doesn't work with 2.4.2 nor 2.4.3. # /lib/nut/megatec_usb_old -D -a belkin Network UPS Tools - Megatec protocol driver 1.6 (2.4.1) Serial-over-USB transport layer 0.10 debug level is '1' Starting UPS detection process.....

Dear List Users Greetings, i have come across the problem where CentOS 6.3 x64 has more than 700 processes running. i am not sure where to start, what in normal or abnormal. [root at jet]# ps -A PID TTY TIME CMD 1 ? 00:00:03 init 2 ? 00:00:00 kthreadd 3 ? 00:00:00 migration/0 4 ? 00:00:00 ksoftirqd/0 5 ? 00:00:00 migration/0...

...i?d used tcpdump to see whats going on and found these errormessages ouer network is quite small, the linuxserver(samba), some windoofclients and the plotter_pc ( this one runs as a MSdosclient and searches a pathstructure for new files) what is this SNAP length ??? and how to increase it ? 00:14:04.556765 plotter.godstream.net.46135 > godstream.netbios-ssn: P 870:942(72) ack 529 win 1450 >>> NBT Packet NBT Session Packet Flags=0x0 Length=68 WARNING: Short packet. Try increasing the snap length (44) SMB PACKET: SMBsearch (REQUEST) SMB Command = 0x81 Error class = 0x0 E...

I mistakenly only replied to Yijing Wang the first time. Here are the further details. uname -a: Linux p5-133 3.15.2-p5-133 #1 Thu Jun 26 22:56:27 EDT 2014 i586 GNU/Linux Here is the output from lspci -vvvxxx: root at p5-133:~# cat lspci.txt 00:00.0 Host bridge: Intel Corporation 430FX - 82437FX TSC [Triton I] (rev 01) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- &lt...

...amd_iommu" as xen boot parameter. 1-cleanup.patch: code cleanup, bug fix, minor enhancements to existing amd-iommu codes. 2-passthru-amd.patch: passthru support, modifications to exsiting amd-iommu codes. 3-passthru-xen.patch: passthru support, minimodifications to in xen and vtd code. 4-ht1100.patch: fixup to ht1100 chipset detection. Signed-off-by: Wei Wang <wei.wang2@amd.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Full_Name: Bas Zimmerman Version: 2.7.0 (2008-04-22) OS: Windows 2000 Pro SP 4 Eng Submission from: (NULL) (62.51.53.106) Running the following line of the R-code SurvivalEnsembles.R, part of the MBoost package results in a program crash: 'AMLrf <- cforest(I(log(time)) ~ ., data = AMLlearn, control = ctrl, weights =...

Yijing, cat /sys/bus/pci/devices/0000\:00\:0e.0/msi_bus returns 1, suggesting that it supports MSI. However, this "00:0e.0 PCI bridge: PLX Technology, Inc. PEX8112 x1 Lane PCI Express-to-PCI Bridge (rev aa)" is a component of the addin card. Wouldn't the lack of support for MSI by the chipset "00:00.0 Host bridge:...

...ery old board. The nouveau code does: pmc->use_msi = pci_enable_msi(device->pdev) == 0; Does it need to do more checking than that before trying to enable MSI on the device? Could it be that the linux pci subsystem is missing on inheriting MSI capabilities somewhere? Thanks, -ilia [1] 00:00.0 Host bridge [0600]: Intel Corporation 430FX - 82437FX TSC [Triton I] [8086:122d] (rev 01) Flags: bus master, medium devsel, latency 64 00:0e.0 PCI bridge [0604]: PLX Technology, Inc. PEX8112 x1 Lane PCI Express-to-PCI Bridge [10b5:8112] (rev aa) (prog-if 00 [Normal decode]) Fl...

...virtio_pci_remove(), vp_dev is still used after being freed in unregister_virtio_device() (in virtio_pci_release_dev() more precisely). I don't know the proper way to fix this. Here is the KASan output: [ 467.987227] ================================================================== [ 467.990023] BUG: KASAN: use-after-free in virtio_pci_remove+0x37/0x70 [virtio_pci] at addr ffff880035364540 [ 467.993397] Read of size 8 by task modprobe/12507 [ 467.995656] ============================================================================= [ 467.998737] BUG kmalloc-2048 (Tainted: G B D C...

...virtio_pci_remove(), vp_dev is still used after being freed in unregister_virtio_device() (in virtio_pci_release_dev() more precisely). I don't know the proper way to fix this. Here is the KASan output: [ 467.987227] ================================================================== [ 467.990023] BUG: KASAN: use-after-free in virtio_pci_remove+0x37/0x70 [virtio_pci] at addr ffff880035364540 [ 467.993397] Read of size 8 by task modprobe/12507 [ 467.995656] ============================================================================= [ 467.998737] BUG kmalloc-2048 (Tainted: G B D C...

On Thu, Jul 3, 2014 at 10:35 PM, Yijing Wang <wangyijing at huawei.com> wrote: > Hi Brian, > From your 01:00.0 VGA compatible controller PCI config register, it supports 1 MSI vector, so I think this > card has no problem. But you didn't answer what's the pci_enable_msi() return during it enable MSI fail. > > You can check PCI bus whether support MSI like: > > cat /sys/bus/pci/devic...

Hi Brian, From your 01:00.0 VGA compatible controller PCI config register, it supports 1 MSI vector, so I think this card has no problem. But you didn't answer what's the pci_enable_msi() return during it enable MSI fail. You can check PCI bus whether support MSI like: cat /sys/bus/pci/devices/00:0e.0/msi_bus Oth...

Hallo, I have this dataset with repeated measures. There are two within-subject factors, "formant" (2 levels: 1 and 2) and "f2 Ref" (25 levels: 670, 729, 788, 846, 905, 1080, 1100, 1120, 1140, 1170, 1480, 1470, 1450, 1440, 1430, 1890, 1840, 1790, 1740, 1690, 2290, 2210, 2120, 2040, 1950), and one between-subject factor, lang (2 levels:1 and 2). The response variable is "thresh". I ran a three-way ANOVA with repeated measures: vThresh<-read.table("rR...

On 2014/7/4 10:45, Brian Becker wrote: > Yijing, > > cat /sys/bus/pci/devices/0000\:00\:0e.0/msi_bus returns 1, suggesting > that it supports MSI. However, this "00:0e.0 PCI bridge: PLX > Technology, Inc. PEX8112 x1 Lane PCI Express-to-PCI Bridge (rev aa)" > is a component of the addin card. Wouldn't the lack of support for MSI > by the chipset "0...

...nd i'd like to know if there will be support on this brand and model. When i reconnect it, i get this: [739610.568073] usb 1-1: USB disconnect, address 2 [739617.020038] usb 1-1: new low speed USB device using uhci_hcd and address 3 [739617.233813] usb 1-1: New USB device found, idVendor=0665, idProduct=5161...

On 2014/7/4 10:43, Ilia Mirkin wrote: > On Thu, Jul 3, 2014 at 10:35 PM, Yijing Wang <wangyijing at huawei.com> wrote: >> Hi Brian, >> From your 01:00.0 VGA compatible controller PCI config register, it supports 1 MSI vector, so I think this >> card has no problem. But you didn't answer what's the pci_enable_msi() return during it enable MSI fail. >> >> You can check PCI bus whether support MSI like: >> >> ca...

...ba configuration: [global] workgroup = DEV netbios name = CLUSTER1 vfs objects = fileid acl_xattr fileid:mapping = fsid private dir = /mnt/common/private clustering = yes encrypt passwords = yes domain logons = no log level = 1 syslog = 0 max log size = 6000 socket options = TCP_NODELAY IPTOS_LOWDELAY os level = 0 local master = no preferred master = no domain master = no invalid users = root guest account = nobody map to guest = Bad User wide links = no force unknown acl user = yes winbind separator = +...

...structure(list(date = structure(c(1L, 2L, 3L, 4L, 5L, 6L, 7L, 8L, 9L, 10L, 11L, 12L, 13L, 14L, 15L, 16L, 17L, 18L, 19L, 20L, 5L, 6L, 7L, 8L, 9L, 10L, 11L, 12L, 13L, 14L, 15L, 16L, 17L, 18L, 19L, 20L, 21L, 22L, 23L, 24L, 7L, 8L, 9L, 10L, 11L, 12L, 13L, 14L, 15L, 16L), .Label = c("2012-01-25 18:00:00", "2012-01-26 00:00:00", "2012-01-26 06:00:00", "2012-01-26 12:00:00", "2012-01-26 18:00:00", "2012-01-27 00:00:00", "2012-01-27 06:00:00", "2012-01-27 12:00:00", "2012-01-27 18:00:00", "2012-01-28 00:00:00...

On Thu, Jan 14, 2016 at 02:25:50PM +0100, Jerome Marchand wrote: > Hi Michael, > > KASan detected a use-after-free error in virtio-pci remove code. In > virtio_pci_remove(), vp_dev is still used after being freed in > unregister_virtio_device() (in virtio_pci_release_dev() more > precisely). I don't know the proper...

...structure(list(date = structure(c(1L, 2L, 3L, 4L, 5L, 6L, 7L, 8L, 9L, 10L, 11L, 12L, 13L, 14L, 15L, 16L, 17L, 18L, 19L, 20L, 5L, 6L, 7L, 8L, 9L, 10L, 11L, 12L, 13L, 14L, 15L, 16L, 17L, 18L, 19L, 20L, 21L, 22L, 23L, 24L, 7L, 8L, 9L, 10L, 11L, 12L, 13L, 14L, 15L, 16L), .Label = c("2012-01-25 18:00:00", "2012-01-26 00:00:00", "2012-01-26 06:00:00", "2012-01-26 12:00:00", "2012-01-26 18:00:00", "2012-01-27 00:00:00", "2012-01-27 06:00:00", "2012-01-27 12:00:00", "2012-01-27 18:00:00", "2012-01-28 00:00:00...