Eric,
I am still seeing the same errors (yet in a different order) on a completely clean default full installation.
Here is what I'm seeing:
Boot up in run level 3, the tail of dmesg:
[ 10.246136] EXT4-fs (sda7): re-mounted. Opts: (null)
[ 10.353347] EXT4-fs (sda7): re-mounted. Opts: (null)
[ 10.728691] lp0: using parport0 (interrupt-driven).
[ 10.730784] lp0: console ready
[ 15.155692] eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
[ 26.374991] cx18-0: Failed to initialize on vbi0
[ 26.383401] cx18-0: Failed to initialize on video0
[ 26.389967] cx18-0: Failed to initialize on video24
[ 26.393303] cx18-0: Failed to initialize on video32
Please ignore the messages about the cx18, as that simply means that I don't have the firmatware installed for my tv tuner, which as I said, this is a default full installation.
Now, as root I issue 'telinit 4' and here is the tail of dmesg:
[ 10.246136] EXT4-fs (sda7): re-mounted. Opts: (null)
[ 10.353347] EXT4-fs (sda7): re-mounted. Opts: (null)
[ 10.728691] lp0: using parport0 (interrupt-driven).
[ 10.730784] lp0: console ready
[ 15.155692] eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
[ 26.374991] cx18-0: Failed to initialize on vbi0
[ 26.383401] cx18-0: Failed to initialize on video0
[ 26.389967] cx18-0: Failed to initialize on video24
[ 26.393303] cx18-0: Failed to initialize on video32
So no errors yet.
Here is tail of dmesg after using logs into kdm and launches kde 4.6.5 without only the files in their home issued by Slackware's /etc/skeleton files:
[ 10.246136] EXT4-fs (sda7): re-mounted. Opts: (null)
[ 10.353347] EXT4-fs (sda7): re-mounted. Opts: (null)
[ 10.728691] lp0: using parport0 (interrupt-driven).
[ 10.730784] lp0: console ready
[ 15.155692] eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
[ 26.374991] cx18-0: Failed to initialize on vbi0
[ 26.383401] cx18-0: Failed to initialize on video0
[ 26.389967] cx18-0: Failed to initialize on video24
[ 26.393303] cx18-0: Failed to initialize on video32
[ 169.652832] ata1.00: configured for UDMA/133
[ 169.652843] ata1: EH complete
[ 170.133156] EXT4-fs (sda7): re-mounted. Opts: commit=0
[ 187.565128] NET: Registered protocol family 10
[ 187.565555] lo: Disabled Privacy Extensions
[ 198.346019] eth0: no IPv6 routers present
You'll notice that libata is issuing a error code for the hard drive, and resets the drive.
Now the tail of dmesg on logout:
[ 10.246136] EXT4-fs (sda7): re-mounted. Opts: (null)
[ 10.353347] EXT4-fs (sda7): re-mounted. Opts: (null)
[ 10.728691] lp0: using parport0 (interrupt-driven).
[ 10.730784] lp0: console ready
[ 15.155692] eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
[ 26.374991] cx18-0: Failed to initialize on vbi0
[ 26.383401] cx18-0: Failed to initialize on video0
[ 26.389967] cx18-0: Failed to initialize on video24
[ 26.393303] cx18-0: Failed to initialize on video32
[ 169.652832] ata1.00: configured for UDMA/133
[ 169.652843] ata1: EH complete
[ 170.133156] EXT4-fs (sda7): re-mounted. Opts: commit=0
[ 187.565128] NET: Registered protocol family 10
[ 187.565555] lo: Disabled Privacy Extensions
[ 198.346019] eth0: no IPv6 routers present
[ 300.232473] akonadi_agent_l[2478]: segfault at b485eaf8 ip b70b74e2 sp bfc39ce0 error 4 in libQtGui.so.4.7.0[b6d30000+a80000]
[ 302.343905] akonadi_agent_l[2569]: segfault at 0 ip b6bee360 sp bf86ded0 error 4 in libQtCore.so.4.7.0[b6a6f000+293000]
Here akonadi segfaults.
So it appears that this version of KDE still is whacking my hard drive and, instead of segfaulting at the initial login to KDE, now it segfaults on the exit of KDE
Perhaps I need to move up to Slackware current and see if the newer 4.7.X series of KDE will fix this for me or not.
This computer I tested on is a relatively new hard drive, 2 terbytes in size and smartctl is reporting no issues on the drive at all.
And like I had said previously, I see the libata/reinitiliazing on a few other Slack boxes as well. So I don't suspect it's my hardware. On my netbook, that hard drive is reinitialized/erroring every time we even resume from suspend to disk. But the computer feels flawless, and Slackware sleep/hibernates perfectly IMO, except this matter (which maybe is libata?? or KDE ??) I can't explain it.
Perhaps when I get some time over the next few days I'll give it a go at --current and see how that goes.
Other than that, I must say that despite the hard drive matter, this kde 4.6 is very nice, and may of the fixes that they did are very welcome here for sure
Thanks again for you help.
Fogie