[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-users] Continuing BUG:-iness booting Fedora Rawhide 3.1.0-rc's (was Summary: Experiences setting up a debug serial port)
On Tue August 30 2011, 11:20:45 PM, Todd Deshane wrote: > (adding fedora-xen to the CC) > > On Tue, Aug 30, 2011 at 5:17 PM, jim burns <jim_burn@xxxxxxxxxxxxx> wrote: > > On Tue August 23 2011, 5:12:52 PM, jim burns wrote: > >> On Tue August 16 2011, 7:46:33 PM, jim burns wrote: > >> > On Mon August 15 2011, 4:04:20 AM, jim burns wrote: > >> >> Pls cc me with responses, as I'm not subscribed. > >> > > >> > Yay! After a string of fedora rawhide 3.1.0-rc0 and -rc1's that > >> > did not boot under xen, 3.1.0-0.rc2.git0.1.fc17.x86_64 boots > >> > under xen, it has the vga patch, and xen-pciback correctly siezes > >> > my wireless device. Unfortunately, while a baremetal boot is > >> > clean, a xen boot has several BUG:'s of the form: > >> Rawhide is up to 3.1.0-0.rc3.git0.0.fc17.x86_64 , and it still has the > >> same BUGS: of the form: > >> > >> BUG: scheduling while atomic: modprobe/493/0x10000002 > >> > >> BUG: sleeping function called from invalid context at > >> kernel/mutex.c:271 > >> > >> BUG: scheduling while atomic: xenstored/3184/0x10000002 > >> > >> both while booting up under xen, and when starting and stopping a(n > >> hvm) guest. > > > > Rawhide is up to 3.1.0-0.rc4.git0.0.fc17 , and still the same bugs, plus > > the new one 'spinlock wrong CPU': > > > > Aug 30 17:07:13 Insp6400 kernel: [ 9.657492] BUG: sleeping function > > called from invalid context at kernel/mutex.c:271 > > Aug 30 17:07:13 Insp6400 kernel: [ 9.657553] in_atomic(): 1, > > irqs_disabled(): 0, pid: 254, name: modprobe > > -- > > Aug 30 17:07:13 Insp6400 kernel: [ 9.714251] BUG: scheduling while > > atomic: modprobe/254/0x10000002 > > Aug 30 17:07:13 Insp6400 kernel: [ 9.715224] 3 locks held by > > modprobe/254: > > -- > > Aug 30 17:07:13 Insp6400 kernel: [ 52.675476] BUG: sleeping function > > called from invalid context at kernel/mutex.c:271 > > Aug 30 17:07:13 Insp6400 kernel: [ 52.676191] in_atomic(): 1, > > irqs_disabled(): 0, pid: 511, name: modprobe > > -- > > Aug 30 17:07:13 Insp6400 kernel: [ 52.682754] BUG: scheduling while > > atomic: modprobe/511/0x10000002 > > Aug 30 17:07:13 Insp6400 kernel: [ 52.682754] 3 locks held by > > modprobe/511: > > -- > > Aug 30 17:07:13 Insp6400 kernel: [ 52.867221] BUG: spinlock wrong CPU > > on CPU#1, modprobe/511 > > Aug 30 17:07:13 Insp6400 kernel: [ 52.868082] lock: ffffffff81a7de60, > > .magic: dead4ead, .owner: modprobe/511, .owner_cpu: 0 > > -- > > Aug 30 17:07:13 Insp6400 kernel: [ 55.038559] BUG: sleeping function > > called from invalid context at kernel/mutex.c:271 > > Aug 30 17:07:13 Insp6400 kernel: [ 55.039487] in_atomic(): 1, > > irqs_disabled(): 0, pid: 508, name: modprobe > > -- > > Aug 30 17:07:13 Insp6400 kernel: [ 55.039487] BUG: scheduling while > > atomic: modprobe/508/0x10000002 > > Aug 30 17:07:13 Insp6400 kernel: [ 55.039487] INFO: lockdep is turned > > off. > > -- > > Aug 30 17:07:13 Insp6400 kernel: [ 55.153964] BUG: scheduling while > > atomic: modprobe/508/0x10000002 > > Aug 30 17:07:13 Insp6400 kernel: [ 55.154664] INFO: lockdep is turned > > off. > > -- > > Aug 30 17:08:04 Insp6400 kernel: [ 117.158477] BUG: sleeping function > > called from invalid context at kernel/mutex.c:271 > > Aug 30 17:08:04 Insp6400 kernel: [ 117.159068] in_atomic(): 1, > > irqs_disabled(): 0, pid: 3204, name: xenstored Rawhide is up to 3.1.0-0.rc5.git0.0.fc17 , and still the same dom0 boot bugs as in rc4. _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |