Symmetric Multiprocessing (SMP) development
 help / color / mirror / Atom feed
From: "Paul Hernandez" <ph@digitalquake.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: linux-smp@vger.kernel.org
Subject: Randy, your patch fixed it!
Date: Fri, 18 Oct 2002 08:32:38 -0700	[thread overview]
Message-ID: <FMEDJKFPPLANNCCEABDMMEKDCBAA.ph@digitalquake.com> (raw)
In-Reply-To: <Pine.LNX.4.33L2.0210171628530.2499-100000@dragon.pdx.osdl.net>


Came in this morning and finished the build to try your
patch and it successfully corrected the

WARNING: unexpected IO-APIC,

issue. It's really great when folks add the "please mail to"
bit after an unexpected error occurs. Kudos to you for
that.

As you suggest I shall follow-up with acpi-devel@lists.sf.net
on the "ACPI-0361: *** Error: GPE0 block overlaps the GPE1 block"
matter.

Any suggestions on who to follow up with on 2.4.19's NIC card
issues? I've tried three different vendors cards with no luck.
All worked fine on 2.4.18 but had to upgrade to fix other issues.
mii-tool won't even work on 2.4.19 claiming

SIOCGMIIPHY on eth0 failed:
Operation not supported.
No MII interfaces found

Thanks again Randy.

				Paul Hernandez  408-374-8686  x202
				Campbell, Ca

-----Original Message-----
From: Randy.Dunlap [mailto:rddunlap@osdl.org]
Sent: Thursday, October 17, 2002 4:31 PM
To: Paul Hernandez
Subject: RE: WARNING: unexpected IO-APIC, please mail


On Thu, 17 Oct 2002, Paul Hernandez wrote:

|
| It's compiling. By the way, later in the same dmesg output was:
|
| ACPI: Subsystem revision 20020829
| PCI: PCI BIOS revision 2.10 entry at 0xfd921, last bus=4
| PCI: Using configuration type 1
|       ACPI-0361: *** Error: GPE0 block overlaps the GPE1 block
| ACPI: Unable to start the ACPI Interpreter
|
|
| Does your patch resolve this as well?

Nope, it does not.  I don't know anything about that one.
If you want to follow-up on that problem, please send an
email about it to acpi-devel@lists.sf.net .

~Randy

| 			Paul
|
| -----Original Message-----
| From: Randy.Dunlap [mailto:rddunlap@osdl.org]
| Sent: Thursday, October 17, 2002 3:58 PM
| To: Paul Hernandez
| Subject: RE: WARNING: unexpected IO-APIC, please mail
|
|
| On Thu, 17 Oct 2002, Paul Hernandez wrote:
|
| |
| | I believe so Randy thanks. Yes I meant rpms!
| | Is your patch intended to work with the versions
| | of the files found in 2.4.19.SuSE?
|
| It should work with them unless they changed the source code a lot.
| If it doesn't apply cleanly, just send me the error messages and
| your original /usr/src/linux/include/asm-i386/io_apic.h file
| and I can make it work.
|
| Thanks,
| ~Randy
|
| | -----Original Message-----
| | From: Randy.Dunlap [mailto:rddunlap@osdl.org]
| | Sent: Thursday, October 17, 2002 3:39 PM
| | To: Paul Hernandez
| | Subject: RE: WARNING: unexpected IO-APIC, please mail
| |
| |
| | Hi Paul--
| |
| | On Thu, 17 Oct 2002, Paul Hernandez wrote:
| |
| | | Randy,
| | |
| | | Haven't tried your patch yet but now I'm running 2.4.19.SuSE (SuSE
8.1)
| | and
| | | the same WARNING message is printed. This version now correctly
| | | recognizes the ide controller and runs drives on DMA but this version
| | | has broken my eepro100 (won't ping gateway like it did in 8.0) and the
| | | Promise FastTrack 100 prints "lost interrups" indefinately ... sigh.
| | |
| | | I'd like to try you patch below. I'm comfortable building kernels
| however
| | | I've only used xpm's and not patch. If your willing to give me a few
| | | steps on how to use your patch I'll try it and let you know.
| |
| | xpm's? or rpm's?
| | I don't even know what xpm's are.
| |
| | | I'm assuming you copy the files below into a file say randy.patch,
| | | cd to /usr/src/linux anf type
| | |
| | | patch [some option here] < randy.patch
| |
| | Sure, here's what I would do:
| |
| |   patch -p0 -bs --dry-run < randy.patch
| | to make sure that it doesn't complain about patch file errors
| |
| | and then
| |   patch -p0 -b < randy.patch
| | to really apply the patch.
| | Using -b makes backup files of the patched files.
| |
| | Then 'make bzImage' will rebuild the kernel.
| | Can you take it from there?
| |
| | Thanks,
| | ~Randy


           reply	other threads:[~2002-10-18 15:32 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <Pine.LNX.4.33L2.0210171628530.2499-100000@dragon.pdx.osdl.net>]

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=FMEDJKFPPLANNCCEABDMMEKDCBAA.ph@digitalquake.com \
    --to=ph@digitalquake.com \
    --cc=linux-smp@vger.kernel.org \
    --cc=rddunlap@osdl.org \
    /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