mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Patrick Useldinger <uselpa@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Fwd: segmentation fault when accessing /proc/ioports
Date: Sun, 30 Oct 2005 10:22:12 -0800	[thread overview]
Message-ID: <20051030102212.679f35db.rdunlap@xenotime.net> (raw)
In-Reply-To: <b2992ee70510291004n66537b79h38c6d94005b82cf4@mail.gmail.com>

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

  reply	other threads:[~2005-10-30 18:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-29  9:09 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 [this message]
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=20051030102212.679f35db.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=uselpa@gmail.com \
    /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®