Debian – the difference between all of these Debian version numbers

debianversion

In attempting to find the version of Debian I am running, I have run several commands; the confusing thing is, nearly all of these commands return different results.

For instance, in /proc/version I find:

Linux version 3.2.0-4-686-pae (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.63-2+deb7u2

I can tell 3.2.0-4-686-pae is the kernel version, this is clear to me. But the rest of the output seems to give two different Debian version numbers of 4.6.3-14 and 3.2.63-2+deb7u2 (the latter also being output from uname).

Moreover, when I look in /etc/debian_version, it tells me I'm using version 7.7.

Why am I getting so many different Debian versions listed in these places, and what is the difference between the numbers?

Best Answer

The GCC version is the version of the GNU C Compiler used to build the kernel.

According to Debian's documentation, the 3.2.0-4-686-pae is the kernel version as described upstreamversion[-abiname][-featureset]-flavour. So the upstream version is 3.2 (with .0 added in wheezy). The final 3.2.63-2+deb7u2 most likely is the package version.

I suspect the first version (3.2.0) is for ABI compatibility, and the package name reflects the actual versioning in the pacakge database.

Related Solutions

Debian – How to fix mpt2sas “port enable: FAILED with timeout (timeout=300s)”

Does it work with the PUIS disabled?

The fact that you get a port enable failed may indicate an HBA problem but the fact that you got the target resets on the drives (log_info 0x31111000) shows you got the port enabled in some cases but the drives failed to respond. This may be due to the PUIS condition, they simply did not initialize.

Normally when you have disks behind a SAS expander the expander will take on the task to wake them up. You can try to get the status of the expander with the sg_ses utility to see what it thinks.

The errors you are showing in SMP may indicate a cable problem somewhere. You do not have errors on the disks but you do have them on the cable from the expander to the initiator. You should check that option too.

The log_info 0x31111000 decodes into:

./lsi_decode_loginfo.py 0x31111000
Value       31111000h
Type:       30000000h   SAS 
Origin:     01000000h   PL 
Code:       00110000h   PL_LOGINFO_CODE_RESET See Sub-Codes below (PL_LOGINFO_SUB_CODE)
Sub Code:   00001000h   PL_LOGINFO_SUB_CODE_DSCVRY_SATA_INIT_TIMEOUT

Debian won’t shut down completely

I have the same issue, I have no idea what is, to temporarily resolve this I created an alias in .bashrc.

alias poweroff='su -c "'"systemctl poweroff"'"'

alias restart='su -c "'"systemctl reboot"'"'

Best Answer

Related Solutions

Debian – How to fix mpt2sas “port enable: FAILED with timeout (timeout=300s)”

Debian won’t shut down completely

Related Question