plymouth crashes on boot with kernel NULL pointer dereference

Bug #591825 reported by Sebastian Jürges
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: plymouth

see attached apport-bug report.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: plymouth 0.8.2-2ubuntu2
ProcVersionSignature: Ubuntu 2.6.32-22.36-server 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-server x86_64
Architecture: amd64
Date: Wed Jun 9 18:47:52 2010
DefaultPlymouth: Error: command ['readlink', '/etc/alternatives/default.plymouth'] failed with exit code 1:
Lsusb:
 Bus 002 Device 002: ID 04e8:3268 Samsung Electronics Co., Ltd ML-1610 Mono Laser Printer
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: System manufacturer System name
ProcCmdLine: root=UUID=2c9f00e3-2c62-4bf8-97bd-ff010e04de43 ro quiet splash vga=791
ProcEnviron:
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 radeondrmfb
SourcePackage: plymouth
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
dmi.bios.date: 09/29/2006
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS A8N-SLI DELUXE ACPI BIOS Revision 1805
dmi.board.name: A8N-SLI DELUXE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.XX
dmi.chassis.asset.tag: 123456789000
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSA8N-SLIDELUXEACPIBIOSRevision1805:bd09/29/2006:svnSystemmanufacturer:pnSystemname:pvr1.XX:rvnASUSTeKComputerINC.:rnA8N-SLIDELUXE:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System name
dmi.product.version: 1.XX
dmi.sys.vendor: System manufacturer

Revision history for this message
Sebastian Jürges (sjuerges) wrote :
Revision history for this message
Steve Langasek (vorlon) wrote :

Thank you for taking the time to report this bug and help to improve Ubuntu.

The report includes no information about the actual crash, so this is impossible to debug. Did apport not manage to collect a backtrace for this crash (because plymouth crashed too early, maybe)?

I see you have the radeon KMS driver loaded but are booting with vga=791. Is the problem reproducible if you drop this vga= option from your boot commandline? Is it reproducible if you boot without 'splash' (which is not the default for new installations of 10.04 LTS server)?

Changed in plymouth (Ubuntu):
status: New → Incomplete
Revision history for this message
Sebastian Jürges (sjuerges) wrote : Re: [Bug 591825] Re: plymouth crashes on boot with kernel NULL pointer dereference

plymouth crashed very early in the boot process, so i presume, apport did
not manage to gather any other information.

I've droppen the vga=791 and splash from the defoptions line in menu.lst,
that completely kills my console (only ssh login possible)
Dropping only the splash from the menu.lst still crashes plymouth (directly
after cups boot).

Can i manually collect a backtrace you can use and if yes, please send me
the appropriate commands. (direct debugging also possible, contact me via
jabber @ <email address hidden>)

Sebastian

2010/6/9 Steve Langasek <email address hidden>

> Thank you for taking the time to report this bug and help to improve
> Ubuntu.
>
> The report includes no information about the actual crash, so this is
> impossible to debug. Did apport not manage to collect a backtrace for
> this crash (because plymouth crashed too early, maybe)?
>
> I see you have the radeon KMS driver loaded but are booting with
> vga=791. Is the problem reproducible if you drop this vga= option from
> your boot commandline? Is it reproducible if you boot without 'splash'
> (which is not the default for new installations of 10.04 LTS server)?
>
> ** Changed in: plymouth (Ubuntu)
> Status: New => Incomplete
>
> --
> plymouth crashes on boot with kernel NULL pointer dereference
> https://bugs.launchpad.net/bugs/591825
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for plymouth (Ubuntu) because there has been no activity for 60 days.]

Changed in plymouth (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Alex Shulgin (alex-shulgin) wrote :
Download full text (5.1 KiB)

Happened to me one time today. Here's the relevant part of syslog:

Jan 3 15:58:00 moon init: plymouth main process (290) killed by SEGV signal
Jan 3 15:58:00 moon kernel: [ 69.750059] BUG: unable to handle kernel NULL pointer dereference at 0000000000000130
Jan 3 15:58:00 moon kernel: [ 69.750068] IP: [<ffffffffa01e4b63>] intel_release_load_detect_pipe+0x33/0xc0 [i915]
Jan 3 15:58:00 moon kernel: [ 69.750095] PGD 3ee78067 PUD 3ee84067 PMD 0
Jan 3 15:58:00 moon kernel: [ 69.750101] Oops: 0000 [#1] SMP
Jan 3 15:58:00 moon kernel: [ 69.750105] last sysfs file: /sys/devices/virtual/backlight/acpi_video0/actual_brightness
Jan 3 15:58:00 moon kernel: [ 69.750110] CPU 0
Jan 3 15:58:00 moon kernel: [ 69.750111] Modules linked in: parport_pc ppdev nls_utf8 nls_cp866 vfat fat snd_hda_codec_realtek joydev arc4 ipt_REJECT xt_comment ipt_LOG xt_multiport xt_limit xt_tcpudp ipt_addrtype xt_state snd_hda_intel ip6table_filter snd_hda_codec snd_hwdep ip6_tables snd_pcm nf_nat_irc nf_conntrack_irc nf_nat_ftp nf_nat snd_seq_midi nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack_ftp snd_rawmidi i915 rtl8187 nf_conntrack snd_seq_midi_event mac80211 snd_seq iptable_filter led_class snd_timer drm_kms_helper ip_tables snd_seq_device cfg80211 x_tables uvcvideo usbhid eeprom_93cx6 videodev drm v4l1_compat v4l2_compat_ioctl32 hid psmouse snd serio_raw i2c_algo_bit video output intel_agp soundcore snd_page_alloc lp parport usb_storage ahci r8169 mii libahci
Jan 3 15:58:00 moon kernel: [ 69.750173]
Jan 3 15:58:00 moon kernel: [ 69.750177] Pid: 1218, comm: Xorg Not tainted 2.6.35-24-generic #42-Ubuntu Base Board Product Name/Satellite L300
Jan 3 15:58:00 moon kernel: [ 69.750180] RIP: 0010:[<ffffffffa01e4b63>] [<ffffffffa01e4b63>] intel_release_load_detect_pipe+0x33/0xc0 [i915]
Jan 3 15:58:00 moon kernel: [ 69.750195] RSP: 0018:ffff88003c91fac8 EFLAGS: 00010202
Jan 3 15:58:00 moon kernel: [ 69.750198] RAX: 00000000ffffffff RBX: ffff880062235800 RCX: ffffc90005070024
Jan 3 15:58:00 moon kernel: [ 69.750201] RDX: 0000000000000003 RSI: ffff880062236000 RDI: ffff880062235800
Jan 3 15:58:00 moon kernel: [ 69.750204] RBP: ffff88003c91fb08 R08: 0000000000000000 R09: 00000000ffffffff
Jan 3 15:58:00 moon kernel: [ 69.750207] R10: 00000000ffffffff R11: 0000000000000001 R12: 0000000000000000
Jan 3 15:58:00 moon kernel: [ 69.750210] R13: ffff880062235888 R14: ffffffffa01ffd60 R15: ffff88006329f800
Jan 3 15:58:00 moon kernel: [ 69.750213] FS: 00007fb1310e9840(0000) GS:ffff880001e00000(0000) knlGS:0000000000000000
Jan 3 15:58:00 moon kernel: [ 69.750217] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Jan 3 15:58:00 moon kernel: [ 69.750219] CR2: 0000000000000130 CR3: 000000003d09e000 CR4: 00000000000006f0
Jan 3 15:58:00 moon kernel: [ 69.750223] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Jan 3 15:58:00 moon kernel: [ 69.750226] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Jan 3 15:58:00 moon kernel: [ 69.750229] Process Xorg (pid: 1218, threadinfo ffff88003c91e000, task ffff880063addb80)
Jan 3 15:58:00 moon kernel: [ 69.750232] Stack:
Jan 3 15:58:00 moon kernel: [...

Read more...

Steve Langasek (vorlon)
Changed in plymouth (Ubuntu):
status: Expired → New
Revision history for this message
dino99 (9d9) wrote :

That version has died long ago; no more supported

Changed in plymouth (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.