No. This was during a maintenance update of a running Lucid (10.04)
system. autofs5 had been running on the affected machines for months.
The previous version of autofs was 5.0.4-3.1ubuntu5. (Without the .1 at
the end)
There were no magic done prior to the update. Just a normal, apt-get
update
No. This was during a maintenance update of a running Lucid (10.04)
system. autofs5 had been running on the affected machines for months.
The previous version of autofs was 5.0.4-3.1ubuntu5. (Without the .1 at
the end)
There were no magic done prior to the update. Just a normal, apt-get
update
Public bug reported:
Binary package hint: autofs5
upon upgrading autofs5, to version 5.0.4-3.1ubuntu5.1, the system complained
about non existing directories in
/usr/share/autofs5/conffiles.
Since /usr/share is a good candidate for automounting, and is indeed
automounted and shared between all
Here is another JMicron-chip that gives the symtoms listed above and
which are fixed by disabling devicekit-disks:
Bus 001 Device 005: ID 152d:2338 JMicron Technology Corp. / JMicron USA
Technology Corp. JM20337 Hi-Speed USB to SATA PATA Combo Bridge
Additionally it seems to fix the similar
Seems I was a bit too trigger-happy about the Alcor chip. More testing
shows that it's still causing resets, so it's probably another bug. The
JMicron is still positive.
-- K
--
JMicron drive 152d:2329 and 1523:2339 cause USB resets on ATA smart probing
https://bugs.launchpad.net/bugs/387161
