Bug 105048 - [trm] trm(4) panics on sparc64
Summary: [trm] trm(4) panics on sparc64
Status: Closed Overcome By Events
Alias: None
Product: Base System
Classification: Unclassified
Component: sparc64 (show other bugs)
Version: 6.1-RELEASE
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-sparc64 (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-11-01 21:00 UTC by Stéphane Witzmann
Modified: 2020-07-11 18:16 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stéphane Witzmann 2006-11-01 21:00:41 UTC
trm(4) is not in GENERIC. Loading it causes a panic on my Ultra 10:

# kldload trm
trm0: <Tekram DC395U/UW/F DC315/U Fast20 Wide SCSI Adapter> port 0x400-0x4ff mem 0x2000-0x2fff at device 1.0 on pci2
panic: trap: data access error


The same thing happens if trm.ko is loaded at boot time.
Comment 1 Stéphane Witzmann 2006-11-01 21:23:56 UTC
I booted a quite recent 7.0 snapshot. Same panic. Details follow:

db> bt
(...)
-- data access error %o7=0xc0b8552c
NVRAM_trm_wait_30us() at NVRAM_trm_wait_30us+0x4c
trm_attach() at trm_attach+0x548
device_attach() at device_attach+0x0x60
(...)


NetBSD 3.0.1/sparc64 successfully attaches the card and its associated
CDROM drive, so this is definitely not a hardware problem.
Comment 2 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 07:59:54 UTC
For bugs matching the following criteria:

Status: In Progress Changed: (is less than) 2014-06-01

Reset to default assignee and clear in-progress tags.

Mail being skipped
Comment 3 Mark Johnston freebsd_committer freebsd_triage 2020-07-11 18:16:28 UTC
I'm sorry that this PR never got any attention.  sparc64 platform support has since been removed from FreeBSD, along with trm(4), so I don't think this is going to get fixed, unless it was incidentally addressed sometime after this PR was submitted.