* Reiser4 for 2.6.36 kernel panic
@ 2011-03-04 18:08 Dushan Tcholich
2011-03-04 18:37 ` Edward Shishkin
0 siblings, 1 reply; 9+ messages in thread
From: Dushan Tcholich @ 2011-03-04 18:08 UTC (permalink / raw)
To: reiserfs-devel, Edward Shishkin
I captured kernel output with a mobile
camera.http://img854.imageshack.us/i/04032011.jpg/
Missing text says:
"reiser4_handle_error (fs/reiser4/vfs_ops.c:240)[foobar-42]
It happened day after I enabled KMS in kernel for ati card, didn't
notice this problem earlier.
It happened twice, once after ~12h uptime, next time after ~2h uptime.
Nothing in /var/log/messages
Have a nice day
Dushan
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Reiser4 for 2.6.36 kernel panic
2011-03-04 18:08 Reiser4 for 2.6.36 kernel panic Dushan Tcholich
@ 2011-03-04 18:37 ` Edward Shishkin
2011-03-07 18:50 ` Dushan Tcholich
0 siblings, 1 reply; 9+ messages in thread
From: Edward Shishkin @ 2011-03-04 18:37 UTC (permalink / raw)
To: Dushan Tcholich; +Cc: reiserfs-devel
On 03/04/2011 07:08 PM, Dushan Tcholich wrote:
> I captured kernel output with a mobile
> camera.http://img854.imageshack.us/i/04032011.jpg/
>
> Missing text says:
> "reiser4_handle_error (fs/reiser4/vfs_ops.c:240)[foobar-42]
>
> It happened day after I enabled KMS in kernel for ati card, didn't
> notice this problem earlier.
>
> It happened twice, once after ~12h uptime, next time after ~2h uptime.
Could you please check kernel messages more carefully:
are there complaints (IO errors, etc) of any low-level
subsystem?
Thanks,
Edward.
>
> Nothing in /var/log/messages
>
> Have a nice day
>
> Dushan
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Reiser4 for 2.6.36 kernel panic
2011-03-04 18:37 ` Edward Shishkin
@ 2011-03-07 18:50 ` Dushan Tcholich
2011-03-24 22:13 ` Dushan Tcholich
0 siblings, 1 reply; 9+ messages in thread
From: Dushan Tcholich @ 2011-03-07 18:50 UTC (permalink / raw)
To: Edward Shishkin; +Cc: reiserfs-devel
I went back to older kernel config (which worked for me atleast for a
month uptime before) and after 2 days uptime nothing bad happened,
machine is fine and nothing in logs.
This is the diff of configs (good one > with problems):
4c4
< # Tue Feb 8 18:39:42 2011
---
> # Thu Mar 3 17:35:09 2011
352c352,353
< # CONFIG_PM_RUNTIME is not set
---
> CONFIG_PM_RUNTIME=y
> CONFIG_PM_OPS=y
434a436
> CONFIG_PCIE_PME=y
738c740
< # CONFIG_FIRMWARE_IN_KERNEL is not set
---
> CONFIG_FIRMWARE_IN_KERNEL=y
1162a1165
> CONFIG_I2C_ALGOBIT=y
1339,1343c1342
< CONFIG_AGP=y
< # CONFIG_AGP_AMD64 is not set
< # CONFIG_AGP_INTEL is not set
< # CONFIG_AGP_SIS is not set
< # CONFIG_AGP_VIA is not set
---
> # CONFIG_AGP is not set
1347c1346,1355
< # CONFIG_DRM is not set
---
> CONFIG_DRM=y
> CONFIG_DRM_KMS_HELPER=y
> CONFIG_DRM_TTM=y
> # CONFIG_DRM_TDFX is not set
> # CONFIG_DRM_R128 is not set
> CONFIG_DRM_RADEON=y
> CONFIG_DRM_RADEON_KMS=y
> # CONFIG_DRM_MGA is not set
> # CONFIG_DRM_VIA is not set
> # CONFIG_DRM_SAVAGE is not set
1350c1358,1415
< # CONFIG_FB is not set
---
> CONFIG_FB=y
> # CONFIG_FIRMWARE_EDID is not set
> # CONFIG_FB_DDC is not set
> # CONFIG_FB_BOOT_VESA_SUPPORT is not set
> CONFIG_FB_CFB_FILLRECT=y
> CONFIG_FB_CFB_COPYAREA=y
> CONFIG_FB_CFB_IMAGEBLIT=y
> # CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set
> # CONFIG_FB_SYS_FILLRECT is not set
> # CONFIG_FB_SYS_COPYAREA is not set
> # CONFIG_FB_SYS_IMAGEBLIT is not set
> # CONFIG_FB_FOREIGN_ENDIAN is not set
> # CONFIG_FB_SYS_FOPS is not set
> # CONFIG_FB_SVGALIB is not set
> # CONFIG_FB_MACMODES is not set
> # CONFIG_FB_BACKLIGHT is not set
> # CONFIG_FB_MODE_HELPERS is not set
> # CONFIG_FB_TILEBLITTING is not set
>
> #
> # Frame buffer hardware drivers
> #
> # CONFIG_FB_CIRRUS is not set
> # CONFIG_FB_PM2 is not set
> # CONFIG_FB_CYBER2000 is not set
> # CONFIG_FB_ARC is not set
> # CONFIG_FB_ASILIANT is not set
> # CONFIG_FB_IMSTT is not set
> # CONFIG_FB_VGA16 is not set
> # CONFIG_FB_VESA is not set
> # CONFIG_FB_N411 is not set
> # CONFIG_FB_HGA is not set
> # CONFIG_FB_S1D13XXX is not set
> # CONFIG_FB_NVIDIA is not set
> # CONFIG_FB_RIVA is not set
> # CONFIG_FB_LE80578 is not set
> # CONFIG_FB_MATROX is not set
> # CONFIG_FB_RADEON is not set
> # CONFIG_FB_ATY128 is not set
> # CONFIG_FB_ATY is not set
> # CONFIG_FB_S3 is not set
> # CONFIG_FB_SAVAGE is not set
> # CONFIG_FB_SIS is not set
> # CONFIG_FB_VIA is not set
> # CONFIG_FB_NEOMAGIC is not set
> # CONFIG_FB_KYRO is not set
> # CONFIG_FB_3DFX is not set
> # CONFIG_FB_VOODOO1 is not set
> # CONFIG_FB_VT8623 is not set
> # CONFIG_FB_TRIDENT is not set
> # CONFIG_FB_ARK is not set
> # CONFIG_FB_PM3 is not set
> # CONFIG_FB_CARMINE is not set
> # CONFIG_FB_GEODE is not set
> # CONFIG_FB_VIRTUAL is not set
> # CONFIG_FB_METRONOME is not set
> # CONFIG_FB_MB862XX is not set
> # CONFIG_FB_BROADSHEET is not set
1364a1430,1437
> CONFIG_FRAMEBUFFER_CONSOLE=y
> # CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY is not set
> # CONFIG_FRAMEBUFFER_CONSOLE_ROTATION is not set
> # CONFIG_FB_CON_DECOR is not set
> # CONFIG_FONTS is not set
> CONFIG_FONT_8x8=y
> CONFIG_FONT_8x16=y
> # CONFIG_LOGO is not set
1564a1638
> # CONFIG_USB_SUSPEND is not set
I hope this helps
Thanks
Dushan
On Fri, Mar 4, 2011 at 7:37 PM, Edward Shishkin
<edward.shishkin@gmail.com> wrote:
> On 03/04/2011 07:08 PM, Dushan Tcholich wrote:
>>
>> I captured kernel output with a mobile
>> camera.http://img854.imageshack.us/i/04032011.jpg/
>>
>> Â Missing text says:
>> "reiser4_handle_error (fs/reiser4/vfs_ops.c:240)[foobar-42]
>>
>> It happened day after I enabled KMS in kernel for ati card, didn't
>> notice this problem earlier.
>>
>> It happened twice, once after ~12h uptime, next time after ~2h uptime.
>
>
> Could you please check kernel messages more carefully:
> are there complaints (IO errors, etc) of any low-level
> subsystem?
>
> Thanks,
> Edward.
>
>>
>> Nothing in /var/log/messages
>>
>> Have a nice day
>>
>> Dushan
>
>
--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Reiser4 for 2.6.36 kernel panic
2011-03-07 18:50 ` Dushan Tcholich
@ 2011-03-24 22:13 ` Dushan Tcholich
2011-03-24 22:34 ` Edward Shishkin
0 siblings, 1 reply; 9+ messages in thread
From: Dushan Tcholich @ 2011-03-24 22:13 UTC (permalink / raw)
To: Edward Shishkin; +Cc: reiserfs-devel
After 17 days more with old config machine stays up, no problems.
Thanks
Dushan
On Mon, Mar 7, 2011 at 7:50 PM, Dushan Tcholich <dusanc@gmail.com> wrote:
> I went back to older kernel config (which worked for me atleast for a
> month uptime before) and after 2 days uptime nothing bad happened,
> machine is fine and nothing in logs.
>
> This is the diff of configs (good one > with problems):
>
> 4c4
> < # Tue Feb 8 18:39:42 2011
> ---
>> # Thu Mar 3 17:35:09 2011
> 352c352,353
> < # CONFIG_PM_RUNTIME is not set
> ---
>> CONFIG_PM_RUNTIME=y
>> CONFIG_PM_OPS=y
> 434a436
>> CONFIG_PCIE_PME=y
> 738c740
> < # CONFIG_FIRMWARE_IN_KERNEL is not set
> ---
>> CONFIG_FIRMWARE_IN_KERNEL=y
> 1162a1165
>> CONFIG_I2C_ALGOBIT=y
> 1339,1343c1342
> < CONFIG_AGP=y
> < # CONFIG_AGP_AMD64 is not set
> < # CONFIG_AGP_INTEL is not set
> < # CONFIG_AGP_SIS is not set
> < # CONFIG_AGP_VIA is not set
> ---
>> # CONFIG_AGP is not set
> 1347c1346,1355
> < # CONFIG_DRM is not set
> ---
>> CONFIG_DRM=y
>> CONFIG_DRM_KMS_HELPER=y
>> CONFIG_DRM_TTM=y
>> # CONFIG_DRM_TDFX is not set
>> # CONFIG_DRM_R128 is not set
>> CONFIG_DRM_RADEON=y
>> CONFIG_DRM_RADEON_KMS=y
>> # CONFIG_DRM_MGA is not set
>> # CONFIG_DRM_VIA is not set
>> # CONFIG_DRM_SAVAGE is not set
> 1350c1358,1415
> < # CONFIG_FB is not set
> ---
>> CONFIG_FB=y
>> # CONFIG_FIRMWARE_EDID is not set
>> # CONFIG_FB_DDC is not set
>> # CONFIG_FB_BOOT_VESA_SUPPORT is not set
>> CONFIG_FB_CFB_FILLRECT=y
>> CONFIG_FB_CFB_COPYAREA=y
>> CONFIG_FB_CFB_IMAGEBLIT=y
>> # CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set
>> # CONFIG_FB_SYS_FILLRECT is not set
>> # CONFIG_FB_SYS_COPYAREA is not set
>> # CONFIG_FB_SYS_IMAGEBLIT is not set
>> # CONFIG_FB_FOREIGN_ENDIAN is not set
>> # CONFIG_FB_SYS_FOPS is not set
>> # CONFIG_FB_SVGALIB is not set
>> # CONFIG_FB_MACMODES is not set
>> # CONFIG_FB_BACKLIGHT is not set
>> # CONFIG_FB_MODE_HELPERS is not set
>> # CONFIG_FB_TILEBLITTING is not set
>>
>> #
>> # Frame buffer hardware drivers
>> #
>> # CONFIG_FB_CIRRUS is not set
>> # CONFIG_FB_PM2 is not set
>> # CONFIG_FB_CYBER2000 is not set
>> # CONFIG_FB_ARC is not set
>> # CONFIG_FB_ASILIANT is not set
>> # CONFIG_FB_IMSTT is not set
>> # CONFIG_FB_VGA16 is not set
>> # CONFIG_FB_VESA is not set
>> # CONFIG_FB_N411 is not set
>> # CONFIG_FB_HGA is not set
>> # CONFIG_FB_S1D13XXX is not set
>> # CONFIG_FB_NVIDIA is not set
>> # CONFIG_FB_RIVA is not set
>> # CONFIG_FB_LE80578 is not set
>> # CONFIG_FB_MATROX is not set
>> # CONFIG_FB_RADEON is not set
>> # CONFIG_FB_ATY128 is not set
>> # CONFIG_FB_ATY is not set
>> # CONFIG_FB_S3 is not set
>> # CONFIG_FB_SAVAGE is not set
>> # CONFIG_FB_SIS is not set
>> # CONFIG_FB_VIA is not set
>> # CONFIG_FB_NEOMAGIC is not set
>> # CONFIG_FB_KYRO is not set
>> # CONFIG_FB_3DFX is not set
>> # CONFIG_FB_VOODOO1 is not set
>> # CONFIG_FB_VT8623 is not set
>> # CONFIG_FB_TRIDENT is not set
>> # CONFIG_FB_ARK is not set
>> # CONFIG_FB_PM3 is not set
>> # CONFIG_FB_CARMINE is not set
>> # CONFIG_FB_GEODE is not set
>> # CONFIG_FB_VIRTUAL is not set
>> # CONFIG_FB_METRONOME is not set
>> # CONFIG_FB_MB862XX is not set
>> # CONFIG_FB_BROADSHEET is not set
> 1364a1430,1437
>> CONFIG_FRAMEBUFFER_CONSOLE=y
>> # CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY is not set
>> # CONFIG_FRAMEBUFFER_CONSOLE_ROTATION is not set
>> # CONFIG_FB_CON_DECOR is not set
>> # CONFIG_FONTS is not set
>> CONFIG_FONT_8x8=y
>> CONFIG_FONT_8x16=y
>> # CONFIG_LOGO is not set
> 1564a1638
>> # CONFIG_USB_SUSPEND is not set
>
> I hope this helps
>
> Thanks
> Dushan
>
> On Fri, Mar 4, 2011 at 7:37 PM, Edward Shishkin
> <edward.shishkin@gmail.com> wrote:
>> On 03/04/2011 07:08 PM, Dushan Tcholich wrote:
>>>
>>> I captured kernel output with a mobile
>>> camera.http://img854.imageshack.us/i/04032011.jpg/
>>>
>>> Missing text says:
>>> "reiser4_handle_error (fs/reiser4/vfs_ops.c:240)[foobar-42]
>>>
>>> It happened day after I enabled KMS in kernel for ati card, didn't
>>> notice this problem earlier.
>>>
>>> It happened twice, once after ~12h uptime, next time after ~2h uptime.
>>
>>
>> Could you please check kernel messages more carefully:
>> are there complaints (IO errors, etc) of any low-level
>> subsystem?
>>
>> Thanks,
>> Edward.
>>
>>>
>>> Nothing in /var/log/messages
>>>
>>> Have a nice day
>>>
>>> Dushan
>>
>>
>
--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Reiser4 for 2.6.36 kernel panic
2011-03-24 22:13 ` Dushan Tcholich
@ 2011-03-24 22:34 ` Edward Shishkin
2011-03-24 23:12 ` Dushan Tcholich
0 siblings, 1 reply; 9+ messages in thread
From: Edward Shishkin @ 2011-03-24 22:34 UTC (permalink / raw)
To: Dushan Tcholich; +Cc: reiserfs-devel
On 03/24/2011 11:13 PM, Dushan Tcholich wrote:
> After 17 days more with old config machine stays up, no problems.
>
Make sure you have passed "onerror=remount-ro", Ok?
> Thanks
>
> Dushan
>
> On Mon, Mar 7, 2011 at 7:50 PM, Dushan Tcholich<dusanc@gmail.com> wrote:
>> I went back to older kernel config (which worked for me atleast for a
>> month uptime before) and after 2 days uptime nothing bad happened,
>> machine is fine and nothing in logs.
>>
>> This is the diff of configs (good one> with problems):
>>
>> 4c4
>> < # Tue Feb 8 18:39:42 2011
>> ---
>>> # Thu Mar 3 17:35:09 2011
>> 352c352,353
>> < # CONFIG_PM_RUNTIME is not set
>> ---
>>> CONFIG_PM_RUNTIME=y
>>> CONFIG_PM_OPS=y
>> 434a436
>>> CONFIG_PCIE_PME=y
>> 738c740
>> < # CONFIG_FIRMWARE_IN_KERNEL is not set
>> ---
>>> CONFIG_FIRMWARE_IN_KERNEL=y
>> 1162a1165
>>> CONFIG_I2C_ALGOBIT=y
>> 1339,1343c1342
>> < CONFIG_AGP=y
>> < # CONFIG_AGP_AMD64 is not set
>> < # CONFIG_AGP_INTEL is not set
>> < # CONFIG_AGP_SIS is not set
>> < # CONFIG_AGP_VIA is not set
>> ---
>>> # CONFIG_AGP is not set
>> 1347c1346,1355
>> < # CONFIG_DRM is not set
>> ---
>>> CONFIG_DRM=y
>>> CONFIG_DRM_KMS_HELPER=y
>>> CONFIG_DRM_TTM=y
>>> # CONFIG_DRM_TDFX is not set
>>> # CONFIG_DRM_R128 is not set
>>> CONFIG_DRM_RADEON=y
>>> CONFIG_DRM_RADEON_KMS=y
>>> # CONFIG_DRM_MGA is not set
>>> # CONFIG_DRM_VIA is not set
>>> # CONFIG_DRM_SAVAGE is not set
>> 1350c1358,1415
>> < # CONFIG_FB is not set
>> ---
>>> CONFIG_FB=y
>>> # CONFIG_FIRMWARE_EDID is not set
>>> # CONFIG_FB_DDC is not set
>>> # CONFIG_FB_BOOT_VESA_SUPPORT is not set
>>> CONFIG_FB_CFB_FILLRECT=y
>>> CONFIG_FB_CFB_COPYAREA=y
>>> CONFIG_FB_CFB_IMAGEBLIT=y
>>> # CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set
>>> # CONFIG_FB_SYS_FILLRECT is not set
>>> # CONFIG_FB_SYS_COPYAREA is not set
>>> # CONFIG_FB_SYS_IMAGEBLIT is not set
>>> # CONFIG_FB_FOREIGN_ENDIAN is not set
>>> # CONFIG_FB_SYS_FOPS is not set
>>> # CONFIG_FB_SVGALIB is not set
>>> # CONFIG_FB_MACMODES is not set
>>> # CONFIG_FB_BACKLIGHT is not set
>>> # CONFIG_FB_MODE_HELPERS is not set
>>> # CONFIG_FB_TILEBLITTING is not set
>>>
>>> #
>>> # Frame buffer hardware drivers
>>> #
>>> # CONFIG_FB_CIRRUS is not set
>>> # CONFIG_FB_PM2 is not set
>>> # CONFIG_FB_CYBER2000 is not set
>>> # CONFIG_FB_ARC is not set
>>> # CONFIG_FB_ASILIANT is not set
>>> # CONFIG_FB_IMSTT is not set
>>> # CONFIG_FB_VGA16 is not set
>>> # CONFIG_FB_VESA is not set
>>> # CONFIG_FB_N411 is not set
>>> # CONFIG_FB_HGA is not set
>>> # CONFIG_FB_S1D13XXX is not set
>>> # CONFIG_FB_NVIDIA is not set
>>> # CONFIG_FB_RIVA is not set
>>> # CONFIG_FB_LE80578 is not set
>>> # CONFIG_FB_MATROX is not set
>>> # CONFIG_FB_RADEON is not set
>>> # CONFIG_FB_ATY128 is not set
>>> # CONFIG_FB_ATY is not set
>>> # CONFIG_FB_S3 is not set
>>> # CONFIG_FB_SAVAGE is not set
>>> # CONFIG_FB_SIS is not set
>>> # CONFIG_FB_VIA is not set
>>> # CONFIG_FB_NEOMAGIC is not set
>>> # CONFIG_FB_KYRO is not set
>>> # CONFIG_FB_3DFX is not set
>>> # CONFIG_FB_VOODOO1 is not set
>>> # CONFIG_FB_VT8623 is not set
>>> # CONFIG_FB_TRIDENT is not set
>>> # CONFIG_FB_ARK is not set
>>> # CONFIG_FB_PM3 is not set
>>> # CONFIG_FB_CARMINE is not set
>>> # CONFIG_FB_GEODE is not set
>>> # CONFIG_FB_VIRTUAL is not set
>>> # CONFIG_FB_METRONOME is not set
>>> # CONFIG_FB_MB862XX is not set
>>> # CONFIG_FB_BROADSHEET is not set
>> 1364a1430,1437
>>> CONFIG_FRAMEBUFFER_CONSOLE=y
>>> # CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY is not set
>>> # CONFIG_FRAMEBUFFER_CONSOLE_ROTATION is not set
>>> # CONFIG_FB_CON_DECOR is not set
>>> # CONFIG_FONTS is not set
>>> CONFIG_FONT_8x8=y
>>> CONFIG_FONT_8x16=y
>>> # CONFIG_LOGO is not set
>> 1564a1638
>>> # CONFIG_USB_SUSPEND is not set
>>
>> I hope this helps
>>
>> Thanks
>> Dushan
>>
>> On Fri, Mar 4, 2011 at 7:37 PM, Edward Shishkin
>> <edward.shishkin@gmail.com> wrote:
>>> On 03/04/2011 07:08 PM, Dushan Tcholich wrote:
>>>>
>>>> I captured kernel output with a mobile
>>>> camera.http://img854.imageshack.us/i/04032011.jpg/
>>>>
>>>> Missing text says:
>>>> "reiser4_handle_error (fs/reiser4/vfs_ops.c:240)[foobar-42]
>>>>
>>>> It happened day after I enabled KMS in kernel for ati card, didn't
>>>> notice this problem earlier.
>>>>
>>>> It happened twice, once after ~12h uptime, next time after ~2h uptime.
>>>
>>>
>>> Could you please check kernel messages more carefully:
>>> are there complaints (IO errors, etc) of any low-level
>>> subsystem?
>>>
>>> Thanks,
>>> Edward.
>>>
>>>>
>>>> Nothing in /var/log/messages
>>>>
>>>> Have a nice day
>>>>
>>>> Dushan
>>>
>>>
>>
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Reiser4 for 2.6.36 kernel panic
2011-03-24 22:34 ` Edward Shishkin
@ 2011-03-24 23:12 ` Dushan Tcholich
2011-03-24 23:15 ` Dushan Tcholich
0 siblings, 1 reply; 9+ messages in thread
From: Dushan Tcholich @ 2011-03-24 23:12 UTC (permalink / raw)
To: Edward Shishkin; +Cc: reiserfs-devel
cat /etc/fstab | grep "#" -v
/dev/sda1 /boot ext2 noauto,noatime 1 2
/dev/md1 none swap sw 0 0
/dev/sda2 / reiser4
noatime,onerror=remount-ro 0 0
/dev/md126 /mnt/media reiser4
noatime,users,onerror=remount-ro 0 0
/dev/md127 /usr/portage reiser4
noatime,onerror=remount-ro 0 0
shm /dev/shm tmpfs
nodev,nosuid,noexec 0 0
This is fstab for last 2 weeks:D
On Thu, Mar 24, 2011 at 11:34 PM, Edward Shishkin
<edward.shishkin@gmail.com> wrote:
> On 03/24/2011 11:13 PM, Dushan Tcholich wrote:
>>
>> After 17 days more with old config machine stays up, no problems.
>>
>
> Make sure you have passed "onerror=remount-ro", Ok?
>
>
>> Thanks
>>
>> Dushan
>>
>> On Mon, Mar 7, 2011 at 7:50 PM, Dushan Tcholich<dusanc@gmail.com> wrote:
>>>
>>> I went back to older kernel config (which worked for me atleast for a
>>> month uptime before) and after 2 days uptime nothing bad happened,
>>> machine is fine and nothing in logs.
>>>
>>> This is the diff of configs (good one> with problems):
>>>
>>> 4c4
>>> < # Tue Feb 8 18:39:42 2011
>>> ---
>>>>
>>>> # Thu Mar 3 17:35:09 2011
>>>
>>> 352c352,353
>>> < # CONFIG_PM_RUNTIME is not set
>>> ---
>>>>
>>>> CONFIG_PM_RUNTIME=y
>>>> CONFIG_PM_OPS=y
>>>
>>> 434a436
>>>>
>>>> CONFIG_PCIE_PME=y
>>>
>>> 738c740
>>> < # CONFIG_FIRMWARE_IN_KERNEL is not set
>>> ---
>>>>
>>>> CONFIG_FIRMWARE_IN_KERNEL=y
>>>
>>> 1162a1165
>>>>
>>>> CONFIG_I2C_ALGOBIT=y
>>>
>>> 1339,1343c1342
>>> < CONFIG_AGP=y
>>> < # CONFIG_AGP_AMD64 is not set
>>> < # CONFIG_AGP_INTEL is not set
>>> < # CONFIG_AGP_SIS is not set
>>> < # CONFIG_AGP_VIA is not set
>>> ---
>>>>
>>>> # CONFIG_AGP is not set
>>>
>>> 1347c1346,1355
>>> < # CONFIG_DRM is not set
>>> ---
>>>>
>>>> CONFIG_DRM=y
>>>> CONFIG_DRM_KMS_HELPER=y
>>>> CONFIG_DRM_TTM=y
>>>> # CONFIG_DRM_TDFX is not set
>>>> # CONFIG_DRM_R128 is not set
>>>> CONFIG_DRM_RADEON=y
>>>> CONFIG_DRM_RADEON_KMS=y
>>>> # CONFIG_DRM_MGA is not set
>>>> # CONFIG_DRM_VIA is not set
>>>> # CONFIG_DRM_SAVAGE is not set
>>>
>>> 1350c1358,1415
>>> < # CONFIG_FB is not set
>>> ---
>>>>
>>>> CONFIG_FB=y
>>>> # CONFIG_FIRMWARE_EDID is not set
>>>> # CONFIG_FB_DDC is not set
>>>> # CONFIG_FB_BOOT_VESA_SUPPORT is not set
>>>> CONFIG_FB_CFB_FILLRECT=y
>>>> CONFIG_FB_CFB_COPYAREA=y
>>>> CONFIG_FB_CFB_IMAGEBLIT=y
>>>> # CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set
>>>> # CONFIG_FB_SYS_FILLRECT is not set
>>>> # CONFIG_FB_SYS_COPYAREA is not set
>>>> # CONFIG_FB_SYS_IMAGEBLIT is not set
>>>> # CONFIG_FB_FOREIGN_ENDIAN is not set
>>>> # CONFIG_FB_SYS_FOPS is not set
>>>> # CONFIG_FB_SVGALIB is not set
>>>> # CONFIG_FB_MACMODES is not set
>>>> # CONFIG_FB_BACKLIGHT is not set
>>>> # CONFIG_FB_MODE_HELPERS is not set
>>>> # CONFIG_FB_TILEBLITTING is not set
>>>>
>>>> #
>>>> # Frame buffer hardware drivers
>>>> #
>>>> # CONFIG_FB_CIRRUS is not set
>>>> # CONFIG_FB_PM2 is not set
>>>> # CONFIG_FB_CYBER2000 is not set
>>>> # CONFIG_FB_ARC is not set
>>>> # CONFIG_FB_ASILIANT is not set
>>>> # CONFIG_FB_IMSTT is not set
>>>> # CONFIG_FB_VGA16 is not set
>>>> # CONFIG_FB_VESA is not set
>>>> # CONFIG_FB_N411 is not set
>>>> # CONFIG_FB_HGA is not set
>>>> # CONFIG_FB_S1D13XXX is not set
>>>> # CONFIG_FB_NVIDIA is not set
>>>> # CONFIG_FB_RIVA is not set
>>>> # CONFIG_FB_LE80578 is not set
>>>> # CONFIG_FB_MATROX is not set
>>>> # CONFIG_FB_RADEON is not set
>>>> # CONFIG_FB_ATY128 is not set
>>>> # CONFIG_FB_ATY is not set
>>>> # CONFIG_FB_S3 is not set
>>>> # CONFIG_FB_SAVAGE is not set
>>>> # CONFIG_FB_SIS is not set
>>>> # CONFIG_FB_VIA is not set
>>>> # CONFIG_FB_NEOMAGIC is not set
>>>> # CONFIG_FB_KYRO is not set
>>>> # CONFIG_FB_3DFX is not set
>>>> # CONFIG_FB_VOODOO1 is not set
>>>> # CONFIG_FB_VT8623 is not set
>>>> # CONFIG_FB_TRIDENT is not set
>>>> # CONFIG_FB_ARK is not set
>>>> # CONFIG_FB_PM3 is not set
>>>> # CONFIG_FB_CARMINE is not set
>>>> # CONFIG_FB_GEODE is not set
>>>> # CONFIG_FB_VIRTUAL is not set
>>>> # CONFIG_FB_METRONOME is not set
>>>> # CONFIG_FB_MB862XX is not set
>>>> # CONFIG_FB_BROADSHEET is not set
>>>
>>> 1364a1430,1437
>>>>
>>>> CONFIG_FRAMEBUFFER_CONSOLE=y
>>>> # CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY is not set
>>>> # CONFIG_FRAMEBUFFER_CONSOLE_ROTATION is not set
>>>> # CONFIG_FB_CON_DECOR is not set
>>>> # CONFIG_FONTS is not set
>>>> CONFIG_FONT_8x8=y
>>>> CONFIG_FONT_8x16=y
>>>> # CONFIG_LOGO is not set
>>>
>>> 1564a1638
>>>>
>>>> # CONFIG_USB_SUSPEND is not set
>>>
>>> I hope this helps
>>>
>>> Thanks
>>> Dushan
>>>
>>> On Fri, Mar 4, 2011 at 7:37 PM, Edward Shishkin
>>> <edward.shishkin@gmail.com> wrote:
>>>>
>>>> On 03/04/2011 07:08 PM, Dushan Tcholich wrote:
>>>>>
>>>>> I captured kernel output with a mobile
>>>>> camera.http://img854.imageshack.us/i/04032011.jpg/
>>>>>
>>>>> Missing text says:
>>>>> "reiser4_handle_error (fs/reiser4/vfs_ops.c:240)[foobar-42]
>>>>>
>>>>> It happened day after I enabled KMS in kernel for ati card, didn't
>>>>> notice this problem earlier.
>>>>>
>>>>> It happened twice, once after ~12h uptime, next time after ~2h uptime.
>>>>
>>>>
>>>> Could you please check kernel messages more carefully:
>>>> are there complaints (IO errors, etc) of any low-level
>>>> subsystem?
>>>>
>>>> Thanks,
>>>> Edward.
>>>>
>>>>>
>>>>> Nothing in /var/log/messages
>>>>>
>>>>> Have a nice day
>>>>>
>>>>> Dushan
>>>>
>>>>
>>>
>
>
--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Reiser4 for 2.6.36 kernel panic
2011-03-24 23:12 ` Dushan Tcholich
@ 2011-03-24 23:15 ` Dushan Tcholich
2011-03-25 1:48 ` Edward Shishkin
0 siblings, 1 reply; 9+ messages in thread
From: Dushan Tcholich @ 2011-03-24 23:15 UTC (permalink / raw)
To: Edward Shishkin; +Cc: reiserfs-devel
Btw. I found something suspicious in my /var/log/messages
Mar 24 17:03:48 krshina3 kernel: [18656.820109] ata1: lost interrupt
(Status 0x50)
Mar 24 17:03:48 krshina3 kernel: [18656.820128] ata1.00: exception
Emask 0x10 SAct 0x0 SErr 0x4050002 action 0xe frozen
Mar 24 17:03:48 krshina3 kernel: [18656.820133] ata1.00: SError: {
RecovComm PHYRdyChg CommWake DevExch }
Mar 24 17:03:48 krshina3 kernel: [18656.820137] ata1.00: failed
command: WRITE DMA
Mar 24 17:03:48 krshina3 kernel: [18656.820145] ata1.00: cmd
ca/00:10:18:0e:03/00:00:00:00:00/e1 tag 0 dma 8192 out
Mar 24 17:03:48 krshina3 kernel: [18656.820146] res
40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x14 (ATA bus error)
Mar 24 17:03:48 krshina3 kernel: [18656.820150] ata1.00: status: { DRDY }
Mar 24 17:03:48 krshina3 kernel: [18656.820161] ata1.00: hard resetting link
Mar 24 17:03:48 krshina3 kernel: [18657.544072] ata1.01: hard resetting link
Mar 24 17:03:48 krshina3 kernel: [18658.020149] ata1.00: SATA link up
3.0 Gbps (SStatus 123 SControl 300)
Mar 24 17:03:50 krshina3 kernel: [18658.020161] ata1.01: SATA link
down (SStatus 4 SControl 300)
Mar 24 17:03:50 krshina3 kernel: [18658.036242] ata1.00: configured for UDMA/133
Mar 24 17:03:50 krshina3 kernel: [18658.036248] ata1.00: device
reported invalid CHS sector 0
Mar 24 17:03:50 krshina3 kernel: [18658.036257] ata1: EH complete
But it doesn't make kernel panic, system continues to work 24/7.
Thanks
Dushan
On Fri, Mar 25, 2011 at 12:12 AM, Dushan Tcholich <dusanc@gmail.com> wrote:
> cat /etc/fstab | grep "#" -v
>
>
> /dev/sda1 /boot ext2 noauto,noatime 1 2
> /dev/md1 none swap sw 0 0
> /dev/sda2 / reiser4
> noatime,onerror=remount-ro 0 0
> /dev/md126 /mnt/media reiser4
> noatime,users,onerror=remount-ro 0 0
> /dev/md127 /usr/portage reiser4
> noatime,onerror=remount-ro 0 0
>
> shm /dev/shm tmpfs
> nodev,nosuid,noexec 0 0
>
> This is fstab for last 2 weeks:D
>
> On Thu, Mar 24, 2011 at 11:34 PM, Edward Shishkin
> <edward.shishkin@gmail.com> wrote:
>> On 03/24/2011 11:13 PM, Dushan Tcholich wrote:
>>>
>>> After 17 days more with old config machine stays up, no problems.
>>>
>>
>> Make sure you have passed "onerror=remount-ro", Ok?
>>
>>
>>> Thanks
>>>
>>> Dushan
>>>
>>> On Mon, Mar 7, 2011 at 7:50 PM, Dushan Tcholich<dusanc@gmail.com> wrote:
>>>>
>>>> I went back to older kernel config (which worked for me atleast for a
>>>> month uptime before) and after 2 days uptime nothing bad happened,
>>>> machine is fine and nothing in logs.
>>>>
>>>> This is the diff of configs (good one> with problems):
>>>>
>>>> 4c4
>>>> < # Tue Feb 8 18:39:42 2011
>>>> ---
>>>>>
>>>>> # Thu Mar 3 17:35:09 2011
>>>>
>>>> 352c352,353
>>>> < # CONFIG_PM_RUNTIME is not set
>>>> ---
>>>>>
>>>>> CONFIG_PM_RUNTIME=y
>>>>> CONFIG_PM_OPS=y
>>>>
>>>> 434a436
>>>>>
>>>>> CONFIG_PCIE_PME=y
>>>>
>>>> 738c740
>>>> < # CONFIG_FIRMWARE_IN_KERNEL is not set
>>>> ---
>>>>>
>>>>> CONFIG_FIRMWARE_IN_KERNEL=y
>>>>
>>>> 1162a1165
>>>>>
>>>>> CONFIG_I2C_ALGOBIT=y
>>>>
>>>> 1339,1343c1342
>>>> < CONFIG_AGP=y
>>>> < # CONFIG_AGP_AMD64 is not set
>>>> < # CONFIG_AGP_INTEL is not set
>>>> < # CONFIG_AGP_SIS is not set
>>>> < # CONFIG_AGP_VIA is not set
>>>> ---
>>>>>
>>>>> # CONFIG_AGP is not set
>>>>
>>>> 1347c1346,1355
>>>> < # CONFIG_DRM is not set
>>>> ---
>>>>>
>>>>> CONFIG_DRM=y
>>>>> CONFIG_DRM_KMS_HELPER=y
>>>>> CONFIG_DRM_TTM=y
>>>>> # CONFIG_DRM_TDFX is not set
>>>>> # CONFIG_DRM_R128 is not set
>>>>> CONFIG_DRM_RADEON=y
>>>>> CONFIG_DRM_RADEON_KMS=y
>>>>> # CONFIG_DRM_MGA is not set
>>>>> # CONFIG_DRM_VIA is not set
>>>>> # CONFIG_DRM_SAVAGE is not set
>>>>
>>>> 1350c1358,1415
>>>> < # CONFIG_FB is not set
>>>> ---
>>>>>
>>>>> CONFIG_FB=y
>>>>> # CONFIG_FIRMWARE_EDID is not set
>>>>> # CONFIG_FB_DDC is not set
>>>>> # CONFIG_FB_BOOT_VESA_SUPPORT is not set
>>>>> CONFIG_FB_CFB_FILLRECT=y
>>>>> CONFIG_FB_CFB_COPYAREA=y
>>>>> CONFIG_FB_CFB_IMAGEBLIT=y
>>>>> # CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set
>>>>> # CONFIG_FB_SYS_FILLRECT is not set
>>>>> # CONFIG_FB_SYS_COPYAREA is not set
>>>>> # CONFIG_FB_SYS_IMAGEBLIT is not set
>>>>> # CONFIG_FB_FOREIGN_ENDIAN is not set
>>>>> # CONFIG_FB_SYS_FOPS is not set
>>>>> # CONFIG_FB_SVGALIB is not set
>>>>> # CONFIG_FB_MACMODES is not set
>>>>> # CONFIG_FB_BACKLIGHT is not set
>>>>> # CONFIG_FB_MODE_HELPERS is not set
>>>>> # CONFIG_FB_TILEBLITTING is not set
>>>>>
>>>>> #
>>>>> # Frame buffer hardware drivers
>>>>> #
>>>>> # CONFIG_FB_CIRRUS is not set
>>>>> # CONFIG_FB_PM2 is not set
>>>>> # CONFIG_FB_CYBER2000 is not set
>>>>> # CONFIG_FB_ARC is not set
>>>>> # CONFIG_FB_ASILIANT is not set
>>>>> # CONFIG_FB_IMSTT is not set
>>>>> # CONFIG_FB_VGA16 is not set
>>>>> # CONFIG_FB_VESA is not set
>>>>> # CONFIG_FB_N411 is not set
>>>>> # CONFIG_FB_HGA is not set
>>>>> # CONFIG_FB_S1D13XXX is not set
>>>>> # CONFIG_FB_NVIDIA is not set
>>>>> # CONFIG_FB_RIVA is not set
>>>>> # CONFIG_FB_LE80578 is not set
>>>>> # CONFIG_FB_MATROX is not set
>>>>> # CONFIG_FB_RADEON is not set
>>>>> # CONFIG_FB_ATY128 is not set
>>>>> # CONFIG_FB_ATY is not set
>>>>> # CONFIG_FB_S3 is not set
>>>>> # CONFIG_FB_SAVAGE is not set
>>>>> # CONFIG_FB_SIS is not set
>>>>> # CONFIG_FB_VIA is not set
>>>>> # CONFIG_FB_NEOMAGIC is not set
>>>>> # CONFIG_FB_KYRO is not set
>>>>> # CONFIG_FB_3DFX is not set
>>>>> # CONFIG_FB_VOODOO1 is not set
>>>>> # CONFIG_FB_VT8623 is not set
>>>>> # CONFIG_FB_TRIDENT is not set
>>>>> # CONFIG_FB_ARK is not set
>>>>> # CONFIG_FB_PM3 is not set
>>>>> # CONFIG_FB_CARMINE is not set
>>>>> # CONFIG_FB_GEODE is not set
>>>>> # CONFIG_FB_VIRTUAL is not set
>>>>> # CONFIG_FB_METRONOME is not set
>>>>> # CONFIG_FB_MB862XX is not set
>>>>> # CONFIG_FB_BROADSHEET is not set
>>>>
>>>> 1364a1430,1437
>>>>>
>>>>> CONFIG_FRAMEBUFFER_CONSOLE=y
>>>>> # CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY is not set
>>>>> # CONFIG_FRAMEBUFFER_CONSOLE_ROTATION is not set
>>>>> # CONFIG_FB_CON_DECOR is not set
>>>>> # CONFIG_FONTS is not set
>>>>> CONFIG_FONT_8x8=y
>>>>> CONFIG_FONT_8x16=y
>>>>> # CONFIG_LOGO is not set
>>>>
>>>> 1564a1638
>>>>>
>>>>> # CONFIG_USB_SUSPEND is not set
>>>>
>>>> I hope this helps
>>>>
>>>> Thanks
>>>> Dushan
>>>>
>>>> On Fri, Mar 4, 2011 at 7:37 PM, Edward Shishkin
>>>> <edward.shishkin@gmail.com> wrote:
>>>>>
>>>>> On 03/04/2011 07:08 PM, Dushan Tcholich wrote:
>>>>>>
>>>>>> I captured kernel output with a mobile
>>>>>> camera.http://img854.imageshack.us/i/04032011.jpg/
>>>>>>
>>>>>> Missing text says:
>>>>>> "reiser4_handle_error (fs/reiser4/vfs_ops.c:240)[foobar-42]
>>>>>>
>>>>>> It happened day after I enabled KMS in kernel for ati card, didn't
>>>>>> notice this problem earlier.
>>>>>>
>>>>>> It happened twice, once after ~12h uptime, next time after ~2h uptime.
>>>>>
>>>>>
>>>>> Could you please check kernel messages more carefully:
>>>>> are there complaints (IO errors, etc) of any low-level
>>>>> subsystem?
>>>>>
>>>>> Thanks,
>>>>> Edward.
>>>>>
>>>>>>
>>>>>> Nothing in /var/log/messages
>>>>>>
>>>>>> Have a nice day
>>>>>>
>>>>>> Dushan
>>>>>
>>>>>
>>>>
>>
>>
>
--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Reiser4 for 2.6.36 kernel panic
2011-03-24 23:15 ` Dushan Tcholich
@ 2011-03-25 1:48 ` Edward Shishkin
2011-03-25 7:16 ` Dushan Tcholich
0 siblings, 1 reply; 9+ messages in thread
From: Edward Shishkin @ 2011-03-25 1:48 UTC (permalink / raw)
To: Dushan Tcholich; +Cc: reiserfs-devel
On 03/25/2011 12:15 AM, Dushan Tcholich wrote:
> Btw. I found something suspicious in my /var/log/messages
>
> Mar 24 17:03:48 krshina3 kernel: [18656.820109] ata1: lost interrupt
> (Status 0x50)
> Mar 24 17:03:48 krshina3 kernel: [18656.820128] ata1.00: exception
> Emask 0x10 SAct 0x0 SErr 0x4050002 action 0xe frozen
> Mar 24 17:03:48 krshina3 kernel: [18656.820133] ata1.00: SError: {
> RecovComm PHYRdyChg CommWake DevExch }
> Mar 24 17:03:48 krshina3 kernel: [18656.820137] ata1.00: failed
> command: WRITE DMA
> Mar 24 17:03:48 krshina3 kernel: [18656.820145] ata1.00: cmd
> ca/00:10:18:0e:03/00:00:00:00:00/e1 tag 0 dma 8192 out
> Mar 24 17:03:48 krshina3 kernel: [18656.820146] res
> 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x14 (ATA bus error)
> Mar 24 17:03:48 krshina3 kernel: [18656.820150] ata1.00: status: { DRDY }
> Mar 24 17:03:48 krshina3 kernel: [18656.820161] ata1.00: hard resetting link
> Mar 24 17:03:48 krshina3 kernel: [18657.544072] ata1.01: hard resetting link
> Mar 24 17:03:48 krshina3 kernel: [18658.020149] ata1.00: SATA link up
> 3.0 Gbps (SStatus 123 SControl 300)
> Mar 24 17:03:50 krshina3 kernel: [18658.020161] ata1.01: SATA link
> down (SStatus 4 SControl 300)
> Mar 24 17:03:50 krshina3 kernel: [18658.036242] ata1.00: configured for UDMA/133
> Mar 24 17:03:50 krshina3 kernel: [18658.036248] ata1.00: device
> reported invalid CHS sector 0
> Mar 24 17:03:50 krshina3 kernel: [18658.036257] ata1: EH complete
>
> But it doesn't make kernel panic,
It shouldn't panic with such mount options.
At the "moment of truth" your system will become read-only..
system continues to work 24/7.
>
> Thanks
>
> Dushan
>
> On Fri, Mar 25, 2011 at 12:12 AM, Dushan Tcholich<dusanc@gmail.com> wrote:
>> cat /etc/fstab | grep "#" -v
>>
>>
>> /dev/sda1 /boot ext2 noauto,noatime 1 2
>> /dev/md1 none swap sw 0 0
>> /dev/sda2 / reiser4
>> noatime,onerror=remount-ro 0 0
>> /dev/md126 /mnt/media reiser4
>> noatime,users,onerror=remount-ro 0 0
>> /dev/md127 /usr/portage reiser4
>> noatime,onerror=remount-ro 0 0
>>
>> shm /dev/shm tmpfs
>> nodev,nosuid,noexec 0 0
>>
>> This is fstab for last 2 weeks:D
>>
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Reiser4 for 2.6.36 kernel panic
2011-03-25 1:48 ` Edward Shishkin
@ 2011-03-25 7:16 ` Dushan Tcholich
0 siblings, 0 replies; 9+ messages in thread
From: Dushan Tcholich @ 2011-03-25 7:16 UTC (permalink / raw)
To: Edward Shishkin; +Cc: reiserfs-devel
Yeah, well all I wanted to report that it hadn't become read-only in
last 17 days :D
When I said it's fine, maybe I should have clarified it :D
On Fri, Mar 25, 2011 at 2:48 AM, Edward Shishkin
<edward.shishkin@gmail.com> wrote:
> On 03/25/2011 12:15 AM, Dushan Tcholich wrote:
>>
>> Btw. I found something suspicious in my /var/log/messages
>>
>> Mar 24 17:03:48 krshina3 kernel: [18656.820109] ata1: lost interrupt
>> (Status 0x50)
>> Mar 24 17:03:48 krshina3 kernel: [18656.820128] ata1.00: exception
>> Emask 0x10 SAct 0x0 SErr 0x4050002 action 0xe frozen
>> Mar 24 17:03:48 krshina3 kernel: [18656.820133] ata1.00: SError: {
>> RecovComm PHYRdyChg CommWake DevExch }
>> Mar 24 17:03:48 krshina3 kernel: [18656.820137] ata1.00: failed
>> command: WRITE DMA
>> Mar 24 17:03:48 krshina3 kernel: [18656.820145] ata1.00: cmd
>> ca/00:10:18:0e:03/00:00:00:00:00/e1 tag 0 dma 8192 out
>> Mar 24 17:03:48 krshina3 kernel: [18656.820146] res
>> 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x14 (ATA bus error)
>> Mar 24 17:03:48 krshina3 kernel: [18656.820150] ata1.00: status: { DRDY }
>> Mar 24 17:03:48 krshina3 kernel: [18656.820161] ata1.00: hard resetting
>> link
>> Mar 24 17:03:48 krshina3 kernel: [18657.544072] ata1.01: hard resetting
>> link
>> Mar 24 17:03:48 krshina3 kernel: [18658.020149] ata1.00: SATA link up
>> 3.0 Gbps (SStatus 123 SControl 300)
>> Mar 24 17:03:50 krshina3 kernel: [18658.020161] ata1.01: SATA link
>> down (SStatus 4 SControl 300)
>> Mar 24 17:03:50 krshina3 kernel: [18658.036242] ata1.00: configured for
>> UDMA/133
>> Mar 24 17:03:50 krshina3 kernel: [18658.036248] ata1.00: device
>> reported invalid CHS sector 0
>> Mar 24 17:03:50 krshina3 kernel: [18658.036257] ata1: EH complete
>>
>> But it doesn't make kernel panic,
>
>
> It shouldn't panic with such mount options.
> At the "moment of truth" your system will become read-only..
>
>
> system continues to work 24/7.
>>
>> Thanks
>>
>> Dushan
>>
>> On Fri, Mar 25, 2011 at 12:12 AM, Dushan Tcholich<dusanc@gmail.com>
>> wrote:
>>>
>>> cat /etc/fstab | grep "#" -v
>>>
>>>
>>> /dev/sda1 /boot ext2 noauto,noatime 1
>>> 2
>>> /dev/md1 none swap sw 0
>>> 0
>>> /dev/sda2 / reiser4
>>> noatime,onerror=remount-ro 0 0
>>> /dev/md126 /mnt/media reiser4
>>> noatime,users,onerror=remount-ro 0 0
>>> /dev/md127 /usr/portage reiser4
>>> noatime,onerror=remount-ro 0 0
>>>
>>> shm /dev/shm tmpfs
>>> nodev,nosuid,noexec 0 0
>>>
>>> This is fstab for last 2 weeks:D
>>>
>
--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2011-03-25 7:16 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-03-04 18:08 Reiser4 for 2.6.36 kernel panic Dushan Tcholich
2011-03-04 18:37 ` Edward Shishkin
2011-03-07 18:50 ` Dushan Tcholich
2011-03-24 22:13 ` Dushan Tcholich
2011-03-24 22:34 ` Edward Shishkin
2011-03-24 23:12 ` Dushan Tcholich
2011-03-24 23:15 ` Dushan Tcholich
2011-03-25 1:48 ` Edward Shishkin
2011-03-25 7:16 ` Dushan Tcholich
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).