From: Patrick Useldinger <uselpa@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: segmentation fault when accessing /proc/ioports
Date: Sat, 29 Oct 2005 11:09:25 +0200 [thread overview]
Message-ID: <b2992ee70510290209h26c1fd6ex92fd137cd2c9d747@mail.gmail.com> (raw)
Hello,
according to "oops-tracing.txt", I send you this problem report.
This is a problem I have been experiencing with all kernels I have
tried later than 2.6.11.12, currently with 2.6.13.4. I am using the
Slackware 10.2 distribution.
The system is working normally and completely stable. When I shutdown
or restart, however, I have the following message:
[code]
Oct 29 10:32:33 slackw kernel: mtrr: 0xd0000000,0x4000000 overlaps
existing 0xd0000000,0x2000000
Oct 29 10:32:45 slackw kernel: Unable to handle kernel paging request
at virtual address f8ce5a0a
Oct 29 10:32:45 slackw kernel: printing eip:
Oct 29 10:32:45 slackw kernel: c01dbcfe
Oct 29 10:32:45 slackw kernel: *pde = 36523067
Oct 29 10:32:45 slackw kernel: *pte = 00000000
Oct 29 10:32:45 slackw kernel: Oops: 0000 [#1]
Oct 29 10:32:45 slackw kernel: PREEMPT
Oct 29 10:32:45 slackw kernel: Modules linked in: vmnet vmmon sch_sfq
snd_pcm_oss snd_mixer_oss ipv6 ipt_state ipt_REJECT ipt_LOG
ip_conntrack_ftp ip_conntrack iptable_filter ip_tables uhci_hcd
sis_agp shpchp i2c_sis96x i2c_core snd_intel8x0 snd_ac97_codec snd_pcm
snd_timer snd soundcore snd_page_alloc ohci_hcd ehci_hcd ohci1394
ieee1394 8139too mii pcmcia firmware_class yenta_socket rsrc_nonstatic
pcmcia_core dm_mod evdev agpgart lp parport_pc parport psmouse
Oct 29 10:32:45 slackw kernel: CPU: 0
Oct 29 10:32:45 slackw kernel: EIP: 0060:[<c01dbcfe>] Tainted: P VLI
Oct 29 10:32:45 slackw kernel: EFLAGS: 00010297 (2.6.13.4)
Oct 29 10:32:45 slackw kernel: EIP is at vsnprintf+0x35e/0x4f0
Oct 29 10:32:45 slackw kernel: eax: f8ce5a0a ebx: 0000000a ecx:
f8ce5a0a edx: fffffffe
Oct 29 10:32:45 slackw kernel: esi: ee123134 edi: 00000000 ebp:
ee123fff esp: ee257eb4
Oct 29 10:32:45 slackw kernel: ds: 007b es: 007b ss: 0068
Oct 29 10:32:45 slackw kernel: Process grep (pid: 5996,
threadinfo=ee256000 task=e91b6530)
Oct 29 10:32:45 slackw kernel: Stack: ee12312d ee123fff 000003e1
00000000 00000010 00000004 00000002 00000001
Oct 29 10:32:45 slackw kernel: ffffffff ffffffff f5ceb9c0
c0350234 f5ceb9c0 00000128 c017be67 ee123128
Oct 29 10:32:45 slackw kernel: 00000ed8 c0355e66 ee257f2c
c0355e54 c011fb04 f5ceb9c0 c0355e54 00000000
Oct 29 10:32:45 slackw kernel: Call Trace:
Oct 29 10:32:45 slackw kernel: [<c017be67>] seq_printf+0x37/0x60
Oct 29 10:32:45 slackw kernel: [<c011fb04>] r_show+0x84/0x90
Oct 29 10:32:45 slackw kernel: [<c017b966>] seq_read+0x1d6/0x2d0
Oct 29 10:32:45 slackw kernel: [<c0159306>] vfs_read+0xb6/0x180
Oct 29 10:32:45 slackw kernel: [<c01596b1>] sys_read+0x51/0x80
Oct 29 10:32:45 slackw kernel: [<c01031a5>] syscall_call+0x7/0xb
Oct 29 10:32:45 slackw kernel: Code: 00 83 cf 01 89 44 24 24 eb bb 8b
44 24 48 8b 54 24 20 83 44 24 48 04 8b 08 b8 8c 24 36 c0 81 f9 ff 0f
00 00 0f 46 c8 89 c8 eb 06 <80> 38 00 74 07 40 4a 83 fa ff 75 f4 29 c8
83 e7 10 89 c3 75 20
Oct 29 10:32:45 slackw kernel: <6>note: grep[5996] exited with preempt_count 1
[/code]
Before, it says something about a segmentation fault in line 54 of rc.6.
I have tracked this down to the following command in line 44:
[code] if ! grep -q -w rtc /proc/ioports ; then[/code]
and a simple [code]cat /proc/ioports[/code] gives me a segmentation
fault every time.
I have read on the kernel mailing lists that this is due to drivers
not properly unloading, so I won't post an lsmod.
Thanks for your attention,
-pu
next reply other threads:[~2005-10-29 9:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-29 9:09 Patrick Useldinger [this message]
2005-10-29 9:44 ` Arjan van de Ven
2005-10-29 11:03 ` Adrian Bunk
[not found] ` <b2992ee70510290422g1912d1e5sedcdf6fc0155c4b0@mail.gmail.com>
[not found] ` <20051029112617.GJ4180@stusta.de>
[not found] ` <b2992ee70510290736l7ec43091o880f141bd8be09e7@mail.gmail.com>
2005-10-29 17:04 ` Fwd: " Patrick Useldinger
2005-10-30 18:22 ` Randy.Dunlap
2005-10-30 18:32 ` Patrick Useldinger
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=b2992ee70510290209h26c1fd6ex92fd137cd2c9d747@mail.gmail.com \
--to=uselpa@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
all inboxes | Powered by JetHome®