From: Andrej Hocevar <and.hocevar@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: PROBLEM with kernel
Date: Thu, 5 Jun 2008 13:23:57 +0200 [thread overview]
Message-ID: <20080605112357.GA7588@stoa> (raw)
I got this right after resuming from hibernation. Unfortunatelly, I
don't have the kernel-sources anymore as I've actually upgraded to
2.6.25.4.
Buffer I/O error on device sda1, logical block 0
lost page write due to I/O error on sda1
scsi 1:0:0:0: Direct-Access WD 5000AAKS Externa 106a PQ: 0
ANSI: 4
sd 1:0:0:0: [sdb] 976773168 512-byte hardware sectors (500108 MB)
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Mode Sense: 11 00 00 00
sd 1:0:0:0: [sdb] Assuming drive cache: write through
sd 1:0:0:0: [sdb] 976773168 512-byte hardware sectors (500108 MB)
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Mode Sense: 11 00 00 00
sd 1:0:0:0: [sdb] Assuming drive cache: write through
sdb: sdb1 sdb2 sdb3
sd 1:0:0:0: [sdb] Attached SCSI disk
usb-storage: device scan complete
------------[ cut here ]------------
WARNING: at fs/buffer.c:1183 mark_buffer_dirty+0x20/0x6a()
Modules linked in: xt_state xt_tcpudp iptable_filter ip_tables x_tables
nf_nat_ftp nf_nat nf_conntrack_ipv4 nf_conntrack_ftp nf_conntrack ppdev
lp cpufreq_stats fuse sr_mod sbp2 sd_mod parport_pc parport
snd_intel8x0 snd_ac97_codec rtc ac97_bus snd_pcm_oss snd_mixer_oss
snd_pcm 8250_pci snd_timer 8250 serial_core snd_page_alloc rng_core
video output evdev ide_cd_mod cdrom ide_disk usb_storage usbhid
scsi_mod ohci1394 piix ieee1394 ide_core ehci_hcd uhci_hcd usbcore unix
[last unloaded: firmware_class]
Pid: 7364, comm: umount Not tainted 2.6.25.3summer #1
[<c011767f>] warn_on_slowpath+0x40/0x4f
[<c013c6d5>] generic_writepages+0x1a/0x21
[<c014dd56>] check_bytes_and_report+0x25/0x98
[<c014dd56>] check_bytes_and_report+0x25/0x98
[<c014e046>] check_object+0x114/0x19f
[<c0192fdf>] journal_destroy+0x11e/0x125
[<c014e561>] __slab_free+0x1be/0x1ed
[<c0192fdf>] journal_destroy+0x11e/0x125
[<c014eb91>] kfree+0x79/0x81
[<c0192fdf>] journal_destroy+0x11e/0x125
[<c0192fdf>] journal_destroy+0x11e/0x125
[<c0124ac8>] autoremove_wake_function+0x0/0x2d
[<c016a436>] mark_buffer_dirty+0x20/0x6a
[<c018a729>] ext3_put_super+0x41/0x137
[<c0153257>] generic_shutdown_super+0x4a/0xad
[<c01532c6>] kill_block_super+0xc/0x1b
[<c0153334>] deactivate_super+0x2c/0x3f
[<c01620bf>] sys_umount+0x231/0x269
[<c014e561>] __slab_free+0x1be/0x1ed
[<c01543ef>] sys_stat64+0xf/0x23
[<c01440c0>] remove_vma+0x36/0x3b
[<c0144938>] do_munmap+0x181/0x19b
[<c0162102>] sys_oldumount+0xb/0xe
[<c010393e>] syscall_call+0x7/0xb
=======================
---[ end trace 02c95bee20be13a0 ]---
Andrej
--
www.ljudmila.org/ludliteratura
next reply other threads:[~2008-06-05 11:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-05 11:23 Andrej Hocevar [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-03-05 0:44 Problem with Kernel Timothy M. Totten
2002-03-08 18:03 ` Robert Claeson
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=20080605112357.GA7588@stoa \
--to=and.hocevar@gmail.com \
--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