1. UCS-3.0 MS2 amd64 auf xen6 installiert 2. Nach dem Reboot sieht man noch kurz das rotierende Etwas 3. Danach wird der Bildschirm schwarz und Powersave geht an 4. Am Ende des Boot-Prozesses kommt der Bildschirm wieder und man sieht folgende Kernel-Meldung: [ 33.913780] [drm] nouveau 0000:02:00.0: 0x11B3: parsing clock script 0 [ 33.913809] BUG: unable to handle kernel NULL pointer dereference at (null) [ 33.913818] IP: [<ffffffff81312d0f>] __mutex_lock_common+0xc6/0x192 [ 33.913829] PGD 11ac4b067 PUD 11be63067 PMD 0 [ 33.913837] Oops: 0002 [#1] SMP [ 33.913842] last sysfs file: /sys/devices/system/cpu/cpu1/topology/thread_siblings [ 33.913850] CPU 1 [ 33.913854] Modules linked in: ip6table_filter ip6_tables ebtable_nat ebtables nfsd lockd nfs_acl auth_rpcgss sunrpc exportfs iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 iptable_filter ip_tables x_tables ext3 jbd kvm_amd kvm quota_v2 quota_tree nouveau ttm drm_kms_helper drm i2c_algo_bit snd_hda_codec_realtek i2c_nforce2 i2c_core k10temp shpchp snd_hda_intel pci_hotplug snd_hda_codec snd_hwdep edac_core edac_mce_amd snd_pcm snd_timer snd soundcore snd_page_alloc wmi pcspkr evdev processor psmouse serio_raw ext4 jbd2 crc16 dm_snapshot dm_mirror dm_region_hash dm_log dm_mod sg sr_mod cdrom sd_mod crc_t10dif ohci_hcd ahci video output ehci_hcd thermal thermal_sys button libata forcedeth usbcore nls_base [last unloaded: scsi_wait_scan] [ 33.914133] Pid: 384, comm: plymouthd Not tainted 2.6.32-ucs49-amd64 #1 To Be Filled By O.E.M. [ 33.914157] RIP: 0010:[<ffffffff81312d0f>] [<ffffffff81312d0f>] __mutex_lock_common+0xc6/0x192 [ 33.914187] RSP: 0018:ffff88011acc3e58 EFLAGS: 00010246 [ 33.914205] RAX: ffff88011acc3e68 RBX: ffff88011faeb008 RCX: ffff88011faeb010 [ 33.914226] RDX: 0000000000000000 RSI: 0000000000000002 RDI: ffff88011faeb00c [ 33.914247] RBP: ffff88011faeb00c R08: 0000000000000000 R09: 0000000000000000 [ 33.914269] R10: 0000000000000000 R11: 0000000000000246 R12: ffff88011be81530 [ 33.914291] R13: 0000000000000002 R14: ffff88011acc3fd8 R15: ffff88011be81530 [ 33.914313] FS: 00007f523ef2c700(0000) GS:ffff880005480000(0000) knlGS:0000000000000000 [ 33.914337] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 33.914355] CR2: 0000000000000000 CR3: 000000011af79000 CR4: 00000000000006e0 [ 33.914377] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 33.914397] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 [ 33.914419] Process plymouthd (pid: 384, threadinfo ffff88011acc2000, task ffff88011be81530) [ 33.914442] Stack: [ 33.914450] ffff88011faeb020 ffff88011faeb010 ffff88011faeb010 0000000000000000 [ 33.914485] <0> ffff88011fc12000 ffffffff810e5a1b ffff88011adf5500 ffff88011faeb008 [ 33.914529] <0> ffff88011faeb008 ffff88011f584b40 ffff88011fae4d70 ffff88011fae4d70 [ 33.914574] Call Trace: [ 33.914584] [<ffffffff810e5a1b>] ? __slab_free+0x7f/0x27a [ 33.914596] [<ffffffff81312e93>] ? mutex_lock+0x1a/0x31 [ 33.914610] [<ffffffff811bc62c>] ? fb_release+0x19/0x50 [ 33.914627] [<ffffffff810efe2d>] ? __fput+0x100/0x1af [ 33.914638] [<ffffffff810ed292>] ? filp_close+0x5b/0x62 [ 33.914653] [<ffffffff810ed32d>] ? sys_close+0x94/0xcd [ 33.914663] [<ffffffff81010b42>] ? system_call_fastpath+0x16/0x1b [ 33.914683] Code: ef e8 c9 0b 00 00 48 8d 43 08 48 8b 53 10 48 89 44 24 08 48 8b 4c 24 08 48 8d 44 24 10 48 89 54 24 18 48 89 43 10 48 89 4c 24 10 <48> 89 02 48 83 ca ff 4c 89 64 24 20 48 89 d0 87 03 ff c8 74 51 [ 33.914913] RIP [<ffffffff81312d0f>] __mutex_lock_common+0xc6/0x192 [ 33.914930] RSP <ffff88011acc3e58> [ 33.914940] CR2: 0000000000000000 [ 33.914951] ---[ end trace fa997fbf28060a12 ]---
Tritt das auch noch nach einem Update auf die aktuellen Versionen auf?
Das trat frisch mit einem UCS-3.0 MS2 auf. Nach einem Update aller Pakete von Omar (2011-10-12 ~17:30 Uhr) trat das nach dem Reboot immer noch auf, selbst nach einem # update-initramfs -k `uname -r` -u
Auf xen4 ist hierbei ein unschöner Nebeneffekt aufgetreten: Wenn man das System mit aktiviertem splash startet (welcher jedoch nicht angezeigt wird) und anschließend aufs tty1 wechselt, wird das eigene Passwort beim login angezeigt. Deaktiviert man den splash, ist die shell wieder "heile" und das PW ist nicht sichtbar.
Tritt das Problem noch auf?
(In reply to comment #4) > Tritt das Problem noch auf? Ja, ich konnte das mit einer aktuellen AMD64 DVD auf XEN6 reproduzieren, allerdings ohne die Kernel Meldung am Ende des Bootprozesses, dafür mit zusätzlicher Info aus dem syslog: Feb 20 14:13:06 mas kernel: [ 58.790630] nouveau_ratelimit: 10270 callbacks suppressed Feb 20 14:13:06 mas kernel: [ 58.790640] [drm] nouveau 0000:02:00.0: VM: trapped write at 0x000105870c on ch 0 [0x00000050] BAR/PFIFO_WRITE/IN reason: PAGE_NOT_PRESENT Feb 20 14:13:06 mas kernel: [ 58.790664] [drm] nouveau 0000:02:00.0: VM: trapped write at 0x0001058d4c on ch 0 [0x00000050] BAR/PFIFO_WRITE/IN reason: PAGE_NOT_PRESENT Feb 20 14:13:06 mas kernel: [ 58.790686] [drm] nouveau 0000:02:00.0: VM: trapped write at 0x000105938c on ch 0 [0x00000050] BAR/PFIFO_WRITE/IN reason: PAGE_NOT_PRESENT Feb 20 14:13:06 mas kernel: [ 58.790706] [drm] nouveau 0000:02:00.0: VM: trapped write at 0x00010599cc on ch 0 [0x00000050] BAR/PFIFO_WRITE/IN reason: PAGE_NOT_PRESENT Feb 20 14:13:06 mas kernel: [ 58.790727] [drm] nouveau 0000:02:00.0: VM: trapped write at 0x000105a00c on ch 0 [0x00000050] BAR/PFIFO_WRITE/IN reason: PAGE_NOT_PRESENT Feb 20 14:13:06 mas kernel: [ 58.790748] [drm] nouveau 0000:02:00.0: VM: trapped write at 0x000105a64c on ch 0 [0x00000050] BAR/PFIFO_WRITE/IN reason: PAGE_NOT_PRESENT Feb 20 14:13:06 mas kernel: [ 58.790768] [drm] nouveau 0000:02:00.0: VM: trapped write at 0x000105ac8c on ch 0 [0x00000050] BAR/PFIFO_WRITE/IN reason: PAGE_NOT_PRESENT Feb 20 14:13:06 mas kernel: [ 58.790789] [drm] nouveau 0000:02:00.0: VM: trapped write at 0x000105b2cc on ch 0 [0x00000050] BAR/PFIFO_WRITE/IN reason: PAGE_NOT_PRESENT Feb 20 14:13:06 mas kernel: [ 58.790808] [drm] nouveau 0000:02:00.0: VM: trapped write at 0x000105b90c on ch 0 [0x00000050] BAR/PFIFO_WRITE/IN reason: PAGE_NOT_PRESENT Feb 20 14:13:06 mas kernel: [ 58.790827] [drm] nouveau 0000:02:00.0: VM: trapped write at 0x000105bf4c on ch 0 [0x00000050] BAR/PFIFO_WRITE/IN reason: PAGE_NOT_PRESENT Feb 20 14:13:06 mas kernel: [ 58.790847] [drm] nouveau 0000:02:00.0: VM: trapped write at 0x000105c58c on ch 0 [0x00000050] BAR/PFIFO_WRITE/IN reason: PAGE_NOT_PRESENT Feb 20 14:13:06 mas kernel: [ 58.790868] [drm] nouveau 0000:02:00.0: VM: trapped write at 0x000105cbcc on ch 0 [0x00000050] BAR/PFIFO_WRITE/IN reason: PAGE_NOT_PRESENT Feb 20 14:13:06 mas kernel: [ 58.790889] [drm] nouveau 0000:02:00.0: VM: trapped write at 0x000105d20c on ch 0 [0x00000050] BAR/PFIFO_WRITE/IN reason: PAGE_NOT_PRESENT Feb 20 14:13:06 mas kernel: [ 58.790908] [drm] nouveau 0000:02:00.0: VM: trapped write at 0x000105d84c on ch 0 [0x00000050] BAR/PFIFO_WRITE/IN reason: PAGE_NOT_PRESENT Feb 20 14:13:06 mas kernel: [ 58.790929] [drm] nouveau 0000:02:00.0: VM: trapped write at 0x000105de8c on ch 0 [0x00000050] BAR/PFIFO_WRITE/IN reason: PAGE_NOT_PRESENT Feb 20 14:13:06 mas kernel: [ 58.790950] [drm] nouveau 0000:02:00.0: VM: trapped write at 0x000105e4cc on ch 0 [0x00000050] BAR/PFIFO_WRITE/IN reason: PAGE_NOT_PRESENT Feb 20 14:13:06 mas kernel: [ 58.790971] [drm] nouveau 0000:02:00.0: VM: trapped write at 0x000105eb0c on ch 0 [0x00000050] BAR/PFIFO_WRITE/IN reason: PAGE_NOT_PRESENT Feb 20 14:13:06 mas kernel: [ 58.790991] [drm] nouveau 0000:02:00.0: VM: trapped write at 0x000105f14c on ch 0 [0x00000050] BAR/PFIFO_WRITE/IN reason: PAGE_NOT_PRESENT Feb 20 14:13:06 mas kernel: [ 58.791011] [drm] nouveau 0000:02:00.0: VM: trapped write at 0x000105f78c on ch 0 [0x00000050] BAR/PFIFO_WRITE/IN reason: PAGE_NOT_PRESENT Feb 20 14:13:06 mas kernel: [ 58.791030] [drm] nouveau 0000:02:00.0: VM: trapped write at 0x000105fdcc on ch 0 [0x00000050] BAR/PFIFO_WRITE/IN reason: PAGE_NOT_PRESENT
Das scheint auf einer HP ProLiant G7 mit UCS 3.1 auch aufzutreten: Apr 9 15:49:18 virt kernel: imklog 4.6.4, log source = /proc/kmsg started. Apr 9 15:49:18 virt kernel: /linux-3.2.30/drivers/gpu/drm/radeon/radeon_gart.c:187 radeon_gart_bind+0x3c/0x176 [radeon]() Apr 9 15:49:18 virt kernel: [ 27.671796] Hardware name: ProLiant DL380 G7 Apr 9 15:49:18 virt kernel: [ 27.671798] trying to bind memory to uninitialized GART ! Apr 9 15:49:18 virt kernel: [ 27.671801] Modules linked in: ext4 jbd2 crc16 sha256_generic dm_crypt blktap xen_blkfront xenfs xen_evtchn quota_v2 quota_tree uas sg sr_mod snd_pcm snd_timer snd soundcore tpm_tis snd_page_alloc tpm tpm_bios coretemp cdrom pcspkr psmouse serio_raw joydev i7core_edac edac_core hpwdt hpilo acpi_power_meter container evdev proces sor ext3 jbd usbhid hid dm_snapshot dm_mirror dm_region_hash dm_log dm_mod usb_storage sd_mod crc_t10dif crc32c_intel ghash_clmulni_intel radeon aesni_intel cryptd ttm aes_x86_64 ae s_generic uhci_hcd drm_kms_helper drm i2c_algo_bit i2c_core power_supply ehci_hcd usbcore usb_common bnx2 thermal thermal_sys button hpsa [last unloaded: scsi_wait_scan] Apr 9 15:49:18 virt kernel: [ 27.671866] Pid: 356, comm: plymouthd Tainted: G W 3.2.0-ucs17-amd64 #1 Debian 3.2.30-1.17.201210041157 Apr 9 15:49:18 virt kernel: [ 27.671870] Call Trace: Apr 9 15:49:18 virt kernel: [ 27.671881] [<ffffffff81049874>] ? warn_slowpath_common+0x78/0x8c Apr 9 15:49:18 virt kernel: [ 27.671886] [<ffffffff81049926>] ? warn_slowpath_fmt+0x45/0x4a Apr 9 15:49:18 virt kernel: [ 27.671910] [<ffffffffa0106ff1>] ? radeon_gart_bind+0x3c/0x176 [radeon] Apr 9 15:49:18 virt kernel: [ 27.671932] [<ffffffffa01054b9>] ? radeon_ttm_backend_bind+0x54/0x82 [radeon] Apr 9 15:49:18 virt kernel: [ 27.671942] [<ffffffffa00cb2c7>] ? ttm_tt_bind+0x3c/0x5c [ttm] Apr 9 15:49:18 virt kernel: [ 27.671951] [<ffffffffa00cbb7f>] ? ttm_bo_handle_move_mem+0x172/0x320 [ttm] Apr 9 15:49:18 virt kernel: [ 27.671961] [<ffffffffa00cd620>] ? ttm_bo_move_buffer+0xc6/0xf6 [ttm] Apr 9 15:49:18 virt kernel: [ 27.671971] [<ffffffffa00cd6f2>] ? ttm_bo_validate+0xa2/0xec [ttm] Apr 9 15:49:18 virt kernel: [ 27.671980] [<ffffffffa00cdab5>] ? ttm_bo_init+0x379/0x3b8 [ttm] Apr 9 15:49:18 virt kernel: [ 27.672002] [<ffffffffa0106d21>] ? radeon_bo_create+0x1ad/0x234 [radeon] Apr 9 15:49:18 virt kernel: [ 27.672024] [<ffffffffa0106ad4>] ? radeon_bo_kmap+0x6b/0x6b [radeon] Apr 9 15:49:18 virt kernel: [ 27.672049] [<ffffffffa01138fc>] ? radeon_gem_object_create+0x49/0xd5 [radeon] Apr 9 15:49:18 virt kernel: [ 27.672074] [<ffffffffa0113a75>] ? radeon_gem_create_ioctl+0x42/0x7c [radeon] Apr 9 15:49:18 virt kernel: [ 27.672085] [<ffffffff8137f9c0>] ? _raw_spin_lock_irqsave+0x11/0x2f Apr 9 15:49:18 virt kernel: [ 27.672092] [<ffffffff8106639d>] ? lock_hrtimer_base+0x1b/0x3c Apr 9 15:49:18 virt kernel: [ 27.672106] [<ffffffffa00857b5>] ? drm_ioctl+0x271/0x345 [drm] Apr 9 15:49:18 virt kernel: [ 27.672114] [<ffffffff81066598>] ? hrtimer_cancel+0xc/0x16 Apr 9 15:49:18 virt kernel: [ 27.672144] [<ffffffffa0113a33>] ? radeon_mode_dumb_create+0xab/0xab [radeon] Apr 9 15:49:18 virt kernel: [ 27.672152] [<ffffffff8137ef40>] ? schedule_hrtimeout_range_clock+0xc4/0x125 Apr 9 15:49:18 virt kernel: [ 27.672157] [<ffffffff8137f7d5>] ? _raw_spin_unlock_irqrestore+0x10/0x11 Apr 9 15:49:18 virt kernel: [ 27.672164] [<ffffffff81137722>] ? ep_poll+0x236/0x2db Apr 9 15:49:18 virt kernel: [ 27.672169] [<ffffffff81113def>] ? do_vfs_ioctl+0x464/0x4b1 Apr 9 15:49:18 virt kernel: [ 27.672177] [<ffffffff8106a272>] ? timekeeping_get_ns+0xd/0x2a Apr 9 15:49:18 virt kernel: [ 27.672183] [<ffffffff81113e87>] ? sys_ioctl+0x4b/0x70 Apr 9 15:49:18 virt kernel: [ 27.672190] [<ffffffff810621b0>] ? posix_ktime_get_ts+0xc/0x11 Apr 9 15:49:18 virt kernel: [ 27.672197] [<ffffffff81384e12>] ? system_call_fastpath+0x16/0x1b Apr 9 15:49:18 virt kernel: [ 27.672201] ---[ end trace 368b93c809aba1ce ]--- Apr 9 15:49:18 virt kernel: [ 27.672208] [drm:radeon_ttm_backend_bind] *ERROR* failed to bind 768 pages at 0x00000000 Apr 9 15:49:18 virt kernel: [ 27.672442] radeon 0000:01:03.0: object_init failed for (3145728, 0x00000002) Apr 9 15:49:18 virt kernel: [ 27.672448] [drm:radeon_gem_object_create] *ERROR* Failed to allocate GEM object (3145728, 2, 4096, -22) Apr 9 15:49:18 virt kernel: [ 27.691795] ------------[ cut here ]------------
(In reply to comment #6) > Das scheint auf einer HP ProLiant G7 mit UCS 3.1 auch aufzutreten: Das ist nicht der gleiche Trace wie auf xen6, denn dort ist eine Nvidia-Grafikkarte im Einsatz. > /linux-3.2.30/drivers/gpu/drm/radeon/radeon_gart.c:187 > radeon_gart_bind+0x3c/0x176 [radeon]() > Apr 9 15:49:18 virt kernel: [ 27.671796] Hardware name: ProLiant DL380 G7 > Apr 9 15:49:18 virt kernel: [ 27.671798] trying to bind memory to > uninitialized GART ! Zumindest dieser Trace sollte mit dem 3.2.39-Kernel (3.2.0-ucs27-amd64) aus UCS-3.1-0-errata81 nicht mehr auftreten, den folgender Patch ist darin bereits enthalten: <https://bugzilla.redhat.com/show_bug.cgi?id=785375#c73> <https://bugzilla.redhat.com/attachment.cgi?id=603278&action=diff>
This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4. If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.
There is a Customer ID set so I set the flag "Enterprise Customer affected".
This issue has been filed against UCS 3.1. UCS 3.1 is out of maintenance and many UCS components have vastly changed in later releases. Thus, this issue is now being closed. If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen this issue. In this case please provide detailed information on how this issue is affecting you.