Obtaining a list of memory address ranges allocated to processes
I am trying to create a custom ELF and Windows PE loader for the purpose of security research. I am having a difficult time finding how to allocate memory for a binary at the desired address in memory (especially if its non-relocatable). I would like to see why I cannot get memory allocated at the exact address request in the binary headers. Is there a program or system call that allows me to see a list of memory address ranges allocated to the running processes on a system? Stephen - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Obtaining a list of memory address ranges allocated to processes
I am trying to create a custom ELF and Windows PE loader for the purpose of security research. I am having a difficult time finding how to allocate memory for a binary at the desired address in memory (especially if its non-relocatable). I would like to see why I cannot get memory allocated at the exact address request in the binary headers. Is there a program or system call that allows me to see a list of memory address ranges allocated to the running processes on a system? Stephen - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: OOPS on 2.4.4-ac4
The nvidia driver has been fine for me up to 2.4.2-ac20. I am going to update to 2.4.4-ac8 today. In regards to the module the source code is available from nvidia for inspection. The library that they want you to use with it is binary only. The library should be source code as well but the powers that be have said otherwise. I will keep tabs on the release for kernel oops as well. I am using XFree 4.0.3 with NVIDIA-0.9-769 Stephen On Sat, 12 May 2001, Alan Cox wrote: > > > Ok, I will remove vmware and switch from the nvidia driver the nv > driver from > XFree 4.3. Maybe I get the oops again. > > Let me know if you do. I've got some other dmfe reports I'm looking at so its > quite possible that is the trigger, but this time I'll be able to know its not > giant binary stuff 8) > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > -- --- Buyer's Guide for a Operating System: Don't care to know: Mac Don't mind knowing but not too much: Windows Hit me! I can take it!: Linux - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: OOPS on 2.4.4-ac4
The nvidia driver has been fine for me up to 2.4.2-ac20. I am going to update to 2.4.4-ac8 today. In regards to the module the source code is available from nvidia for inspection. The library that they want you to use with it is binary only. The library should be source code as well but the powers that be have said otherwise. I will keep tabs on the release for kernel oops as well. I am using XFree 4.0.3 with NVIDIA-0.9-769 Stephen On Sat, 12 May 2001, Alan Cox wrote: Ok, I will remove vmware and switch from the nvidia driver the nv driver from XFree 4.3. Maybe I get the oops again. Let me know if you do. I've got some other dmfe reports I'm looking at so its quite possible that is the trigger, but this time I'll be able to know its not giant binary stuff 8) - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ -- --- Buyer's Guide for a Operating System: Don't care to know: Mac Don't mind knowing but not too much: Windows Hit me! I can take it!: Linux - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
2.4.4-ac4 OOPS: acpi_get_timer
I compiled 2.4.4-ac4 with gcc-2.95.3. No problems with previous versions until today. Here is the output of the kenerl panic from ksymoops: EIP: c0247cfa Trace: c025602e Trace: c02567a5 Trace: c0105058 Trace: c0105594 Code; c0247cfa <_EIP>: Code: c0247cfa 0: 8b 80 d4 00 00 00 mov, 0xd4(%eax), %eax Code: c0247d00 6: 50push %eax Code: c0247d01 7: e8 4a 77 ff ffcall 7756 <_EIP+0x7756> c023f450 Code: c0247d06 c: 89 03 mov %eax, (%ebx) Code: c0247d08 e: 31 c0 xor %eax, %eax Code: c0247d0a 10: 83 c4 04 add $0x4, %esp Code: c0247d0d 13: eb 00 jmp 15 <_EIP+0x15> c0247d0f acpi_get_timer is in drivers/acpi/hardware/hwtimer It makes a call to acpi_os_in32 acpi_os_in32 is in drivers/acpi/os.c This takes the argument of an ACPI_IO_ADDRESS for a port number. What is given as arguments in acpi_get_timer is acpi_os_in32((ACPI_IO_ADDRESS) ACPI_GET_ADDRESS (acpi_gbl_FADT->Xpm_tmr_blk.address)); ACPI_IO_ADDRESS is a cast ACPI_GET_ADDRESS is a converter from 32 or 64 bit addresses to 16 bit addresses if necessary. On this system it should not do anything. acpi_gbl+FADT is a FADT_DESCRIPTOR_REV2 (a struct). Looking at FADT_DESCRIPTOR_REV2's definition I fail to see where the pointer is referring to in the struct. There is no element named Xpm_tmr_blk) --- The message that I received at the top of the oops was: unable to handle NULL pointer dereference at virutal address 00d4 --- System: Dual P3@450Mhz, 392 MB Ram Supermicro P6DBE motherboard ACPI Disabled during first boot - got oops ACPI Enabled during second boot - got same oops ACPI settings: all except for battery. Stephen --- Buyer's Guide for a Operating System: Don't care to know: Mac Don't mind knowing but not too much: Windows Hit me! I can take it!: Linux - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
2.4.4-ac4 OOPS: acpi_get_timer
I compiled 2.4.4-ac4 with gcc-2.95.3. No problems with previous versions until today. Here is the output of the kenerl panic from ksymoops: EIP: c0247cfa acpi_get_timer+e/2c Trace: c025602e bm_initialize+56/278 Trace: c02567a5 bm_osl_init+79/8c Trace: c0105058 init+58/1d0 Trace: c0105594 kernel thread+28/38 Code; c0247cfa acpi_get_timer+e/2c _EIP: Code: c0247cfa acpi_get_timer+e/2c 0: 8b 80 d4 00 00 00 mov, 0xd4(%eax), %eax Code: c0247d00 acpi_get_timer+14/2c 6: 50push %eax Code: c0247d01 acpi_get_timer+15/2c 7: e8 4a 77 ff ffcall 7756 _EIP+0x7756 c023f450 acpi_os_in_32+0/8 Code: c0247d06 acpi_get_timer+1a/2c c: 89 03 mov %eax, (%ebx) Code: c0247d08 acpi_get_timer +1c/2c e: 31 c0 xor %eax, %eax Code: c0247d0a acpi_get_timer+1e/2c 10: 83 c4 04 add $0x4, %esp Code: c0247d0d acpi_get_timer+21/2c 13: eb 00 jmp 15 _EIP+0x15 c0247d0f acpi_get_timer+23/2c acpi_get_timer is in drivers/acpi/hardware/hwtimer It makes a call to acpi_os_in32 acpi_os_in32 is in drivers/acpi/os.c This takes the argument of an ACPI_IO_ADDRESS for a port number. What is given as arguments in acpi_get_timer is acpi_os_in32((ACPI_IO_ADDRESS) ACPI_GET_ADDRESS (acpi_gbl_FADT-Xpm_tmr_blk.address)); ACPI_IO_ADDRESS is a cast ACPI_GET_ADDRESS is a converter from 32 or 64 bit addresses to 16 bit addresses if necessary. On this system it should not do anything. acpi_gbl+FADT is a FADT_DESCRIPTOR_REV2 (a struct). Looking at FADT_DESCRIPTOR_REV2's definition I fail to see where the pointer is referring to in the struct. There is no element named Xpm_tmr_blk) --- The message that I received at the top of the oops was: unable to handle NULL pointer dereference at virutal address 00d4 --- System: Dual P3@450Mhz, 392 MB Ram Supermicro P6DBE motherboard ACPI Disabled during first boot - got oops ACPI Enabled during second boot - got same oops ACPI settings: all except for battery. Stephen --- Buyer's Guide for a Operating System: Don't care to know: Mac Don't mind knowing but not too much: Windows Hit me! I can take it!: Linux - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: Recent ACPI patch
No. I tried with everything in ACPI selected in the general setup config. Broke. Tried it with only ACPI enabled and no options selected. Broke. ac12 and on don't have it. I will try it against and report where it broke. Stephen On Wed, 25 Apr 2001, Grover, Andrew wrote: > Doh! > > OK, I'm on it. ;-) BTW did ACPI in ac11 build for you? > > -- Andy > -- --- Buyer's Guide for a Operating System: Don't care to know: Mac Don't mind knowing but not too much: Windows Hit me! I can take it!: Linux - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Recent ACPI patch
I noticed that the big update patch for ACPI was a part of 2.4.3-ac11 (Can remember). Now its not a part of 2.4.3-ac12. Has it been removed? I have turned on experimental settings when running make xconfig. Stephen --- Buyer's Guide for a Operating System: Don't care to know: Mac Don't mind knowing but not too much: Windows Hit me! I can take it!: Linux - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Recent ACPI patch
I noticed that the big update patch for ACPI was a part of 2.4.3-ac11 (Can remember). Now its not a part of 2.4.3-ac12. Has it been removed? I have turned on experimental settings when running make xconfig. Stephen --- Buyer's Guide for a Operating System: Don't care to know: Mac Don't mind knowing but not too much: Windows Hit me! I can take it!: Linux - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.3-ac3 XIRCOM_CB only working as module
I have built this as a module due to the RedHat system I use (to be consistent). I found that the xircom_cb driver works fine as a module except for when using dhcp for dynamic ip address. If I set the ip address of the network card to a static ip number it work fine. Yet if I choose to use the dhcp to get my ip address packets leave, as seen via tcpdump, but it doesn't get an address. I watched tcpdump at the dhcp server and saw the packets come in from the laptop and the responses go out. The laptop either is ignoring the message coming from the dhcp server or some other bizarre reason. I cannot say if I noticed anything about the yenta_socket driver. If I could get dhcp to work fine I would be willing to give it a go. Stephen [EMAIL PROTECTED] On Thu, 12 Apr 2001, Arjan van de Ven wrote: > In article <[EMAIL PROTECTED]> you wrote: > > It looks like the new xircom_cb driver only works as module - if built > > in kernel there is no sign of eth0 setup. > > I haven't tried this; I'll look into this once I get back to work (eg where > my cardbus machine is). I would not be surprised if it > turns out to be of the "yenta_socket is not initialized yet, so the card is > invisible at pci scan time" type > > Greetings, >Arjan van de Ven > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > -- --- Buyer's Guide for a Operating System: Don't care to know: Mac Don't mind knowing but not too much: Windows Hit me! I can take it!: Linux - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.3-ac3 XIRCOM_CB only working as module
I have built this as a module due to the RedHat system I use (to be consistent). I found that the xircom_cb driver works fine as a module except for when using dhcp for dynamic ip address. If I set the ip address of the network card to a static ip number it work fine. Yet if I choose to use the dhcp to get my ip address packets leave, as seen via tcpdump, but it doesn't get an address. I watched tcpdump at the dhcp server and saw the packets come in from the laptop and the responses go out. The laptop either is ignoring the message coming from the dhcp server or some other bizarre reason. I cannot say if I noticed anything about the yenta_socket driver. If I could get dhcp to work fine I would be willing to give it a go. Stephen [EMAIL PROTECTED] On Thu, 12 Apr 2001, Arjan van de Ven wrote: In article [EMAIL PROTECTED] you wrote: It looks like the new xircom_cb driver only works as module - if built in kernel there is no sign of eth0 setup. I haven't tried this; I'll look into this once I get back to work (eg where my cardbus machine is). I would not be surprised if it turns out to be of the "yenta_socket is not initialized yet, so the card is invisible at pci scan time" type Greetings, Arjan van de Ven - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ -- --- Buyer's Guide for a Operating System: Don't care to know: Mac Don't mind knowing but not too much: Windows Hit me! I can take it!: Linux - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: ACPI:system description tables not found.
On Thu, 8 Mar 2001, Grover, Andrew wrote: > download the pmtools package from > http://developer.intel.com/technology/iapc/acpi/downloads.htm . (It's at the > bottom.) The acpidmp utility is what you're interested in (you can ignore > compile errors from the others.) Does this utility find tables, or not? > > Thanks -- Regards -- Andy I got the utility and compiled it under 2.4.2-ac12. No problem wit that. Acpidump reports: acpidump: cannot find an RSDP (Is ACPI enabled?). Yes ACPI is enabled in the system bios. Motherboard is P6DBU (Supermicro) with Dual P3 @ 450MHz. Stephen --- Buyer's Guide for a Operating System: Don't care to know: Mac Don't mind knowing but not too much: Windows Hit me! I can take it!: Linux - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: ACPI:system description tables not found.
On Thu, 8 Mar 2001, David Christensen wrote: > Stephen, > > Is there a BIOS setup option for enabling ACPI? Make sure it is enabled. The BIOS setup option for ACPI is enabled. > Also attach a copy of the E820 output from dmesg. Linux version 2.4.2 ([EMAIL PROTECTED]) (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #2 SMP Mon Feb 26 23:47:16 GMT 2001 BIOS-provided physical RAM map: BIOS-e820: 0009fc00 @ (usable) BIOS-e820: 0400 @ 0009fc00 (reserved) BIOS-e820: 0002 @ 000e (reserved) BIOS-e820: 17f0 @ 0010 (usable) BIOS-e820: 1000 @ fec0 (reserved) BIOS-e820: 1000 @ fee0 (reserved) BIOS-e820: 0004 @ fffc (reserved) Scan SMP from c000 for 1024 bytes. Scan SMP from c009fc00 for 1024 bytes. Scan SMP from c00f for 65536 bytes. found SMP MP-table at 000fb4f0 hm, page 000fb000 reserved twice. hm, page 000fc000 reserved twice. hm, page 000f2000 reserved twice. hm, page 000f3000 reserved twice. On node 0 totalpages: 98304 zone(0): 4096 pages. zone(1): 94208 pages. zone(2): 0 pages. Stephen --- Buyer's Guide for a Operating System: Don't care to know: Mac Don't mind knowing but not too much: Windows Hit me! I can take it!: Linux - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: ACPI:system description tables not found.
On Thu, 8 Mar 2001, David Christensen wrote: Stephen, Is there a BIOS setup option for enabling ACPI? Make sure it is enabled. The BIOS setup option for ACPI is enabled. Also attach a copy of the E820 output from dmesg. Linux version 2.4.2 ([EMAIL PROTECTED]) (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #2 SMP Mon Feb 26 23:47:16 GMT 2001 BIOS-provided physical RAM map: BIOS-e820: 0009fc00 @ (usable) BIOS-e820: 0400 @ 0009fc00 (reserved) BIOS-e820: 0002 @ 000e (reserved) BIOS-e820: 17f0 @ 0010 (usable) BIOS-e820: 1000 @ fec0 (reserved) BIOS-e820: 1000 @ fee0 (reserved) BIOS-e820: 0004 @ fffc (reserved) Scan SMP from c000 for 1024 bytes. Scan SMP from c009fc00 for 1024 bytes. Scan SMP from c00f for 65536 bytes. found SMP MP-table at 000fb4f0 hm, page 000fb000 reserved twice. hm, page 000fc000 reserved twice. hm, page 000f2000 reserved twice. hm, page 000f3000 reserved twice. On node 0 totalpages: 98304 zone(0): 4096 pages. zone(1): 94208 pages. zone(2): 0 pages. Stephen --- Buyer's Guide for a Operating System: Don't care to know: Mac Don't mind knowing but not too much: Windows Hit me! I can take it!: Linux - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: ACPI:system description tables not found.
On Thu, 8 Mar 2001, Grover, Andrew wrote: download the pmtools package from http://developer.intel.com/technology/iapc/acpi/downloads.htm . (It's at the bottom.) The acpidmp utility is what you're interested in (you can ignore compile errors from the others.) Does this utility find tables, or not? Thanks -- Regards -- Andy I got the utility and compiled it under 2.4.2-ac12. No problem wit that. Acpidump reports: acpidump: cannot find an RSDP (Is ACPI enabled?). Yes ACPI is enabled in the system bios. Motherboard is P6DBU (Supermicro) with Dual P3 @ 450MHz. Stephen --- Buyer's Guide for a Operating System: Don't care to know: Mac Don't mind knowing but not too much: Windows Hit me! I can take it!: Linux - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: ACPI:system description tables not found.
Motherboard is a P6DBE. IDE drives. Just found the site and confirmed it. Stephen On Thu, 8 Mar 2001, Stephen Torri wrote: > I am using kernel-2.4.2-ac12 (will try ac14). The motherboard is a > Supermicro P6DBU. (I will need to check the board when I get home to > confirm). I get the messages below when the system starts: > > acpi: system description tables not found > > The manufacturer says that there is support for acpi. So I willing to beat > it around a bit to get the tables found. Any ideas where to start? > > Stephen > > --- > Buyer's Guide for a Operating System: > Don't care to know: Mac > Don't mind knowing but not too much: Windows > Hit me! I can take it!: Linux > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > --- Buyer's Guide for a Operating System: Don't care to know: Mac Don't mind knowing but not too much: Windows Hit me! I can take it!: Linux - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
ACPI:system description tables not found.
I am using kernel-2.4.2-ac12 (will try ac14). The motherboard is a Supermicro P6DBU. (I will need to check the board when I get home to confirm). I get the messages below when the system starts: acpi: system description tables not found The manufacturer says that there is support for acpi. So I willing to beat it around a bit to get the tables found. Any ideas where to start? Stephen --- Buyer's Guide for a Operating System: Don't care to know: Mac Don't mind knowing but not too much: Windows Hit me! I can take it!: Linux - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
ACPI:system description tables not found.
I am using kernel-2.4.2-ac12 (will try ac14). The motherboard is a Supermicro P6DBU. (I will need to check the board when I get home to confirm). I get the messages below when the system starts: acpi: system description tables not found The manufacturer says that there is support for acpi. So I willing to beat it around a bit to get the tables found. Any ideas where to start? Stephen --- Buyer's Guide for a Operating System: Don't care to know: Mac Don't mind knowing but not too much: Windows Hit me! I can take it!: Linux - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: ACPI:system description tables not found.
Motherboard is a P6DBE. IDE drives. Just found the site and confirmed it. Stephen On Thu, 8 Mar 2001, Stephen Torri wrote: I am using kernel-2.4.2-ac12 (will try ac14). The motherboard is a Supermicro P6DBU. (I will need to check the board when I get home to confirm). I get the messages below when the system starts: acpi: system description tables not found The manufacturer says that there is support for acpi. So I willing to beat it around a bit to get the tables found. Any ideas where to start? Stephen --- Buyer's Guide for a Operating System: Don't care to know: Mac Don't mind knowing but not too much: Windows Hit me! I can take it!: Linux - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ --- Buyer's Guide for a Operating System: Don't care to know: Mac Don't mind knowing but not too much: Windows Hit me! I can take it!: Linux - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
PCMCIA CARDBUS detection incorrect.
using the following: kernel-2.4.2 (linus release - no patches added) kernel-2.2.17-4 (RedHat 7 release - no patches added) kgcc-2.96.66 (kernel config - see compressed text file) I have a Xircom Realport2 10/100 Card that uses the tulip_cb driver. In kernel-2.2.17-4 (from RedHat with pcmcia installed) the card is detected as: /sbin/cardctl ident Socket 0: product info: "Xircom", "RealPort2 CardBus Ethernet 10/100", "R2BE-100BTX", "1.00" manfid: 0x0105, 0x0103 function: 6 (network) Socket 1: no product info available /sbin/cardctl status Socket 0: 3.3V CardBus card function 0: [ready] Socket 1: no card cat /proc/pci PCI devices found: Bus 32, device 0, function 0: Ethernet controller: Unknown vendor Unknown device (rev 3). Vendor id=115d. Device id=3. Medium devsel. IRQ 3. I/O at 0x100 [0x101]. Non-prefetchable 32 bit memory at 0x6000d000 [0x6000d000]. Non-prefetchable 32 bit memory at 0x6000c000 [0x6000c000]. Bus 0, device 0, function 0: Host bridge: Intel 440BX - 82443BX Host (rev 3). Medium devsel. Master Capable. Latency=64. Prefetchable 32 bit memory at 0xe800 [0xe808]. Bus 0, device 1, function 0: PCI bridge: Intel 440BX - 82443BX AGP (rev 3). Medium devsel. Master Capable. Latency=128. Min Gnt=140. Bus 0, device 3, function 0: ISA bridge: Intel 82371AB PIIX4 ISA (rev 2). Medium devsel. Fast back-to-back capable. Master Capable. No bursts. Bus 0, device 3, function 1: IDE interface: Intel 82371AB PIIX4 IDE (rev 1). Medium devsel. Fast back-to-back capable. Master Capable. Latency=64. I/O at 0xfc60 [0xfc61]. Bus 0, device 3, function 2: USB Controller: Intel 82371AB PIIX4 USB (rev 1). Medium devsel. Fast back-to-back capable. IRQ 11. Master Capable. No bursts. I/O at 0xfca0 [0xfca1]. Bus 0, device 3, function 3: Bridge: Intel 82371AB PIIX4 ACPI (rev 2). Medium devsel. Fast back-to-back capable. Bus 0, device 6, function 0: Multimedia audio controller: Unknown vendor Unknown device (rev 0). Vendor id=1102. Device id=8938. Slow devsel. IRQ 5. Master Capable. Latency=96. Min Gnt=12.Max Lat=128. I/O at 0xfcc0 [0xfcc1]. I/O at 0xfc40 [0xfc41]. Bus 0, device 7, function 0: Communication controller: Unknown vendor Unknown device (rev 1). Vendor id=134d. Device id=7890. Medium devsel. IRQ 11. I/O at 0xfc00 [0xfc01]. Bus 0, device 10, function 0: CardBus bridge: Texas Instruments Unknown device (rev 1). Vendor id=104c. Device id=ac1c. Medium devsel. Master Capable. Latency=168. Min Gnt=128.Max Lat=7. Bus 0, device 10, function 1: CardBus bridge: Texas Instruments Unknown device (rev 1). Vendor id=104c. Device id=ac1c. Medium devsel. Master Capable. Latency=168. Min Gnt=192.Max Lat=7. Bus 1, device 0, function 0: VGA compatible controller: Trident Unknown device (rev 73). Vendor id=1023. Device id=9525. Medium devsel. Fast back-to-back capable. IRQ 11. Master Capable. Latency=64. Non-prefetchable 32 bit memory at 0xfe40 [0xfe40]. Non-prefetchable 32 bit memory at 0xfedc [0xfedc]. Non-prefetchable 32 bit memory at 0xfe80 [0xfe80]. The problem is that when I run kernel-2.4.2 the pcmcia does start when compiled as modules (just so that it keeps the RH7 scripts happy). Yet the cardctl reports: /sbin/cardctl ident Socket 0: no product info available Socket 1: no product info available /sbin/cardctl status Socket 0: 5V 16-bit PC Card function 0: [busy], [bat dead], [bat low] Socket 1: no card cat /proc/pci PCI devices found: Bus 0, device 0, function 0: Host bridge: Intel Corporation 440BX/ZX - 82443BX/ZX Host bridge (rev 3). Master Capable. Latency=64. Prefetchable 32 bit memory at 0xe800 [0xebff]. Bus 0, device 1, function 0: PCI bridge: Intel Corporation 440BX/ZX - 82443BX/ZX AGP bridge (rev 3). Master Capable. Latency=128. Min Gnt=140. Bus 0, device 3, function 0: ISA bridge: Intel Corporation 82371AB PIIX4 ISA (rev 2). Bus 0, device 3, function 1: IDE interface: Intel Corporation 82371AB PIIX4 IDE (rev 1). Master Capable. Latency=64. I/O at 0xfc60 [0xfc6f]. Bus 0, device 3, function 2: USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 1). IRQ 11. Master Capable. Latency=64. I/O at 0xfca0 [0xfcbf]. Bus 0, device 3, function 3: Bridge: Intel Corporation 82371AB PIIX4 ACPI (rev 2). Bus 0, device 6, function 0: Multimedia audio controller: PCI device 1102:8938 (Creative Labs) (rev 0). IRQ
PCMCIA CARDBUS detection incorrect.
using the following: kernel-2.4.2 (linus release - no patches added) kernel-2.2.17-4 (RedHat 7 release - no patches added) kgcc-2.96.66 (kernel config - see compressed text file) I have a Xircom Realport2 10/100 Card that uses the tulip_cb driver. In kernel-2.2.17-4 (from RedHat with pcmcia installed) the card is detected as: /sbin/cardctl ident Socket 0: product info: "Xircom", "RealPort2 CardBus Ethernet 10/100", "R2BE-100BTX", "1.00" manfid: 0x0105, 0x0103 function: 6 (network) Socket 1: no product info available /sbin/cardctl status Socket 0: 3.3V CardBus card function 0: [ready] Socket 1: no card cat /proc/pci PCI devices found: Bus 32, device 0, function 0: Ethernet controller: Unknown vendor Unknown device (rev 3). Vendor id=115d. Device id=3. Medium devsel. IRQ 3. I/O at 0x100 [0x101]. Non-prefetchable 32 bit memory at 0x6000d000 [0x6000d000]. Non-prefetchable 32 bit memory at 0x6000c000 [0x6000c000]. Bus 0, device 0, function 0: Host bridge: Intel 440BX - 82443BX Host (rev 3). Medium devsel. Master Capable. Latency=64. Prefetchable 32 bit memory at 0xe800 [0xe808]. Bus 0, device 1, function 0: PCI bridge: Intel 440BX - 82443BX AGP (rev 3). Medium devsel. Master Capable. Latency=128. Min Gnt=140. Bus 0, device 3, function 0: ISA bridge: Intel 82371AB PIIX4 ISA (rev 2). Medium devsel. Fast back-to-back capable. Master Capable. No bursts. Bus 0, device 3, function 1: IDE interface: Intel 82371AB PIIX4 IDE (rev 1). Medium devsel. Fast back-to-back capable. Master Capable. Latency=64. I/O at 0xfc60 [0xfc61]. Bus 0, device 3, function 2: USB Controller: Intel 82371AB PIIX4 USB (rev 1). Medium devsel. Fast back-to-back capable. IRQ 11. Master Capable. No bursts. I/O at 0xfca0 [0xfca1]. Bus 0, device 3, function 3: Bridge: Intel 82371AB PIIX4 ACPI (rev 2). Medium devsel. Fast back-to-back capable. Bus 0, device 6, function 0: Multimedia audio controller: Unknown vendor Unknown device (rev 0). Vendor id=1102. Device id=8938. Slow devsel. IRQ 5. Master Capable. Latency=96. Min Gnt=12.Max Lat=128. I/O at 0xfcc0 [0xfcc1]. I/O at 0xfc40 [0xfc41]. Bus 0, device 7, function 0: Communication controller: Unknown vendor Unknown device (rev 1). Vendor id=134d. Device id=7890. Medium devsel. IRQ 11. I/O at 0xfc00 [0xfc01]. Bus 0, device 10, function 0: CardBus bridge: Texas Instruments Unknown device (rev 1). Vendor id=104c. Device id=ac1c. Medium devsel. Master Capable. Latency=168. Min Gnt=128.Max Lat=7. Bus 0, device 10, function 1: CardBus bridge: Texas Instruments Unknown device (rev 1). Vendor id=104c. Device id=ac1c. Medium devsel. Master Capable. Latency=168. Min Gnt=192.Max Lat=7. Bus 1, device 0, function 0: VGA compatible controller: Trident Unknown device (rev 73). Vendor id=1023. Device id=9525. Medium devsel. Fast back-to-back capable. IRQ 11. Master Capable. Latency=64. Non-prefetchable 32 bit memory at 0xfe40 [0xfe40]. Non-prefetchable 32 bit memory at 0xfedc [0xfedc]. Non-prefetchable 32 bit memory at 0xfe80 [0xfe80]. The problem is that when I run kernel-2.4.2 the pcmcia does start when compiled as modules (just so that it keeps the RH7 scripts happy). Yet the cardctl reports: /sbin/cardctl ident Socket 0: no product info available Socket 1: no product info available /sbin/cardctl status Socket 0: 5V 16-bit PC Card function 0: [busy], [bat dead], [bat low] Socket 1: no card cat /proc/pci PCI devices found: Bus 0, device 0, function 0: Host bridge: Intel Corporation 440BX/ZX - 82443BX/ZX Host bridge (rev 3). Master Capable. Latency=64. Prefetchable 32 bit memory at 0xe800 [0xebff]. Bus 0, device 1, function 0: PCI bridge: Intel Corporation 440BX/ZX - 82443BX/ZX AGP bridge (rev 3). Master Capable. Latency=128. Min Gnt=140. Bus 0, device 3, function 0: ISA bridge: Intel Corporation 82371AB PIIX4 ISA (rev 2). Bus 0, device 3, function 1: IDE interface: Intel Corporation 82371AB PIIX4 IDE (rev 1). Master Capable. Latency=64. I/O at 0xfc60 [0xfc6f]. Bus 0, device 3, function 2: USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 1). IRQ 11. Master Capable. Latency=64. I/O at 0xfca0 [0xfcbf]. Bus 0, device 3, function 3: Bridge: Intel Corporation 82371AB PIIX4 ACPI (rev 2). Bus 0, device 6, function 0: Multimedia audio controller: PCI device 1102:8938 (Creative Labs) (rev 0). IRQ
Re: Linux booting from HD on Promise Ultra ATA 100
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, 12 Jan 2001, Martin Josefsson wrote: > My setup looks like this, I boot from hde > I configured my BIOS to boot from SCSI (I have no scsi-adapter but the > promise card reports itself as one at boottime) > > boot = /dev/hde3 > delay = 50 > message = /boot/message > vga = extended > read-only > lba32 > disk=/dev/hde > bios=0x80 The line "lba32" is for what? I have to ask this because I have never seen it in an example of a lilo.conf file before. Also you put "disk=/dev/hde and bios=0x80" to inform lilo that there was a disk there and its bios address is 0x80. Is this right? If I would follow your example then I would put: lba32 disk=/dev/hdf bios=0x82 Stephen - -- Buyer's Guide for a Operating System: Don't care to know: Mac Don't mind knowing but not too much: Windows Hit me! I can take it!: Linux -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.1 (GNU/Linux) Comment: For info see http://www.gnupg.org Filter: gpg4pine 4.0 (http://azzie.robotics.net) iD8DBQE6XyltI7ZT+dSlizsRAiM/AJ9SdDSNbYk1Pep2+guGakfYcYUYjQCgzLWR BcrGeMP0DKwgZWo3m0KdEho= =gGWn -END PGP SIGNATURE- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Linux booting from HD on Promise Ultra ATA 100
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm having difficulty booting from the Promise controller. Here is the story: I originally had my system setup with all drives working off the mainsboard IDE controller (Intel 82371AB PIIX4). The setup was /dev/hda - ST310232A, FwRev=3.09 (Seagate) /dev/hdb - 927308, FwRev=RA530JNO (Maxtor) * Linux installed here /dev/hdc - CD-532E-B (Teach CDROM) /dev/hdd - CD-RW4224A (Smart & Friendly CDRW). Well I got an Promise Ultra ATA 100 controller card. Went over to linux-ide.org and get the patches for kernel-2.2.16. Took a pristine kernel-2.2.16 and patched it and then compiled it on a RedHat 6.2 system. I then made a bootdisk with this new kernel. So then I installed the drives in this order: (Mainsboard controller) primary master - ST310232A (Seagate) primary slave - none secondary master - CDROM secondary slave - CDRW (Promise controller) primary slave - IBM-DLTA-307045 (IBM) primary slave - 927308 (Maxtor) * Linux install here secondary master - none secondary slave - none The system boots if I use the bootdisk and tell it "linux root=/dev/hdf3". I edited the lilo.conf and the fstab for the new setup. I can log in and do my business with my the linux partition but when I tried to use lilo to setup the MBR on the first disk (mainsboard) I got this: warning: BIOS Drive 0x82 may not be accessible. Is there some settings that I need to give to the lilo to boot? Stephen - -- Buyer's Guide for a Operating System: Don't care to know: Mac Don't mind knowing but not too much: Windows Hit me! I can take it!: Linux -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.1 (GNU/Linux) Comment: For info see http://www.gnupg.org Filter: gpg4pine 4.0 (http://azzie.robotics.net) iD8DBQE6XyOTI7ZT+dSlizsRAu3BAKCdtwlgiJ9+isy9NOlltIs+logHMgCfViiy ofYOmWxhH6Qt8FDeoJNZvsg= =+RwL -END PGP SIGNATURE- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Linux booting from HD on Promise Ultra ATA 100
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm having difficulty booting from the Promise controller. Here is the story: I originally had my system setup with all drives working off the mainsboard IDE controller (Intel 82371AB PIIX4). The setup was /dev/hda - ST310232A, FwRev=3.09 (Seagate) /dev/hdb - 927308, FwRev=RA530JNO (Maxtor) * Linux installed here /dev/hdc - CD-532E-B (Teach CDROM) /dev/hdd - CD-RW4224A (Smart Friendly CDRW). Well I got an Promise Ultra ATA 100 controller card. Went over to linux-ide.org and get the patches for kernel-2.2.16. Took a pristine kernel-2.2.16 and patched it and then compiled it on a RedHat 6.2 system. I then made a bootdisk with this new kernel. So then I installed the drives in this order: (Mainsboard controller) primary master - ST310232A (Seagate) primary slave - none secondary master - CDROM secondary slave - CDRW (Promise controller) primary slave - IBM-DLTA-307045 (IBM) primary slave - 927308 (Maxtor) * Linux install here secondary master - none secondary slave - none The system boots if I use the bootdisk and tell it "linux root=/dev/hdf3". I edited the lilo.conf and the fstab for the new setup. I can log in and do my business with my the linux partition but when I tried to use lilo to setup the MBR on the first disk (mainsboard) I got this: warning: BIOS Drive 0x82 may not be accessible. Is there some settings that I need to give to the lilo to boot? Stephen - -- Buyer's Guide for a Operating System: Don't care to know: Mac Don't mind knowing but not too much: Windows Hit me! I can take it!: Linux -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.1 (GNU/Linux) Comment: For info see http://www.gnupg.org Filter: gpg4pine 4.0 (http://azzie.robotics.net) iD8DBQE6XyOTI7ZT+dSlizsRAu3BAKCdtwlgiJ9+isy9NOlltIs+logHMgCfViiy ofYOmWxhH6Qt8FDeoJNZvsg= =+RwL -END PGP SIGNATURE- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Linux booting from HD on Promise Ultra ATA 100
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, 12 Jan 2001, Martin Josefsson wrote: My setup looks like this, I boot from hde I configured my BIOS to boot from SCSI (I have no scsi-adapter but the promise card reports itself as one at boottime) boot = /dev/hde3 delay = 50 message = /boot/message vga = extended read-only lba32 disk=/dev/hde bios=0x80 The line "lba32" is for what? I have to ask this because I have never seen it in an example of a lilo.conf file before. Also you put "disk=/dev/hde and bios=0x80" to inform lilo that there was a disk there and its bios address is 0x80. Is this right? If I would follow your example then I would put: lba32 disk=/dev/hdf bios=0x82 Stephen - -- Buyer's Guide for a Operating System: Don't care to know: Mac Don't mind knowing but not too much: Windows Hit me! I can take it!: Linux -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.1 (GNU/Linux) Comment: For info see http://www.gnupg.org Filter: gpg4pine 4.0 (http://azzie.robotics.net) iD8DBQE6XyltI7ZT+dSlizsRAiM/AJ9SdDSNbYk1Pep2+guGakfYcYUYjQCgzLWR BcrGeMP0DKwgZWo3m0KdEho= =gGWn -END PGP SIGNATURE- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Transmission errors for Xircom RealPort2 10/100 Cardbus NIC.
I am having a real interesting time with the Xircom card and kernel-2.2.16. All transmission packets from the NIC are being flagged for errors while all received packets are fine. The card is in a Twinhead P88TE Cardbus PCMCIA slot. Eradicate errors like total packet loss, 1 packet out of 4 returning fine with ping, and others are causing me to be concerned. The module I am using is tulip_cb. I got these details from ifconfig. eth0 Link encap:Ethernet HWaddr 00:10:A4:B9:6C:D2 inet addr:10.0.0.4 Bcast:10.0.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:965 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:983 dropped:0 overruns:0 carrier:983 collisions:0 txqueuelen:100 Interrupt:3 Base address:0x100 I checked the file /proc/net/dev Inter-| Receive| Transmit face |bytespackets errs drop fifo frame compressed multicast|bytespackets errs drop fifo colls carrier compressed lo: 6138712002000 0 0 0 6138712002 000 0 0 0 eth0: 5975441017000 0 0 00 0 103800 01038 0 That reports no errors. Just to let you know what modules are loaded: Module Size Used by tulip_cb 30856 2 cb_enabler 2472 2 [tulip_cb] ds 6600 2 [cb_enabler] i82365 29764 2 pcmcia_core44192 0 [cb_enabler ds i82365] nls_cp437 3876 3 (autoclean) vfat9276 1 (autoclean) fat30400 1 (autoclean) [vfat] es1371 27264 0 soundcore 2628 4 [es1371] Stephen -- Buyer's Guide for a Operating System: Don't care to know: Mac Don't mind knowing but not too much: Windows Hit me! I can take it!: Linux - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Transmission errors for Xircom RealPort2 10/100 Cardbus NIC.
I am having a real interesting time with the Xircom card and kernel-2.2.16. All transmission packets from the NIC are being flagged for errors while all received packets are fine. The card is in a Twinhead P88TE Cardbus PCMCIA slot. Eradicate errors like total packet loss, 1 packet out of 4 returning fine with ping, and others are causing me to be concerned. The module I am using is tulip_cb. I got these details from ifconfig. eth0 Link encap:Ethernet HWaddr 00:10:A4:B9:6C:D2 inet addr:10.0.0.4 Bcast:10.0.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:965 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:983 dropped:0 overruns:0 carrier:983 collisions:0 txqueuelen:100 Interrupt:3 Base address:0x100 I checked the file /proc/net/dev Inter-| Receive| Transmit face |bytespackets errs drop fifo frame compressed multicast|bytespackets errs drop fifo colls carrier compressed lo: 6138712002000 0 0 0 6138712002 000 0 0 0 eth0: 5975441017000 0 0 00 0 103800 01038 0 That reports no errors. Just to let you know what modules are loaded: Module Size Used by tulip_cb 30856 2 cb_enabler 2472 2 [tulip_cb] ds 6600 2 [cb_enabler] i82365 29764 2 pcmcia_core44192 0 [cb_enabler ds i82365] nls_cp437 3876 3 (autoclean) vfat9276 1 (autoclean) fat30400 1 (autoclean) [vfat] es1371 27264 0 soundcore 2628 4 [es1371] Stephen -- Buyer's Guide for a Operating System: Don't care to know: Mac Don't mind knowing but not too much: Windows Hit me! I can take it!: Linux - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Dell 5000e APM (fixed!)
On the topic of APM, I have a supermicro P6DBE motherboard (SMP). APM does not work because its not safe with SMP systems. What can I do to get power management for this motherboard? Stephen On Tue, 28 Nov 2000, Alan Cox wrote: > > The BIOS listed is a new test BIOS that has a *corrected* APM that I > > received this morning. I really want to take a second to thank the > > Good they've changed the BIOS id. > > Thansk > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > Please read the FAQ at http://www.tux.org/lkml/ > -- Buyer's Guide for a Operating System: Don't care to know: Mac Don't mind knowing but not too much: Windows Hit me! I can take it!: Linux - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Dell 5000e APM (fixed!)
On the topic of APM, I have a supermicro P6DBE motherboard (SMP). APM does not work because its not safe with SMP systems. What can I do to get power management for this motherboard? Stephen On Tue, 28 Nov 2000, Alan Cox wrote: The BIOS listed is a new test BIOS that has a *corrected* APM that I received this morning. I really want to take a second to thank the Good they've changed the BIOS id. Thansk - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/ -- Buyer's Guide for a Operating System: Don't care to know: Mac Don't mind knowing but not too much: Windows Hit me! I can take it!: Linux - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
hdparm settings: Can they be permanent?
It was suggested to me that the way to make hdparm settings permanent was to create a script to change the settings on startup. Is this the best choice? Stephen [EMAIL PROTECTED] -- Questions are only stupid if they are never asked. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
hdparm settings: Can they be permanent?
It was suggested to me that the way to make hdparm settings permanent was to create a script to change the settings on startup. Is this the best choice? Stephen [EMAIL PROTECTED] -- Questions are only stupid if they are never asked. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
warning message posted from apic.h
I get the following message compiling 2.4.0-test6 or test8 on a RedHat 7 system. "/usr/src/linux/include/asm/apic.h:13:29: warning: nothing can be posted after this token". Is this an issue with apic? Stephen -- [EMAIL PROTECTED] -- 5 systems (98% Linux, 2% MS). - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
warning message posted from apic.h
I get the following message compiling 2.4.0-test6 or test8 on a RedHat 7 system. "/usr/src/linux/include/asm/apic.h:13:29: warning: nothing can be posted after this token". Is this an issue with apic? Stephen -- [EMAIL PROTECTED] -- 5 systems (98% Linux, 2% MS). - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
