RE: Problem with kernel 2.2.19 Ultra-DMA and SMP, once more
:: If this is a VIA SMP system there are APIC problems that you :: do not want :: to even think about addressing. :: :: MPS1.1 and passing "noapic" will fix most of there mess, but :: you have a :: semi-crippled system, but it runs. Andre, I don't suppose these APIC problems are documented anywhere...? -- Juha, who's wrestling with a VIA 694X dualie mobo here. - 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: [patch] ioapic-2.4.5-A1
The attachment didn't survive... please try again. -- Juha :: -Original Message- :: From: [EMAIL PROTECTED] :: [mailto:[EMAIL PROTECTED]] On Behalf Of Ingo Molnar :: Sent: Tuesday, 29 May 2001 23:11 :: To: [EMAIL PROTECTED] :: Cc: [EMAIL PROTECTED]; Alan Cox :: Subject: [patch] ioapic-2.4.5-A1 :: :: :: :: the attached ioapic-2.4.5-A1 patch includes a number of :: important IO-APIC :: related fixes (against 2.4.5-ac3): :: :: - correctly handle bridged devices that are not listed in :: the mptable ::directly. This fixes eg. dual-port eepro100 devices on :: Compaq boxes ::with such PCI layout: :: :: -+-[0d]---0b.0 :: +-[05]-+-02.0 :: | \-0b.0 :: \-[00]-+-02.0 :: +-03.0-[01]--+-04.0<=== eth0 :: |\-05.0<=== eth1 :: +-0b.0 :: +-0c.0 :: +-0d.0 :: +-0e.0 :: +-0f.0 :: +-14.0 :: +-14.1 :: +-19.0 :: +-1a.0 :: \-1b.0 :: ::without the patch the eepro100 devices get misdetected as :: XT-PIC IRQs ::and their interrupts are stuck. :: :: - the srcbus entry in the mptable does not have to be :: translated into ::a PCI-bus value. :: :: - add more APIC versions to the whitelist :: :: - initialize mp_bus_id_to_pci_bus[] correctly, so that we can detect ::nonlisted/bridged PCI busses more accurately. :: :: the patch should only affect systems that were not working properly :: before, but it might break broken-mptable systems - we'll see. :: :: Ingo :: - 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: [patch] ioapic-2.4.5-A1
The attachment didn't survive... please try again. -- Juha :: -Original Message- :: From: [EMAIL PROTECTED] :: [mailto:[EMAIL PROTECTED]] On Behalf Of Ingo Molnar :: Sent: Tuesday, 29 May 2001 23:11 :: To: [EMAIL PROTECTED] :: Cc: [EMAIL PROTECTED]; Alan Cox :: Subject: [patch] ioapic-2.4.5-A1 :: :: :: :: the attached ioapic-2.4.5-A1 patch includes a number of :: important IO-APIC :: related fixes (against 2.4.5-ac3): :: :: - correctly handle bridged devices that are not listed in :: the mptable ::directly. This fixes eg. dual-port eepro100 devices on :: Compaq boxes ::with such PCI layout: :: :: -+-[0d]---0b.0 :: +-[05]-+-02.0 :: | \-0b.0 :: \-[00]-+-02.0 :: +-03.0-[01]--+-04.0=== eth0 :: |\-05.0=== eth1 :: +-0b.0 :: +-0c.0 :: +-0d.0 :: +-0e.0 :: +-0f.0 :: +-14.0 :: +-14.1 :: +-19.0 :: +-1a.0 :: \-1b.0 :: ::without the patch the eepro100 devices get misdetected as :: XT-PIC IRQs ::and their interrupts are stuck. :: :: - the srcbus entry in the mptable does not have to be :: translated into ::a PCI-bus value. :: :: - add more APIC versions to the whitelist :: :: - initialize mp_bus_id_to_pci_bus[] correctly, so that we can detect ::nonlisted/bridged PCI busses more accurately. :: :: the patch should only affect systems that were not working properly :: before, but it might break broken-mptable systems - we'll see. :: :: Ingo :: - 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: Can't boot with the 2.4.3 kernel.
:: I configured and build it, and all looked OK. Did you select the right CPU type in the configuration? -- Juha - 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: Can't boot with the 2.4.3 kernel.
:: I configured and build it, and all looked OK. Did you select the right CPU type in the configuration? -- Juha - 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: ASSISTANCE
This is a variant on the Nigerian Scam... avoid at all cost. :: -Original Message- :: From: [EMAIL PROTECTED] :: [mailto:[EMAIL PROTECTED]]On Behalf Of mani elisabeth :: Sent: Monday, March 26, 2001 10:24 PM :: To: [EMAIL PROTECTED] :: Subject: ASSISTANCE :: :: :: FROM : MRS ELIZABETH NKEIRU-MANI - 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: ASSISTANCE
This is a variant on the Nigerian Scam... avoid at all cost. :: -Original Message- :: From: [EMAIL PROTECTED] :: [mailto:[EMAIL PROTECTED]]On Behalf Of mani elisabeth :: Sent: Monday, March 26, 2001 10:24 PM :: To: [EMAIL PROTECTED] :: Subject: ASSISTANCE :: :: :: FROM : MRS ELIZABETH NKEIRU-MANI drivelectomy - 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-pre7 and System.map, bzImage ??
:: I've compiled 2.4.3-pre7 and no errors were reported, yet I can't find :: the kernel bzImage or System.map file. Did I miss a major change in the :: install procedure since 2.4.1? :: :: I can't find any references in the docs or archives. Do: make bzlilo and look in your / directory. -- Juha - 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-pre7 and System.map, bzImage ??
:: I've compiled 2.4.3-pre7 and no errors were reported, yet I can't find :: the kernel bzImage or System.map file. Did I miss a major change in the :: install procedure since 2.4.1? :: :: I can't find any references in the docs or archives. Do: make bzlilo and look in your / directory. -- Juha - 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: [PATCH] Prevent OOM from killing init
:: Your ideas sound really good, would you have the time to implement :: them for 2.4 ? 2.4 or 2.5? -- Juha - 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: [PATCH] Prevent OOM from killing init
:: Your ideas sound really good, would you have the time to implement :: them for 2.4 ? 2.4 or 2.5? -- Juha - 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: Question about memory usage in 2.4 vs 2.2
:: > And can this behavior be tuned so that it uses less of the overall :: > memory? :: :: This isn't currently possible. Also, I suspect what we really want :: for most situations is a way to better balance between the different :: uses of memory. Again, patches are welcome (I haven't figured out a :: way to take care of this balancing yet ... maybe we DO want some way :: of limiting memory usage of each subsystem??). man ulimit? ;-) On a more serious note, is there a way to find out what has been paged out to disk, and also limit what can be paged out? I could be wrong, but for instance I leave X running for a while (not sure about the timing here but let's say several hours), and come back and log in again, it is very slow to "come alive". The screen redraws slowly, and there's quite a bit of disk access. This only happens if the system is left alone for a long period of time (no, I don't have APM running on it). Squid behaves the same -- the first access after a long period of inactivity causes a lot of disk grinding, but successive accesses are fine. Don't see this behaviour with the 2.2.x kernels. -- Juha - 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: Question about memory usage in 2.4 vs 2.2
:: And can this behavior be tuned so that it uses less of the overall :: memory? :: :: This isn't currently possible. Also, I suspect what we really want :: for most situations is a way to better balance between the different :: uses of memory. Again, patches are welcome (I haven't figured out a :: way to take care of this balancing yet ... maybe we DO want some way :: of limiting memory usage of each subsystem??). man ulimit? ;-) On a more serious note, is there a way to find out what has been paged out to disk, and also limit what can be paged out? I could be wrong, but for instance I leave X running for a while (not sure about the timing here but let's say several hours), and come back and log in again, it is very slow to "come alive". The screen redraws slowly, and there's quite a bit of disk access. This only happens if the system is left alone for a long period of time (no, I don't have APM running on it). Squid behaves the same -- the first access after a long period of inactivity causes a lot of disk grinding, but successive accesses are fine. Don't see this behaviour with the 2.2.x kernels. -- Juha - 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: APIC usb MPS 1.4 and the 2.4.2 kernel
:: AFAIK, the option to compile w/o APIC is only for UP systems. If you :: want to use both of your processors, you have to compile in APIC :: support, but just disable it when loading the kernel (ie. for lilo, :: 'append="noapic"') I haven't seen the beginning of the APIC/VIA/Tyan thread, but isn't there a way to check if the APIC's OK, instead of resorting to workarounds like the above? :: That would explain why it works for me. Now, if only I didn't have :: devices that need to have their BIOSes upgraded via a Windows .exe... ;-). That's a good point, actually. I can't recall a single BIOS or device BIOS flasher that works under anything but DOS (or in some cases, Windows). Is there any work being done on this for Linux? -- Juha - 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: APIC usb MPS 1.4 and the 2.4.2 kernel
Greg, :: It seems that the APIC on this motherboard does not have most of the :: pins connected, so that even if we could get the USB interrupt to work :: properly (which we couldn't) there would be no benefit to run in APIC :: mode. I was going to run some crude benchmarks on the box with and :: without APIC mode just to get an sense if we are missing anything :: running in noapic mode, but I haven't gotten around to it yet. So for Tyan Tigers, is it better to compile the kernel without APIC? About to install Linux on a dual 500 P3 here. :: But, Linux does seem to run just fine with USB and SMP in the noapic :: mode, which is a lot better than Win2000 can say, as it doesn't even :: support the VIA USB chipset on this board at all :) There's a Win2K patch for VIA chip sets now... I've got USB working under Win2K here. -- Juha - 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: APIC usb MPS 1.4 and the 2.4.2 kernel
Greg, :: It seems that the APIC on this motherboard does not have most of the :: pins connected, so that even if we could get the USB interrupt to work :: properly (which we couldn't) there would be no benefit to run in APIC :: mode. I was going to run some crude benchmarks on the box with and :: without APIC mode just to get an sense if we are missing anything :: running in noapic mode, but I haven't gotten around to it yet. So for Tyan Tigers, is it better to compile the kernel without APIC? About to install Linux on a dual 500 P3 here. :: But, Linux does seem to run just fine with USB and SMP in the noapic :: mode, which is a lot better than Win2000 can say, as it doesn't even :: support the VIA USB chipset on this board at all :) There's a Win2K patch for VIA chip sets now... I've got USB working under Win2K here. -- Juha - 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: APIC usb MPS 1.4 and the 2.4.2 kernel
:: AFAIK, the option to compile w/o APIC is only for UP systems. If you :: want to use both of your processors, you have to compile in APIC :: support, but just disable it when loading the kernel (ie. for lilo, :: 'append="noapic"') I haven't seen the beginning of the APIC/VIA/Tyan thread, but isn't there a way to check if the APIC's OK, instead of resorting to workarounds like the above? :: That would explain why it works for me. Now, if only I didn't have :: devices that need to have their BIOSes upgraded via a Windows .exe... ;-). That's a good point, actually. I can't recall a single BIOS or device BIOS flasher that works under anything but DOS (or in some cases, Windows). Is there any work being done on this for Linux? -- Juha - 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/
