Prev: SlackE17 for Slackware 12.1
Next: Kmail Error:could not start process pop3
From: Stephen Bloom on 6 May 2008 22:13
I have largely lurked here for a number of years, but
I now have a truly vexing problem. I have a Dell D820 laptop
that I have been running (with pretty good success) with
Slack-current right up to the last change (12.1 RC-4). I rebuilt
the kernel with the tuxonice-3.0 patches and things appeared to
be working well -- until I tried a test hibernation. Boom.

After the smoke cleared, I now have a situation where ldconfig
always segfaults. I have the 12.1 iso's, and did a complete
reinstall, using the default slack kernels, and I *still* get
ldconfig with segfaults. Memtest doesn't appear to indicate
any memory issues. Tuxonice was set up to use swap - so far I
haven't found any identifiable issues with swap (using fdisk).

So - anyone out there run into anything remotely like this? I'm
currently out of ideas of how to diagnose further this debacle.
The only other step I see right now is to reformat all the linux
partitions and restart from the ground up.

Steve
From: Chris Sorenson on 7 May 2008 00:49
Stephen Bloom wrote:
> I have largely lurked here for a number of years, but
> I now have a truly vexing problem. I have a Dell D820 laptop
> that I have been running (with pretty good success) with
> Slack-current right up to the last change (12.1 RC-4). I rebuilt
> the kernel with the tuxonice-3.0 patches and things appeared to
> be working well -- until I tried a test hibernation. Boom.
>
> After the smoke cleared, I now have a situation where ldconfig
> always segfaults. I have the 12.1 iso's, and did a complete
> reinstall, using the default slack kernels, and I *still* get
> ldconfig with segfaults. Memtest doesn't appear to indicate
> any memory issues. Tuxonice was set up to use swap - so far I
> haven't found any identifiable issues with swap (using fdisk).
>
> So - anyone out there run into anything remotely like this? I'm
> currently out of ideas of how to diagnose further this debacle.
> The only other step I see right now is to reformat all the linux
> partitions and restart from the ground up.
>

You could try compiling ldconfig yourself, passing -g to the compiler
(to include all the debugging symbols), and then run it in the debugger
to find out exactly where it's crashing...
From: No_One on 7 May 2008 01:01
On 2008-05-07, Stephen Bloom <sbloom(a)beast.toad.net> wrote:
> I have largely lurked here for a number of years, but
> I now have a truly vexing problem. I have a Dell D820 laptop
> that I have been running (with pretty good success) with
> Slack-current right up to the last change (12.1 RC-4). I rebuilt
> the kernel with the tuxonice-3.0 patches and things appeared to
> be working well -- until I tried a test hibernation. Boom.
>
> After the smoke cleared, I now have a situation where ldconfig
> always segfaults. I have the 12.1 iso's, and did a complete
> reinstall, using the default slack kernels, and I *still* get
> ldconfig with segfaults. Memtest doesn't appear to indicate
> any memory issues. Tuxonice was set up to use swap - so far I
> haven't found any identifiable issues with swap (using fdisk).
>
> So - anyone out there run into anything remotely like this? I'm
> currently out of ideas of how to diagnose further this debacle.
> The only other step I see right now is to reformat all the linux
> partitions and restart from the ground up.
>
> Steve

If I understand, you downloaded the 12.1 iso's and that's when the problem
appeared???

If so, just some ideas....

did you check the m5d numbers
run stat /sbin/ldconfig - see if you get any results
are you running reiserfs, did you check for lost blocks
any messages in system logs
after it chokes, did you run dmesg and look for kernel messages

ken

 | 
Pages: 1
Prev: SlackE17 for Slackware 12.1
Next: Kmail Error:could not start process pop3