Ubuntu
linux package

On native_write_msr_safe function issue

Bug #1596412 reported by asu on 2016-06-27

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	linux (Ubuntu)	Triaged	Medium	Unassigned

Bug Description

Bellow is content of perf report:
       │ ◆
       │ ▒
       │ ▒
       │ Disassembly of section load0: ▒
       │ ▒
       │ ffffffff810644b0 <load0>: ▒
       │ push %rbp ▒
       │ mov %esi,%eax ▒
       │ mov %edi,%ecx ▒
       │ mov %rsp,%rbp ▒
       │ wrmsr ▒
100,00 │ xor %eax,%eax ▒
       │ pop %rbp ▒
       │ ← retq ▒
       │ xchg %ax,%ax ▒

Process stall on do_trace_write_msr.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-24-generic 4.4.0-24.43
ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
Uname: Linux 4.4.0-24-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: asu 2888 F.... pulseaudio
CurrentDesktop: MATE
Date: Mon Jun 27 07:45:26 2016
InstallationDate: Installed on 2016-04-29 (58 days ago)
InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
IwConfig:
lo no wireless extensions.

enp1s0 no wireless extensions.
MachineType: Olidata S.p.A. ALABAMA
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-24-generic root=/dev/mapper/192--168--0--108--vg-root ro
RelatedPackageVersions:
linux-restricted-modules-4.4.0-24-generic N/A
linux-backports-modules-4.4.0-24-generic N/A
linux-firmware 1.157.1
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/08/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: S0101
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: To be filled by O.E.M.
dmi.board.vendor: To be filled by O.E.M.
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrS0101:bd07/08/2008:svnOlidataS.p.A.:pnALABAMA:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: ALABAMA
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: Olidata S.p.A.

Tags:

Revision history for this message

asu (corcodel-marian) wrote on 2016-06-27:

AlsaInfo.txt Edit (28.6 KiB, text/plain; charset="utf-8")
CRDA.txt Edit (422 bytes, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (56.5 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.7 KiB, text/plain; charset="utf-8")
JournalErrors.txt Edit (17.7 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (9.3 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (419 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.4 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (103 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.8 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (4.5 KiB, text/plain; charset="utf-8")
PulseList.txt Edit (23.8 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (111.2 KiB, text/plain; charset="utf-8")
WifiSyslog.txt Edit (82.1 KiB, text/plain; charset="utf-8")

Revision history for this message

Brad Figg (brad-figg) wrote on 2016-06-27: Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status:	New → Confirmed

Revision history for this message

asu (corcodel-marian) wrote on 2016-06-27:

apply_on_nes.patch Edit (1.9 KiB, text/plain)

This patch bellow set type notrace on all required function because trace is explycit performed and not need to put auto by compile on begin and end of function. Whit this patch applied only on perf must have proc stalled.

Ubuntu Foundations Team Bug Bot (crichton) on 2016-06-27

tags:

added: patch

Revision history for this message

Joseph Salisbury (jsalisbury) wrote on 2016-06-29:

Can you provide some information on the status of the patch with regards to getting it merged upstream? Has it been sent upstream, what sort of feedback has it received, is it getting applied to a subsystem maintainer's tree, etc?

People affected by this bug are probably wondering why the kernel team doesn't just apply the patch and fix it. The reason is that the kernel team is reluctant (not opposed) to apply any patch to a stable kernel that is not from upstream. Applying patches that don't come from upstream add greatly to the support of the kernel as other upstream patches may touch the same area as the non-upstream patch and may prevent them from applying cleanly.

To submit your patch, send your patch with the detailed description/changelog and your Signoff (ending with Signed-off-by: your name <email>), to the emails listed from ./scripts/get_maintainer.pl drivers/SUBSYSTEM-DETAILS (the get_maintainer.pl is from the kernel sources). Once you have sent the patch upstream and it's accepted, please drop a note here so that we can cherry-pick/include the patch into Ubuntu kernel.

Changed in linux (Ubuntu):
importance:	Undecided → Medium
status:	Confirmed → Triaged

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Patches

apply_on_nes.patch Edit

Add patch

Remote bug watches

Bug watches keep track of this bug in other bug trackers.

Ubuntulinux package

On native_write_msr_safe function issue

Bug Description

Other bug subscribers

Patches

Bug attachments

Remote bug watches

Ubuntu
linux package