From: Serge V Kompan <skompan@kspu.kr.ua>
To: sisyphus@altlinux.ru
Subject: [sisyphus] error in Kernel 2.6.6
Date: Wed, 19 May 2004 11:10:28 +0300
Message-ID: <1611997062.20040519111028@kspu.kr.ua> (raw)
>> Здравствуйте!
>>
>> Пользуюсь ядром
>> uname -r
>> 2.6.6-std26-up-alt3
>>
>> В логах наблюдаю ошибки такого вида:
>> Это начинаются проблеммы с винтом или это проблеммы в ядре?
>>
>> May 17 15:08:38 shadow kernel: EXT3-fs error (device hda5):
>> ext3_readdir: direct ory #32 contains a hole at offset 0
>
> У меня oops, правда на wks версии ядра
>
> Unable to handle kernel NULL pointer dereference at virtual
> address 00000000 printing eip:
> 00000000
> *pde = 00000000
> Oops: 0000 [#1]
> CPU: 0
> EIP: 0f20:[<00000000>] Tainted: PF
> EFLAGS: 00210246 (2.6.6-wks26-up-alt1)
> EIP is at 0x0
> eax: e1812b54 ebx: c16ce89c ecx: c16ce89c edx: c16ce898
> esi: dbc557b0 edi: dbc55790 ebp: c16ce800 esp: c694fed0
> ds: 0f3b es: 0f3b ss: 0f28
> Process mc (pid: 4375, threadinfo=c694e000 task=c6e883b0)
> Stack: c016c864 dbc55790 00000000 dbc55790 ccda0114 001e808d
> ccda0114 c016cc03 dbc55790 00000000 c016d6cb dbc55790
> c5a113b8 ccda0114 e185b9e6 ccda0114 ccda0114 c16ce800
> e1850da7 ccda0114 c5a113b8 00000000 dfd5be54 c4aea3dc Call
> Trace: [dquot_release+100/128] dquot_release+0x64/0x80
> [<c016c864>] dquot_release+0x64/0x80
> [dqput+99/240] dqput+0x63/0xf0
> [<c016cc03>] dqput+0x63/0xf0
> [dquot_drop+107/128] dquot_drop+0x6b/0x80
> [<c016d6cb>] dquot_drop+0x6b/0x80
> [__crc_secpath_dup+13392436/15755453]
> ext3_dquot_drop+0x26/0x40 [ext3] [<e185b9e6>]
> ext3_dquot_drop+0x26/0x40 [ext3]
> [__crc_secpath_dup+13348341/15755453] ext3_free_inode+0x97/0x320
> [ext3] [<e1850da7>] ext3_free_inode+0x97/0x320 [ext3]
> [__crc_secpath_dup+13353229/15755453]
> ext3_delete_inode+0x8f/0xe0 [ext3] [<e18520bf>]
> ext3_delete_inode+0x8f/0xe0 [ext3]
> [__crc_secpath_dup+13353086/15755453] ext3_delete_inode+0x0/0xe0
> [ext3] [<e1852030>] ext3_delete_inode+0x0/0xe0 [ext3]
> [generic_delete_inode+147/272] generic_delete_inode+0x93/0x110
> [<c015dd93>] generic_delete_inode+0x93/0x110
> [iput+78/112] iput+0x4e/0x70
> [<c015df7e>] iput+0x4e/0x70
> [sys_unlink+242/304] sys_unlink+0xf2/0x130
> [<c0155cd2>] sys_unlink+0xf2/0x130
> [do_IRQ+197/224] do_IRQ+0xc5/0xe0
> [<c0108475>] do_IRQ+0xc5/0
Что делать? Откатится назад на 2.6.5?
--
С уважением,
Serge mailto:skompan@kspu.kr.ua
next reply other threads:[~2004-05-19 8:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-19 8:10 Serge V Kompan [this message]
2004-05-19 10:27 ` Anton Farygin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1611997062.20040519111028@kspu.kr.ua \
--to=skompan@kspu.kr.ua \
--cc=sisyphus@altlinux.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
ALT Linux Sisyphus discussions
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://lore.altlinux.org/sisyphus/0 sisyphus/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 sisyphus sisyphus/ http://lore.altlinux.org/sisyphus \
sisyphus@altlinux.ru sisyphus@altlinux.org sisyphus@lists.altlinux.org sisyphus@lists.altlinux.ru sisyphus@lists.altlinux.com sisyphus@linuxteam.iplabs.ru sisyphus@list.linux-os.ru
public-inbox-index sisyphus
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://lore.altlinux.org/org.altlinux.lists.sisyphus
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git