Software or Hardware error?
Hi,
I´ve found the following message on the console and in the logs:
> Nov 5 04:49:00 prometheus kernel: kblockd/0: page allocation failure. order:0, mode:0x21
> Nov 5 04:49:00 prometheus kernel:
> Nov 5 04:49:00 prometheus kernel: Call Trace:<ffffffff801561b0>{__alloc_pages+816} <ffffffff8016d073>{alloc_page_interleave+67}
> Nov 5 04:49:00 prometheus kernel: <ffffffff801561f0>{__get_free_pages+16} <ffffffff80159873>{kmem_getpages+35}
> Nov 5 04:49:00 prometheus kernel: <ffffffff8011e4f3>{dma_map_sg+691} <ffffffff8015a80b>{cache_grow+187}
> Nov 5 04:49:00 prometheus kernel: <ffffffff8015aa50>{cache_alloc_refill+416} <ffffffff80208780>{as_work_handler+0}
> Nov 5 04:49:00 prometheus kernel: <ffffffff8015ad26>{kmem_cache_alloc+54} <ffffffff8020bf44>{__scsi_get_command+36}
> Nov 5 04:49:00 prometheus kernel: <ffffffff8020bfc5>{scsi_get_command+21} <ffffffff80211538>{scsi_prep_fn+264}
> Nov 5 04:49:00 prometheus kernel: <ffffffff801ff6f8>{elv_next_request+72} <ffffffff8021164a>{scsi_request_fn+74}
> Nov 5 04:49:00 prometheus kernel: <ffffffff802087b6>{as_work_handler+54} <ffffffff80145ffc>{worker_thread+476}
> Nov 5 04:49:00 prometheus kernel: <ffffffff80131d50>{default_wake_function+0} <ffffffff80131d50>{default_wake_function+0}
> Nov 5 04:49:00 prometheus kernel: <ffffffff8014a540>{keventd_create_kthread+0} <ffffffff80145e20>{worker_thread+0}
> Nov 5 04:49:00 prometheus kernel: <ffffffff8014a540>{keventd_create_kthread+0} <ffffffff8014a502>{kthread+146}
> Nov 5 04:49:00 prometheus kernel: <ffffffff801112ab>{child_rip+8} <ffffffff8014a540>{keventd_create_kthread+0}
> Nov 5 04:49:00 prometheus kernel: <ffffffff8014a470>{kthread+0} <ffffffff801112a3>{child_rip+0}
What´s kblockd? There are kblockd/0 and kblockd/1 in the process list.
Does this error indicate a hardware or a software problem?
Anything I can/should do?
Reference:
Uptime was 146 days yesterday, so the error occured after 140 days, and
the system is supposed to have been idle at that time except for
probably running clamscan across the filesystems. I rebooted the system
and forced a check on the filesystems; no errors were found. No problems
have been noted in the 6 days after the error messages showed up. If
there´s a problem with the disks, the RAID controller is supposed to
beep, but it doesn´t.
kernel 2.6.9 SMP (dual Opteron maschine)
> 0000:02:02.0 SCSI storage controller: Adaptec ASC-29320A U320 (rev 10)
> 0000:03:01.0 RAID bus controller: ICP Vortex Computersysteme GmbH GDT NEWRX
The Adaptec is for the tape drive only:
> Attached devices:
> Host: scsi0 Channel: 00 Id: 00 Lun: 00
> Vendor: ICP Model: Host Drive #00 Rev:
> Type: Direct-Access ANSI SCSI revision: 02
> Host: scsi1 Channel: 00 Id: 00 Lun: 00
> Vendor: EXABYTE Model: VXA 1x10 1U Rev: A102
> Type: Medium Changer ANSI SCSI revision: 04
> Host: scsi1 Channel: 00 Id: 01 Lun: 00
> Vendor: EXABYTE Model: VXA-2 Rev: 100E
> Type: Sequential-Access ANSI SCSI revision: 02
> # /etc/fstab: static file system information.
> #
> # <file system> <mount point> <type> <options> <dump> <pass>
>
> proc /proc proc defaults 0 0
>
> /dev/sda1 / ext3 defaults,errors=remount-ro 0 1
> /dev/sda7 /ahodi ext3 defaults,errors=remount-ro 0 2
>
> /dev/sda8 /home ext3 acl,usrquota,grpquota,errors=remount-ro 0 2
> /dev/sda9 /share ext3 acl,usrquota,grpquota,errors=remount-ro 0 2
> /dev/sda3 /tmp ext3 defaults,errors=remount-ro 0 2
> /dev/sda6 /usr ext3 defaults,ro 0 2
> /dev/sda5 /var ext3 defaults,errors=remount-ro 0 2
>
> /dev/sda2 none swap sw 0 0
>
> /dev/hdc /media/cdrom0 iso9660 ro,nouser,noauto 0 0
> /dev/fd0 /media/floppy0 auto rw,nouser,noauto 0 0
GH
Reply to: