From: Giuseppe Sacco <giuseppe@eppesuigoccas.homedns.org>
To: linux-scsi@vger.kernel.org
Subject: Re: new kernel oops in recent kernels
Date: Mon, 17 Mar 2008 09:17:51 +0100 [thread overview]
Message-ID: <1205741871.3515.9.camel@localhost> (raw)
In-Reply-To: <20080317044142.GC26285@parisc-linux.org>
Hi all,
I wrote a message to linux-mips mailing list for investigating on the
assembly code generated in sr_cdrom_status() since adding the suggested
printk() stopped the oops. I supposed there is a problem with the
compiler, but people there are investigating about problem with cache
coherency.
You may follow the thread on public web archive, at
http://www.linux-mips.org/archives/linux-mips/2008-03/msg00079.html
I'll be back on this list after checking any problem with cache
coherence and c compiler.
Thanks,
Giuseppe
next prev parent reply other threads:[~2008-03-17 8:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-16 15:19 new kernel oops in recent kernels Giuseppe Sacco
2008-03-16 16:39 ` James Bottomley
2008-03-16 18:32 ` Giuseppe Sacco
2008-03-16 18:47 ` James Bottomley
2008-03-16 16:42 ` Matthew Wilcox
2008-03-16 18:29 ` Giuseppe Sacco
2008-03-17 3:58 ` Matthew Wilcox
2008-03-17 4:41 ` Matthew Wilcox
2008-03-17 8:17 ` Giuseppe Sacco [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-03-16 10:49 Giuseppe Sacco
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=1205741871.3515.9.camel@localhost \
--to=giuseppe@eppesuigoccas.homedns.org \
--cc=linux-scsi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.