[Dell Vostro 3400] Cannot access the text console.

Bug #734996 reported by PKduck
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

During a booting process, there should a "kubuntu" logo with 5 blinking dots since I am using Kubuntu. But it shows a black screen instead after loading the kernel and before Xorg started. Disabling modeset can get back the boot splash but lost accelerated 3D.
After Xorg loaded, it shows a normal composited desktop with full hardware acceleration. But pressing Ctrl+Alt+F1 will hide the mouse cursor and cause the screen to freeze. Pressing Ctrl+Alt+7 can switch back to Xorg. It is also true for live DVD or a fully updated(as of today) system.

WORKAROUND: I get back the text console by doing the following:
1) Blacklist nouveau
2) Rename "/lib/modules/2.6.38-8-generic/kernel/drivers/gpu/drm/nouveau/nouveau.ko" to something else.
3) sudo update-initramfs -k all -u
4) sudo update-grub2
5) Reboot.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: linux-image-2.6.38-6-generic 2.6.38-6.34
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.38-6.34-generic 2.6.38-rc7
Uname: Linux 2.6.38-6-generic x86_64
NonfreeKernelModules: wl
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
   Subdevices: 0/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: pkduck 1513 F.... pulseaudio
 /dev/snd/pcmC0D0c: pkduck 1513 F...m pulseaudio
 /dev/snd/pcmC0D0p: pkduck 1513 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfb400000 irq 48'
   Mixer name : 'IDT 92HD81B1X5'
   Components : 'HDA:111d7605,10280440,00100105'
   Controls : 14
   Simple ctrls : 9
Card1.Amixer.info:
 Card hw:1 'NVidia'/'HDA NVidia at 0xfa080000 irq 16'
   Mixer name : 'Nvidia GPU 0b HDMI/DP'
   Components : 'HDA:10de000b,10de0101,00100100'
   Controls : 16
   Simple ctrls : 4
Date: Tue Mar 15 01:55:25 2011
HibernationDevice: RESUME=UUID=9ae7919b-4723-47c8-ad54-618575be1235
InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110303)
MachineType: Dell Inc. Vostro 3400
ProcEnviron:
 LANGUAGE=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-6-generic root=UUID=ac177ace-fa7e-48ae-b159-9294925b4e89 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-2.6.38-6-generic N/A
 linux-backports-modules-2.6.38-6-generic N/A
 linux-firmware 1.48
SourcePackage: linux
StagingDrivers: brcm80211
Title: [STAGING]
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/21/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A04
dmi.board.name: 0RXV7H
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: dmi:bvnDellInc.:bvrA04:bd05/21/2010:svnDellInc.:pnVostro3400:pvrNotSpecified:rvnDellInc.:rn0RXV7H:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Vostro 3400
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.
---
ApportVersion: 2.12.7-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: pkduck 1419 F.... pulseaudio
 /dev/snd/controlC0: pkduck 1419 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.04
InstallationDate: Installed on 2013-12-15 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131215)
MachineType: Dell Inc. Vostro 3400
MarkForUpload: True
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-7-generic root=UUID=0260376b-5122-4d52-be39-576de2d88f1b ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
RelatedPackageVersions:
 linux-restricted-modules-3.12.0-7-generic N/A
 linux-backports-modules-3.12.0-7-generic N/A
 linux-firmware 1.117
Tags: trusty
Uname: Linux 3.12.0-7-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 05/21/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A04
dmi.board.name: 0RXV7H
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: dmi:bvnDellInc.:bvrA04:bd05/21/2010:svnDellInc.:pnVostro3400:pvrNotSpecified:rvnDellInc.:rn0RXV7H:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Vostro 3400
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.

Revision history for this message
PKduck (jhnpwa) wrote :
tags: added: regression-release
removed: regression-update
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
PKduck (jhnpwa) wrote :

I get back the text console by doing the following:
1) Blacklist nouveau
2) Rename "/lib/modules/2.6.38-8-generic/kernel/drivers/gpu/drm/nouveau/nouveau.ko" to something else.
3) sudo update-initramfs -k all -u
4) sudo update-grub2
5) Reboot.

penalvch (penalvch)
tags: added: bios-outdated-a10
description: updated
Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
PKduck (jhnpwa) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected trusty
description: updated
Revision history for this message
PKduck (jhnpwa) wrote : BootDmesg.txt

apport information

Revision history for this message
PKduck (jhnpwa) wrote : CRDA.txt

apport information

Revision history for this message
PKduck (jhnpwa) wrote : CurrentDmesg.txt

apport information

Revision history for this message
PKduck (jhnpwa) wrote : IwConfig.txt

apport information

Revision history for this message
PKduck (jhnpwa) wrote : Lspci.txt

apport information

Revision history for this message
PKduck (jhnpwa) wrote : Lsusb.txt

apport information

Revision history for this message
PKduck (jhnpwa) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
PKduck (jhnpwa) wrote : ProcEnviron.txt

apport information

Revision history for this message
PKduck (jhnpwa) wrote : ProcInterrupts.txt

apport information

Revision history for this message
PKduck (jhnpwa) wrote : ProcModules.txt

apport information

Revision history for this message
PKduck (jhnpwa) wrote : PulseList.txt

apport information

Revision history for this message
PKduck (jhnpwa) wrote : RfKill.txt

apport information

Revision history for this message
PKduck (jhnpwa) wrote : UdevDb.txt

apport information

Revision history for this message
PKduck (jhnpwa) wrote : UdevLog.txt

apport information

Revision history for this message
PKduck (jhnpwa) wrote : WifiSyslog.txt

apport information

Revision history for this message
PKduck (jhnpwa) wrote : Re: [STAGING]Cannot access the text console.

Not sure how to mark this bug. When booting without "nomodeset" and with the module "nouveau" active, the screen will freeze minutes after showing Unity. When booting with "nomodeset" and with or without the module "nouveau", the screen won't freeze but there is no 3D acceleration. When booting without "nomodeset" and without the module "nouveau" active, the screen won't freeze. In all cases, I can switch to the text console with Ctrl+Alt+F1 before the screen freezes. The results are the same with a mainline kernel.

penalvch (penalvch)
summary: - [STAGING]Cannot access the text console.
+ [Dell Vostro 3400] Cannot access the text console.
tags: added: kernel-bug-exists-upstream-v13.3-rc3
Revision history for this message
PKduck (jhnpwa) wrote :

I updated the BIOS. The screen still freezes. The command output the following:
A10
10/25/2010

penalvch (penalvch)
tags: added: latest-bios-a10
removed: bios-outdated-a10
Revision history for this message
PKduck (jhnpwa) wrote :

No. The 11.04 release didn't have freezes even with the nouveau module loaded although the text console was inaccessible.

Revision history for this message
penalvch (penalvch) wrote :

PKduck, was there a release prior to 11.04 where the text console was accessible?

Revision history for this message
PKduck (jhnpwa) wrote :

The text console was accessible in 10.04.4 LTS and 10.10. In 9.10, the screen went blank with backlight on after isolinux.

Revision history for this message
penalvch (penalvch) wrote :

PKduck, the next step is to fully commit bisect from 10.10 to 11.04, in order to identify the offending commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

Revision history for this message
PKduck (jhnpwa) wrote :

I followed the guide and I found out the offending commit is between 2.6.35-32.68 and 2.6.36-0.1. I tried git://kernel.ubuntu.com/ubuntu-archive/ubuntu-maverick.git and git://kernel.ubuntu.com/ubuntu-archive/ubuntu-natty.git, but none of them contains both tags for me to bisect.

Revision history for this message
PKduck (jhnpwa) wrote :

It is getting more and more confusing. Mainline 2.6.35 and 2.6.36 both have this bug. It looks like if nouveau is loaded too fast, the console won't be accessible.

Revision history for this message
penalvch (penalvch) wrote :

PKduck, it would be expected 2.6.35 mainline has the bug as the Ubuntu kernel doesn't map exactly to mainline. One would want to test an older version of the mainline (ex. http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.34.1-maverick/ or even earlier than that) in order to find a version that is free of the bug.

Revision history for this message
PKduck (jhnpwa) wrote :

The offending commit is between mainline 2.6.35-rc1 and 2.6.35-rc2. However, I cannot reproduce the bug on a locally compiled 2.6.35-rc2 kernel with default config. If I compiled the same version with the config from http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.35-rc2-maverick/, it will panic right when it begins to boot.

Revision history for this message
penalvch (penalvch) wrote :

PKduck, thank you for continuing to work on fully commit bisecting. Just to clarify your results so far:
"However, I cannot reproduce the bug on a locally compiled 2.6.35-rc2 kernel with default config."

So, when you compile the kernel pulled from git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git 2.6.35-rc2 works?

>"If I compiled the same version with the config from http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.35-rc2-maverick/"

Could you please clarify what you mean by this? Are you just installing the provided debs or are you doing some pre/post install modifications?

Revision history for this message
PKduck (jhnpwa) wrote :

I compiled my kernel according to the guide at https://wiki.ubuntu.com/KernelTeam/GitKernelBuild. It says I need to clone from git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git. When I build the kernel with the following commands and install the compiled deb, it works. I can access the text console for 10+ boots in a row so far.

git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
cd linux
git checkout v2.6.35-rc2
yes '' | make oldconfig
make clean
make -j4 deb-pkg
sudo dpkg --install ../linux-image-2.6.35-rc2_2.6.35-rc2-1_amd64.deb <-- the name is different every time

However, if I replace the ".config" file with /boot/config-2.6.35-020635rc2-generic then compile it again and install the compiled deb, it panics every time I turn on the machine.

It will boot if I use "linux-image-2.6.35-020635rc2-generic_2.6.35-020635rc2_amd64.deb" provided by the mainline kernel ppa. But the text console cannot be accessed occasionally.

I did not do any modifications beyond that.

Revision history for this message
penalvch (penalvch) wrote :

PKduck, thank you for your comments. Unfortunately, it is not quite clear what you are referring to.

I'm following the fact you downloaded linux.git compiled it with no modifications and it works.

However, I'm not following the source of your /boot//config-2.6.35-020635rc2-generic. Where did you copy this from specifically your current install? Direct URL?

Revision history for this message
PKduck (jhnpwa) wrote :

The file is provided by http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.35-rc2-maverick/linux-image-2.6.35-020635rc2-generic_2.6.35-020635rc2_amd64.deb. I was trying to compile the kernel as similar to the precompiled one as possible.

penalvch (penalvch)
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote : Test with newer development kernel (3.13.0-24.46)

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

  With the recent release of this Ubuntu release, would like to confirm if this bug is still present. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.13.0-24.46
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.