[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#372465: marked as done (Kernel oops every days at 6h25 am in vfs_getattr)

Your message dated Thu, 5 Jul 2007 01:39:43 +0200
with message-id <20070705013943.45e85e85@localhost.localdomain>
and subject line Kernel oops every days at 6h25 am in vfs_getattr
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: kernel-image-2.6.8-3-686-smp
Version: 2.6.8-16sarge2

Every days at 6h25am I got the following oops on
Linux xilun 2.6.8-3-686-smp #1 SMP Thu Feb 9 07:05:39 UTC 2006 i686 GNU/Linux
Jun 6 06:25:02 localhost kernel: <1>Unable to handle kernel NULL pointer dereference at virtual address 000001a5 
Jun  6 06:25:02 localhost kernel: c016ae5e
Jun  6 06:25:02 localhost kernel: PREEMPT SMP
Jun 6 06:25:02 localhost kernel: Modules linked in: isofs ipv6 af_packet joydev snd_intel8x0 snd_ac97_codec snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd_page_alloc gameport snd_mpu401_uart snd_rawmidi snd_seq_device snd soundcore capability commoncap reiserfs ext2 ext3 jbd mbcache piix dm_mod radeon lp parport_pc parport pcspkr rtc evdev mousedev tsdev usbhid uhci_hcd pciehp shpchp pci_hotplug intel_mch_agp intel_agp agpgart e100 mii 3c59x ehci_hcd usbcore psmouse ide_cd cdrom ide_generic ide_disk ide_core sd_mod ata_piix libata scsi_mod unix font vesafb cfbcopyarea cfbimgblt cfbfillrect 
Jun  6 06:25:02 localhost kernel: CPU:    0
Jun 6 06:25:02 localhost kernel: EIP: 0060:[vfs_getattr+62/208] Not tainted 
Jun  6 06:25:02 localhost kernel: EFLAGS: 00010246   (2.6.8-3-686-smp)
Jun  6 06:25:02 localhost kernel: EIP is at vfs_getattr+0x3e/0xd0
Jun 6 06:25:02 localhost kernel: eax: 00000169 ebx: dc3f88d0 ecx: 00000000 edx: f7ae4380 Jun 6 06:25:02 localhost kernel: esi: e33b7dd0 edi: c5475f6c ebp: f7081d80 esp: c5475eec 
Jun  6 06:25:02 localhost kernel: ds: 007b   es: 007b   ss: 0068
Jun 6 06:25:02 localhost kernel: Process find (pid: 8773, threadinfo=c5474000 task=f760ee70) Jun 6 06:25:02 localhost kernel: Stack: f7081d80 e33b7dd0 d59a2000 00000000 c5475f18 0807d4e8 c5474000 c016af9c Jun 6 06:25:02 localhost kernel: f7081d80 e33b7dd0 c5475f6c e33b7dd0 f7081d80 00000000 00020000 00000008 Jun 6 06:25:02 localhost kernel: 00000000 00000001 00000000 41fce78c 00000000 43873529 00000000 000124ec 
Jun  6 06:25:02 localhost kernel: Call Trace:
Jun  6 06:25:02 localhost kernel:  [vfs_lstat+76/96] vfs_lstat+0x4c/0x60
Jun  6 06:25:02 localhost kernel:  [sys_lstat64+27/64] sys_lstat64+0x1b/0x40
Jun  6 06:25:02 localhost kernel:  [syscall_call+7/11] syscall_call+0x7/0xb
Jun 6 06:25:02 localhost kernel: Code: 8b 50 3c 85 d2 74 2f 89 7c 24 08 89 74 24 04 89 2c 24 ff 50 

There is a crontab at this time:
xilun:~# cat /etc/crontab
# /etc/crontab: system-wide crontab
# Unlike any other crontab you don't have to run the `crontab'
# command to install the new version when you edit this file.
# This file also has a username field, that none of the other crontabs do.

SHELL=/bin/sh
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin

# m h dom mon dow user  command
17 *    * * *   root    run-parts --report /etc/cron.hourly
25 6 * * * root test -x /usr/sbin/anacron || run-parts --report /etc/cron.daily 47 6 * * 7 root test -x /usr/sbin/anacron || run-parts --report /etc/cron.weekly 52 6 1 * * root test -x /usr/sbin/anacron || run-parts --report /etc/cron.monthly 
#
Running scripts of /etc/cron.daily by hand, I found this happens when /etc/cron.daily/find runs, 
and updatedb trigger the crash.

Running updatedb by hand also trigger the crash.

Here are the last syscalls as displayed by strace -f on updatedb :
[pid 19278] lstat64("replace-xx.xpm", {st_mode=S_IFREG|0644, st_size=1001, ...}) = 0 [pid 19278] lstat64("next-win-cap-up.xpm", {st_mode=S_IFREG|0644, st_size=1396, ...}) = 0 [pid 19278] lstat64("info-prev-cap-up.xpm", {st_mode=S_IFREG|0644, st_size=1067, ...}) = 0 [pid 19278] lstat64("info-prev-up.xbm", {st_mode=S_IFREG|0644, st_size=656, ...}) = 0 [pid 19278] lstat64("info-prev-up.xpm", {st_mode=S_IFREG|0644, st_size=1067, ...}) = 0 [pid 19278] lstat64("folder-dn.xbm", {st_mode=S_IFREG|0644, st_size=656, ...}) = 0 
[pid 19278] lstat64("next-win-cap-xx.xpm",  <unfinished ...>
[pid 19278] +++ killed by SIGSEGV +++
where next-win-cap-xx.xpm is in /usr/share/xemacs-21.4.17/etc/toolbar/ on a reiserfs partition 

xilun:/# mount
/dev/sda1 on / type reiserfs (rw,noatime,notail)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw)
usbfs on /proc/bus/usb type usbfs (rw)
/dev/sda8 on /home type reiserfs (rw,noatime)
/dev/sda5 on /usr type reiserfs (rw,noatime)
/dev/sda7 on /usr/local type reiserfs (rw,noatime)
/dev/sda6 on /var type reiserfs (rw,noatime)
tmpfs on /dev type tmpfs (rw,size=10M,mode=0755)

fsck.reiserfs are fine on every partitions

UPDATE:
A reboot made the problem disappeared, I'll try to find what triggers it if it shows again. 

---
Guillaume KNISPEL
Proformatique - 67 rue Voltaire - 92800 Puteaux
Tel. : 01 41 38 99 60 - Fax. : 01 41 38 99 70
gknispel@proformatique.com - http://www.proformatique.com/

--- End Message ---
--- Begin Message --- 
On Fri, Jun 09, 2006 at 03:06:04PM +0200, Guillaume Knispel wrote:
<snipp repeatable oops + ..>
> 
> fsck.reiserfs are fine on every partitions
> 
> UPDATE:
>  A reboot made the problem disappeared, I'll try to find what triggers 
> it if it shows again.

This was a RAM problem
Thanks
-- 
Guillaume KNISPEL
Proformatique - 67 rue Voltaire - 92800 Puteaux
Tel. : 01 41 38 99 60 - Fax. : 01 41 38 99 70
gknispel@proformatique.com - http://www.proformatique.com/

--- End Message ---
Reply to: