similar to: [GIT PULL net-2.6] vhost-net: more error handling fixes

on an ASUS P5K-E wifi (wifi disabled in bios) board with: 02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8056 PCI-E Gigabit Ethernet Controller (rev 12) centos 5.1 did not configure the device. Anyone else see this or have a solution? Tried forcing sky2 module, but init just says device does not seem to be present even tho lspci shows it on the bus. Is there another kernel

On 24/11/2019 14:33, Ebed wrote: > Hi, > > Here it is... > > > 05:00.0 Ethernet controller [0200]: Marvell Technology Group Ltd. 88E8039 > PCI-E Fast Ethernet Controller [11ab:4353] (rev 14) Thanks, that device requires the Marvell sky2 driver which is not supported in el8. I have built you a driver for CentOS 8.0 and uploaded it to the elrepo repository. It should be

I have a CentOS 5.2 install on a machine with the Marvell nic issue outlined in http://bugs.centos.org/view.php?id=2612. I have a few questions regarding this, what does the # echo "11ab 4364" > /sys/bus/pci/drivers/sky2/new_id line do? Obviously it starts right after but what specifically is the "11ab 4364" part? Also, how do I get this to load across reboots? I have the

As far as I work out the version of the Dom0 linux kernel has to be 2.6.18. This is causing me a lot of problem, because the driver support in 2.6.18 is slowly falling behind, and I finding that more modern hardware isn''t supported by the 2.6.18 drivers. Is it possible to use a more recent version of the kernel for Dom0, or am I stuck with 2.6.18? Is there another way I can use more

Hello, I''m facing a strange issue with network card PCI passthrough on my openwrt test domU. - With network PCI passthrough, DNS lookup failed for some domains (exemple, google.com) but not for other (free.fr my ISP, or my domain jbfavre.org). I can ping an IP address without any problem. - Starting domU as a "normal" (ie without PCI passthrough), no problem. As far as I can

i''m running Xen Host & Guest, both version xen-4.1.2/64-bit. i pass through an ethernet NIC from host to guest. it uses the standard Marvell ''sky2'' kernel module. when i start the guest, usually -- but not always -- the NIC gets properly passed through and setup, and is completely usable. if i shutdown & restart the Guest, sometimes -- maybe 20% of the time?

Has anyone had any luck getting this to work? The kernel provide skge, sky2 and sk98lin modules all fail to load. I was able to download the latest version from the syskonnect.de site, and with some hacking/klduging of their install script managed to compile the module in there (a newer version of sk98lin, it seems) which recognised the card... but this isn't really sustainable 'cos new

Did a ''git pull'' a few minutes ago and tried to rebuild my kernel and was given this error: make CHK include/linux/version.h CHK include/linux/utsrelease.h SYMLINK include/asm -> include/asm-x86 CALL scripts/checksyscalls.sh CHK include/linux/compile.h CC drivers/acpi/acpica/hwsleep.o drivers/acpi/acpica/hwsleep.c: In function

Hello, I had noticed strange crackling sound on my phone calls going through my zaptel device (TDM400P), so i decided to check on possible timer issue, and found lots of issues on forums concerning the sensibility of zaptel with IRQs, and tried about everything: moving PCI slots, noapic and acpi=off boot options, play with different kernel options: iosched/preemption/timer/..., play with

Hello, Similar to others I have freezeups on the system, it is consistent with high IO load. If the system runs (even with multiple) XenU it does not happen. But I can consistently force the situation to occur. Running 4 dd processes dumping 20GB each on a LVM/mdadm soft RAID5 volume it consistenly crashes in a DomU. Running without XEN I do not see the problem at all - (e.g. after about 3TB of

Hi, after I saw that my machine was having problems to forward more than 200 Mbit/s, I decided to profile the kernel and find out the hotspots. This is what I found: [...] 1028 bridge.ko __br_forward 1033 bridge.ko br_nf_forward_finish 1074 bridge.ko ip_sabotage_in 1119 ebtable_filter.ko ebt_hook 1177 sky2.ko

Hi, I cannot have suspend and hibernate working on a Samsung NC10 (netbook) running CentOS 5.4 i386. When I try suspending/hibernating the screen becomes black (with a few logs, like "shrinking memory" for hibernate) and then the computer hangs and I have to force a shutdown with the power button. This wiki page seems to say that it should work out of the box:

Dear Devs, I have x4 4TB HDDs formatted with: mkfs.btrfs -L bu-16TB_0 -d raid1 -m raid1 /dev/sd[cdef] /etc/fstab mounts with the options: noatime,noauto,space_cache,inode_cache All on kernel 3.8.13. Upon using rsync to copy some heavily hardlinked backups from ReiserFS, I''ve seen: The following "block rsv returned -28" is repeated 7 times until there is a call trace

Hi Michael, Em sex., 22 de nov. de 2019 ?s 07:31, Michael S. Tsirkin <mst at redhat.com> escreveu: > > On Thu, Nov 21, 2019 at 10:36:36PM -0300, Julio Faracco wrote: > > Driver virtio_net is not handling error events for TX provided by > > dev_watchdog. This event is reached when transmission queue is having > > problems to transmit packets. This could happen for any

Hi Michael, Em sex., 22 de nov. de 2019 ?s 07:31, Michael S. Tsirkin <mst at redhat.com> escreveu: > > On Thu, Nov 21, 2019 at 10:36:36PM -0300, Julio Faracco wrote: > > Driver virtio_net is not handling error events for TX provided by > > dev_watchdog. This event is reached when transmission queue is having > > problems to transmit packets. This could happen for any

A bunch of drivers want to know which tx queue triggered a timeout, and virtio wants to do the same. We actually have the info to hand, let's just pass it on to drivers. Note: tested with an experimental virtio patch by Julio. That patch itself isn't ready yet though, so not included. Other drivers compiled only. Michael S. Tsirkin (3): netdev: pass the stuck queue to the timeout

Testing with a modified copy of the fsfuzz, the btrfs filesystem hanged with the following output in dmesg. The system still remain responsive, except for the terminal that was doing the testing. Any attempt to list files in the btrfs-mounted directory will block as well. I am not sure how to proceed from here. Possibly to reboot the system next. But anyone can shed some suggestion?

Does anyone know if the "sky2 transmitter lockup" bug that was in 4.4 has been resolved in CentOS 5? This bug causes the sky2 NIC driver to lock up when transferring large amounts of data through the NIC. Here is a link to the bug at CentOS: http://bugs.centos.org/view.php?id=1540 The status still says "open". Thanks, Joe

Having done a current checkout, creating a new FS and running iozone [1] on it results in an oops [2]. remove_suid is called, accessing offset 14 of a NULL pointer. Let me know if you''d like me to test any fix, do further debugging or get more information. Thanks, Daniel --- [1] # mkfs.btrfs /dev/sda4 # mount /dev/sda4 /mnt /mnt# iozone -a . --- [2] [ 899.118926] BUG: unable to

On Sun, 24 Nov 2019 18:29:49 -0500, Michael S. Tsirkin wrote: > netdev: pass the stuck queue to the timeout handler > > This allows incrementing the correct timeout statistic without any mess. > Down the road, devices can learn to reset just the specific queue. FWIW Acked-by: Jakub Kicinski <jakub.kicinski at netronome.com>