On 2/20/14, 9:32 AM, Erinn Looney-Triggs wrote:
> Well you get a cell picture this time. Couldn't even log in. I am using btrfs at the moment as you can see from the exception.
"kernel BUG at mm/filemap.c:610"
which is
void unlock_page(struct page *page)
{
VM_BUG_ON(!PageLocked(page)); <===
unlocking a page which is not locked in a btrfs endio thread ... very little to go on here.
the subsequent btrfs errors may or may not be related; btrfs error handling is not superb.
Probably best to file a bug in RH bugzilla, and add any additional info there as you are able to obtain it.
-Eric
> Erinn
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------!
---
> From: Eric Sandeen <mailto:sandeen@xxxxxxxxxx>
> Sent: 2/19/2014 20:45
> To: Erinn Looney-Triggs <mailto:erinn.looneytriggs@xxxxxxxxx>; kernel@xxxxxxxxxxxxxxxxxxxxxxx <mailto:kernel@xxxxxxxxxxxxxxxxxxxxxxx>
> Subject: Re: Latest kernel in F20 leads to read only file system
>
> On 2/19/14, 11:19 PM, Erinn Looney-Triggs wrote:
>> On 2/19/2014 6:36 PM, Eric Sandeen wrote:
>>> On 2/19/14, 6:02 PM, Erinn Looney-Triggs wrote:
>>>> kernel-3.13.3-201.fc20.x86_64 seems to lead to file system failures
>>>> for me. Kernels < 3.13 however do not have this issue.
>>>>
>>>> At first I thought it was just file system corruption. However, after
>>>> approximately 5 reinstalls today the issue continues to surface every
>>>> time I move to the 3.13 kernel, whether using BTRFS or ext4.
>>>>
>>>> Behavior for both file systems differs slightly, ext4 complains about
>>>> a fair number of errors (sorry I don't have the specifics)
>>> We'll need those specifics. ;) dmesg and/or kernel logs in a bugzilla
>>> would probably be best.
>>>
>>> -Eric
>>>
>>
>> Ok given that I don't have a writeable file system, is there any reasonably smart way to go about getting these error messages to you other than writing them down and typing them up?
>>
>> -Erinn
>
> You wouldn't be the first to submit a cellphone photo :)
>
> -Eric
_______________________________________________
kernel mailing list
kernel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/kernel
