/srv/irclogs.ubuntu.com/2008/06/02/#ubuntu-kernel.txt

emgentmorning02:50
=== asac_ is now known as asac
osmosisfrom a kernel driver perspective, what is the preferred RAID card vendor?06:24
pwnguinosmosis: ive heard many people suggest software RAID06:33
pwnguinbut I also don't use raid (I should change that)06:34
amitkosmosis: 3ware has always had good support for linux08:01
amitkosmosis: http://linas.org/linux/raid.html for other vendors and specific model details08:03
alex_joniosmosis: my personal oppinion is that software RAID is sometimes easier to recover08:29
alex_joniif your card has problems, it's not possible to recover the RAID on another machine, unless it's a compatible one08:30
alex_joniand software RAID doesn't have that much performance loss to be an issue08:30
tjaaltonshould I blame the kernel for not being able to resume from hibernation? Worked fine before enabling -proposed09:18
tjaaltonhangs after the message "Suspending the terminal(s)"09:18
=== mdz_ is now known as mdz
=== pgraner_ is now known as pgraner
newz2000when running virtualbox 1.6 my computer freezes up and the caps lock key blinks. Is there a way I can get any diagnostic information so I can file a bug report with the vendor?19:38
rtg__soren: ^^20:41
=== emgent_ is now known as emgent
sorennewz2000: Do you have vmware installed, too?21:06
sorenby any chance?21:06
newz2000no21:06
sorenHm... Kvm, then?21:06
newz2000yes21:06
sorenAh.21:06
sorenThat's likely your problem.21:07
newz2000:-( I can't use them both? Oh bummer.21:07
sorenNot at the same time.21:07
sorenTry unloading the kvm modules (sudo /etc/init.d/kvm stop) and try again.21:07
newz2000ok, I have to wait until I have finished my current work because I can't handle a hard lock at the moment21:08
newz2000this is a new problem with virtualbox 1.6 (1.5 worked fine)21:08
sorenThe various modules who use the virtualisation extensions in the CPU's have not agreen on a locking mechanism yet, and things go boom if more than one thing tries to use them at the same time.21:08
sorennewz2000: Well, it's a *possible* cause. It might be something completely different.21:08
newz2000ok, I'll test after a bit21:09
dupondjehttps://bugs.launchpad.net/ubuntu/+bug/235889 plz check :)21:40
ceekayanyone able to clue me in / point me to docs regarding kernel crash dumps at present and possibly where they were as of 7.04? I see it was accepted for hardy on https://blueprints.launchpad.net/ubuntu/+spec/linux-kernel-crash-dump , but the status does not seem to indicate that it was completed21:45
jeplerceekay: I'd also love to know more about this21:52
emgentheya22:10
rtg__Ng: saw your comment about e1000 EEPROM. Can you reproduce the problem reliably so that if I apply a patch you can tell that I fixed something?22:11
Ngrtg__: the machine in particular showing the problem is silbs' laptop, so while we do have a reliable testcase, we probably shouldn't interrupt her too much ;)22:16
rtg__Ng: well, if you'll work with her as she has time, I'll apply the patch in my PPA version.  I'll get it done later this evening since she's already left.22:17
Ngrtg__: ok, I can probably get on it during lunch or so22:19
rtg__Ng: ok, I'll add a comment to the bug report when its ready. I'm out for a bit...22:21
ceekayjepler: from what i've seen BenC 's footprints seem to show up in a few places (that link above as well as the grub changelog mentioning something about "we're no longer using kdump kernels") so i suspect he might have an understanding of what's going on/where things have been22:23
BenCNo, we're still using kdump kernels22:51
BenCjust that we are using a different method of loading them that the old menu.lst grub thing I had originally22:51
ceekayBenC: any documentation out there that i could use to see where things are/were?23:18

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!