On Monday, 2 July 2007 18:36, David Greaves wrote:
> Rafael J. Wysocki wrote:
> > On Monday, 2 July 2007 16:32, David Greaves wrote:
> >> Rafael J. Wysocki wrote:
> >>> On Monday, 2 July 2007 12:56, Tejun Heo wrote:
> David Greaves wrote:
> >> Tejun Heo wrote:
> >>> It's really weird
Rafael J. Wysocki wrote:
On Monday, 2 July 2007 16:32, David Greaves wrote:
Rafael J. Wysocki wrote:
On Monday, 2 July 2007 12:56, Tejun Heo wrote:
David Greaves wrote:
Tejun Heo wrote:
It's really weird tho. The PHY RDY status changed events are coming
from the device which is NOT used
On Monday, 2 July 2007 16:32, David Greaves wrote:
> Rafael J. Wysocki wrote:
> > On Monday, 2 July 2007 12:56, Tejun Heo wrote:
> >> David Greaves wrote:
> Tejun Heo wrote:
> > It's really weird tho. The PHY RDY status changed events are coming
> > from the device which is NOT used
Rafael J. Wysocki wrote:
On Monday, 2 July 2007 12:56, Tejun Heo wrote:
David Greaves wrote:
Tejun Heo wrote:
It's really weird tho. The PHY RDY status changed events are coming
from the device which is NOT used while resuming
There is an obvious problem there though Tejun (the errors even
On Monday, 2 July 2007 12:56, Tejun Heo wrote:
> David Greaves wrote:
> >> Tejun Heo wrote:
> >>> It's really weird tho. The PHY RDY status changed events are coming
> >>> from the device which is NOT used while resuming
> >
> > There is an obvious problem there though Tejun (the errors even
David Greaves wrote:
>> Tejun Heo wrote:
>>> It's really weird tho. The PHY RDY status changed events are coming
>>> from the device which is NOT used while resuming
>
> There is an obvious problem there though Tejun (the errors even when sda
> isn't involved in the OS boot) - can I start
David Greaves wrote:
Tejun Heo wrote:
It's really weird tho. The PHY RDY status changed events are coming
from the device which is NOT used while resuming
There is an obvious problem there though Tejun (the errors even when sda
isn't involved in the OS boot) - can I start another thread
On Monday, 2 July 2007 12:56, Tejun Heo wrote:
David Greaves wrote:
Tejun Heo wrote:
It's really weird tho. The PHY RDY status changed events are coming
from the device which is NOT used while resuming
There is an obvious problem there though Tejun (the errors even when sda
isn't
Rafael J. Wysocki wrote:
On Monday, 2 July 2007 12:56, Tejun Heo wrote:
David Greaves wrote:
Tejun Heo wrote:
It's really weird tho. The PHY RDY status changed events are coming
from the device which is NOT used while resuming
There is an obvious problem there though Tejun (the errors even
On Monday, 2 July 2007 16:32, David Greaves wrote:
Rafael J. Wysocki wrote:
On Monday, 2 July 2007 12:56, Tejun Heo wrote:
David Greaves wrote:
Tejun Heo wrote:
It's really weird tho. The PHY RDY status changed events are coming
from the device which is NOT used while resuming
There
Rafael J. Wysocki wrote:
On Monday, 2 July 2007 16:32, David Greaves wrote:
Rafael J. Wysocki wrote:
On Monday, 2 July 2007 12:56, Tejun Heo wrote:
David Greaves wrote:
Tejun Heo wrote:
It's really weird tho. The PHY RDY status changed events are coming
from the device which is NOT used
On Monday, 2 July 2007 18:36, David Greaves wrote:
Rafael J. Wysocki wrote:
On Monday, 2 July 2007 16:32, David Greaves wrote:
Rafael J. Wysocki wrote:
On Monday, 2 July 2007 12:56, Tejun Heo wrote:
David Greaves wrote:
Tejun Heo wrote:
It's really weird tho. The PHY RDY status
David Greaves wrote:
been away, back now...
again...
David Greaves wrote:
When I move the swap/resume partition to a different controller (ie when
I broke the / mirror and used the freed space) the problem seems to go
away.
No, it's not gone away - but it's taking longer to show up.
I can
David Greaves wrote:
been away, back now...
again...
David Greaves wrote:
When I move the swap/resume partition to a different controller (ie when
I broke the / mirror and used the freed space) the problem seems to go
away.
No, it's not gone away - but it's taking longer to show up.
I can
been away, back now...
Tejun Heo wrote:
David Greaves wrote:
Tejun Heo wrote:
How reproducible is the problem? Does the problem go away or occur more
often if you change the drive you write the memory image to?
I don't think there should be activity on the sda drive during resume
itself.
been away, back now...
Tejun Heo wrote:
David Greaves wrote:
Tejun Heo wrote:
How reproducible is the problem? Does the problem go away or occur more
often if you change the drive you write the memory image to?
I don't think there should be activity on the sda drive during resume
itself.
David Greaves wrote:
> Tejun Heo wrote:
>> Your controller is repeatedly reporting PHY readiness changed exception.
>> Are you reading the system image from the device attached to the first
>> SATA port?
>
> Yes if you mean 1st as in the one after the zero-th ...
I meant the first first (0th).
David Greaves wrote:
Tejun Heo wrote:
Your controller is repeatedly reporting PHY readiness changed exception.
Are you reading the system image from the device attached to the first
SATA port?
Yes if you mean 1st as in the one after the zero-th ...
I meant the first first (0th).
How
On Tue, Jun 19, 2007 at 10:24:23AM +0100, David Greaves wrote:
> David Greaves wrote:
> so I cd'ed out of /scratch and umounted.
>
> I then tried the xfs_check.
>
> haze:~# xfs_check /dev/video_vg/video_lv
> ERROR: The filesystem has valuable metadata changes in a log which needs to
> be
Rafael J. Wysocki wrote:
This is on 2.6.22-rc5
Is the Tejun's patch
http://www.sisk.pl/kernel/hibernation_and_suspend/2.6.22-rc5/patches/30-block-always-requeue-nonfs-requests-at-the-front.patch
applied on top of that?
2.6.22-rc5 includes it.
(but, when I was testing rc4, I did apply this
Tejun Heo wrote:
Hello,
again...
David Greaves wrote:
Good :)
Now, not so good :)
Oh, crap. :-)
So I hibernated last night and resumed this morning.
Before hibernating I froze and sync'ed. After resume I thawed it. (Sorry
Dave)
Here are some photos of the screen during resume. This
On Tuesday, 19 June 2007 11:24, David Greaves wrote:
> David Greaves wrote:
> > I'm going to have to do some more testing...
> done
>
>
> > David Chinner wrote:
> >> On Mon, Jun 18, 2007 at 08:49:34AM +0100, David Greaves wrote:
> >>> David Greaves wrote:
> >>> So doing:
> >>> xfs_freeze -f
Hello,
David Greaves wrote:
>> Good :)
> Now, not so good :)
Oh, crap. :-)
> So I hibernated last night and resumed this morning.
> Before hibernating I froze and sync'ed. After resume I thawed it. (Sorry
> Dave)
>
> Here are some photos of the screen during resume. This is not 100%
>
David Greaves wrote:
I'm going to have to do some more testing...
done
David Chinner wrote:
On Mon, Jun 18, 2007 at 08:49:34AM +0100, David Greaves wrote:
David Greaves wrote:
So doing:
xfs_freeze -f /scratch
sync
echo platform > /sys/power/disk
echo disk > /sys/power/state
# resume
David Greaves wrote:
I'm going to have to do some more testing...
done
David Chinner wrote:
On Mon, Jun 18, 2007 at 08:49:34AM +0100, David Greaves wrote:
David Greaves wrote:
So doing:
xfs_freeze -f /scratch
sync
echo platform /sys/power/disk
echo disk /sys/power/state
# resume
Hello,
David Greaves wrote:
Good :)
Now, not so good :)
Oh, crap. :-)
So I hibernated last night and resumed this morning.
Before hibernating I froze and sync'ed. After resume I thawed it. (Sorry
Dave)
Here are some photos of the screen during resume. This is not 100%
reproducable -
On Tuesday, 19 June 2007 11:24, David Greaves wrote:
David Greaves wrote:
I'm going to have to do some more testing...
done
David Chinner wrote:
On Mon, Jun 18, 2007 at 08:49:34AM +0100, David Greaves wrote:
David Greaves wrote:
So doing:
xfs_freeze -f /scratch
sync
echo
Tejun Heo wrote:
Hello,
again...
David Greaves wrote:
Good :)
Now, not so good :)
Oh, crap. :-)
grin
So I hibernated last night and resumed this morning.
Before hibernating I froze and sync'ed. After resume I thawed it. (Sorry
Dave)
Here are some photos of the screen during resume.
Rafael J. Wysocki wrote:
This is on 2.6.22-rc5
Is the Tejun's patch
http://www.sisk.pl/kernel/hibernation_and_suspend/2.6.22-rc5/patches/30-block-always-requeue-nonfs-requests-at-the-front.patch
applied on top of that?
2.6.22-rc5 includes it.
(but, when I was testing rc4, I did apply this
On Tue, Jun 19, 2007 at 10:24:23AM +0100, David Greaves wrote:
David Greaves wrote:
so I cd'ed out of /scratch and umounted.
I then tried the xfs_check.
haze:~# xfs_check /dev/video_vg/video_lv
ERROR: The filesystem has valuable metadata changes in a log which needs to
be replayed.
30 matches
Mail list logo