From: Jens Axboe <axboe@suse.de>
To: Chase Venters <chase.venters@clientec.com>
Cc: Andrew Morton <akpm@osdl.org>, Anton Titov <a.titov@host.bg>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: OOM Killer killing whole system
Date: Mon, 23 Jan 2006 09:39:39 +0100 [thread overview]
Message-ID: <20060123083939.GB12773@suse.de> (raw)
In-Reply-To: <200601201819.58366.chase.venters@clientec.com>
On Fri, Jan 20 2006, Chase Venters wrote:
> On Friday 20 January 2006 16:49, Andrew Morton wrote:
> > This is 2.6.15 and we have a deadly bug in scsi.
> >
> > Next time you reboot 2.6.15 on that machine can you please send the output
> > of `dmesg -s 1000000'? You might have to set CONFIG_LOG_BUF_SHIFT=17 to
> > prevent it from being truncated.
>
> Here's mine (attached). Curious - the -s... were you expecting the
> ring buffer to exceed 16384? I don't think my (boot time) buffer does.
Just a note - you seem to have the raid1 in common with the rest of the
reporters so far.
--
Jens Axboe
next prev parent reply other threads:[~2006-01-23 8:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-15 15:05 Anton Titov
2006-01-20 12:11 ` Andrew Morton
2006-01-20 20:04 ` Chase Venters
2006-01-20 21:48 ` Anton Titov
2006-01-20 22:50 ` Andrew Morton
2006-01-21 0:09 ` Anton Titov
2006-01-21 0:19 ` Chase Venters
2006-01-21 0:50 ` Andrew Morton
2006-01-21 1:17 ` James Bottomley
2006-01-21 3:29 ` Anton Titov
2006-01-21 3:44 ` Andrew Morton
2006-01-25 22:20 ` Matthias Urlichs
2006-01-21 3:45 ` Anton Titov
2006-01-21 3:53 ` Chase Venters
2006-01-21 4:21 ` Anton Titov
2006-01-21 4:35 ` Chase Venters
2006-01-23 2:56 ` Kalin KOZHUHAROV
2006-01-23 3:28 ` Chase Venters
2006-01-23 8:39 ` Jens Axboe [this message]
2006-01-23 8:41 ` Arjan van de Ven
2006-01-23 9:10 ` Chase Venters
2006-01-23 12:55 Nicolas Mailhot
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=20060123083939.GB12773@suse.de \
--to=axboe@suse.de \
--cc=a.titov@host.bg \
--cc=akpm@osdl.org \
--cc=chase.venters@clientec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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
all inboxes | Powered by JetHome®