[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:       Volker Krause <volker.krause () rwth-aachen ! de>
Date:       2005-02-01 19:45:26
Message-ID: 200502012045.29381.volker.krause () rwth-aachen ! de
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Tuesday 01 February 2005 18:53, Kévin Ottens wrote:
> Le Mardi 1 Février 2005 12:24, Volker Krause a écrit :
> > I have two other machines here running CVS HEAD without problems, only my
> > laptop signals permanent cdrom activity.
>
> I'm wondering if the machines where mediamanager is problematic have
> something in common...
>
> Since you have two where it works correctly, I'd be interested in more
> input... Do they run the same Linux flavor? Do they have something
> different in their fstab? Do they use supermount or something similar?

Here are relevant information about the machine that crashs:
SuSE 9.1, x86, Kernel 2.6.6 + packet writing patch
CD-ROM + DVD writer on secondary IDE channel, no supermount or similar
vkrause@vkpc2:~> cat /etc/fstab
/dev/hdb2            /                    ext3       defaults              1 1
/dev/hda6            /data1               auto       noauto,user           0 0
/dev/hda8            /data2               auto       noauto,user           0 0
/dev/hda1            /windows/C       vfat      users,gid=users,umask=0002 0 0
/dev/hda5            /windows/E       vfat      users,gid=users,umask=0002 0 0
/dev/hda6            /mnt/hda6            ext2       auto                  0 0
/dev/hda7            swap                 swap       pri=42                0 0
/dev/hda8            /mnt/hda8            ext2       auto                  0 0
/dev/hdb1            swap                 swap       pri=42                0 0
devpts               /dev/pts             devpts     mode=0620,gid=5       0 0
proc                 /proc                proc       defaults              0 0
usbdevfs             /proc/bus/usb        usbdevfs   noauto                0 0
/dev/sda4            /media/zip           auto       noauto,user           0 0
/dev/hdd             /media/cdrecorder    auto       ro,noauto,user,exec   0 0
/dev/cdrom           /media/cdrom         auto       ro,noauto,user,exec   0 0
/dev/fd0             /media/floppy        auto       noauto,user,sync 0 0
/mnt/hda8/home/vkrause/ /home/vkrause/    none       auto,bind             0 0

And here the information about the working machines:
(1) SuSE 9.1, x86, Kernel 2.6.8.1
DVD-ROM on secondary IDE channel, also no supermount or similar
vkrause@vkpc3:~> cat /etc/fstab
/dev/hda8       /       ext3    defaults 1 2
/dev/hda6       /boot   ext2    defaults
/dev/cdrom           /media/cdrom         auto ro,user,noauto 0 0
devpts  /dev/pts        devpts  defaults 0 0
/dev/dvd             /media/dvd           auto      ro,user,noauto 0 0
/dev/fd0             /media/floppy        auto      user,noauto,sync 0 0
proc    /proc   proc    defaults 0 0
usbdevfs        /proc/bus/usb   usbdevfs        noauto 0 0
/dev/hda1       /windows/C      vfat    uid=0,gid=0,umask=077,noauto,user 0 0
/dev/hda5       /windows/D      vfat    uid=500,gid=0,umask=077,user 0 0
/dev/hda7       swap    swap    pri=42 0 0

(2) SuSE 9.2, x86_64, Kernel 2.6.8 (SuSE default kernel, ie. heavily patched)
DVD-ROM on primary IDE channel
vkrause@vkpc5:~> cat /etc/fstab
/dev/sda3      /               ext3       acl,user_xattr        1 1
/dev/sda1     /windows/C    ntfs    ro,users,gid=users,umask=0002,nls=utf8 0 0
/dev/sda2      swap              swap       pri=42                0 0
devpts          /dev/pts           devpts     mode=0620,gid=5       0 0
proc           /proc                proc       defaults              0 0
usbfs          /proc/bus/usb    usbfs      noauto                0 0
sysfs          /sys                sysfs      noauto                0 0
/dev/dvd     /media/dvd  subfs      
fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0

> Does it happen only when something is in the drive? Or only when it's
> empty? Both?

IIRC the drives were always empty. I'll have to test what happens if there is 
a disc in (since this most likely means killing the machine, I'm not sure 
when I get the chance to do it).

regards
Volker

[Attachment #5 (application/pgp-signature)]

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<


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