Kernel Panic on sys-net

[cmagi...@gmail.com]

Hey all,

Hope I'm posting this correctly.
I seem to be getting an error when my sys-net comes up, which makes it more difficult to update qubes, (assuming that would fix it).

I attempted to troubleshooting the issue by searching this group and found:
https://groups.google.com/forum/#!searchin/qubes-users/sys-net$20kernel$20panic|sort:relevance/qubes-users/YrB6xJH1DJM/L2v7hvSyDQAJ

However, I wasn't able to determine a solution from it.

It appears I'm unable to upload a file here.
Used pastebin for my log.

http://pastebin.com/0n7Ad6tp

Thanks for your time.

Kind Regards,
Chris

[Chris Laprise]

Hi,

Could you provide background on your system...

Does your system have Vt-d capability? Check this with 'xl info' in dmesg.

Is your NIC assigned to sys-net? Check this in VM Settings / Devices.

What are the brand/model of NIC(s)?

Can you try to manually start sys-net from Qubes Manager or the CLI?


Chris

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

> [ 1.263296] blk_update_request: I/O error, dev xvda, sector 0
> [ 1.263301] Buffer I/O error on dev xvda, logical block 0, async page
> read
> [ 1.263326] blk_update_request: I/O error, dev xvda, sector 0
> [ 1.263330] Buffer I/O error on dev xvda, logical block 0, async page
> read
> [ 1.263349] blk_update_request: I/O error, dev xvda, sector 0

This suggests some problems with storage. Do you have similar messages
in dom0? Maybe your hard drive is failing?

- --
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?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJYIPTiAAoJENuP0xzK19csg9wH/375dTx+77OHvr0mpYVhTQLK
3y8+3oZwtZomXLDBauTYb5AC0ezU4tLzFqM6Bzx+pa9m7ZQf/OeHyVuWEx1rGi3I
7OFncZGswC/l7/42iabI5pOacsHBoSsjGsAeT1fhK8vY2DyBdEfwoBmlqAUlTHjy
A4cvQIJ2Fxb20OjTcgYYbVkM7PgSaY79REHrUsH4dV/iPZ1AdRlgibX7IMa7rO9L
bPxPnAn57DM/wr5hoIFBsUQhCTZn31f2OkGFN/btFY7v0tnYpwlqo/KoNA+VhR6e
IfNJdgsnm4ukqAnw+knQeuYhRYaJ8UGG7TUYicPe/qHmLUYgdIkirm0vHwmbfYM=
=F8Y3
-----END PGP SIGNATURE-----

[cmagi...@gmail.com]

Thank you both for your assistance!
I'm lucky to receive help from Marek. I've been a Qubes user for awhile and seen many of your posts when I have issues.

>Does your system have Vt-d capability? Check this with 'xl info' in dmesg.

Yes. Intel I-7 3770k & it's enabled.

>Is your NIC assigned to sys-net? Check this in VM Settings / Devices.

Yes.

>What are the brand/model of NIC(s)?

Currently I have 3 NICs connected to it.
1 Qualcomm, 1 Realtek, and 1 Intel (mb)

>Can you try to manually start sys-net from Qubes Manager or the CLI?

I'm unable to start it from both the CLI and Manager.

>This suggests some problems with storage. Do you have similar messages
in dom0? Maybe your hard drive is failing?

I feel this is the most realistic cause. My SSD is pretty worn and old.
I took a peek in /var/log to find a log that matches or is similar to one I provided.
$ grep error boot.log
nothing.

$ dmesg | grep error
Could not initialized VPMU for cpu 0, error -95

Might there be another file that could provide some insight?

One script I did create to assist with moving my VMs away from the main SSD to external HDD is this.

https://github.com/CMagistrado/Nexus/blob/master/Qubexus/fragment
sudo mv /var/lib/qubes/appvms/$1 /mnt/VMs
ln -s /mnt/VMs/$1 /var/lib/qubes/appvms/

Might this have anything to do with the sys-net VM? I didn't move sys-net to external though. =/