Legacy SUSE Linux Troubleshooting and Kernel-Version Tables
This is a historical Linux/SLES reference. Its kernel tables cover releases from 2006–2014 and are not a list of current supported kernels. Use the installed distribution’s supported maintenance branch and entitlement.
1. Long-uptime crash / reboot case
The source describes SLES 11 SP1 crashes after long operation. It attributes one divide error to total_pwr, a total CPU-scheduling-time value becoming zero through a 64-to-32-bit assignment, and gives roughly 208 days, dependent on load/process count. It separately mentions a counter-related crash after 500 days, but later gives an R3-board TSC-related example of about208 days. Those timing/mechanism statements are inconsistent and were not independently established as universal raw-TSC overflow behavior.
The vendor note identifies 2.6.32.59-0.7.1 or later in its applicable maintenance branch as its correction, with these affected examples:
Source operating system
Listed affected kernel examples
Source corrected kernel
SLES 11 SP1
2.6.32.12-0.7.1
2.6.32.59-0.7.1
SLES 11 SP1
2.6.32.24-0.2.1
2.6.32.59-0.7.1
SLES 11 SP1
2.6.32.36-0.5.2
2.6.32.59-0.7.1
SLES 11 SP1
2.6.32.45-0.3.2
2.6.32.59-0.7.1
SLES 11 SP1
2.6.32.54-0.3.1
2.6.32.59-0.7.1
Confirm the exact SLES service pack and package branch before applying that historical number: the source’s own history places the2.6.32.59 build among later SP1 maintenance entries. “Later” is not permission to install an arbitrary kernel from another branch. The source’s Novell/licensing statement reflects its period; access to vendor updates depends on the actual subscription/support arrangements.
2. Archived SLES release / kernel tables
All original date/version rows follow, including continued tables and architecture-specific entries. These tables are historical reference data, not current update instructions.
SLES 10
SHIP-Jul-2006
2.6.16.21-0.8
Aug-18-2006
2.6.16.21-0.15
Sep-26-2006
2.6.16.21-0.25
Dec-21-2006
2.6.16.27-0.6
Feb-23-2007
2.6.16.27-0.9
Jun-2007
SP1 release – see table below
SLES10 SP1
SP1-Jun-2007
2.6.16.46-0.12
Jun-19-2007
2.6.16.46-0.14
Sep-04-2007
2.6.16.53-0.8
Oct-11-2007
2.6.16.53-0.16
Nov-07-2007
2.6.16.53-0.18 (s390x only)
Dec-03-2007
2.6.16.54-0.2.3
Feb-07-2008
2.6.16.54-0.2.5
May-2008
SP2 release – see table below
July-04-2008
2.6.16.54-0.2.8
Oct-01-2008
2.6.16.54-0.2.10 2.6.16.54-0.2.11 (x86_64)
Dec-02-2008
2.6.16.54-0.2.12
SLES10 SP2
SP2-May-2008
2.6.16.60-0.21
Jun-01-2008
2.6.16.60-0.23
July-18-2008
2.6.16.60-0.25
July-29-2008
2.6.16.60-0.27
Oct-01-2008
2.6.16.60-0.29 2.6.16.60-0.30 (x86_64)
Oct-20-2008
2.6.16.60-0.31
Nov-25-2008
2.6.16.60-0.33
Jan-29-2009
2.6.16.60-0.34
Feb-17-2009
2.6.16.60-0.35 (ia64 only)
Apr-03-2009
2.6.16.60-0.37_f594963d
May-20-2009
2.6.16.60-0.39.3
Aug-20-2009
2.6.16.60-0.42.4
Aug-27-2009
2.6.16.60-0.42.5
October-2009
SP3 release – see table below
Nov-10-2009
2.6.16.60-0.42.7
Dec-22-2009
2.6.16.60-0.42.8
Feb-04-2010
2.6.16.60-0.42.9
May-06-2010
2.6.16.60-0.42.10
SLES10 SP2 – LTSS
Jun-14-2011
2.6.16.60-0.42.11
Jan-24-2012
2.6.16.60-0.42.54.1
SLES10 SP3
SP3-Oct-2009
2.6.16.60-0.54.5
Nov-12-2009
2.6.16.60-0.57.1
Dec-14-2009
2.6.16.60-0.58.1
Jan-22-2010
2.6.16.60-0.59.1
Mar-29-2010
2.6.16.60-0.60.1
Apr-26-2010
2.6.16.60-0.62.1 (x86_64 only)
Jun-11-2010
2.6.16.60-0.66.1
Aug-17-2010
2.6.16.60-0.67.1
Sep-03-2010
2.6.16.60-0.68.1
Sep-22-2010
2.6.16.60-0.69.1
Dec-13-2010
2.6.16.60-0.74.7
Jan-25-2011
2.6.16.60-0.76.8
Mar-24-2011
2.6.16.60-0.77.1
April-2011
SP4 release – see table below
Jun-29-2011
2.6.16.60-0.79.1
Jul-02-2011
2.6.16.60-0.81.2
Sep-20-2011
2.6.16.60-0.83.2
SLES10 SP3 – LTSS
Dec-09-2013
2.6.16.60-0.113.1
SLES10 SP4
SP4-Apr-2011
2.6.16.60-0.85.1
May-19-2011
2.6.16.60-0.87.1
Aug-12-2011
2.6.16.60-0.89.1
Oct-28-2011
2.6.16.60-0.91.1
Jan-23-2012
2.6.16.60-0.93.1 2.6.16.60-0.95.1 (s390x)
Jun-14-2012
2.6.16.60-0.97.1
Oct-23-2012
2.6.16.60-0.99.1
Apr-12-2013
2.6.16.60-0.101.1
Jun-04-2013
2.6.16.60-0.103.1
SLES 11
SHIP-Mar-2009
2.6.27.19-5.1
Apr-16-2009
2.6.27.21-0.1.2
Jun-09-2009
2.6.27.23-0.1.1
July-23-2009
2.6.27.25-0.1.1
Aug-20-2009
2.6.27.29-0.1.1
Nov-02-2009
2.6.27.37-0.1.1
Dec-02-2009
2.6.27.39-0.3.1
Jan-14-2010
2.6.27.42-0.1.1
Mar-02-2010
2.6.27.45-0.1.1
Jun-2010
SP1 release – see table below
July-20-2010
2.6.27.48-0.1.1
Aug-09-2010
2.6.27.48-0.6.1
Sep-22-2010
2.6.27.48-0.12.1
Oct-26-2010
2.6.27.54-0.2.1
SLES11 SP1
SP1-Jun-2010
2.6.32.12-0.7.1
July-01-2010
2.6.32.13-0.4.1
Aug-02-2010
2.6.32.13-0.5.1
Sep-13-2010
2.6.32.19-0.2.1
Sep-22-2010
2.6.32.19-0.3.1
Oct-13-2010
2.6.32.23-0.3.1
Nov-10-2010
2.6.32.24-0.2.1
Jan-14-2011
2.6.32.27-0.2.2
Mar-08-2011
2.6.32.29-0.3.1
Apr-27-2011
2.6.32.36-0.5.2
July-25-2011
2.6.32.43-0.4.1
Sep-01-2011
2.6.32.45-0.3.2
Oct-07-2011
2.6.32.46-0.3.1
Dec-13-2011
2.6.32.49-0.3.1
Feb-06-2012
2.6.32.54-0.3.1
Feb-2012
SP2 release – see table below
May-14-2012
2.6.32.59-0.3.1
July-23-2012
2.6.32.59-0.7.1
SLES11 SP1 – LTSS
Jan-24-2014
2.6.32.59-0.9.1
SLES11 SP2
SP2-Feb-2012
3.0.13-0.27.1
Apr-23-2012
3.0.26-0.7.6
Jun-01-2012
3.0.31-0.9.1
Jun-25-2012
3.0.34-0.7.9
Aug-21-2012
3.0.38-0.5.1
Oct-15-2012
3.0.42-0.7.3
Dec-19-2012
3.0.51-0.7.9.1
Feb-07-2013
3.0.58-0.6.2.1
Feb-25-2013
3.0.58-0.6.6.1
May-07-2013
3.0.74-0.6.6.2
May-22-2013
3.0.74-0.6.8.1
May-31-2013
3.0.74-0.6.10.1
June-17-2013
3.0.80-0.5.1
July-05-2013
3.0.80-0.7.1
July-2013
SP3 release – see table below
Sep-20-2013
3.0.93-0.5.1
Nov-21-2013
3.0.101-0.5.1
Jan-27-2014
3.0.101-0.7.15.1
Feb-12-2014
3.0.101-0.7.17.1
SLES11 SP3
SP3-July-2013
3.0.76-0.11.1
July-11-2013
3.0.82-0.7.9
Sep-21-2013
3.0.93-0.8.2
Nov-22-2013
3.0.101-0.8.1
Feb-04-2014
3.0.101-0.15.1
Mar-27-2014
3.0.101-0.18.1
3. Slow scp transfer
The source observes30–40 MB/s on a1 Gb/s network and attributes overhead to encryption and a single scp process. It reports130 MB/s in its10 Gb/s test after selecting scp -c arcfour. These are case measurements, not throughput guarantees. The arcfour cipher is obsolete and must not be enabled as a current performance fix; use supported SSH algorithms and diagnose CPU, network, disk and protocol behavior for the actual systems. SCP is not a network-bandwidth benchmark.
4. CPU/memory visible in BIOS but not fully visible in the OS
The prerequisite in the source is that BIOS sees the expected CPU and memory. It gives two legacy causes:
A nosmp boot argument in /boot/grub/menu.lst disables SMP, limiting CPU visibility. Inspect the active boot arguments/dmesg and the appropriate bootloader configuration before correcting that argument.
A Xen dom0 kernel reports resources allocated to dom0 through cat /proc/cpuinfo and free; the hypervisor may reserve the remainder. Inspect the matching hypervisor view rather than assuming hardware is missing.
The source checks uname -a, gives the example Linux version 2.6.18-238.12.1.el5xen, and uses xm info to inspect Xen resources. That example is a separate legacy Xen environment; it must not be mistaken for the SLES kernel table. Newer Xen toolstacks may use different tools.
5. Legacy network interface not activated after installation
The source describes no interface in ordinary ifconfig output and no link light, attributing its case to an interface not configured/started during installation. This is one possible case, not a diagnosis of every missing link. Check the actual interface, driver, cable and installed network manager.
Its example file is /etc/sysconfig/network/ifcfg-eth0. The following reproduces the source values with valid ASCII shell-style quotes; addresses and interface identity are examples to adapt:
The source changes STARTMODE to onboot, then runs rcnetwork restart. This is a legacy SUSE network-service layout; restarting networking interrupts management connectivity and does not apply unchanged to every modern distribution.
Can't find an answer?
Upload a log for AI diagnosis, or ask the AI assistant directly in the console.