[08:13] Hi all, now tested with upstream (mainline) kernel. - Bug #870250 and removed the according tag. Anything else I can do? [08:13] Launchpad bug 870250 in linux "Problem with external firewire disk and new firewire stack in Kubuntu 11.04 and 11.10 beta2" [Undecided,Confirmed] https://launchpad.net/bugs/870250 [08:14] Is there a way to switch back to the old firewire stack in 11.04? === yofel_ is now known as yofel === bigbash is now known as zz_bigbash [15:30] Any kernel expert wanna take a look at this? [15:30] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/863873 [15:30] Launchpad bug 863873 in linux "xubuntu 11.10 beta2 kernel boot problem" [Undecided,Confirmed] [15:30] I have attached two screen shots just before restart [15:37] Anyone? [17:38] Hello, I am running Ubuntu Natty with kernel 2.6.38-11-generic #50 and am getting a kernel oops which seems to involve my Radeon X300 video card. I have captured a crash dump (320+ MB) in /var/crash and would like to know the recommended next step. Thanks for advice. [17:58] Hello, I am running Ubuntu Natty with kernel 2.6.38-11-generic #50 and am getting a kernel oops which seems to involve my Radeon X300 video card. I have captured a crash dump (320+ MB) in /var/crash and would like to know the recommended next step. Thanks for advice. [17:58] x300: file a bug, from a terminal type ubuntu-bug [17:59] Thx, I will go ahead with that [17:59] and it will step you through filing the bug and attaching the crash info [17:59] OK [18:04] jjohansen: The "content of the report" window in Apport shows that the ProblemType is Bug. Shouldn't it say something like "kernel oops?" [18:05] x300: hrmm, actually I am not sure. Different versions of apport use different wording [18:06] x300: if you want to guarentee that it is filed against the kernel do [18:06] ubuntu-bug linux [18:06] jjohansen: I did :-) [18:06] generally ubuntu-bug should get you there by looking at what crashed and asking questions [18:07] but sometime specifying linux seems to be needed [18:07] jjohansen: OK, I will keep going in Apport. Maybe it will get better as I go. [18:39] In the webpage that is opened by Apport, the tag "apport-bug" is automatically added, but it appears this should be "apport-kerneloops." How can I get Apport to detect that the issue being reported is a kernel oops? Also, is there a procedure for modifying the Launchpad bug report to include the oops crash dump? [18:41] About "modifying" - I can try attaching the crash dump, but uploading 320+ MB may take a while [18:45] Is it OK to gzip the crash dump before attaching it? [19:43] How can I find out what options are compiled into my running kernel? [22:31] Heya, I'm seeing kernel panics with KVM+the latest Oneiric kernel, anyone familiar with debugging issues like this? https://bugs.launchpad.net/ubuntu/+source/linux/+bug/870168 [22:31] Launchpad bug 870168 in linux "Kernel Oops - Oneiric KVM/OpenStack triggers 'Unable to handle kernel NULL pointer deference'" [Undecided,Confirmed] [22:33] Heya, I'm seeing kernel panics with KVM+the latest Oneiric kernel, anyone familiar with debugging issues like this? https://bugs.launchpad.net/ubuntu/+source/linux/+bug/870168 [22:33] Launchpad bug 870168 in linux "Kernel Oops - Oneiric KVM/OpenStack triggers 'Unable to handle kernel NULL pointer deference'" [Undecided,Confirmed] [22:33] dooh [22:33] wrong window [22:34] (wrong window to him up+enter in ;))