Re: swsusp: which page should be saved?

On Tue, 2006-03-21 at 17:42 +0800, Pavel Machek wrote:
> Hi!
> 
> > > Ok, I guess it is okay to go in if it stays in -mm for long enough
> to  
> > > get a lot of testing. 
> > I'll do more tests and back to you. BTW, I wonder if BIOS already
> saved 
> > reserved memory (those doing communication with OS) in the
> 'platform' 
> > method of S4.
> 
> Yep, it should be safe. I bet it will break some obscure machine, but 
> it will probably fix some obscure machine, too... Just needs lots of
> testing.
> 
> > > > Anyway, skipping kernel text should be safe, isn't it? 
> > >  
> > > It probably is. But you need to save modules.  
> > I just consider the region from kernel start(1M) to the end of
> rodata. 
> > In my test, the region is about 4M memory. Just adding several lines
> to 
> > save 4M memory is worthy.
> 
> Well, few lines to save 4MB is nice. OTOH 4MB are saved in about 
> 100msec, and if it brings in hard-to-debug bug on obscure 
> machine... we did not win much.
> 
> > > And we do use some  

CELF Power management requirements draft for 2006.

I wanted to get his posted before the PM-summit as I'll be speaking to
items in it on Wednesday.

http://tree.celinuxforum.org/CelfPubWiki/CELFPmRequirements2006?action=A
ttachFile&do=get&target=CELF_PM_requierments2006.pdf

is a draft.  Feel free to provide any comments or feed back.

It is also linked too from the top of the following Wiki page.

http://tree.celinuxforum.org/CelfPubWiki/CELFPmRequirements2006

--mgross
Intel Open Source Technology Center
(503) 677-4628
(503)-712-6227
ms: JF1-235
2111 NW 25th Ave
Hillsboro, OR 97124

I wanted to get his posted before the PM-summit as I'll be speaking to
items in it on Wednesday.

http://tree.celinuxforum.org/CelfPubWiki/CELFPmRequirements2006?action=A
ttachFile&do=get&target=CELF_PM_requierments2006.pdf

is a draft.  Feel free to provide any comments or feed back.

Re: [PATCH] suspend.c: make sure stdin, stdout and stderr are open

On Fri, Mar 24, 2006 at 08:13:48PM +0100, Stefan Rompf wrote:
> Hi,
> 
> recently I patched my 2.6.16 kernel to use uswsusp. Nice work, but when I 
> installed /usr/local/sbin/suspend into the Suse 9.3 powermanagement scripts, 
> I've stumbled over a bad interaction: powersaved closes all filedescriptors 
> before calling scripts. suspend then opens snapshot and swap device, 

FWIW, i will also adress this in powersaved. More programs will run into
the same trap probably 
--

-- 
Stefan Seyfried                  \ "I didn't want to write for pay. I
QA / R&D Team Mobile Devices      \ wanted to be paid for what I write."
SUSE LINUX Products GmbH, Nürnberg \                    -- Leonard Cohen

Re: swsusp: which page should be saved?

Hi!

> > > > Ouch and IIRC top-level pagedir or something  
> > > > like that lives in kernel "text" -- it is in assembly and
> > wrongly  
> > > > placed. 
> > > i386 does the right thing and put the pagedir in data segment.
> > x86_64 
> > > not, I think we could clean it up.
> > 
> > This probably should be done, first, and gotten past Andi.
> We asked the question to (intel's) BIOS guys, and below is the result.
> a. BIOS reserved region/hole - no save/restore
> b. ACPI NVS - save/restore
> c. 'ACPI Data' is a little tricky. After OS boots, os can reclaim this
> region, so regard it as normal ram. But we are afraid Linux runtime
> module loading might use this region somewhere, so we also mark this
> region as save/restore. Anyway, this hasn't any side effect.
> Hopefully all BIOSes follow this rule.

This comment needs to go somewhere in source.... aha, it is there,
mostly, but without the "tricky" remark.

> Pages (Reserved/ACPI NVS/ACPI Data) below
> end_pfn(x86_64)/max_low_pfn(i386) will be saved/restored by S4
> currently. We should mark 'Reserved' pages not saveable.
> Pages (Reserved/ACPI NVS/ACPI Data) above end_pfn/max_low_pfn
> will not be saved/restored by S4 currently. We should save the
> 'ACPI NVS/ACPI Data' pages in the highmem.

Re: swsusp: which page should be saved?

On Tue, 2006-04-11 at 15:39 +0800, Pavel Machek wrote:
> Hi!
> 
> > > > > Ouch and IIRC top-level pagedir or something   
> > > > > like that lives in kernel "text" -- it is in assembly and 
> > > wrongly   
> > > > > placed.  
> > > > i386 does the right thing and put the pagedir in data segment. 
> > > x86_64  
> > > > not, I think we could clean it up. 
> > >  
> > > This probably should be done, first, and gotten past Andi. 
> > We asked the question to (intel's) BIOS guys, and below is the
> result. 
> > a. BIOS reserved region/hole - no save/restore 
> > b. ACPI NVS - save/restore 
> > c. 'ACPI Data' is a little tricky. After OS boots, os can reclaim
> this 
> > region, so regard it as normal ram. But we are afraid Linux runtime 
> > module loading might use this region somewhere, so we also mark
> this 
> > region as save/restore. Anyway, this hasn't any side effect. 
> > Hopefully all BIOSes follow this rule.
> 
> This comment needs to go somewhere in source.... aha, it is there, 
> mostly, but without the "tricky" remark.
Ok, will add that one in code too.
> 
> > Pages (Reserved/ACPI NVS/ACPI Data) below 
> > end_pfn(x86_64)/max_low_pfn(i386) will be saved/restored by S4 

Problem with kernel recompilation

<div>
<div>
<div>
<p class="MsoNormal"><span defanged_style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Trebuchet MS'"><span class="254140814-11042006"><span class="176022914-11042006">Hi 
all,</span></span></span></p>
<p class="MsoNormal"><span defanged_style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Trebuchet MS'"><span class="254140814-11042006"><span class="176022914-11042006"></span>I have a 
</span>laptop&nbsp;<span class="254140814-11042006">which</span> doe<span class="254140814-11042006">s</span>n&rsquo;t have a brandname. It is a &lsquo;china make&rsquo; and 
I think is assembled laptop. This laptop uses a promise SATA card, to which a 
harddisk is connected. So, during booting it requires a promise SATA card 
driver, otherwise Harddisk is not detected properly. I faced this problem with 
Windows and Linux installation. I could install&nbsp; linux in 3rd 
attempt.&nbsp;<span class="254140814-11042006">Anyways now the problem is that 
when i recompiled kernel 2.6.15.4 on the same machine it gives the following 
kernel panic message:</span></span></p>
<span defanged_style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Trebuchet MS'">
<p class="MsoNormal"><span defanged_style="FONT-SIZE: 12pt; FONT-FAMILY: 'Courier New'"><span class="254140814-11042006">****************************************************************</span></span></p>
<p class="MsoNormal"><span defanged_style="FONT-SIZE: 12pt; FONT-FAMILY: 'Courier New'">Booting&nbsp; &lsquo;Fedora Core 4 
(2.16.15.4)&rsquo;<p></p></span></p>
<p class="MsoNormal"><span defanged_style="FONT-SIZE: 12pt; FONT-FAMILY: 'Courier New'">Root 
(hd0,4)<p></p></span></p>
<p class="MsoNormal"><span defanged_style="FONT-SIZE: 12pt; FONT-FAMILY: 'Courier New'">&nbsp;Filesystem type is 
ext2fs, partition type 0x83<p></p></span></p>
<p class="MsoNormal" defanged_style="MARGIN-BOTTOM: 6pt"><span defanged_style="FONT-SIZE: 12pt; FONT-FAMILY: 'Courier New'">Kernel 
/boot/vmlinuz-2.6.15.4 ro root=LABEL=/1 rootfstype=ext3 enforcing=0 rhgb 
quiet<p></p></span></p>
<p class="MsoNormal" defanged_style="MARGIN-BOTTOM: 6pt"><span defanged_style="FONT-SIZE: 12pt; FONT-FAMILY: 'Courier New'">&nbsp;[Linux-bzImage, 
setup=0x1e00, size=0x19f457]<p></p></span></p>
<p class="MsoNormal" defanged_style="MARGIN-BOTTOM: 6pt"><span defanged_style="FONT-SIZE: 12pt; FONT-FAMILY: 'Courier New'">Initrd 
/boot/initrd-2.6.15.4.img<p></p></span></p>
<p class="MsoNormal" defanged_style="MARGIN-BOTTOM: 6pt"><span defanged_style="FONT-SIZE: 12pt; FONT-FAMILY: 'Courier New'">&nbsp;[Linux-initrd  <at>  
0x1fd67000, 0x128da7 bytes ]<p></p></span></p>
<p class="MsoNormal" defanged_style="MARGIN-BOTTOM: 6pt"><span defanged_style="FONT-SIZE: 12pt; FONT-FAMILY: 'Courier New'"><p>&nbsp;</p></span></p>
<p class="MsoNormal" defanged_style="MARGIN-BOTTOM: 6pt"><span defanged_style="FONT-SIZE: 12pt; FONT-FAMILY: 'Courier New'">Uncompressing 
Linux . . . Ok, booting kernel.<p></p></span></p>
<p class="MsoNormal" defanged_style="MARGIN-BOTTOM: 6pt"><span defanged_style="FONT-SIZE: 12pt; FONT-FAMILY: 'Courier New'">PCI: Failed to 
allocate mem resource #6:20000 <at> d0000000 for 
0000:01:00.0<p></p></span></p>
<p class="MsoNormal" defanged_style="MARGIN-BOTTOM: 6pt"><span defanged_style="FONT-SIZE: 12pt; FONT-FAMILY: 'Courier New'">Red Hat nash 
version 4.2.15 starting<p></p></span></p>
<p class="MsoNormal" defanged_style="MARGIN-BOTTOM: 6pt"><span defanged_style="FONT-SIZE: 12pt; FONT-FAMILY: 'Courier New'">Mkrootdev: 
label / not found<p></p></span></p>
<p class="MsoNormal" defanged_style="MARGIN-BOTTOM: 6pt"><span defanged_style="FONT-SIZE: 12pt; FONT-FAMILY: 'Courier New'">Mount: error 2 
mounting ext3<p></p></span></p>
<p class="MsoNormal" defanged_style="MARGIN-BOTTOM: 6pt"><span defanged_style="FONT-SIZE: 12pt; FONT-FAMILY: 'Courier New'">ERROR opening 
/dev/console!!!!: 2<p></p></span></p>
<p class="MsoNormal" defanged_style="MARGIN-BOTTOM: 6pt"><span defanged_style="FONT-SIZE: 12pt; FONT-FAMILY: 'Courier New'">Error dup2&rsquo;ing 
fd of 0 to 0<p></p></span></p>
<p class="MsoNormal" defanged_style="MARGIN-BOTTOM: 6pt"><span defanged_style="FONT-SIZE: 12pt; FONT-FAMILY: 'Courier New'">Error dup2&rsquo;ing 
fd of 0 to 1<p></p></span></p>
<p class="MsoNormal" defanged_style="MARGIN-BOTTOM: 6pt"><span defanged_style="FONT-SIZE: 12pt; FONT-FAMILY: 'Courier New'">Error dup2&rsquo;ing 
fd of 0 to 2<p></p></span></p>
<p class="MsoNormal" defanged_style="MARGIN-BOTTOM: 6pt"><span defanged_style="FONT-SIZE: 12pt; FONT-FAMILY: 'Courier New'">Switchroot: 
mount failed: 22<p></p></span></p>
<p class="MsoNormal" defanged_style="MARGIN-BOTTOM: 6pt"><span defanged_style="FONT-SIZE: 12pt; FONT-FAMILY: 'Courier New'">Kernel Panic &ndash; 
not syncing: Attempted to kill init!<p></p></span></p>
<p class="MsoNormal" defanged_style="MARGIN-BOTTOM: 6pt"><span defanged_style="FONT-SIZE: 12pt; FONT-FAMILY: 'Courier New'"><p>&nbsp;<span class="254140814-11042006">******************************************************************************************************************************</span></p></span></p>
<p class="MsoNormal" defanged_style="MARGIN-BOTTOM: 6pt"><span defanged_style="FONT-SIZE: 12pt; FONT-FAMILY: 'Courier New'"><p><span class="254140814-11042006">My grub.conf looks this 
way:</span></p></span></p>
<p class="MsoNormal" defanged_style="MARGIN-BOTTOM: 6pt"><span defanged_style="FONT-SIZE: 12pt; FONT-FAMILY: 'Courier New'"><p><span class="254140814-11042006"></span></p></span>&nbsp;</p>
<span defanged_style="FONT-SIZE: 12pt; FONT-FAMILY: 'Courier New'"><p><span class="254140814-11042006">
<p>#boot=/dev/sda5</p>
<p>default=3</p>
<p>timeout=5</p>
<p>splashimage=(hd0,4)/boot/grub/splash.xpm.gz</p>
<p>hiddenmenu</p>
<p>title Fedora Core 
(2.6.11-1.1369_FC4smp)</p>
<p>root (hd0,4)</p>
<p>kernel /boot/vmlinuz-2.6.11-1.1369_FC4smp ro 
root=LABEL=/ rhgb quiet</p>
<p>initrd 
/boot/initrd-2.6.11-1.1369_FC4smp.img</p>
<p>title Fedora Core-up 
(2.6.11-1.1369_FC4)</p>
<p>root (hd0,4)</p>
<p>kernel /boot/vmlinuz-2.6.11-1.1369_FC4 ro 
root=LABEL=/ rhgb quiet</p>
<p>initrd 
/boot/initrd-2.6.11-1.1369_FC4.img</p>
<p>title Fedora Core 4 (2.6.15.4)</p>
<p>root (hd0,4)</p>
<p>kernel /boot/vmlinuz-2.6.15.4 ro root=/dev/sda5 
rhgb quiet</p>
<p>initrd /boot/initrd-2.6.15.4.img</p>
<p>title Other</p>
<p>rootnoverify (hd0,0)</p>
<p>chainloader +1</p>
<p><span class="254140814-11042006">**************************************************************************≤/span></p>
<p><span class="254140814-11042006">My fdisk&nbsp;-l 
looks like this:</span></p>
<span class="254140814-11042006">
<p>Disk /dev/sda: 60.0 GB, 60011642880 bytes</p>
<p>255 heads, 63 sectors/track, 7296 cylinders</p>
<p>Units = cylinders of 16065 * 512 = 8225280 bytes</p>
<p>Device Boot Start End Blocks Id System</p>
<p>/dev/sda1 * 1 3824 30716248+ c W95 FAT32 (LBA)</p>
<p>/dev/sda2 3825 7295 27880807+ f W95 Ext'd (LBA)</p>
<p>/dev/sda5 3825 7167 26852616 83 Linux</p>
<p>/dev/sda6 7168 7294 1020096 82 Linux swap / Solaris</p>
<p><span class="254140814-11042006">And the 
fstab entry looks like this :</span></p>
<span class="254140814-11042006">
<p># This file is edited by fstab-sync - see 'man fstab-sync' for 
details</p>
<p>LABEL=/ / ext3 defaults 1 1</p>
<p>/dev/devpts /dev/pts devpts gid=5,mode=620 0 0</p>
<p>/dev/shm /dev/shm tmpfs defaults 0 0</p>
<p>/dev/proc /proc proc defaults 0 0</p>
<p>/dev/sys /sys sysfs defaults 0 0</p>
<p>LABEL=SWAP-sda6 swap swap defaults 0 0</p>
<p>/dev/hdb /media/cdrecorder auto pamconsole,exec,noauto,managed 0 
0</p>
<p><span class="254140814-11042006">****************************************************************************************************************************</span></p>
<p><span class="254140814-11042006">What 
could be the reason for 
this??</span></p></span></span></span></p></span></span>
<p class="MsoNormal"><span defanged_style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Trebuchet MS'"></span>Regards<span class="176022914-11042006">,</span></p>
<p class="MsoNormal"><span class="176022914-11042006">Rasmit 
Ranjan Swain.</span></p>
</div>
</div>
</div>

Behavior of PCMCIA based HCD in the event of SUSPEND

Hi all,

I have the following queries regarding the power management on a PCMCIA
based USB host controller driver.

1. The SUSPEND event in the PCMCIA client driver is handled in the
following way:

In the PCMCIA layer, on a SUSPEND event, the socket layer powers off the
card. As the USB framework behavior is not allowed to suspend if lower
nodes are not already suspended, we assume that the correct behavior for
the above case should be to shut down the Host Controller.
I want to confirm whether the assumed behavior is ok or should the
behavior be something else?

2. And if the correct behavior is what we had assumed, then to implement
that we call usb_remove_hcd from the PCMCIA client driver. Is this the
correct way to do so? 
The reason for the question is it can happen that after suspending the
card, before resume card may be manually removed. In that case, there is
a possibility of usb_remove_hcd being called twice consecutively which
can cause error.
Please suggest if any better way of implementing the above.

Looking forward to you replies and thanks in advance

Thank you,
With Regards,
Kaustav Majumdar

-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
_______________________________________________
linux-usb-devel <at> lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

How to enable/power off a port

Hi all,
	I can suspend a port from the user space manualy by doing
	
	echo -n 3 > /sys/bus/usb....../power/state

Similarlly can I enable/power off a port from the user space manually ?

Please suggest.

Thanks and regards,
Rasmit Ranjan Swain.

Hi all,
	I can suspend a port from the user space manualy by doing
	
	echo -n 3 > /sys/bus/usb....../power/state

Similarlly can I enable/power off a port from the user space manually ?

Please suggest.

Thanks and regards,
Rasmit Ranjan Swain.

Re: [linux-pm] Behavior of PCMCIA based HCD in the event of SUSPEND

On Mon, 17 Apr 2006 kaustav.majumdar <at> wipro.com wrote:

> Hi all,
> 
> I have the following queries regarding the power management on a PCMCIA
> based USB host controller driver.
> 
> 1. The SUSPEND event in the PCMCIA client driver is handled in the
> following way:
> 
> In the PCMCIA layer, on a SUSPEND event, the socket layer powers off the
> card. As the USB framework behavior is not allowed to suspend if lower
> nodes are not already suspended, we assume that the correct behavior for
> the above case should be to shut down the Host Controller.
> I want to confirm whether the assumed behavior is ok or should the
> behavior be something else?

The HCD's behavior should be to suspend the host controller, with the 
understanding that factors beyond the HCD's control (such as the 
behavior of the PCMCIA client driver) may cause the host controller to be 
shut down entirely.  The HCD should not shut down the host controller 
during a suspend event.

> 2. And if the correct behavior is what we had assumed, then to implement
> that we call usb_remove_hcd from the PCMCIA client driver. Is this the
> correct way to do so? 

No.  The PCMCIA client driver should not make any assumptions about its 
clients.  All it should do is check that all the clients have been 
suspended already before allowing itself to be suspended.

> The reason for the question is it can happen that after suspending the
> card, before resume card may be manually removed. In that case, there is
> a possibility of usb_remove_hcd being called twice consecutively which
> can cause error.
> Please suggest if any better way of implementing the above.

The PCMCIA client driver should not call usb_remove_hcd at all.  Only a
USB host controller driver is allowed to call that routine.

Alan Stern

-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
linux-usb-devel <at> lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Re: How to enable/power off a port

On Mon, Apr 17, 2006 at 05:12:11PM +0530, rasmit.ranjan <at> wipro.com wrote:
> Hi all,
> 	I can suspend a port from the user space manualy by doing
> 	
> 	echo -n 3 > /sys/bus/usb....../power/state
> 
> Similarlly can I enable/power off a port from the user space manually ?

Search the archives of the linux-usb-devel mailing list for a small
program that does this through usbfs.  That's the only way to disable
power for a USB port (and then only for some hubs, not all support it.)

good luck,

greg k-h

On Mon, Apr 17, 2006 at 05:12:11PM +0530, rasmit.ranjan <at> wipro.com wrote:
> Hi all,
> 	I can suspend a port from the user space manualy by doing
> 	
> 	echo -n 3 > /sys/bus/usb....../power/state
> 
> Similarlly can I enable/power off a port from the user space manually ?

Search the archives of the linux-usb-devel mailing list for a small
program that does this through usbfs.  That's the only way to disable
power for a USB port (and then only for some hubs, not all support it.)

good luck,

greg k-h