On Mon August 15 2011, 4:04:20 AM, jim burns wrote:
> Pls cc me with responses, as I'm not subscribed.
>
> On Tue August 2 2011, 12:36:26 AM, Pasi Kärkkäinen wrote:
> > On Sat, Jul 30, 2011 at 06:28:26PM -0400, jim burns wrote:
> > > > solved the bare metal boot problem. I just got another
> > > > kernel-3.1.0-0.rc0 update (from git9.1 to git11.2). Hopefully,
> > > > fedora has sorted out it's kernel identity crisis!
> > >
> > >
> > >
> > > Rawhide kernel 3.1.0-0.rc0.git11.2.fc17.x86_64 boots correctly bare
> > > metal. It still reboots after the hypervisor output, tho'. It's
> > > around
> > > the time drm should kick in, but putting 'nomodeset' on the kernel's
> > > 'module' line has no effect.
> >
> >
> >
> > Konrad: Do you know if this is a known problem?
> >
> >
> >
> > -- Pasi
>
> On Mon August 15 2011, 1:43:23 AM, Konrad Rzeszutek Wilk wrote:
> > On Sun, Aug 14, 2011 at 06:41:37PM -0400, jim burns wrote:
> > > On Sun August 14 2011, 6:38:34 PM, jim burns wrote:
> > > > OK - replacing 'debug loglevel=8 video.allow_duplicates=1
> > > > nomodeset'
> > > > with 'nomodeset initcall_debug debug loglevel=10'. (The video
> > > > option was left over from a separate debug problem.) Log
> > > > included
> > > > - looks the same to me.>
> > >
> > > Ahem! And the log:
> > Yeah, this is the bug introduced by Andi. 3.1-rc2 has the fix. You are
> > looking for this git commit 06e727d2a5d9d889fabad35223ad77205a9bebb9
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:
Aug 16 19:18:50 Insp6400 kernel: [ 54.177011] BUG: scheduling while atomic:
modprobe/519/0x10000002
Aug 16 19:18:50 Insp6400 kernel: [ 54.177011] 3 locks held by modprobe/519:
Aug 16 19:18:50 Insp6400 kernel: [ 54.177011] #0:
(&__lockdep_no_validate__){......}, at: [<ffffffff8131605c>]
__driver_attach+0x3b/0x82
Aug 16 19:18:50 Insp6400 kernel: [ 54.177011] #1:
(&__lockdep_no_validate__){......}, at: [<ffffffff8131606a>]
__driver_attach+0x49/0x82
Aug 16 19:18:50 Insp6400 kernel: [ 54.177011] #2:
(irq_mapping_update_lock){+.+.+.}, at: [<ffffffff812d90be>]
xen_bind_pirq_msi_to_irq+0x31/0xda
Aug 16 19:18:50 Insp6400 kernel: [ 54.177011] Modules linked in: snd_pcm(+)
iwl3945(+) iwl_legacy dell_laptop microcode(+) r852 dcdbas mac80211 sm_common
nand nand_ids b44 nand_ecc ssb r592 i2c_i801 snd_timer mtd memstick joydev mii
cfg80211 snd iTCO_wdt rfkill soundcore iTCO_vendor_support snd_page_alloc tun
xen_gntalloc xen_netback xen_blkback xen_gntdev xen_evtchn binfmt_misc xenfs
sdhci_pci sdhci mmc_core firewire_ohci firewire_core crc_itu_t wmi i915
drm_kms_helper drm i2c_algo_bit i2c_core video
Aug 16 19:18:50 Insp6400 kernel: [ 54.177011] Pid: 519, comm: modprobe Not
tainted 3.1.0-0.rc2.git0.1.fc17.x86_64 #1
Aug 16 19:18:50 Insp6400 kernel: [ 54.177011] Call Trace:
--
Aug 16 19:18:50 Insp6400 kernel: [ 56.075632] BUG: sleeping function called
from invalid context at kernel/mutex.c:271
Aug 16 19:18:50 Insp6400 kernel: [ 56.076126] in_atomic(): 1,
irqs_disabled(): 0, pid: 506, name: modprobe
Aug 16 19:18:50 Insp6400 kernel: [ 56.076126] 3 locks held by modprobe/506:
Aug 16 19:18:50 Insp6400 kernel: [ 56.076126] #0:
(&__lockdep_no_validate__){......}, at: [<ffffffff8131605c>]
__driver_attach+0x3b/0x82
Aug 16 19:18:50 Insp6400 kernel: [ 56.076126] #1:
(&__lockdep_no_validate__){......}, at: [<ffffffff8131606a>]
__driver_attach+0x49/0x82
Aug 16 19:18:50 Insp6400 kernel: [ 56.076126] #2:
(irq_mapping_update_lock){+.+.+.}, at: [<ffffffff812d90be>]
xen_bind_pirq_msi_to_irq+0x31/0xda
Aug 16 19:18:50 Insp6400 kernel: [ 56.076126] Pid: 506, comm: modprobe Not
tainted 3.1.0-0.rc2.git0.1.fc17.x86_64 #1
Aug 16 19:18:50 Insp6400 kernel: [ 56.076126] Call Trace:
(and xenstored also is one of the 'comm:'s involved)
and INFO: errors of the form:
Aug 16 18:59:03 Insp6400 kernel: [ 84.717079] [ INFO: HARDIRQ-safe ->
HARDIRQ-unsafe lock order detected ]
Aug 16 18:59:03 Insp6400 kernel: [ 84.717079] 3.1.0-0.rc2.git0.1.fc17.x86_64
#1
Aug 16 18:59:03 Insp6400 kernel: [ 84.717079]
------------------------------------------------------
Aug 16 18:59:03 Insp6400 kernel: [ 84.717079] make/1668
[HC0[0]:SC1[3]:HE0:SE0] is trying to acquire:
Aug 16 18:59:03 Insp6400 kernel: [ 84.727071] (nf_conntrack_lock){+.-...},
at: [<ffffffffa03427b7>] destroy_conntrack+0x70/0xec [nf_conntrack]
Aug 16 18:59:03 Insp6400 kernel: [ 84.727071]
Aug 16 18:59:03 Insp6400 kernel: [ 84.727071] and this task is already
holding:
Aug 16 18:59:03 Insp6400 kernel: [ 84.727071] (&(&bp->lock)->rlock)
{-.-...}, at: [<ffffffffa01efa6a>] b44_poll+0x28/0x3ec [b44]
--
Aug 16 18:59:38 Insp6400 kernel: [ 119.749236] INFO: lockdep is turned off.
Aug 16 18:59:38 Insp6400 kernel: [ 119.749236] Pid: 2999, comm: rc.local
Tainted: G W 3.1.0-0.rc2.git0.1.fc17.x86_64 #1
Aug 16 18:59:38 Insp6400 kernel: [ 119.749236] Call Trace:
Aug 16 18:59:38 Insp6400 kernel: [ 119.749236] [<ffffffff8104f7bb>]
__might_sleep+0x103/0x108
Aug 16 18:59:38 Insp6400 kernel: [ 119.749236] [<ffffffff814f7744>]
mutex_lock_nested+0x25/0x45
Aug 16 18:59:38 Insp6400 kernel: [ 119.749236] [<ffffffff810c1f3e>]
free_desc+0x30/0x64
Aug 16 18:59:38 Insp6400 kernel: [ 119.749236] [<ffffffff810c1fab>]
irq_free_descs+0x39/0x72
Aug 16 18:59:38 Insp6400 kernel: [ 119.749236] [<ffffffff812d8424>]
xen_free_irq+0x49/0x4e
so it still has a way to go to being stable.
I did bring up an hvm (winxp) domain as far as grub, and got more 'BUG:
sleeping function's, so I 'xm destroy'-ed it, and rebooted back into f15's
2.6.40.
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home