search for: op_mode

With CentOS 7.2 a laptop wireless card is recognized in dmesg, but nonfunctional. Toggling the hardware wifi switch causes the Bluetooth icon to appear and disappear. The network configuration window shows the Wireless tab greyed out. Rebooting with the bluetooth enabled does not help. It appears the appropriate driver is iwlwifi, which is what works in Fedora and appears to be available and

A firmware error is triggered when configuring a 9k MTU on the PF after switching to switchdev mode and then using a vdpa device with larger (1k) rings: mlx5_cmd_out_err: CREATE_GENERAL_OBJECT(0xa00) op_mod(0xd) failed, status bad resource(0x5), syndrome (0xf6db90), err(-22) This is due to the fact that the hw VQ size parameters are computed based on the umem_1/2/3_buffer_param_a/b capabilities

Otherwise the virtqueue object to instate could point to invalid address that was unmapped from the MTT: mlx5_core 0000:41:04.2: mlx5_cmd_out_err:782:(pid 8321): CREATE_GENERAL_OBJECT(0xa00) op_mod(0xd) failed, status bad parameter(0x3), syndrome (0x5fa1c), err(-22) Fixes: cae15c2ed8e6 ("vdpa/mlx5: Implement susupend virtqueue callback") Cc: Eli Cohen <elic at nvidia.com>

On Mon, Mar 20, 2023 at 10:01:05AM +0200, Eli Cohen wrote: > Current code ignores link state updates if VIRTIO_NET_F_STATUS was not > negotiated. However, link state updates could be received before feature > negotiation was completed , therefore causing link state events to be > lost, possibly leaving the link state down. > > Add code to detect if VIRTIO_NET_F_STATUS was set

On Wed, Feb 15, 2023 at 9:31 AM Si-Wei Liu <si-wei.liu at oracle.com> wrote: > > Otherwise the virtqueue object to instate could point to invalid address > that was unmapped from the MTT: > > mlx5_core 0000:41:04.2: mlx5_cmd_out_err:782:(pid 8321): > CREATE_GENERAL_OBJECT(0xa00) op_mod(0xd) failed, status > bad parameter(0x3), syndrome (0x5fa1c), err(-22) > >

On 2/15/2023 8:48 PM, Jason Wang wrote: > On Wed, Feb 15, 2023 at 9:31 AM Si-Wei Liu <si-wei.liu at oracle.com> wrote: >> Otherwise the virtqueue object to instate could point to invalid address >> that was unmapped from the MTT: >> >> mlx5_core 0000:41:04.2: mlx5_cmd_out_err:782:(pid 8321): >> CREATE_GENERAL_OBJECT(0xa00) op_mod(0xd) failed, status

...ages Nov 20 09:24:16 osl-97214 kernel: iwlwifi 0000:04:00.0: firmware: requesting iwlwifi-8000C-17.ucode Nov 20 09:24:16 osl-97214 kernel: iwlwifi 0000:04:00.0: firmware: requesting iwlwifi-8000C-16.ucode Nov 20 09:24:16 osl-97214 kernel: iwlwifi 0000:04:00.0: loaded firmware version 16.242414.0 op_mode iwlmvm and I think the following shows that the device is actually there # lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 003: ID 1...

On Mon, Apr 3, 2023 at 2:47?PM Eli Cohen <elic at nvidia.com> wrote: > > > On 03/04/2023 8:01, Jason Wang wrote: > > On Sun, Apr 2, 2023 at 10:15?PM Eli Cohen <elic at nvidia.com> wrote: > >> Current code ignores link state updates if VIRTIO_NET_F_STATUS was not > >> negotiated. However, link state updates could be received before feature > >>

...: Bluetooth Soft blocked: no Hard blocked: no $ dmesg|grep iwlwifi [ 3.766133] iwlwifi 0000:08:00.0: can't disable ASPM; OS doesn't have ASPM control [ 3.766267] iwlwifi 0000:08:00.0: irq 31 for MSI/MSI-X [ 3.783806] iwlwifi 0000:08:00.0: loaded firmware version 18.168.6.1 op_mode iwldvm [ 3.836905] iwlwifi 0000:08:00.0: CONFIG_IWLWIFI_DEBUG disabled [ 3.836909] iwlwifi 0000:08:00.0: CONFIG_IWLWIFI_DEBUGFS enabled [ 3.836911] iwlwifi 0000:08:00.0: CONFIG_IWLWIFI_DEVICE_TRACING disabled [ 3.836914] iwlwifi 0000:08:00.0: Detected Intel(R) Centrino(R) Wireless-N 223...

