On Thu, Aug 10, 2006 at 12:54:19AM +0200, Sheer El-Showk wrote:
> Is this a similar problem to what you were having on your laptop
> before the patch? Would you expect your patch to work for me or do
> you think its an unrelated problem? Whatever it is I definately have
> an issue with the disk t
Sorry to say that it doesn't seem to help much on my laptop. I
installed 2.6.18-rc3 with your patch (I even checked the code to see
that the patch got implemented) and tried s2ram from the console and
suspend still took noticably long. Moreover, when I got back a prompt
I tried and 'ls' and the m
On Wednesday 09 August 2006 23:28, Luca Tettamanti wrote:
> On 8/9/06, Rafael J. Wysocki <[EMAIL PROTECTED]> wrote:
> > > After having disabled the so called "IBM Predesktop Area" in the BIOS
> > > everything works (in the BIOS setup: Security -> IBM Predesktop Area ->
> > > Current Setting: Disabl
On 8/9/06, Rafael J. Wysocki <[EMAIL PROTECTED]> wrote:
> > After having disabled the so called "IBM Predesktop Area" in the BIOS
> > everything works (in the BIOS setup: Security -> IBM Predesktop Area ->
> > Current Setting: Disabled).
> > As far as I know this IBM Predesktop Area is located in a
On Wednesday 09 August 2006 22:38, Jason Lunz wrote:
> On Wed, Aug 09, 2006 at 10:12:10PM +0200, Rafael J. Wysocki wrote:
]--snip--[
>
> I think Benjamin's may be describing my hardware. My current patch is
> calling hwif->tuneproc(), which resets both controller and drives
> afaict. I plan on co
On Wednesday 09 August 2006 17:06, Tim Dijkstra wrote:
> Hi,
>
> I got a bug report in the debian BTS which is beyond my knowledge.
> Could one of you shed some light on the issue?
>
> Thanks,
>
> Tim
>
>
> Forwarded message:
>
> Machine: IBM Thinkpad R50p
>
> I recognized following issues
On Wed, Aug 09, 2006 at 10:12:10PM +0200, Rafael J. Wysocki wrote:
> AFAIK, the AHCI suspend to RAM support is on its way, but does anyone know
> about the other SATA/PATA drivers?
AFAICT, the situation with drivers/ide is that it happens to work (by
luck) well enough for most people that it's bee
On 8/9/06, Michal Čihař <[EMAIL PROTECTED]> wrote:
> On Wed, 9 Aug 2006 14:31:59 +0200
> Pavel Machek <[EMAIL PROTECTED]> wrote:
>
> > Well, plus huge comment saying what stupid manufacturer did this
> > :-). Assuming there's only one i***t making notebooks, it will
> > actually work okay.
>
> I di
On Wednesday 09 August 2006 15:15, Jason Lunz wrote:
> On Wed, Aug 09, 2006 at 01:42:17PM +0200, Rafael J. Wysocki wrote:
> > The fix was for AMD/NVidia IDE, but Alan vetoed it on the basis that it
> > should
> > be done at the general level. Everyone agreed, but I don't know if anyone
> > took c
On Wednesday 09 August 2006 18:27, Sheer El-Showk wrote:
> So, might this general IDE fix solve my problem? I compiled
> 2.6.18-rc3-mm2 and tried 's2ram -f' but it just crashed while
> suspending so I couldn't test this.
There is a general suspend failure related to the block IO in -rc3-mm2.
I'm
On Wed, Aug 09, 2006 at 11:32:06AM +0200, Tim Dijkstra wrote:
> Hi,
>
> With the libc6-dev in current debian sid, I need to include
> to compile. Else gcc will complain
>
> swsusp.h:141: error: "SYNC_FILE_RANGE_WRITE" undeclared
>
> This problem was hidden by the fact that that constant i
On Wed, Aug 09, 2006 at 06:27:13PM +0200, Sheer El-Showk wrote:
> So, might this general IDE fix solve my problem? I compiled
> 2.6.18-rc3-mm2 and tried 's2ram -f' but it just crashed while
> suspending so I couldn't test this.
Maybe. Which ide driver are you using? There's plenty of other stuff
On Wed, 9 Aug 2006 14:31:59 +0200
Pavel Machek <[EMAIL PROTECTED]> wrote:
> Well, plus huge comment saying what stupid manufacturer did this
> :-). Assuming there's only one i***t making notebooks, it will
> actually work okay.
I didn't say it's notebook :-). It's desktop computer. And as I can s
So, might this general IDE fix solve my problem? I compiled
2.6.18-rc3-mm2 and tried 's2ram -f' but it just crashed while
suspending so I couldn't test this. Will this patch eventually get
merged into the next release (i.e. 2.6.19)? Jason if you want this
tested more I can try it but the -mm2 is
On Wed, Aug 09, 2006 at 05:06:02PM +0200, Tim Dijkstra wrote:
> Hi,
>
> I got a bug report in the debian BTS which is beyond my knowledge.
> Could one of you shed some light on the issue?
Hopefully.
I ran across exactly the same on a T42p today.
> Machine: IBM Thinkpad R50p
>
> I recognized fo
On Wed, Aug 02, 2006 at 04:47:06PM +1000, Brian Keck wrote:
>
> Hello,
>
> This is to report a s2ram success on a Vaio TX17 ...
> sys_vendor = "Sony Corporation"
> sys_product = "VGN-TX17GP_W"
> sys_version = "J0019H8C"
> bios_version = "R0031V1"
>
> Kernel is
Hi,
I got a bug report in the debian BTS which is beyond my knowledge.
Could one of you shed some light on the issue?
Thanks,
Tim
Forwarded message:
Machine: IBM Thinkpad R50p
I recognized following issues concerning s2ram/s2disk/s2both:
- calling s2ram works fine, resuming from RAM work
On Tue, Aug 01, 2006 at 01:54:50PM +0200, Martin Sack wrote:
> Hello
>
> I'm using s2ram integrated within powersaved on an Acer TravelMate
> 801LCi which has been recognized as a TravelMate 800. Its graphics
> adapter is a Radeon M9 which suffers from the usual radeon chip
> problems. To get s2ra
On Sat, Jul 29, 2006 at 02:50:16PM +0200, Pavel Machek wrote:
> Hi!
>
> We got the report (twice :-).
> > The only other notes I have is that:
> > 1) This is a desktop PC (ASUS A7V600, AMD Barton 2800+, ATI X700 Pro
> > AGP, 2 GB DDR 400)
>
> ...but desktop PCs are little trickier to whitelist
On Wed, Aug 09, 2006 at 01:42:17PM +0200, Rafael J. Wysocki wrote:
> The fix was for AMD/NVidia IDE, but Alan vetoed it on the basis that it should
> be done at the general level. Everyone agreed, but I don't know if anyone
> took care of that. Jason?
I redid the patch at the general IDE level.
Hi!
> Pavel Machek <[EMAIL PROTECTED]> wrote:
>
> > Heh... right solution here would be to make them fix their BIOS.
>
> Hmm, I just tried two latest and it says "stem manufacturer" instead of
> "System manufacturer", what a great improvement.
>
> > Or you could submit a patch to add required f
Hi
On Wed, 9 Aug 2006 09:50:33 +0200
Pavel Machek <[EMAIL PROTECTED]> wrote:
> Heh... right solution here would be to make them fix their BIOS.
Hmm, I just tried two latest and it says "stem manufacturer" instead of
"System manufacturer", what a great improvement.
> Or you could submit a patch
Hi,
On Wednesday 09 August 2006 13:23, Pavel Machek wrote:
]--snip--[
>
> Yes, so it is definitely harddrive. You probably should add all
> details to bugzilla.kernel.org, and then ask the IDE maintainers.
>
> Ouch and I think there were patches fixing that, not yet in
> mainline...
Well, I'm n
Hi!
> I think you're right Stefan, this is very possibly a hard disk timeout
> issue because even after suspend wakes up I can run a few commands,
> even accessing the hard disk, but then after another few seconds if I
> try to access the hard-disk the command will block (the machine does
> not fr
On Wednesday 09 August 2006 12:31, Sheer El-Showk wrote:
> Hi Rafael,
>
> Should the patch you gave me work against a normal 2.6.18-rc3 tree?
> The patch command is telling me it can't find the file to patch at
> input line 9 (which does not seem to point to a file). Sorry if I'm
> being dense bu
On Wed, Aug 09, 2006 at 12:40:19PM +0200, Sheer El-Showk wrote:
> Hi,
>
> I think you're right Stefan, this is very possibly a hard disk timeout
> issue because even after suspend wakes up I can run a few commands,
> even accessing the hard disk, but then after another few seconds if I
> try to ac
Hi,
I think you're right Stefan, this is very possibly a hard disk timeout
issue because even after suspend wakes up I can run a few commands,
even accessing the hard disk, but then after another few seconds if I
try to access the hard-disk the command will block (the machine does
not freeze, just
On Wed, Aug 09, 2006 at 11:30:50AM +0200, Sheer El-Showk wrote:
> Hi Guys,
>
> Again, thanks for all the input. Stefan my machine is new. I bought it less
> than two years ago and it was a very expensive laptop ;-> Its a Sony A190
> (the ones with the giant screens that are completely unportable
Hi Rafael,
Should the patch you gave me work against a normal 2.6.18-rc3 tree?
The patch command is telling me it can't find the file to patch at
input line 9 (which does not seem to point to a file). Sorry if I'm
being dense but I don't know the expected syntax of the patch file. I
ran 'patch -
Hi!
Please no html posts.
>I don't really know how powersave is setup but I presume if I just
>call s2ram manually from the console that this does not run any
>scripts or anything on resume right? But when I try s2ram manually it
>still takes ~30 seconds to get me back to X windo
Hi!
> My new HP dv8000t will not resume from suspend-to-RAM. It seems to be truly
> dead, not just a display issue (though obviously, the display doesn't go on
> either). Upon resume(=from RAM), there is no caps lock, and any command
> issued blindly does nothing, even after cacheing the command f
On Wednesday 09 August 2006 11:30, Sheer El-Showk wrote:
> Hi Guys,
>
> Again, thanks for all the input. Stefan my machine is new. I bought it less
> than two years ago and it was a very expensive laptop ;-> Its a Sony A190
> (the ones with the giant screens that are completely unportable) and i
Hi,
With the libc6-dev in current debian sid, I need to include
to compile. Else gcc will complain
swsusp.h:141: error: "SYNC_FILE_RANGE_WRITE" undeclared
This problem was hidden by the fact that that constant is defined
in swsusp.h if SYS_sync_file_range was not, which wasn't defined
On Wed 2006-08-09 10:02:44, Stefan Seyfried wrote:
> On Wed, Aug 09, 2006 at 09:52:49AM +0200, Pavel Machek wrote:
> > Hi!
> >
> > I found out that my X60 was not in the whitelist, because its serial
> > was not in range. I'll just commit "1709*" addition to the whitelist,
> > but...
> >
> > Coul
Hi Guys,Again, thanks for all the input. Stefan my machine is new. I bought it less than two years ago and it was a very expensive laptop ;-> Its a Sony A190 (the ones with the giant screens that are completely unportable) and in Windows resume is pretty fast (its been a while since i tested it b
On Wed, Aug 09, 2006 at 09:52:49AM +0200, Pavel Machek wrote:
> Hi!
>
> I found out that my X60 was not in the whitelist, because its serial
> was not in range. I'll just commit "1709*" addition to the whitelist,
> but...
>
> Could not we use ThinkPad X60 string to just whitelist all of them? I
>
Hi,
On Wed, Aug 09, 2006 at 09:47:18AM +0200, Pavel Machek wrote:
> On Wed 2006-08-09 08:50:07, Stefan Seyfried wrote:
> > I think this highly depends on the specific machine's BIOS.
> > I have machines here that resume in less than 2 seconds and others that
> > take 20 seconds and more.
>
> Whi
Hi!
I found out that my X60 was not in the whitelist, because its serial
was not in range. I'll just commit "1709*" addition to the whitelist,
but...
Could not we use ThinkPad X60 string to just whitelist all of them? I
see it would not work on older thinkpads, but on x60 we have
meaningful strin
Hi!
> I hope this is right place to write :-).
Yes.
> On ASUS P5LD2-VM s2ram -f works fine, here is output of s2ram -i:
>
> sys_vendor = "System manufacturer"
> sys_product = "System Product Name"
> sys_version = "System Version"
> bios_version = "0406"
>
> Using Board
On Wed 2006-08-09 08:50:07, Stefan Seyfried wrote:
> Hi,
>
> On Tue, Aug 08, 2006 at 10:07:49PM +0200, Sheer El-Showk wrote:
>
> > to work at all (which I'll try to debug). I even used the new version of
> > suspend downloaded from sourceforge (which doesn't go through powersave) and
> > it stil
Hi!
>Thanks for the response. Does it matter that its 2.6.18-rc4 and not
>2.6.18-rc3? I compiled rc3 a while ago and just tried it out and
>didn't get a significant improvment. Specifically, suspending to ram
>using powersave still takes about 30 seconds to resume and suspending
41 matches
Mail list logo
