| Summary: | patch for sys-apps/smartmontools-5.37 for SATA disks | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Wolfram Schlich (RETIRED) <wschlich> |
| Component: | Current packages | Assignee: | Gentoo's Team for Core System packages <base-system> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | http://www.mail-archive.com/debian-bugs-closed@lists.debian.org/msg147665.html | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
nuts to debian bug tracking when the issue is upstream can you confirm the upstream change mentioned resolves the issue ? http://smartmontools.cvs.sourceforge.net/smartmontools/sm5/os_linux.cpp?r1=1.94&r2=1.95&view=patch (In reply to comment #1) > > can you confirm the upstream change mentioned resolves the issue ? > http://smartmontools.cvs.sourceforge.net/smartmontools/sm5/os_linux.cpp?r1=1.94&r2=1.95&view=patch No, haven't tried it yet. Also, looking at http://smartmontools.cvs.sourceforge.net/smartmontools/sm5/CHANGELOG?view=markup it might be a good idea to incorporate more of those not-yet-released changes into a patchset to ship with our 5.37 package.... i dont really want to go cherry picking what i cant test (In reply to comment #3) > i dont really want to go cherry picking what i cant test I will be able to test (all) that soon... Upstream has released 5.38 which is already in the tree. |
The kernel resets SATA ports when smartd/smartctl tries to enable attribute autosaving and automatic offline testing: --8<-- ata9.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata9.00: (BMDMA stat 0x4) ata9.00: cmd 35/00:d8:74:47:14/00:02:03:00:00/e0 tag 0 cdb 0x0 data 372736 out res 51/84:00:74:47:14/84:00:03:00:00/e0 Emask 0x10 (ATA bus error) ata9: soft resetting port ata9.00: configured for UDMA/100 ata9.01: configured for UDMA/100 ata9: EH complete ata9.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata9.00: (BMDMA stat 0x4) ata9.00: cmd 35/00:d8:74:47:14/00:02:03:00:00/e0 tag 0 cdb 0x0 data 372736 out res 51/84:00:74:47:14/84:00:03:00:00/e0 Emask 0x10 (ATA bus error) ata9: soft resetting port ata9.00: configured for UDMA/100 ata9.01: configured for UDMA/100 ata9: EH complete ata9.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata9.00: (BMDMA stat 0x4) ata9.00: cmd 35/00:d8:74:47:14/00:02:03:00:00/e0 tag 0 cdb 0x0 data 372736 out res 51/84:00:74:47:14/84:00:03:00:00/e0 Emask 0x10 (ATA bus error) ata9: soft resetting port ata9.00: configured for UDMA/100 ata9.01: configured for UDMA/100 ata9: EH complete ata9.00: limiting speed to UDMA/66:PIO4 ata9.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata9.00: (BMDMA stat 0x4) ata9.00: cmd 35/00:d8:74:47:14/00:02:03:00:00/e0 tag 0 cdb 0x0 data 372736 out res 51/84:00:74:47:14/84:00:03:00:00/e0 Emask 0x10 (ATA bus error) ata9: soft resetting port ata9.00: configured for UDMA/66 ata9.01: configured for UDMA/100 ata9: EH complete --8<-- The patch mentioned there will fix it...