public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Thibaut VARENE <T-Bone@parisc-linux.org>
To: linux-ia64@vger.kernel.org
Subject: kernel troubles on rx2600 while running sbuild
Date: Sun, 26 Sep 2004 16:33:33 +0000	[thread overview]
Message-ID: <20040926183333.1592f4cd@Tatooine.r3z0> (raw)

Hi,

I've been having some troubles while running 'sbuild' (debian package
autobuilder system) on freshly installed Debian Sarge rx2600 boxes.

First issue:
rx2600 2-way with 4GB RAM, using debian
kernel-image-2.6.8.1-4-mckinley-smp

The box went into a very unstable state while building aptitude (roughly
5 hours after starting sbuild). Several processes went into "D" state and
the logs started to get flooded by the following 3 lines (repeated 435743
times, that is, until i rebooted the system):

Sep 24 02:03:27 gandalf kernel: b_state=0x00000019, b_size@96
Sep 24 02:03:27 gandalf kernel: device blocksize: 4096
Sep 24 02:03:27 gandalf kernel:__find_get_block_slow() failed.
block\x1605635, b_blocknr\x1605632

At that point I could nonetheless login and reboot the system.
I then ran a disk check just in case (including badblocks check) which
shown nothing.

There I thought that SMP might not be a good idea when running sbuild so I
switched to a UP system, with the same configuration (except for the RAM &
nb of CPUs):

Second issue:
rx2600 1-way with 2GB RAM, using debian kernel-image-2.6.8.1-4-mckinley

The system was taken down approx 4h after staring sbuild, unfortunately
the console logs were bloated with stack dumps and got enventually
purged, so i couldn't gather much info, therefore i'm just posting it for
the record. Here is what I could collect:

<6>note: sh[8180] exited with preempt_count 1
Unable to handle kernel NULL pointer dereference (address
0000000000000028)
sh[8180]: Oops 8813272891392 [18]

As a matter of fact, I can't tell whether this was the problem that took
the machine down. The only thing i can tell, is that switching back to 2.4
(kernel-image-2.4.27-1-mckinley) seems to have made this system much more
stable, since it's been running sbuild now for 16h straight without any
problem.

HTH,


Thibaut VARENE
The PA/Linux ESIEE Team
http://www.pateam.org/

             reply	other threads:[~2004-09-26 16:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-26 16:33 Thibaut VARENE [this message]
2004-09-29  7:17 ` kernel troubles on rx2600 while running sbuild Thibaut VARENE
2004-09-29  7:47 ` Thibaut VARENE
2004-09-29 19:13 ` dann frazier
2004-09-29 20:31 ` Thibaut VARENE

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=20040926183333.1592f4cd@Tatooine.r3z0 \
    --to=t-bone@parisc-linux.org \
    --cc=linux-ia64@vger.kernel.org \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox