From: maximilian attems <janitor@sternwelten.at>
To: NetDev <netdev@oss.sgi.com>, Pavel Machek <pavel@ucw.cz>
Subject: Re: sis900 oops on resume
Date: Thu, 18 Nov 2004 10:46:02 +0100 [thread overview]
Message-ID: <20041118094602.GB2287@stro.at> (raw)
In-Reply-To: <20041118084431.GA13870@gateway.milesteg.arr>
On Thu, 18 Nov 2004, Daniele Venzano wrote:
> On Thu, Nov 18, 2004 at 03:14:25AM +0100, maximilian attems wrote:
> > On Wed, 17 Nov 2004, Pavel Machek wrote:
> > > > happens since the use of guessnet,
> > > > guessnet is based on divine and sends arp requests to network.
> > > > network was down after the oops, but beside resume system worked.
> > >
> > > And where do you see the oops? Irq 10 does not work, that's only
> > > backtrace. Fix the sis900 driver...
> >
> > ok, i'm not that familiar with suspend pathes,
> > what's going wrong in sis900_resume() or sis900_suspend()?
>
> I'm aware of this problem, sis900 looses the first interrupt after
> resume, I have to check the code.
> On my tests the card, after that lost interrupt, worked normally. Is
> that your case, or do you have a non working sis900 after resume ?
well it works, as long as i do not use guessnet(8),
as described in the bug report, but the lost interrupt is reported
on every resume.
--
maks
next prev parent reply other threads:[~2004-11-18 9:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-17 18:24 sis900 oops on resume maximilian attems
2004-11-17 20:10 ` Pavel Machek
2004-11-18 2:14 ` maximilian attems
2004-11-18 8:44 ` Daniele Venzano
2004-11-18 9:46 ` maximilian attems [this message]
2004-11-19 10:01 ` Daniele Venzano
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=20041118094602.GB2287@stro.at \
--to=janitor@sternwelten.at \
--cc=netdev@oss.sgi.com \
--cc=pavel@ucw.cz \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.