Averatec 6240 pcmcia_socket0: unable to apply power

James supersaucy151 at yahoo.com
Thu Sep 8 19:21:17 EDT 2005


here is my latest dmesg
ksign: Installing public key data
Loading keyring
- Added public key 1C1942C715575330
- User ID: Red Hat, Inc. (Kernel Module GPG key)
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
ACPI: CPU0 (power states: C1[C1])
ACPI: Thermal Zone [THRM] (70 C)
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Real Time Clock Driver v1.12
Linux agpgart interface v0.101 (c) Dave Jones
agpgart: Detected SiS 760 chipset
agpgart: AGP aperture is 4M @ 0xe0000000
PNP: PS/2 Controller [PNP0303:PS2K,PNP0f03:PS2M] at
0x60,0x64 irq 1,12
i8042.c: Detected active multiplexing controller, rev
1.1.
serio: i8042 AUX0 port at 0x60,0x64 irq 12
serio: i8042 AUX1 port at 0x60,0x64 irq 12
serio: i8042 AUX2 port at 0x60,0x64 irq 12
serio: i8042 AUX3 port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
Serial: 8250/16550 driver $Revision: 1.90 $ 76 ports,
IRQ sharing enabled
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11
PCI: setting IRQ 11 as level-triggered
ACPI: PCI Interrupt 0000:00:02.6[C] -> Link [LNKC] ->
GSI 11 (level, low) -> IRQ  11
ACPI: PCI interrupt for device 0000:00:02.6 disabled
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
RAMDISK driver initialized: 16 RAM disks of 16384K
size 1024 blocksize
Uniform Multi-Platform E-IDE driver Revision:
7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes;
override with idebus=xx
SIS5513: IDE controller at PCI slot 0000:00:02.5
SIS5513: chipset revision 0
SIS5513: not 100% native mode: will probe irqs later
SIS5513: SiS 962/963 MuTIOL IDE UDMA133 controller
    ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings:
hda:DMA, hdb:DMA
    ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings:
hdc:DMA, hdd:DMA
Probing IDE interface ide0...
hda: IC25N080ATMR04-0, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hdc: Slimtype DVDRW SOSW-852S, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 1024KiB
hda: 156301488 sectors (80026 MB) w/7884KiB Cache,
CHS=16383/255/63, UDMA(33)
hda: cache flushes supported
 hda: hda1 hda2 < hda5 hda6 hda7 >
hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB
Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
ide-floppy driver 0.99.newide
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.01:USB HID core
driver
mice: PS/2 mouse device common for all mice
md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27
NET: Registered protocol family 2
IP: routing cache hash table of 1024 buckets, 32Kbytes
TCP established hash table entries: 16384 (order: 5,
131072 bytes)
TCP bind hash table entries: 16384 (order: 6, 458752
bytes)
TCP: Hash tables configured (established 16384 bind
16384)
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
ACPI wakeup devices:
AC97 MC97 CBC0  MAC
ACPI: (supports S0 S1 S3 S4 S5)
Freeing unused kernel memory: 184k freed
device-mapper: 4.4.0-ioctl (2005-01-12) initialised:
dm-devel at redhat.com
input: AT Translated Set 2 keyboard on isa0060/serio0
alps.c: Enabling hardware tapping
input: PS/2 Mouse on isa0060/serio1
input: AlpsPS/2 ALPS GlidePoint on isa0060/serio1
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
security:  3 users, 6 roles, 764 types, 87 bools
security:  55 classes, 180131 rules
SELinux:  Completing initialization.
SELinux:  Setting up existing superblocks.
SELinux: initialized (dev dm-0, type ext3), uses xattr
SELinux: initialized (dev tmpfs, type tmpfs), uses
transition SIDs
SELinux: initialized (dev selinuxfs, type selinuxfs),
uses genfs_contexts
SELinux: initialized (dev mqueue, type mqueue), not
configured for labeling
SELinux: initialized (dev hugetlbfs, type hugetlbfs),
not configured for labelin g
SELinux: initialized (dev devpts, type devpts), uses
transition SIDs
SELinux: initialized (dev eventpollfs, type
eventpollfs), uses genfs_contexts
SELinux: initialized (dev tmpfs, type tmpfs), uses
transition SIDs
SELinux: initialized (dev futexfs, type futexfs), uses
genfs_contexts
SELinux: initialized (dev pipefs, type pipefs), uses
task SIDs
SELinux: initialized (dev sockfs, type sockfs), uses
task SIDs
SELinux: initialized (dev proc, type proc), uses
genfs_contexts
SELinux: initialized (dev bdev, type bdev), uses
genfs_contexts
SELinux: initialized (dev rootfs, type rootfs), uses
genfs_contexts
SELinux: initialized (dev sysfs, type sysfs), uses
genfs_contexts
SELinux: initialized (dev usbfs, type usbfs), uses
genfs_contexts
floppy0: no floppy controllers found
sis900.c: v1.08.08 Jan. 22 2005
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 4
PCI: setting IRQ 4 as level-triggered
ACPI: PCI Interrupt 0000:00:04.0[A] -> Link [LNKD] ->
GSI 4 (level, low) -> IRQ 4
0000:00:04.0: Realtek RTL8201 PHY transceiver found at
address 1.
0000:00:04.0: Using transceiver found at address 1 as
default
eth0: SiS 900 PCI Fast Ethernet at 0xd800, IRQ 4,
00:0c:76:f8:14:14.
Linux Kernel Card Services
  options:  [pci] [cardbus] [pm]
