Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upSystem crash triggered by Logitech unifying receiver - R3.1rc2 #1689
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Jan 25, 2016
Member
Really strange... Do you have anything interesting in
/var/log/xen/console/guest-sys-net.log? (you can access the log from
Qubes Manager)
Also it may be good idea to post this to qubes-users mailing list.
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
|
Really strange... Do you have anything interesting in Also it may be good idea to post this to qubes-users mailing list. Best Regards, |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
tasket
Jan 25, 2016
That would be the log for the network vm? I'm not seeing anything bad, though I'm not accustomed to looking at xen logs. Also don't know what that vm has to do with USB mice.
I already mentioned this issue as a part of this thread:
https://groups.google.com/d/msg/qubes-users/pqH_f-kkUYo/S1kS6vWHAQAJ
I can start a dedicated thread for this, too.
tasket
commented
Jan 25, 2016
|
That would be the log for the network vm? I'm not seeing anything bad, though I'm not accustomed to looking at xen logs. Also don't know what that vm has to do with USB mice. I already mentioned this issue as a part of this thread: I can start a dedicated thread for this, too. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Jan 25, 2016
Member
On Mon, Jan 25, 2016 at 01:25:29PM -0800, ttasket wrote:
That would be the log for the network vm? I'm not seeing anything bad, though I'm not accustomed to looking at xen logs. Also don't know what that vm has to do with USB mice.
Err, I meant sys-usb of course ;)
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
|
On Mon, Jan 25, 2016 at 01:25:29PM -0800, ttasket wrote:
Err, I meant Best Regards, |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
tasket
commented
Jan 25, 2016
|
I don't have sys-usb. This was an experimental upgrade from 3.0. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Feb 4, 2016
Member
What kernel version in dom0 do you have?
I've hit the same issue on 4.2.8-8. No idea what is happening there, yet.
|
What kernel version in dom0 do you have? |
marmarek
added
bug
C: kernel
P: minor
labels
Feb 4, 2016
marmarek
added this to the Release 3.1 milestone
Feb 4, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
aberja
Feb 4, 2016
I experienced the same issue of my system (v3.1.11) crashing throughout the day on kernel 4.1.13-8.
The crashing stopped once I unplugged the Logitech unifying receiver.
aberja
commented
Feb 4, 2016
|
I experienced the same issue of my system (v3.1.11) crashing throughout the day on kernel 4.1.13-8. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
tasket
Feb 4, 2016
tasket
commented
Feb 4, 2016
|
I'm using kernel 4.1.13-8. Do you think its worth trying to reproduce
this with plain fedora 20?
|
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Feb 5, 2016
Member
Most likely it will work there.
Do you have any access to serial console there (docking station or
something)? There is most likely some panic message but it isn't written
anywhere before reboot...
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
|
Most likely it will work there. Best Regards, |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
nrgaway
Feb 5, 2016
I found I had this issue often when the Unified Receiver was plugged into a USB3 port. I have moved it to a USB2 hub which is connected to the USB3.0 and do not have as many panics; maybe 1 every week or so.
nrgaway
commented
Feb 5, 2016
|
I found I had this issue often when the Unified Receiver was plugged into a USB3 port. I have moved it to a USB2 hub which is connected to the USB3.0 and do not have as many panics; maybe 1 every week or so. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
aberja
Feb 5, 2016
My Unified Receiver was plugged into a USB2 port when it was causing the crashes.
aberja
commented
Feb 5, 2016
|
My Unified Receiver was plugged into a USB2 port when it was causing the crashes. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Feb 5, 2016
Member
Same here - crash when using it in USB2 port.
Anyone with a way to get serial console output?
FWIW for me it happens on ThinPad T61, without IOMMU support (but that
USB controller is in dom0 anyway).
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
|
Same here - crash when using it in USB2 port. Best Regards, |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
tasket
Feb 6, 2016
On 02/05/2016 08:27 AM, Marek Marczykowski-Górecki wrote:
Same here - crash when using it in USB2 port.
Anyone with a way to get serial console output?
FWIW for me it happens on ThinPad T61, without IOMMU support (but that
USB controller is in dom0 anyway).Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?—
Reply to this email directly or view it on GitHub
#1689 (comment).
FWIW, my system has full IOMMU support. No sys-USB has been created and
not sure if that makes a difference.
I'll ask a friend if I can use his docking station to get a serial console.
tasket
commented
Feb 6, 2016
|
On 02/05/2016 08:27 AM, Marek Marczykowski-Górecki wrote:
FWIW, my system has full IOMMU support. No sys-USB has been created and I'll ask a friend if I can use his docking station to get a serial console. |
marmarek
modified the milestones:
Release 3.1,
Release 3.1 updates
Feb 8, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Rudd-O
Mar 15, 2016
I have the same issue. The crash happens irrespective of whether sys-usb was powered on or not. Just the act of connecting the receiver, or a USB hub that has it connected, causes the crash. Sporadically. Oh, and by the way, there's no way to get to a serial console in my case, but even if there were, the machine just cold-reboots.
Rudd-O
commented
Mar 15, 2016
|
I have the same issue. The crash happens irrespective of whether sys-usb was powered on or not. Just the act of connecting the receiver, or a USB hub that has it connected, causes the crash. Sporadically. Oh, and by the way, there's no way to get to a serial console in my case, but even if there were, the machine just cold-reboots. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
memfail
Jul 9, 2016
Hi,
same here on r3.1 without a sys-usb and now on r3.2 RC1 with a sys-usb VM.
After the Crash of the sys usb VM this Kernel Panic appears in the guest-sys-usb.log:
`Fedora 23 (Workstation Edition)
Kernel 4.4.12-9.pvops.qubes.x86_64 on an x86_64 (hvc0)
sys-usb login: [ 9.192974] fuse init (API version 7.23)
[ 10.788891] sda: sda1
[ 10.794206] sd 1:0:0:0: [sda] Attached SCSI disk
[ 177.437528] usb 2-1.4.2: USB disconnect, device number 5
[ 179.662204] usb 2-1.4.2: new full-speed USB device number 7 using ehci-pci
[ 179.751727] usb 2-1.4.2: New USB device found, idVendor=046d, idProduct=c52b
[ 179.751760] usb 2-1.4.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 179.751775] usb 2-1.4.2: Product: USB Receiver
[ 179.751786] usb 2-1.4.2: Manufacturer: Logitech
[ 179.763306] logitech-djreceiver 0003:046D:C52B.0008: hiddev0,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:00.0-1.4.2/input2
[ 179.872912] BUG: unable to handle kernel paging request at ffff88000a918a9c
[ 179.872955] IP: [<ffffffff81600ca8>] hid_input_field+0xc8/0x250
[ 179.872991] PGD 1c0a067 PUD 1c0b067 PMD 12bc3067 PTE 0
[ 179.873013] Oops: 0000 [#1] SMP
[ 179.873013] Modules linked in: fuse xt_nat xen_netback xt_REDIRECT nf_nat_redirect ip6table_filter ip6_tables xt_conntrack ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack joydev input_leds hid_logitech_hidpp hid_logitech_dj uas usb_storage uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core v4l2_common videodev media ehci_pci ehci_hcd intel_rapl iosf_mbi x86_pkg_temp_thermal coretemp crct10dif_pclmul crc32_pclmul crc32c_intel pcspkr xen_pcifront dummy_hcd udc_core xen_blkback xenfs xen_privcmd u2mfn(O) xen_blkfront
[ 179.873013] CPU: 0 PID: 1256 Comm: systemd-udevd Tainted: G O 4.4.12-9.pvops.qubes.x86_64 #1
[ 179.873013] task: ffff880005a0ba00 ti: ffff88000f6e0000 task.ti: ffff88000f6e0000
[ 179.873013] RIP: e030:[<ffffffff81600ca8>] [<ffffffff81600ca8>] hid_input_field+0xc8/0x250
[ 179.873013] RSP: e02b:ffff880012803d38 EFLAGS: 00010002
[ 179.873013] RAX: ffff88000a918a9c RBX: ffff88000ab882a4 RCX: 0000000000000001
[ 179.873013] RDX: 0000000000000000 RSI: ffff88000a917f70 RDI: ffff88000f4fc000
[ 179.873013] RBP: ffff880012803da8 R08: ffff88001281a0e0 R09: ffff880010801c00
[ 179.873013] R10: ffff88000ab882a0 R11: ffff88000f740400 R12: 0000000000000000
[ 179.873013] R13: 0000000000000008 R14: ffff88000a917f00 R15: 0000000000000008
[ 179.873013] FS: 00007fed628468c0(0000) GS:ffff880012800000(0000) knlGS:0000000000000000
[ 179.873013] CS: e033 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 179.873013] CR2: ffff88000a918a9c CR3: 000000000ab8a000 CR4: 0000000000042660
[ 179.873013] Stack:
[ 179.873013] 0000000000000018 0000000000000005 0000000000000018 00000001816086fe
[ 179.873013] ffff88000ab882a0 ffff880000046181 ffff88000ab882b8 00000000000000ff
[ 179.873013] ffff88000f4fc000 ffff88000f4fc000 ffff88000ff45000 ffff880000046181
[ 179.873013] Call Trace:
[ 179.873013] <IRQ>
[ 179.873013] [<ffffffff81600f32>] hid_report_raw_event+0x102/0x1b0
[ 179.873013] [<ffffffff816010e6>] hid_input_report+0x106/0x170
[ 179.873013] [<ffffffff8160bffc>] hid_irq_in+0xbc/0x220
[ 179.873013] [<ffffffff8157cae5>] __usb_hcd_giveback_urb+0x85/0x130
[ 179.873013] [<ffffffff8157d4d0>] usb_giveback_urb_bh+0xa0/0x100
[ 179.873013] [<ffffffff810a36c8>] tasklet_hi_action+0xf8/0x110
[ 179.873013] [<ffffffff810a3de6>] __do_softirq+0x106/0x2d0
[ 179.873013] [<ffffffff810a41b2>] irq_exit+0x102/0x110
[ 179.873013] [<ffffffff8147dce5>] xen_evtchn_do_upcall+0x35/0x40
[ 179.873013] [<ffffffff8175df3e>] xen_do_hypervisor_callback+0x1e/0x40
[ 179.873013] <EOI>
[ 179.873013] Code: 89 03 41 8b 56 1c 40 0f 9e c6 44 39 e0 0f 9d c1 40 84 ce 74 1e f6 c2 02 75 19 44 29 e0 49 8b 76 10 48 98 48 8d 04 80 48 8d 04 86 <81> 38 01 00 07 00 74 42 48 83 c3 04 45 01 ef 48 3b 5d c0 74 4d
[ 179.873013] RIP [<ffffffff81600ca8>] hid_input_field+0xc8/0x250
[ 179.873013] RSP <ffff880012803d38>
[ 179.873013] CR2: ffff88000a918a9c
[ 179.873013] ---[ end trace 077edd87c691cf84 ]---
[ 179.873013] Kernel panic - not syncing: Fatal exception in interrupt
[ 179.873013] Kernel Offset: disabled
memfail
commented
Jul 9, 2016
|
Hi, same here on r3.1 without a sys-usb and now on r3.2 RC1 with a sys-usb VM. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Rudd-O
Jul 9, 2016
Does only your VM crash, or does it cause a general system reboot as well?
I tried with and without sys-usb, and in both cases it caused my machine
to reboot.
Rudd-O
commented
Jul 9, 2016
|
Does only your VM crash, or does it cause a general system reboot as well? I tried with and without sys-usb, and in both cases it caused my machine |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Jul 9, 2016
Member
It looks like almost certainly kernel driver bug, should crash only VM to which that USB device is connected (which may be dom0 if no sys-usb is used).
|
It looks like almost certainly kernel driver bug, should crash only VM to which that USB device is connected (which may be dom0 if no sys-usb is used). |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Rudd-O
Jul 9, 2016
On 07/09/2016 10:48 PM, Marek Marczykowski-Górecki wrote:
It looks like almost certainly kernel driver bug, should crash only VM
to which that USB device is connected (which may be dom0 if no sys-usb
is used).How can kernel driver in VM crash whole machine?
Rudd-O
http://rudd-o.com/
Rudd-O
commented
Jul 9, 2016
|
On 07/09/2016 10:48 PM, Marek Marczykowski-Górecki wrote:
|
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Jul 10, 2016
Member
On Sat, Jul 09, 2016 at 04:57:27PM -0700, Rudd-O wrote:
How can kernel driver in VM crash whole machine?
Are you sure that the USB controller was really assigned to that VM at
that time?
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
|
On Sat, Jul 09, 2016 at 04:57:27PM -0700, Rudd-O wrote:
Are you sure that the USB controller was really assigned to that VM at Best Regards, |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Rudd-O
Jul 10, 2016
On 07/10/2016 12:14 AM, Marek Marczykowski-Górecki wrote:
On Sat, Jul 09, 2016 at 04:57:27PM -0700, Rudd-O wrote:
How can kernel driver in VM crash whole machine?
Are you sure that the USB controller was really assigned to that VM at
that time?
100% certain.
Rudd-O
http://rudd-o.com/
Rudd-O
commented
Jul 10, 2016
|
On 07/10/2016 12:14 AM, Marek Marczykowski-Górecki wrote:
100% certain. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
memfail
commented
Jul 10, 2016
|
In my case it only killed the sys-usb VM. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Jul 11, 2016
Member
This patch looks to be related: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=50220dead1650609206efe91f0cc116132d59b3f
Given the traceback above, I'd guess it's exactly fix for this issue. Will upload kernel with this patch applied in a moment.
|
This patch looks to be related: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=50220dead1650609206efe91f0cc116132d59b3f Given the traceback above, I'd guess it's exactly fix for this issue. Will upload kernel with this patch applied in a moment. |
marmarek
self-assigned this
Jul 11, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Jul 11, 2016
Member
Kernel 4.4.14-9 uploaded to unstable repo of R3.2. Both for dom0 (kernel package) and VM (kernel-qubes-vm package). Please test and report back whether it helps.
|
Kernel 4.4.14-9 uploaded to unstable repo of R3.2. Both for dom0 (kernel package) and VM (kernel-qubes-vm package). Please test and report back whether it helps. |
added a commit
to marmarek/qubes-linux-kernel
that referenced
this issue
Jul 13, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Jul 13, 2016
Member
Automated announcement from builder-github
The package kernel-devel-4.4.14-10.pvops.qubes has been pushed to the r3.2 testing repository for the Fedora fc23 template.
To test this update, please install it with the following command:
sudo yum update --enablerepo=qubes-vm-r3.2-current-testing
|
Automated announcement from builder-github The package |
marmarek
added
the
r3.2-fc23-cur-test
label
Jul 13, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Jul 13, 2016
Member
Automated announcement from builder-github
The package kernel-devel-4.4.14-10.pvops.qubes has been pushed to the r3.2 testing repository for the Fedora fc24 template.
To test this update, please install it with the following command:
sudo yum update --enablerepo=qubes-vm-r3.2-current-testing
|
Automated announcement from builder-github The package |
marmarek
added
the
r3.2-fc24-cur-test
label
Jul 13, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Jul 13, 2016
Member
Automated announcement from builder-github
The package kernel-4.4.14-10.pvops.qubes has been pushed to the r3.2 testing repository for dom0.
To test this update, please install it with the following command:
sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing
|
Automated announcement from builder-github The package |
marmarek
added
the
r3.2-dom0-cur-test
label
Jul 13, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
tasket
Jul 14, 2016
Almost a day of using logitech mouse with 4.4.14-10 and no crashes yet.
However, there is now a 'bouncing' problem with the mouse buttons. A single click often turns into a double click, and a double sometimes into a triple. So using it like this is a nuisance.
tasket
commented
Jul 14, 2016
|
Almost a day of using logitech mouse with 4.4.14-10 and no crashes yet. However, there is now a 'bouncing' problem with the mouse buttons. A single click often turns into a double click, and a double sometimes into a triple. So using it like this is a nuisance. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
tasket
Jul 14, 2016
By "often" I mean perhaps 1 in 30 clicks. Not sure if the mouse developed a mechanical problem, so will test on another system.
tasket
commented
Jul 14, 2016
|
By "often" I mean perhaps 1 in 30 clicks. Not sure if the mouse developed a mechanical problem, so will test on another system. |
added a commit
to marmarek/qubes-linux-kernel
that referenced
this issue
Jul 20, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Jul 20, 2016
Member
Automated announcement from builder-github
The package kernel-devel-4.1.28-10.pvops.qubes has been pushed to the r3.1 testing repository for the Fedora fc21 template.
To test this update, please install it with the following command:
sudo yum update --enablerepo=qubes-vm-r3.1-current-testing
|
Automated announcement from builder-github The package |
marmarek
added
the
r3.1-fc21-cur-test
label
Jul 20, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Jul 20, 2016
Member
Automated announcement from builder-github
The package kernel-devel-4.1.28-10.pvops.qubes has been pushed to the r3.1 testing repository for the Fedora fc22 template.
To test this update, please install it with the following command:
sudo yum update --enablerepo=qubes-vm-r3.1-current-testing
|
Automated announcement from builder-github The package |
marmarek
added
the
r3.1-fc22-cur-test
label
Jul 20, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Jul 20, 2016
Member
Automated announcement from builder-github
The package kernel-devel-4.1.28-10.pvops.qubes has been pushed to the r3.1 testing repository for the Fedora fc23 template.
To test this update, please install it with the following command:
sudo yum update --enablerepo=qubes-vm-r3.1-current-testing
|
Automated announcement from builder-github The package |
marmarek
added
the
r3.1-fc23-cur-test
label
Jul 20, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Jul 20, 2016
Member
Automated announcement from builder-github
The package kernel-4.1.28-10.pvops.qubes has been pushed to the r3.1 testing repository for dom0.
To test this update, please install it with the following command:
sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing
|
Automated announcement from builder-github The package |
marmarek
added
the
r3.1-dom0-cur-test
label
Jul 20, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
memfail
commented
Jul 22, 2016
|
Seems to work (without multiple clicks). Thanks. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
tasket
Jul 22, 2016
My mouse button must have suffered from lack of use :) or else I have somehow gotten used to it. Clicking seems correct now.
tasket
commented
Jul 22, 2016
|
My mouse button must have suffered from lack of use :) or else I have somehow gotten used to it. Clicking seems correct now. |
marmarek
closed this
Jul 24, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Jul 28, 2016
Member
Automated announcement from builder-github
The package kernel-devel-4.4.14-11.pvops.qubes has been pushed to the r3.2 stable repository for the Fedora fc23 template.
To install this update, please use the standard update command:
sudo yum update
|
Automated announcement from builder-github The package |
marmarek
added
r3.2-fc23-stable
and removed
r3.2-fc23-cur-test
labels
Jul 28, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Jul 28, 2016
Member
Automated announcement from builder-github
The package kernel-devel-4.4.14-11.pvops.qubes has been pushed to the r3.2 stable repository for the Fedora fc24 template.
To install this update, please use the standard update command:
sudo yum update
|
Automated announcement from builder-github The package |
marmarek
added
r3.2-fc24-stable
and removed
r3.2-fc24-cur-test
labels
Jul 28, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Jul 28, 2016
Member
Automated announcement from builder-github
The package kernel-4.4.14-11.pvops.qubes has been pushed to the r3.2 stable repository for dom0.
To install this update, please use the standard update command:
sudo qubes-dom0-update
Or update dom0 via Qubes Manager.
|
Automated announcement from builder-github The package Or update dom0 via Qubes Manager. |
marmarek
added
r3.2-dom0-stable
and removed
r3.2-dom0-cur-test
labels
Jul 28, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Aug 5, 2016
Member
Automated announcement from builder-github
The package kernel-devel-4.1.24-10.pvops.qubes has been pushed to the r3.1 stable repository for the Fedora fc21 template.
To install this update, please use the standard update command:
sudo yum update
|
Automated announcement from builder-github The package |
marmarek
added
r3.1-fc21-stable
and removed
r3.1-fc21-cur-test
labels
Aug 5, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Aug 5, 2016
Member
Automated announcement from builder-github
The package kernel-devel-4.1.24-10.pvops.qubes has been pushed to the r3.1 stable repository for the Fedora fc22 template.
To install this update, please use the standard update command:
sudo yum update
|
Automated announcement from builder-github The package |
marmarek
added
r3.1-fc22-stable
and removed
r3.1-fc22-cur-test
labels
Aug 5, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Aug 5, 2016
Member
Automated announcement from builder-github
The package kernel-devel-4.1.24-10.pvops.qubes has been pushed to the r3.1 stable repository for the Fedora fc23 template.
To install this update, please use the standard update command:
sudo yum update
|
Automated announcement from builder-github The package |
marmarek
added
r3.1-fc23-stable
and removed
r3.1-fc23-cur-test
labels
Aug 5, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Aug 5, 2016
Member
Automated announcement from builder-github
The package kernel-4.1.24-10.pvops.qubes has been pushed to the r3.1 stable repository for dom0.
To install this update, please use the standard update command:
sudo qubes-dom0-update
Or update dom0 via Qubes Manager.
|
Automated announcement from builder-github The package Or update dom0 via Qubes Manager. |
marmarek
added
r3.1-dom0-stable
and removed
r3.1-dom0-cur-test
labels
Aug 5, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Rudd-O
commented
Aug 13, 2016
|
Thanks! |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Rudd-O
commented
Oct 23, 2016
|
I confirm: The Logitech device issue is no longer a problem in modern kernels. |
tasket commentedJan 25, 2016
After upgrading to R3.1rc2 my system will crash and reset if certain conditions are met.
All I have to do is first boot the machine (without the unifying receiver) and get to the desktop, then put it in sleep mode, then wake it. Then start an appvm, then plug in the logitech receiver. (I may have to repeat the last step once more: unplug receiver, start another appvm, then insert receiver.) As soon as the receiver is plugged in, the system will freeze for a few seconds and reboot. Having the logitech mouse 'wake up' after going into conservation mode also causes system reset, as if the receiver were being plugged in.
Repeatability is 100%. I tried a different Logitech mouse/receiver combo and the crash happened again. Then I switched to a non-logitech mouse/receiver combo and cannot produce the crash.
There appears to be a bug in the new Xen or dom0 kernel USB or HID code that can be triggered this way. I tried switching to kernel 3.18 or 3.19 but those would not boot.