linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Cliff White <cliffw@osdl.org>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Dave McCracken <dmccr@us.ibm.com>,
	cliffw@osdl.org
Subject: 2.5.62-mm3 -Panics during dbt2 run
Date: Tue, 25 Feb 2003 10:49:43 -0800	[thread overview]
Message-ID: <200302251849.h1PInh921599@mail.osdl.org> (raw)
In-Reply-To: Message from Andrew Morton <akpm@digeo.com> of "Tue, 25 Feb 2003 01:55:37 PST." <20030225015537.4062825b.akpm@digeo.com>

Tried hard to test this, but all it does for me is panic.
Is this fixed in 2.5.63?
This is 4-way PIII system. 
 panic, while booting
Press Y within 1 seconds to force file system integrity check...
 [<c02409e8>] as_next_request+0x38/0x50
 [<c02385c6>] elv_next_request+0x16/0x110
 [<c02823bc>] scsi_request_fn+0x4c/0x300
 [<c023a358>] blk_remove_plug+0x88/0x100
 [<c023a64d>] __blk_run_queue+0x1d/0x30
 [<c0281739>] scsi_queue_next_request+0xa9/0x240
 [<c023c060>] end_that_request_last+0x50/0x90
 [<c02819d2>] scsi_end_request+0x102/0x120
 [<c0281d31>] scsi_io_completion+0x161/0x4e0
 [<c02a545c>] ahc_done+0x1ec/0x470
 [<c02ab3fb>] sd_rw_intr+0x7b/0x210
 [<c027b6f6>] scsi_finish_command+0x86/0xf0
 [<c027b4d9>] scsi_softirq+0xc9/0x220
 [<c0129515>] do_softirq+0xc5/0xd0
 [<c010bf35>] do_IRQ+0x1c5/0x1f0
 [<c0107340>] default_idle+0x0/0x40
 [<c010a584>] common_interrupt+0x18/0x20
 [<c0107340>] default_idle+0x0/0x40
 [<c010736d>] default_idle+0x2d/0x40
 [<c010740a>] cpu_idle+0x4a/0x60
 [<c0105000>] rest_init+0x0/0x80

Code: 8b 46 14 8b 40 50 89 04 24 e8 5e 9b ff ff 8d 43 70 e8 c6 52
---------------------------------

It died again, while bunzipping the db backup, but
i did not get the panic string

--------------------------------------
cliffw


--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org">aart@kvack.org</a>

  parent reply	other threads:[~2003-02-25 18:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-24  7:00 2.5.62-mm3 Andrew Morton
2003-02-24 12:26 ` 2.5.62-mm3 - no X for me Helge Hafting
2003-02-24 20:16   ` Andrew Morton
2003-02-25  9:45     ` Zilvinas Valinskas
2003-02-25  9:55       ` Andrew Morton
2003-02-25 17:57         ` Dave McCracken
2003-02-25 21:27           ` Andrew Morton
2003-02-25 21:46             ` Dave McCracken
2003-02-25 23:02               ` [PATCH 2.5.62-mm3] objrmap fix for X Dave McCracken
2003-02-26  6:14                 ` Martin J. Bligh
2003-02-26 17:52                   ` Martin J. Bligh
2003-02-26 18:03                     ` Marc-Christian Petersen
2003-02-26 18:24                       ` Martin J. Bligh
2003-03-01  9:31                     ` Anton Blanchard
2003-02-25 18:49         ` Cliff White [this message]
2003-02-25 19:12           ` 2.5.62-mm3 -Panics during dbt2 run Andrew Morton
2003-02-25 22:37             ` 2.5.62-mm3 -DBT2 (was) " Cliff White
2003-02-24 18:04 ` 2.5.62-mm3 won't mount root Steven Cole

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=200302251849.h1PInh921599@mail.osdl.org \
    --to=cliffw@osdl.org \
    --cc=akpm@digeo.com \
    --cc=dmccr@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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