mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "John Stoffel" <stoffel@lucent.com>
To: Eric <eric@cisu.net>
Cc: Andrew Morton <akpm@osdl.org>,
	stoffel@lucent.com, ak@muc.de, Valdis.Kletnieks@vt.edu,
	bunk@fs.tum.de, cova@ferrara.linux.it,
	linux-kernel@vger.kernel.org
Subject: 2.6.2-rc2-mm1 now boots, 2.6.2-rc? doesn't
Date: Thu, 29 Jan 2004 09:44:23 -0500	[thread overview]
Message-ID: <16409.7239.119612.861354@gargle.gargle.HOWL> (raw)


Hi Andrew,

Thank you for your -mm1 patch to 2.6.2-rc2, I've now got my system up
and running again.  I'm not sure where the problem was, since I didn't
find the problem point after sprinkling a bunch of AAA(); debugging
printks() all over the stuff in arch/i386/kernel/setup.c and some
other files in there as well.  

Would it make sense for me to try and work backwards from the -mm1 and
see which patch(es) makes the difference?  

One thing I notice is that now my interrupts are all on just one
processor:

   > cat /proc/interrupts            CPU0       CPU1       
     0:   59000197         20    IO-APIC-edge  timer
     1:       1867          1    IO-APIC-edge  i8042
     2:          0          0          XT-PIC  cascade
     8:          3          1    IO-APIC-edge  rtc
    11:          1          0    IO-APIC-edge  Cyclom-Y
    12:        703          1    IO-APIC-edge  i8042
    14:        281          0    IO-APIC-edge  ide0
    16:      42762          3   IO-APIC-level  ide2, ide3, ohci_hcd
    17:     183325          1   IO-APIC-level  ehci_hcd, eth0
    18:     119211          1   IO-APIC-level  aic7xxx, aic7xxx, Ensoniq AudioPCI
    19:          0          0   IO-APIC-level  ohci_hcd
   NMI:          0          0 
   LOC:   58999640   58999802 
   ERR:          0
   MIS:         26

Should I think about using that daemon to move interrupts around?
Gotta go find the pointer to that stuff again.

Thanks again Andrew!

John

                 reply	other threads:[~2004-01-29 15:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=16409.7239.119612.861354@gargle.gargle.HOWL \
    --to=stoffel@lucent.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=ak@muc.de \
    --cc=akpm@osdl.org \
    --cc=bunk@fs.tum.de \
    --cc=cova@ferrara.linux.it \
    --cc=eric@cisu.net \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®