LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: "Chatre, Reinette" <reinette.chatre@intel.com>
Cc: ipw3945-devel@lists.sourceforge.net,
	linux-wireless@vger.kernel.org, "Zhu, Yi" <yi.zhu@intel.com>,
	kernel list <linux-kernel@vger.kernel.org>
Subject: Re: ipw3945: not only it periodically dies, it also BUG()s
Date: Wed, 20 Feb 2008 00:48:22 +0100	[thread overview]
Message-ID: <20080219234822.GA23882@elf.ucw.cz> (raw)
In-Reply-To: <D936D925018D154694D8A362EEB0892003ABD431@orsmsx416.amr.corp.intel.com>

Hi!

> > unfortunately the link here does not work. 
> 
> The instructions on how to report a bug have been updated to address the
> above issues. Thank you very much for helping us to make it better.

Thanks.

One more nit:

bugzilla-daemon@bughost.org seems like normal bugzilla, where you can
hit reply button, and control it using email... but that does not
actually work.

It would be nice to fix that. (Or at least make mail appear from
noreply@bughost.org, so that it is plain to see it does not work).

It seems that iwl3945 problem is somehow linked to
GROUP_SCHED... probably iwl can not handle latencies introduced by it?


									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2008-02-19 23:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-05 21:44 Pavel Machek
2008-02-05 22:59 ` Pavel Machek
2008-02-06  2:20 ` Chatre, Reinette
2008-02-06 14:32   ` Pavel Machek
2008-02-06 17:13     ` Chatre, Reinette
2008-02-06 21:00       ` Pavel Machek
2008-02-06 23:08         ` Chatre, Reinette
2008-02-15 22:41         ` Chatre, Reinette
2008-02-19 23:48           ` Pavel Machek [this message]
2008-02-07 22:04       ` iwl3945: not only it periodically dies, it also BUG()s, and oopses Pavel Machek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080219234822.GA23882@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=ipw3945-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=reinette.chatre@intel.com \
    --cc=yi.zhu@intel.com \
    --subject='Re: ipw3945: not only it periodically dies, it also BUG()s' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).