Re: [kde-freebsd] multislot cardreader and hald
Joe Marcus Clarke said: > Committed with a change to check that the driver is one of da, sa, or cd > when the bus type is USB (we now have ATA USB support as well). I also Maybe block.freebsd.cam_path could be used as a discriminant here ? I don't know, just guessing. > changed the cdrom variable name to scsi_device as we aren't necessarily > dealing with cdrom devices in all cases. The functionality should not > be changed, though. Thanks for doing this. Thank you for the FreeBSD HAL! P.S. I had to reply by using a web archive of the list, because your message didn't make it through to me. The following is diagnostics from our local mail admin: 24.172.16.118 is listed in a RBL at blackholes.five-ten-sg.com as 127.0.0.2 -- Andriy Gapon ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd
Re: [kde-freebsd] multislot cardreader and hald
On Mon, 2007-12-24 at 19:11 +0200, Andriy Gapon wrote: > on 24/12/2007 16:32 Andriy Gapon said the following: > > on 21/12/2007 15:33 Joe Marcus Clarke said the following: > >> Disc media is treated differently than USB media. USB umass devices are > >> assumed to have media. This is part of the issue with the card reader > >> (floppy drives behave the same way). > > > > Isn't this a bad assumption? > > Attached is a patch that attempts to address removable storage devices > (that are not CD-ROMs) attached either via SCSI or via USB. The purpose > is to do "gentler" probing of media presence than that done by OS in > response to open(2). > I employed one hack in the code to avoid device being open()-ed if > cam_open_device() fails, but this was "just in case", not sure if it was > really needed. > > The patch works very well for me, especially in tandem with the patch > for SCSI verboseness that I posted to -stable and -scsi. Committed with a change to check that the driver is one of da, sa, or cd when the bus type is USB (we now have ATA USB support as well). I also changed the cdrom variable name to scsi_device as we aren't necessarily dealing with cdrom devices in all cases. The functionality should not be changed, though. Thanks for doing this. Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: [EMAIL PROTECTED] FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome signature.asc Description: This is a digitally signed message part ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd
Re: [kde-freebsd] multislot cardreader and hald
on 24/12/2007 16:32 Andriy Gapon said the following:
> on 21/12/2007 15:33 Joe Marcus Clarke said the following:
>> Disc media is treated differently than USB media. USB umass devices are
>> assumed to have media. This is part of the issue with the card reader
>> (floppy drives behave the same way).
>
> Isn't this a bad assumption?
Attached is a patch that attempts to address removable storage devices
(that are not CD-ROMs) attached either via SCSI or via USB. The purpose
is to do "gentler" probing of media presence than that done by OS in
response to open(2).
I employed one hack in the code to avoid device being open()-ed if
cam_open_device() fails, but this was "just in case", not sure if it was
really needed.
The patch works very well for me, especially in tandem with the patch
for SCSI verboseness that I posted to -stable and -scsi.
--
Andriy Gapon
--- addons/addon-storage.c.orig Mon Dec 24 16:45:04 2007
+++ addons/addon-storage.c Mon Dec 24 18:22:19 2007
@@ -42,6 +42,7 @@ static struct
char *device_file;
char *parent;
boolean is_cdrom;
+ boolean is_scsi_removable;
boolean had_media;
struct timeval next_update;
} addon = { { 2, 0 } };
@@ -71,6 +72,18 @@ hf_addon_storage_cdrom_eject_pressed (HF
}
static boolean
+hf_addon_storage_scsi_read_capacity (HFPCDROM *cdrom)
+{
+ unsigned char buf[8];
+ static char ccb[16] = { /*HFP_CDROM_READ_CAPACITY*/ 0x25 };
+
+ assert(cdrom != NULL);
+
+ /* we check only success/error and discard the data */
+ return hfp_cdrom_send_ccb(cdrom, ccb, 10, HFP_CDROM_DIRECTION_IN, buf, sizeof(buf), NULL);
+}
+
+static boolean
hf_addon_storage_update (void)
{
boolean has_media = FALSE;
@@ -94,6 +107,31 @@ hf_addon_storage_update (void)
hfp_cdrom_free(cdrom);
}
}
+ else if (addon.is_scsi_removable)
+{
+ /* (ab)use cdrom-specific routines:
+ * for what we are doing here there is no difference between
+ * a SCSI CD-ROM and any other disk-like SCSI device
+ * with removable media.
+ * This is a gentler check than trying to open the device.
+ */
+ HFPCDROM *cdrom;
+
+ /* XXX hfp_cdrom_new_from_fd(-1) below is an ugly hack to prevent
+ * regular open() in the case cam_open_device() fails.
+ */
+ cdrom = hfp_cdrom_new_from_fd(-1, addon.device_file, addon.parent);
+ if (cdrom)
+ {
+ /* some umass devices may lie in TEST UNIT READY,
+ * so doing READ CAPACITY to be sure.
+ */
+ if (hfp_cdrom_test_unit_ready(cdrom) && hf_addon_storage_scsi_read_capacity(cdrom))
+ has_media = TRUE;
+
+ hfp_cdrom_free(cdrom);
+ }
+}
else
{
int fd;
@@ -115,7 +153,9 @@ hf_addon_storage_update (void)
int
main (int argc, char **argv)
{
- char *drive_type;
+ const char *drive_type;
+ const char *removable;
+ const char *bus;
DBusConnection *connection;
if (! hfp_init(argc, argv))
@@ -129,6 +169,14 @@ main (int argc, char **argv)
if (! drive_type)
goto end;
+ removable = getenv("HAL_PROP_STORAGE_REMOVABLE");
+ if (! removable)
+goto end;
+
+ bus = getenv("HAL_PROP_STORAGE_BUS");
+ if (! bus)
+goto end;
+
addon.parent = getenv("HAL_PROP_INFO_PARENT");
if (! addon.parent)
goto end;
@@ -137,6 +185,7 @@ main (int argc, char **argv)
setproctitle("%s", addon.device_file);
addon.is_cdrom = ! strcmp(drive_type, "cdrom");
+ addon.is_scsi_removable = (! strcmp(bus, "scsi") || ! strcmp(bus, "usb")) && ! strcmp(removable, "true");
addon.had_media = hf_addon_storage_update();
connection = libhal_ctx_get_dbus_connection(hfp_ctx);
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
Re: [kde-freebsd] multislot cardreader and hald
On Mon, 2007-12-24 at 16:32 +0200, Andriy Gapon wrote:
> on 21/12/2007 15:33 Joe Marcus Clarke said the following:
> > Jeremy Messenger wrote:
> >> On Fri, 21 Dec 2007 05:59:44 -0600, Andriy Gapon <[EMAIL PROTECTED]> wrote:
> >>
> >>> on 20/12/2007 19:03 Jeremy Messenger said the following:
> I am no expert on hald, but if I understand it correct. If there is no
> probe in hald then hald will never know if you put/keep your da disks in
> and pull out. I bet other OSs do the same things. Correct me if I am
> wrong.
> >>> I now see what you are saying and this makes a lot of sense indeed. And
> >>> I agree that FreeBSD kernel is overly verbose about such a condition -
> >>> after all it is normal that a device with a ("field") removable media
> >>> can have no media. I need to check how FreeBSD 7 behaves in this respect
> >> FreeBSD 7 beahves same. I have 7.0-BETA4 (Dec 13). If I put DVD movie in
> >> and I will get over 16k lines in message under a minute.
> >>
> >> http://people.freebsd.org/~mezz/messages.txt.bz2
> >>
> >> If I put a blank CD in and I only get less than ten lines in messages. I
> >> can't wait for someone to fix FreeBSD because that over 16k lines under
> >> a minute is very annoy.
> >
> > Disc media is treated differently than USB media. USB umass devices are
> > assumed to have media. This is part of the issue with the card reader
> > (floppy drives behave the same way).
>
> Isn't this a bad assumption?
Probably, but right now I'm strapped with what I have time to do. Since
you have the hardware, if you could come up with a fix for hal, I'd be
happy to commit it.
Joe
--
Joe Marcus Clarke
FreeBSD GNOME Team :: [EMAIL PROTECTED]
FreeNode / #freebsd-gnome
http://www.FreeBSD.org/gnome
signature.asc
Description: This is a digitally signed message part
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
Re: [kde-freebsd] multislot cardreader and hald
on 21/12/2007 15:33 Joe Marcus Clarke said the following:
> Jeremy Messenger wrote:
>> On Fri, 21 Dec 2007 05:59:44 -0600, Andriy Gapon <[EMAIL PROTECTED]> wrote:
>>
>>> on 20/12/2007 19:03 Jeremy Messenger said the following:
I am no expert on hald, but if I understand it correct. If there is no
probe in hald then hald will never know if you put/keep your da disks in
and pull out. I bet other OSs do the same things. Correct me if I am
wrong.
>>> I now see what you are saying and this makes a lot of sense indeed. And
>>> I agree that FreeBSD kernel is overly verbose about such a condition -
>>> after all it is normal that a device with a ("field") removable media
>>> can have no media. I need to check how FreeBSD 7 behaves in this respect
>> FreeBSD 7 beahves same. I have 7.0-BETA4 (Dec 13). If I put DVD movie in
>> and I will get over 16k lines in message under a minute.
>>
>> http://people.freebsd.org/~mezz/messages.txt.bz2
>>
>> If I put a blank CD in and I only get less than ten lines in messages. I
>> can't wait for someone to fix FreeBSD because that over 16k lines under
>> a minute is very annoy.
>
> Disc media is treated differently than USB media. USB umass devices are
> assumed to have media. This is part of the issue with the card reader
> (floppy drives behave the same way).
Isn't this a bad assumption?
--
Andriy Gapon
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
Re: [kde-freebsd] multislot cardreader and hald
Jeremy Messenger wrote:
> On Fri, 21 Dec 2007 05:59:44 -0600, Andriy Gapon <[EMAIL PROTECTED]> wrote:
>
>> on 20/12/2007 19:03 Jeremy Messenger said the following:
>>> I am no expert on hald, but if I understand it correct. If there is no
>>> probe in hald then hald will never know if you put/keep your da disks in
>>> and pull out. I bet other OSs do the same things. Correct me if I am
>>> wrong.
>>
>> I now see what you are saying and this makes a lot of sense indeed. And
>> I agree that FreeBSD kernel is overly verbose about such a condition -
>> after all it is normal that a device with a ("field") removable media
>> can have no media. I need to check how FreeBSD 7 behaves in this respect
>
> FreeBSD 7 beahves same. I have 7.0-BETA4 (Dec 13). If I put DVD movie in
> and I will get over 16k lines in message under a minute.
>
> http://people.freebsd.org/~mezz/messages.txt.bz2
>
> If I put a blank CD in and I only get less than ten lines in messages. I
> can't wait for someone to fix FreeBSD because that over 16k lines under
> a minute is very annoy.
Disc media is treated differently than USB media. USB umass devices are
assumed to have media. This is part of the issue with the card reader
(floppy drives behave the same way).
Joe
>
> Cheers,
> Mezz
>
>> - I still use 6.2.
>> BTW, it seems that the messages come from SCSI/CAM code, so USB code
>> might not be a culprit here, it's just a "transport" for SCSI.
>>
>> OTOH, I wonder why the same doesn't happen for empty CD tray ? - I mean
>> the constant querying (errors are still printed on access).
>> This is a very un-educated guess: maybe HAL knows that acd/cd can have
>> have no media and does some checks before accessing it, but maybe it
>> expects that da always has media and so it tries to access it without
>> any special checks ?
>> I.e. one can simply open and try to read da device or one could issue
>> some SCSI commands to query the actual HW.
>
>
--
Joe Marcus Clarke
FreeBSD GNOME Team :: [EMAIL PROTECTED]
FreeNode / #freebsd-gnome
http://www.FreeBSD.org/gnome
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
Re: [kde-freebsd] multislot cardreader and hald
On Fri, 21 Dec 2007 05:59:44 -0600, Andriy Gapon <[EMAIL PROTECTED]> wrote:
> on 20/12/2007 19:03 Jeremy Messenger said the following:
>> I am no expert on hald, but if I understand it correct. If there is no
>> probe in hald then hald will never know if you put/keep your da disks in
>> and pull out. I bet other OSs do the same things. Correct me if I am
>> wrong.
>
> I now see what you are saying and this makes a lot of sense indeed. And
> I agree that FreeBSD kernel is overly verbose about such a condition -
> after all it is normal that a device with a ("field") removable media
> can have no media. I need to check how FreeBSD 7 behaves in this respect
FreeBSD 7 beahves same. I have 7.0-BETA4 (Dec 13). If I put DVD movie in
and I will get over 16k lines in message under a minute.
http://people.freebsd.org/~mezz/messages.txt.bz2
If I put a blank CD in and I only get less than ten lines in messages. I
can't wait for someone to fix FreeBSD because that over 16k lines under a
minute is very annoy.
Cheers,
Mezz
> - I still use 6.2.
> BTW, it seems that the messages come from SCSI/CAM code, so USB code
> might not be a culprit here, it's just a "transport" for SCSI.
>
> OTOH, I wonder why the same doesn't happen for empty CD tray ? - I mean
> the constant querying (errors are still printed on access).
> This is a very un-educated guess: maybe HAL knows that acd/cd can have
> have no media and does some checks before accessing it, but maybe it
> expects that da always has media and so it tries to access it without
> any special checks ?
> I.e. one can simply open and try to read da device or one could issue
> some SCSI commands to query the actual HW.
--
[EMAIL PROTECTED] - [EMAIL PROTECTED]
FreeBSD GNOME Team - FreeBSD Multimedia Hat (ports, not src)
http://www.FreeBSD.org/gnome/ - [EMAIL PROTECTED]
http://wiki.freebsd.org/multimedia - [EMAIL PROTECTED]
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
Re: [kde-freebsd] multislot cardreader and hald
on 20/12/2007 19:03 Jeremy Messenger said the following:
> I am no expert on hald, but if I understand it correct. If there is no
> probe in hald then hald will never know if you put/keep your da disks in
> and pull out. I bet other OSs do the same things. Correct me if I am wrong.
I now see what you are saying and this makes a lot of sense indeed. And
I agree that FreeBSD kernel is overly verbose about such a condition -
after all it is normal that a device with a ("field") removable media
can have no media. I need to check how FreeBSD 7 behaves in this respect
- I still use 6.2.
BTW, it seems that the messages come from SCSI/CAM code, so USB code
might not be a culprit here, it's just a "transport" for SCSI.
OTOH, I wonder why the same doesn't happen for empty CD tray ? - I mean
the constant querying (errors are still printed on access).
This is a very un-educated guess: maybe HAL knows that acd/cd can have
have no media and does some checks before accessing it, but maybe it
expects that da always has media and so it tries to access it without
any special checks ?
I.e. one can simply open and try to read da device or one could issue
some SCSI commands to query the actual HW.
--
Andriy Gapon
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
Re: [kde-freebsd] multislot cardreader and hald
On Thursday 20 December 2007 19:13:29 Joe Marcus Clarke wrote: > On Thu, 2007-12-20 at 11:03 -0600, Jeremy Messenger wrote: > > On Thu, 20 Dec 2007 10:51:37 -0600, Andriy Gapon <[EMAIL PROTECTED]> wrote: > > > on 20/12/2007 18:47 Jeremy Messenger said the following: > > >> On Thu, 20 Dec 2007 09:28:01 -0600, Andriy Gapon <[EMAIL PROTECTED]> > > >> > > >> wrote: > > >>> When I connect a USB multislot cardreader (CF, SD, etc) with only one > > >>> card inserted to my computer my /var/log/messages gets spammed with > > >>> the endless reports like the following: > > >>> kernel: Opened disk da1 -> 6 > > >>> kernel: (da2:umass-sim0:0:0:2): READ CAPACITY. CDB: 25 40 0 0 0 0 0 0 > > >>> 0 0 > > >>> kernel: (da2:umass-sim0:0:0:2): CAM Status: SCSI Status Error > > >>> kernel: (da2:umass-sim0:0:0:2): SCSI Status: Check Condition > > >>> kernel: (da2:umass-sim0:0:0:2): NOT READY csi:0,aa,55,41 asc:3a,0 > > >>> kernel: (da2:umass-sim0:0:0:2): Medium not present field replaceable > > >>> unit: 1 > > >>> kernel: (da2:umass-sim0:0:0:2): Unretryable error > > >>> kernel: Opened disk da2 -> 6 > > >>> kernel: (da3:umass-sim0:0:0:3): READ CAPACITY. CDB: 25 60 0 0 0 0 0 0 > > >>> 0 0 > > >>> kernel: (da3:umass-sim0:0:0:3): CAM Status: SCSI Status Error > > >>> kernel: (da3:umass-sim0:0:0:3): SCSI Status: Check Condition > > >>> kernel: (da3:umass-sim0:0:0:3): NOT READY csi:0,aa,55,41 asc:3a,0 > > >>> kernel: (da3:umass-sim0:0:0:3): Medium not present field replaceable > > >>> unit: 1 > > >>> kernel: (da3:umass-sim0:0:0:3): Unretryable error > > >>> kernel: Opened disk da3 -> 6 > > >>> > > >>> These reports are for the empty slots. > > >>> If I disable hald these messages get printed only a few times, but > > >>> with hald this happens endlessly, apparently every 2 seconds. > > >>> > > >>> I am curious if this is hald itself or KDE acting through it. > > >> > > >> It's FreeBSD since you still get w/out hald, report to [EMAIL PROTECTED] > > > > > > It's true that messages come from the kernel but, as I said, without > > > hald I get only a few of them and that's it. With hald running these > > > messages are produced every 2 seconds until the card-reader is > > > disconnected. So hald must be doing something silly here, like never > > > giving up on probing those da disks without any media behind them. > > > > I am no expert on hald, but if I understand it correct. If there is no > > probe in hald then hald will never know if you put/keep your da disks in > > and pull out. I bet other OSs do the same things. Correct me if I am > > wrong. > > This is a FreeBSD problem, but it's not a hal problem per se. I think > the GEOM/SCSI people are working to hide these kind of messages, but in > the meantime, you either need to live with them, stop using hal, or tell > hal to stop probing that device. > > The way hal works is that it periodically probes devices to determine if > there is media changes. In this manner, hal can auto-mount volumes. If > you do not want to auto-mount media from this device, then search the > archives for ways to manipulate the .fdi files to stop hal from probing > this device. Again, the ideal solution would be for the kernel people > to hide these messages behind verbose booting. > Ideal solution will be this way if you insert media into reader then it sends kernel a message about insertion (I guess cd/dvd works that way) and tell HALd to mount that device. IIRC then on Linux hald works correctly- this is only FreeBSD problem. ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd
Re: [kde-freebsd] multislot cardreader and hald
On Thu, 2007-12-20 at 11:03 -0600, Jeremy Messenger wrote: > On Thu, 20 Dec 2007 10:51:37 -0600, Andriy Gapon <[EMAIL PROTECTED]> wrote: > > > on 20/12/2007 18:47 Jeremy Messenger said the following: > >> On Thu, 20 Dec 2007 09:28:01 -0600, Andriy Gapon <[EMAIL PROTECTED]> > >> wrote: > >> > >>> When I connect a USB multislot cardreader (CF, SD, etc) with only one > >>> card inserted to my computer my /var/log/messages gets spammed with the > >>> endless reports like the following: > >>> kernel: Opened disk da1 -> 6 > >>> kernel: (da2:umass-sim0:0:0:2): READ CAPACITY. CDB: 25 40 0 0 0 0 0 0 > >>> 0 0 > >>> kernel: (da2:umass-sim0:0:0:2): CAM Status: SCSI Status Error > >>> kernel: (da2:umass-sim0:0:0:2): SCSI Status: Check Condition > >>> kernel: (da2:umass-sim0:0:0:2): NOT READY csi:0,aa,55,41 asc:3a,0 > >>> kernel: (da2:umass-sim0:0:0:2): Medium not present field replaceable > >>> unit: 1 > >>> kernel: (da2:umass-sim0:0:0:2): Unretryable error > >>> kernel: Opened disk da2 -> 6 > >>> kernel: (da3:umass-sim0:0:0:3): READ CAPACITY. CDB: 25 60 0 0 0 0 0 0 > >>> 0 0 > >>> kernel: (da3:umass-sim0:0:0:3): CAM Status: SCSI Status Error > >>> kernel: (da3:umass-sim0:0:0:3): SCSI Status: Check Condition > >>> kernel: (da3:umass-sim0:0:0:3): NOT READY csi:0,aa,55,41 asc:3a,0 > >>> kernel: (da3:umass-sim0:0:0:3): Medium not present field replaceable > >>> unit: 1 > >>> kernel: (da3:umass-sim0:0:0:3): Unretryable error > >>> kernel: Opened disk da3 -> 6 > >>> > >>> These reports are for the empty slots. > >>> If I disable hald these messages get printed only a few times, but with > >>> hald this happens endlessly, apparently every 2 seconds. > >>> > >>> I am curious if this is hald itself or KDE acting through it. > >> > >> It's FreeBSD since you still get w/out hald, report to [EMAIL PROTECTED] > > > > It's true that messages come from the kernel but, as I said, without > > hald I get only a few of them and that's it. With hald running these > > messages are produced every 2 seconds until the card-reader is > > disconnected. So hald must be doing something silly here, like never > > giving up on probing those da disks without any media behind them. > > I am no expert on hald, but if I understand it correct. If there is no > probe in hald then hald will never know if you put/keep your da disks in > and pull out. I bet other OSs do the same things. Correct me if I am wrong. This is a FreeBSD problem, but it's not a hal problem per se. I think the GEOM/SCSI people are working to hide these kind of messages, but in the meantime, you either need to live with them, stop using hal, or tell hal to stop probing that device. The way hal works is that it periodically probes devices to determine if there is media changes. In this manner, hal can auto-mount volumes. If you do not want to auto-mount media from this device, then search the archives for ways to manipulate the .fdi files to stop hal from probing this device. Again, the ideal solution would be for the kernel people to hide these messages behind verbose booting. Joe -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd
Re: [kde-freebsd] multislot cardreader and hald
On Thu, 20 Dec 2007 09:28:01 -0600, Andriy Gapon <[EMAIL PROTECTED]> wrote: > > When I connect a USB multislot cardreader (CF, SD, etc) with only one > card inserted to my computer my /var/log/messages gets spammed with the > endless reports like the following: > kernel: Opened disk da1 -> 6 > kernel: (da2:umass-sim0:0:0:2): READ CAPACITY. CDB: 25 40 0 0 0 0 0 0 0 0 > kernel: (da2:umass-sim0:0:0:2): CAM Status: SCSI Status Error > kernel: (da2:umass-sim0:0:0:2): SCSI Status: Check Condition > kernel: (da2:umass-sim0:0:0:2): NOT READY csi:0,aa,55,41 asc:3a,0 > kernel: (da2:umass-sim0:0:0:2): Medium not present field replaceable > unit: 1 > kernel: (da2:umass-sim0:0:0:2): Unretryable error > kernel: Opened disk da2 -> 6 > kernel: (da3:umass-sim0:0:0:3): READ CAPACITY. CDB: 25 60 0 0 0 0 0 0 0 0 > kernel: (da3:umass-sim0:0:0:3): CAM Status: SCSI Status Error > kernel: (da3:umass-sim0:0:0:3): SCSI Status: Check Condition > kernel: (da3:umass-sim0:0:0:3): NOT READY csi:0,aa,55,41 asc:3a,0 > kernel: (da3:umass-sim0:0:0:3): Medium not present field replaceable > unit: 1 > kernel: (da3:umass-sim0:0:0:3): Unretryable error > kernel: Opened disk da3 -> 6 > > These reports are for the empty slots. > If I disable hald these messages get printed only a few times, but with > hald this happens endlessly, apparently every 2 seconds. > > I am curious if this is hald itself or KDE acting through it. It's FreeBSD since you still get w/out hald, report to [EMAIL PROTECTED] Cheers, Mezz -- [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD GNOME Team - FreeBSD Multimedia Hat (ports, not src) http://www.FreeBSD.org/gnome/ - [EMAIL PROTECTED] http://wiki.freebsd.org/multimedia - [EMAIL PROTECTED] ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd
Re: [kde-freebsd] multislot cardreader and hald
On Thu, 20 Dec 2007 10:51:37 -0600, Andriy Gapon <[EMAIL PROTECTED]> wrote: > on 20/12/2007 18:47 Jeremy Messenger said the following: >> On Thu, 20 Dec 2007 09:28:01 -0600, Andriy Gapon <[EMAIL PROTECTED]> >> wrote: >> >>> When I connect a USB multislot cardreader (CF, SD, etc) with only one >>> card inserted to my computer my /var/log/messages gets spammed with the >>> endless reports like the following: >>> kernel: Opened disk da1 -> 6 >>> kernel: (da2:umass-sim0:0:0:2): READ CAPACITY. CDB: 25 40 0 0 0 0 0 0 >>> 0 0 >>> kernel: (da2:umass-sim0:0:0:2): CAM Status: SCSI Status Error >>> kernel: (da2:umass-sim0:0:0:2): SCSI Status: Check Condition >>> kernel: (da2:umass-sim0:0:0:2): NOT READY csi:0,aa,55,41 asc:3a,0 >>> kernel: (da2:umass-sim0:0:0:2): Medium not present field replaceable >>> unit: 1 >>> kernel: (da2:umass-sim0:0:0:2): Unretryable error >>> kernel: Opened disk da2 -> 6 >>> kernel: (da3:umass-sim0:0:0:3): READ CAPACITY. CDB: 25 60 0 0 0 0 0 0 >>> 0 0 >>> kernel: (da3:umass-sim0:0:0:3): CAM Status: SCSI Status Error >>> kernel: (da3:umass-sim0:0:0:3): SCSI Status: Check Condition >>> kernel: (da3:umass-sim0:0:0:3): NOT READY csi:0,aa,55,41 asc:3a,0 >>> kernel: (da3:umass-sim0:0:0:3): Medium not present field replaceable >>> unit: 1 >>> kernel: (da3:umass-sim0:0:0:3): Unretryable error >>> kernel: Opened disk da3 -> 6 >>> >>> These reports are for the empty slots. >>> If I disable hald these messages get printed only a few times, but with >>> hald this happens endlessly, apparently every 2 seconds. >>> >>> I am curious if this is hald itself or KDE acting through it. >> >> It's FreeBSD since you still get w/out hald, report to [EMAIL PROTECTED] > > It's true that messages come from the kernel but, as I said, without > hald I get only a few of them and that's it. With hald running these > messages are produced every 2 seconds until the card-reader is > disconnected. So hald must be doing something silly here, like never > giving up on probing those da disks without any media behind them. I am no expert on hald, but if I understand it correct. If there is no probe in hald then hald will never know if you put/keep your da disks in and pull out. I bet other OSs do the same things. Correct me if I am wrong. Cheers, Mezz -- [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD GNOME Team - FreeBSD Multimedia Hat (ports, not src) http://www.FreeBSD.org/gnome/ - [EMAIL PROTECTED] http://wiki.freebsd.org/multimedia - [EMAIL PROTECTED] ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd
Re: [kde-freebsd] multislot cardreader and hald
on 20/12/2007 18:47 Jeremy Messenger said the following: > On Thu, 20 Dec 2007 09:28:01 -0600, Andriy Gapon <[EMAIL PROTECTED]> wrote: > >> When I connect a USB multislot cardreader (CF, SD, etc) with only one >> card inserted to my computer my /var/log/messages gets spammed with the >> endless reports like the following: >> kernel: Opened disk da1 -> 6 >> kernel: (da2:umass-sim0:0:0:2): READ CAPACITY. CDB: 25 40 0 0 0 0 0 0 0 0 >> kernel: (da2:umass-sim0:0:0:2): CAM Status: SCSI Status Error >> kernel: (da2:umass-sim0:0:0:2): SCSI Status: Check Condition >> kernel: (da2:umass-sim0:0:0:2): NOT READY csi:0,aa,55,41 asc:3a,0 >> kernel: (da2:umass-sim0:0:0:2): Medium not present field replaceable >> unit: 1 >> kernel: (da2:umass-sim0:0:0:2): Unretryable error >> kernel: Opened disk da2 -> 6 >> kernel: (da3:umass-sim0:0:0:3): READ CAPACITY. CDB: 25 60 0 0 0 0 0 0 0 0 >> kernel: (da3:umass-sim0:0:0:3): CAM Status: SCSI Status Error >> kernel: (da3:umass-sim0:0:0:3): SCSI Status: Check Condition >> kernel: (da3:umass-sim0:0:0:3): NOT READY csi:0,aa,55,41 asc:3a,0 >> kernel: (da3:umass-sim0:0:0:3): Medium not present field replaceable >> unit: 1 >> kernel: (da3:umass-sim0:0:0:3): Unretryable error >> kernel: Opened disk da3 -> 6 >> >> These reports are for the empty slots. >> If I disable hald these messages get printed only a few times, but with >> hald this happens endlessly, apparently every 2 seconds. >> >> I am curious if this is hald itself or KDE acting through it. > > It's FreeBSD since you still get w/out hald, report to [EMAIL PROTECTED] It's true that messages come from the kernel but, as I said, without hald I get only a few of them and that's it. With hald running these messages are produced every 2 seconds until the card-reader is disconnected. So hald must be doing something silly here, like never giving up on probing those da disks without any media behind them. -- Andriy Gapon ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd
[kde-freebsd] multislot cardreader and hald
When I connect a USB multislot cardreader (CF, SD, etc) with only one card inserted to my computer my /var/log/messages gets spammed with the endless reports like the following: kernel: Opened disk da1 -> 6 kernel: (da2:umass-sim0:0:0:2): READ CAPACITY. CDB: 25 40 0 0 0 0 0 0 0 0 kernel: (da2:umass-sim0:0:0:2): CAM Status: SCSI Status Error kernel: (da2:umass-sim0:0:0:2): SCSI Status: Check Condition kernel: (da2:umass-sim0:0:0:2): NOT READY csi:0,aa,55,41 asc:3a,0 kernel: (da2:umass-sim0:0:0:2): Medium not present field replaceable unit: 1 kernel: (da2:umass-sim0:0:0:2): Unretryable error kernel: Opened disk da2 -> 6 kernel: (da3:umass-sim0:0:0:3): READ CAPACITY. CDB: 25 60 0 0 0 0 0 0 0 0 kernel: (da3:umass-sim0:0:0:3): CAM Status: SCSI Status Error kernel: (da3:umass-sim0:0:0:3): SCSI Status: Check Condition kernel: (da3:umass-sim0:0:0:3): NOT READY csi:0,aa,55,41 asc:3a,0 kernel: (da3:umass-sim0:0:0:3): Medium not present field replaceable unit: 1 kernel: (da3:umass-sim0:0:0:3): Unretryable error kernel: Opened disk da3 -> 6 These reports are for the empty slots. If I disable hald these messages get printed only a few times, but with hald this happens endlessly, apparently every 2 seconds. I am curious if this is hald itself or KDE acting through it. -- Andriy Gapon ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd
