[Bug 1888018] [NEW] nvme0 does not resume from standby
Public bug reported: This new laptop has a Samsung NVME SSD. The SSD (or the SSD controller) sometimes fails to resume from standby. The probability of this goes up with the time the laptop is on standby & I have to save all files when I put the laptop on standby at the end of the day as most likely it won't resume successfully. When I try & resume, normally the laptop appears to resume, I can unlock the screen but there's no disk access. Any programs that were in memory when I suspended the laptop are OK but everything else fails with an I/O error. The syslog includes entries like the following. nvme nvme0: Device not ready: aborting reset nvme nvme0: Removing after probe failure status: -19 Sometimes the first of these is repeated. Here is the relevant line from lspci. 02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 $ lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 $ uname -a Linux orion 5.4.0-40-generic #44-Ubuntu SMP Tue Jun 23 00:01:04 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888018 Title: nvme0 does not resume from standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1888018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886278] [NEW] iwlwifi: Queue 10 is active on fifo 3 and stuck for 10000 ms. SW [1, 3] HW [1, 3]
Public bug reported: The wifi has now crashed 3 times in as many hours on a clean new installation of focal. Unlike some other bugs here, I don't have to re-start. It's enough to re-connect using the network manager UI. The laptop is a Lenovo T495. The wifi controller is; 01:00.0 Network controller: Intel Corporation Wireless-AC 9260 (rev 29) Here are the results of 'grep iwlwifi /var/log/syslog' for the 3 crashes. Jul 4 14:27:23 orion kernel: [24242.258694] iwlwifi :01:00.0: Queue 10 is active on fifo 1 and stuck for 1 ms. SW [1, 13] HW [1, 13] FH TRB=0x0c010a000 Jul 4 14:27:23 orion kernel: [24242.259034] iwlwifi :01:00.0: Microcode SW error detected. Restarting 0x0. Jul 4 14:27:23 orion kernel: [24242.259226] iwlwifi :01:00.0: Start IWL Error Log Dump: Jul 4 14:27:23 orion kernel: [24242.259230] iwlwifi :01:00.0: Status: 0x0040, count: 6 Jul 4 14:27:23 orion kernel: [24242.259234] iwlwifi :01:00.0: Loaded firmware version: 46.6bf1df06.0 Jul 4 14:27:23 orion kernel: [24242.259238] iwlwifi :01:00.0: 0x0084 | NMI_INTERRUPT_UNKNOWN Jul 4 14:27:23 orion kernel: [24242.259241] iwlwifi :01:00.0: 0xA210 | trm_hw_status0 Jul 4 14:27:23 orion kernel: [24242.259243] iwlwifi :01:00.0: 0x | trm_hw_status1 Jul 4 14:27:23 orion kernel: [24242.259246] iwlwifi :01:00.0: 0x0048853E | branchlink2 Jul 4 14:27:23 orion kernel: [24242.259248] iwlwifi :01:00.0: 0x00479392 | interruptlink1 Jul 4 14:27:23 orion kernel: [24242.259251] iwlwifi :01:00.0: 0x00479392 | interruptlink2 Jul 4 14:27:23 orion kernel: [24242.259253] iwlwifi :01:00.0: 0x000111A2 | data1 Jul 4 14:27:23 orion kernel: [24242.259256] iwlwifi :01:00.0: 0xFF00 | data2 Jul 4 14:27:23 orion kernel: [24242.259258] iwlwifi :01:00.0: 0xF008 | data3 Jul 4 14:27:23 orion kernel: [24242.259260] iwlwifi :01:00.0: 0x1A417ECD | beacon time Jul 4 14:27:23 orion kernel: [24242.259263] iwlwifi :01:00.0: 0x66536102 | tsf low Jul 4 14:27:23 orion kernel: [24242.259265] iwlwifi :01:00.0: 0x0116 | tsf hi Jul 4 14:27:23 orion kernel: [24242.259268] iwlwifi :01:00.0: 0x | time gp1 Jul 4 14:27:23 orion kernel: [24242.259271] iwlwifi :01:00.0: 0x1238B516 | time gp2 Jul 4 14:27:23 orion kernel: [24242.259274] iwlwifi :01:00.0: 0x0001 | uCode revision type Jul 4 14:27:23 orion kernel: [24242.259278] iwlwifi :01:00.0: 0x002E | uCode version major Jul 4 14:27:23 orion kernel: [24242.259281] iwlwifi :01:00.0: 0x6BF1DF06 | uCode version minor Jul 4 14:27:23 orion kernel: [24242.259284] iwlwifi :01:00.0: 0x0321 | hw version Jul 4 14:27:23 orion kernel: [24242.259287] iwlwifi :01:00.0: 0x00C89004 | board version Jul 4 14:27:23 orion kernel: [24242.259289] iwlwifi :01:00.0: 0x001C019C | hcmd Jul 4 14:27:23 orion kernel: [24242.259292] iwlwifi :01:00.0: 0x24022000 | isr0 Jul 4 14:27:23 orion kernel: [24242.259295] iwlwifi :01:00.0: 0x | isr1 Jul 4 14:27:23 orion kernel: [24242.259298] iwlwifi :01:00.0: 0x08001802 | isr2 Jul 4 14:27:23 orion kernel: [24242.259301] iwlwifi :01:00.0: 0x004154C0 | isr3 Jul 4 14:27:23 orion kernel: [24242.259304] iwlwifi :01:00.0: 0x | isr4 Jul 4 14:27:23 orion kernel: [24242.259306] iwlwifi :01:00.0: 0x001C019C | last cmd Id Jul 4 14:27:23 orion kernel: [24242.259309] iwlwifi :01:00.0: 0x000111A2 | wait_event Jul 4 14:27:23 orion kernel: [24242.259312] iwlwifi :01:00.0: 0x0094 | l2p_control Jul 4 14:27:23 orion kernel: [24242.259315] iwlwifi :01:00.0: 0x00010034 | l2p_duration Jul 4 14:27:23 orion kernel: [24242.259318] iwlwifi :01:00.0: 0x000F | l2p_mhvalid Jul 4 14:27:23 orion kernel: [24242.259321] iwlwifi :01:00.0: 0x | l2p_addr_match Jul 4 14:27:23 orion kernel: [24242.259323] iwlwifi :01:00.0: 0x000D | lmpm_pmg_sel Jul 4 14:27:23 orion kernel: [24242.259326] iwlwifi :01:00.0: 0x08081424 | timestamp Jul 4 14:27:23 orion kernel: [24242.259329] iwlwifi :01:00.0: 0x983C | flow_handler Jul 4 14:27:23 orion kernel: [24242.259435] iwlwifi :01:00.0: Start IWL Error Log Dump: Jul 4 14:27:23 orion kernel: [24242.259438] iwlwifi :01:00.0: Status: 0x0040, count: 7 Jul 4 14:27:23 orion kernel: [24242.259441] iwlwifi :01:00.0: 0x2066 | NMI_INTERRUPT_HOST Jul 4 14:27:23 orion kernel: [24242.259443] iwlwifi :01:00.0: 0x | umac branchlink1 Jul 4 14:27:23 orion kernel: [24242.259445] iwlwifi :01:00.0: 0xC00E | umac branchlink2 Jul 4 14:27:23 orion kernel: [24242.259447] iwlwifi :01:00.0: 0xC0084414 | umac interruptlink1 Jul 4 14:27:23 orion kernel: [24242.259450] iwlwifi :01:00.0: 0xC0084414 | umac interruptlink2 Jul 4 14:27:23 orion kernel: [24242.259452] iwlwifi :01:00.0: 0x0100 | umac data1 Jul 4 14:27:23 orion kernel: [24242.259454] iwlwifi :01:00.0:
[Bug 1322968] Re: Changing country leads to invalid locale
Moving around between countries in Europe (UK <-> Belgium <-> France <-> Germany <-> Switzerland <-> Austria), I get all sorts of weird results for locales when I change the timezone from UK to anything else and back again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322968 Title: Changing country leads to invalid locale To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kde-runtime/+bug/1322968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] AlsaDevices.txt
apport information ** Attachment added: AlsaDevices.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489719/+files/AlsaDevices.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] Re: iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x82000008
apport information
** Tags added: apport-collected
** Description changed:
Having upgraded from Karmic to Lucid, the iwl3945 driver no longer works on
this laptop. Under karmic, perhaps every 1-2 days the wifi system would die
with a 'Microcode SW error'. The fix was to disable wifi, 'rmmod iwl3945',
suspend the laptop for some seconds, resume, re-load the iwl3945 module and
re-enable wireless.
Under Lucid, the wifi system dies immediately on boot and the former fix no
longer works. I've had a look at the various bugs of this sort in launchpad and
other places. This is definitely not related to heavy network loading - this
laptop has not been able to connect to wifi since I put Lucid on it this
morning.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-22-generic 2.6.32-22.33
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jon1832 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xefebc000 irq 21'
Mixer name : 'SigmaTel STAC9200'
Components : 'HDA:83847690,102801d6,00102201
HDA:14f12bfa,14f100c3,0009'
Controls : 12
Simple ctrls : 7
Date: Sun May 16 21:04:06 2010
HibernationDevice: RESUME=UUID=6f3da75c-ec03-4f2e-b552-ae1b75cb9eee
InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100427.1)
MachineType: Dell Inc. Latitude D420
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-22-generic root=/dev/mapper/foo-home
ro quiet splash
ProcEnviron:
LANG=en_GB.utf8
SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34
SourcePackage: linux
dmi.bios.date: 02/02/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 0YJ387
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA06:bd02/02/2008:svnDellInc.:pnLatitudeD420:pvr:rvnDellInc.:rn0YJ387:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude D420
dmi.sys.vendor: Dell Inc.
+ ---
+ AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
+ Architecture: i386
+ ArecordDevices:
+ List of CAPTURE Hardware Devices
+ card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
+Subdevices: 1/1
+Subdevice #0: subdevice #0
+ AudioDevicesInUse:
+ Cannot stat file /proc/2956/fd/35: Stale NFS file handle
+ Cannot stat file /proc/2956/fd/40: Stale NFS file handle
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: ubuntu 2964 F pulseaudio
+ CRDA: Error: [Errno 2] No such file or directory
+ Card0.Amixer.info:
+ Card hw:0 'Intel'/'HDA Intel at 0xefebc000 irq 44'
+Mixer name : 'SigmaTel STAC9200'
+Components : 'HDA:83847690,102801d6,00102201
HDA:14f12bfa,14f100c3,0009'
+Controls : 12
+Simple ctrls : 7
+ DistroRelease: Ubuntu 10.10
+ LiveMediaBuild: Ubuntu 10.10 Maverick Meerkat - Alpha i386 (20100803.1)
+ MachineType: Dell Inc. Latitude D420
+ Package: linux (not installed)
+ PccardctlIdent:
+ Socket 0:
+no product info available
+ PccardctlStatus:
+ Socket 0:
+no card
+ ProcCmdLine: file=/cdrom/preseed/hostname.seed boot=casper
initrd=/casper/initrd.lz quiet splash --
+ ProcEnviron:
+ LANG=en_US.UTF-8
+ SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 2.6.35-14.19-generic 2.6.35
+ Regression: No
+ RelatedPackageVersions: linux-firmware 1.37
+ Reproducible: Yes
+ Tags: maverick networking needs-upstream-testing
+ Uname: Linux 2.6.35-14-generic i686
+ UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
+ dmi.bios.date: 02/02/2008
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: A06
+ dmi.board.name: 0YJ387
+ dmi.board.vendor: Dell Inc.
+ dmi.chassis.type: 8
+ dmi.chassis.vendor: Dell Inc.
+ dmi.modalias:
dmi:bvnDellInc.:bvrA06:bd02/02/2008:svnDellInc.:pnLatitudeD420:pvr:rvnDellInc.:rn0YJ387:rvr:cvnDellInc.:ct8:cvr:
+ dmi.product.name: Latitude D420
+ dmi.sys.vendor: Dell Inc.
** Attachment added: AcpiTables.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489718/+files/AcpiTables.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
https://bugs.launchpad.net/bugs/581441
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
[Bug 581441] AplayDevices.txt
apport information ** Attachment added: AplayDevices.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489720/+files/AplayDevices.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] BootDmesg.txt
apport information ** Attachment added: BootDmesg.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489721/+files/BootDmesg.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] Card0.Codecs.codec.0.txt
apport information ** Attachment added: Card0.Codecs.codec.0.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489723/+files/Card0.Codecs.codec.0.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] Card0.Amixer.values.txt
apport information ** Attachment added: Card0.Amixer.values.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489722/+files/Card0.Amixer.values.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] Card0.Codecs.codec.1.txt
apport information ** Attachment added: Card0.Codecs.codec.1.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489724/+files/Card0.Codecs.codec.1.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489725/+files/CurrentDmesg.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] IwConfig.txt
apport information ** Attachment added: IwConfig.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489726/+files/IwConfig.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489727/+files/Lspci.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489728/+files/Lsusb.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489731/+files/ProcInterrupts.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] PciMultimedia.txt
apport information ** Attachment added: PciMultimedia.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489729/+files/PciMultimedia.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489730/+files/ProcCpuinfo.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489732/+files/ProcModules.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] RfKill.txt
apport information ** Attachment added: RfKill.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489733/+files/RfKill.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489735/+files/UdevLog.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489734/+files/UdevDb.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] Re: iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x82000008
I just booted this laptop off the Maverick Alpha 3 CDROM and left it while I went shopping. Firefox was running with a page loaded which refreshed every 5 minutes or so and nothing else. The output of dmesg shows that this problem still occurs. -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] WifiSyslog.txt
apport information ** Attachment added: WifiSyslog.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489736/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Expired = New -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] Re: iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x82000008
apport information
** Description changed:
Having upgraded from Karmic to Lucid, the iwl3945 driver no longer works on
this laptop. Under karmic, perhaps every 1-2 days the wifi system would die
with a 'Microcode SW error'. The fix was to disable wifi, 'rmmod iwl3945',
suspend the laptop for some seconds, resume, re-load the iwl3945 module and
re-enable wireless.
Under Lucid, the wifi system dies immediately on boot and the former fix no
longer works. I've had a look at the various bugs of this sort in launchpad and
other places. This is definitely not related to heavy network loading - this
laptop has not been able to connect to wifi since I put Lucid on it this
morning.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-22-generic 2.6.32-22.33
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jon1832 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xefebc000 irq 21'
Mixer name : 'SigmaTel STAC9200'
Components : 'HDA:83847690,102801d6,00102201
HDA:14f12bfa,14f100c3,0009'
Controls : 12
Simple ctrls : 7
Date: Sun May 16 21:04:06 2010
HibernationDevice: RESUME=UUID=6f3da75c-ec03-4f2e-b552-ae1b75cb9eee
InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100427.1)
MachineType: Dell Inc. Latitude D420
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-22-generic root=/dev/mapper/foo-home
ro quiet splash
ProcEnviron:
LANG=en_GB.utf8
SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34
SourcePackage: linux
dmi.bios.date: 02/02/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 0YJ387
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA06:bd02/02/2008:svnDellInc.:pnLatitudeD420:pvr:rvnDellInc.:rn0YJ387:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude D420
dmi.sys.vendor: Dell Inc.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
Cannot stat file /proc/2956/fd/35: Stale NFS file handle
Cannot stat file /proc/2956/fd/40: Stale NFS file handle
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 2964 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xefebc000 irq 44'
Mixer name : 'SigmaTel STAC9200'
Components : 'HDA:83847690,102801d6,00102201
HDA:14f12bfa,14f100c3,0009'
Controls : 12
Simple ctrls : 7
DistroRelease: Ubuntu 10.10
LiveMediaBuild: Ubuntu 10.10 Maverick Meerkat - Alpha i386 (20100803.1)
MachineType: Dell Inc. Latitude D420
Package: linux (not installed)
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdLine: file=/cdrom/preseed/hostname.seed boot=casper
initrd=/casper/initrd.lz quiet splash --
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.35-14.19-generic 2.6.35
Regression: No
RelatedPackageVersions: linux-firmware 1.37
Reproducible: Yes
Tags: maverick networking needs-upstream-testing
Uname: Linux 2.6.35-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 02/02/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 0YJ387
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA06:bd02/02/2008:svnDellInc.:pnLatitudeD420:pvr:rvnDellInc.:rn0YJ387:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude D420
dmi.sys.vendor: Dell Inc.
+
+ ---
+ AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
+ Architecture: i386
+ ArecordDevices:
+ List of CAPTURE Hardware Devices
+ card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
+Subdevices: 1/1
+Subdevice #0: subdevice #0
+ AudioDevicesInUse:
+ Cannot stat file /proc/2956/fd/34: Stale NFS file handle
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: ubuntu 2964 F
[Bug 581441] AlsaDevices.txt
apport information ** Attachment added: AlsaDevices.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489799/+files/AlsaDevices.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] AplayDevices.txt
apport information ** Attachment added: AplayDevices.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489800/+files/AplayDevices.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] BootDmesg.txt
apport information ** Attachment added: BootDmesg.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489801/+files/BootDmesg.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] Card0.Amixer.values.txt
apport information ** Attachment added: Card0.Amixer.values.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489802/+files/Card0.Amixer.values.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] Card0.Codecs.codec.0.txt
apport information ** Attachment added: Card0.Codecs.codec.0.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489804/+files/Card0.Codecs.codec.0.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] Card0.Codecs.codec.1.txt
apport information ** Attachment added: Card0.Codecs.codec.1.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489805/+files/Card0.Codecs.codec.1.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489806/+files/CurrentDmesg.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] IwConfig.txt
apport information ** Attachment added: IwConfig.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489807/+files/IwConfig.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489808/+files/Lspci.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489809/+files/Lsusb.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] PciMultimedia.txt
apport information ** Attachment added: PciMultimedia.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489810/+files/PciMultimedia.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489812/+files/ProcInterrupts.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489811/+files/ProcCpuinfo.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489815/+files/UdevDb.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489816/+files/UdevLog.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489813/+files/ProcModules.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] WifiSyslog.txt
apport information ** Attachment added: WifiSyslog.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489817/+files/WifiSyslog.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] RfKill.txt
apport information ** Attachment added: RfKill.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489814/+files/RfKill.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] Re: iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x82000008
And here's a second example of the problem running from the Maverick Alpha 3 CDROM. I just rebooted the machine after the previous example and left it to go and have lunch. When I came back, the problem had happened. -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] Re: iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x82000008
apport information
** Description changed:
Having upgraded from Karmic to Lucid, the iwl3945 driver no longer works on
this laptop. Under karmic, perhaps every 1-2 days the wifi system would die
with a 'Microcode SW error'. The fix was to disable wifi, 'rmmod iwl3945',
suspend the laptop for some seconds, resume, re-load the iwl3945 module and
re-enable wireless.
Under Lucid, the wifi system dies immediately on boot and the former fix no
longer works. I've had a look at the various bugs of this sort in launchpad and
other places. This is definitely not related to heavy network loading - this
laptop has not been able to connect to wifi since I put Lucid on it this
morning.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-22-generic 2.6.32-22.33
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jon1832 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xefebc000 irq 21'
Mixer name : 'SigmaTel STAC9200'
Components : 'HDA:83847690,102801d6,00102201
HDA:14f12bfa,14f100c3,0009'
Controls : 12
Simple ctrls : 7
Date: Sun May 16 21:04:06 2010
HibernationDevice: RESUME=UUID=6f3da75c-ec03-4f2e-b552-ae1b75cb9eee
InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100427.1)
MachineType: Dell Inc. Latitude D420
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-22-generic root=/dev/mapper/foo-home
ro quiet splash
ProcEnviron:
LANG=en_GB.utf8
SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34
SourcePackage: linux
dmi.bios.date: 02/02/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 0YJ387
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA06:bd02/02/2008:svnDellInc.:pnLatitudeD420:pvr:rvnDellInc.:rn0YJ387:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude D420
dmi.sys.vendor: Dell Inc.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
Cannot stat file /proc/2956/fd/35: Stale NFS file handle
Cannot stat file /proc/2956/fd/40: Stale NFS file handle
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 2964 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xefebc000 irq 44'
Mixer name : 'SigmaTel STAC9200'
Components : 'HDA:83847690,102801d6,00102201
HDA:14f12bfa,14f100c3,0009'
Controls : 12
Simple ctrls : 7
DistroRelease: Ubuntu 10.10
LiveMediaBuild: Ubuntu 10.10 Maverick Meerkat - Alpha i386 (20100803.1)
MachineType: Dell Inc. Latitude D420
Package: linux (not installed)
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdLine: file=/cdrom/preseed/hostname.seed boot=casper
initrd=/casper/initrd.lz quiet splash --
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.35-14.19-generic 2.6.35
Regression: No
RelatedPackageVersions: linux-firmware 1.37
Reproducible: Yes
Tags: maverick networking needs-upstream-testing
Uname: Linux 2.6.35-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 02/02/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 0YJ387
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA06:bd02/02/2008:svnDellInc.:pnLatitudeD420:pvr:rvnDellInc.:rn0YJ387:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude D420
dmi.sys.vendor: Dell Inc.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
Cannot stat file /proc/2956/fd/34: Stale NFS file handle
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 2964 F
[Bug 581441] AlsaDevices.txt
apport information ** Attachment added: AlsaDevices.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489835/+files/AlsaDevices.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] AplayDevices.txt
apport information ** Attachment added: AplayDevices.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489836/+files/AplayDevices.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] BootDmesg.txt
apport information ** Attachment added: BootDmesg.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489837/+files/BootDmesg.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] Card0.Amixer.values.txt
apport information ** Attachment added: Card0.Amixer.values.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489838/+files/Card0.Amixer.values.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] Card0.Codecs.codec.0.txt
apport information ** Attachment added: Card0.Codecs.codec.0.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489839/+files/Card0.Codecs.codec.0.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489841/+files/CurrentDmesg.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] Card0.Codecs.codec.1.txt
apport information ** Attachment added: Card0.Codecs.codec.1.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489840/+files/Card0.Codecs.codec.1.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489844/+files/Lsusb.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] IwConfig.txt
apport information ** Attachment added: IwConfig.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489842/+files/IwConfig.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489843/+files/Lspci.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489846/+files/ProcCpuinfo.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] PciMultimedia.txt
apport information ** Attachment added: PciMultimedia.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489845/+files/PciMultimedia.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489847/+files/ProcInterrupts.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489848/+files/ProcModules.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] RfKill.txt
apport information ** Attachment added: RfKill.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489849/+files/RfKill.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489851/+files/UdevLog.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] WifiSyslog.txt
apport information ** Attachment added: WifiSyslog.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489852/+files/WifiSyslog.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] Re: iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x82000008
And the same again - I've booted Maverick Alpha 3 times on this machine and each time this happens. In this case before the boot process has really completed. -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489850/+files/UdevDb.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581633] Re: boot fails due to null pointer dereference in drm/radeon
** Changed in: linux (Ubuntu) Status: Incomplete = New -- boot fails due to null pointer dereference in drm/radeon https://bugs.launchpad.net/bugs/581633 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 258446] Re: JMicron internal card reader recognizes SD only when inserted at startup
I'm seeing this exact problem with Lucid on an Aspire One AOA 150Ab and an SD card. A variant on #61 works for me - I only needed #1 and #2. -- JMicron internal card reader recognizes SD only when inserted at startup https://bugs.launchpad.net/bugs/258446 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] Re: iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x82000008
** Attachment added: Here's another log file extract showing this bug. http://launchpadlibrarian.net/49160507/launchpad_581441.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] Re: iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x82000008
I've tried linux-image-2.6.33-02063304-generic and linux-image-2.6.34-020634-generic as well as getting more experience with the standard lucid kernel. The behaviour of all 3 is closer to the karmic behaviour - perhaps every 1-2 days the wifi system would die with a 'Microcode SW error'. The fix which worked for karmic of disabling wifi, unloading the iwl3945 module, suspending the laptop, waiting 10-20 seconds, resuming the laptop and reloading the iwl3945 module doesn't work as often as it worked with karmic but works more than I first feared. With linux-image-2.6.33-02063304-generic, there's less log information captured than with karmic. What happens is an error from wpa_supplicant as followsl May 23 18:35:06 cameron wpa_supplicant[947]: Failed to initiate AP scan. May 23 18:36:13 cameron wpa_supplicant[947]: last message repeated 6 times May 23 18:37:13 cameron wpa_supplicant[947]: last message repeated 6 times May 23 18:38:13 cameron wpa_supplicant[947]: last message repeated 6 times May 23 18:39:13 cameron wpa_supplicant[947]: last message repeated 6 times The network connection stays working for some time and doesn't die immediately. With linux-image-2.6.34-020634-generic, there's more logging information and I've just captured the following. May 23 17:31:03 cameron kernel: [26917.748945] iwl3945 :0c:00.0: Microcode SW error detected. Restarting 0x8208. May 23 17:31:03 cameron kernel: [26917.748989] iwl3945 :0c:00.0: Start IWL Error Log Dump: May 23 17:31:03 cameron kernel: [26917.748997] iwl3945 :0c:00.0: Status: 0x0002A2E4, count: 1 May 23 17:31:03 cameron kernel: [26917.749004] iwl3945 :0c:00.0: Desc Time asrtPC blink2 ilink1 nmiPC Line May 23 17:31:03 cameron kernel: [26917.749239] iwl3945 :0c:00.0: SYSASSERT (#5) 0903237322 0x008B6 0x00274 0x00320 0x007FE 116 May 23 17:31:03 cameron kernel: [26917.749243] May 23 17:31:03 cameron kernel: [26917.749376] iwl3945 :0c:00.0: Start IWL Event Log Dump: display last 20 count May 23 17:31:03 cameron kernel: [26917.749424] iwl3945 :0c:00.0: 09032372300x 0302 May 23 17:31:03 cameron kernel: [26917.749451] iwl3945 :0c:00.0: 09032372390x8000 0350 May 23 17:31:03 cameron kernel: [26917.749479] iwl3945 :0c:00.0: 09032372440x00d9 0106 May 23 17:31:03 cameron kernel: [26917.749507] iwl3945 :0c:00.0: 09032372450x 0302 May 23 17:31:03 cameron kernel: [26917.749534] iwl3945 :0c:00.0: 09032372540x8000 0350 May 23 17:31:03 cameron kernel: [26917.749562] iwl3945 :0c:00.0: 09032372590x00d9 0106 May 23 17:31:03 cameron kernel: [26917.749589] iwl3945 :0c:00.0: 09032372610x 0302 May 23 17:31:03 cameron kernel: [26917.749617] iwl3945 :0c:00.0: 09032372690x8000 0350 May 23 17:31:03 cameron kernel: [26917.749644] iwl3945 :0c:00.0: 09032372740x00d9 0106 May 23 17:31:03 cameron kernel: [26917.749672] iwl3945 :0c:00.0: 09032372760x 0302 May 23 17:31:03 cameron kernel: [26917.749699] iwl3945 :0c:00.0: 09032372840x8000 0350 May 23 17:31:03 cameron kernel: [26917.749727] iwl3945 :0c:00.0: 09032372890x00d9 0106 May 23 17:31:03 cameron kernel: [26917.749754] iwl3945 :0c:00.0: 09032372910x 0302 May 23 17:31:03 cameron kernel: [26917.749782] iwl3945 :0c:00.0: 09032372990x8000 0350 May 23 17:31:03 cameron kernel: [26917.749809] iwl3945 :0c:00.0: 09032373040x00d9 0106 May 23 17:31:03 cameron kernel: [26917.749837] iwl3945 :0c:00.0: 09032373060x 0302 May 23 17:31:03 cameron kernel: [26917.749865] iwl3945 :0c:00.0: 09032373140x8000 0350 May 23 17:31:03 cameron kernel: [26917.749892] iwl3945 :0c:00.0: 09032373190x00d9 0106 May 23 17:31:03 cameron kernel: [26917.749920] iwl3945 :0c:00.0: 09032373200x0002 0123 May 23 17:31:03 cameron kernel: [26917.749947] iwl3945 :0c:00.0: 09032373230x0100 0125 May 23 17:31:03 cameron kernel: [26917.749977] iwl3945 :0c:00.0: Error Reply type 0x0005 cmd REPLY_TX (0x1C) seq 0x ser 0x0074 May 23 17:31:03 cameron kernel: [26917.754566] iwl3945 :0c:00.0: Can't stop Rx DMA. May 23 17:31:34 cameron wpa_supplicant[947]: Failed to initiate AP scan. May 23 17:32:40 cameron wpa_supplicant[947]: last message repeated 6 times May 23 17:33:40 cameron wpa_supplicant[947]: last message repeated 6 times May 23 17:34:40 cameron wpa_supplicant[947]: last message repeated 6 times May 23 17:35:01 cameron wpa_supplicant[947]: last message repeated 2 times To be clear, there may be more than one problem here. With Karmic, the Can't stop Rx DMA error message didn't happen all the times when wifi access died. ** Tags removed: needs-upstream-testing -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208
[Bug 581633] Re: boot fails due to null pointer dereference in drm/radeon
I've tried two upstream kernels - linux-image-2.6.33-02063304-generic and linux-image-2.6.34-020634-generic. Neither of these boots far enough to reproduce this problem due to a bug in the dc395x driver. ** Tags removed: needs-upstream-testing -- boot fails due to null pointer dereference in drm/radeon https://bugs.launchpad.net/bugs/581633 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581633] [NEW] boot fails due to null pointer dereference in drm/radeon
Public bug reported: 9 times out of 10 on this PC, the boot process fails with a null pointer dereference in DRM. It boots as far as a login prompt and I can login but the whole system hangs within a few minutes. This sounds extremely similar to 549476 however I was asked to open a new bug rather than re-open that one. Adding nomodeset to the boot parameters makes the boot process complete successfully however the splash screen while booting is shown at a strange, low resolution and prompts for passwords aren't really visible. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: linux-image-2.6.32-22-generic 2.6.32-22.33 Regression: Yes Reproducible: Yes ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic i686 AlsaDevices: total 0 crw-rw+ 1 root audio 116, 3 2010-05-17 10:10 seq crw-rw+ 1 root audio 116, 2 2010-05-17 10:10 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. AplayDevices: aplay: device_list:223: no soundcards found... Architecture: i386 ArecordDevices: arecord: device_list:223: no soundcards found... AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer', '/dev/sequencer2', '/dev/sequencer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [ 27.944009] eth0: no IPv6 routers present Date: Mon May 17 10:11:13 2010 HibernationDevice: RESUME=UUID=e88460fc-5821-40f5-8432-0722907d6bdc InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: System Manufacturer System Name ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=3a460971-de45-41dc-875a-e13aafe4a2fc ro quiet splash ProcEnviron: SHELL=/bin/bash LANG=en_GB.UTF-8 RelatedPackageVersions: linux-firmware 1.34 RfKill: SourcePackage: linux dmi.bios.date: 04/17/2002 dmi.bios.vendor: Award Software, Inc. dmi.bios.version: ASUS A7V333 ACPI BIOS Revision 1006 dmi.board.name: A7V333 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: REV 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 7 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAwardSoftware,Inc.:bvrASUSA7V333ACPIBIOSRevision1006:bd04/17/2002:svnSystemManufacturer:pnSystemName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnA7V333:rvrREV1.xx:cvnChassisManufacture:ct7:cvrChassisVersion: dmi.product.name: System Name dmi.product.version: System Version dmi.sys.vendor: System Manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug graphics i386 lucid needs-upstream-testing regression-release -- boot fails due to null pointer dereference in drm/radeon https://bugs.launchpad.net/bugs/581633 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581633] Re: boot fails due to null pointer dereference in drm/radeon
** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/48594337/BootDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/48594338/Dependencies.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/48594339/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/48594340/Lsusb.txt ** Attachment added: PciMultimedia.txt http://launchpadlibrarian.net/48594341/PciMultimedia.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/48594342/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/48594343/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/48594344/ProcModules.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/48594345/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/48594346/UdevLog.txt ** Attachment added: WifiSyslog.txt http://launchpadlibrarian.net/48594347/WifiSyslog.txt -- boot fails due to null pointer dereference in drm/radeon https://bugs.launchpad.net/bugs/581633 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 464712] Re: Black screen + freeze when suspending or hibernating with mounted SD Card
I see this in Lucid on my Dell D420. -- Black screen + freeze when suspending or hibernating with mounted SD Card https://bugs.launchpad.net/bugs/464712 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] [NEW] iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x82000008
Public bug reported: Having upgraded from Karmic to Lucid, the iwl3945 driver no longer works on this laptop. Under karmic, perhaps every 1-2 days the wifi system would die with a 'Microcode SW error'. The fix was to disable wifi, 'rmmod iwl3945', suspend the laptop for some seconds, resume, re-load the iwl3945 module and re-enable wireless. Under Lucid, the wifi system dies immediately on boot and the former fix no longer works. I've had a look at the various bugs of this sort in launchpad and other places. This is definitely not related to heavy network loading - this laptop has not been able to connect to wifi since I put Lucid on it this morning. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: linux-image-2.6.32-22-generic 2.6.32-22.33 Regression: Yes Reproducible: Yes ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jon1832 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xefebc000 irq 21' Mixer name : 'SigmaTel STAC9200' Components : 'HDA:83847690,102801d6,00102201 HDA:14f12bfa,14f100c3,0009' Controls : 12 Simple ctrls : 7 Date: Sun May 16 21:04:06 2010 HibernationDevice: RESUME=UUID=6f3da75c-ec03-4f2e-b552-ae1b75cb9eee InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100427.1) MachineType: Dell Inc. Latitude D420 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-22-generic root=/dev/mapper/foo-home ro quiet splash ProcEnviron: LANG=en_GB.utf8 SHELL=/bin/bash RelatedPackageVersions: linux-firmware 1.34 SourcePackage: linux dmi.bios.date: 02/02/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0YJ387 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd02/02/2008:svnDellInc.:pnLatitudeD420:pvr:rvnDellInc.:rn0YJ387:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D420 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid needs-upstream-testing networking regression-release -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581441] Re: iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x82000008
** Attachment added: AlsaDevices.txt http://launchpadlibrarian.net/48570565/AlsaDevices.txt ** Attachment added: AplayDevices.txt http://launchpadlibrarian.net/48570566/AplayDevices.txt ** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/48570567/BootDmesg.txt ** Attachment added: Card0.Amixer.values.txt http://launchpadlibrarian.net/48570568/Card0.Amixer.values.txt ** Attachment added: Card0.Codecs.codec.0.txt http://launchpadlibrarian.net/48570569/Card0.Codecs.codec.0.txt ** Attachment added: Card0.Codecs.codec.1.txt http://launchpadlibrarian.net/48570570/Card0.Codecs.codec.1.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/48570571/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/48570572/Dependencies.txt ** Attachment added: IwConfig.txt http://launchpadlibrarian.net/48570573/IwConfig.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/48570574/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/48570575/Lsusb.txt ** Attachment added: PciMultimedia.txt http://launchpadlibrarian.net/48570576/PciMultimedia.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/48570577/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/48570578/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/48570579/ProcModules.txt ** Attachment added: RfKill.txt http://launchpadlibrarian.net/48570580/RfKill.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/48570581/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/48570582/UdevLog.txt ** Attachment added: WifiSyslog.txt http://launchpadlibrarian.net/48570583/WifiSyslog.txt -- iwl3945: immediately after boot goes into loop of Microcode SW error detected. Restarting 0x8208 https://bugs.launchpad.net/bugs/581441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 549476] Re: [r100 drm] BUG: unable to handle kernel NULL pointer dereference in r100_get_accessible_vram
I get this bug with a brand new install of the Karmic release CD. ** Changed in: linux (Ubuntu) Status: Invalid = New -- [r100 drm] BUG: unable to handle kernel NULL pointer dereference in r100_get_accessible_vram https://bugs.launchpad.net/bugs/549476 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 549476] Re: [r100 drm] BUG: unable to handle kernel NULL pointer dereference in r100_get_accessible_vram
Here is the kern.log file. ** Attachment added: kern.log http://launchpadlibrarian.net/47217931/kern.log -- [r100 drm] BUG: unable to handle kernel NULL pointer dereference in r100_get_accessible_vram https://bugs.launchpad.net/bugs/549476 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 468298] [NEW] suspend to RAM crash when SD card filesystem mounted
Public bug reported: Binary package hint: pm-utils Just installed karmic on this laptop. Now if I suspend to RAM with the SD card mounted, the system just hangs some way down in the process. It's 100% reproducible in my tests so far. It worked fine in previous releases. It works fine if I unmount the card (but leave it in the slot). ProblemType: Bug Architecture: i386 Date: Sun Nov 1 10:53:49 2009 DistroRelease: Ubuntu 9.10 Package: pm-utils 1.2.5-2ubuntu7 PackageArchitecture: all ProcEnviron: LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: pm-utils Uname: Linux 2.6.31-14-generic i686 ** Affects: pm-utils (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- suspend to RAM crash when SD card filesystem mounted https://bugs.launchpad.net/bugs/468298 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 468298] Re: suspend to RAM crash when SD card filesystem mounted
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/34854104/Dependencies.txt ** Attachment added: XsessionErrors.txt http://launchpadlibrarian.net/34854105/XsessionErrors.txt -- suspend to RAM crash when SD card filesystem mounted https://bugs.launchpad.net/bugs/468298 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 468298] Re: suspend to RAM crash when SD card filesystem mounted
** Attachment added: output of lspci -vvnn http://launchpadlibrarian.net/34854420/lspci_vvnn -- suspend to RAM crash when SD card filesystem mounted https://bugs.launchpad.net/bugs/468298 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 468298] Re: suspend to RAM crash when SD card filesystem mounted
I've tried the instructions in the DebuggingKernelSuspendHibernateResume wiki under Suspending from text mode. The system hangs when I do pm- suspend but no output is printed. -- suspend to RAM crash when SD card filesystem mounted https://bugs.launchpad.net/bugs/468298 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 385830] Re: logout on resume from suspend
*** This bug is a duplicate of bug 347587 *** https://bugs.launchpad.net/bugs/347587 While digging around, I found that when I'm logged out, a logfile is generated in /var/log/gdm which finishes with the following; X: ../../src/i830_batchbuffer.h:78: intel_batch_emit_dword: Assertion `pI830-ba tch_ptr != ((void *)0)' failed. -- logout on resume from suspend https://bugs.launchpad.net/bugs/385830 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 385830] Re: logout on resume from suspend
*** This bug is a duplicate of bug 347587 *** https://bugs.launchpad.net/bugs/347587 ** This bug has been marked a duplicate of bug 347587 [i4500MHD] Kubuntu: X asserts on pI830-batch_ptr != 0 on resume from suspend (UXA bug) -- logout on resume from suspend https://bugs.launchpad.net/bugs/385830 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 347587] Re: [i4500MHD] Kubuntu: X asserts on pI830-batch_ptr != 0 on resume from suspend (UXA bug)
Is there any chance of a Jaunty version of this fix appearing in x-updates? -- [i4500MHD] Kubuntu: X asserts on pI830-batch_ptr != 0 on resume from suspend (UXA bug) https://bugs.launchpad.net/bugs/347587 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 384730] Re: [i945GM] screen goes black about once per day after upgrading to latest intel drivers
I've removed both UXA and virtual from Xorg.conf and I'm seeing if the problems re-occur. So far they haven't but I'll need to give it more time to be confident. Also https://bugs.launchpad.net/bugs/385830 hasn't re-occurred either (logout on resume from suspend). -- [i945GM] screen goes black about once per day after upgrading to latest intel drivers https://bugs.launchpad.net/bugs/384730 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 385830] [NEW] logout on resume from suspend
Public bug reported: Sometimes when I resume from suspend, there's a long wait and then I get the login screen and everything which was there when I suspended is lost. I've not managed to find a reproducible set of circumstances for the first occurence of the problem after a reboot however once it's happened once, it does seem to happen much more often and the only way to fix this is to reboot. This is on a Dell Latitude D420 with Jaunty. The X/Intel driver has been updated to version 2.7.1 from x-updates in order to get dual-screen to work (see https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/379805). Some other packages were updated while debugging this which may have impacted this issue. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- logout on resume from suspend https://bugs.launchpad.net/bugs/385830 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 384730] Re: [i945GM] screen goes black about once per day after upgrading to latest intel drivers
Ctrl+Alt+F1 does indeed add a drmDropMaster line each time I switch to a VT. ** Attachment added: Xorg.0.log showing switch to VT and return http://launchpadlibrarian.net/27769425/Xorg.0.log -- [i945GM] screen goes black about once per day after upgrading to latest intel drivers https://bugs.launchpad.net/bugs/384730 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 384730] Re: [i945GM] screen goes black about once per day after upgrading to latest intel drivers
The black screen just happened again. Ctrl+Alt+F1 / Ctrl+Alt+F7 works to repeatedly switch between the VT and the black screen. The drmDropMaster line is added each time. Attached is a copy of Xorg.log.0 taken after a Ctrl+Alt+F1. It turns out that suspend / resume clears the problem until the next time (where suspend = Fn+Esc on this laptop). ** Attachment added: Xorg.0.log.blank.screen http://launchpadlibrarian.net/27771701/Xorg.0.log.blank.screen -- [i945GM] screen goes black about once per day after upgrading to latest intel drivers https://bugs.launchpad.net/bugs/384730 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 384730] [NEW] screen goes black about once per day after upgrading to latest intel drivers
Public bug reported: Binary package hint: xserver-xorg-video-intel I was advised to upgrade to version 2.7.1 of the intel drivers from x-updates in order to get dual-screen to work (see https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/379805). Since then, about once per day, the screen just goes completely black. Control+Alt+F1 gets me a command line but nothing makes X work again except for rebooting. What appears in syslog when this happens is; Jun 8 08:58:17 cameron kernel: [41066.989758] [drm:i915_setparam] *ERROR* unknown parameter 4 Jun 8 08:58:17 cameron kernel: [41066.989789] [drm:i915_getparam] *ERROR* Unknown parameter 6 Jun 8 08:58:18 cameron kernel: [41068.145609] [drm:i915_getparam] *ERROR* Unknown parameter 6 Jun 8 08:58:26 cameron kernel: [41075.594275] [drm:i915_get_vblank_counter] *ERROR* trying to get vblank count for disabled pipe 0 The files automatically attached by ubuntu-bug are *after* a reboot. Manually attached are copies of some of the files taken before the reboot. There are quite a few hits when I google for the last entry in syslog. This sounds a little like 305227 but that goes pack to 8.10 and this is extremely recent. This problem did not happen with vanilla jaunty - only after after installing 2.7.1. Of course various other package updates were installed while trying to solve the problems with 379805 and it could be one of them. I apologise if this is not the correct package to report this bug against. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 Package: xserver-xorg-video-intel 2:2.7.1-0ubuntu1~xup~1 ProcEnviron: LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersion: Linux version 2.6.28-11-generic (bui...@palmer) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 SourcePackage: xserver-xorg-video-intel Uname: Linux 2.6.28-11-generic i686 UnreportableReason: This is not a genuine Ubuntu package ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- screen goes black about once per day after upgrading to latest intel drivers https://bugs.launchpad.net/bugs/384730 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 384730] Re: screen goes black about once per day after upgrading to latest intel drivers
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/27638166/Dependencies.txt ** Attachment added: LsHal.txt http://launchpadlibrarian.net/27638167/LsHal.txt ** Attachment added: LsMod.txt http://launchpadlibrarian.net/27638168/LsMod.txt ** Attachment added: LsPci.txt http://launchpadlibrarian.net/27638169/LsPci.txt ** Attachment added: XorgConf.txt http://launchpadlibrarian.net/27638171/XorgConf.txt ** Attachment added: XorgLog.gz http://launchpadlibrarian.net/27638172/XorgLog.gz ** Attachment added: XorgLogOld.gz http://launchpadlibrarian.net/27638173/XorgLogOld.gz ** Attachment added: Xrandr.txt http://launchpadlibrarian.net/27638174/Xrandr.txt ** Attachment added: glxinfo.txt http://launchpadlibrarian.net/27638175/glxinfo.txt ** Attachment added: monitors.xml.txt http://launchpadlibrarian.net/27638176/monitors.xml.txt ** Attachment added: setxkbmap.txt http://launchpadlibrarian.net/27638177/setxkbmap.txt ** Attachment added: system.txt http://launchpadlibrarian.net/27638178/system.txt ** Attachment added: xdpyinfo.txt http://launchpadlibrarian.net/27638179/xdpyinfo.txt ** Attachment added: xkbcomp.txt http://launchpadlibrarian.net/27638180/xkbcomp.txt -- screen goes black about once per day after upgrading to latest intel drivers https://bugs.launchpad.net/bugs/384730 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 384730] Re: screen goes black about once per day after upgrading to latest intel drivers
** Attachment added: The last 200 lines of syslog after the screen goes black before reboot http://launchpadlibrarian.net/27638201/syslog -- screen goes black about once per day after upgrading to latest intel drivers https://bugs.launchpad.net/bugs/384730 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 384730] Re: screen goes black about once per day after upgrading to latest intel drivers
** Attachment added: Xorg.0.log - after the screen went black before reboot http://launchpadlibrarian.net/27638215/Xorg.0.log -- screen goes black about once per day after upgrading to latest intel drivers https://bugs.launchpad.net/bugs/384730 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379805] Re: [i945gm] virtual 2048 in xorg.conf causes blank white screen on login
Sorry for the delay in replying - work's been rather busy. Switching to UXA solves this problem. The white screen is gone! Dual screen behaves as expected. Unfortunately somewhere in the set of updates which got installed something else broke. About once per day, the entire screen just goes black and a reboot is required. Next time it happens and I can login remotely to the laptop, I'll open that as a new bug in launchpad. -- [i945gm] virtual 2048 in xorg.conf causes blank white screen on login https://bugs.launchpad.net/bugs/379805 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379805] Re: [i945gm] virtual 2048 in xorg.conf causes blank white screen on login
Where should I find a suitable version of xorg-xserver-video-intel-dbg? As far as I can see, it's not in regular jaunty, jaunty-proposed or the x-swat PPA. The laptop is a Dell Latitude D420. -- [i945gm] virtual 2048 in xorg.conf causes blank white screen on login https://bugs.launchpad.net/bugs/379805 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379805] Re: [i945gm] virtual 2048 in xorg.conf causes blank white screen on login
I've managed to resolve the partially installed package problem. As part of this, I've ended up running the kernel from jaunty-proposed. Version 2.7.1 shows the same problem - a white screen after login. I've checked both with and without an external screen connected. I've attached the Xorg.0.log files with version 2.7.1, both working (without virtual) and non-working (with virtual). Please let me know if other information should be updated now 2.7.1 is installed. ** Attachment added: Log with version 2.7.1 - working http://launchpadlibrarian.net/27168409/Xorg.0.log -- [i945gm] virtual 2048 in xorg.conf causes blank white screen on login https://bugs.launchpad.net/bugs/379805 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379805] Re: [i945gm] virtual 2048 in xorg.conf causes blank white screen on login
** Attachment added: Xorg.0.log - not working http://launchpadlibrarian.net/27168442/Xorg.0.log.old -- [i945gm] virtual 2048 in xorg.conf causes blank white screen on login https://bugs.launchpad.net/bugs/379805 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379805] Re: [i945gm] virtual 2048 in xorg.conf causes blank white screen on login
1. Is it the external monitor, the laptop monitor or both that go white? The LCD screen on the laptop. 2. With which desktop environment does this happen? (kde, gnome, xfce, etc...) Does it happen with other desktop environment as well? Gnome. I don't have any others installed. 3. Does the problem occur irrespective of whether you have the external monitor connected? - no external monitor connected : White screen - external monitor plugged in after GDM login page is shown but before login : external monitor never comes out of power saving mode - external monitor plugged in then GDM restarted : white screen on both LCD and external monitor 4. Why do you use the option UseFBdev? The log file says that it is ignored. I''ve not edited the xorg.conf file by hand except to comment out the virtual. This must have been added by one of the config or reconfig programs. I've removed it. 5. What computer model do you have? Dell Latitude D420 6. Could you test if it is still a problem with the newer drivers (2.7.1) available from https://launchpad.net/~ubuntu-x-swat/+archive/x-updates/ ? There are quite a few bug fixes in that version, and we don't want to upstream bugs to the intel developers that they have already fixed. I'm not currently in a position to test this. I've got a partially installed package which won't complete installation and won't remove. I can't install anything at the moment (sigh). I'm researching how to fix this. I'll try these drives once installation works again. 7. Could you try to vary the maximum in your virtual setting to see where the problem occurs? It is likely that it will work for 2048 and not work for 2049, since the driver behaviour changes at that limit. Could you verify that this is the limit? I've checked. 2049 shows the white screen. 2048 works. -- [i945gm] virtual 2048 in xorg.conf causes blank white screen on login https://bugs.launchpad.net/bugs/379805 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379805] [NEW] virtual keyword in xorg.conf causes blank white screen on login
Public bug reported: Binary package hint: xserver-xorg-video-intel I'm trying to configure the secondary output on this laptop for use with projectors (etc). When I go through system / preferences / display, it tells me that the virtual keyword needs adding to my xorg.conf file and does it for me. When I reboot with virtual in xorg.conf and login, I get a blank white screen. If I use ctrl+alt+f1 to get a command line, edit xorg.conf to comment out the display subsection and then restart gdm, everything is works - except that of course the secondary output will only work as a mirror. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 Package: xserver-xorg-video-intel 2:2.6.3-0ubuntu9 ProcEnviron: LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersion: Linux version 2.6.28-11-generic (bui...@palmer) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 SourcePackage: xserver-xorg-video-intel Uname: Linux 2.6.28-11-generic i686 ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- virtual keyword in xorg.conf causes blank white screen on login https://bugs.launchpad.net/bugs/379805 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379805] Re: virtual keyword in xorg.conf causes blank white screen on login
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/27093431/Dependencies.txt ** Attachment added: LsHal.txt http://launchpadlibrarian.net/27093432/LsHal.txt ** Attachment added: LsMod.txt http://launchpadlibrarian.net/27093433/LsMod.txt ** Attachment added: LsPci.txt http://launchpadlibrarian.net/27093434/LsPci.txt ** Attachment added: XorgConf.txt http://launchpadlibrarian.net/27093435/XorgConf.txt ** Attachment added: XorgLog.txt http://launchpadlibrarian.net/27093436/XorgLog.txt ** Attachment added: XorgLogOld.txt http://launchpadlibrarian.net/27093437/XorgLogOld.txt ** Attachment added: Xrandr.txt http://launchpadlibrarian.net/27093438/Xrandr.txt ** Attachment added: glxinfo.txt http://launchpadlibrarian.net/27093439/glxinfo.txt ** Attachment added: monitors.xml.txt http://launchpadlibrarian.net/27093441/monitors.xml.txt ** Attachment added: setxkbmap.txt http://launchpadlibrarian.net/27093442/setxkbmap.txt ** Attachment added: system.txt http://launchpadlibrarian.net/27093443/system.txt ** Attachment added: xdpyinfo.txt http://launchpadlibrarian.net/27093444/xdpyinfo.txt ** Attachment added: xkbcomp.txt http://launchpadlibrarian.net/27093445/xkbcomp.txt -- virtual keyword in xorg.conf causes blank white screen on login https://bugs.launchpad.net/bugs/379805 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 320173] Re: [jaunty] Mouse and keyboard stop responding
I'm having the same problem having just installed Jaunty on a Dell Latitude D420. It's happened twice today having installed Jaunty last night. One of the questions asked if hal was running. Here's the output of ps aux | grep hal 105 2555 0.0 0.1 6684 2768 ?Ss 13:54 0:12 /usr/sbin/hald root 2622 0.0 0.0 3328 1072 ?S13:54 0:02 hald-runner root 2652 0.0 0.0 5176 1820 ?S13:54 0:00 /usr/lib/hal/hald-addon-dell-backlight root 2656 0.0 0.0 5176 1728 ?S13:54 0:00 hald-addon-input: Listening on /dev/input/event2 /dev/input/event1 /dev/input/event5 /dev/input/event6 /dev/input/event0 /dev/input/event4 root 2667 0.0 0.0 5304 1908 ?S13:54 0:01 /usr/lib/hal/hald-addon-rfkill-killswitch root 2702 0.0 0.0 5188 1696 ?S13:54 0:00 /usr/lib/hal/hald-addon-cpufreq 105 2703 0.0 0.0 5032 1672 ?S13:54 0:00 hald-addon-acpi: listening on acpid socket /var/run/acpid.socket jon 3469 0.0 0.1 7996 3048 ?S13:54 0:00 /usr/lib/gvfs/gvfs-hal-volume-monitor jon 21682 0.0 0.0 3344 816 pts/5S+ 20:34 0:00 grep hal ** Attachment added: /var/log/Xorg.0.log with no keyboard input working http://launchpadlibrarian.net/26825255/Xorg.0.log -- [jaunty] Mouse and keyboard stop responding https://bugs.launchpad.net/bugs/320173 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 320173] Re: [jaunty] Mouse and keyboard stop responding
I've just re-started hal (/etc/init.d/hal restart) and the problem is still here. Attached is the output of lshal after this. ** Attachment added: Output of lshal when keyboard input is not working - after hal restart http://launchpadlibrarian.net/26825600/lshal-keyboard-not-working-after-hal-restart -- [jaunty] Mouse and keyboard stop responding https://bugs.launchpad.net/bugs/320173 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 320173] Re: [jaunty] Mouse and keyboard stop responding
** Attachment added: Output of lshal when keyboard input is not working http://launchpadlibrarian.net/26825488/lshal-keyboard-not-working -- [jaunty] Mouse and keyboard stop responding https://bugs.launchpad.net/bugs/320173 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
