All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Andreolini <m.andreolini@tiscali.it>
To: Daniele Venzano <webvenza@libero.it>
Cc: linux-kernel@vger.kernel.org
Subject: Re: problems with suspend-to-disk (ACPI), 2.6.1-rc2
Date: Wed, 14 Jan 2004 16:47:57 +0100	[thread overview]
Message-ID: <400564AD.6050407@tiscali.it> (raw)
In-Reply-To: <20040113212811.GA12144@gateway.milesteg.arr>

Daniele Venzano wrote:

 >
 >I added support for sis900 and the bash was being killed even before the
 >driver had any support for suspend/resume.
 >I reported that same problem (shell being killed) some time ago, there 
was
 >some follow up, but if I remember right no solution was found at the
 >time.
 >
 >>>bad: scheduling while atomic!
 >>>Call Trace:
 >>> [<c0119d16>] schedule+0x586/0x590
 >>> [<c0124f5c>] __mod_timer+0xfc/0x170
 >>> [<c0125ab3>] schedule_timeout+0x63/0xc0
 >>> [<c0125a40>] process_timeout+0x0/0x10
 >>> [<c01da44b>] pci_set_power_state+0xeb/0x190
 >>> [<ec947823>] sis900_resume+0x63/0x130 [sis900]
 >>> [<c01dc9a6>] pci_device_resume+0x26/0x30
 >
 >
 >I'll check this, the card keeps working after resume or not ?
 >
 >Thanks, bye.
 >
Hi Daniele,

the card does _not_ work after resume, both on 2.6.1-rc2 vanilla and 
with Pavel's patch.
I have to manually

rmmod sis900
modprobe sis900
ifconfig <ip> eth0 up

After that, it starts working again.

Bye
Mauro Andreolini



  reply	other threads:[~2004-01-14 15:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-08 19:03 problems with suspend-to-disk (ACPI), 2.6.1-rc2 m.andreolini
2004-01-13 13:18 ` Pavel Machek
2004-01-13 21:28   ` Daniele Venzano
2004-01-14 15:47     ` Mauro Andreolini [this message]
2004-01-14 16:50       ` Daniele Venzano
2004-01-14 17:59         ` m.andreolini
2004-01-14 19:18           ` Daniele Venzano
2004-01-14 20:30             ` Mauro Andreolini
2004-01-14 19:47       ` Nigel Cunningham
2004-01-14 20:35         ` Mauro Andreolini
2004-01-14 10:03   ` m.andreolini

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=400564AD.6050407@tiscali.it \
    --to=m.andreolini@tiscali.it \
    --cc=linux-kernel@vger.kernel.org \
    --cc=webvenza@libero.it \
    /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.