Björn Steinbrink wrote:
> On 2007.06.04 16:39:25 +0200, Björn Steinbrink wrote:
>> On 2007.06.04 15:55:14 +0200, Benjamin Pineau wrote:
>>> lspci -vv, lspci -vn, /proc/config.gz, /proc/timer_list, lsmod,
>>> /proc/interrupts, /proc/vmstat, ps auxf, and dmesg (with and 
>>> without the bug's logs) outputs at
>>> http://oshima.zouh.org/~ben/2.6.23-rc3_bug_details.txt
>> To save somebody else from guessing, that's HIRoshima, i.e. the correct
>> URL is http://hiroshima.zouh.org/~ben/2.6.23-rc3_bug_details.txt
> 
> Hmpf, about a second later the original URL also started to work...
> 
> Confused,
> Björn
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

I get something reproducible when using a setup that worked up until 2.6.22-rc2.
I did not report it because the authors of the projects involved do not like that I
use the particular setup that I do.
The setup is using iSCSI Initiator from kernel with iscsi enterprise Target (IET)
which is an out-of-tree kernel module. Both run on the same machine.

(The iet project do not like that I run on the same machine with the Initiator, and
they are probably right, just that it worked perfectly well up to 2.6.21, The first
2.6.22 patches broke the iet over files, and now I have above brakege also when
using iet-over-block-io)

Do I need to bisect this over my setup?

Some dmesg prints: