From: Pierre Ossman <drzeus-list@drzeus.cx>
To: randy_dunlap <rdunlap@xenotime.net>
Cc: g.liakhovetski@gmx.de, oliver@neukum.name, linux-scsi@vger.kernel.org
Subject: Re: Fw: Kernel panic with dc395x in 2.6.12.2
Date: Fri, 29 Jul 2005 01:05:48 +0200 [thread overview]
Message-ID: <42E964CC.5060600@drzeus.cx> (raw)
In-Reply-To: <20050726202058.133382c1.rdunlap@xenotime.net>
randy_dunlap wrote:
>
>oh drat. Please test 2.6.12.2 with the following patch segment
>backed out (-R, reversed). I don't see any other patches that could
>be the cause. If this isn't the problem, I would have to begin
>to suspect some kind of toolchain problem.
>
>
>
It seems the blame falls solely on my shoulders. I hadn't undone one of
the patches I had previously applied when searching for the HIGHMEM bug. :(
So there is no problem with the driver without HIGHMEM enabled, 2.6.12.2
or otherwise.
I'll get on figuring out with -rc caused the HIGHMEM issue instead..
Sorry
Pierre
next prev parent reply other threads:[~2005-07-28 23:05 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-10 0:57 Fw: Kernel panic with dc395x in 2.6.12.2 randy_dunlap
2005-07-10 1:49 ` Pierre Ossman
2005-07-10 4:08 ` randy_dunlap
2005-07-10 14:01 ` Pierre Ossman
2005-07-10 16:39 ` randy_dunlap
2005-07-10 17:22 ` Pierre Ossman
2005-07-10 17:56 ` randy_dunlap
2005-07-10 19:55 ` Pierre Ossman
2005-07-13 21:16 ` Guennadi Liakhovetski
2005-07-13 23:57 ` Pierre Ossman
2005-07-14 1:57 ` randy_dunlap
2005-07-14 21:30 ` Guennadi Liakhovetski
2005-07-14 22:25 ` Pierre Ossman
2005-07-21 23:51 ` Pierre Ossman
2005-07-22 6:53 ` randy_dunlap
2005-07-22 12:30 ` Pierre Ossman
2005-07-22 12:40 ` Pierre Ossman
[not found] ` <20050722135055.6cb4597d.rdunlap@xenotime.net>
[not found] ` <42E17451.6090706@drzeus.cx>
[not found] ` <20050722153651.28d5db51.rdunlap@xenotime.net>
[not found] ` <42E17772.3020903@drzeus.cx>
[not found] ` <20050723100945.7d43d063.rdunlap@xenotime.net>
[not found] ` <42E2933C.4050808@drzeus.cx>
[not found] ` <20050723152714.4212ba52.rdunlap@xenotime.net>
[not found] ` <42E2ECF1.8070501@drzeus.cx>
[not found] ` <20050723184014.49629f9e.rdunlap@xenotime.net>
[not found] ` <42E39462.3040007@drzeus.cx>
[not found] ` <20050724100153.3e891484.rdunlap@xenotime.net>
2005-07-25 22:21 ` Pierre Ossman
2005-07-26 3:31 ` randy_dunlap
2005-07-26 21:06 ` Pierre Ossman
2005-07-27 3:20 ` randy_dunlap
2005-07-28 23:05 ` Pierre Ossman [this message]
2005-07-29 3:13 ` Randy.Dunlap
2005-08-05 14:32 ` Pierre Ossman
2005-08-06 22:35 ` Guennadi Liakhovetski
2005-08-07 12:21 ` Pierre Ossman
2005-08-07 20:49 ` atomic_kmap for PIO (was Re: Fw: Kernel panic with dc395x in 2.6.12.2) Guennadi Liakhovetski
2005-08-07 22:34 ` Mike Christie
2005-08-07 23:31 ` Guennadi Liakhovetski
2005-08-07 23:53 ` Mike Christie
2005-08-08 19:31 ` Guennadi Liakhovetski
2005-09-05 21:50 ` Guennadi Liakhovetski
2005-09-13 3:09 ` James Bottomley
2005-09-13 16:56 ` Guennadi Liakhovetski
2005-09-16 17:28 ` Guennadi Liakhovetski
2005-07-15 12:54 ` Fw: Kernel panic with dc395x in 2.6.12.2 Pierre Ossman
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=42E964CC.5060600@drzeus.cx \
--to=drzeus-list@drzeus.cx \
--cc=g.liakhovetski@gmx.de \
--cc=linux-scsi@vger.kernel.org \
--cc=oliver@neukum.name \
--cc=rdunlap@xenotime.net \
/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;
as well as URLs for NNTP newsgroup(s).