This bug was fixed in the package linux - 2.6.31-6.26
---
linux (2.6.31-6.26) karmic; urgency=low
[ Andy Whitcroft ]
* [Config] enable CONFIG_AUFS_BR_RAMFS
- LP: #414738
* split out debian directory ready for abstraction
* add printdebian target to find branch target
*
** Changed in: linux (Ubuntu Karmic)
Status: Incomplete => In Progress
--
'modprobe aoe' on Karmic kernel oopses with AOE device from Jaunty
https://bugs.launchpad.net/bugs/410198
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Greetings,
I've tested (modprobe aoe with vblade running on another host), and it
looks good. I was able to discover, mount read/write data from/to the
volume, and unmount.
Thank you again, it looks like this latest patch resolved the oops!
--
'modprobe aoe' on Karmic kernel oopses with AOE de
Ok, I've respun the patch could you test the updated version for me and
report back here. Thanks! Kernels are at the URL below:
http://people.ubuntu.com/~apw/lp410198-karmic/
** Changed in: linux (Ubuntu Karmic)
Status: In Progress => Incomplete
--
'modprobe aoe' on Karmic kernel
** Also affects: linux (Ubuntu Karmic)
Importance: High
Assignee: Andy Whitcroft (apw)
Status: In Progress
** Changed in: linux (Ubuntu Karmic)
Milestone: None => karmic-alpha-5
--
'modprobe aoe' on Karmic kernel oopses with AOE device from Jaunty
https://bugs.launchpad.net/bu
Setting this to High as it is a blocker for Eucalyptus 1.6 delivery in
karmic.
** Changed in: linux (Ubuntu)
Importance: Medium => High
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
--
'modprobe aoe' on Karmic kernel oopses with AOE device from Jaunty
https://bugs.la
Greetings,
Thank you for tracking down and working on this issue; I've installed
the new kernel:
Linux foobar-desktop 2.6.31-6-generic #25~lp410198apw1 SMP Tue Aug 11
13:35:31 UTC 2009 x86_64 GNU/Linux
With a vblade running on another machine (on the same broadcast
network), ran 'modprobe aoe' a
Ok I have attempted to fix the driver to initialise the request_queue
structure correctly. I do not have a simple way to test this fix. I
have built fixed kernels and pushed them to the URL below. If you could
test these and let me know if they work better for you that would be
helpful. Kernels
We are panicing when trying to register the block queue:
[ 2645.959090] kobject '' (880059ca22c0): tried to add an
uninitialized object, something is seriously wrong.
[ 2645.959104] Pid: 6, comm: events/0 Not tainted 2.6.31-5-generic #24-Ubuntu
[ 2645.959107] Call Trace:
[ 2645.959139
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Tags added: regression-potential
--
'modprobe aoe' on Karmic kernel oopses with AOE device from Jaunty
https://bugs.launchpad.net/bugs/410198
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Some more info on reproducing this bug:
machine A running jaunty, with a number of vblade processes exporting
AOE devices:
# uname -a
Linux gibson 2.6.28-14-generic #47-Ubuntu SMP Sat Jul 25 01:19:55 UTC 2009
x86_64 GNU/Linux
# apt-cache policy vblade
vblade:
Installed: 16-1ubuntu2
Candidat
Thank you for taking the time to report this bug and helping to make Ubuntu
better. This bug did not have a package associated with it, which is important
for ensuring that it gets looked at by the proper developers. You can learn
more about finding the right package at
https://wiki.ubuntu.com
12 matches
Mail list logo
