Damyan Ivanov wrote:
> My data integrity problem disappeared after the system provider replaced
> the zero-channel controller. Sorry for not informing you earlier. Later
> I upgraded the kernel and 2.6.15 is running just fine right now.
> It was not the kernel to blame.
Oh, my conclusion was way t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jurij Smakov wrote:
> Hi guys,
Hi, Jurij,
> As the kernels against which this bug has been reported are not in the
> archive any more, we would appreciate if you could provide the updated
> information, testing whether the bug still exist in the lates
Hi guys,
As the kernels against which this bug has been reported are not in the
archive any more, we would appreciate if you could provide the updated
information, testing whether the bug still exist in the latest kernels.
Otherwise I'll close the bug a week from now (Sunday, April 2nd, 2006).
Hi all!
Could one of you please retest with a current kernel (testing:2.6.12,
unstable:2.6.14)?
Additionally, please send in output for these commands:
dmesg
lspci
lspci -n
lsmod
Thanks, David
--
- hallo... wie gehts heute?
- *hust* gut *rotz* *keuch*
- gott sei dank kommunizieren wir über e
Package: kernel-source-2.6.11
Version: 2.6.11-3
Severity: important
When running an em64t kernel with either the megaraid driver or the newer
megaraid_mbox driver, and the machine in question has 4GiB of memory,
reads/writes past the 130GiB mark (approximately) of a partition on the
logical scsi
5 matches
Mail list logo