linux-kernel - Bio device too big | kernel BUG at mm/filemap.c:537!

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1170734919.15636.1173102761@webmail.messagingengine.com>
Date:	Mon, 05 Feb 2007 20:08:39 -0800
From:	"Kai" <epimetreus@...tmail.fm>
To:	linux-kernel@...r.kernel.org
Subject: Bio device too big | kernel BUG at mm/filemap.c:537!

I booted up the new kernel version, 2.6.20; I pretty much copied over my
.config that worked in 2.6.19.2, that has worked correctly since that
version came out... I looked through the menuconfig to see if any new
options had been added, but I'm pretty sure I didn't change anything,
and got this error message shortly after booting:

bio too big device hdg1 (184 > 128)
------------[ cut here ]------------
kernel BUG at mm/filemap.c:537!
invalid opcode: 0000 [#1]
Modules linked in: iptable_filter ip_tables x_tables snd_seq_dummy
snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss
snd_mixer_oss nvidia_agp agpgart
CPU:    0
EIP:    0060:[<c012dc66>]    Not tainted VLI
EFLAGS: 00010246   (2.6.20 #1)
EIP is at unlock_page+0xd/0x22
eax: 00000000   ebx: c1714a20   ecx: 00000000   edx: c1714a20
esi: c199c45c   edi: 00000001   ebp: 1422bf48   esp: f7c8df18
ds: 007b   es: 007b   ss: 0068
Process md0_raid5 (pid: 901, ti=f7c8c000 task=f7c50050 task.ti=f7c8c000)
Stack: c1997920 c016363c c1bca460 c1997920 c1bca460 c0315af2 f7c8df4c
f7c8df50
       c1bca460 00000000 00000000 1422bf48 0a115f48 00000002 00000000
       c1bca460
       00000002 f7faf600 fffffffc c0315b92 f7ee6c20 7fffffff f7c8df8c
       c031f877
Call Trace:
 [<c016363c>] mpage_end_io_read+0x4c/0x5e
 [<c0315af2>] retry_aligned_read+0x108/0x13a
 [<c0315b92>] raid5d+0x6e/0xcc
 [<c031f877>] md_thread+0xdc/0xf2
 [<c0122465>] autoremove_wake_function+0x0/0x33
 [<c0110a90>] __wake_up_common+0x35/0x4f
 [<c0122465>] autoremove_wake_function+0x0/0x33
 [<c031f79b>] md_thread+0x0/0xf2
 [<c01221b8>] kthread+0x72/0x97
 [<c0122146>] kthread+0x0/0x97
 [<c0103a7b>] kernel_thread_helper+0x7/0x10
 =======================
Code: 73 ff ff ff b9 a4 d6 12 c0 89 fa c7 04 24 02 00 00 00 e8 87 77 27
00 83 c4 44 5b 5e 5f c3 53 89 c3 0f ba 30 00 19 c0 85 c0 75 04 <0f> 0b
eb fe 89 d8 e8 41 ff ff ff 89$
EIP: [<c012dc66>] unlock_page+0xd/0x22 SS:ESP 0068:f7c8df18

The devices it seems to be complaining about are /dev/hdg and /dev/hde,
which are physically attached to the PCI0680 Ultra ATA-133 Host
Controller listed in lspci.txt.
Both drives are 160 GB Western Digital HDDs... don't remember the
precise model, but I can find out if necessary.

Attached are the output of lspci and my .config; if anyone needs further
info, let me know.
Please CC replies, not subscribed.

Cheers,

-Kai

Download attachment ".config" of type "application/octet-stream" (37714 bytes)

View attachment "lspci.txt" of type "text/plain" (5949 bytes)