In article <[EMAIL PROTECTED]>,
Alan Cox <[EMAIL PROTECTED]> wrote:
>Yep - known problem. AMI have one more pre patch to sort it our Im going back
>to the older driver
I've tried the AMI patch and it appears to work. I'm now running
2.2.18pre18 + fix to ideprobe.c + ami megaraid fix and it looks
I don't believe that v1.09 (as in Red Hat Linux 7) has this problem, but
does have fixes over-and-above 1.07 (particularly, 1.07 and v1.08 touch
user-space inappropriately, 1.09 fixes). If PeterJ can't get to it before
2.2.18final, Alan, would you consider putting in the v1.09 driver?
Thanks,
Ma
Yep - known problem. AMI have one more pre patch to sort it our Im going back
to the older driver
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
LINUX KERNEL PROBLEM REPORT
[1.] Megaraid driver in Linux 2.2.18pre17 hangs on boot
[2.] Full description of the problem:
The Megaraid driver in Linux 2.2.18pre17 (labelling itself as "1.11") hangs
completely
on loading/boot on a DELL 6300, after detecting the DELL PERC adapter
On Fri, Oct 27, 2000 at 12:14:56PM +0100, Ian Jackson wrote:
> gcc version 2.95.2 2220 (Debian GNU/Linux)
Please give a try to 2.95.2 19991024 (release) or egcs 1.1.2 or gcc 2.7.2.3. I
don't see anything strange in your .config.
Andrea
-
To unsubscribe from this list: send the line "unsubscr
Andrea Arcangeli writes ("Re: linux 2.2.18pre17 + VM-global -7 = `Negative d_count'
oops"):
> On Thu, Oct 26, 2000 at 06:37:37PM +0100, Ian Jackson wrote:
> > Negative d_count (-805538369) for [binary garbage]/
> >
> > followed by an oops. Kernel logfile e
On Thu, Oct 26, 2000 at 06:37:37PM +0100, Ian Jackson wrote:
> Negative d_count (-805538369) for [binary garbage]/
>
> followed by an oops. Kernel logfile extract below, uuencoded.
Thanks for the feedback.
The oops is forced by the kernel after it sees then wrong negative d_count.
I'd say it
Andrea Arcangeli writes ("Re: linux 2.2.18-pre17: "Kernel panic: LRU list corrupted""):
> I also included the fix in a new VM-global patch against vanilla 2.2.18pre17
> (the VM-global patch is available as a single patch inside 2.2.18pre17aa1/
> directory too but I have to maintain a separate vers
On Thu, 19 Oct 2000, Alan Cox wrote:
> - Get to the bottom of the VM mystery if possible
The RAID problem (which is caused by VM changes) is the same deadlock
found in drbd and nbd.
It was not a problem with kernels < 2.2.17 because there was no write
throttling in shrink_mmap.
I'm attach
On Thu, 19 Oct 2000, Alan Cox wrote:
> This is just to give folks something to sync against. Test it by all means
> however.
>
> Must fix stuff left to do for 2.2.18final
> - Merge the S/390 stuff and make S/390 build again
> - Fix the megaraid (revert if need be)
> - Fix the ps/2 m
This is just to give folks something to sync against. Test it by all means
however.
Must fix stuff left to do for 2.2.18final
- Merge the S/390 stuff and make S/390 build again
- Fix the megaraid (revert if need be)
- Fix the ps/2 misdetect bug that has appeared
- NFSv3 ha
11 matches
Mail list logo
