From: Chuck Ebbert <cebbert@redhat.com>
To: "Jay L. T. Cornwall" <jay@esuna.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.22-rc5: pdflush oops under heavy disk load
Date: Fri, 22 Jun 2007 10:47:52 -0400 [thread overview]
Message-ID: <467BE118.4090308@redhat.com> (raw)
In-Reply-To: <467B12CA.5060405@esuna.co.uk>
On 06/21/2007 08:07 PM, Jay L. T. Cornwall wrote:
> Hi,
>
> Kernel version: 2.6.22-rc5 (confirmed also on 2.6.20)
> Kernel config : Ubuntu 7.04 default (SMP)
>
> Relevant hardware:
> Asus P5K (Intel P35 chipset)
> Core 2 Duo E6600 2.4GHz
> Western Digital 10KRPM 150GB HDD on JMicron 20360/20363 AHCI
>
> Netconsoled dump:
>
> [ 724.350222] general protection fault: 0000 [1] SMP
> [ 724.350413] CPU 1
> [ 724.350520] Modules linked in: usb_storage libusual netconsole
> binfmt_misc rfcomm l2cap bluetooth ppdev capability commoncap
> acpi_cpufreq cpufreq_stats cpufreq_userspace cpufreq_ondemand
> cpufreq_conservative cpufreq_powersave freq_table video container
> battery dock asus_acpi ac sbs button af_packet nls_utf8 ntfs w83627ehf
> i2c_isa parport_pc lp parport fuse mt2060 snd_hda_intel snd_pcm_oss
> snd_mixer_oss snd_pcm cx22702 snd_seq_dummy snd_seq_oss dvb_usb_dib0700
> dib7000m dib7000p dvb_usb cx88_dvb cx88_vp3054_i2c snd_seq_midi
> snd_rawmidi video_buf_dvb dvb_core ipv6 snd_seq_midi_event snd_seq
> snd_timer dvb_pll cx8800 cx8802 cx88xx sr_mod ir_common snd_seq_device
> cdrom i2c_algo_bit dib3000mc dibx000_common tveeprom atl1 usbhid psmouse
> videodev compat_ioctl32 hid mii i2c_core v4l2_common v4l1_compat
> btcx_risc video_buf serio_raw snd soundcore pcspkr shpchp pci_hotplug
> snd_page_alloc intel_agp tsdev evdev ext3 jbd mbcache sg sd_mod
> pata_jmicron ata_generic ata_piix ahci libata scsi_mod ehci_hcd generic
> uhci_hcd usbcore thermal processor fan
> [ 724.355028] Pid: 199, comm: pdflush Not tainted 2.6.22-rc5-edge #1
> [ 724.355125] RIP: 0010:[<ffffffff880f1b44>] [<ffffffff880f1b44>]
> :ext3:walk_page_buffers+0x34/0x90
Step 1: run fsck on the filesystem.
next prev parent reply other threads:[~2007-06-22 14:48 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-22 0:07 2.6.22-rc5: pdflush oops under heavy disk load Jay L. T. Cornwall
2007-06-22 14:47 ` Chuck Ebbert [this message]
2007-06-22 15:04 ` Jay L. T. Cornwall
2007-06-23 12:14 ` Jay L. T. Cornwall
2007-06-23 17:23 ` Andrew Morton
2007-06-24 9:57 ` (Last oops is Tainted: P) " Oleg Verych
2007-06-24 10:10 ` Jay L. T. Cornwall
2007-06-24 10:57 ` Oleg Verych
2007-06-24 17:59 ` Jay Cliburn
2007-06-24 20:31 ` Jay L. T. Cornwall
2007-06-24 21:45 ` Jay Cliburn
2007-06-25 12:16 ` Attansic L1 page corruption (was: 2.6.22-rc5: pdflush oops under heavy disk load) Jay L. T. Cornwall
2007-06-25 12:42 ` Attansic L1 page corruption Jay Cliburn
2007-06-25 21:18 ` [PATCH] atl1: disable 64bit DMA Luca Tettamanti
2007-06-25 21:36 ` Chris Snook
2007-06-25 21:51 ` Jay L. T. Cornwall
2007-06-25 21:57 ` Chris Snook
2007-06-25 23:00 ` Jay Cliburn
2007-06-25 23:17 ` Jeff Garzik
2007-06-25 23:40 ` Chris Snook
2007-06-26 21:12 ` Luca
2007-06-27 0:16 ` Jay Cliburn
2007-06-25 12:58 ` Attansic L1 page corruption (was: 2.6.22-rc5: pdflush oops under heavy disk load) Luca
2007-06-24 22:51 ` 2.6.22-rc5: pdflush oops under heavy disk load Jesper Juhl
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=467BE118.4090308@redhat.com \
--to=cebbert@redhat.com \
--cc=jay@esuna.co.uk \
--cc=linux-kernel@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