openwrt / openwrt/packages

nss-utils: Illegal instruction on i386

Open
#21,988 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Makefile
Stars
4.6k
Forks
4k
Avg merge
3d 12h
Merged PRs (30d)
134

Description

Maintainer: @lucize
Environment: (Geode(TM) Integrated Processor by AMD PCS, Alix Board, OpenWrt 22.03.05 and 23.05.0-rc3)

Description:

I believe it is related to compilation options of nss-utils package (and those it depends on).

Steps to reproduce:

Board: Alix Board
CPU: Geode(TM) Integrated Processor by AMD PCS (family: 0x5, model: 0xa, stepping: 0x2)
OpenWRT: 22.03.05
Package: nss-utils

    mkdir ${HOME}/temp
    certutil -N -d sql:${HOME}/temp
    certutil -S -x -n "Router CA" -s "O=Router,CN=Router CA" -k rsa -g 4096 -v 12 -d sql:${HOME}/temp -t "CT,," -2

During CA generation it will generate Illegal instruction with following lines in dmesg:

traps: certutil[8135] trap invalid opcode ip:b7b2c5a4 sp:bf8e49d0 error:0 in libfreebl3.so[b7acb000+62000]

P.S. I posted it at forum already but I also submit it here in order respect formalities - https://forum.openwrt.org/t/nss-utils-i386-illegal-instruction

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the nss-utils package definition and its compilation options, then inspect the dependencies providing certutil and libfreebl3.so. Reproduce the listed certutil commands on the Geode i386 environment and identify which build setting causes the invalid opcode; done means CA generation completes without an illegal-instruction trap on the affected board.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, linux
Domain
build-system, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.