public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* segmentation fault when accessing /proc/ioports
@ 2005-10-29  9:09 Patrick Useldinger
  2005-10-29  9:44 ` Arjan van de Ven
  2005-10-29 11:03 ` Adrian Bunk
  0 siblings, 2 replies; 6+ messages in thread
From: Patrick Useldinger @ 2005-10-29  9:09 UTC (permalink / raw)
  To: linux-kernel

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: segmentation fault when accessing /proc/ioports
  2005-10-29  9:09 segmentation fault when accessing /proc/ioports Patrick Useldinger
@ 2005-10-29  9:44 ` Arjan van de Ven
  2005-10-29 11:03 ` Adrian Bunk
  1 sibling, 0 replies; 6+ messages in thread
From: Arjan van de Ven @ 2005-10-29  9:44 UTC (permalink / raw)
  To: Patrick Useldinger; +Cc: linux-kernel


> I have read on the kernel mailing lists that this is due to drivers
> not properly unloading, so I won't post an lsmod.

this makes no sense. A driver is not properly doing it's unloading.. to
find out which that is an lsmod is NEEDED .....
unless people on this list are clearvoyant nobody can help you
otherwise...


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: segmentation fault when accessing /proc/ioports
  2005-10-29  9:09 segmentation fault when accessing /proc/ioports Patrick Useldinger
  2005-10-29  9:44 ` Arjan van de Ven
@ 2005-10-29 11:03 ` Adrian Bunk
       [not found]   ` <b2992ee70510290422g1912d1e5sedcdf6fc0155c4b0@mail.gmail.com>
  1 sibling, 1 reply; 6+ messages in thread
From: Adrian Bunk @ 2005-10-29 11:03 UTC (permalink / raw)
  To: Patrick Useldinger; +Cc: linux-kernel

On Sat, Oct 29, 2005 at 11:09:25AM +0200, Patrick Useldinger wrote:

> Hello,

Hi Patrick,

>...
> [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
>...

Does this problem happen without ever loading the vmware modules since 
booting?

It it doesn't, please complain to vmware.

> I have read on the kernel mailing lists that this is due to drivers
> not properly unloading, so I won't post an lsmod.

You've already sent it above.

> Thanks for your attention,
> -pu

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Fwd: segmentation fault when accessing /proc/ioports
       [not found]       ` <b2992ee70510290736l7ec43091o880f141bd8be09e7@mail.gmail.com>
@ 2005-10-29 17:04         ` Patrick Useldinger
  2005-10-30 18:22           ` Randy.Dunlap
  0 siblings, 1 reply; 6+ messages in thread
From: Patrick Useldinger @ 2005-10-29 17:04 UTC (permalink / raw)
  To: linux-kernel

This is what I get when I throw out the LVM2 packages
(device-mapper-1.01.04-i486-1.tgz and lvm2-2.01.09-i486-1.tgz):

root@slackw:~$ cat /proc/ioports
0000-001f : dma1
0020-0021 : pic1
0040-0043 : timer0
0050-0053 : timer1
0060-006f : keyboard
0070-0077 : rtc
0080-008f : dma page reg
00a0-00a1 : pic2
00c0-00df : dma2
00f0-00ff : fpu
0170-0177 : ide1
01f0-01f7 : ide0
0376-0376 : ide1
0378-037a : parport0
037b-037f : parport0
03c0-03df : vesafb
03e0-03e1 : $
             LB D$B$è~'PÇ·D$S%ÿ
03f6-03f6 : ide0
03f8-03ff : serial
0800-0803 : PM1a_EVT_BLK
0804-0805 : PM1a_CNT_BLK
0808-080b : PM_TMR
0816-0816 : PM2_CNT_BLK
0820-0823 : GPE0_BLK
0830-0833 : GPE1_BLK
0c00-0c1f : 0000:00:02.1
  0c00-0c1f : sis96x-smbus
0cf8-0cff : PCI conf1
1000-1fff : PCI CardBus #03
2000-2fff : PCI CardBus #03
3000-3fff : PCI CardBus #07
4000-4fff : PCI CardBus #07
b000-bfff : PCI Bus #01
  bc00-bc7f : 0000:01:00.0
d400-d4ff : 0000:00:0f.0
  d400-d4ff : 8139too
d800-d87f : 0000:00:02.7
  d800-d87f : SiS SI7012
dc00-dcff : 0000:00:02.7
  dc00-dcff : SiS SI7012
ff00-ff0f : 0000:00:02.5
  ff00-ff07 : ide0
  ff08-ff0f : ide1

The address at 03e0-03e1 still looks strange, but no more oopses.

... meaning that the module who produces the problem is dm_mod.
BTW, I have no VGs on my system.
Anything else I can do to help tracking the problem?

Regards,
-pu

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Fwd: segmentation fault when accessing /proc/ioports
  2005-10-29 17:04         ` Fwd: " Patrick Useldinger
@ 2005-10-30 18:22           ` Randy.Dunlap
  2005-10-30 18:32             ` Patrick Useldinger
  0 siblings, 1 reply; 6+ messages in thread
From: Randy.Dunlap @ 2005-10-30 18:22 UTC (permalink / raw)
  To: Patrick Useldinger; +Cc: linux-kernel

On Sat, 29 Oct 2005 19:04:39 +0200 Patrick Useldinger wrote:

> This is what I get when I throw out the LVM2 packages
> (device-mapper-1.01.04-i486-1.tgz and lvm2-2.01.09-i486-1.tgz):
> 
> root@slackw:~$ cat /proc/ioports
> 0000-001f : dma1
> 0020-0021 : pic1
> 0040-0043 : timer0
> 0050-0053 : timer1
> 0060-006f : keyboard
> 0070-0077 : rtc
> 0080-008f : dma page reg
> 00a0-00a1 : pic2
> 00c0-00df : dma2
> 00f0-00ff : fpu
> 0170-0177 : ide1
> 01f0-01f7 : ide0
> 0376-0376 : ide1
> 0378-037a : parport0
> 037b-037f : parport0
> 03c0-03df : vesafb
> 03e0-03e1 : $
>              LB D$B$è~'PÇ·D$S%ÿ
> 03f6-03f6 : ide0
> 03f8-03ff : serial
> 0800-0803 : PM1a_EVT_BLK
> 0804-0805 : PM1a_CNT_BLK
> 0808-080b : PM_TMR
> 0816-0816 : PM2_CNT_BLK
> 0820-0823 : GPE0_BLK
> 0830-0833 : GPE1_BLK
> 0c00-0c1f : 0000:00:02.1
>   0c00-0c1f : sis96x-smbus
> 0cf8-0cff : PCI conf1
> 1000-1fff : PCI CardBus #03
> 2000-2fff : PCI CardBus #03
> 3000-3fff : PCI CardBus #07
> 4000-4fff : PCI CardBus #07
> b000-bfff : PCI Bus #01
>   bc00-bc7f : 0000:01:00.0
> d400-d4ff : 0000:00:0f.0
>   d400-d4ff : 8139too
> d800-d87f : 0000:00:02.7
>   d800-d87f : SiS SI7012
> dc00-dcff : 0000:00:02.7
>   dc00-dcff : SiS SI7012
> ff00-ff0f : 0000:00:02.5
>   ff00-ff07 : ide0
>   ff08-ff0f : ide1
> 
> The address at 03e0-03e1 still looks strange, but no more oopses.

Did you perhaps load and unload the (PCMCIA) i82365 driver module?

> ... meaning that the module who produces the problem is dm_mod.
> BTW, I have no VGs on my system.
> Anything else I can do to help tracking the problem?

What's a VG?

---
~Randy

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Fwd: segmentation fault when accessing /proc/ioports
  2005-10-30 18:22           ` Randy.Dunlap
@ 2005-10-30 18:32             ` Patrick Useldinger
  0 siblings, 0 replies; 6+ messages in thread
From: Patrick Useldinger @ 2005-10-30 18:32 UTC (permalink / raw)
  To: Randy.Dunlap; +Cc: linux-kernel

On 10/30/05, Randy.Dunlap <rdunlap@xenotime.net> wrote:

> Did you perhaps load and unload the (PCMCIA) i82365 driver module?

It's possible, the machine has a PCMCIA slot I never use.
But I haven't changed anything related to PCMCIA, so the problem
should still be there, but it isn't since I got rid of dm_mod.

> What's a VG?
A volume group, as used in the context of logical volumes and LVM2.

Regards,
-pu

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2005-10-30 18:32 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-10-29  9:09 segmentation fault when accessing /proc/ioports Patrick Useldinger
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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox