[Kernel-packages] [Bug 2078553] Re: (Nvidia) system freezes when called to suspend since Linux 6.7.0 on Nvidia hardware with modeset
** Attachment added: "/etc/systemd/system/getty@tty1.service.d/override.conf" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2078553/+attachment/5813642/+files/override.conf -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2078553 Title: (Nvidia) system freezes when called to suspend since Linux 6.7.0 on Nvidia hardware with modeset Status in linux package in Ubuntu: New Bug description: == Summary == On my computer with an ancient Nvidia chipset (Geforce 7025/nForce 630a), running `sysctl suspend` (or suspending from the Gnome menu) causes the system to start suspending, but it freezes halfway, leaving fans and hard drives spinning. There's no way to resume from this frozen state apart from forcing a reboot (with a hardware reset button/poweroff). == Steps to reproduce == * boot with modeset enabled * run `sysctl suspend` == What I expect to happen == For the system to suspend, shutting down all fans and hard drives. == What happens == The system begins to suspend, but freezes halfway, leaving the display on and fans and hard drives spinning, but the keyboard unresponsive. == Workaround == Disable kernel modesetting by adding "nomodeset" to the kernel commandline. == Affected kernels == Prior to upgrades the system was running HWE kernel 5.15.0, so I tried the 5.15 series, and found that I could now suspend and wake the machine again just as before. I worked my way up the versions: * 5.15.50: unaffected * 5.15.165: unaffected * 5.19.17: unaffected * 6.4.0: unaffected * 6.6.0: unaffected * 6.6.48: unaffected * 6.7.0: first to fail I also tried the current newest mainline kernel 6.10.7, and the issue is still present there. == Background == I have an old desktop machine now functioning as a NAS, and yesterday I upgraded it from Ubuntu 20.04 first to 22.04, and then all the way up to 24.04. The upgrade went smoothly, and this is the only issue I've come across since. In the BIOS settings of the affected machine there are three "suspend mode" alternatives to choose from: "S1 (POS) only", "S3 only" and "Auto". I've always had it on "Auto", but with this issue I also tested both "S1 only" and "S3 only", with no effect. The issue is also present when booting from the installation media (USB) into a live environment. I've previously upgraded my laptop to 24.04, and there suspending still works as it did before the ugprade, so this is probably hardware-specific; the laptop is a modern one with all-Intel hardware. Googling around, I could smelled hints of this being once again related to the troublesome Nvidia chipset, so I tried nomodeset with the stock 6.8.0 kernel (6.8.0-41 currently) and voilà! Suspend and wake were working again. Well, except for the display, which stayed black. But I couldn't say if this was the way it was before, because the NAS is normally running headless. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-41-generic 6.8.0-41.41 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k6.8.0-41-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer', '/dev/snd/seq', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D2c', '/dev/snd/hwC0D0', '/dev/snd/controlC0', '/dev/snd/by-path'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown Date: Sat Aug 31 14:16:51 2024 HibernationDevice: RESUME=UUID=2faf9ef0-28e5-490f-8c62-376d78bf29b3 MachineType: System manufacturer System Product Name ProcFB: 0 simpledrmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-41-generic root=UUID=f2668afb-32fb-4af1-9f29-5b4665b43cf3 ro consoleblank=0 nomodeset RelatedPackageVersions: linux-restricted-modules-6.8.0-41-generic N/A linux-backports-modules-6.8.0-41-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2.2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-08-30 (1 days ago) dmi.bios.date: 08/23/2010 dmi.bios.release: 8.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1804 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N68-AM Plus dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dm
[Kernel-packages] [Bug 2078553] Re: (Nvidia) system freezes when called to suspend since Linux 6.7.0 on Nvidia hardware with modeset
Hi Vinicius, thanks for looking into this! I'll have to postpone further testing until the next time there's an issue, as my backups rely on the NAS (and it's now back in operation with the nomodeset workaround). Taking it down is also physically fairly involved, as I prefer to unplug all the data drives, to spare them from repeated powercycling during testing. However, I'm about 80 % sure I checked the journal for the failed suspends, and it just stopped there, resuming thereafter with just the boot messages from the next boot onward. Also, I have TTY1 configured to display the journal "live" (I'll attach my /etc/systemd/system/getty@tty1.service.d/override.conf below), and I *did* try suspending with that TTY showing the journal (`sleep 5 && systemctl suspend` on TTY2, then switching to TTY1 before the timeout); I'll attach a photo of that view when the suspend had resulted in this freezing issue. Unfortunately I don't have a cable to do debugging over a serial console. ** Attachment added: "IMG_1527.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2078553/+attachment/5813641/+files/IMG_1527.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2078553 Title: (Nvidia) system freezes when called to suspend since Linux 6.7.0 on Nvidia hardware with modeset Status in linux package in Ubuntu: New Bug description: == Summary == On my computer with an ancient Nvidia chipset (Geforce 7025/nForce 630a), running `sysctl suspend` (or suspending from the Gnome menu) causes the system to start suspending, but it freezes halfway, leaving fans and hard drives spinning. There's no way to resume from this frozen state apart from forcing a reboot (with a hardware reset button/poweroff). == Steps to reproduce == * boot with modeset enabled * run `sysctl suspend` == What I expect to happen == For the system to suspend, shutting down all fans and hard drives. == What happens == The system begins to suspend, but freezes halfway, leaving the display on and fans and hard drives spinning, but the keyboard unresponsive. == Workaround == Disable kernel modesetting by adding "nomodeset" to the kernel commandline. == Affected kernels == Prior to upgrades the system was running HWE kernel 5.15.0, so I tried the 5.15 series, and found that I could now suspend and wake the machine again just as before. I worked my way up the versions: * 5.15.50: unaffected * 5.15.165: unaffected * 5.19.17: unaffected * 6.4.0: unaffected * 6.6.0: unaffected * 6.6.48: unaffected * 6.7.0: first to fail I also tried the current newest mainline kernel 6.10.7, and the issue is still present there. == Background == I have an old desktop machine now functioning as a NAS, and yesterday I upgraded it from Ubuntu 20.04 first to 22.04, and then all the way up to 24.04. The upgrade went smoothly, and this is the only issue I've come across since. In the BIOS settings of the affected machine there are three "suspend mode" alternatives to choose from: "S1 (POS) only", "S3 only" and "Auto". I've always had it on "Auto", but with this issue I also tested both "S1 only" and "S3 only", with no effect. The issue is also present when booting from the installation media (USB) into a live environment. I've previously upgraded my laptop to 24.04, and there suspending still works as it did before the ugprade, so this is probably hardware-specific; the laptop is a modern one with all-Intel hardware. Googling around, I could smelled hints of this being once again related to the troublesome Nvidia chipset, so I tried nomodeset with the stock 6.8.0 kernel (6.8.0-41 currently) and voilà! Suspend and wake were working again. Well, except for the display, which stayed black. But I couldn't say if this was the way it was before, because the NAS is normally running headless. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-41-generic 6.8.0-41.41 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k6.8.0-41-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer', '/dev/snd/seq', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D2c', '/dev/snd/hwC0D0', '/dev/snd/controlC0', '/dev/snd/by-path'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown Date: Sat Aug 31 14:16:51 2024 HibernationDevice: RESUME=UU
[Kernel-packages] [Bug 2078553] [NEW] (Nvidia) system freezes when called to suspend since Linux 6.7.0 on Nvidia hardware with modeset
Public bug reported: == Summary == On my computer with an ancient Nvidia chipset (Geforce 7025/nForce 630a), running `sysctl suspend` (or suspending from the Gnome menu) causes the system to start suspending, but it freezes halfway, leaving fans and hard drives spinning. There's no way to resume from this frozen state apart from forcing a reboot (with a hardware reset button/poweroff). == Steps to reproduce == * boot with modeset enabled * run `sysctl suspend` == What I expect to happen == For the system to suspend, shutting down all fans and hard drives. == What happens == The system begins to suspend, but freezes halfway, leaving the display on and fans and hard drives spinning, but the keyboard unresponsive. == Workaround == Disable kernel modesetting by adding "nomodeset" to the kernel commandline. == Affected kernels == Prior to upgrades the system was running HWE kernel 5.15.0, so I tried the 5.15 series, and found that I could now suspend and wake the machine again just as before. I worked my way up the versions: * 5.15.50: unaffected * 5.15.165: unaffected * 5.19.17: unaffected * 6.4.0: unaffected * 6.6.0: unaffected * 6.6.48: unaffected * 6.7.0: first to fail I also tried the current newest mainline kernel 6.10.7, and the issue is still present there. == Background == I have an old desktop machine now functioning as a NAS, and yesterday I upgraded it from Ubuntu 20.04 first to 22.04, and then all the way up to 24.04. The upgrade went smoothly, and this is the only issue I've come across since. In the BIOS settings of the affected machine there are three "suspend mode" alternatives to choose from: "S1 (POS) only", "S3 only" and "Auto". I've always had it on "Auto", but with this issue I also tested both "S1 only" and "S3 only", with no effect. The issue is also present when booting from the installation media (USB) into a live environment. I've previously upgraded my laptop to 24.04, and there suspending still works as it did before the ugprade, so this is probably hardware- specific; the laptop is a modern one with all-Intel hardware. Googling around, I could smelled hints of this being once again related to the troublesome Nvidia chipset, so I tried nomodeset with the stock 6.8.0 kernel (6.8.0-41 currently) and voilà! Suspend and wake were working again. Well, except for the display, which stayed black. But I couldn't say if this was the way it was before, because the NAS is normally running headless. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-41-generic 6.8.0-41.41 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k6.8.0-41-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer', '/dev/snd/seq', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D2c', '/dev/snd/hwC0D0', '/dev/snd/controlC0', '/dev/snd/by-path'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown Date: Sat Aug 31 14:16:51 2024 HibernationDevice: RESUME=UUID=2faf9ef0-28e5-490f-8c62-376d78bf29b3 MachineType: System manufacturer System Product Name ProcFB: 0 simpledrmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-41-generic root=UUID=f2668afb-32fb-4af1-9f29-5b4665b43cf3 ro consoleblank=0 nomodeset RelatedPackageVersions: linux-restricted-modules-6.8.0-41-generic N/A linux-backports-modules-6.8.0-41-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2.2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-08-30 (1 days ago) dmi.bios.date: 08/23/2010 dmi.bios.release: 8.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1804 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N68-AM Plus dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1804:bd08/23/2010:br8.14:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N68-AMPlus:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer mtime.conffile..etc.init.d.apport: 2024-07-22T17:59:07 ** Affects: linux (Ubuntu) Importance: Undecided
[Kernel-packages] [Bug 1010926] Re: HP Folio 13: Lid close event is never fired => no suspend on lid close
** Bug watch added: hacking a member #512958
https://bugzilla.redhat.com/cgi-bin/bugreport.cgi?bug=512958
** Also affects: linux via
https://bugzilla.redhat.com/cgi-bin/bugreport.cgi?bug=512958
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1010926
Title:
HP Folio 13: Lid close event is never fired => no suspend on lid close
Status in Linux:
Unknown
Status in linux package in Ubuntu:
Triaged
Bug description:
The machine is an HP Folio 13 notebook.
The state of the lid is correctly reported in /proc:
With lid open:
gpothier@tadzim2:~$ cat /proc/acpi/button/lid/*/state
state: open
With lid closed:
gpothier@tadzim2:~$ cat /proc/acpi/button/lid/*/state
state: closed
The events are never fired however. This is the output of acpi_listen
after hitting the power button (just to check that some acpi events
are indeed fired):
gpothier@tadzim2:~$ acpi_listen
button/power PWRF 0080 0001
video GFX0 0080
button/lid LID0 0080 0001
But when closing/opening the lid, nothing happens. This prevents the
suspend on lid close feature to work.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-24-generic 3.2.0-24.39
ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
Uname: Linux 3.2.0-24-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu8
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D3',
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D3p', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xc270 irq 50'
Mixer name : 'Intel CougarPoint HDMI'
Components : 'HDA:111d76e5,103c17f8,00100102
HDA:80862805,80860101,0010'
Controls : 22
Simple ctrls : 10
Date: Sat Jun 9 11:45:19 2012
HibernationDevice: RESUME=UUID=cb1ceaaa-6de7-42c5-a842-50edef2af7c3
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64
(20120425)
MachineType: Hewlett-Packard HP Folio 13 Notebook PCC
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic
root=UUID=acdbf868-560a-4ec7-8772-45c16c166819 ro acpi_backlight=vendor quiet
splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-3.2.0-24-generic N/A
linux-backports-modules-3.2.0-24-generic N/A
linux-firmware1.79
SourcePackage: linux
StagingDrivers: rts_pstor mei
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/05/2012
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.06
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 17F8
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 46.34
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnHewlett-Packard:bvrF.06:bd03/05/2012:svnHewlett-Packard:pnHPFolio13NotebookPCC:pvr068C10204A0320100:rvnHewlett-Packard:rn17F8:rvr46.34:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Folio 13 Notebook PCC
dmi.product.version: 068C10204A0320100
dmi.sys.vendor: Hewlett-Packard
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1010926/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 926012] Re: With a -pae kernel, freeze during boot when wistron_btns loaded
Hi Christopher. I was unable to test the Saucy images and the latest mainline kernel, as they refuse to boot/install on the Amilo due to lack of PAE support. jani@kingugidora:~$ LC_ALL=C sudo dpkg --install linux-image-3.11.0-031100rc6-generic_3.11.0-031100rc6.201308181835_i386.deb (Reading database ... 818498 files and directories currently installed.) Unpacking linux-image-3.11.0-031100rc6-generic (from linux-image-3.11.0-031100rc6-generic_3.11.0-031100rc6.201308181835_i386.deb) ... This kernel does not support a non-PAE CPU. dpkg: error processing linux-image-3.11.0-031100rc6-generic_3.11.0-031100rc6.201308181835_i386.deb (--install): subprocess new pre-installation script returned error exit status 1 Examining /etc/kernel/postrm.d . run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.11.0-031100rc6-generic /boot/vmlinuz-3.11.0-031100rc6-generic run-parts: executing /etc/kernel/postrm.d/zz-update-grub 3.11.0-031100rc6-generic /boot/vmlinuz-3.11.0-031100rc6-generic Errors were encountered while processing: linux-image-3.11.0-031100rc6-generic_3.11.0-031100rc6.201308181835_i386.deb I guess the only (unimportant) question remaining is how come I was able to boot -pae kernels on this very same device back in the pre-release times (3.2.0-[<23]) - perhaps those earlier kernels didn't properly detect the lack of PAE? The wireless now (with the current 3.2.0-52-generic #78-Ubuntu) seems to somehow work without wistron_btns. I'm not sure how to deal with the tags & bug status in this case, so I'll leave it to your discretion. If you have further ideas to test, I'll be happy to provide, but closing this report (perhaps as 'Invalid') is also fine by me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/926012 Title: With a -pae kernel, freeze during boot when wistron_btns loaded Status in The Linux Kernel: Confirmed Status in “linux” package in Ubuntu: Incomplete Bug description: With my Amilo M7400 and the recent Precise kernels (at least 3.2.0-[10-12] I think), the system freezes during boot with the Ubuntu logo and colored dots on screen (the dots stop progressing), when I have wistron_btns enabled in /etc/modules. I need wistron_btns on this laptop for the wireless to work, which is why I'd like to have it enabled. This is unrelated to Bug #926007 which I also just filed: the wistron_btns freeze happens even when I'm using fbdev. (With -intel, the #926007 panic and this freeze take turns in who gets to mess with me.) From what I've gathered so far, it seems that wistron_btns works fine if I manually modprobe it from my desktop, after booting without it. So that's a workaround at least. I can kill the freeze with Alt+PrtSc+REISUB. I'll provide any additional info needed, though I don't know how to produce logs when the system is frozen. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-12-generic-pae 3.2.0-12.21 ProcVersionSignature: Ubuntu 3.2.0-12.21-generic-pae 3.2.2 Uname: Linux 3.2.0-12-generic-pae i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.91-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jani 1782 F pulseaudio Card0.Amixer.info: Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with CS4299 at irq 10' Mixer name : 'Cirrus Logic CS4299 rev 4' Components : 'AC97a:43525934' Controls : 36 Simple ctrls : 22 CurrentDmesg: [ 35.672075] intel8x0: clocking to 48000 [ 36.816209] b44 ssb0:0: eth0: Link is up at 100 Mbps, full duplex [ 36.816216] b44 ssb0:0: eth0: Flow control is off for TX and off for RX [ 36.816551] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 46.880038] eth0: no IPv6 routers present Date: Fri Feb 3 13:58:44 2012 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=80b87005-5f3a-4290-bba9-d30ef32f8151 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: FUJITSU SIEMENS AMILO M PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=fi:en_US:en PATH=(custom, user) LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-12-generic-pae root=UUID=f5b168d7-b4d0-40d8-b76a-8bda4fb90be5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.2.0-12-generic-pae N/A linux-backports-modules-3.2.0-12-generic-pae N/A linux-firmware1.68
