Hi!
> Suspend damage filesystem each times on 4G SD.
> I use bluetooth. But corruption doesn't depend on it.
> I also test 2.6.21-rc4-git7 kernel. The same problem.
> 512Mb SD works normal.
Try using smaller filesystem on 4G SD, and be sure to CC SD/MMC
maintainer next time.
Hi!
Suspend damage filesystem each times on 4G SD.
I use bluetooth. But corruption doesn't depend on it.
I also test 2.6.21-rc4-git7 kernel. The same problem.
512Mb SD works normal.
Try using smaller filesystem on 4G SD, and be sure to CC SD/MMC
maintainer next time.
Suspend damage filesystem each times on 4G SD.
I use bluetooth. But corruption doesn't depend on it.
I also test 2.6.21-rc4-git7 kernel. The same problem.
512Mb SD works normal.
Pavel Machek wrote:
> Hi!
>
>> I use 2.6.20.2 kernel with ext3 rootfs on 4Gb SD on sharp zaurus sl-750
>> (PXA255).
>>
Suspend damage filesystem each times on 4G SD.
I use bluetooth. But corruption doesn't depend on it.
I also test 2.6.21-rc4-git7 kernel. The same problem.
512Mb SD works normal.
Pavel Machek wrote:
Hi!
I use 2.6.20.2 kernel with ext3 rootfs on 4Gb SD on sharp zaurus sl-750
(PXA255).
After
Hi!
> I use 2.6.20.2 kernel with ext3 rootfs on 4Gb SD on sharp zaurus sl-750
> (PXA255).
> After suspend/resume filesystem stay clean. But some i-nodes become broken.
> Some files looks like block device or pipe with strange permissions, owner
> etc.
> I'm sure that there is no bad blocks on
Hi!
I use 2.6.20.2 kernel with ext3 rootfs on 4Gb SD on sharp zaurus sl-750
(PXA255).
After suspend/resume filesystem stay clean. But some i-nodes become broken.
Some files looks like block device or pipe with strange permissions, owner
etc.
I'm sure that there is no bad blocks on SD.
On Friday, 23 March 2007 12:25, Sergey Smirnov wrote:
> It's happen only with 4G SD. I made the same test in 512Mb SD.
> After suspend/resume there is no errors on fs.
>
> If I resume PDA with 4G SD it go back to suspend after few seconds.
Well, I believe the problem is related to the SD driver
It's happen only with 4G SD. I made the same test in 512Mb SD.
After suspend/resume there is no errors on fs.
If I resume PDA with 4G SD it go back to suspend after few seconds.
Rafael J. Wysocki wrote:
> On Thursday, 22 March 2007 13:35, Sergey Smirnov wrote:
>> I use 2.6.20.2 kernel with ext3
It's happen only with 4G SD. I made the same test in 512Mb SD.
After suspend/resume there is no errors on fs.
If I resume PDA with 4G SD it go back to suspend after few seconds.
Rafael J. Wysocki wrote:
On Thursday, 22 March 2007 13:35, Sergey Smirnov wrote:
I use 2.6.20.2 kernel with ext3
On Friday, 23 March 2007 12:25, Sergey Smirnov wrote:
It's happen only with 4G SD. I made the same test in 512Mb SD.
After suspend/resume there is no errors on fs.
If I resume PDA with 4G SD it go back to suspend after few seconds.
Well, I believe the problem is related to the SD driver
On Thursday, 22 March 2007 13:35, Sergey Smirnov wrote:
> I use 2.6.20.2 kernel with ext3 rootfs on 4Gb SD on sharp zaurus sl-750
> (PXA255).
> After suspend/resume filesystem stay clean. But some i-nodes become broken.
> Some files looks like block device or pipe with strange permissions, owner
I use 2.6.20.2 kernel with ext3 rootfs on 4Gb SD on sharp zaurus sl-750
(PXA255).
After suspend/resume filesystem stay clean. But some i-nodes become broken.
Some files looks like block device or pipe with strange permissions, owner etc.
I'm sure that there is no bad blocks on SD.
I'll send any
I use 2.6.20.2 kernel with ext3 rootfs on 4Gb SD on sharp zaurus sl-750
(PXA255).
After suspend/resume filesystem stay clean. But some i-nodes become broken.
Some files looks like block device or pipe with strange permissions, owner etc.
I'm sure that there is no bad blocks on SD.
I'll send any
On Thursday, 22 March 2007 13:35, Sergey Smirnov wrote:
I use 2.6.20.2 kernel with ext3 rootfs on 4Gb SD on sharp zaurus sl-750
(PXA255).
After suspend/resume filesystem stay clean. But some i-nodes become broken.
Some files looks like block device or pipe with strange permissions, owner
14 matches
Mail list logo