From: Giuseppe Sacco <giuseppe@eppesuigoccas.homedns.org>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: linux-mips@linux-mips.org
Subject: Re: Compiler error? [was: Re: new kernel oops in recent kernels]
Date: Mon, 17 Mar 2008 09:05:42 +0100 [thread overview]
Message-ID: <1205741142.3515.2.camel@localhost> (raw)
In-Reply-To: <20080316233619.GA29511@alpha.franken.de>
Hi Thomas,
Il giorno lun, 17/03/2008 alle 00.36 +0100, Thomas Bogendoerfer ha
scritto:
> On Sun, Mar 16, 2008 at 09:27:37PM +0100, Giuseppe Sacco wrote:
> > the gcc I am using in versione 4.1.2. Any help is really appreciated.
>
> 4.2.1 generates nearly the same (reasonable) code. The major difference
> between the version with printk and the version without is the size
> of the local stack. I guess this prevents killing of *cd.
> Could you try the hack below and tell me, if it helps ? This hack
> ensures, that the buffer given to the scsi driver is one cache
> line big (at least on R5k O2s). If this helps, there are more
> places to fix for non-coherent machines...
[...]
The patch you proposed, that use a larger buffer, does not seems to
trigger the bug.
Thanks,
Giuseppe
next prev parent reply other threads:[~2008-03-17 8:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-16 10:49 new kernel oops in recent kernels Giuseppe Sacco
2008-03-16 20:27 ` Compiler error? [was: Re: new kernel oops in recent kernels] Giuseppe Sacco
2008-03-16 23:36 ` Thomas Bogendoerfer
2008-03-17 8:05 ` Giuseppe Sacco [this message]
2008-03-17 14:18 ` Ralf Baechle
2008-03-17 14:32 ` Thomas Bogendoerfer
2008-03-21 23:00 ` Thomas Bogendoerfer
2008-03-22 23:39 ` Giuseppe Sacco
2008-03-23 11:16 ` Thomas Bogendoerfer
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=1205741142.3515.2.camel@localhost \
--to=giuseppe@eppesuigoccas.homedns.org \
--cc=linux-mips@linux-mips.org \
--cc=tsbogend@alpha.franken.de \
/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