← Back to team overview

group.of.nepali.translators team mailing list archive

  1. group.of.nepali.translators team
  2. Mailing list archive
  3. Message #23931

[Bug 1769182] Re: ./configure --enable-arm needed for ARM events

  Thread Previous • Date Previous • • Thread Next 
This bug was fixed in the package rasdaemon - 0.5.6-2ubuntu1.1

---------------
rasdaemon (0.5.6-2ubuntu1.1) xenial; urgency=medium

  * debian/rules: Enable ARM events --enable-arm (LP: #1769182)

rasdaemon (0.5.6-2ubuntu1) xenial; urgency=medium

  * Cherrypick upstream patches to support ARM kernel trace events.
    LP: #1741978

 -- Manoj Iyer <manoj.iyer@xxxxxxxxxxxxx>  Wed, 09 May 2018 14:54:44
-0500

** Changed in: rasdaemon (Ubuntu Xenial)
       Status: Fix Committed => Fix Released

** Changed in: rasdaemon (Ubuntu Artful)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1769182

Title:
  ./configure --enable-arm needed for ARM events

Status in rasdaemon package in Ubuntu:
  Fix Released
Status in rasdaemon source package in Xenial:
  Fix Released
Status in rasdaemon source package in Artful:
  Fix Released
Status in rasdaemon source package in Bionic:
  Fix Released
Status in rasdaemon package in Debian:
  Fix Released

Bug description:
  [Impact]
  The UEFI 2.6 spec added support for ARM processor errors and errors
  that have unrecognized CPER section types. rasdaemon needs to support ARM kernel trace events. To enable arm events we need to configure rasdaemon package with --enable-arm 

  [Test]
  debian/rules needs --enable-arm to enable arm events. I have a test build of the rasdaemon package in ppa:centriq-team/lp1741978-rasdaemon. I tested this on an a QDF2400 system. Here are the results for bionic, artful and xenial.

  --- bionic ---
  ubuntu@awrep3:~$ sudo service rasdaemon status
  ● rasdaemon.service - RAS daemon to log the RAS events
     Loaded: loaded (/lib/systemd/system/rasdaemon.service; enabled; vendor preset
     Active: active (running) since Mon 2018-04-23 15:25:18 UTC; 17s ago
   Main PID: 3369 (rasdaemon)
      Tasks: 1 (limit: 7065)
     CGroup: /system.slice/rasdaemon.service
             └─3369 /usr/sbin/rasdaemon -f -r

  Apr 23 15:25:18 awrep3 rasdaemon[3369]: ras:arm_event event enabled
  Apr 23 15:25:18 awrep3 rasdaemon[3369]: Enabled event ras:arm_event
  Apr 23 15:25:18 awrep3 rasdaemon[3369]: Can't parse /proc/cpuinfo: missing [vend
  Apr 23 15:25:18 awrep3 rasdaemon[3369]: Can't register mce handler
  Apr 23 15:25:18 awrep3 rasdaemon[3369]: Can't get traces from ras:aer_event
  Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Recording mc_event events
  Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Recording aer_event events
  Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Recording extlog_event events
  Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Recording mce_record events
  Apr 23 15:25:19 awrep3 rasdaemon[3369]: rasdaemon: Recording arm_event events

  ubuntu@awrep3:~$ grep rasdaemon /var/log/syslog 
  Apr 23 15:25:18 awrep3 rasdaemon: ras:mc_event event enabled
  Apr 23 15:25:18 awrep3 rasdaemon: ras:mc_event event enabled
  Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: ras:mc_event event enabled
  Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Enabled event ras:mc_event
  Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: ras:aer_event event enabled
  Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Enabled event ras:aer_event
  Apr 23 15:25:18 awrep3 rasdaemon[3370]: rasdaemon: ras:mc_event event enabled
  Apr 23 15:25:18 awrep3 rasdaemon[3370]: rasdaemon: ras:aer_event event enabled
  Apr 23 15:25:18 awrep3 rasdaemon[3370]: rasdaemon: Can't write to set_event
  Apr 23 15:25:18 awrep3 rasdaemon[3370]: rasdaemon: Can't write to set_event
  Apr 23 15:25:18 awrep3 rasdaemon[3370]: rasdaemon: ras:arm_event event enabled
  Apr 23 15:25:18 awrep3 rasdaemon: Enabled event ras:mc_event
  Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: ras:arm_event event enabled
  Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Enabled event ras:arm_event
  Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Can't parse /proc/cpuinfo: missing [vendor_id] [cpu family] [model] [cpu MHz] [flags]
  Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Can't register mce handler
  Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Can't get ras:extlog_mem_event traces. Perhaps this feature is not supported on your system.
  Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Can't get traces from ras:aer_event
  Apr 23 15:25:18 awrep3 rasdaemon: ras:aer_event event enabled
  Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Listening to events for cpus 0 to 45
  Apr 23 15:25:18 awrep3 rasdaemon: Can't write to set_event
  Apr 23 15:25:18 awrep3 rasdaemon: ras:aer_event event enabled
  Apr 23 15:25:18 awrep3 rasdaemon: Enabled event ras:aer_event
  Apr 23 15:25:18 awrep3 rasdaemon: Can't write to set_event
  Apr 23 15:25:18 awrep3 rasdaemon: ras:arm_event event enabled
  Apr 23 15:25:18 awrep3 rasdaemon: ras:arm_event event enabled
  Apr 23 15:25:18 awrep3 rasdaemon: Enabled event ras:arm_event
  Apr 23 15:25:18 awrep3 rasdaemon: Can't parse /proc/cpuinfo: missing [vendor_id] [cpu family] [model] [cpu MHz] [flags]
  Apr 23 15:25:18 awrep3 rasdaemon: Can't register mce handler
  Apr 23 15:25:18 awrep3 rasdaemon: Can't get traces from ras:aer_event
  Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Recording mc_event events
  Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Recording aer_event events
  Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Recording extlog_event events
  Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Recording mce_record events
  Apr 23 15:25:19 awrep3 rasdaemon[3369]: rasdaemon: Recording arm_event events

  -- artful --
  ubuntu@awrep3:~$ sudo service rasdaemon status
  ● rasdaemon.service - RAS daemon to log the RAS events
     Loaded: loaded (/lib/systemd/system/rasdaemon.service; enabled; vendor preset
     Active: active (running) since Mon 2018-04-23 15:51:55 UTC; 13s ago
   Main PID: 3683 (rasdaemon)
      Tasks: 1 (limit: 7065)
     Memory: 7.9M
        CPU: 48ms
     CGroup: /system.slice/rasdaemon.service
             └─3683 /usr/sbin/rasdaemon -f -r

  Apr 23 15:51:55 awrep3 rasdaemon[3683]: ras:arm_event event enabled
  Apr 23 15:51:55 awrep3 rasdaemon[3683]: Enabled event ras:arm_event
  Apr 23 15:51:55 awrep3 rasdaemon[3683]: Can't parse /proc/cpuinfo: missing [vend
  Apr 23 15:51:55 awrep3 rasdaemon[3683]: Can't register mce handler
  Apr 23 15:51:55 awrep3 rasdaemon[3683]: Can't get traces from ras:aer_event
  Apr 23 15:51:55 awrep3 rasdaemon[3683]: rasdaemon: Recording mc_event events
  Apr 23 15:51:55 awrep3 rasdaemon[3683]: rasdaemon: Recording aer_event events
  Apr 23 15:51:56 awrep3 rasdaemon[3683]: rasdaemon: Recording extlog_event events
  Apr 23 15:51:56 awrep3 rasdaemon[3683]: rasdaemon: Recording mce_record events
  Apr 23 15:51:56 awrep3 rasdaemon[3683]: rasdaemon: Recording arm_event events

  ubuntu@awrep3:~$ grep rasdaemon /var/log/syslog 
  Apr 23 15:51:55 awrep3 rasdaemon: ras:mc_event event enabled
  Apr 23 15:51:55 awrep3 rasdaemon: Enabled event ras:mc_event
  Apr 23 15:51:55 awrep3 rasdaemon[3683]: rasdaemon: ras:mc_event event enabled
  Apr 23 15:51:55 awrep3 rasdaemon[3683]: rasdaemon: Enabled event ras:mc_event
  Apr 23 15:51:55 awrep3 rasdaemon[3683]: rasdaemon: ras:aer_event event enabled
  Apr 23 15:51:55 awrep3 rasdaemon[3683]: rasdaemon: Enabled event ras:aer_event
  Apr 23 15:51:55 awrep3 rasdaemon: ras:aer_event event enabled
  Apr 23 15:51:55 awrep3 rasdaemon[3684]: rasdaemon: ras:mc_event event enabled
  Apr 23 15:51:55 awrep3 rasdaemon[3684]: rasdaemon: ras:aer_event event enabled
  Apr 23 15:51:55 awrep3 rasdaemon[3684]: rasdaemon: Can't write to set_event
  Apr 23 15:51:55 awrep3 rasdaemon[3684]: rasdaemon: Can't write to set_event
  Apr 23 15:51:55 awrep3 rasdaemon[3684]: rasdaemon: ras:arm_event event enabled
  Apr 23 15:51:55 awrep3 rasdaemon[3683]: rasdaemon: ras:arm_event event enabled
  Apr 23 15:51:55 awrep3 rasdaemon[3683]: rasdaemon: Enabled event ras:arm_event
  Apr 23 15:51:55 awrep3 rasdaemon[3683]: rasdaemon: Can't parse /proc/cpuinfo: missing [vendor_id] [cpu family] [model] [cpu MHz] [flags]
  Apr 23 15:51:55 awrep3 rasdaemon[3683]: rasdaemon: Can't register mce handler
  Apr 23 15:51:55 awrep3 rasdaemon[3683]: rasdaemon: Can't get ras:extlog_mem_event traces. Perhaps this feature is not supported on your system.
  Apr 23 15:51:55 awrep3 rasdaemon[3683]: rasdaemon: Can't get traces from ras:aer_event
  Apr 23 15:51:55 awrep3 rasdaemon[3683]: rasdaemon: Listening to events for cpus 0 to 45
  Apr 23 15:51:55 awrep3 rasdaemon: Enabled event ras:aer_event
  Apr 23 15:51:55 awrep3 rasdaemon: ras:arm_event event enabled
  Apr 23 15:51:55 awrep3 rasdaemon: Enabled event ras:arm_event
  Apr 23 15:51:55 awrep3 rasdaemon: ras:mc_event event enabled
  Apr 23 15:51:55 awrep3 rasdaemon: ras:aer_event event enabled
  Apr 23 15:51:55 awrep3 rasdaemon: Can't write to set_event
  Apr 23 15:51:55 awrep3 rasdaemon: Can't write to set_event
  Apr 23 15:51:55 awrep3 rasdaemon: Can't parse /proc/cpuinfo: missing [vendor_id] [cpu family] [model] [cpu MHz] [flags]
  Apr 23 15:51:55 awrep3 rasdaemon: Can't register mce handler
  Apr 23 15:51:55 awrep3 rasdaemon: Can't get traces from ras:aer_event
  Apr 23 15:51:55 awrep3 rasdaemon: ras:arm_event event enabled
  Apr 23 15:51:55 awrep3 rasdaemon[3683]: rasdaemon: Recording mc_event events
  Apr 23 15:51:55 awrep3 rasdaemon[3683]: rasdaemon: Recording aer_event events
  Apr 23 15:51:56 awrep3 rasdaemon[3683]: rasdaemon: Recording extlog_event events
  Apr 23 15:51:56 awrep3 rasdaemon[3683]: rasdaemon: Recording mce_record events
  Apr 23 15:51:56 awrep3 rasdaemon[3683]: rasdaemon: Recording arm_event events

  -- xenial --
  ubuntu@awrep3:~$ sudo service rasdaemon status
  sudo: unable to resolve host awrep3
  ● rasdaemon.service - RAS daemon to log the RAS events
     Loaded: loaded (/lib/systemd/system/rasdaemon.service; enabled; vendor preset
     Active: active (running) since Mon 2018-04-23 16:05:09 UTC; 13s ago
   Main PID: 4624 (rasdaemon)
      Tasks: 1
     Memory: 8.0M
        CPU: 49ms
     CGroup: /system.slice/rasdaemon.service
             └─4624 /usr/sbin/rasdaemon -f -r

  Apr 23 16:05:09 awrep3 rasdaemon[4624]: ras:arm_event event enabled
  Apr 23 16:05:09 awrep3 rasdaemon[4624]: Enabled event ras:arm_event
  Apr 23 16:05:09 awrep3 rasdaemon[4624]: Can't parse /proc/cpuinfo: missing [vend
  Apr 23 16:05:09 awrep3 rasdaemon[4624]: Can't register mce handler
  Apr 23 16:05:09 awrep3 rasdaemon[4624]: Can't get traces from ras:aer_event
  Apr 23 16:05:09 awrep3 rasdaemon[4624]: rasdaemon: Recording mc_event events
  Apr 23 16:05:09 awrep3 rasdaemon[4624]: rasdaemon: Recording aer_event events
  Apr 23 16:05:09 awrep3 rasdaemon[4624]: rasdaemon: Recording extlog_event events
  Apr 23 16:05:09 awrep3 rasdaemon[4624]: rasdaemon: Recording mce_record events
  Apr 23 16:05:10 awrep3 rasdaemon[4624]: rasdaemon: Recording arm_event events

  ubuntu@awrep3:~$ grep rasdaemon /var/log/syslog 
  Apr 23 16:05:09 awrep3 rasdaemon: ras:mc_event event enabled
  Apr 23 16:05:09 awrep3 rasdaemon: ras:mc_event event enabled
  Apr 23 16:05:09 awrep3 rasdaemon[4624]: rasdaemon: ras:mc_event event enabled
  Apr 23 16:05:09 awrep3 rasdaemon[4624]: rasdaemon: Enabled event ras:mc_event
  Apr 23 16:05:09 awrep3 rasdaemon[4625]: rasdaemon: ras:mc_event event enabled
  Apr 23 16:05:09 awrep3 rasdaemon[4625]: rasdaemon: ras:aer_event event enabled
  Apr 23 16:05:09 awrep3 rasdaemon[4625]: rasdaemon: Can't write to set_event
  Apr 23 16:05:09 awrep3 rasdaemon[4625]: rasdaemon: Can't write to set_event
  Apr 23 16:05:09 awrep3 rasdaemon[4625]: rasdaemon: ras:arm_event event enabled
  Apr 23 16:05:09 awrep3 rasdaemon: Enabled event ras:mc_event
  Apr 23 16:05:09 awrep3 rasdaemon[4624]: rasdaemon: ras:aer_event event enabled
  Apr 23 16:05:09 awrep3 rasdaemon[4624]: rasdaemon: Enabled event ras:aer_event
  Apr 23 16:05:09 awrep3 rasdaemon[4624]: rasdaemon: ras:arm_event event enabled
  Apr 23 16:05:09 awrep3 rasdaemon[4624]: rasdaemon: Enabled event ras:arm_event
  Apr 23 16:05:09 awrep3 rasdaemon[4624]: rasdaemon: Can't parse /proc/cpuinfo: missing [vendor_id] [cpu family] [model] [cpu MHz] [flags]
  Apr 23 16:05:09 awrep3 rasdaemon[4624]: rasdaemon: Can't register mce handler
  Apr 23 16:05:09 awrep3 rasdaemon[4624]: rasdaemon: Can't get ras:extlog_mem_event traces. Perhaps this feature is not supported on your system.
  Apr 23 16:05:09 awrep3 rasdaemon[4624]: rasdaemon: Can't get traces from ras:aer_event
  Apr 23 16:05:09 awrep3 rasdaemon[4624]: rasdaemon: Listening to events for cpus 0 to 45
  Apr 23 16:05:09 awrep3 rasdaemon: ras:aer_event event enabled
  Apr 23 16:05:09 awrep3 rasdaemon: Can't write to set_event
  Apr 23 16:05:09 awrep3 rasdaemon: Can't write to set_event
  Apr 23 16:05:09 awrep3 rasdaemon: ras:aer_event event enabled
  Apr 23 16:05:09 awrep3 rasdaemon: Enabled event ras:aer_event
  Apr 23 16:05:09 awrep3 rasdaemon: ras:arm_event event enabled
  Apr 23 16:05:09 awrep3 rasdaemon: ras:arm_event event enabled
  Apr 23 16:05:09 awrep3 rasdaemon: Enabled event ras:arm_event
  Apr 23 16:05:09 awrep3 rasdaemon: Can't parse /proc/cpuinfo: missing [vendor_id] [cpu family] [model] [cpu MHz] [flags]
  Apr 23 16:05:09 awrep3 rasdaemon: Can't register mce handler
  Apr 23 16:05:09 awrep3 rasdaemon: Can't get traces from ras:aer_event
  Apr 23 16:05:09 awrep3 rasdaemon[4624]: rasdaemon: Recording mc_event events
  Apr 23 16:05:09 awrep3 rasdaemon[4624]: rasdaemon: Recording aer_event events
  Apr 23 16:05:09 awrep3 rasdaemon[4624]: rasdaemon: Recording extlog_event events
  Apr 23 16:05:09 awrep3 rasdaemon[4624]: rasdaemon: Recording mce_record events
  Apr 23 16:05:10 awrep3 rasdaemon[4624]: rasdaemon: Recording arm_event events

  [Regression Potential]
  This option is enabled only for target ARM64 in debian/rules.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rasdaemon/+bug/1769182/+subscriptions
  Thread Previous • Date Previous • • Thread Next