linux-kernel - Re: Dell PowerEdge 4200 scsi, worked in 2.6.18, not in 2.6.26

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110912065618.GA23340@elie>
Date:	Mon, 12 Sep 2011 01:56:18 -0500
From:	Jonathan Nieder <jrnieder@...il.com>
To:	trouble daemon <troubledaemon@...il.com>
Cc:	linux-kernel@...r.kernel.org, aystarik@...il.com, x86@...nel.org
Subject: Re: Dell PowerEdge 4200 scsi, worked in 2.6.18, not in 2.6.26

(resending with a newer address for Alexey - sorry for the noise)
Hi,

trouble daemon wrote:

> I am using a pair of Dell PowerEdg 4200's that have been working with
> debian since 2002 or so, 100% perfectly.
[...]
>   - 2.6.26 kernel that panics (latest unmodified debian kernel):
> http://pastebin.ca/1886636
>   - 2.6.18 kernel that works (latest unmodified debian kernel):
> http://pastebin.ca/1886641

pastebin.ca doesn't seem to exist any more, alas.

[...]
> Ben Hutchings wrote:

>> Another option that may be worth trying is 'noapic'.
>
> Wow, that worked just fine actually on 2.6.26 stock kernel. Thanks a lot!
[...]
> f8924e770e048429ae13bfabe1ddad9bf1e64df7 is first bad commit
> commit f8924e770e048429ae13bfabe1ddad9bf1e64df7
> Author: Alexey Starikovskiy <astarikovskiy@...e.de>
> Date:   Fri Apr 4 23:42:21 2008 +0400
>
>    x86: unify mp_bus_info
[...]
> I have verified that checking out the patch just before this one works
> fine on the machines.

Sorry we dropped the ball on this.  Dan, any news (e.g., do later
kernels do any better)?  Alexey, any ideas for tracking this down?

Thanks,
Jonathan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/