orinoco 0.15rc2 (David Gibson
<hermes at gibson.dropbear.id.au>, Pavel Roskin <pros
ki at gnu.org>, et al)
orinoco_cs 0.15rc2 (David Gibson
<hermes at gibson.dropbear.id.au>, Pavel Roskin <p
roski at gnu.org>, et al)
snd_intel8x0: Unknown parameter `'
ACPI: PCI Interrupt 0000:00:02.7[C] -> Link [LNKC] ->
GSI 11 (level, low) -> IRQ  11
intel8x0_measure_ac97_clock: measured 49503 usecs
intel8x0: clocking to 48000
ACPI: PCI Interrupt 0000:00:02.6[C] -> Link [LNKC] ->
GSI 11 (level, low) -> IRQ  11
i2c-sis96x version 1.0.0
sis96x_smbus 0000:00:02.1: SiS96x SMBus base address:
0x0c00
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver
version: 0.4
ACPI: PCI Interrupt Link [LNKH] enabled at IRQ 10
PCI: setting IRQ 10 as level-triggered
ACPI: PCI Interrupt 0000:00:03.3[D] -> Link [LNKH] ->
GSI 10 (level, low) -> IRQ  10
ehci_hcd 0000:00:03.3: EHCI Host Controller
ehci_hcd 0000:00:03.3: new USB bus registered,
assigned bus number 1
ehci_hcd 0000:00:03.3: irq 10, io mem 0xdffff000
PCI: cache line size of 64 is not supported by device
0000:00:03.3
ehci_hcd 0000:00:03.3: USB 2.0 initialized, EHCI 1.00,
driver 10 Dec 2004
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 6 ports detected
ohci_hcd: 2004 Nov 08 USB 1.1 'Open' Host Controller
(OHCI) Driver (PCI)
ACPI: PCI Interrupt Link [LNKE] enabled at IRQ 7
PCI: setting IRQ 7 as level-triggered
ACPI: PCI Interrupt 0000:00:03.0[A] -> Link [LNKE] ->
GSI 7 (level, low) -> IRQ 7
ohci_hcd 0000:00:03.0: OHCI Host Controller
ohci_hcd 0000:00:03.0: new USB bus registered,
assigned bus number 2
ohci_hcd 0000:00:03.0: irq 7, io mem 0xdfffd000
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 3 ports detected
ACPI: PCI Interrupt Link [LNKF] enabled at IRQ 5
PCI: setting IRQ 5 as level-triggered
ACPI: PCI Interrupt 0000:00:03.1[B] -> Link [LNKF] ->
GSI 5 (level, low) -> IRQ 5
ohci_hcd 0000:00:03.1: OHCI Host Controller
ohci_hcd 0000:00:03.1: new USB bus registered,
assigned bus number 3
ohci_hcd 0000:00:03.1: irq 5, io mem 0xdfffe000
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 3 ports detected
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 11
ACPI: PCI Interrupt 0000:00:0a.0[A] -> Link [LNKB] ->
GSI 11 (level, low) -> IRQ  11
Yenta: CardBus bridge found at 0000:00:0a.0
[1462:0111]
Yenta: Enabling burst memory read transactions
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:00:0a.0, mfunc 0x00001002,
devctl 0x44
Yenta: ISA IRQ mask 0x0000, PCI irq 11
Socket status: 30000010
SELinux: initialized (dev ramfs, type ramfs), uses
genfs_contexts
NET: Registered protocol family 10
Disabled Privacy Extensions on device c03e6a20(lo)
IPv6 over IPv4 tunneling driver
ACPI: AC Adapter [ADP1] (on-line)
Using generic hotkey driver
ACPI: Battery Slot [BAT1] (battery present)
ACPI: Power Button (FF) [PWRF]
ACPI: Lid Switch [LID0]
ACPI: Sleep Button (CM) [SLPB]
ACPI: Power Button (CM) [PWRB]
ibm_acpi: Using generic hotkey driver
toshiba_acpi: Using generic hotkey driver
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
audit(1126213138.973:2): avc:  denied  { write } for 
pid=1433 comm="fsck" name= "rhgb-console" dev=ramfs
ino=5177 scontext=system_u:system_r:fsadm_t
tcontext=sy stem_u:object_r:ramfs_t tclass=fifo_file
EXT3 FS on dm-0, internal journal
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hda6, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
SELinux: initialized (dev hda6, type ext3), uses xattr
SELinux: initialized (dev tmpfs, type tmpfs), uses
transition SIDs
NTFS driver 2.1.22 [Flags: R/W MODULE].
NTFS-fs error (device hda1): parse_options():
Unrecognized mount option owner.ro .umask.
Adding 917496k swap on /dev/VolGroup00/LogVol01. 
Priority:-1 extents:1
SELinux: initialized (dev binfmt_misc, type
binfmt_misc), uses genfs_contexts
cs: IO port probe 0xc00-0xcff: clean.
cs: IO port probe 0x800-0x8ff: excluding 0x818-0x84f
0x858-0x89f
cs: IO port probe 0x100-0x4ff: excluding 0x480-0x48f
0x4d0-0x4d7
cs: IO port probe 0xa00-0xaff: clean.
cs: memory probe 0xa0000000-0xa0ffffff: clean.
Unable to handle kernel NULL pointer dereference at
virtual address 00000000
 printing eip:
c0138ea5
*pde = 1d54f067
Oops: 0000 [#1]
Modules linked in: p80211(U) ntfs(U) video button
battery ac md5 ipv6 yenta_sock et rsrc_nonstatic
ohci_hcd ehci_hcd shpchp i2c_sis96x i2c_core
snd_intel8x0m snd _intel8x0 snd_ac97_codec
snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq
sn d_seq_device snd_pcm_oss snd_mixer_oss snd_pcm
snd_timer snd soundcore snd_page_ alloc orinoco_cs
pcmcia orinoco hermes pcmcia_core sis900 mii
dm_snapshot dm_zer o dm_mirror ext3 jbd dm_mod
CPU:    0
EIP:    0060:[<c0138ea5>]    Not tainted VLI
EFLAGS: 00010246   (2.6.12-1.1447_FC4)
EIP is at call_usermodehelper+0x136/0x171
eax: 00000000   ebx: dd560e34   ecx: ddfca540   edx:
00000000
esi: 00000000   edi: dd560e80   ebp: dd560f68   esp:
dd560e30
ds: 007b   es: 007b   ss: 0068
Process modprobe (pid: 1609, threadinfo=dd560000
task=dd357550)
Stack: dd676c1c 00000000 dd560e38 dd560e38 c0138d1f
dd560ea4 00000000 00000000
       00000000 00000000 1d244b3c 00000000 0000000a
c038746f 00000000 00000000
       4b87ad6e 00000000 00000000 00000000 00000000
1d244b3c 00000000 0000000a
Call Trace:
 [<c0138d1f>] __call_usermodehelper+0x0/0x50
 [<de9ea020>] p80211_run_sbin_hotplug+0x104/0x13c
[p80211]
 [<c01f42a9>] inode_alloc_security+0x24/0xc9
 [<c031ff6c>] netlink_insert+0x86/0x12c
 [<de9e6016>] init_module+0x16/0x19 [p80211]
 [<c014889c>] sys_init_module+0xca/0x1c4
 [<c0103a61>] syscall_call+0x7/0xb
Code: 84 24 94 00 00 00 89 44 24 2c c7 44 24 28 3c 4b
24 1d c7 44 24 40 6e ad 87  4b 8b 0d 94 ea 47 c0 b8 f0
ff ff ff 85 c9 74 07 31 c0 <80> 3e 00 75 0b 81 c4 9c 
00 00 00 5b 5e 5f 5d c3 89 da 89 c8 e8
 <6>eth0: Media Link Off
SELinux: initialized (dev rpc_pipefs, type
rpc_pipefs), uses genfs_contexts
Bluetooth: Core ver 2.7
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager
initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP ver 2.7
Bluetooth: L2CAP socket layer initialized
Bluetooth: RFCOMM ver 1.5
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
NTFS-fs error (device hda1): parse_options():
Unrecognized mount option owner.ro .umask.
SELinux: initialized (dev autofs, type autofs), uses
genfs_contexts
SELinux: initialized (dev autofs, type autofs), uses
genfs_contexts
lp: driver loaded but no devices found
NTFS-fs error (device hda1): parse_options():
Unrecognized mount option owner.ro .umask.
application mixer_applet2 uses obsolete OSS audio
interface
eth0: Media Link On 100mbps full-duplex
eth0: Media Link On 100mbps full-duplex
eth0: no IPv6 routers present
cs: IO port probe 0xc00-0xcff: clean.
cs: IO port probe 0x800-0x8ff: excluding 0x818-0x84f
0x858-0x89f
cs: IO port probe 0x100-0x4ff: excluding 0x480-0x48f
0x4d0-0x4d7
cs: IO port probe 0xa00-0xaff: clean.
prism2_cs: Unknown symbol p80211netdev_rx
prism2_cs: Unknown symbol register_wlandev
prism2_cs: Unknown symbol wlan_unsetup
prism2_cs: Unknown symbol unregister_wlandev
prism2_cs: Unknown symbol p80211netdev_hwremoved
prism2_cs: Unknown symbol wlan_setup
prism2_cs: Unknown symbol p80211skb_rxmeta_attach
prism2_cs: Unknown symbol p80211netdev_rx
prism2_cs: Unknown symbol register_wlandev
prism2_cs: Unknown symbol wlan_unsetup
prism2_cs: Unknown symbol unregister_wlandev
prism2_cs: Unknown symbol p80211netdev_hwremoved
prism2_cs: Unknown symbol wlan_setup
prism2_cs: Unknown symbol p80211skb_rxmeta_attach
prism2_cs: Unknown symbol p80211netdev_rx
prism2_cs: Unknown symbol register_wlandev
prism2_cs: Unknown symbol wlan_unsetup
prism2_cs: Unknown symbol unregister_wlandev
prism2_cs: Unknown symbol p80211netdev_hwremoved
prism2_cs: Unknown symbol wlan_setup
prism2_cs: Unknown symbol p80211skb_rxmeta_attach
prism2_cs: Unknown symbol p80211netdev_rx
prism2_cs: Unknown symbol register_wlandev
prism2_cs: Unknown symbol wlan_unsetup
prism2_cs: Unknown symbol unregister_wlandev
prism2_cs: Unknown symbol p80211netdev_hwremoved
prism2_cs: Unknown symbol wlan_setup
prism2_cs: Unknown symbol p80211skb_rxmeta_attach
eth0: Media Link On 100mbps full-duplex
eth0: no IPv6 routers present
prism2_cs: Unknown symbol p80211netdev_rx
prism2_cs: Unknown symbol register_wlandev
prism2_cs: Unknown symbol wlan_unsetup
prism2_cs: Unknown symbol unregister_wlandev
prism2_cs: Unknown symbol p80211netdev_hwremoved
prism2_cs: Unknown symbol wlan_setup
prism2_cs: Unknown symbol p80211skb_rxmeta_attach
prism2_cs: Unknown symbol p80211netdev_rx
prism2_cs: Unknown symbol register_wlandev
prism2_cs: Unknown symbol wlan_unsetup
prism2_cs: Unknown symbol unregister_wlandev
prism2_cs: Unknown symbol p80211netdev_hwremoved
prism2_cs: Unknown symbol wlan_setup
prism2_cs: Unknown symbol p80211skb_rxmeta_attach
ieee1394: Initialized config rom entry `ip1394'
ieee1394: Initialized config rom entry `ip1394'
cs: pcmcia_socket0: unable to apply power.
prism2_cs: Unknown symbol p80211netdev_rx
prism2_cs: Unknown symbol register_wlandev
prism2_cs: Unknown symbol wlan_unsetup
prism2_cs: Unknown symbol unregister_wlandev
prism2_cs: Unknown symbol p80211netdev_hwremoved
prism2_cs: Unknown symbol wlan_setup
prism2_cs: Unknown symbol p80211skb_rxmeta_attach
ieee1394: Initialized config rom entry `ip1394'
prism2_cs: disagrees about version of symbol
p80211netdev_rx
prism2_cs: Unknown symbol p80211netdev_rx
prism2_cs: disagrees about version of symbol
register_wlandev
prism2_cs: Unknown symbol register_wlandev
prism2_cs: disagrees about version of symbol
wlan_unsetup
prism2_cs: Unknown symbol wlan_unsetup
prism2_cs: disagrees about version of symbol
unregister_wlandev
prism2_cs: Unknown symbol unregister_wlandev
prism2_cs: disagrees about version of symbol
p80211netdev_hwremoved
prism2_cs: Unknown symbol p80211netdev_hwremoved
prism2_cs: disagrees about version of symbol
wlan_setup
prism2_cs: Unknown symbol wlan_setup
prism2_cs: disagrees about version of symbol
p80211skb_rxmeta_attach
prism2_cs: Unknown symbol p80211skb_rxmeta_attach
prism2_cs: disagrees about version of symbol
p80211netdev_rx
prism2_cs: Unknown symbol p80211netdev_rx
prism2_cs: disagrees about version of symbol
register_wlandev
prism2_cs: Unknown symbol register_wlandev
prism2_cs: disagrees about version of symbol
wlan_unsetup
prism2_cs: Unknown symbol wlan_unsetup
prism2_cs: disagrees about version of symbol
unregister_wlandev
prism2_cs: Unknown symbol unregister_wlandev
prism2_cs: disagrees about version of symbol
p80211netdev_hwremoved
prism2_cs: Unknown symbol p80211netdev_hwremoved
prism2_cs: disagrees about version of symbol
wlan_setup
prism2_cs: Unknown symbol wlan_setup
prism2_cs: disagrees about version of symbol
p80211skb_rxmeta_attach
prism2_cs: Unknown symbol p80211skb_rxmeta_attach
prism2_cs: disagrees about version of symbol
p80211netdev_rx
prism2_cs: Unknown symbol p80211netdev_rx
prism2_cs: disagrees about version of symbol
register_wlandev
prism2_cs: Unknown symbol register_wlandev
prism2_cs: disagrees about version of symbol
wlan_unsetup
prism2_cs: Unknown symbol wlan_unsetup
prism2_cs: disagrees about version of symbol
unregister_wlandev
prism2_cs: Unknown symbol unregister_wlandev
prism2_cs: disagrees about version of symbol
p80211netdev_hwremoved
prism2_cs: Unknown symbol p80211netdev_hwremoved
prism2_cs: disagrees about version of symbol
wlan_setup
prism2_cs: Unknown symbol wlan_setup
prism2_cs: disagrees about version of symbol
p80211skb_rxmeta_attach
prism2_cs: Unknown symbol p80211skb_rxmeta_attach
prism2_cs: disagrees about version of symbol
p80211netdev_rx
prism2_cs: Unknown symbol p80211netdev_rx
prism2_cs: disagrees about version of symbol
register_wlandev
prism2_cs: Unknown symbol register_wlandev
prism2_cs: disagrees about version of symbol
wlan_unsetup
prism2_cs: Unknown symbol wlan_unsetup
prism2_cs: disagrees about version of symbol
unregister_wlandev
prism2_cs: Unknown symbol unregister_wlandev
prism2_cs: disagrees about version of symbol
p80211netdev_hwremoved
prism2_cs: Unknown symbol p80211netdev_hwremoved
prism2_cs: disagrees about version of symbol
wlan_setup
prism2_cs: Unknown symbol wlan_setup
prism2_cs: disagrees about version of symbol
p80211skb_rxmeta_attach
prism2_cs: Unknown symbol p80211skb_rxmeta_attach
prism2_cs: disagrees about version of symbol
p80211netdev_rx
prism2_cs: Unknown symbol p80211netdev_rx
prism2_cs: disagrees about version of symbol
register_wlandev
prism2_cs: Unknown symbol register_wlandev
prism2_cs: disagrees about version of symbol
wlan_unsetup
prism2_cs: Unknown symbol wlan_unsetup
prism2_cs: disagrees about version of symbol
unregister_wlandev
prism2_cs: Unknown symbol unregister_wlandev
prism2_cs: disagrees about version of symbol
p80211netdev_hwremoved
prism2_cs: Unknown symbol p80211netdev_hwremoved
prism2_cs: disagrees about version of symbol
wlan_setup
prism2_cs: Unknown symbol wlan_setup
prism2_cs: disagrees about version of symbol
p80211skb_rxmeta_attach
prism2_cs: Unknown symbol p80211skb_rxmeta_attach
prism2_cs: disagrees about version of symbol
p80211netdev_rx
prism2_cs: Unknown symbol p80211netdev_rx
prism2_cs: disagrees about version of symbol
register_wlandev
prism2_cs: Unknown symbol register_wlandev
prism2_cs: disagrees about version of symbol
wlan_unsetup
prism2_cs: Unknown symbol wlan_unsetup
prism2_cs: disagrees about version of symbol
unregister_wlandev
prism2_cs: Unknown symbol unregister_wlandev
prism2_cs: disagrees about version of symbol
p80211netdev_hwremoved
prism2_cs: Unknown symbol p80211netdev_hwremoved
prism2_cs: disagrees about version of symbol
wlan_setup
prism2_cs: Unknown symbol wlan_setup
prism2_cs: disagrees about version of symbol
p80211skb_rxmeta_attach
prism2_cs: Unknown symbol p80211skb_rxmeta_attach
prism2_cs: disagrees about version of symbol
p80211netdev_rx
prism2_cs: Unknown symbol p80211netdev_rx
prism2_cs: disagrees about version of symbol
register_wlandev
prism2_cs: Unknown symbol register_wlandev
prism2_cs: disagrees about version of symbol
wlan_unsetup
prism2_cs: Unknown symbol wlan_unsetup
prism2_cs: disagrees about version of symbol
unregister_wlandev
prism2_cs: Unknown symbol unregister_wlandev
prism2_cs: disagrees about version of symbol
p80211netdev_hwremoved
prism2_cs: Unknown symbol p80211netdev_hwremoved
prism2_cs: disagrees about version of symbol
wlan_setup
prism2_cs: Unknown symbol wlan_setup
prism2_cs: disagrees about version of symbol
p80211skb_rxmeta_attach
prism2_cs: Unknown symbol p80211skb_rxmeta_attach
prism2_cs: disagrees about version of symbol
p80211netdev_rx
prism2_cs: Unknown symbol p80211netdev_rx
prism2_cs: disagrees about version of symbol
register_wlandev
prism2_cs: Unknown symbol register_wlandev
prism2_cs: disagrees about version of symbol
wlan_unsetup
prism2_cs: Unknown symbol wlan_unsetup
prism2_cs: disagrees about version of symbol
unregister_wlandev
prism2_cs: Unknown symbol unregister_wlandev
prism2_cs: disagrees about version of symbol
p80211netdev_hwremoved
prism2_cs: Unknown symbol p80211netdev_hwremoved
prism2_cs: disagrees about version of symbol
wlan_setup
prism2_cs: Unknown symbol wlan_setup
prism2_cs: disagrees about version of symbol
p80211skb_rxmeta_attach
prism2_cs: Unknown symbol p80211skb_rxmeta_attach
prism2_cs: disagrees about version of symbol
p80211netdev_rx
prism2_cs: Unknown symbol p80211netdev_rx
prism2_cs: disagrees about version of symbol
register_wlandev
prism2_cs: Unknown symbol register_wlandev
prism2_cs: disagrees about version of symbol
wlan_unsetup
prism2_cs: Unknown symbol wlan_unsetup
prism2_cs: disagrees about version of symbol
unregister_wlandev
prism2_cs: Unknown symbol unregister_wlandev
prism2_cs: disagrees about version of symbol
p80211netdev_hwremoved
prism2_cs: Unknown symbol p80211netdev_hwremoved
prism2_cs: disagrees about version of symbol
wlan_setup
prism2_cs: Unknown symbol wlan_setup
prism2_cs: disagrees about version of symbol
p80211skb_rxmeta_attach
prism2_cs: Unknown symbol p80211skb_rxmeta_attach
eth0: Media Link On 100mbps full-duplex
eth0: no IPv6 routers present
prism2_cs: disagrees about version of symbol
p80211netdev_rx
prism2_cs: Unknown symbol p80211netdev_rx
prism2_cs: disagrees about version of symbol
register_wlandev
prism2_cs: Unknown symbol register_wlandev
prism2_cs: disagrees about version of symbol
wlan_unsetup
prism2_cs: Unknown symbol wlan_unsetup
prism2_cs: disagrees about version of symbol
unregister_wlandev
prism2_cs: Unknown symbol unregister_wlandev
prism2_cs: disagrees about version of symbol
p80211netdev_hwremoved
prism2_cs: Unknown symbol p80211netdev_hwremoved
prism2_cs: disagrees about version of symbol
wlan_setup
prism2_cs: Unknown symbol wlan_setup
prism2_cs: disagrees about version of symbol
p80211skb_rxmeta_attach
prism2_cs: Unknown symbol p80211skb_rxmeta_attach
prism2_cs: disagrees about version of symbol
p80211netdev_rx
prism2_cs: Unknown symbol p80211netdev_rx
prism2_cs: disagrees about version of symbol
register_wlandev
prism2_cs: Unknown symbol register_wlandev
prism2_cs: disagrees about version of symbol
wlan_unsetup
prism2_cs: Unknown symbol wlan_unsetup
prism2_cs: disagrees about version of symbol
unregister_wlandev
prism2_cs: Unknown symbol unregister_wlandev
prism2_cs: disagrees about version of symbol
p80211netdev_hwremoved
prism2_cs: Unknown symbol p80211netdev_hwremoved
prism2_cs: disagrees about version of symbol
wlan_setup
prism2_cs: Unknown symbol wlan_setup
prism2_cs: disagrees about version of symbol
p80211skb_rxmeta_attach
prism2_cs: Unknown symbol p80211skb_rxmeta_attach
prism2_cs: disagrees about version of symbol
p80211netdev_rx
prism2_cs: Unknown symbol p80211netdev_rx
prism2_cs: disagrees about version of symbol
register_wlandev
prism2_cs: Unknown symbol register_wlandev
prism2_cs: disagrees about version of symbol
wlan_unsetup
prism2_cs: Unknown symbol wlan_unsetup
prism2_cs: disagrees about version of symbol
unregister_wlandev
prism2_cs: Unknown symbol unregister_wlandev
prism2_cs: disagrees about version of symbol
p80211netdev_hwremoved
prism2_cs: Unknown symbol p80211netdev_hwremoved
prism2_cs: disagrees about version of symbol
wlan_setup
prism2_cs: Unknown symbol wlan_setup
prism2_cs: disagrees about version of symbol
p80211skb_rxmeta_attach
prism2_cs: Unknown symbol p80211skb_rxmeta_attach
eth0: Media Link On 100mbps full-duplex
eth0: no IPv6 routers present
prism2_cs: disagrees about version of symbol
p80211netdev_rx
prism2_cs: Unknown symbol p80211netdev_rx
prism2_cs: disagrees about version of symbol
register_wlandev
prism2_cs: Unknown symbol register_wlandev
prism2_cs: disagrees about version of symbol
wlan_unsetup
prism2_cs: Unknown symbol wlan_unsetup
prism2_cs: disagrees about version of symbol
unregister_wlandev
prism2_cs: Unknown symbol unregister_wlandev
prism2_cs: disagrees about version of symbol
p80211netdev_hwremoved
prism2_cs: Unknown symbol p80211netdev_hwremoved
prism2_cs: disagrees about version of symbol
wlan_setup
prism2_cs: Unknown symbol wlan_setup
prism2_cs: disagrees about version of symbol
p80211skb_rxmeta_attach
prism2_cs: Unknown symbol p80211skb_rxmeta_attach


--- Daniel Ritz <daniel.ritz at gmx.ch> wrote:

> On Thursday 08 September 2005 19.33, David Hinds
> wrote:
> > On Thu, Sep 08, 2005 at 06:30:23PM +0200, Daniel
> Ritz wrote:
> > > hi james
> > > 
> > > [ please always use reply-to-all. i'm not
> subscribed to the list ]
> > > 
> > > you have a notebook with graphic controller
> working in shared memory mode
> > > which means it uses the main memory.
> unfortunatley the is BIOS crap and
> > > forgets to report that. add the following to the
> kernel command line to
> > > fix the problem:
> > > 	reserve=0x1e000000,0x2000000
> > > it tells the kernel not to use the region from
> 480-512 MB.
> > 
> > I thought that this had been fixed, so the kernel
> would round up
> > apparent memory sizes that were a bit smaller than
> a power of two.
> 
> it currently only rounds up to the next MB. but that
> doesn't catch
> the shared VGAs...
> 
> > I guess not.  It really should get fixed properly
> (even though it
> > technically is not a kernel problem), because it
> generates a huge
> > amount of problem reports.
> > 
> 
> something like the attached patch...
> 
> cc:ing linus as he is the one that added the "find
> the largest gap" code
> that comes handy here...
> and cc:ing andrew for the obvious reason...
> 
> rgds
> -daniel
> 
> ----
> 
> [PATCH] i386/x86_64: align pci iomem start address
> to 64MB
> 
> align the PCI iomemory starting address to a muliple
> of 64MB to avoid problems
> with some BIOS that forget to report the memory used
> by a shared memory graphic
> controller in the e820 memory map.
> 
> most people don't give the shared VGA more than
> 64MB, right?
> 
> Signed-off-by: Daniel Ritz <daniel.ritz at gmx.ch>
> 
> diff --git a/arch/i386/kernel/setup.c
> b/arch/i386/kernel/setup.c
> --- a/arch/i386/kernel/setup.c
> +++ b/arch/i386/kernel/setup.c
> @@ -1325,7 +1325,16 @@ static void __init
> register_memory(void)
>  	i = e820.nr_map;
>  	while (--i >= 0) {
>  		unsigned long long start = e820.map[i].addr;
> -		unsigned long long end = start +
> e820.map[i].size;
> +		unsigned long long end;
> +
> +		/*
> +		 * try to find the largest gap starting at a
> muliple of 64MB.
> +		 * this is to avoid problems with some BIOSen
> that forget to report
> +		 * memory used by the shared memory graphic
> controller.
> +		 * most people are not going to use more than
> 64MB for a shared
> +		 * controller, right? round up to 128MB?
> +		 */
> +		end = (start + e820.map[i].size + 0x3ffffff) &
> ~0x3ffffff;
>  
>  		/*
>  		 * Since "last" is at most 4GB, we know we'll
> @@ -1344,14 +1353,10 @@ static void __init
> register_memory(void)
>  	}
>  
>  	/*
> -	 * Start allocating dynamic PCI memory a bit into
> the gap,
> -	 * aligned up to the nearest megabyte.
> -	 *
> -	 * Question: should we try to pad it up a bit (do
> something
> -	 * like " + (gapsize >> 3)" in there too?). We now
> have the
> -	 * technology.
> +	 * Start allocating dynamic PCI memory at gapstart
> which is already
> +	 * rounded up to a multiple of 6 MB.
>  	 */
> -	pci_mem_start = (gapstart + 0xfffff) & ~0xfffff;
> +	pci_mem_start = gapstart;
>  
>  	printk("Allocating PCI resources starting at %08lx
> (gap: %08lx:%08lx)\n",
>  		pci_mem_start, gapstart, gapsize);
> diff --git a/arch/x86_64/kernel/e820.c
> b/arch/x86_64/kernel/e820.c
> --- a/arch/x86_64/kernel/e820.c
> +++ b/arch/x86_64/kernel/e820.c
> @@ -578,7 +578,16 @@ __init void
> e820_setup_gap(void)
>  	i = e820.nr_map;
>  	while (--i >= 0) {
>  		unsigned long long start = e820.map[i].addr;
> -		unsigned long long end = start +
> e820.map[i].size;
> +		unsigned long long end;
> +
> +		/*
> +		 * try to find the largest gap starting at a
> muliple of 64MB.
> +		 * this is to avoid problems with some BIOSen
> that forget to report
> +		 * memory used by the shared memory graphic
> controller.
> +		 * most people are not going to use more than
> 64MB for a shared
> +		 * controller, right? round up to 128MB?
> +		 */
> +		end = (start + e820.map[i].size + 0x3ffffff) &
> ~0x3ffffff;
>  
>  		/*
>  		 * Since "last" is at most 4GB, we know we'll
> @@ -604,14 +613,10 @@ __init void
> e820_setup_gap(void)
>  	}
>  
>  	/*
> -	 * Start allocating dynamic PCI memory a bit into
> the gap,
> -	 * aligned up to the nearest megabyte.
> -	 *
> -	 * Question: should we try to pad it up a bit (do
> something
> -	 * like " + (gapsize >> 3)" in there too?). We now
> have the
> -	 * technology.
> +	 * Start allocating dynamic PCI memory at gapstart
> which is already
> +	 * rounded up to a multiple of 6 MB.
>  	 */
> -	pci_mem_start = (gapstart + 0xfffff) & ~0xfffff;
> +	pci_mem_start = gapstart;
>  
>  	printk(KERN_INFO "Allocating PCI resources
> starting at %lx (gap: %lx:%lx)\n",
>  		pci_mem_start, gapstart, gapsize);
> 
>  
> 



	
		
______________________________________________________
Click here to donate to the Hurricane Katrina relief effort.
http://store.yahoo.com/redcross-donate3/



More information about the linux-pcmcia mailing list