David Liontooth <[EMAIL PROTECTED]> writes:
> Ron Johnson wrote:
>
>>On Fri, 2004-12-10 at 11:45 -0800, David Liontooth wrote:
>>
>>
>>>Goswin von Brederlow wrote:
>>>
>>>
>>>
>>>>Same time the official sarge will be released (+ a day or two) the
>>>>unofficial sarge amd64 should be finished.
>>>>
>>>>
>>>>
>>>>
>>>Hey, that's great news! (News to me anyway.)
>>>Aside from hankering after sarge, I've found sid to be rock
>>>solid at this end (aside from ud and xprt, which segfault).
>>>
>>>
>>
>>ud?
>>
>>
>>
> uptime daemon -- crashes on startup:
>
> dmesg-2.6.9-ac6-5-FX5500: ud[1921]: segfault at 00000000958a7d00 rip
> 0000002a956e9980 rsp 0000007fbffff048 error 4
> dmesg-2.6.9-ac6-5-riva: ud[1788]: segfault at 00000000958a7d00 rip
> 0000002a956e9980 rsp 0000007fbffff048 error 4
> dmesg-2.6.9-ac6-5-snd-bt87x:ud[1948]: segfault at 00000000958a7d00 rip
> 0000002a956e9980 rsp 0000007fbffff048 error 4
> dmesg-2.6.9-ac6-6-ACPI: ud[3858]: segfault at 00000000958a7d00 rip
> 0000002a956e9980 rsp 0000007fbffff058 error 4
> dmesg-2.6.9-rc2: ud[1625]: segfault at 000000009589ffc0 rip
> 0000002a956e3790 rsp 0000007fbffff068 error 4
> dmesg-2.6.9-rc2-02-promise: ud[1834]: segfault at 000000009589ffc0 rip
> 0000002a956e3790 rsp 0000007fbffff068 error 4
> dmesg-2.6.9-rc2-acpi: ud[1891]: segfault at 000000009589ffc0 rip
> 0000002a956e3790 rsp 0000007fbffff068 error 4
> dmesg-2.6.9-rc2-afterXP: ud[1766]: segfault at 000000009589ffc0 rip
> 0000002a956e3790 rsp 0000007fbffff068 error 4
> dmesg-2.6.9-rc2-no-acpi: ud[1875]: segfault at 000000009589ffc0 rip
> 0000002a956e3790 rsp 0000007fbffff068 error 4
>
> Not exactly crucial. The uptime command works fine.
>
> Dave
That looks more like unaligned access. Unlike other architecture this
seems to get reported as segfault instead of unaligned access.
Or is uptimed realy stoping to run?
MfG
Goswin
