From vmoutoussamy at suse.com Wed Aug 1 08:32:42 2018 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Wed, 1 Aug 2018 16:32:42 +0200 Subject: [sle-beta] Unsupported version of key: V3 In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76D014DD9DDC4@daeexmbx1.eur.ad.sag> References: <46AC8C81C10B8C48820201DF2AE1D76D014DD9B4CF@daeexmbx1.eur.ad.sag> <1532331131.20033.50.camel@suse.com> <46AC8C81C10B8C48820201DF2AE1D76D014DD9DDC4@daeexmbx1.eur.ad.sag> Message-ID: Hi, Well could you give more information on the faulty packages or faulty keys? Before starting to think about any solution we need to understand the issue and where it came from. > On 22 Jul 2018, at 13:32, Waite, Dick (External) wrote: > In November and December we were told they will soon be gone.... It's July and they are still with us with a SLES15 SP-0 GM Correct me if I?m wrong but we didn?t tell such thing, but I do remember asking for more detailed information on your issue back in 2017. Regards, -- Vincent Moutoussamy SUSE Beta Program, JeOS and SDK Project Manager > On 23 Jul 2018, at 11:19, Waite, Dick (External) wrote: > > Very good words Frederic, > > I have cleaned up a few machines but I was thinking would the "Cleanup when deleting package" in Yast2 not be the right place for this. After a few machines it does get rather tedious and the cleanup option sounds the right place or ? As I have a number of machine to do I'd be happy to Beta check the option when ready.... > > __R > ________________________________________ > From: sle-beta-bounces at lists.suse.com [sle-beta-bounces at lists.suse.com] on behalf of Frederic Crozat [fcrozat at suse.com] > Sent: 23 July 2018 09:32 > To: sle-beta at lists.suse.com > Subject: Re: [sle-beta] Unsupported version of key: V3 > > Le dimanche 22 juillet 2018 ? 11:32 +0000, Waite, Dick (External) a > ?crit : >> Grand Sunny Sunday, >> >> Why am I still seeing so many lines of: >> >> Warning: Unsupported version of key: V3 >> >> In November and December we were told they will soon be gone.... It's >> July and they are still with us with a SLES15 SP-0 GM > > This should help you: > > http://dominique.leuenberger.net/blog/2017/03/zypper-and-rpm-says-warning-unsupported-version-of-key-v3/ > > -- > Frederic Crozat > Enterprise Desktop Release Manager > SUSE > > _______________________________________________ > sle-beta mailing list > sle-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sle-beta > > Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com > > _______________________________________________ > sle-beta mailing list > sle-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sle-beta -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: Message signed with OpenPGP URL: From mmarion at qualcomm.com Wed Aug 1 10:09:54 2018 From: mmarion at qualcomm.com (Mike Marion) Date: Wed, 1 Aug 2018 16:09:54 +0000 Subject: [sle-beta] SLES12 SP4 Beta1 -- Looking good In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76D014DDA43F1@daeexmbx1.eur.ad.sag> References: <46AC8C81C10B8C48820201DF2AE1D76D014DDA43F1@daeexmbx1.eur.ad.sag> Message-ID: <20180801160952.GI27345@qualcomm.com> On Wed, Aug 01, 2018 at 04:27:07AM +0000, Waite, Dick (External) wrote: > Not see a lot of chatter on the list so I thought I'd give some input on Beta1, > with SLES15 often quite -ve, but with SLES12 SP4 Beta1 has been grand. I've noticed a couple minor things.. kernel-source/devel is missing the make cloneconfig bits. For some reason, the %flavors_to_build macro isn't expanding for me, when I attempt to build openafs. Only just zypper dup'd a 12.3 VM to 12.4 and attempted to build openafs though. -- Mike Marion-Unix SysAdmin/Sr. Staff IT Engineer-http://www.qualcomm.com From vmoutoussamy at suse.com Thu Aug 2 02:44:07 2018 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Thu, 2 Aug 2018 10:44:07 +0200 Subject: [sle-beta] Bugzilla says No. In-Reply-To: <2BED0F7D-3BD6-46E7-ADF6-220B4EF6C70E@suse.com> References: <46AC8C81C10B8C48820201DF2AE1D76D014DDA2112@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D014DDA283B@daeexmbx1.eur.ad.sag> <2BED0F7D-3BD6-46E7-ADF6-220B4EF6C70E@suse.com> Message-ID: Hi, Sorry for the delay and the inconvenience, this is fixed now! Your bugs are welcomed again. Regards, -- Vincent Moutoussamy SUSE Beta Program, JeOS and SDK Project Manager > On 30 Jul 2018, at 09:50, Vincent Moutoussamy > wrote: > > Signed PGP part > Hi, > > I?m on it and hope to fix this soon, > sorry for the inconvenience. > > Regards, > -- > Vincent Moutoussamy > SUSE Beta Program, JeOS and SDK Project Manager > >> On 30 Jul 2018, at 08:28, Waite, Dick (External) > wrote: >> >> Grand New Monday, >> >> Seems Firefox knows how to do Screenshots, so here is my issue with Bugzilla. >> >> I do have a couple more Bugs to create when your open for business ;o) >> >> __R >> >> >> From: Waite, Dick (External) >> Sent: 29 July 2018 10:16 >> To: sle-beta at lists.suse.com >> Subject: RE: Bugzilla says No. >> >> Grand Morning, >> >> I tried to create a Bugzilla report for a SLES12 SP-4 Beta 1 issues and I was told I was not allowed. >> >> I thought I had done all the pre-req.. >> >> __R >> >> >> >> ... >> ... >> >> Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com _______________________________________________ >> sle-beta mailing list >> sle-beta at lists.suse.com >> http://lists.suse.com/mailman/listinfo/sle-beta > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: Message signed with OpenPGP URL: From fcrozat at suse.com Thu Aug 2 06:25:39 2018 From: fcrozat at suse.com (Frederic Crozat) Date: Thu, 02 Aug 2018 14:25:39 +0200 Subject: [sle-beta] SLES12 SP4 Beta1 -- Looking good In-Reply-To: <20180801160952.GI27345@qualcomm.com> References: <46AC8C81C10B8C48820201DF2AE1D76D014DDA43F1@daeexmbx1.eur.ad.sag> <20180801160952.GI27345@qualcomm.com> Message-ID: <1533212739.16985.21.camel@suse.com> Le mercredi 01 ao?t 2018 ? 16:09 +0000, Mike Marion a ?crit : > On Wed, Aug 01, 2018 at 04:27:07AM +0000, Waite, Dick (External) > wrote: > > > Not see a lot of chatter on the list so I thought I'd give some > > input on Beta1, > > with SLES15 often quite -ve, but with SLES12 SP4 Beta1 has been > > grand. > > I've noticed a couple minor things.. > kernel-source/devel is missing the > make cloneconfig > bits. > > For some reason, the %flavors_to_build macro isn't expanding for me, > when I attempt to build openafs. > > Only just zypper dup'd a 12.3 VM to 12.4 and attempted to build > openafs > though. Could you open a bug report for this, now that bugzilla is able again to accept SLE12 SP4 bug report ? Thanks ! -- Frederic Crozat Enterprise Desktop Release Manager SUSE From beta-programs at lists.suse.com Wed Aug 8 03:08:00 2018 From: beta-programs at lists.suse.com (SUSE Beta Program) Date: Wed, 08 Aug 2018 09:08:00 +0000 Subject: [sle-beta] [ANNOUNCE] SUSE Linux Enterprise 12 Service Pack 4 Beta 2 is out! Message-ID: <5b6ab2f0b915c_318212a33106904b@sle-prjmgr.mail> We are happy to announce SUSE Linux Enterprise 12 SP4 Beta 2: SUSE Linux Enterprise Server (SLES), SUSE Linux Enterprise Server For SAP (SLES for SAP), SUSE Linux Enterprise Just Enough Operating System (JeOS), SUSE Linux Enterprise Desktop (SLED), SUSE Linux Enterprise High Availability (SLEHA), SUSE Linux Enterprise Workstation Extension (SLEWE), and SUSE Linux Enterprise Software Development Kit (SLESDK). Download[2] == Notable changes since Beta 1 - Kernel stability improvements - Driver updates for: Cavium, Broadcom, Cheiso, Microsemi, Intel i40e/i40evf, - Other updates for: Melanox librdmacm library update, Adding CPUMF Counters for z14 - Apache pass fixes - Improvements in Shared Memory Communications (SMC) - Protected key dm-crypt key management tool (crypto) (s390-tools) - New instruction support in toolchain - glibc part (z14) - Support for CPACF enhancements to kernel (crypto) (z14) - Support architectural limit of crypto adapters in zcrypt device driver - Kernel/zcrypt exploitation support for CEX6S crypto cards FATE#324997 == Selection of fixed bugs in Beta 2 - HA problems with cluster_md bsc#1101348 - Kernel Performance and Stability bsc#1098686 bsc#1103522 bsc#1103517 bsc#1103521 bsc#1103529 bsc#1009475 == More informations SLE Beta Page[1] Release Notes[3] Known Issues[4] We are thankful for your support in trying out our beta products and we welcome your feedback. Have fun beta testing! Your SUSE Linux Enterprise Team Please refer to our dedicated SLE Beta Program webpage[1] for any general information. However, do not hesitate to contact us at beta-programs at lists.suse.com if you have any questions. You received this email because you're signed up to get updates from us. Please send an email to beta-programs at lists.suse.com if you want to unsubscribe. [1]https://www.suse.com/betaprogram/sle-beta/ [2]https://www.suse.com/betaprogram/sle-beta/#download [3]https://www.suse.com/betaprogram/sle-beta/#releasenotes [4]https://www.suse.com/betaprogram/sle-beta/#knownissues -------------- next part -------------- An HTML attachment was scrubbed... URL: From S.M.Flood at uis.cam.ac.uk Wed Aug 15 08:39:27 2018 From: S.M.Flood at uis.cam.ac.uk (Simon Flood) Date: Wed, 15 Aug 2018 15:39:27 +0100 Subject: [sle-beta] Multiple subnets with opensm service In-Reply-To: References: Message-ID: <00322e3d-1d53-a326-c881-fe28300cd2ff@uis.cam.ac.uk> On 15/08/18 15:25, Schulte, Matt wrote: > Does anyone know if there is a good way of running opensm (IB subnet manager) on multiple subnets? > > It looks like what gets installed in /etc/sysconfig/opensm and /etc/init.d/opensmd are meant to run only one subnet. > > I have been running two opensm processes in the /etc/initi.d/after.local file and I wonder if there is a better way. Is this specifically related to the current SLE12 SP4 Beta? Sounds like more of a support question which would be better addressed via a support request or in the SUSE Forums. HTH, Simon -- Simon Flood HPC System Administrator University of Cambridge Information Services United Kingdom SUSE/Micro Focus Knowledge Partner From beta-programs at lists.suse.com Thu Aug 16 09:11:51 2018 From: beta-programs at lists.suse.com (SUSE Beta Program) Date: Thu, 16 Aug 2018 15:11:51 +0000 Subject: [sle-beta] [ANNOUNCE] SUSE Linux Enterprise 12 Service Pack 4 Beta 3 is out! Message-ID: <5b759437db1f2_2286b0b3149974b@sle-prjmgr.mail> We are happy to announce SUSE Linux Enterprise 12 SP4 Beta 3: SUSE Linux Enterprise Server (SLES), SUSE Linux Enterprise Server For SAP (SLES for SAP), SUSE Linux Enterprise Just Enough Operating System (JeOS), SUSE Linux Enterprise Desktop (SLED), SUSE Linux Enterprise High Availability (SLEHA), SUSE Linux Enterprise Workstation Extension (SLEWE), and SUSE Linux Enterprise Software Development Kit (SLESDK). Download[2] == NEW Raspberry Pi image available We are happy to announce the inclusion of SLES 12 SP4 bootable image for Raspberry Pi in the SLE Public Beta Program. The image is available via the SLES download link and is named: SLES12-SP4-JeOS.aarch64-12.4-RaspberryPi-Beta3.raw.xz. Compared to SLES 12 SP3, the support for Model B+ and Compute Module 3 is new, and it offers easier configuration of expansion boards by the user. Both were already SLES 15 features though. == Notable changes since Beta 2 Updates for the following packages: - kernel with some security fixes (like CVE-2018-5390), - virtualisation: qclib, qemu, - zlib, yast, freeipmi, openCryptoki, mariadb 10.2, - openssl-ibmca, libica and other s390x relevant changes. SAP: - Hands free support for SAP HANA, - SR wizard in bare-metal. == More informations SLE Beta Page[1] Release Notes[3] Known Issues[4] We are thankful for your support in trying out our beta products and we welcome your feedback. Have fun beta testing! Your SUSE Linux Enterprise Team Please refer to our dedicated SLE Beta Program webpage[1] for any general information. However, do not hesitate to contact us at beta-programs at lists.suse.com if you have any questions. You received this email because you're signed up to get updates from us. Please send an email to beta-programs at lists.suse.com if you want to unsubscribe. [1]https://www.suse.com/betaprogram/sle-beta/ [2]https://www.suse.com/betaprogram/sle-beta/#download [3]https://www.suse.com/betaprogram/sle-beta/#releasenotes [4]https://www.suse.com/betaprogram/sle-beta/#knownissues -------------- next part -------------- An HTML attachment was scrubbed... URL: From Matt.Schulte at netapp.com Fri Aug 17 14:16:47 2018 From: Matt.Schulte at netapp.com (Schulte, Matt) Date: Fri, 17 Aug 2018 20:16:47 +0000 Subject: [sle-beta] Problems with kdump? Message-ID: Is anybody else seeing problems like this during boot: 2018-08-17T16:02:43.923174-05:00 linux-fxnc load.sh[1522]: Unknown type (Reserved) while parsing /sys/firmware/memmap/7/type. Please report this as bug. Using RANGE_RESERVED now. 2018-08-17T16:02:43.923929-05:00 linux-fxnc load.sh[1522]: Unknown type (Reserved) while parsing /sys/firmware/memmap/11/type. Please report this as bug. Using RANGE_RESERVED now. 2018-08-17T16:02:43.924465-05:00 linux-fxnc load.sh[1522]: Unknown type (Reserved) while parsing /sys/firmware/memmap/1/type. Please report this as bug. Using RANGE_RESERVED now. 2018-08-17T16:02:43.924931-05:00 linux-fxnc load.sh[1522]: Unknown type (Reserved) while parsing /sys/firmware/memmap/4/type. Please report this as bug. Using RANGE_RESERVED now. 2018-08-17T16:02:43.925436-05:00 linux-fxnc load.sh[1522]: Unknown type (Reserved) while parsing /sys/firmware/memmap/12/type. Please report this as bug. Using RANGE_RESERVED now. 2018-08-17T16:02:43.925930-05:00 linux-fxnc load.sh[1522]: Unknown type (Reserved) while parsing /sys/firmware/memmap/2/type. Please report this as bug. Using RANGE_RESERVED now. 2018-08-17T16:02:43.926398-05:00 linux-fxnc load.sh[1522]: Unknown type (Reserved) while parsing /sys/firmware/memmap/10/type. Please report this as bug. Using RANGE_RESERVED now. 2018-08-17T16:02:43.926764-05:00 linux-fxnc load.sh[1522]: Unknown type (Reserved) while parsing /sys/firmware/memmap/9/type. Please report this as bug. Using RANGE_RESERVED now. 2018-08-17T16:02:43.927126-05:00 linux-fxnc load.sh[1522]: ELF core (kcore) parse failed 2018-08-17T16:02:43.927858-05:00 linux-fxnc kdump[1871]: FAILED to load kdump kernel: /sbin/kexec -p /boot/vmlinuz-4.12.14-94.33-default --append="ksdevice=bootif text quiet plymouth.enable=0 biosdevname=0 net.ifnames=0 console=tty0 console=ttyS0,115200 rdloaddriver=scsi_dh_rdac,scsi_dh_alua scsi_dh_alua.optimize_stpg=1 nvme-core.multipath=N elevator=deadline sysrq=yes reset_devices acpi_no_memhotplug cgroup_disable=memory irqpoll nr_cpus=1 root=kdump rootflags=bind rd.udev.children-max=8 disable_cpu_apicid=0 panic=1" --initrd=/boot/initrd-4.12.14-94.33-default-kdump , Result: Unknown type (Reserved) while parsing /sys/firmware/memmap/7/type. Please report this as bug. Using RANGE_RESERVED now.#012Unknown type (Reserved) while parsing /sys/firmware/memmap/11/type. Please report this as bug. Using RANGE_RESERVED now.#012Unknown type (Reserved) while parsing /sys/firmware/memmap/1/type. Please report this as bug. Using RANGE_RESERVED now.#012Unknown type (Reserved) while parsing /sys/firmware/memmap/4/type. Please report this as bug. Using RANGE_RESERVED now.#012Unknown type ( 2018-08-17T16:02:44.277525-05:00 linux-fxnc kdump[1894]: Loaded kdump kernel: /sbin/kexec -p /boot/vmlinuz-4.12.14-94.33-default --append="ksdevice=bootif text quiet plymouth.enable=0 biosdevname=0 net.ifnames=0 console=tty0 console=ttyS0,115200 rdloaddriver=scsi_dh_rdac,scsi_dh_alua scsi_dh_alua.optimize_stpg=1 nvme-core.multipath=N elevator=deadline sysrq=yes reset_devices acpi_no_memhotplug cgroup_disable=memory irqpoll nr_cpus=1 root=kdump rootflags=bind rd.udev.children-max=8 disable_cpu_apicid=0 panic=1" --initrd=/boot/initrd-4.12.14-94.33-default-kdump -s, Result: 2018-08-17T16:02:44.280357-05:00 linux-fxnc systemd[1]: Started Load kdump kernel early on startup. 2018-08-17T16:02:44.280852-05:00 linux-fxnc load.sh[1522]: Cannot load /boot/vmlinuz-4.12.14-94.33-default Matt Schulte From jbohac at suse.cz Sat Aug 18 01:20:10 2018 From: jbohac at suse.cz (Jiri Bohac) Date: Sat, 18 Aug 2018 09:20:10 +0200 Subject: [sle-beta] Problems with kdump? In-Reply-To: References: Message-ID: <20180818072010.nqwncaxxy7eksoxj@dwarf.suse.cz> Hello, On Fri, Aug 17, 2018 at 08:16:47PM +0000, Schulte, Matt wrote: > Is anybody else seeing problems like this during boot: > > 2018-08-17T16:02:43.923174-05:00 linux-fxnc load.sh[1522]: Unknown type (Reserved) while parsing /sys/firmware/memmap/7/type. Please report this as bug. Using RANGE_RESERVED now. this has been reported in Bugzilla in bsc#1104783. Looks like the kexec-tools version in SLE12-SP4 needs a few fixes or an update to work with the 4.12 kernel. Thanks for reporting this. -- Jiri Bohac SUSE Labs, Prague, Czechia From beta-programs at lists.suse.com Mon Aug 20 07:16:40 2018 From: beta-programs at lists.suse.com (SUSE Beta Program) Date: Mon, 20 Aug 2018 13:16:40 +0000 Subject: [sle-beta] [ANNOUNCE] SUSE Linux Enterprise Server for SAP Applications 12 Service Pack 4 Beta! Message-ID: <5b7abf38e98ad_75a4f43314738cb@sle-prjmgr.mail> We are happy to announce that SUSE Linux Enterprise Server for SAP Applications 12 SP4 is now also available as part of the SUSE Linux Enterprise Public Beta program. You can download it here[2]. With Service Pack 4 we are going to introduce some new exciting features while still maintaining the stability and feature set of Service Pack 3. Here are some selected new features we are going to introduce especially for SUSE Linux Enterprise Server for SAP Applications 12 SP4: 1. To maintain the high performance of SAP systems we are adding Workload Memory Protection as a better performing alternative to the existing Page Cache Management. This feature is based on open source cgroup and provides a highly scalable solution to protect the memory where SAP applications store data for fast access from Linux kernel memory management. 2. Non-Volatile Dual In-line Memory Module (NV-DIMM) support for disk-less databases paves the way for instant database recovery after system reboots. 3. For deploying pre-configured HANA-SR environments we are offering an unattended installation mode for the HANA-SR wizard on bare-metal servers. In order to use it, you first have to create a configuration file by running the YaST sap_ha module manually and save the configuration on the last screen. This configuration can now be used for automatic deployments using following CLI-commands: 3.1 yast2 sap_ha readconfig to upload and validate the configuration automatically 3.2 yast2 sap_ha readconfig unattended for an unattended import, validation and installation of the cluster, based on the provided configuration file == More informations SLE Beta Page[1] Release Notes[3] Known Issues[4] We are thankful for your support in trying out our beta products and we welcome your feedback. Have fun beta testing! Your SUSE Linux Enterprise and SUSE SAP Team Please refer to our dedicated SLE Beta Program webpage[1] for any general information. However, do not hesitate to contact us at beta-programs at lists.suse.com if you have any questions. You received this email because you're signed up to get updates from us. Please send an email to beta-programs at lists.suse.com if you want to unsubscribe. [1]https://www.suse.com/betaprogram/sle-beta/ [2]https://www.suse.com/betaprogram/sle-beta/#download [3]https://www.suse.com/betaprogram/sle-beta/#releasenotes [4]https://www.suse.com/betaprogram/sle-beta/#knownissues -------------- next part -------------- An HTML attachment was scrubbed... URL: From vmoutoussamy at suse.com Mon Aug 20 09:24:34 2018 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Mon, 20 Aug 2018 17:24:34 +0200 Subject: [sle-beta] lzo errors immediately after grub In-Reply-To: References: Message-ID: <5D68068B-C8AD-4043-9A1C-F1252EB0269B@suse.com> Hi, Well with my level of expertise I can?t do much and can just confirm the error message in the supportconfig. So I have opened a bug report for the issue: bsc#1105368 - lzo errors immediately after grub Regards, -- Vincent Moutoussamy SUSE Beta Program, JeOS and SDK Project Manager > On 20 Aug 2018, at 16:34, Schulte, Matt wrote: > > I believe I have seen this on all of eight my servers that I have installed SP4 on so far. > > They do continue to boot. > > Attaching a supportconfig from one of them. > > Matt Schulte > > From: Vincent Moutoussamy > Sent: Monday, August 20, 2018 8:09 AM > To: Schulte, Matt > Cc: sle-beta at lists.suse.com > Subject: Re: [sle-beta] lzo errors immediately after grub > > Hi, > > pstore is a filesystem used to store data information when a kernel crash occurs. > Were you able to boot the system? > Could you retrieve a supportconfig on that server? > > Regards, > -- > Vincent Moutoussamy > SUSE Beta Program, JeOS and SDK Project Manager > > > On 17 Aug 2018, at 20:26, Schulte, Matt > wrote: > > I am seeing these lzo_decompress error messages immediately after the grub menu exits and then eventually the server completes boot. > > I saw these with Beta 2 and still see them after upgrading to Beta 3. > > Anybody else see this? Know what it is? > > > > Matt Schulte > > _______________________________________________ > sle-beta mailing list > sle-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sle-beta > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: Message signed with OpenPGP URL: From vmoutoussamy at suse.com Wed Aug 22 02:57:06 2018 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Wed, 22 Aug 2018 10:57:06 +0200 Subject: [sle-beta] Odd server hang In-Reply-To: References: Message-ID: Hi, Please open a bug report via https://bugzilla.suse.com/enter_bug.cgi?product=Beta%20SUSE%20Linux%20Enterprise%20Server%2012%20SP4 And attach a supportconfig of this server so we can investigate the issue. Thanks, Regards, -- Vincent Moutoussamy SUSE Beta Program, JeOS and SDK Project Manager > On 21 Aug 2018, at 15:59, Schulte, Matt wrote: > > The last thing I had done yesterday was configure the server as an iSCSI initiator. It would seem this morning that the server hung with the attached messages displayed on the terminal. > > Upon rebooting I don?t see any crash dump in /var/crash. At what I assume was the time of the crash I don?t see anything in the message log to indicate a problem. > > Running SLES 12 SP4 Beta 3 > > Matt Schulte > > _______________________________________________ > sle-beta mailing list > sle-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sle-beta -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: Message signed with OpenPGP URL: From vmoutoussamy at suse.com Wed Aug 29 02:28:20 2018 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Wed, 29 Aug 2018 10:28:20 +0200 Subject: [sle-beta] assert in dmi_check_system In-Reply-To: References: Message-ID: Hi, Could you please create a bug report for this issue? Here is the direct link to do so: https://bugzilla.suse.com/enter_bug.cgi?product=Beta%20SUSE%20Linux%20Enterprise%20Server%2012%20SP4 Thank you, Regards, -- Vincent Moutoussamy SUSE Beta Program, JeOS and SDK Project Manager > On 29 Aug 2018, at 09:03, tiantao (H) wrote: > > > HI : > > I found a bug on Hi1616. Using beta3 on sles12sp4 > > The system will encounter the following warning when it start up on beta3.but the system will boot ok using the sle12sp3 or sle15 on same platform > > > [ 0.000986] dmi check: not initialized yet. > [ 0.001000] ------------[ cut here ]------------ > [ 0.001011] WARNING: CPU: 0 PID: 0 at ../drivers/firmware/dmi_scan.c:832 dmi_check_system+0x8c/0x94 > [ 0.001012] Modules linked in: > [ 0.001015] Supported: Yes > [ 0.001018] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.12.14-94.33-default #1 SLE12-SP4 > [ 0.001019] Hardware name: (null) (DT) > [ 0.001021] task: ffff000008e22980 task.stack: ffff000008e10000 > [ 0.001023] PC is at dmi_check_system+0x8c/0x94 > [ 0.001025] LR is at dmi_check_system+0x8c/0x94 > [ 0.001027] pc : [] lr : [] pstate: 60000005 > [ 0.001028] sp : ffff000008e13f70 > [ 0.001030] x29: ffff000008e13f70 x28: 0000000000c80018 > [ 0.001033] x27: 000000000000015a x26: 000000003ed67828 > [ 0.001036] x25: 0000000000000000 x24: ffff80affbfffd00 > [ 0.001039] x23: ffff000008e19000 x22: ffff000008f7a000 > [ 0.001042] x21: ffff000008d3f828 x20: ffff000008f7a000 > [ 0.001045] x19: ffff000008d4a0f8 x18: 000000000000000b > [ 0.001048] x17: 0000000000000000 x16: 0000000000000000 > [ 0.001051] x15: ffffffffffffffff x14: 662072656d697420 > [ 0.001054] x13: 676e697375206465 x12: 0000000000000000 > [ 0.001057] x11: 00000000000000fc x10: 0000000000000004 > [ 0.001060] x9 : 00000000000000fd x8 : ffff000008e1a488 > [ 0.001063] x7 : ffff0000085fb018 x6 : ffff000008fd493e > [ 0.001065] x5 : ffff801ffbe38e00 x4 : 0000000000000000 > [ 0.001068] x3 : 0000000000000001 x2 : ffffffffffffffff > [ 0.001071] x1 : ffff000008e42338 x0 : 000000000000001f > [ 0.001075] Call trace: > [ 0.001077] Exception stack(0xffff000008e13e30 to 0xffff000008e13f70) > [ 0.001079] 3e20: 000000000000001f ffff000008e42338 > [ 0.001081] 3e40: ffffffffffffffff 0000000000000001 0000000000000000 ffff801ffbe38e00 > [ 0.001083] 3e60: ffff000008fd493e ffff0000085fb018 ffff000008e1a488 00000000000000fd > [ 0.001084] 3e80: 0000000000000004 00000000000000fc 0000000000000000 676e697375206465 > [ 0.001086] 3ea0: 662072656d697420 ffffffffffffffff 0000000000000000 0000000000000000 > [ 0.001087] 3ec0: 000000000000000b ffff000008d4a0f8 ffff000008f7a000 ffff000008d3f828 > [ 0.001089] 3ee0: ffff000008f7a000 ffff000008e19000 ffff80affbfffd00 0000000000000000 > [ 0.001091] 3f00: 000000003ed67828 000000000000015a 0000000000c80018 ffff000008e13f70 > [ 0.001092] 3f20: ffff00000872ba88 ffff000008e13f70 ffff00000872ba88 0000000060000005 > [ 0.001094] 3f40: ffff00000987c000 0000000000000001 ffffffffffffffff ffff801ffbe38e00 > [ 0.001095] 3f60: ffff000008e13f70 ffff00000872ba88 > [ 0.001098] [] dmi_check_system+0x8c/0x94 > [ 0.001102] [] acpi_early_init+0x58/0xd8 > [ 0.001104] [] start_kernel+0x38c/0x3fc > [ 0.001108] ---[ end trace f68728a0d3053b52 ]--- > [ 0.004534] ACPI: 1 ACPI AML tables successfully acquired and loaded > > > As you can see from the code below,the above callstack is because the dmi_initialized is not assigned a value of 1. > > 827 int dmi_check_system(const struct dmi_system_id *list) > 828 { > 829 int count = 0; > 830 const struct dmi_system_id *d; > 831 > 832 WARN(!dmi_initialized, KERN_ERR "dmi check: not initialized yet.\n"); > 833 > 834 for (d = list; !dmi_is_end_of_table(d); d++) > 835 if (dmi_matches(d)) { > 836 count++; > 837 if (d->callback && d->callback(d)) > 838 break; > 839 } > 840 > 841 return count; > 842 } > > but the dmi_initialized will be assigned the value of 1 in dmi_scan_machine function under any condition . I notice the dmi_scan_machine is different from the latest kernel. > > ----------------------------------------------------------------------------- > Best Regards, > > tiantao6 at huawei.com > Turing Architecture and Design Dept, Hisilicon > > ---------------------------------------------------------------------- > ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????? > This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it! > > _______________________________________________ > sle-beta mailing list > sle-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sle-beta -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: Message signed with OpenPGP URL: From hui.zhi.zhao at suse.com Wed Aug 29 02:50:21 2018 From: hui.zhi.zhao at suse.com (Hui-Zhi) Date: Wed, 29 Aug 2018 16:50:21 +0800 Subject: [sle-beta] assert in dmi_check_system In-Reply-To: References: Message-ID: Hi Vincent, Here's the issue on Bugzilla: https://bugzilla.novell.com/show_bug.cgi?id=1105597 --Regards,Hui-Zhi On Wed, 2018-08-29 at 10:28 +0200, Vincent Moutoussamy wrote: > Hi, > Could you please create a bug report for this issue? > Here is the direct link to do so: > https://bugzilla.suse.com/enter_bug.cgi?product=Beta%20SUSE%20Linux%20Enterprise%20Server%2012%20SP4 > > Thank you, > > Regards, > > -- > Vincent Moutoussamy > SUSE Beta Program, JeOS and SDK Project Manager > > > > > On 29 Aug 2018, at 09:03, tiantao (H) wrote: > > > > > > HI : > > > > I found a bug on Hi1616. Using beta3 on sles12sp4 > > > > The system will encounter the following warning when it start up on > > beta3.but the system will boot ok using the sle12sp3 or sle15 on > > same platform > > > > > > [ 0.000986] dmi check: not initialized yet. > > [ 0.001000] ------------[ cut here ]------------ > > [ 0.001011] WARNING: CPU: 0 PID: 0 at > > ../drivers/firmware/dmi_scan.c:832 dmi_check_system+0x8c/0x94 > > [ 0.001012] Modules linked in: > > [ 0.001015] Supported: Yes > > [ 0.001018] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.12.14- > > 94.33-default #1 SLE12-SP4 > > [ 0.001019] Hardware name: (null) (DT) > > [ 0.001021] task: ffff000008e22980 task.stack: ffff000008e10000 > > [ 0.001023] PC is at dmi_check_system+0x8c/0x94 > > [ 0.001025] LR is at dmi_check_system+0x8c/0x94 > > [ 0.001027] pc : [] lr : [] > > pstate: 60000005 > > [ 0.001028] sp : ffff000008e13f70 > > [ 0.001030] x29: ffff000008e13f70 x28: 0000000000c80018 > > [ 0.001033] x27: 000000000000015a x26: 000000003ed67828 > > [ 0.001036] x25: 0000000000000000 x24: ffff80affbfffd00 > > [ 0.001039] x23: ffff000008e19000 x22: ffff000008f7a000 > > [ 0.001042] x21: ffff000008d3f828 x20: ffff000008f7a000 > > [ 0.001045] x19: ffff000008d4a0f8 x18: 000000000000000b > > [ 0.001048] x17: 0000000000000000 x16: 0000000000000000 > > [ 0.001051] x15: ffffffffffffffff x14: 662072656d697420 > > [ 0.001054] x13: 676e697375206465 x12: 0000000000000000 > > [ 0.001057] x11: 00000000000000fc x10: 0000000000000004 > > [ 0.001060] x9 : 00000000000000fd x8 : ffff000008e1a488 > > [ 0.001063] x7 : ffff0000085fb018 x6 : ffff000008fd493e > > [ 0.001065] x5 : ffff801ffbe38e00 x4 : 0000000000000000 > > [ 0.001068] x3 : 0000000000000001 x2 : ffffffffffffffff > > [ 0.001071] x1 : ffff000008e42338 x0 : 000000000000001f > > [ 0.001075] Call trace: > > [ 0.001077] Exception stack(0xffff000008e13e30 to > > 0xffff000008e13f70) > > [ 0.001079] 3e20: > > 000000000000001f ffff000008e42338 > > [ 0.001081] 3e40: ffffffffffffffff 0000000000000001 > > 0000000000000000 ffff801ffbe38e00 > > [ 0.001083] 3e60: ffff000008fd493e ffff0000085fb018 > > ffff000008e1a488 00000000000000fd > > [ 0.001084] 3e80: 0000000000000004 00000000000000fc > > 0000000000000000 676e697375206465 > > [ 0.001086] 3ea0: 662072656d697420 ffffffffffffffff > > 0000000000000000 0000000000000000 > > [ 0.001087] 3ec0: 000000000000000b ffff000008d4a0f8 > > ffff000008f7a000 ffff000008d3f828 > > [ 0.001089] 3ee0: ffff000008f7a000 ffff000008e19000 > > ffff80affbfffd00 0000000000000000 > > [ 0.001091] 3f00: 000000003ed67828 000000000000015a > > 0000000000c80018 ffff000008e13f70 > > [ 0.001092] 3f20: ffff00000872ba88 ffff000008e13f70 > > ffff00000872ba88 0000000060000005 > > [ 0.001094] 3f40: ffff00000987c000 0000000000000001 > > ffffffffffffffff ffff801ffbe38e00 > > [ 0.001095] 3f60: ffff000008e13f70 ffff00000872ba88 > > [ 0.001098] [] dmi_check_system+0x8c/0x94 > > [ 0.001102] [] acpi_early_init+0x58/0xd8 > > [ 0.001104] [] start_kernel+0x38c/0x3fc > > [ 0.001108] ---[ end trace f68728a0d3053b52 ]--- > > [ 0.004534] ACPI: 1 ACPI AML tables successfully acquired and > > loaded > > > > > > As you can see from the code below,the above callstack is because > > the dmi_initialized is not assigned a value of 1. > > > > 827 int dmi_check_system(const struct dmi_system_id *list) > > 828 { > > 829 int count = 0; > > 830 const struct dmi_system_id *d; > > 831 > > 832 WARN(!dmi_initialized, KERN_ERR "dmi check: not > > initialized yet.\n"); > > 833 > > 834 for (d = list; !dmi_is_end_of_table(d); d++) > > 835 if (dmi_matches(d)) { > > 836 count++; > > 837 if (d->callback && d->callback(d)) > > 838 break; > > 839 } > > 840 > > 841 return count; > > 842 } > > > > but the dmi_initialized will be assigned the value of 1 in > > dmi_scan_machine function under any condition . I notice the > > dmi_scan_machine is different from the latest kernel. > > > > ----------------------------------------------------------------- > > ------------ > > Best Regards, > > > > tiantao6 at huawei.com > > Turing Architecture and Design Dept, Hisilicon > > > > ----------------------------------------------------------------- > > ----- > > ??????????????????????????????????????????????????????????????????? > > ???????????????????????????????????????????????? > > This e-mail and its attachments contain confidential information > > from HUAWEI, which is intended only for the person or entity whose > > address is listed above. Any use of the information contained > > herein in any way (including, but not limited to, total or partial > > disclosure, reproduction, or dissemination) by persons other than > > the intended recipient(s) is prohibited. If you receive this e-mail > > in error, please notify the sender by phone or email immediately > > and delete it! > > > > _______________________________________________ > > sle-beta mailing list > > sle-beta at lists.suse.com > > http://lists.suse.com/mailman/listinfo/sle-beta > > _______________________________________________sle-beta mailing > listsle-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sle-beta -------------- next part -------------- An HTML attachment was scrubbed... URL: From beta-programs at lists.suse.com Fri Aug 31 08:25:36 2018 From: beta-programs at lists.suse.com (SUSE Beta Program) Date: Fri, 31 Aug 2018 14:25:36 +0000 Subject: [sle-beta] [ANNOUNCE] SUSE Linux Enterprise 12 Service Pack 4 Beta 4 is out! Message-ID: <5b894fe025724_6e8111b93144455c@sle-prjmgr.mail> We are happy to announce SUSE Linux Enterprise 12 SP4 Beta 4: SUSE Linux Enterprise Server (SLES), SUSE Linux Enterprise Server For SAP (SLES for SAP), SUSE Linux Enterprise Just Enough Operating System (JeOS), SUSE Linux Enterprise Desktop (SLED), SUSE Linux Enterprise High Availability (SLEHA), SUSE Linux Enterprise Workstation Extension (SLEWE), and SUSE Linux Enterprise Software Development Kit (SLESDK). Download[2] == Notable changes since Beta 3 Added packages: - google-noto-sans-cjk-fonts - libssh version 0.6.3 now directly in SLES and SLED. It was previously present in SDK. Updated packages: - curl version 7.60.0 (rebase from SLE15) - dapl version 2.1.10 - google-noto-fonts version 20170919 (new font and remove CJK) - intel-gpu-tools (security/bugfix/feature) [x86_64] - kernel, kdump, kexec-tools, crash, linux-glibc-devel, kexec-tools - kvm_stat backporting kvm_stat patches from upstream - libvirt (bugfix) - ndctl version 62 - nvme-cli (rebase from SLE15) - open-iscsi update to latest upstream version - openssl-1.0 version 1.0.2p - openssl-1.1 version 1.1.0i - openvswitch - qemu - smc-tools version 1.1.0 [s390x] - tomcat version 9.0.10 - tpm, tss - xen [x86_64] - xfsprogs version 4.15.0 - yast2 For more details, please check [5]. == More informations SLE Beta Page[1] Release Notes[3] Known Issues[4] We are thankful for your support in trying out our beta products and we welcome your feedback. Have fun beta testing! Your SUSE Linux Enterprise Team Please refer to our dedicated SLE Beta Program webpage[1] for any general information. However, do not hesitate to contact us at beta-programs at lists.suse.com if you have any questions. You received this email because you're signed up to get updates from us. Please send an email to beta-programs at lists.suse.com if you want to unsubscribe. [1]https://www.suse.com/betaprogram/sle-beta/ [2]https://www.suse.com/betaprogram/sle-beta/#download [3]https://www.suse.com/betaprogram/sle-beta/#releasenotes [4]https://www.suse.com/betaprogram/sle-beta/#knownissues [5]https://www.suse.com/betaprogram/sle-beta/#changelogs -------------- next part -------------- An HTML attachment was scrubbed... URL: