public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniele Venzano <webvenza@libero.it>
To: Pavel Machek <pavel@ucw.cz>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Ollie Lho <ollie@sis.com.tw>
Subject: Re: Linux 2.6.0-test7 - Suspend to Disk success
Date: Sun, 19 Oct 2003 09:38:45 +0200	[thread overview]
Message-ID: <20031019073845.GA820@picchio.gall.it> (raw)
In-Reply-To: <20031018180102.GA461@elf.ucw.cz>

CC'ed sis900 mantainer.

On Sat, Oct 18, 2003 at 08:01:02PM +0200, Pavel Machek wrote:
> Did sis900 driver work in -test7?

No, it didn't and reconfiguring the interface after resume doesn't 
make it work, probably it needs a module reload, but I use sis900
compiled in.

For the bash problem, there is something different between test7 and test8, 
with test7 I get on resume:

Unable to handle kernel paging request at virtual address 401289b8
 printing eip:
401289b8
*pde = 0155d067
*pte = 00000000
Oops: 0004 [#1]
CPU:    0
EIP:    0073:[<401289b8>]    Not tainted
EFLAGS: 00010246
EIP is at 0x401289b8
eax: 00000004   ebx: 00000001   ecx: 080f8c08   edx: 00000004
esi: 00000004   edi: 080f8c08   ebp: bffff868   esp: bffff838
ds: 007b   es: 007b   ss: 007b
Process bash (pid: 1037, threadinfo=dafec000 task=db29a140)
 <6>note: bash[1037] exited with preempt_count 1

And then bash dies. With test8, bash dies the same, but there is no such
message on resume...

-- 
----------------------------------------
Daniele Venzano
Web: http://digilander.iol.it/webvenza/


  parent reply	other threads:[~2003-10-19  7:39 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-08 19:47 Linux 2.6.0-test7 - stability freeze Linus Torvalds
2003-10-08 23:57 ` Linux 2.6.0-test7 - stability freeze (compile stats) John Cherry
2003-10-09 12:45 ` Linux 2.6.0-test7 - compile/boot success iain d broadfoot
2003-10-09 13:29 ` 2.6.0-test7 BLK_DEV_FD dependence on ISA breakage Mikael Pettersson
2003-10-09 14:05   ` Andrew Morton
2003-10-09 18:04     ` Anton Blanchard
2003-10-09 18:18     ` Arun Sharma
2003-10-09 20:21       ` Mikael Pettersson
2003-10-10 11:55         ` Geert Uytterhoeven
2003-10-13  4:52 ` Linux 2.6.0-test7 - stability freeze Rob Landley
2003-10-13  4:53 ` Deja vu Rob Landley
2003-10-13 17:34 ` Linux 2.6.0-test7 - stability freeze Olaf Hering
2003-10-13 20:50   ` gcc -msoft-float [Was: Linux 2.6.0-test7 - stability freeze] Sam Ravnborg
2003-10-14  8:12     ` Olaf Hering
2003-10-14  8:31       ` Arjan van de Ven
2003-10-14  8:50         ` Olaf Hering
2003-10-14 11:40   ` Linux 2.6.0-test7 - stability freeze Jakub Jelinek
2003-10-15 17:27 ` Linux 2.6.0-test7 - Suspend to Disk success Jonathan McDowell
2003-10-15 21:00   ` Daniele Venzano
2003-10-16 14:06     ` Pavel Machek
2003-10-18 17:35       ` Daniele Venzano
2003-10-18 17:54       ` Daniele Venzano
2003-10-18 18:01         ` Pavel Machek
2003-10-18 20:48           ` Daniele Venzano
2003-10-19  7:38           ` Daniele Venzano [this message]
2003-10-20 19:08             ` Patrick Mochel

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=20031019073845.GA820@picchio.gall.it \
    --to=webvenza@libero.it \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ollie@sis.com.tw \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox