[qubes-users] Qubes does not recover from crashed X11 (related to shmoverride and GUID)
Hello, sometimes, Intel driver makes my X11 crash (see X11-crash.log). It happens usually when I rotate the screen, but also sometimes without any apparent reason. I can usually replicate in a minute by rotating the screen like crazy. Note that this situation does not happen when I log out or kill the X server. What's worse, Qubes OS does not recover properly. It displays login prompt, but when I log in, all previously opened windows just flash and the GUID crashes. In the debug output, it complains about something related to SHM, see guid.disp7824.log. Even newly started VM don't have a working GUID. Some debugging with strace has accidentally* pointed me to /var/run/qubes/shm.id.0 file. When I rename the file, the GUID seems to be able to start it again. The shm.id.0 fle is recreated with a different number and it works again. I have found that the file is related to shmoverride documented at https://github.com/QubesOS/qubes-gui-daemon/tree/master/shmoverride . I however don't have much further idea about that. Well, it is some X11 shared memory and it has some identifier. When the X11 crashes, maybe it gets corrupted or maybe just the old file is not removed. I don't think there is a corruption of the SHM, as some similar situation happened on OOM kill. So maybe it is just about some final cleaning missing there. Do you have some further idea? Regards, Vít Šesták 'v6ak' *) Well, I hit a kind of antiheisenbug. GUID does not work when I run it with strace (even before the X11 crash), because strace breaks SUID for obvious reason. As a result, it will fail when trying to access /var/run/qubes/shm.id.0. Nevertheless, this file seems to be relevant, although the discovery was rather random. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/d649df91-4e6c-4660-a84c-e439412b6eb6%40googlegroups.com. Icon size: 128x128 ErrorHandler: BadValue (integer parameter out of range for operation) Major opcode: 130 (MIT-SHM) Minor opcode: 3 (X_ShmPutImage) Value:0x1e4 Failed serial number: 110 Current serial number: 111 [ 47101.381] (EE) Backtrace: [ 47101.389] (EE) 0: /usr/bin/X (OsLookupColor+0x139) [0x59ea19] [ 47101.390] (EE) 1: /lib64/libpthread.so.0 (funlockfile+0x50) [0x7ef51523961f] [ 47101.391] (EE) 2: /usr/lib64/xorg/modules/drivers/intel_drv.so (_init+0xc7e7) [0x7ef510c656c7] [ 47101.391] (EE) 3: /usr/lib64/xorg/modules/drivers/intel_drv.so (_init+0xce93) [0x7ef510c66463] [ 47101.391] (EE) 4: /usr/lib64/xorg/modules/drivers/intel_drv.so (_init+0xd172) [0x7ef510c669b2] [ 47101.392] (EE) 5: /usr/lib64/xorg/modules/drivers/intel_drv.so (_init+0xe5cf) [0x7ef510c692df] [ 47101.392] (EE) 6: /usr/lib64/xorg/modules/drivers/intel_drv.so (_init+0x13e6e) [0x7ef510c743be] [ 47101.392] (EE) 7: /usr/lib64/xorg/modules/drivers/intel_drv.so (_init+0x6b8a4) [0x7ef510d23674] [ 47101.393] (EE) 8: /usr/lib64/xorg/modules/drivers/intel_drv.so (_init+0x6c0ec) [0x7ef510d246cc] [ 47101.393] (EE) 9: /usr/lib64/xorg/modules/drivers/intel_drv.so (_init+0x6e16a) [0x7ef510d2811a] [ 47101.394] (EE) 10: /usr/lib64/xorg/modules/drivers/intel_drv.so (_init+0x2cce4) [0x7ef510ca5844] [ 47101.394] (EE) 11: /usr/lib64/xorg/modules/drivers/intel_drv.so (_init+0x61749) [0x7ef510d0f489] [ 47101.394] (EE) 12: /usr/lib64/xorg/modules/drivers/intel_drv.so (_init+0x433ae) [0x7ef510cd2e7e] [ 47101.395] (EE) 13: /usr/lib64/xorg/modules/drivers/intel_drv.so (_init+0x446d6) [0x7ef510cd5316] [ 47101.395] (EE) 14: /usr/lib64/xorg/modules/drivers/intel_drv.so (_init+0x6362d) [0x7ef510d1336d] [ 47101.395] (EE) 15: /usr/bin/X (BlockHandler+0x4e) [0x43ba3e] [ 47101.396] (EE) 16: /usr/bin/X (WaitForSomething+0x141) [0x598441] [ 47101.396] (EE) 17: /usr/bin/X (SendErrorToClient+0x13a) [0x436eaa] [ 47101.396] (EE) 18: /usr/bin/X (InitFonts+0x428) [0x43b0b8] [ 47101.399] (EE) 19: /lib64/libc.so.6 (__libc_start_main+0xf1) [0x7ef514e82431] [ 47101.399] (EE) 20: /usr/bin/X (_start+0x2a) [0x424d5a] [ 47101.399] (EE) [ 47101.399] (EE) Segmentation fault at address 0x8 [ 47101.399] (EE) Fatal server error: [ 47101.399] (EE) Caught signal 11 (Segmentation fault). Server aborting [ 47101.399] (EE) [ 47101.399] (EE) Please consult the Fedora Project support at http://wiki.x.org for help. [ 47101.399] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 47101.399] (EE) [ 47101.399] (II) AIGLX: Suspending AIGLX clients for VT switch [ 47101.463] (EE) Server terminated with error (1). Closing log file.
[qubes-users] Cannot Install on Partion
Hello, I have a iMac (27-inch, Late 2013) I have 1TB and have partioned it 4 ways. 250GB for Windows, Mac, PureOS, and Qubes. *I want to install Qubes on a 250GB partion.* *I am not sure what to do on the manual partioning section of the install. Can anyone tell me how to please? * appreciate it -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/a2731a8f-fdb6-40e4-b92f-d4068f2a6c46%40googlegroups.com.
Re: [qubes-users] Emergency shell on boot; qubes_dom0-pool00_tmeta: read failed: Input/output error
On Tuesday, August 20, 2019 at 6:41:36 AM UTC-4, Chris Laprise wrote: > > On 8/19/19 7:08 PM, Dave C wrote: > > Following this thread: > https://groups.google.com/forum/m/#!searchin/qubes-users/Lvconvert/qubes-users/bPxKHOfZ3Mg > > > > > ... I edited my locking mode (from 4 to 1) in /etc/lvm/lvm.conf, then > retried the 'lvm lvconvert --repair ...' > > > > That command has logged one error so far, "print_req_error: critical > medium error, dev nvme1n1, sector [number]" > > Since that one error, it hasn't shown anything. Its been running at > least ½ hour. I'm not sure if its still at work or has failed but hasn't > exited. > > Hi Dave, > > Did the repair operation finish? > > The "critical medium error" indicates a basic hardware access issue, > such as a bad hardware sector or block. Best to run a command like > 'smartctl -H ' to check drive health status. You could also run > a thorough test with 'smartctl -t long '. > > -- > > Chris Laprise, tas...@posteo.net > https://github.com/tasket > https://twitter.com/ttaskett > PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 > I was not able to get anything helpful from `smartctl`. But I ran the diagnostics built into my bios on the disk, and that showed read errors. I'm pretty confident the disk has hardware problems. I was able to run `ddrescue` on the disk, so now I am working with a copy of the partition, on a good drive. Unfortunately I still cannot activate the volumes. But I do get different errors: $ sudo lvconvert --repair qubes_dom0/pool00 WARNING: Not using lvmetad because of repair. WARNING: Disabling lvmetad cache for repair command. bad checksum in superblock, wanted 823063976 Repair of thin metadata volume of thin pool qubes_dom0/pool00 failed ( status:1). Manual repair required! I've been searching the web for a next step, but haven't found it. I'm not sure what "manual repair" would entail or whether it is possible at this point. `ddrescue` indicated it was able to rescue 99.99% of the corrupt partition. So I remain hopeful that I can still extract some of the data, but at this point I still cannot activate any volumes in qubes_dom0/pool00. I'm open to any suggestions! -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/86efd8aa-22b6-423e-af23-6672146c84eb%40googlegroups.com.
[qubes-users] Re: Ethernet problem after install 4.0.1 - qvm-start "sys-firewall' failed "unable to reset pci device" "no FLR, Pm reset or bus reset available"
Thanks unman, you are a scholar and a gentleman.. that worked a treat. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/6cb91a51-efac-4b59-9c4f-8ad6a9d0bfc6%40googlegroups.com.
Re: [qubes-users] Ethernet problem after install 4.0.1 - qvm-start "sys-firewall' failed "unable to reset pci device" "no FLR, Pm reset or bus reset available"
On Wed, Aug 21, 2019 at 02:03:33AM -0700, Bush Al wrote: > Hi all, I am new to Qubes, and trying to install it on a new Intel 9600K > with intel 219-V ethernet. Just after install i got the sys-firewall > message above which seems weird as there should be no pci device in > sys-firewall. > > The boot.log says failed to start sys-net, sys_firewall and sys_whonix > unable to reset pci device :00;1f.6 which is my ethernet card > > systemctl status qubes...@sys.net.service shows the unable to reset message > and so does sys_firewall. > the libvirt/libxl/libxl-driver.log has messages about unable to read > console tty which doesnt seem related and > > libxl: libxl_pci.c:1176:libxl__device_pci_reset: The kernal doesn't support > reset from sysfs for PCI device :00:14.0 > libxl: libxl_pci.c:1176:libxl_linux.c:155:libxl_loopdev_cleanup unable to > release device /dev/loop0: No such device or address > > I have no idea where to go from here, though its obviously an issue with > the network. > > Any ideas gratefully received. > > Thanks > Al > Hi Al Welcome to Qubes. The problem is that your sys-net is unable to start because of the ethernet card. (You see two messages because when sys-firewall tries to start it tries to start its netvm , and reports *that* failure too.) It should be quite easy to fix. Open Qube Manager (under Menu -System Tools), Right-click on sys-net, and open Qube Settings. Click Devices Tab, and hit the "Configure strict reset" button at the bottom of the pane. Select the NIC in the window that opens, click OK. Click OK. Try to start sys-net. unman -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20190821110556.GA13237%40thirdeyesecurity.org.
[qubes-users] Ethernet problem after install 4.0.1 - qvm-start "sys-firewall' failed "unable to reset pci device" "no FLR, Pm reset or bus reset available"
Hi all, I am new to Qubes, and trying to install it on a new Intel 9600K with intel 219-V ethernet. Just after install i got the sys-firewall message above which seems weird as there should be no pci device in sys-firewall. The boot.log says failed to start sys-net, sys_firewall and sys_whonix unable to reset pci device :00;1f.6 which is my ethernet card systemctl status qubes...@sys.net.service shows the unable to reset message and so does sys_firewall. the libvirt/libxl/libxl-driver.log has messages about unable to read console tty which doesnt seem related and libxl: libxl_pci.c:1176:libxl__device_pci_reset: The kernal doesn't support reset from sysfs for PCI device :00:14.0 libxl: libxl_pci.c:1176:libxl_linux.c:155:libxl_loopdev_cleanup unable to release device /dev/loop0: No such device or address I have no idea where to go from here, though its obviously an issue with the network. Any ideas gratefully received. Thanks Al -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/b0a5acde-bdab-4239-ac87-81e3dd0a3120%40googlegroups.com.
