[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Endless modprobe calls logged in KDE 3.4
From:       Gábor_Lehel <illissius () gmail ! com>
Date:       2005-01-30 12:32:13
Message-ID: 9cfeadb80501300432221b70e2 () mail ! gmail ! com
[Download RAW message or body]

Yes, I also had an issue where if I inserted a CD with the media
manager kded module enabled, it would completely lock up the disk and
constantly access it for... well, longer than I was willing to wait. I
also spent a few hours trying to figure out wtf was causing my disk
access light to flash every half second, and turns out it was the same
thing...
Just confirming the thus far reported.


On Sun, 30 Jan 2005 00:44:00 +0100, David Faure <faure@kde.org> wrote:
> On Saturday 29 January 2005 19:24, David Jarvie wrote:
> > When I run KDE 3.4 (CVS 25/1/05), it outputs the following line
> > to /var/log/ksymoops, every second approximately. This occurs indefinitely,
> > throughout my session until I log off.
> >
> >     start /sbin/modprobe -s -k -- block-major-11 safemode=1
> >
> > This doesn't happen under KDE 3.3.2. Note that I copied my $KDEHOME branch for
> > use with KDE 3.4, so that all my config options would be kept, so there
> > should be nothing different, other than that I have only installed kdelibs,
> > kdebase and kdepim under KDE 3.4.
> 
> I suspect it's actually twice per second, and it's the polling done by the new
> "mediamanager" KDED module (it's new, this is why you're not seeing this in 3.3.x).
> I'm seeing problems with that modules too - even worse ones:
> 
> On startup kded loads all modules from newInstance(), and for some reason the
> LinuxCDPolling thread of the mediamanager module takes a VERY long time
> before the main thread can return from newInstance. I mean VERY. KDE startup
> is blocked for about 10 minutes here (on the laptop). If I kill X with Ctrl-Alt-Backspace
> and restart it, it then works for some reason. I suspect a deadlock somewhere?
> Not sure exactly what happens, but the whole of kded is definitely blocked
> (even the parent kded process which forked and calls newInstance()...) during
> all that time.
> 
> I think this polling thread is also why the "harddisk" led of the laptop lightens
> up twice per second - which btw is said to reduce the harddisk's life....
> 
> Kevin: do we really need this cd-polling thread? :/
> 
> --
> David Faure, faure@kde.org, sponsored by Trolltech to work on KDE,
> Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).
> 
> >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
> 


-- 
Work is punishment for failing to procrastinate effectively.
Mailing lists: illissius@gmail.com, everything else: illissius@elitemail.org
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]