On Sat, Dec 27, 2008 at 5:00 PM, Moritz Muehlenhoff j...@inutil.org wrote:
On Tue, May 20, 2008 at 06:36:22PM +0200, maximilian attems wrote:
does this still happen with a recent kernel aka 2.6.25 linux images?
thanks for feedback.
Andrew, does this error still occur with more recent kernel
On Mon, Apr 14, 2008 at 3:38 PM, Andrew Moise [EMAIL PROTECTED] wrote:
Debian kernel guys, how do you feel about the situation? Would you
be willing to apply a patch upgrading 2.6.24's iscsi subsystem to the
version from 2.6.25 if that fixed serious known bugs? Would you
prefer
On Mon, Apr 14, 2008 at 12:56 PM, Mike Christie [EMAIL PROTECTED] wrote:
You mean you want the sync cache fix right? Can I just send a patch for
what went into 2.6.25 since there are several fixes in there you guys
probably want and because the patch will be easier for me to make? :)
Just
On Thu, Feb 28, 2008 at 10:00 AM, Mike Christie [EMAIL PROTECTED] wrote:
Andrew Moise wrote:
Are there any iscsi fixes in 2.6.24, or is it 2.6.25 or nothing?
There are major fixes in 2.6.23 for error handler races and an oops.
There is one major fix in 2.6.24 for a write out race
On 2/28/08, Mike Christie [EMAIL PROTECTED] wrote:
Andrew Moise wrote:
On 2/23/08, Andrew Moise [EMAIL PROTECTED] wrote:
Okay, the userspace tools in open-iscsi 2.0.868-rc1, when combined
with either the 2.6.25-rc2 kernel or the Debian 4.0 kernel (2.6.18)
with the backported driver
On 2/28/08, Mike Christie [EMAIL PROTECTED] wrote:
I am not familiar with Debain. Is lenny the name of the stable tree for
Debain?
It's the name for the next stable release of Debian.
If you guys tell me what kernel you are using, I can try to port the
upstream patches to your kernel for
clone 466954 -1
reassign -1 open-iscsi
found -1 2.0.865-1
thanks
Okay, Mike Christie (the upstream maintainer) said that this was a
known bug and recommended that I use _both_ the new kernel driver
(available in kernel 2.6.25-rc2) and the new upstream userspace code
(version 2.0-868-rc1).
On 2/22/08, Andrew Moise [EMAIL PROTECTED] wrote:
In any case, I'll try the new userspace tools with 2.6.25-rc2 over
the weekend and let you know. If it seems to work out okay (and I
have a ton of time to kill :-), I'll also try the new kernel modules
on the 2.6.18 kernel that I was using
On 2/22/08, Mike Christie [EMAIL PROTECTED] wrote:
What other issues are you hitting. They might be fixed in the new
release or we might still need a bug report. Let me know.
The etch kernel I was originally using (2.6.18) crashed the machine
when I tried to log in to the MD3000i enclosure,
On 2/22/08, Mike Christie [EMAIL PROTECTED] wrote:
Andrew Moise wrote:
If I still see the problem with the management interface in a newer
kernel, I'll file a separate bug report about it.
Ok thanks for the info. I do not think open-iscsi will be able to do
anything about that. The scsi
After being advised that upgrading to more recent firmware fixes
this problem, I've installed Dell driver update R149666, which
upgrades the Perc 5i firmware to version v5.1.1-0040. That seems to
solve this problem for me even when I boot back into the unmodified
2.6.16 kernel. I therefore
Sumant Patro confirmed that that one-liner is a critical fix that
must be applied. Unfortunately, it doesn't fix my problem :-(.
I've gone back to the BLKDEV_MAX_RQ workaround for now; if I learn of
a better solution, I'll send it along.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
Package: linux-image-2.6.16-2-em64t-p4-smp
Version: 2.6.16-18~bpo.1
Severity: normal
I feel very bad filing a bug against a backports package, but this
backports package is (according to the changelog) an unmodified
2.6.16-18 package, just recompiled for sarge, and people on the
mailing lists
Christophe Chisogne wrote:
You're not alone. It's known kernel bug (at least since 01/2005) and I just
filed
a bug [1] against the linux-image-2.6.16-1-686.
The work around : compile a new kernel without the options that cause the bug.
(partition type detection should start by dos-like
Package: linux-image-2.6.15-1-686
Version: 2.6.15-8
Severity: normal
When I plug in a flash stick that my roommate has filled with stuff
using his Macintosh computer, it doesn't work. Windows reads the
stick. Here's what happens when I put in the stick:
Mar 20 21:01:17 localhost vmunix: usb
Package: initramfs-tools
Version: 0.42
Severity: normal
I don't know whether this is because of initramfs-tools or udev,
or both, but when I upgraded them together they hit a spot of trouble:
Preparing to replace udev 0.076-4 (using .../archives/udev_0.076-5_i386.deb) ...
Unpacking replacement
Package: linux-image-2.6.14-2-686
Version: 2.6.14-3
Severity: normal
The linux kernel now does not boot for me. This is with udev 0.076-1
installed, and with hotplug purged. The IDE subsystem seems to be
initialized correctly, but /dev/hda1 does not exist. I get (copied by
hand):
hda:
Package: linux-image-2.6.12-1-686
Version: 2.6.12-1
Severity: normal
After installing linux-image, the automatic run of lilo failed. I
found that that had been because my /vmlinuz symlink pointed to
'/boot/-2.6' and my /initrd.img to '/boot/-2.6'.
-- System Information:
Debian Release:
- /boot/-2.6
[EMAIL PROTECTED] ~]$ ls -l /boot-2.6
ls: /boot-2.6: No such file or directory
... and, of course:
[EMAIL PROTECTED] ~]$ ls -l /boot/-2.6
ls: /boot/-2.6: No such file or directory
--
Andrew Moise [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
19 matches
Mail list logo