...o wake NIC for hcmd Nov 10 14:55:01 orbex kernel: iwlwifi 0000:04:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5 Nov 10 14:55:01 orbex kernel: iwlwifi 0000:04:00.0: Scan failed! ret -5 Nov 10 14:56:37 orbex kernel: iwlwifi 0000:04:00.0: loaded firmware version 17.3216344376.0 op_mode iwlmvm Nov 10 14:56:37 orbex kernel: iwlwifi 0000:04:00.0: Detected Intel(R) Dual Band Wireless AC 3160, REV=0x164 Nov 10 14:56:37 orbex kernel: iwlwifi 0000:04:00.0: base HW address: 34:de:1a:f0:c2:fb Nov 10 14:56:38 orbex NetworkManager[1154]: <info> [1573394198.8523] rfkill1: found Wi-Fi...

Output of dmesg / messages is found in a previous email (buried in the message thread) https://lists.centos.org/pipermail/centos/2016-April/158703.html Any advice? On Wed, Apr 13, 2016 at 10:42 PM, Philip V <pv.bugzilla+centos at gmail.com> wrote: > With CentOS 7.2 a laptop wireless card is recognized in dmesg, but > nonfunctional. Toggling the hardware wifi switch causes the

...0 [ 649.668605] R13: 0000000000000000 R14: 00007fffaa691f68 R15: 00007fffaa691f5c [ 649.756674] iwlwifi 0000:00:14.3: Found debug destination: EXTERNAL_DRAM [ 649.756676] iwlwifi 0000:00:14.3: Found debug configuration: 0 [ 649.757247] iwlwifi 0000:00:14.3: loaded firmware version 46.6bf1df06.0 op_mode iwlmvm [ 649.757275] iwlwifi 0000:00:14.3: Detected Intel(R) Dual Band Wireless AC 9462, REV=0x318 [ 649.765604] iwlwifi 0000:00:14.3: Applying debug destination EXTERNAL_DRAM [ 649.765843] iwlwifi 0000:00:14.3: Allocated 0x00400000 bytes for firmware monitor. [ 649.806204] iwlwifi 0000:00:14.3...

...or Linux, in-tree: [ 2.201933] Copyright(c) 2003- 2014 Intel Corporation [ 2.202170] iwlwifi 0000:03:00.0: can't disable ASPM; OS doesn't have ASPM control [ 2.202390] iwlwifi 0000:03:00.0: irq 45 for MSI/MSI-X [ 2.206761] iwlwifi 0000:03:00.0: loaded firmware version 18.168.6.1 op_mode iwldvm [ 2.208275] media: Linux media interface: v0.10 [ 2.208354] Bluetooth: Core ver 2.19 [ 2.208367] NET: Registered protocol family 31 [ 2.208369] Bluetooth: HCI device and connection manager initialized [ 2.208375] Bluetooth: HCI socket layer initialized [ 2.208378] Bluetooth...

...ed with error -2 [ 1.825704] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-3168-24.ucode failed with error -2 [ 1.825713] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-3168-23.ucode failed with error -2 [ 1.828500] iwlwifi 0000:02:00.0: loaded firmware version 22.361476.0 op_mode iwlmvm [ 1.828922] MXM: GUID detected in BIOS [ 1.828948] ACPI Warning: \_SB.PCI0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20170531/nsarguments-95) [ 1.828985] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI re...

This may not be the proper place to raise this question but I've had little luck elsewhere. After trying again, unsuccessfully this time, to install the proprietary NVIDIA driver, I've decided to focus my efforts on the open source Nouveau driver. I've seen video drivers blamed for varying degrees of "freeze on resume" but I'm not certain that's what I'm up

Hello, I am encountering a 30 second hang during boot, in the Xorg process just before the display manager comes up. I have bisected the problem to the following commit: commit 2b700825e7a7702fb862edba1262c98040dc1bf6 Author: Ben Skeggs <bskeggs at redhat.com> Date: Thu Aug 20 14:54:22 2015 +1000 drm/nouveau/mc: move device irq handling to platform-specific code The hang only

...eless WiFi driver for Linux [ 2.912660] Copyright(c) 2003- 2015 Intel Corporation [ 2.912835] iwlwifi 0000:03:00.0: can't disable ASPM; OS doesn't have ASPM control [ 2.915977] EXT4-fs (sda4): recovery complete [ 2.917191] iwlwifi 0000:03:00.0: loaded firmware version 18.168.6.1 op_mode iwldvm [ 2.917964] EXT4-fs (sda4): mounted filesystem with writeback data mode. Opts: errors=remount-ro,data=writeback [ 2.924043] ACPI: Video Device [VID] (multi-head: yes rom: no post: no) [ 2.924233] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/inp...

Hello, following up on myself, it was suggested on IRC that I better attach a dmesg output. Here's the output of a clean boot & echo 0f > /sys/.../pstate cycle. I can't spot a message that relates to the reclock action, and there's only one weird "nouveau 0000:04:00.0: clk: base: 7 MHz, boost: 7 MHz" message. On the other hand: # cat