On Fri, Mar 23, 2007 at 11:02:55AM +0100, Bastian Venthur wrote:
>
> I don't know if only a minor subset is affected, do you have numbers I
> don't have? Maybe we can agree that a subset is affected.
During the two and a half months that this bug has been filed, there
were 2 people, other than the original submitter, who reported that
they were affected by it (including you). Given the number of such
wifi cards out there, I think it is reasonable to call it a "minor
subset".
> Besides that, I still think the bug is release critical and I disagree
> that the severity of a bug depends on the number of machines affected.
It does not depend *only* on the number of machines affected. Other
factors which I've already mentioned: the daemon works fine in a
primary mode of operation (with kill switch off), and there is a
simple workaround (blacklisting the module, and loading it by hand
when appropriate). Finally, the release manager has also concurred
that this bug is not RC.
Anyway, to something constructive: if you can reliably reproduce the
problem, please try replacing the start-stop-daemon call, invoking the
daemon in the init file by one with a strace, something along the
lines of
strace /sbin/ipw3945 --pid-file=${DAEMON_PID_FILE} \
--log-file=${DAEMON_LOG_FILE}
and post the last few lines of output. Hopefully, it hangs in some
syscall, that might give us a clue about what's going on. It would be
also useful if you could check whether the bug is reproducible if you
do not start the daemon by init file, but later by hand.
Thanks,
--
Jurij Smakov [EMAIL PROTECTED]
Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
