** Changed in: freeipmi (Debian)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1699933
Title:
ipmi-locate crash on arm64
To manage notifications about this
This bug was fixed in the package freeipmi - 1.4.11-1.1ubuntu4~0.16.04
---
freeipmi (1.4.11-1.1ubuntu4~0.16.04) xenial; urgency=medium
* Backport to xenial
Use kernel DMI table interface, when available, instead of trolling
/dev/mem to avoid a crash on ARM. LP: #1699933.
-
This bug was fixed in the package freeipmi - 1.4.11-1.1ubuntu4~0.17.04
---
freeipmi (1.4.11-1.1ubuntu4~0.17.04) zesty; urgency=medium
* Backport to zesty
Use kernel DMI table interface, when available, instead of trolling
/dev/mem to avoid a crash on ARM. LP: #1699933.
--
On zesty ipmi-locate works well as expected. Actually in zesty and
xenial are same source.
ubuntu@zesty:~$ sudo ipmi-locate
Probing KCS device using DMIDECODE... done
IPMI Version: 2.0
IPMI locate driver: DMIDECODE
IPMI interface: KCS
BMC driver device:
BMC I/O base address: 0xCA2
Register spacin
This bug was fixed in the package freeipmi - 1.4.11-1.1ubuntu4~0.16.10
---
freeipmi (1.4.11-1.1ubuntu4~0.16.10) yakkety; urgency=medium
* Backport to yakkety
Use kernel DMI table interface, when available, instead of trolling
/dev/mem to avoid a crash on ARM. LP: #1699933.
With regards to comment #13 and testing that the update still works on
non-arm64 systems - I don't see any indication of this testing happening
for zesty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
[ + Andres, for MAAS ]
On Thu, Jul 20, 2017 at 9:40 AM, Robie Basak <1699...@bugs.launchpad.net> wrote:
> FTR, Dann asked me about what I was looking for. I said I wanted testing
> of some representative sample of hardware in the wild. I'm open to
> suggestions on what that might mean, but I sugge
FTR, Dann asked me about what I was looking for. I said I wanted testing
of some representative sample of hardware in the wild. I'm open to
suggestions on what that might mean, but I suggested testing against a
couple of different manufacturers' BMCs, for example Dell and HP. Dann
will ask the MAAS
> Dann
Sorry, I mean dann :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1699933
Title:
ipmi-locate crash on arm64
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu
Same here. On x86 server, freeipmi-tools in -update and -proposed has
the same output
xenial-proposed
ikepanhc@keiko:~$ sudo ipmi-locate
Probing KCS device using DMIDECODE... done
IPMI Version: 2.0
IPMI locate driver: DMIDECODE
IPMI interface: KCS
BMC driver device:
BMC I/O base address: 0xCA2
Re
I verified this on an x86 server by testing that the output is the same
before and after the update (see below). I also gave a heads-up to the
MAAS team to consider adding this to their CI (see:
https://bugs.launchpad.net/maas-images/+bug/1702976/comments/11), though
I don't know if that occurred.
And presumably this testing should take place on more than just arm64 as
well?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1699933
Title:
ipmi-locate crash on arm64
To manage notifications about
Thank you for your comprehensive verification report.
Has there been any testing performed to verify that ipmi-locate still
works correctly now that its data source has been changed? I think we
need to do at least some level of testing of this before it's safe to
recommend this update to users.
-
ubuntu@d05-4:~$ sudo ipmi-locate
[71285.659835] pgd = 801fbe0b3000
[71285.663245] [93687c36] *pgd=001fd16f6003, *pud=001fbecab003,
*pmd=001fbed7f003, *pte=016039860fc3
Bus error (core dumped)
ubuntu@d05-4:~$ dpkg --list | grep freeipmi-tools
ii freeipmi-tools
ubuntu@d05-4:~$ sudo ipmi-locate
[70950.778753] pgd = 8417cbcae000
[70950.782162] [8b8f0c36] *pgd=0417bf0e9003, *pud=0417bf959003,
*pmd=0417bf5fa003, *pte=016039860fc3
Bus error (core dumped)
ubuntu@d05-4:~$ dpkg --list | grep freeipmi-tools
ii freeipmi-tools
ubuntu@d05-4:~$ sudo ipmi-locate
[68526.721538] pgd = 801fcbfbb000
[68526.724948] [a5ce0c36] *pgd=001fd272c003, *pud=001fc3da0003,
*pmd=001fd2851003, *pte=016039860fc3
Bus error (core dumped)
ubuntu@d05-4:~$ dpkg --list | grep freeipmi-tools
ii freeipmi-tools
Hello Ike, or anyone else affected,
Accepted freeipmi into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/freeipmi/1.4.11-1.1ubuntu4~0.16.04
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Changed in: freeipmi (Ubuntu Zesty)
Status: Triaged => In Progress
** Changed in: freeipmi (Ubuntu Yakkety)
Status: Triaged => In Progress
** Changed in: freeipmi (Ubuntu Xenial)
Status: Triaged => In Progress
--
You received this bug notification because you are a membe
This bug was fixed in the package freeipmi - 1.4.11-1.1ubuntu4
---
freeipmi (1.4.11-1.1ubuntu4) artful; urgency=medium
* Use kernel DMI table interface, when available, instead of trolling
/dev/mem to avoid a crash on ARM. LP: #1699933.
-- dann frazier Wed, 28 Jun 2017 13:26
** Description changed:
+ [Impact]
+
+ * Read from /dev/mem and scan DMI tables is dangerous, if /dev/mem is
+ not stable to read, it will cause ipmi-locate crash.
+
+ [Test Case]
+
+ * `sudo ipmi-locate` shall not crash
+
+ [Regression Potential]
+
+ * Reading from DMI tables is sysfs is
** Changed in: freeipmi (Ubuntu Xenial)
Assignee: (unassigned) => Ike Panhc (ikepanhc)
** Changed in: freeipmi (Ubuntu Yakkety)
Assignee: (unassigned) => Ike Panhc (ikepanhc)
** Changed in: freeipmi (Ubuntu Zesty)
Assignee: (unassigned) => Ike Panhc (ikepanhc)
** Changed in: freei
** Changed in: freeipmi (Debian)
Status: Unknown => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1699933
Title:
ipmi-locate crash on arm64
To manage notifications about this bug g
** Bug watch added: Debian Bug tracker #800038
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800038
** Also affects: freeipmi (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800038
Importance: Unknown
Status: Unknown
--
You received this bug notification because
http://lists.gnu.org/archive/html/freeipmi-devel/2017-06/msg1.html
Patch reviewed and get positive feedback
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1699933
Title:
ipmi-locate crash on arm
http://lists.gnu.org/archive/html/freeipmi-devel/2017-06/msg0.html
Patch on upstream mailing list
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1699933
Title:
ipmi-locate crash on arm64
To man
@paelzer,
Yes, I have a fix already and plan to propose to upstream for feedback.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1699933
Title:
ipmi-locate crash on arm64
To manage notifications ab
Thanks Ike for the report, you also assigned yourself so I wanted to ask
- are you going ahead and work on a fix that you'll report here?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1699933
Title:
** Also affects: freeipmi (Ubuntu Artful)
Importance: Undecided
Assignee: Ike Panhc (ikepanhc)
Status: New
** Also affects: freeipmi (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: freeipmi (Ubuntu Yakkety)
Importance: Undecided
Status: New
*
28 matches
Mail list logo