Table of Contents
Bugs
How to report a bug that affects Linux on Alpha, and where to find the Alpha-specific bugs already open in each project's tracker. Problems that span several projects are tracked in alphalinux/issues.
How to report a bug
The right place for a report depends on where the bug is. If it is unclear which component is at fault, ask on linux-alpha@vger.kernel.org or the distribution's Alpha list first.
| Bug in | Report to |
|---|---|
| The kernel | linux-alpha@vger.kernel.org, with the Alpha maintainers on Cc. See Kernel: Reporting bugs |
| GCC | GCC Bugzilla, with the target set to alpha-linux-gnu |
| glibc, binutils | Sourceware Bugzilla, with the host set to the output of gcc -dumpmachine, such as alpha-unknown-linux-gnu |
| A Gentoo package | Gentoo Bugzilla, with alpha@gentoo.org on Cc |
| A Debian package | The Debian bug tracking system, with reportbug. Add the user tag with User: debian-alpha@lists.debian.org and Usertags: alpha pseudo-headers, and send a copy to the debian-alpha list with X-Debbugs-Cc |
| A T2 SDE package | The T2 SDE issue tracker on GitHub, linked from t2sde.org |
| QEMU's Alpha emulation | The QEMU issue tracker. Include the full command line and QEMU version |
| Other software | The software's own tracker |
A useful report says which system and processor the bug happens on, with the output of uname -a and the CPU from /proc/cpuinfo, since behavior can differ between an EV56 and an EV67 system, and whether it also happens under QEMU. For a crash, the kernel log, and for a failed build, the full build log. Some common symptoms have well-known causes; see the FAQ for "unaligned trap" messages, "Illegal instruction", and "relocation truncated to fit".