mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Sumit Pandya <sumit@elitecore.com>
Cc: Zwane Mwaikambo <zwane@linuxpower.ca>,
	linux-kernel@vger.kernel.org, len.brown@intel.com
Subject: Re: OOPS - APIC or othere?
Date: Fri, 26 Nov 2004 04:42:01 -0200	[thread overview]
Message-ID: <20041126064200.GB4912@logos.cnet> (raw)
In-Reply-To: <HGEFKOBCHAIJDIEJLAKDAEMKCAAA.sumit@elitecore.com>

On Fri, Nov 26, 2004 at 02:23:57PM +0530, Sumit Pandya wrote:
> Marcelo,
> 	No other message except my name "Sumit" ? 

Yes, because Zwane has written the message

"Sending bug report for partially patched kernel isn't easy for us to 
debug, is there no way for you to simply try booting 2.4.27?"

And I was assuming you read that. Did you?

The bugzilla entry makes it understand that Len has fixed the 
problem in 2.4.27:

------- Additional Comment #2 From Len Brown  2004-11-04 13:32 -------

shipped in 2.4.27 - closing


> Any update in my problem
> statement?	My problem is having an embaded LinuxOS and changing kernel
> version is very critical.

Zwane's statement is valid here.

> Expecting just a quick answer from anyone. Could
> following solution patch break any other functionality if applied on the top
> of 2.4.26?
> http://bugzilla.kernel.org/show_bug.cgi?id=2834
> 	I got attachemnt from the above link and applied patch. Above patch applies
> nicely and runs without any problem. But wanted just a final confirmation
> from authers.

Seems to be doing its job then isnt it?

> Thanks for your time,
> -- Sumit
> 
> > -----Original Message-----
> > From: Marcelo Tosatti [mailto:marcelo.tosatti@cyclades.com]
> > Sent: Thursday, November 25, 2004 5:46 PM
> >
> >
> > On Wed, Nov 17, 2004 at 09:42:58AM -0700, Zwane Mwaikambo wrote:
> > > On Wed, 17 Nov 2004, Sumit Pandya wrote:
> > >
> > > > 	At one of our client I faced timer problem in kernel-2.4.26
> > and I tried to
> > > > fixed with patching "arch/i386/kernel/mpparse.c" file taken from
> > > > patch-2.4.27.
> > > > ...	...	...
> > > > Mikael Pettersson:
> > > >   o i386 and x86_64 ACPI mpparse timer bug
> > > > ...	...	...
> > > > 	After booting up the system now I get OOPS. Did I applied
> > partial patch by
> > > > taking only patch for mpparse.c from the whole buntch? Does it broken
> > > > dependency to some other functionality? I've ACPI support enabled into
> > > > kernel.
> > > > 	Does following Len's patch provide solution to my OOPS?
> > > >
> > ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/patches/test/2.4.
> 26-rc4/200
> > > 40422153228-irq2.patch
> > >
> > > Here is output of ksymsoops.
> >
> > Sending bug reports for partially patched kernels isn't easy for us to
> > debug, is there no way for you to simply try booting 2.4.27?
> 
> Sumit?

  parent reply	other threads:[~2004-11-27  5:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-17 10:06 Sumit Pandya
2004-11-17 10:49 ` Mikael Pettersson
2004-11-17 16:42 ` Zwane Mwaikambo
     [not found]   ` <HGEFKOBCHAIJDIEJLAKDAEMKCAAA.sumit@elitecore.com>
2004-11-26  6:42     ` Marcelo Tosatti [this message]
2004-11-26 13:35       ` Zwane Mwaikambo

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=20041126064200.GB4912@logos.cnet \
    --to=marcelo.tosatti@cyclades.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sumit@elitecore.com \
    --cc=zwane@linuxpower.ca \
    /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®