Re: [Kernel-packages] [Bug 1532145] Re: Kernel Panic wrt btrfs while sbuild/schroot
Thanks Colin! 2016-02-16 19:20 GMT+01:00 Colin Ian King <1532...@bugs.launchpad.net>: > I suggest a workaround for the moment, using aufs as the overlay to see > if this helps. > > Modify the chroot config and set the union-type to aufs: > > union-type=aufs > > you may see an error like: > > "aufs au_xino_create:778:mount[3600]: xino doesn't support > /tmp/.aufs.xino(btrfs)" > > this is caused by the fact that btrfs cannot store aufs xino files. > aufs tries to store these files alongside the rw layer. If that fails, > it tries to store them in /tmp/.aufs.xino, however, if this is btrfs it > will fail. So the workaround for that is to mount /tmp as something > other than btrfs, e.g. tmpfs > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1532145 > > Title: > Kernel Panic wrt btrfs while sbuild/schroot > > Status in Linux: > Unknown > Status in linux package in Ubuntu: > In Progress > > Bug description: > I'm running ubuntu Wily amd64 on a MSI Ghost Pro laptop. > > I'm running btrfs on top of a bcached dmraid setup(intel software > raid0). > > I can't use sbuild, cause it crashes. > > I tried to use a schroot env, and when updating it I got it to crash > also. > > All the keyboard/mouse/X11 are stalled, but I could ssh to it. > Trying to restart lightdm service didn't help. > > I've got a kernel trace in the dmesg: > > [76610.550953] BUG: unable to handle kernel NULL pointer dereference at > 0334 > [76610.550983] IP: [] btrfs_sync_file+0xcc/0x360 > [btrfs] > [76610.551025] PGD 160aaf067 PUD 161531067 PMD 0 > [76610.551039] Oops: 0002 [#1] SMP > [76610.551050] Modules linked in: dm_crypt algif_skcipher af_alg drbg > ansi_cprng ctr ccm rfcomm ipt_REJECT nf_reject_ipv4 nvram msr xt_multiport > ebtable_filter ebtables ip6table_filter ip6_tables overlay bnep uvcvideo > btusb videobuf2_vmalloc videobuf2_memops btrtl btbcm videobuf2_core btintel > v4l2_common bluetooth videodev media xt_addrtype xt_conntrack xt_CHECKSUM > iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat > nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp > bridge aufs stp llc iptable_filter ip_tables x_tables binfmt_misc arc4 > nls_iso8859_1 msi_wmi sparse_keymap intel_rapl iosf_mbi > x86_pkg_temp_thermal snd_hda_codec_hdmi intel_powerclamp coretemp > crct10dif_pclmul snd_hda_codec_realtek snd_hda_codec_generic crc32_pclmul > aesni_intel aes_x86_64 lrw gf128mul > [76610.551253] snd_hda_intel iwlmvm glue_helper snd_hda_codec > ablk_helper mac80211 cryptd snd_hda_core snd_hwdep snd_pcm snd_seq_midi > joydev input_leds snd_seq_midi_event snd_rawmidi serio_raw iwlwifi lpc_ich > mei_me snd_seq mei cfg80211 snd_seq_device snd_timer snd ie31200_edac > edac_core soundcore shpchp mac_hid kvm_intel kvm parport_pc ppdev lp > parport autofs4 btrfs xor raid6_pq dm_mirror dm_region_hash dm_log uas > usb_storage bcache hid_generic usbhid hid i915 i2c_algo_bit drm_kms_helper > psmouse ahci drm alx libahci mdio wmi video > [76610.551395] CPU: 1 PID: 32090 Comm: dpkg Not tainted 4.2.0-23-generic > #28-Ubuntu > [76610.551414] Hardware name: Micro-Star International Co., Ltd. GS60 > 2PE Ghost Pro/MS-16H2, BIOS E16H2IMS.112 05/05/2015 > [76610.551438] task: 8803cf422940 ti: 8801a0be4000 task.ti: > 8801a0be4000 > [76610.551455] RIP: 0010:[] [] > btrfs_sync_file+0xcc/0x360 [btrfs] > [76610.551485] RSP: 0018:8801a0be7e28 EFLAGS: 00010292 > [76610.551497] RAX: 8803cf422940 RBX: 880273bff100 RCX: > > [76610.551513] RDX: 8000 RSI: RDI: > 88040a2fb178 > [76610.551530] RBP: 8801a0be7eb8 R08: 0001 R09: > > [76610.551546] R10: 01f6 R11: 0246 R12: > 88040a2fb178 > [76610.551563] R13: 88040a2fb0d0 R14: R15: > > [76610.551580] FS: 7f3c27bca800() GS:88041fa4() > knlGS: > [76610.551598] CS: 0010 DS: ES: CR0: 80050033 > [76610.551611] CR2: 0334 CR3: 00016159a000 CR4: > 001406e0 > [76610.551628] Stack: > [76610.551633] 80033fffa865 000b 8000 > 88008a657e40 > [76610.551652] 7fff 8801a0be7ea8 > 8804069544a0 > [76610.551671] 800173bff000 10b6e564 > 10b6e564 > [76610.551691] Call Trace: > [76610.551703] [] vfs_fsync_range+0x4b/0xb0 > [76610.551718] [] do_fsync+0x3d/0x70 > [76610.551732] [] SyS_fsync+0x10/0x20 > [76610.551751] [] entry_SYSCALL_64_fastpath+0x16/0x75 > [76610.551766] Code: 8b 0e 48 85 c9 75 e8 eb 9e 48 8b 45 90 4c 8b 75 98 > 4d 8d a5 a8 00 00 00 4c 89 e7 4c 29 f0 48 83 c0 01 48 89 45 80 e8 f4 e2 4b > c1 41 ff 87 34 03 00 00 49 8b 85 70 ff ff ff 48 c1 e8 07 83 e0 > [76610.551845] RIP []
[Kernel-packages] [Bug 1532145] Re: Kernel Panic wrt btrfs while sbuild/schroot
** Also affects: linux via http://bugzilla.kernel.org/show_bug.cgi?id=101951 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/1532145 Title: Kernel Panic wrt btrfs while sbuild/schroot Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: I'm running ubuntu Wily amd64 on a MSI Ghost Pro laptop. I'm running btrfs on top of a bcached dmraid setup(intel software raid0). I can't use sbuild, cause it crashes. I tried to use a schroot env, and when updating it I got it to crash also. All the keyboard/mouse/X11 are stalled, but I could ssh to it. Trying to restart lightdm service didn't help. I've got a kernel trace in the dmesg: [76610.550953] BUG: unable to handle kernel NULL pointer dereference at 0334 [76610.550983] IP: [] btrfs_sync_file+0xcc/0x360 [btrfs] [76610.551025] PGD 160aaf067 PUD 161531067 PMD 0 [76610.551039] Oops: 0002 [#1] SMP [76610.551050] Modules linked in: dm_crypt algif_skcipher af_alg drbg ansi_cprng ctr ccm rfcomm ipt_REJECT nf_reject_ipv4 nvram msr xt_multiport ebtable_filter ebtables ip6table_filter ip6_tables overlay bnep uvcvideo btusb videobuf2_vmalloc videobuf2_memops btrtl btbcm videobuf2_core btintel v4l2_common bluetooth videodev media xt_addrtype xt_conntrack xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge aufs stp llc iptable_filter ip_tables x_tables binfmt_misc arc4 nls_iso8859_1 msi_wmi sparse_keymap intel_rapl iosf_mbi x86_pkg_temp_thermal snd_hda_codec_hdmi intel_powerclamp coretemp crct10dif_pclmul snd_hda_codec_realtek snd_hda_codec_generic crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul [76610.551253] snd_hda_intel iwlmvm glue_helper snd_hda_codec ablk_helper mac80211 cryptd snd_hda_core snd_hwdep snd_pcm snd_seq_midi joydev input_leds snd_seq_midi_event snd_rawmidi serio_raw iwlwifi lpc_ich mei_me snd_seq mei cfg80211 snd_seq_device snd_timer snd ie31200_edac edac_core soundcore shpchp mac_hid kvm_intel kvm parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_mirror dm_region_hash dm_log uas usb_storage bcache hid_generic usbhid hid i915 i2c_algo_bit drm_kms_helper psmouse ahci drm alx libahci mdio wmi video [76610.551395] CPU: 1 PID: 32090 Comm: dpkg Not tainted 4.2.0-23-generic #28-Ubuntu [76610.551414] Hardware name: Micro-Star International Co., Ltd. GS60 2PE Ghost Pro/MS-16H2, BIOS E16H2IMS.112 05/05/2015 [76610.551438] task: 8803cf422940 ti: 8801a0be4000 task.ti: 8801a0be4000 [76610.551455] RIP: 0010:[] [] btrfs_sync_file+0xcc/0x360 [btrfs] [76610.551485] RSP: 0018:8801a0be7e28 EFLAGS: 00010292 [76610.551497] RAX: 8803cf422940 RBX: 880273bff100 RCX: [76610.551513] RDX: 8000 RSI: RDI: 88040a2fb178 [76610.551530] RBP: 8801a0be7eb8 R08: 0001 R09: [76610.551546] R10: 01f6 R11: 0246 R12: 88040a2fb178 [76610.551563] R13: 88040a2fb0d0 R14: R15: [76610.551580] FS: 7f3c27bca800() GS:88041fa4() knlGS: [76610.551598] CS: 0010 DS: ES: CR0: 80050033 [76610.551611] CR2: 0334 CR3: 00016159a000 CR4: 001406e0 [76610.551628] Stack: [76610.551633] 80033fffa865 000b 8000 88008a657e40 [76610.551652] 7fff 8801a0be7ea8 8804069544a0 [76610.551671] 800173bff000 10b6e564 10b6e564 [76610.551691] Call Trace: [76610.551703] [] vfs_fsync_range+0x4b/0xb0 [76610.551718] [] do_fsync+0x3d/0x70 [76610.551732] [] SyS_fsync+0x10/0x20 [76610.551751] [] entry_SYSCALL_64_fastpath+0x16/0x75 [76610.551766] Code: 8b 0e 48 85 c9 75 e8 eb 9e 48 8b 45 90 4c 8b 75 98 4d 8d a5 a8 00 00 00 4c 89 e7 4c 29 f0 48 83 c0 01 48 89 45 80 e8 f4 e2 4b c1 41 ff 87 34 03 00 00 49 8b 85 70 ff ff ff 48 c1 e8 07 83 e0 [76610.551845] RIP [] btrfs_sync_file+0xcc/0x360 [btrfs] [76610.551871] RSP [76610.551881] CR2: 0334 [76610.558028] ---[ end trace 33509d397c46cd18 ]--- ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-23-generic 4.2.0-23.28 ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6 Uname: Linux 4.2.0-23-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Fri Jan 8 11:02:06 2016 HibernationDevice: RESUME=UUID=1699e24b-be2c-494d-90ff-0f313a5eed84 InstallationDate: Installed on 2015-11-24 (44 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151016) MachineType: Micro-Star International Co., Ltd.
[Kernel-packages] [Bug 1532145] Re: Kernel Panic wrt btrfs while sbuild/schroot
Same bug that I already had with another laptop, it seems to be related to overlay and btrfs: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1496438 Happens also on coreos: https://github.com/coreos/rkt/issues/1498 Kernel bug: https://bugzilla.kernel.org/show_bug.cgi?id=101951 ** Bug watch added: Linux Kernel Bug Tracker #101951 http://bugzilla.kernel.org/show_bug.cgi?id=101951 -- 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/1532145 Title: Kernel Panic wrt btrfs while sbuild/schroot Status in linux package in Ubuntu: Confirmed Bug description: I'm running ubuntu Wily amd64 on a MSI Ghost Pro laptop. I'm running btrfs on top of a bcached dmraid setup(intel software raid0). I can't use sbuild, cause it crashes. I tried to use a schroot env, and when updating it I got it to crash also. All the keyboard/mouse/X11 are stalled, but I could ssh to it. Trying to restart lightdm service didn't help. I've got a kernel trace in the dmesg: [76610.550953] BUG: unable to handle kernel NULL pointer dereference at 0334 [76610.550983] IP: [] btrfs_sync_file+0xcc/0x360 [btrfs] [76610.551025] PGD 160aaf067 PUD 161531067 PMD 0 [76610.551039] Oops: 0002 [#1] SMP [76610.551050] Modules linked in: dm_crypt algif_skcipher af_alg drbg ansi_cprng ctr ccm rfcomm ipt_REJECT nf_reject_ipv4 nvram msr xt_multiport ebtable_filter ebtables ip6table_filter ip6_tables overlay bnep uvcvideo btusb videobuf2_vmalloc videobuf2_memops btrtl btbcm videobuf2_core btintel v4l2_common bluetooth videodev media xt_addrtype xt_conntrack xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge aufs stp llc iptable_filter ip_tables x_tables binfmt_misc arc4 nls_iso8859_1 msi_wmi sparse_keymap intel_rapl iosf_mbi x86_pkg_temp_thermal snd_hda_codec_hdmi intel_powerclamp coretemp crct10dif_pclmul snd_hda_codec_realtek snd_hda_codec_generic crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul [76610.551253] snd_hda_intel iwlmvm glue_helper snd_hda_codec ablk_helper mac80211 cryptd snd_hda_core snd_hwdep snd_pcm snd_seq_midi joydev input_leds snd_seq_midi_event snd_rawmidi serio_raw iwlwifi lpc_ich mei_me snd_seq mei cfg80211 snd_seq_device snd_timer snd ie31200_edac edac_core soundcore shpchp mac_hid kvm_intel kvm parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_mirror dm_region_hash dm_log uas usb_storage bcache hid_generic usbhid hid i915 i2c_algo_bit drm_kms_helper psmouse ahci drm alx libahci mdio wmi video [76610.551395] CPU: 1 PID: 32090 Comm: dpkg Not tainted 4.2.0-23-generic #28-Ubuntu [76610.551414] Hardware name: Micro-Star International Co., Ltd. GS60 2PE Ghost Pro/MS-16H2, BIOS E16H2IMS.112 05/05/2015 [76610.551438] task: 8803cf422940 ti: 8801a0be4000 task.ti: 8801a0be4000 [76610.551455] RIP: 0010:[] [] btrfs_sync_file+0xcc/0x360 [btrfs] [76610.551485] RSP: 0018:8801a0be7e28 EFLAGS: 00010292 [76610.551497] RAX: 8803cf422940 RBX: 880273bff100 RCX: [76610.551513] RDX: 8000 RSI: RDI: 88040a2fb178 [76610.551530] RBP: 8801a0be7eb8 R08: 0001 R09: [76610.551546] R10: 01f6 R11: 0246 R12: 88040a2fb178 [76610.551563] R13: 88040a2fb0d0 R14: R15: [76610.551580] FS: 7f3c27bca800() GS:88041fa4() knlGS: [76610.551598] CS: 0010 DS: ES: CR0: 80050033 [76610.551611] CR2: 0334 CR3: 00016159a000 CR4: 001406e0 [76610.551628] Stack: [76610.551633] 80033fffa865 000b 8000 88008a657e40 [76610.551652] 7fff 8801a0be7ea8 8804069544a0 [76610.551671] 800173bff000 10b6e564 10b6e564 [76610.551691] Call Trace: [76610.551703] [] vfs_fsync_range+0x4b/0xb0 [76610.551718] [] do_fsync+0x3d/0x70 [76610.551732] [] SyS_fsync+0x10/0x20 [76610.551751] [] entry_SYSCALL_64_fastpath+0x16/0x75 [76610.551766] Code: 8b 0e 48 85 c9 75 e8 eb 9e 48 8b 45 90 4c 8b 75 98 4d 8d a5 a8 00 00 00 4c 89 e7 4c 29 f0 48 83 c0 01 48 89 45 80 e8 f4 e2 4b c1 41 ff 87 34 03 00 00 49 8b 85 70 ff ff ff 48 c1 e8 07 83 e0 [76610.551845] RIP [] btrfs_sync_file+0xcc/0x360 [btrfs] [76610.551871] RSP [76610.551881] CR2: 0334 [76610.558028] ---[ end trace 33509d397c46cd18 ]--- ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-23-generic 4.2.0-23.28 ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6 Uname: Linux 4.2.0-23-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Fri Jan 8 11:02:06 2016
[Kernel-packages] [Bug 1532145] Re: Kernel Panic wrt btrfs while sbuild/schroot
output of lsblk: http://paste.ubuntu.com/14468218/ -- 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/1532145 Title: Kernel Panic wrt btrfs while sbuild/schroot Status in linux package in Ubuntu: Confirmed Bug description: I'm running ubuntu Wily amd64 on a MSI Ghost Pro laptop. I'm running btrfs on top of a bcached dmraid setup(intel software raid0). I can't use sbuild, cause it crashes. I tried to use a schroot env, and when updating it I got it to crash also. All the keyboard/mouse/X11 are stalled, but I could ssh to it. Trying to restart lightdm service didn't help. I've got a kernel trace in the dmesg: [76610.550953] BUG: unable to handle kernel NULL pointer dereference at 0334 [76610.550983] IP: [] btrfs_sync_file+0xcc/0x360 [btrfs] [76610.551025] PGD 160aaf067 PUD 161531067 PMD 0 [76610.551039] Oops: 0002 [#1] SMP [76610.551050] Modules linked in: dm_crypt algif_skcipher af_alg drbg ansi_cprng ctr ccm rfcomm ipt_REJECT nf_reject_ipv4 nvram msr xt_multiport ebtable_filter ebtables ip6table_filter ip6_tables overlay bnep uvcvideo btusb videobuf2_vmalloc videobuf2_memops btrtl btbcm videobuf2_core btintel v4l2_common bluetooth videodev media xt_addrtype xt_conntrack xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge aufs stp llc iptable_filter ip_tables x_tables binfmt_misc arc4 nls_iso8859_1 msi_wmi sparse_keymap intel_rapl iosf_mbi x86_pkg_temp_thermal snd_hda_codec_hdmi intel_powerclamp coretemp crct10dif_pclmul snd_hda_codec_realtek snd_hda_codec_generic crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul [76610.551253] snd_hda_intel iwlmvm glue_helper snd_hda_codec ablk_helper mac80211 cryptd snd_hda_core snd_hwdep snd_pcm snd_seq_midi joydev input_leds snd_seq_midi_event snd_rawmidi serio_raw iwlwifi lpc_ich mei_me snd_seq mei cfg80211 snd_seq_device snd_timer snd ie31200_edac edac_core soundcore shpchp mac_hid kvm_intel kvm parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_mirror dm_region_hash dm_log uas usb_storage bcache hid_generic usbhid hid i915 i2c_algo_bit drm_kms_helper psmouse ahci drm alx libahci mdio wmi video [76610.551395] CPU: 1 PID: 32090 Comm: dpkg Not tainted 4.2.0-23-generic #28-Ubuntu [76610.551414] Hardware name: Micro-Star International Co., Ltd. GS60 2PE Ghost Pro/MS-16H2, BIOS E16H2IMS.112 05/05/2015 [76610.551438] task: 8803cf422940 ti: 8801a0be4000 task.ti: 8801a0be4000 [76610.551455] RIP: 0010:[] [] btrfs_sync_file+0xcc/0x360 [btrfs] [76610.551485] RSP: 0018:8801a0be7e28 EFLAGS: 00010292 [76610.551497] RAX: 8803cf422940 RBX: 880273bff100 RCX: [76610.551513] RDX: 8000 RSI: RDI: 88040a2fb178 [76610.551530] RBP: 8801a0be7eb8 R08: 0001 R09: [76610.551546] R10: 01f6 R11: 0246 R12: 88040a2fb178 [76610.551563] R13: 88040a2fb0d0 R14: R15: [76610.551580] FS: 7f3c27bca800() GS:88041fa4() knlGS: [76610.551598] CS: 0010 DS: ES: CR0: 80050033 [76610.551611] CR2: 0334 CR3: 00016159a000 CR4: 001406e0 [76610.551628] Stack: [76610.551633] 80033fffa865 000b 8000 88008a657e40 [76610.551652] 7fff 8801a0be7ea8 8804069544a0 [76610.551671] 800173bff000 10b6e564 10b6e564 [76610.551691] Call Trace: [76610.551703] [] vfs_fsync_range+0x4b/0xb0 [76610.551718] [] do_fsync+0x3d/0x70 [76610.551732] [] SyS_fsync+0x10/0x20 [76610.551751] [] entry_SYSCALL_64_fastpath+0x16/0x75 [76610.551766] Code: 8b 0e 48 85 c9 75 e8 eb 9e 48 8b 45 90 4c 8b 75 98 4d 8d a5 a8 00 00 00 4c 89 e7 4c 29 f0 48 83 c0 01 48 89 45 80 e8 f4 e2 4b c1 41 ff 87 34 03 00 00 49 8b 85 70 ff ff ff 48 c1 e8 07 83 e0 [76610.551845] RIP [] btrfs_sync_file+0xcc/0x360 [btrfs] [76610.551871] RSP [76610.551881] CR2: 0334 [76610.558028] ---[ end trace 33509d397c46cd18 ]--- ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-23-generic 4.2.0-23.28 ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6 Uname: Linux 4.2.0-23-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Fri Jan 8 11:02:06 2016 HibernationDevice: RESUME=UUID=1699e24b-be2c-494d-90ff-0f313a5eed84 InstallationDate: Installed on 2015-11-24 (44 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151016) MachineType: Micro-Star International Co., Ltd. GS60 2PE Ghost Pro ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=
[Kernel-packages] [Bug 1532145] Re: Kernel Panic wrt btrfs while sbuild/schroot
I tried with the upstream v4.4-wily kernel. kick@kick-gs60:~/work/merges/freeipmi$ uname -a Linux kick-gs60 4.4.0-040400-generic #201601101930 SMP Mon Jan 11 00:32:41 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux I couldn't re-use my previous schroot (couldn't mount with overlayfs). I've created a new one with --type=btrfs-snapshot. My latop didn't freeze, but I still got traces in the syslog: [ 458.091294] BUG: unable to handle kernel NULL pointer dereference at 0334 [ 458.091320] IP: [] btrfs_sync_file+0xcc/0x350 [btrfs] [ 458.091363] PGD 3e8de9067 PUD 3e8de8067 PMD 0 [ 458.091374] Oops: 0002 [#1] SMP [ 458.091383] Modules linked in: overlay drbg ansi_cprng ctr ccm rfcomm nvram msr xt_multiport ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables ip6table_filter ip6_tables xt_addrtype xt_conntrack xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables binfmt_misc bnep uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core btusb btrtl v4l2_common btbcm btintel videodev bluetooth media arc4 nls_iso8859_1 intel_rapl iwlmvm x86_pkg_temp_thermal intel_powerclamp coretemp msi_wmi sparse_keymap crct10dif_pclmul snd_hda_codec_realtek crc32_pclmul snd_hda_codec_hdmi snd_hda_codec_generic aesni_intel aes_x86_64 mac80211 lrw gf128mul glue_helper ablk_helper [ 458.091575] cryptd snd_hda_intel input_leds snd_hda_codec iwlwifi snd_hda_core snd_hwdep joydev snd_seq_midi snd_seq_midi_event serio_raw snd_pcm snd_rawmidi snd_seq snd_seq_device snd_timer lpc_ich cfg80211 mei_me snd mei soundcore ie31200_edac shpchp edac_core mac_hid kvm_intel kvm irqbypass parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_mirror dm_region_hash dm_log bcache hid_generic usbhid hid i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse drm ahci alx libahci mdio wmi video fjes [ 458.091711] CPU: 1 PID: 5615 Comm: debconf-set-sel Not tainted 4.4.0-040400-generic #201601101930 [ 458.091731] Hardware name: Micro-Star International Co., Ltd. GS60 2PE Ghost Pro/MS-16H2, BIOS E16H2IMS.112 05/05/2015 [ 458.091755] task: 8803e1013700 ti: 8803e8d38000 task.ti: 8803e8d38000 [ 458.091771] RIP: 0010:[] [] btrfs_sync_file+0xcc/0x350 [btrfs] [ 458.091804] RSP: 0018:8803e8d3be48 EFLAGS: 00010246 [ 458.091815] RAX: 8803e1013700 RBX: 8803af242700 RCX: [ 458.091831] RDX: 8000 RSI: RDI: 880409d9c988 [ 458.091846] RBP: 8803e8d3bec8 R08: 0001 R09: 021f5338 [ 458.091861] R10: 009c R11: 0246 R12: 880409d9c988 [ 458.091876] R13: 880409d9c8e0 R14: R15: [ 458.091892] FS: 7f31a0444700() GS:88041fa4() knlGS: [ 458.091910] CS: 0010 DS: ES: CR0: 80050033 [ 458.091922] CR2: 0334 CR3: 0003e8f05000 CR4: 001406e0 [ 458.091937] Stack: [ 458.091942] 027bf270 0001 8000 8803bbc02540 [ 458.091960] 7fff [ 458.091978] 92eff2d8 92eff2d8 8803af242700 [ 458.091995] Call Trace: [ 458.092006] [] vfs_fsync_range+0x4b/0xb0 [ 458.092019] [] do_fsync+0x3d/0x70 [ 458.092030] [] SyS_fsync+0x10/0x20 [ 458.092043] [] entry_SYSCALL_64_fastpath+0x16/0x75 [ 458.092057] Code: 8b 0e 48 85 c9 75 e8 eb 9e 48 8b 45 a0 4c 8b 75 a8 4d 8d a5 a8 00 00 00 4c 89 e7 4c 29 f0 48 83 c0 01 48 89 45 90 e8 d4 48 4b c1 41 ff 87 34 03 00 00 49 8b 85 70 ff ff ff 48 c1 e8 07 83 e0 [ 458.092132] RIP [] btrfs_sync_file+0xcc/0x350 [btrfs] [ 458.092155] RSP [ 458.092163] CR2: 0334 [ 458.097834] ---[ end trace ff869f7e0dc1efc8 ]--- [ 467.516336] general protection fault: [#2] SMP [ 467.516353] Modules linked in: overlay drbg ansi_cprng ctr ccm rfcomm nvram msr xt_multiport ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables ip6table_filter ip6_tables xt_addrtype xt_conntrack xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables binfmt_misc bnep uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core btusb btrtl v4l2_common btbcm btintel videodev bluetooth media arc4 nls_iso8859_1 intel_rapl iwlmvm x86_pkg_temp_thermal intel_powerclamp coretemp msi_wmi sparse_keymap crct10dif_pclmul snd_hda_codec_realtek crc32_pclmul snd_hda_codec_hdmi snd_hda_codec_generic aesni_intel aes_x86_64 mac80211 lrw gf128mul glue_helper ablk_helper [ 467.516558] cryptd snd_hda_intel input_leds snd_hda_codec iwlwifi snd_hda_core snd_hwdep joydev snd_seq_midi snd_seq_midi_event serio_raw snd_pcm
[Kernel-packages] [Bug 1532145] [NEW] Kernel Panic wrt btrfs while sbuild/schroot
Public bug reported: I'm running ubuntu Wily amd64 on a MSI Ghost Pro laptop. I'm running btrfs on top of a bcached dmraid setup(intel software raid0). I can't use sbuild, cause it crashes. I tried to use a schroot env, and when updating it I got it to crash also. All the keyboard/mouse/X11 are stalled, but I could ssh to it. Trying to restart lightdm service didn't help. I've got a kernel trace in the dmesg: [76610.550953] BUG: unable to handle kernel NULL pointer dereference at 0334 [76610.550983] IP: [] btrfs_sync_file+0xcc/0x360 [btrfs] [76610.551025] PGD 160aaf067 PUD 161531067 PMD 0 [76610.551039] Oops: 0002 [#1] SMP [76610.551050] Modules linked in: dm_crypt algif_skcipher af_alg drbg ansi_cprng ctr ccm rfcomm ipt_REJECT nf_reject_ipv4 nvram msr xt_multiport ebtable_filter ebtables ip6table_filter ip6_tables overlay bnep uvcvideo btusb videobuf2_vmalloc videobuf2_memops btrtl btbcm videobuf2_core btintel v4l2_common bluetooth videodev media xt_addrtype xt_conntrack xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge aufs stp llc iptable_filter ip_tables x_tables binfmt_misc arc4 nls_iso8859_1 msi_wmi sparse_keymap intel_rapl iosf_mbi x86_pkg_temp_thermal snd_hda_codec_hdmi intel_powerclamp coretemp crct10dif_pclmul snd_hda_codec_realtek snd_hda_codec_generic crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul [76610.551253] snd_hda_intel iwlmvm glue_helper snd_hda_codec ablk_helper mac80211 cryptd snd_hda_core snd_hwdep snd_pcm snd_seq_midi joydev input_leds snd_seq_midi_event snd_rawmidi serio_raw iwlwifi lpc_ich mei_me snd_seq mei cfg80211 snd_seq_device snd_timer snd ie31200_edac edac_core soundcore shpchp mac_hid kvm_intel kvm parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_mirror dm_region_hash dm_log uas usb_storage bcache hid_generic usbhid hid i915 i2c_algo_bit drm_kms_helper psmouse ahci drm alx libahci mdio wmi video [76610.551395] CPU: 1 PID: 32090 Comm: dpkg Not tainted 4.2.0-23-generic #28-Ubuntu [76610.551414] Hardware name: Micro-Star International Co., Ltd. GS60 2PE Ghost Pro/MS-16H2, BIOS E16H2IMS.112 05/05/2015 [76610.551438] task: 8803cf422940 ti: 8801a0be4000 task.ti: 8801a0be4000 [76610.551455] RIP: 0010:[] [] btrfs_sync_file+0xcc/0x360 [btrfs] [76610.551485] RSP: 0018:8801a0be7e28 EFLAGS: 00010292 [76610.551497] RAX: 8803cf422940 RBX: 880273bff100 RCX: [76610.551513] RDX: 8000 RSI: RDI: 88040a2fb178 [76610.551530] RBP: 8801a0be7eb8 R08: 0001 R09: [76610.551546] R10: 01f6 R11: 0246 R12: 88040a2fb178 [76610.551563] R13: 88040a2fb0d0 R14: R15: [76610.551580] FS: 7f3c27bca800() GS:88041fa4() knlGS: [76610.551598] CS: 0010 DS: ES: CR0: 80050033 [76610.551611] CR2: 0334 CR3: 00016159a000 CR4: 001406e0 [76610.551628] Stack: [76610.551633] 80033fffa865 000b 8000 88008a657e40 [76610.551652] 7fff 8801a0be7ea8 8804069544a0 [76610.551671] 800173bff000 10b6e564 10b6e564 [76610.551691] Call Trace: [76610.551703] [] vfs_fsync_range+0x4b/0xb0 [76610.551718] [] do_fsync+0x3d/0x70 [76610.551732] [] SyS_fsync+0x10/0x20 [76610.551751] [] entry_SYSCALL_64_fastpath+0x16/0x75 [76610.551766] Code: 8b 0e 48 85 c9 75 e8 eb 9e 48 8b 45 90 4c 8b 75 98 4d 8d a5 a8 00 00 00 4c 89 e7 4c 29 f0 48 83 c0 01 48 89 45 80 e8 f4 e2 4b c1 41 ff 87 34 03 00 00 49 8b 85 70 ff ff ff 48 c1 e8 07 83 e0 [76610.551845] RIP [] btrfs_sync_file+0xcc/0x360 [btrfs] [76610.551871] RSP [76610.551881] CR2: 0334 [76610.558028] ---[ end trace 33509d397c46cd18 ]--- ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-23-generic 4.2.0-23.28 ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6 Uname: Linux 4.2.0-23-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Fri Jan 8 11:02:06 2016 HibernationDevice: RESUME=UUID=1699e24b-be2c-494d-90ff-0f313a5eed84 InstallationDate: Installed on 2015-11-24 (44 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151016) MachineType: Micro-Star International Co., Ltd. GS60 2PE Ghost Pro ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-23-generic.efi.signed root=UUID=e8f9dc8a-aa49-481d-8fcc-be8cff0f61b1 ro rootflags=subvol=@ blacklist=nouveau quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-23-generic N/A linux-backports-modules-4.2.0-23-generic N/A linux-firmware1.149.3 SourcePackage: linux UdevLog: Error:
[Kernel-packages] [Bug 1496433] [NEW] Error in i915 driver
Public bug reported: The 7th of september I lost my Xorg display on wily. I was always in failsafe mode. I still could get openbox to run, which was still loading i915, but didn't consume any 3D/advanced instruction I thinK. I didn't got too much time to go beyond. As I got also a btrfs kernel dump message, so I checked my ram at least with memtest86+, all was OK. Reverting to vivid allowed me to be back on unity. Wily-amd64, kernel 4.2.0.7-7-generic/low-latency Here are the traces I got: [ 22.335530] [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in ips_enabled (expected 1, found 0) [ 22.335535] [ cut here ] [ 22.335562] WARNING: CPU: 0 PID: 2190 at /build/linux-4dBub_/linux-4.2.0/drivers/gpu/drm/i915/intel_display.c:12324 check_crtc_state+0x2c5/0x440 [i915]() [ 22.335564] pipe state doesn't match! [ 22.335566] Modules linked in: ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables ip6_tables overlay xt_addrtype xt_conntrack xt_CHECKSUM ax88179_178a iptable_mangle usbnet ipt_MASQUERADE rtsx_usb_ms nf_nat_masquerade_ipv4 aufs iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 mii memstick nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc binfmt_misc iptable_filter ip_tables x_tables bnep drbg ansi_cprng dm_crypt nls_iso8859_1 intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul snd_soc_rt5640 glue_helper ablk_helper snd_soc_rl6231 cryptd snd_soc_core input_leds serio_raw hid_sensor_rotation snd_compress ac97_bus snd_pcm_dmaengine snd_seq_midi snd_seq_midi_event snd_hda_codec_realtek hid_sensor_incl_3d [ 22.335625] uvcvideo videobuf2_vmalloc snd_hda_codec_generic hid_sensor_als videobuf2_memops hid_sensor_magn_3d snd_hda_codec_hdmi hid_sensor_accel_3d hid_sensor_gyro_3d btusb hid_sensor_trigger btrtl industrialio_triggered_buffer btbcm snd_rawmidi joydev btintel videobuf2_core kfifo_buf snd_hda_intel industrialio snd_hda_codec hid_sensor_iio_common v4l2_common videodev snd_hda_core hid_multitouch snd_hwdep media bluetooth mei_me snd_seq lpc_ich mei snd_pcm snd_seq_device dw_dmac dw_dmac_core snd_timer snd soundcore ideapad_laptop sparse_keymap 8250_dw i2c_designware_platform mac_hid spi_pxa2xx_platform soc_button_array i2c_designware_core snd_soc_sst_acpi kvm_intel kvm parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq hid_sensor_custom hid_sensor_hub uas usb_storage bcache hid_generic usbhid [ 22.335682] rtsx_usb_sdmmc rtsx_usb i915 i2c_algo_bit drm_kms_helper drm psmouse ahci libahci sdhci_acpi sdhci video i2c_hid hid [ 22.335698] CPU: 0 PID: 2190 Comm: Xorg Tainted: GW 4.2.0-7-lowlatency #7-Ubuntu [ 22.335700] Hardware name: LENOVO 20344/INVALID, BIOS 96CN25WW(V1.11) 07/09/2014 [ 22.335703] c02081e8 8800995c77e8 817bdf25 [ 22.335708] 8800995c7838 8800995c7828 81078016 8800995c7858 [ 22.335712] 8800995c78c0 880035571000 0001 880035571350 [ 22.335717] Call Trace: [ 22.335724] [] dump_stack+0x4c/0x6e [ 22.335729] [] warn_slowpath_common+0x86/0xc0 [ 22.335734] [] warn_slowpath_fmt+0x46/0x50 [ 22.335758] [] ? intel_pipe_config_compare+0xb31/0xc60 [i915] [ 22.335781] [] check_crtc_state+0x2c5/0x440 [i915] [ 22.335809] [] intel_modeset_check_state+0x20e/0x6b0 [i915] [ 22.335834] [] intel_crtc_set_config+0x4c7/0x580 [i915] [ 22.335852] [] drm_mode_set_config_internal+0x66/0x100 [drm] [ 22.335870] [] drm_mode_setcrtc+0x3a8/0x4c0 [drm] [ 22.335883] [] drm_ioctl+0x125/0x610 [drm] [ 22.335898] [] ? drm_mode_setplane+0x1b0/0x1b0 [drm] [ 22.335903] [] do_vfs_ioctl+0x285/0x460 [ 22.335908] [] ? recalc_sigpending+0x1f/0x60 [ 22.335912] [] ? __fget+0x77/0xb0 [ 22.335916] [] SyS_ioctl+0x79/0x90 [ 22.335921] [] entry_SYSCALL_64_fastpath+0x16/0x75 [ 22.335924] ---[ end trace 7e8588f0d9eb10f9 ]--- ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1496433 Title: Error in i915 driver Status in linux package in Ubuntu: New Bug description: The 7th of september I lost my Xorg display on wily. I was always in failsafe mode. I still could get openbox to run, which was still loading i915, but didn't consume any 3D/advanced instruction I thinK. I didn't got too much time to go beyond. As I got also a btrfs kernel dump message, so I checked my ram at least with memtest86+, all was OK. Reverting to vivid allowed me to be back on unity. Wily-amd64, kernel 4.2.0.7-7-generic/low-latency Here are the traces I got: [ 22.335530] [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in ips_enabled (expected 1, found 0) [ 22.335535] [ cut here ] [
[Kernel-packages] [Bug 1496438] [NEW] 4.2.0.7 BUG: unable to handle kernel NULL pointer dereference at 0000000000000334
Public bug reported: I don't know how to reproduce this, as it worked for 2 weeks before happening, but was consistent then. I used btrfs on top of bcache on top of lvm. While trying to sbuild a package I got strange errors, got this messge in dmesg. Kernel 4.2.0-7-lowlatency release: wily: lsblk: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda8:00 465,8G 0 disk ├─hdd-Work 252:40 232,9G 0 lvm │ └─bcache0 251:00 232,9G 0 disk /home └─hdd-Home 252:50 232,9G 0 lvm └─bcache1 251:10 232,9G 0 disk /media/Work sdb8:16 0 238,5G 0 disk ├─sdb1 8:17 0 512M 0 part /boot/efi ├─sdb2 8:18 0 244M 0 part /boot └─sdb3 8:19 0 237,8G 0 part ├─ssd-root 252:0064G 0 lvm / ├─ssd-bcache 252:1064G 0 lvm │ ├─bcache0251:00 232,9G 0 disk /home │ └─bcache1251:10 232,9G 0 disk /media/Work ├─ssd-swap 252:20 8G 0 lvm │ └─cryptswap1 252:60 8G 0 crypt [SWAP] └─ssd-Free 252:30 101,8G 0 lvm /media/Free loop0 7:00 800M 0 loop └─secrets252:70 798M 0 crypt /home/kick/Secrets Kernel traces: [ 224.670454] BUG: unable to handle kernel NULL pointer dereference at 0334 [ 224.672387] IP: [] btrfs_sync_file+0xc1/0x360 [btrfs] [ 224.674261] PGD 8451a067 PUD 84527067 PMD 0 [ 224.676056] Oops: 0002 [#1] PREEMPT SMP [ 224.677810] Modules linked in: algif_skcipher af_alg ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables ip6_tables overlay xt_addrtype xt_conntrack xt_CHECKSUM ax88179_178a iptable_mangle usbnet ipt_MASQUERADE rtsx_usb_ms nf_nat_masquerade_ipv4 aufs iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 mii memstick nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc binfmt_misc iptable_filter ip_tables x_tables bnep drbg ansi_cprng dm_crypt nls_iso8859_1 intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul snd_soc_rt5640 glue_helper ablk_helper snd_soc_rl6231 cryptd snd_soc_core input_leds serio_raw hid_sensor_rotation snd_compress ac97_bus snd_pcm_dmaengine snd_seq_midi snd_seq_midi_event snd_hda_codec_realtek [ 224.683606] hid_sensor_incl_3d uvcvideo videobuf2_vmalloc snd_hda_codec_generic hid_sensor_als videobuf2_memops hid_sensor_magn_3d snd_hda_codec_hdmi hid_sensor_accel_3d hid_sensor_gyro_3d btusb hid_sensor_trigger btrtl industrialio_triggered_buffer btbcm snd_rawmidi joydev btintel videobuf2_core kfifo_buf snd_hda_intel industrialio snd_hda_codec hid_sensor_iio_common v4l2_common videodev snd_hda_core hid_multitouch snd_hwdep media bluetooth mei_me snd_seq lpc_ich mei snd_pcm snd_seq_device dw_dmac dw_dmac_core snd_timer snd soundcore ideapad_laptop sparse_keymap 8250_dw i2c_designware_platform mac_hid spi_pxa2xx_platform soc_button_array i2c_designware_core snd_soc_sst_acpi kvm_intel kvm parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq hid_sensor_custom hid_sensor_hub uas usb_storage bcache [ 224.689905] hid_generic usbhid rtsx_usb_sdmmc rtsx_usb i915 i2c_algo_bit drm_kms_helper drm psmouse ahci libahci sdhci_acpi sdhci video i2c_hid hid [ 224.694241] CPU: 1 PID: 2915 Comm: debconf-set-sel Tainted: GW 4.2.0-7-lowlatency #7-Ubuntu [ 224.696433] Hardware name: LENOVO 20344/INVALID, BIOS 96CN25WW(V1.11) 07/09/2014 [ 224.698641] task: 880099723800 ti: 88008451 task.ti: 88008451 [ 224.700843] RIP: 0010:[] [] btrfs_sync_file+0xc1/0x360 [btrfs] [ 224.703068] RSP: 0018:880084513e38 EFLAGS: 00010292 [ 224.705272] RAX: 880099723800 RBX: 880159625400 RCX: [ 224.707505] RDX: RSI: RDI: 880098237a58 [ 224.709733] RBP: 880084513eb8 R08: 0001 R09: 01f94ff0 [ 224.711962] R10: 009c R11: 0246 R12: 880098237a58 [ 224.714191] R13: 8800982379b0 R14: R15: [ 224.716431] FS: 7fdffa459700() GS:88015f24() knlGS: [ 224.718656] CS: 0010 DS: ES: CR0: 80050033 [ 224.720882] CR2: 0334 CR3: 8456a000 CR4: 001406e0 [ 224.723098] Stack: [ 224.725289] 880159625410 00020001 8000 8800981d7d80 [ 224.727494] 7fff 88009a803000 [ 224.729686] 1144 0002 880084513ea8 880159625400 [ 224.731860] Call Trace: [ 224.733994] [] vfs_fsync_range+0x4b/0xb0 [ 224.736142] [] do_fsync+0x3d/0x70 [ 224.738275] [] SyS_fsync+0x10/0x20 [ 224.740379] [] entry_SYSCALL_64_fastpath+0x16/0x75 [ 224.742476] Code: eb a1 e8 37 da cf c0 eb 9a 48 8b 45 a0 4c 8b 75 a8 4d 8d a5 a8 00 00 00 4c 89 e7 4c 29 f0 48 83 c0 01 48 89 45 90 e8 0f d4 4b c1 41
[Kernel-packages] [Bug 1377130] Re: Crash at creation of bcache if caching size backing size
Yes you can get rid of bcache0, but you can't re-use the device for anything unless you reboot ( re bcache or just plain fdisk/parted ). In fact whether you unmount before stopping the bcache or not doesn't change the behaviour. I did that this way in the description, to show the process. You just stop the caching device with the echo 1 ... But, the backing is still in use and you have no control over it. -- 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/1377130 Title: Crash at creation of bcache if caching size backing size Status in “bcache-tools” package in Ubuntu: New Status in “linux” package in Ubuntu: Incomplete Bug description: Hi, I found a bug that crashes the machine if you create a bcache where the caching device size is bigger than backing device. This case may happen if you create a bcache with a plan to add a bigger disk/partition/raid later to it. To reproduce it follow this steps: start a vm with utopic-amd64-desktop iso, it must have 2 disks, one of 16G and on of 8G apt-get update apt-get install bcache-tools /dev/sda is 16G caching device /dev/sdb is 8G backing device make-bcache --writeback --discard -C /dev/sda -B /dev/sdb now the machine is hanged! if you reboot and reinstall bcache-tools the bcache device has been created bcache-super-show -f /dev/sda: == sb.magicok sb.first_sector 8 [match] sb.csum 45C96B38A79275A7 [match] sb.version 0 [cache device] dev.label (empty) dev.uuid155ab65e-e74a-4ca8-91da-467ef696db63 dev.sectors_per_block 1 dev.sectors_per_bucket 1024 dev.cache.first_sector 1024 dev.cache.cache_sectors 33553408 dev.cache.total_sectors 33554432 dev.cache.ordered no dev.cache.discard yes dev.cache.pos 0 dev.cache.replacement 0 [lru] cset.uuid bcaa2595-bbc8-43a7-8c44-5d0aca0f3fc8 * bcache-super-show /dev/sdb: = sb.magicok sb.first_sector 8 [match] sb.csum F37A1BB08A7F5DE7 [match] sb.version 1 [backing device] dev.label (empty) dev.uuid341f1c83-1797-4157-aa9e-524107db5606 dev.sectors_per_block 1 dev.sectors_per_bucket 1024 dev.data.first_sector 16 dev.data.cache_mode 1 [writeback] dev.data.cache_state0 [detached] cset.uuid bcaa2595-bbc8-43a7-8c44-5d0aca0f3fc8 * you can format it: mkfs.ext4 /dev/bcache0 Rejet des blocs de périphérique : complété Creating filesystem with 2097150 4k blocks and 524288 inodes Filesystem UUID: b99a09de-3a92-4a44-82cd-29f75f8bf0c9 Superblocs de secours stockés sur les blocs : 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632 Allocation des tables de groupe : complété Écriture des tables d'i-noeuds : complété Création du journal (32768 blocs) : complété Écriture des superblocs et de l'information de comptabilité du système de fichiers : restarting the format gave me an other bug (X.org crashing): free from cli: total used free sharedbuffers cached Mem: 1017168 814040 203128 195568 91264 513064 -/+ buffers/cache: 209712 807456 Swap:0 0 0 tail /var/log/syslog: [ 568.016481] [ 4983] 0 4983 3332 121 110 0 mdadm [ 568.016483] [ 5259] 0 5259 6703 300 190 0 mkfs.ext4 [ 568.016484] Out of memory: Kill process 1947 (Xorg) score 38 or sacrifice child [ 568.016485] Killed process 1947 (Xorg) total-vm:313160kB, anon-rss:35976kB, file-rss:4232kB [ 568.707107] systemd-logind[1396]: Failed to start unit user@112.service: Unknown unit: user@112.service [ 568.707113] systemd-logind[1396]: Failed to start user service: Unknown unit: user@112.service [ 568.709876] systemd-logind[1396]: New session c8 of user lightdm. [ 568.709890] systemd-logind[1396]: Linked /tmp/.X11-unix/X0 to /run/user/112/X11-display. You can unregister the bcache device,but to re-use all disks, you'll need a reboot (cf bug 1377142): [ 830.811150] bcache: cached_dev_detach_finish() Caching disabled for sdb [ 830.949898] bcache: cache_set_free() Cache set bcaa2595-bbc8-43a7-8c44-5d0aca0f3fc8 unregistered To manage notifications about this bug go to:
Re: [Kernel-packages] [Bug 1377130] Re: Crash at creation of bcache if caching size backing size
Strange, I can reproduce each time, I'm using the iso: ubuntu-14.10-beta2-desktop-amd64.iso from http://releases.ubuntu.com/utopic/ I'm on utopic, with vrit-manager. Regards. Le 08/10/2014 13:17, Stefan Bader a écrit : +1 on the fail to reproduce. Followed the steps and everything worked without issues (using kvm/qemu VM with emulated devices and even sda being backed by a real ssd, but I am not sure the difference gets propagated). -- 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/1377130 Title: Crash at creation of bcache if caching size backing size Status in “bcache-tools” package in Ubuntu: New Status in “linux” package in Ubuntu: Incomplete Bug description: Hi, I found a bug that crashes the machine if you create a bcache where the caching device size is bigger than backing device. This case may happen if you create a bcache with a plan to add a bigger disk/partition/raid later to it. To reproduce it follow this steps: start a vm with utopic-amd64-desktop iso, it must have 2 disks, one of 16G and on of 8G apt-get update apt-get install bcache-tools /dev/sda is 16G caching device /dev/sdb is 8G backing device make-bcache --writeback --discard -C /dev/sda -B /dev/sdb now the machine is hanged! if you reboot and reinstall bcache-tools the bcache device has been created bcache-super-show -f /dev/sda: == sb.magicok sb.first_sector 8 [match] sb.csum 45C96B38A79275A7 [match] sb.version 0 [cache device] dev.label (empty) dev.uuid155ab65e-e74a-4ca8-91da-467ef696db63 dev.sectors_per_block 1 dev.sectors_per_bucket 1024 dev.cache.first_sector 1024 dev.cache.cache_sectors 33553408 dev.cache.total_sectors 33554432 dev.cache.ordered no dev.cache.discard yes dev.cache.pos 0 dev.cache.replacement 0 [lru] cset.uuid bcaa2595-bbc8-43a7-8c44-5d0aca0f3fc8 * bcache-super-show /dev/sdb: = sb.magicok sb.first_sector 8 [match] sb.csum F37A1BB08A7F5DE7 [match] sb.version 1 [backing device] dev.label (empty) dev.uuid341f1c83-1797-4157-aa9e-524107db5606 dev.sectors_per_block 1 dev.sectors_per_bucket 1024 dev.data.first_sector 16 dev.data.cache_mode 1 [writeback] dev.data.cache_state0 [detached] cset.uuid bcaa2595-bbc8-43a7-8c44-5d0aca0f3fc8 * you can format it: mkfs.ext4 /dev/bcache0 Rejet des blocs de périphérique : complété Creating filesystem with 2097150 4k blocks and 524288 inodes Filesystem UUID: b99a09de-3a92-4a44-82cd-29f75f8bf0c9 Superblocs de secours stockés sur les blocs : 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632 Allocation des tables de groupe : complété Écriture des tables d'i-noeuds : complété Création du journal (32768 blocs) : complété Écriture des superblocs et de l'information de comptabilité du système de fichiers : restarting the format gave me an other bug (X.org crashing): free from cli: total used free sharedbuffers cached Mem: 1017168 814040 203128 195568 91264 513064 -/+ buffers/cache: 209712 807456 Swap:0 0 0 tail /var/log/syslog: [ 568.016481] [ 4983] 0 4983 3332 121 110 0 mdadm [ 568.016483] [ 5259] 0 5259 6703 300 190 0 mkfs.ext4 [ 568.016484] Out of memory: Kill process 1947 (Xorg) score 38 or sacrifice child [ 568.016485] Killed process 1947 (Xorg) total-vm:313160kB, anon-rss:35976kB, file-rss:4232kB [ 568.707107] systemd-logind[1396]: Failed to start unit user@112.service: Unknown unit: user@112.service [ 568.707113] systemd-logind[1396]: Failed to start user service: Unknown unit: user@112.service [ 568.709876] systemd-logind[1396]: New session c8 of user lightdm. [ 568.709890] systemd-logind[1396]: Linked /tmp/.X11-unix/X0 to /run/user/112/X11-display. You can unregister the bcache device,but to re-use all disks, you'll need a reboot (cf bug 1377142): [ 830.811150] bcache: cached_dev_detach_finish() Caching disabled for sdb [ 830.949898] bcache: cache_set_free() Cache set bcaa2595-bbc8-43a7-8c44-5d0aca0f3fc8 unregistered To manage notifications about this bug go to:
Re: [Kernel-packages] [Bug 1377142] Re: Bcache doesn't allow full unregistering without rebooting
Yes you can get rid of bcache0, but you can't re-use the device for anything unless you reboot ( re bcache or just plain fdisk/parted ). Le 08/10/2014 13:15, Stefan Bader a écrit : There does not seem to be clear documentation on this. Just a note that from your description I was not completely sure whether you did unmount before starting the release procedure. I would say unmount is a must. Doing so, I also ended up in the state where bcache0 still existed. But I was able to get rid of that by echo 1 /sys/block/bcache0/bcache/stop -- 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/1377142 Title: Bcache doesn't allow full unregistering without rebooting Status in “bcache-tools” package in Ubuntu: New Status in “linux” package in Ubuntu: Incomplete Bug description: If you create a bcache device, you can't reuse all your disk/partitions without a reboot. You can reproduce the case this way: start a vm with 2 disks (caching must be bigger or equal to the backing cf bug :1377130) and an iso of utopic desktop amd64 create the bcache device: make-bcache --writeback --discard -C /dev/sda -B /dev/sdb UUID: b245150d-cfbe-4f90-836a-343e0e1a4c55 Set UUID: c990a31a-f531-4231-9603-d40230dc6504 version:0 nbuckets: 16384 block_size: 1 bucket_size:1024 nr_in_set: 1 nr_this_dev:0 first_bucket: 1 UUID: cc31e0bb-db29-4115-a1b2-e9ff54e5f127 Set UUID: c990a31a-f531-4231-9603-d40230dc6504 version:1 block_size: 1 data_offset:16 ** command: lsblk result: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:008G 0 disk └─bcache0 251:00 16G 0 disk sdb 8:16 0 16G 0 disk └─bcache0 251:00 16G 0 disk sr011:01 1,1G 0 rom /cdrom loop0 7:00 1,1G 1 loop /rofs ** All is good lsmod | grep bcache: bcache227884 3 format the bcache device: ** command: mkfs.ext4 /dev/bcache0 result: Rejet des blocs de périphérique :4096/4194302 complété Creating filesystem with 4194302 4k blocks and 1048576 inodes Filesystem UUID: 587d2249-3eaf-4590-a00d-42939f257e99 Superblocs de secours stockés sur les blocs : 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000 Allocation des tables de groupe : 0/128 complété Écriture des tables d'i-noeuds : 0/128 complété Création du journal (32768 blocs) : complété Écriture des superblocs et de l'information de comptabilité du système de fichiers : 0/128 2/128 complété ** Now mount it: mount /dev/bcache0 /mnt/ mkdir /mnt/test_dir touch /mnt/test_file state of: /sys/fs/bcache/ ls /sys/fs/bcache/ c990a31a-f531-4231-9603-d40230dc6504 register register_quiet bcache-super-show /dev/sda sb.magicok sb.first_sector 8 [match] sb.csum E6A8D9AC496B0B04 [match] sb.version 3 [cache device] dev.label (empty) dev.uuidb245150d-cfbe-4f90-836a-343e0e1a4c55 dev.sectors_per_block 1 dev.sectors_per_bucket 1024 dev.cache.first_sector 1024 dev.cache.cache_sectors 16776192 dev.cache.total_sectors 16777216 dev.cache.ordered yes dev.cache.discard yes dev.cache.pos 0 dev.cache.replacement 0 [lru] cset.uuid c990a31a-f531-4231-9603-d40230dc6504 ** bcache-super-show -f /dev/sdb sb.magicok sb.first_sector 8 [match] sb.csum 9600B159F36A67DD [match] sb.version 1 [backing device] dev.label (empty) dev.uuidcc31e0bb-db29-4115-a1b2-e9ff54e5f127 dev.sectors_per_block 1 dev.sectors_per_bucket 1024 dev.data.first_sector 16 dev.data.cache_mode 1 [writeback] dev.data.cache_state2 [dirty] cset.uuid c990a31a-f531-4231-9603-d40230dc6504 ** mount: /dev/bcache0 on /mnt type ext4 (rw) we will unregister the bcache: echo 1 /sys/fs/bcache/c990a31a-f531-4231-9603-d40230dc6504/unregister check the content of /sys/fs/bcache ls /sys/fs/bcache/ register register_quiet So bcache is unregistered, but status of /dev/sda: bcache-super-show -f /dev/sda sb.magicok sb.first_sector 8 [match] sb.csum
Re: [Kernel-packages] [Bug 1377142] Re: Bcache doesn't allow full unregistering without rebooting
In fact whether you unmount before stopping the bcache or not doesn't change the behaviour. I did that this way in the description, to show the process. You just stop the caching device with the echo 1 ... But, the backing is still in use, but you have no control over it. Le 08/10/2014 13:15, Stefan Bader a écrit : There does not seem to be clear documentation on this. Just a note that from your description I was not completely sure whether you did unmount before starting the release procedure. I would say unmount is a must. Doing so, I also ended up in the state where bcache0 still existed. But I was able to get rid of that by echo 1 /sys/block/bcache0/bcache/stop -- 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/1377142 Title: Bcache doesn't allow full unregistering without rebooting Status in “bcache-tools” package in Ubuntu: New Status in “linux” package in Ubuntu: Incomplete Bug description: If you create a bcache device, you can't reuse all your disk/partitions without a reboot. You can reproduce the case this way: start a vm with 2 disks (caching must be bigger or equal to the backing cf bug :1377130) and an iso of utopic desktop amd64 create the bcache device: make-bcache --writeback --discard -C /dev/sda -B /dev/sdb UUID: b245150d-cfbe-4f90-836a-343e0e1a4c55 Set UUID: c990a31a-f531-4231-9603-d40230dc6504 version:0 nbuckets: 16384 block_size: 1 bucket_size:1024 nr_in_set: 1 nr_this_dev:0 first_bucket: 1 UUID: cc31e0bb-db29-4115-a1b2-e9ff54e5f127 Set UUID: c990a31a-f531-4231-9603-d40230dc6504 version:1 block_size: 1 data_offset:16 ** command: lsblk result: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:008G 0 disk └─bcache0 251:00 16G 0 disk sdb 8:16 0 16G 0 disk └─bcache0 251:00 16G 0 disk sr011:01 1,1G 0 rom /cdrom loop0 7:00 1,1G 1 loop /rofs ** All is good lsmod | grep bcache: bcache227884 3 format the bcache device: ** command: mkfs.ext4 /dev/bcache0 result: Rejet des blocs de périphérique :4096/4194302 complété Creating filesystem with 4194302 4k blocks and 1048576 inodes Filesystem UUID: 587d2249-3eaf-4590-a00d-42939f257e99 Superblocs de secours stockés sur les blocs : 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000 Allocation des tables de groupe : 0/128 complété Écriture des tables d'i-noeuds : 0/128 complété Création du journal (32768 blocs) : complété Écriture des superblocs et de l'information de comptabilité du système de fichiers : 0/128 2/128 complété ** Now mount it: mount /dev/bcache0 /mnt/ mkdir /mnt/test_dir touch /mnt/test_file state of: /sys/fs/bcache/ ls /sys/fs/bcache/ c990a31a-f531-4231-9603-d40230dc6504 register register_quiet bcache-super-show /dev/sda sb.magicok sb.first_sector 8 [match] sb.csum E6A8D9AC496B0B04 [match] sb.version 3 [cache device] dev.label (empty) dev.uuidb245150d-cfbe-4f90-836a-343e0e1a4c55 dev.sectors_per_block 1 dev.sectors_per_bucket 1024 dev.cache.first_sector 1024 dev.cache.cache_sectors 16776192 dev.cache.total_sectors 16777216 dev.cache.ordered yes dev.cache.discard yes dev.cache.pos 0 dev.cache.replacement 0 [lru] cset.uuid c990a31a-f531-4231-9603-d40230dc6504 ** bcache-super-show -f /dev/sdb sb.magicok sb.first_sector 8 [match] sb.csum 9600B159F36A67DD [match] sb.version 1 [backing device] dev.label (empty) dev.uuidcc31e0bb-db29-4115-a1b2-e9ff54e5f127 dev.sectors_per_block 1 dev.sectors_per_bucket 1024 dev.data.first_sector 16 dev.data.cache_mode 1 [writeback] dev.data.cache_state2 [dirty] cset.uuid c990a31a-f531-4231-9603-d40230dc6504 ** mount: /dev/bcache0 on /mnt type ext4 (rw) we will unregister the bcache: echo 1 /sys/fs/bcache/c990a31a-f531-4231-9603-d40230dc6504/unregister check the content of /sys/fs/bcache ls /sys/fs/bcache/ register register_quiet So bcache is unregistered, but status
[Kernel-packages] [Bug 1377142] Re: Bcache doesn't allow full unregistering without rebooting
Thanks, I didn't wrote to /sys/block/bcache0/bcache/stop, I missed this as I was only looking in /dev/bcache* and in /sys/fs/bcache; which explains why I was left with an used device. I agree that the interface is not very user-fiendly, we may need to improve the bcache-tools command to simplify this. -- 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/1377142 Title: Bcache doesn't allow full unregistering without rebooting Status in “bcache-tools” package in Ubuntu: New Status in “linux” package in Ubuntu: Incomplete Bug description: If you create a bcache device, you can't reuse all your disk/partitions without a reboot. You can reproduce the case this way: start a vm with 2 disks (caching must be bigger or equal to the backing cf bug :1377130) and an iso of utopic desktop amd64 create the bcache device: make-bcache --writeback --discard -C /dev/sda -B /dev/sdb UUID: b245150d-cfbe-4f90-836a-343e0e1a4c55 Set UUID: c990a31a-f531-4231-9603-d40230dc6504 version:0 nbuckets: 16384 block_size: 1 bucket_size:1024 nr_in_set: 1 nr_this_dev:0 first_bucket: 1 UUID: cc31e0bb-db29-4115-a1b2-e9ff54e5f127 Set UUID: c990a31a-f531-4231-9603-d40230dc6504 version:1 block_size: 1 data_offset:16 ** command: lsblk result: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:008G 0 disk └─bcache0 251:00 16G 0 disk sdb 8:16 0 16G 0 disk └─bcache0 251:00 16G 0 disk sr011:01 1,1G 0 rom /cdrom loop0 7:00 1,1G 1 loop /rofs ** All is good lsmod | grep bcache: bcache227884 3 format the bcache device: ** command: mkfs.ext4 /dev/bcache0 result: Rejet des blocs de périphérique :4096/4194302 complété Creating filesystem with 4194302 4k blocks and 1048576 inodes Filesystem UUID: 587d2249-3eaf-4590-a00d-42939f257e99 Superblocs de secours stockés sur les blocs : 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000 Allocation des tables de groupe : 0/128 complété Écriture des tables d'i-noeuds : 0/128 complété Création du journal (32768 blocs) : complété Écriture des superblocs et de l'information de comptabilité du système de fichiers : 0/128 2/128 complété ** Now mount it: mount /dev/bcache0 /mnt/ mkdir /mnt/test_dir touch /mnt/test_file state of: /sys/fs/bcache/ ls /sys/fs/bcache/ c990a31a-f531-4231-9603-d40230dc6504 register register_quiet bcache-super-show /dev/sda sb.magicok sb.first_sector 8 [match] sb.csum E6A8D9AC496B0B04 [match] sb.version 3 [cache device] dev.label (empty) dev.uuidb245150d-cfbe-4f90-836a-343e0e1a4c55 dev.sectors_per_block 1 dev.sectors_per_bucket 1024 dev.cache.first_sector 1024 dev.cache.cache_sectors 16776192 dev.cache.total_sectors 16777216 dev.cache.ordered yes dev.cache.discard yes dev.cache.pos 0 dev.cache.replacement 0 [lru] cset.uuid c990a31a-f531-4231-9603-d40230dc6504 ** bcache-super-show -f /dev/sdb sb.magicok sb.first_sector 8 [match] sb.csum 9600B159F36A67DD [match] sb.version 1 [backing device] dev.label (empty) dev.uuidcc31e0bb-db29-4115-a1b2-e9ff54e5f127 dev.sectors_per_block 1 dev.sectors_per_bucket 1024 dev.data.first_sector 16 dev.data.cache_mode 1 [writeback] dev.data.cache_state2 [dirty] cset.uuid c990a31a-f531-4231-9603-d40230dc6504 ** mount: /dev/bcache0 on /mnt type ext4 (rw) we will unregister the bcache: echo 1 /sys/fs/bcache/c990a31a-f531-4231-9603-d40230dc6504/unregister check the content of /sys/fs/bcache ls /sys/fs/bcache/ register register_quiet So bcache is unregistered, but status of /dev/sda: bcache-super-show -f /dev/sda sb.magicok sb.first_sector 8 [match] sb.csum E6A8D9AC496B0B04 [match] sb.version 3 [cache device] dev.label (empty) dev.uuidb245150d-cfbe-4f90-836a-343e0e1a4c55 dev.sectors_per_block 1 dev.sectors_per_bucket 1024
[Kernel-packages] [Bug 1377130] [NEW] Crash at creation of bcache if caching size backing size
Public bug reported: Hi, I found a bug that crashes the machine if you create a bcache where the caching device size is bigger than backing device. This case may happen if you create a bcache with a plan to add a bigger disk/partition/raid later to it. To reproduce it follow this steps: start a vm with utopic-amd64-desktop iso, it must have 2 disks, one of 16G and on of 8G apt-get update apt-get install bcache-tools /dev/sda is 16G caching device /dev/sdb is 8G backing device make-bcache --write-back --discard -C /dev/sda -B /dev/sdb now the machine is hanged. if you reboot and reinstall bcache-tools the bcache device has been created bcache-super-show -f /dev/sda: == sb.magicok sb.first_sector 8 [match] sb.csum 45C96B38A79275A7 [match] sb.version 0 [cache device] dev.label (empty) dev.uuid155ab65e-e74a-4ca8-91da-467ef696db63 dev.sectors_per_block 1 dev.sectors_per_bucket 1024 dev.cache.first_sector 1024 dev.cache.cache_sectors 33553408 dev.cache.total_sectors 33554432 dev.cache.ordered no dev.cache.discard yes dev.cache.pos 0 dev.cache.replacement 0 [lru] cset.uuid bcaa2595-bbc8-43a7-8c44-5d0aca0f3fc8 * bcache-super-show /dev/sdb: = sb.magicok sb.first_sector 8 [match] sb.csum F37A1BB08A7F5DE7 [match] sb.version 1 [backing device] dev.label (empty) dev.uuid341f1c83-1797-4157-aa9e-524107db5606 dev.sectors_per_block 1 dev.sectors_per_bucket 1024 dev.data.first_sector 16 dev.data.cache_mode 1 [writeback] dev.data.cache_state0 [detached] cset.uuid bcaa2595-bbc8-43a7-8c44-5d0aca0f3fc8 * you can format it: mkfs.ext4 /dev/bcache0 Rejet des blocs de périphérique : complété Creating filesystem with 2097150 4k blocks and 524288 inodes Filesystem UUID: b99a09de-3a92-4a44-82cd-29f75f8bf0c9 Superblocs de secours stockés sur les blocs : 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632 Allocation des tables de groupe : complété Écriture des tables d'i-noeuds : complété Création du journal (32768 blocs) : complété Écriture des superblocs et de l'information de comptabilité du système de fichiers : restarting the format gave me an other bug (X.org crashing): free from cli: total used free sharedbuffers cached Mem: 1017168 814040 203128 195568 91264 513064 -/+ buffers/cache: 209712 807456 Swap:0 0 0 tail /var/log/syslog: [ 568.016481] [ 4983] 0 4983 3332 121 110 0 mdadm [ 568.016483] [ 5259] 0 5259 6703 300 190 0 mkfs.ext4 [ 568.016484] Out of memory: Kill process 1947 (Xorg) score 38 or sacrifice child [ 568.016485] Killed process 1947 (Xorg) total-vm:313160kB, anon-rss:35976kB, file-rss:4232kB [ 568.707107] systemd-logind[1396]: Failed to start unit user@112.service: Unknown unit: user@112.service [ 568.707113] systemd-logind[1396]: Failed to start user service: Unknown unit: user@112.service [ 568.709876] systemd-logind[1396]: New session c8 of user lightdm. [ 568.709890] systemd-logind[1396]: Linked /tmp/.X11-unix/X0 to /run/user/112/X11-display. You can unregister the bcache device: [ 830.811150] bcache: cached_dev_detach_finish() Caching disabled for sdb [ 830.949898] bcache: cache_set_free() Cache set bcaa2595-bbc8-43a7-8c44-5d0aca0f3fc8 unregistered ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Description changed: Hi, I found a bug that crashes the machine if you create a bcache where the - cahcing device size is bigger than backing device. + caching device size is bigger than backing device. + + This case may happen if you create a bcache with a plan to add a bigger + disk/partition/raid later to it. To reproduce it follow this steps: start a vm with utopic-amd64-desktop iso, it must have 2 disks, one of 16G and on of 8G apt-get update apt-get install bcache-tools /dev/sda is 16G caching device /dev/sdb is 8G backing device make-bcache --write-back --discard -C /dev/sda -B /dev/sdb now the machine is hanged. - if you reboot and reinstall bcache-tools + if you reboot and reinstall bcache-tools the bcache device has been created bcache-super-show -f /dev/sda: == sb.magic ok sb.first_sector 8 [match] sb.csum 45C96B38A79275A7 [match] sb.version0 [cache device] dev.label (empty) dev.uuid
[Kernel-packages] [Bug 1377142] Re: Bcache doesn't allow full unregistering without rebooting
** Description changed: If you create a bcache device, you can't reuse all your disk/partitions without a reboot. You can reproduce the case this way: start a vm with 2 disks (caching must be bigger or equal to the backing cf bug :1377130) and an iso of utopic desktop amd64 create the bcache device: - make-bcache --writeback --discard -C /dev/sda -B - /dev/sdb - - UUID: b245150d-cfbe-4f90-836a-343e0e1a4c55 - Set UUID: c990a31a-f531-4231-9603-d40230dc6504 - version:0 - nbuckets: 16384 - block_size: 1 - bucket_size:1024 - nr_in_set: 1 - nr_this_dev:0 - first_bucket: 1 - UUID: cc31e0bb-db29-4115-a1b2-e9ff54e5f127 - Set UUID: c990a31a-f531-4231-9603-d40230dc6504 - version:1 - block_size: 1 - data_offset:16 - - ** - command: - lsblk - - result: - NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT - sda 8:008G 0 disk - └─bcache0 251:00 16G 0 disk - sdb 8:16 0 16G 0 disk - └─bcache0 251:00 16G 0 disk - sr011:01 1,1G 0 rom /cdrom - loop0 7:00 1,1G 1 loop /rofs - ** + make-bcache --writeback --discard -C /dev/sda -B /dev/sdb + + UUID: b245150d-cfbe-4f90-836a-343e0e1a4c55 + Set UUID: c990a31a-f531-4231-9603-d40230dc6504 + version:0 + nbuckets: 16384 + block_size: 1 + bucket_size:1024 + nr_in_set: 1 + nr_this_dev:0 + first_bucket: 1 + UUID: cc31e0bb-db29-4115-a1b2-e9ff54e5f127 + Set UUID: c990a31a-f531-4231-9603-d40230dc6504 + version:1 + block_size: 1 + data_offset:16 + + ** + command: + lsblk + + result: + NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT + sda 8:008G 0 disk + └─bcache0 251:00 16G 0 disk + sdb 8:16 0 16G 0 disk + └─bcache0 251:00 16G 0 disk + sr011:01 1,1G 0 rom /cdrom + loop0 7:00 1,1G 1 loop /rofs + ** All is good - lsmod | grep bcache: - bcache227884 3 + lsmod | grep bcache: + bcache227884 3 format the bcache device: - ** - command: - mkfs.ext4 /dev/bcache0 - - result: - Rejet des blocs de périphérique :4096/4194302 complété - Creating filesystem with 4194302 4k blocks and 1048576 inodes - Filesystem UUID: 587d2249-3eaf-4590-a00d-42939f257e99 - Superblocs de secours stockés sur les blocs : - 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, - 4096000 - - Allocation des tables de groupe : 0/128 complété - Écriture des tables d'i-noeuds : 0/128 complété - Création du journal (32768 blocs) : complété - Écriture des superblocs et de l'information de comptabilité du système de - fichiers : 0/128 2/128 complété - - ** + ** + command: + mkfs.ext4 /dev/bcache0 + + result: + Rejet des blocs de périphérique :4096/4194302 complété + Creating filesystem with 4194302 4k blocks and 1048576 inodes + Filesystem UUID: 587d2249-3eaf-4590-a00d-42939f257e99 + Superblocs de secours stockés sur les blocs : + 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, + 4096000 + + Allocation des tables de groupe : 0/128 complété + Écriture des tables d'i-noeuds : 0/128 complété + Création du journal (32768 blocs) : complété + Écriture des superblocs et de l'information de comptabilité du système de + fichiers : 0/128 2/128 complété + + ** Now mount it: - mount /dev/bcache0 /mnt/ - mkdir /mnt/test_dir - touch /mnt/test_file + mount /dev/bcache0 /mnt/ + mkdir /mnt/test_dir + touch /mnt/test_file state of: /sys/fs/bcache/ - ls /sys/fs/bcache/ - -
[Kernel-packages] [Bug 1377130] Re: Crash at creation of bcache if caching size backing size
** Description changed: Hi, I found a bug that crashes the machine if you create a bcache where the caching device size is bigger than backing device. This case may happen if you create a bcache with a plan to add a bigger disk/partition/raid later to it. To reproduce it follow this steps: start a vm with utopic-amd64-desktop iso, it must have 2 disks, one of 16G and on of 8G - apt-get update apt-get install bcache-tools - /dev/sda is 16G caching device - /dev/sdb is 8G backing device + apt-get update apt-get install bcache-tools + /dev/sda is 16G caching device + /dev/sdb is 8G backing device - make-bcache --write-back --discard -C /dev/sda -B /dev/sdb - now the machine is hanged. + make-bcache --write-back --discard -C /dev/sda -B + /dev/sdb + + now the machine is hanged! if you reboot and reinstall bcache-tools the bcache device has been created - - bcache-super-show -f /dev/sda: - == - sb.magic ok - sb.first_sector 8 [match] - sb.csum 45C96B38A79275A7 [match] - sb.version0 [cache device] + + bcache-super-show -f /dev/sda: + == + sb.magicok + sb.first_sector 8 [match] + sb.csum 45C96B38A79275A7 [match] + sb.version 0 [cache device] - dev.label (empty) - dev.uuid 155ab65e-e74a-4ca8-91da-467ef696db63 - dev.sectors_per_block 1 - dev.sectors_per_bucket1024 - dev.cache.first_sector1024 - dev.cache.cache_sectors 33553408 - dev.cache.total_sectors 33554432 - dev.cache.ordered no - dev.cache.discard yes - dev.cache.pos 0 - dev.cache.replacement 0 [lru] + dev.label (empty) + dev.uuid155ab65e-e74a-4ca8-91da-467ef696db63 + dev.sectors_per_block 1 + dev.sectors_per_bucket 1024 + dev.cache.first_sector 1024 + dev.cache.cache_sectors 33553408 + dev.cache.total_sectors 33554432 + dev.cache.ordered no + dev.cache.discard yes + dev.cache.pos 0 + dev.cache.replacement 0 [lru] - cset.uuid bcaa2595-bbc8-43a7-8c44-5d0aca0f3fc8 + cset.uuid + bcaa2595-bbc8-43a7-8c44-5d0aca0f3fc8 - * - bcache-super-show /dev/sdb: - = - sb.magic ok - sb.first_sector 8 [match] - sb.csum F37A1BB08A7F5DE7 [match] - sb.version1 [backing device] + * + bcache-super-show /dev/sdb: + = + sb.magicok + sb.first_sector 8 [match] + sb.csum F37A1BB08A7F5DE7 [match] + sb.version 1 [backing device] - dev.label (empty) - dev.uuid 341f1c83-1797-4157-aa9e-524107db5606 - dev.sectors_per_block 1 - dev.sectors_per_bucket1024 - dev.data.first_sector 16 - dev.data.cache_mode 1 [writeback] - dev.data.cache_state 0 [detached] + dev.label (empty) + dev.uuid341f1c83-1797-4157-aa9e-524107db5606 + dev.sectors_per_block 1 + dev.sectors_per_bucket 1024 + dev.data.first_sector 16 + dev.data.cache_mode 1 [writeback] + dev.data.cache_state0 [detached] - cset.uuid bcaa2595-bbc8-43a7-8c44-5d0aca0f3fc8 - * + cset.uuid bcaa2595-bbc8-43a7-8c44-5d0aca0f3fc8 + * you can format it: - mkfs.ext4 /dev/bcache0 - Rejet des blocs de périphérique : complété - Creating filesystem with 2097150 4k blocks and 524288 inodes - Filesystem UUID: b99a09de-3a92-4a44-82cd-29f75f8bf0c9 - Superblocs de secours stockés sur les blocs : - 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632 + mkfs.ext4 /dev/bcache0 + Rejet des blocs de périphérique : complété + Creating filesystem with 2097150 4k blocks and 524288 inodes + Filesystem UUID: b99a09de-3a92-4a44-82cd-29f75f8bf0c9 + Superblocs de secours stockés sur les blocs : +32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632 - Allocation des tables de groupe :
[Kernel-packages] [Bug 1377142] [NEW] Bcache doesn't allow full unregistering without rebooting
Public bug reported: If you create a bcache device, you can't reuse all your disk/partitions without a reboot. You can reproduce the case this way: start a vm with 2 disks (caching must be bigger or equal to the backing cf bug :1377130) and an iso of utopic desktop amd64 create the bcache device: make-bcache --writeback --discard -C /dev/sda -B /dev/sdb UUID: b245150d-cfbe-4f90-836a-343e0e1a4c55 Set UUID: c990a31a-f531-4231-9603-d40230dc6504 version: 0 nbuckets: 16384 block_size: 1 bucket_size: 1024 nr_in_set:1 nr_this_dev: 0 first_bucket: 1 UUID: cc31e0bb-db29-4115-a1b2-e9ff54e5f127 Set UUID: c990a31a-f531-4231-9603-d40230dc6504 version: 1 block_size: 1 data_offset: 16 ** command: lsblk result: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:008G 0 disk └─bcache0 251:00 16G 0 disk sdb 8:16 0 16G 0 disk └─bcache0 251:00 16G 0 disk sr011:01 1,1G 0 rom /cdrom loop0 7:00 1,1G 1 loop /rofs ** All is good lsmod | grep bcache: bcache227884 3 format the bcache device: ** command: mkfs.ext4 /dev/bcache0 result: Rejet des blocs de périphérique :4096/4194302 complété Creating filesystem with 4194302 4k blocks and 1048576 inodes Filesystem UUID: 587d2249-3eaf-4590-a00d-42939f257e99 Superblocs de secours stockés sur les blocs : 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000 Allocation des tables de groupe : 0/128 complété Écriture des tables d'i-noeuds : 0/128 complété Création du journal (32768 blocs) : complété Écriture des superblocs et de l'information de comptabilité du système de fichiers : 0/128 2/128 complété ** Now mount it: mount /dev/bcache0 /mnt/ mkdir /mnt/test_dir touch /mnt/test_file state of: /sys/fs/bcache/ ls /sys/fs/bcache/ c990a31a-f531-4231-9603-d40230dc6504 register register_quiet bcache-super-show /dev/sda sb.magic ok sb.first_sector 8 [match] sb.csum E6A8D9AC496B0B04 [match] sb.version3 [cache device] dev.label (empty) dev.uuid b245150d-cfbe-4f90-836a-343e0e1a4c55 dev.sectors_per_block 1 dev.sectors_per_bucket1024 dev.cache.first_sector1024 dev.cache.cache_sectors 16776192 dev.cache.total_sectors 16777216 dev.cache.ordered yes dev.cache.discard yes dev.cache.pos 0 dev.cache.replacement 0 [lru] cset.uuid c990a31a-f531-4231-9603-d40230dc6504 ** bcache-super-show -f /dev/sdb sb.magic ok sb.first_sector 8 [match] sb.csum 9600B159F36A67DD [match] sb.version1 [backing device] dev.label (empty) dev.uuid cc31e0bb-db29-4115-a1b2-e9ff54e5f127 dev.sectors_per_block 1 dev.sectors_per_bucket1024 dev.data.first_sector 16 dev.data.cache_mode 1 [writeback] dev.data.cache_state 2 [dirty] cset.uuid c990a31a-f531-4231-9603-d40230dc6504 ** mount: /dev/bcache0 on /mnt type ext4 (rw) we will unregister the bcache: echo 1 /sys/fs/bcache/c990a31a-f531-4231-9603-d40230dc6504/unregister check the content of /sys/fs/bcache ls /sys/fs/bcache/ register register_quiet So bcache is unregistered, but status of /dev/sda: bcache-super-show -f /dev/sda sb.magic ok sb.first_sector 8 [match] sb.csum E6A8D9AC496B0B04 [match] sb.version3 [cache device] dev.label (empty) dev.uuid b245150d-cfbe-4f90-836a-343e0e1a4c55 dev.sectors_per_block 1 dev.sectors_per_bucket1024 dev.cache.first_sector1024 dev.cache.cache_sectors 16776192 dev.cache.total_sectors 16777216 dev.cache.ordered yes dev.cache.discard yes dev.cache.pos 0 dev.cache.replacement 0 [lru] cset.uuid c990a31a-f531-4231-9603-d40230dc6504 command: bcache-super-show -f /dev/sdb result: sb.magic ok sb.first_sector 8 [match] sb.csum D41799F794675FA8 [match] sb.version1 [backing device] dev.label (empty) dev.uuid cc31e0bb-db29-4115-a1b2-e9ff54e5f127 dev.sectors_per_block 1 dev.sectors_per_bucket1024 dev.data.first_sector 16 dev.data.cache_mode 1 [writeback] dev.data.cache_state 0 [detached] cset.uuid ----
[Kernel-packages] [Bug 1377130] Re: Crash at creation of bcache if caching size backing size
** Also affects: bcache-tools (Ubuntu) Importance: Undecided Status: New -- 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/1377130 Title: Crash at creation of bcache if caching size backing size Status in “bcache-tools” package in Ubuntu: New Status in “linux” package in Ubuntu: Incomplete Bug description: Hi, I found a bug that crashes the machine if you create a bcache where the caching device size is bigger than backing device. This case may happen if you create a bcache with a plan to add a bigger disk/partition/raid later to it. To reproduce it follow this steps: start a vm with utopic-amd64-desktop iso, it must have 2 disks, one of 16G and on of 8G apt-get update apt-get install bcache-tools /dev/sda is 16G caching device /dev/sdb is 8G backing device make-bcache --write-back --discard -C /dev/sda -B /dev/sdb now the machine is hanged! if you reboot and reinstall bcache-tools the bcache device has been created bcache-super-show -f /dev/sda: == sb.magicok sb.first_sector 8 [match] sb.csum 45C96B38A79275A7 [match] sb.version 0 [cache device] dev.label (empty) dev.uuid155ab65e-e74a-4ca8-91da-467ef696db63 dev.sectors_per_block 1 dev.sectors_per_bucket 1024 dev.cache.first_sector 1024 dev.cache.cache_sectors 33553408 dev.cache.total_sectors 33554432 dev.cache.ordered no dev.cache.discard yes dev.cache.pos 0 dev.cache.replacement 0 [lru] cset.uuid bcaa2595-bbc8-43a7-8c44-5d0aca0f3fc8 * bcache-super-show /dev/sdb: = sb.magicok sb.first_sector 8 [match] sb.csum F37A1BB08A7F5DE7 [match] sb.version 1 [backing device] dev.label (empty) dev.uuid341f1c83-1797-4157-aa9e-524107db5606 dev.sectors_per_block 1 dev.sectors_per_bucket 1024 dev.data.first_sector 16 dev.data.cache_mode 1 [writeback] dev.data.cache_state0 [detached] cset.uuid bcaa2595-bbc8-43a7-8c44-5d0aca0f3fc8 * you can format it: mkfs.ext4 /dev/bcache0 Rejet des blocs de périphérique : complété Creating filesystem with 2097150 4k blocks and 524288 inodes Filesystem UUID: b99a09de-3a92-4a44-82cd-29f75f8bf0c9 Superblocs de secours stockés sur les blocs : 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632 Allocation des tables de groupe : complété Écriture des tables d'i-noeuds : complété Création du journal (32768 blocs) : complété Écriture des superblocs et de l'information de comptabilité du système de fichiers : restarting the format gave me an other bug (X.org crashing): free from cli: total used free sharedbuffers cached Mem: 1017168 814040 203128 195568 91264 513064 -/+ buffers/cache: 209712 807456 Swap:0 0 0 tail /var/log/syslog: [ 568.016481] [ 4983] 0 4983 3332 121 11 0 0 mdadm [ 568.016483] [ 5259] 0 5259 6703 300 19 0 0 mkfs.ext4 [ 568.016484] Out of memory: Kill process 1947 (Xorg) score 38 or sacrifice child [ 568.016485] Killed process 1947 (Xorg) total-vm:313160kB, anon-rss:35976kB, file-rss:4232kB [ 568.707107] systemd-logind[1396]: Failed to start unit user@112.service: Unknown unit: user@112.service [ 568.707113] systemd-logind[1396]: Failed to start user service: Unknown unit: user@112.service [ 568.709876] systemd-logind[1396]: New session c8 of user lightdm. [ 568.709890] systemd-logind[1396]: Linked /tmp/.X11-unix/X0 to
[Kernel-packages] [Bug 1376661] Re: Strange behaviour of ahci driver (intel 82801 Mobile SATA Controller)
** Package changed: linux-ports-meta (Ubuntu) = linux (Ubuntu) -- 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/1376661 Title: Strange behaviour of ahci driver (intel 82801 Mobile SATA Controller) Status in “linux” package in Ubuntu: New Bug description: Hi, I have a MSI GS60E Ghost Pro laptop. It is quite complex: 2 SSD in raid 0 (intel Raid) 1 HDD standard SATA 2 Gpus (intel and nvidia) I was trying to upgrade my trusty to utopic. On trusty if I remember well there was no way to have a functionnal intel raid disks. I had to delete the raid an go to 2 separate disks to take advantage of the SSD (involved reinstalling secondary OS used for gaming). Legacy boot: On utopic, I can now use it but the name of the device is still strange (don't know if it is expected, but on other scsi harware I had I always had standard names /dev/sdx...): /dev/mapper/isw_ihbcddegh_SSD, where SSD is the name given at raid creation of the volume. Despite of this device I still have access to bare device /dev/sda, /dev/sdb, with the added bonus of being able to destroy the raid on it if we let the default /dev/sda for grub install of utopic desktop (destroyed at the end of install). At install time we see /dev/mapper/isw_ /dev/sda /dev/sdb and /dev/sdc, but it is readable on legacy installer even if not ideal. UEFI boot: If we boot on UEFI, it is more complex, as grub is not able to find the windows bootmanager for unknown reason (maybe not related). Don't know if I need to put it somewhere else, but at the install selection of disks and partitions, it is also a bit confusing as it show two devices for the raid /dev/mapper/isw_ each with the copy of the partitions (split the raid) plus bare devices, /dev/sda, /dev/sdb. I don't remember, if I saw partitions on the bare devices equaly. I can make some undestructive tests for you (had hard time at making a working install on this machine). If really needed, I can switch to work on an other laptop, and go for destructive tests. You can find some hardware infos about the config there, setup, etc: http://paste.ubuntu.com/8478288/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1376661/+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 1376661] RfKill.txt
apport information ** Attachment added: RfKill.txt https://bugs.launchpad.net/bugs/1376661/+attachment/480/+files/RfKill.txt -- 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/1376661 Title: Strange behaviour of ahci driver (intel 82801 Mobile SATA Controller) Status in “linux” package in Ubuntu: Incomplete Bug description: Hi, I have a MSI GS60E Ghost Pro laptop. It is quite complex: 2 SSD in raid 0 (intel Raid) 1 HDD standard SATA 2 Gpus (intel and nvidia) I was trying to upgrade my trusty to utopic. On trusty if I remember well there was no way to have a functionnal intel raid disks. I had to delete the raid an go to 2 separate disks to take advantage of the SSD (involved reinstalling secondary OS used for gaming). Legacy boot: On utopic, I can now use it but the name of the device is still strange (don't know if it is expected, but on other scsi harware I had I always had standard names /dev/sdx...): /dev/mapper/isw_ihbcddegh_SSD, where SSD is the name given at raid creation of the volume. Despite of this device I still have access to bare device /dev/sda, /dev/sdb, with the added bonus of being able to destroy the raid on it if we let the default /dev/sda for grub install of utopic desktop (destroyed at the end of install). At install time we see /dev/mapper/isw_ /dev/sda /dev/sdb and /dev/sdc, but it is readable on legacy installer even if not ideal. UEFI boot: If we boot on UEFI, it is more complex, as grub is not able to find the windows bootmanager for unknown reason (maybe not related). Don't know if I need to put it somewhere else, but at the install selection of disks and partitions, it is also a bit confusing as it show two devices for the raid /dev/mapper/isw_ each with the copy of the partitions (split the raid) plus bare devices, /dev/sda, /dev/sdb. I don't remember, if I saw partitions on the bare devices equaly. I can make some undestructive tests for you (had hard time at making a working install on this machine). If really needed, I can switch to work on an other laptop, and go for destructive tests. You can find some hardware infos about the config there, setup, etc: http://paste.ubuntu.com/8478288/ --- ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kick 3322 F pulseaudio /dev/snd/controlC2: kick 3322 F pulseaudio /dev/snd/controlC1: kick 3322 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=46a8dc48-0696-4cc1-9ba5-6718ccae8802 InstallationDate: Installed on 2014-10-01 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140923) MachineType: Micro-Star International Co., Ltd. GS60 2PE Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-17-generic root=UUID=71fadb93-5ab3-4fab-98d7-e558816e33a0 ro quiet splash blacklist=nouveau ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3 RelatedPackageVersions: linux-restricted-modules-3.16.0-17-generic N/A linux-backports-modules-3.16.0-17-generic N/A linux-firmware 1.134 Tags: utopic Uname: Linux 3.16.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/16/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16H2IMS.10B dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-16H2 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.B dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16H2IMS.10B:bd08/16/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS602PE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16H2:rvrREV0.B:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GS60 2PE dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1376661/+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 1376661] IwConfig.txt
apport information ** Attachment added: IwConfig.txt https://bugs.launchpad.net/bugs/1376661/+attachment/472/+files/IwConfig.txt -- 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/1376661 Title: Strange behaviour of ahci driver (intel 82801 Mobile SATA Controller) Status in “linux” package in Ubuntu: Incomplete Bug description: Hi, I have a MSI GS60E Ghost Pro laptop. It is quite complex: 2 SSD in raid 0 (intel Raid) 1 HDD standard SATA 2 Gpus (intel and nvidia) I was trying to upgrade my trusty to utopic. On trusty if I remember well there was no way to have a functionnal intel raid disks. I had to delete the raid an go to 2 separate disks to take advantage of the SSD (involved reinstalling secondary OS used for gaming). Legacy boot: On utopic, I can now use it but the name of the device is still strange (don't know if it is expected, but on other scsi harware I had I always had standard names /dev/sdx...): /dev/mapper/isw_ihbcddegh_SSD, where SSD is the name given at raid creation of the volume. Despite of this device I still have access to bare device /dev/sda, /dev/sdb, with the added bonus of being able to destroy the raid on it if we let the default /dev/sda for grub install of utopic desktop (destroyed at the end of install). At install time we see /dev/mapper/isw_ /dev/sda /dev/sdb and /dev/sdc, but it is readable on legacy installer even if not ideal. UEFI boot: If we boot on UEFI, it is more complex, as grub is not able to find the windows bootmanager for unknown reason (maybe not related). Don't know if I need to put it somewhere else, but at the install selection of disks and partitions, it is also a bit confusing as it show two devices for the raid /dev/mapper/isw_ each with the copy of the partitions (split the raid) plus bare devices, /dev/sda, /dev/sdb. I don't remember, if I saw partitions on the bare devices equaly. I can make some undestructive tests for you (had hard time at making a working install on this machine). If really needed, I can switch to work on an other laptop, and go for destructive tests. You can find some hardware infos about the config there, setup, etc: http://paste.ubuntu.com/8478288/ --- ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kick 3322 F pulseaudio /dev/snd/controlC2: kick 3322 F pulseaudio /dev/snd/controlC1: kick 3322 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=46a8dc48-0696-4cc1-9ba5-6718ccae8802 InstallationDate: Installed on 2014-10-01 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140923) MachineType: Micro-Star International Co., Ltd. GS60 2PE Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-17-generic root=UUID=71fadb93-5ab3-4fab-98d7-e558816e33a0 ro quiet splash blacklist=nouveau ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3 RelatedPackageVersions: linux-restricted-modules-3.16.0-17-generic N/A linux-backports-modules-3.16.0-17-generic N/A linux-firmware 1.134 Tags: utopic Uname: Linux 3.16.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/16/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16H2IMS.10B dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-16H2 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.B dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16H2IMS.10B:bd08/16/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS602PE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16H2:rvrREV0.B:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GS60 2PE dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1376661/+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 1376661] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1376661/+attachment/476/+files/ProcEnviron.txt -- 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/1376661 Title: Strange behaviour of ahci driver (intel 82801 Mobile SATA Controller) Status in “linux” package in Ubuntu: Incomplete Bug description: Hi, I have a MSI GS60E Ghost Pro laptop. It is quite complex: 2 SSD in raid 0 (intel Raid) 1 HDD standard SATA 2 Gpus (intel and nvidia) I was trying to upgrade my trusty to utopic. On trusty if I remember well there was no way to have a functionnal intel raid disks. I had to delete the raid an go to 2 separate disks to take advantage of the SSD (involved reinstalling secondary OS used for gaming). Legacy boot: On utopic, I can now use it but the name of the device is still strange (don't know if it is expected, but on other scsi harware I had I always had standard names /dev/sdx...): /dev/mapper/isw_ihbcddegh_SSD, where SSD is the name given at raid creation of the volume. Despite of this device I still have access to bare device /dev/sda, /dev/sdb, with the added bonus of being able to destroy the raid on it if we let the default /dev/sda for grub install of utopic desktop (destroyed at the end of install). At install time we see /dev/mapper/isw_ /dev/sda /dev/sdb and /dev/sdc, but it is readable on legacy installer even if not ideal. UEFI boot: If we boot on UEFI, it is more complex, as grub is not able to find the windows bootmanager for unknown reason (maybe not related). Don't know if I need to put it somewhere else, but at the install selection of disks and partitions, it is also a bit confusing as it show two devices for the raid /dev/mapper/isw_ each with the copy of the partitions (split the raid) plus bare devices, /dev/sda, /dev/sdb. I don't remember, if I saw partitions on the bare devices equaly. I can make some undestructive tests for you (had hard time at making a working install on this machine). If really needed, I can switch to work on an other laptop, and go for destructive tests. You can find some hardware infos about the config there, setup, etc: http://paste.ubuntu.com/8478288/ --- ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kick 3322 F pulseaudio /dev/snd/controlC2: kick 3322 F pulseaudio /dev/snd/controlC1: kick 3322 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=46a8dc48-0696-4cc1-9ba5-6718ccae8802 InstallationDate: Installed on 2014-10-01 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140923) MachineType: Micro-Star International Co., Ltd. GS60 2PE Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-17-generic root=UUID=71fadb93-5ab3-4fab-98d7-e558816e33a0 ro quiet splash blacklist=nouveau ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3 RelatedPackageVersions: linux-restricted-modules-3.16.0-17-generic N/A linux-backports-modules-3.16.0-17-generic N/A linux-firmware 1.134 Tags: utopic Uname: Linux 3.16.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/16/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16H2IMS.10B dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-16H2 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.B dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16H2IMS.10B:bd08/16/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS602PE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16H2:rvrREV0.B:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GS60 2PE dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1376661/+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 1376661] WifiSyslog.txt
apport information ** Attachment added: WifiSyslog.txt https://bugs.launchpad.net/bugs/1376661/+attachment/483/+files/WifiSyslog.txt -- 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/1376661 Title: Strange behaviour of ahci driver (intel 82801 Mobile SATA Controller) Status in “linux” package in Ubuntu: Incomplete Bug description: Hi, I have a MSI GS60E Ghost Pro laptop. It is quite complex: 2 SSD in raid 0 (intel Raid) 1 HDD standard SATA 2 Gpus (intel and nvidia) I was trying to upgrade my trusty to utopic. On trusty if I remember well there was no way to have a functionnal intel raid disks. I had to delete the raid an go to 2 separate disks to take advantage of the SSD (involved reinstalling secondary OS used for gaming). Legacy boot: On utopic, I can now use it but the name of the device is still strange (don't know if it is expected, but on other scsi harware I had I always had standard names /dev/sdx...): /dev/mapper/isw_ihbcddegh_SSD, where SSD is the name given at raid creation of the volume. Despite of this device I still have access to bare device /dev/sda, /dev/sdb, with the added bonus of being able to destroy the raid on it if we let the default /dev/sda for grub install of utopic desktop (destroyed at the end of install). At install time we see /dev/mapper/isw_ /dev/sda /dev/sdb and /dev/sdc, but it is readable on legacy installer even if not ideal. UEFI boot: If we boot on UEFI, it is more complex, as grub is not able to find the windows bootmanager for unknown reason (maybe not related). Don't know if I need to put it somewhere else, but at the install selection of disks and partitions, it is also a bit confusing as it show two devices for the raid /dev/mapper/isw_ each with the copy of the partitions (split the raid) plus bare devices, /dev/sda, /dev/sdb. I don't remember, if I saw partitions on the bare devices equaly. I can make some undestructive tests for you (had hard time at making a working install on this machine). If really needed, I can switch to work on an other laptop, and go for destructive tests. You can find some hardware infos about the config there, setup, etc: http://paste.ubuntu.com/8478288/ --- ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kick 3322 F pulseaudio /dev/snd/controlC2: kick 3322 F pulseaudio /dev/snd/controlC1: kick 3322 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=46a8dc48-0696-4cc1-9ba5-6718ccae8802 InstallationDate: Installed on 2014-10-01 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140923) MachineType: Micro-Star International Co., Ltd. GS60 2PE Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-17-generic root=UUID=71fadb93-5ab3-4fab-98d7-e558816e33a0 ro quiet splash blacklist=nouveau ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3 RelatedPackageVersions: linux-restricted-modules-3.16.0-17-generic N/A linux-backports-modules-3.16.0-17-generic N/A linux-firmware 1.134 Tags: utopic Uname: Linux 3.16.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/16/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16H2IMS.10B dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-16H2 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.B dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16H2IMS.10B:bd08/16/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS602PE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16H2:rvrREV0.B:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GS60 2PE dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1376661/+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 1376661] Re: Strange behaviour of ahci driver (intel 82801 Mobile SATA Controller)
apport information ** Tags added: apport-collected utopic ** Description changed: Hi, I have a MSI GS60E Ghost Pro laptop. It is quite complex: 2 SSD in raid 0 (intel Raid) 1 HDD standard SATA 2 Gpus (intel and nvidia) I was trying to upgrade my trusty to utopic. On trusty if I remember well there was no way to have a functionnal intel raid disks. I had to delete the raid an go to 2 separate disks to take advantage of the SSD (involved reinstalling secondary OS used for gaming). Legacy boot: On utopic, I can now use it but the name of the device is still strange (don't know if it is expected, but on other scsi harware I had I always had standard names /dev/sdx...): /dev/mapper/isw_ihbcddegh_SSD, where SSD is the name given at raid creation of the volume. Despite of this device I still have access to bare device /dev/sda, /dev/sdb, with the added bonus of being able to destroy the raid on it if we let the default /dev/sda for grub install of utopic desktop (destroyed at the end of install). At install time we see /dev/mapper/isw_ /dev/sda /dev/sdb and /dev/sdc, but it is readable on legacy installer even if not ideal. UEFI boot: If we boot on UEFI, it is more complex, as grub is not able to find the windows bootmanager for unknown reason (maybe not related). Don't know if I need to put it somewhere else, but at the install selection of disks and partitions, it is also a bit confusing as it show two devices for the raid /dev/mapper/isw_ each with the copy of the partitions (split the raid) plus bare devices, /dev/sda, /dev/sdb. I don't remember, if I saw partitions on the bare devices equaly. I can make some undestructive tests for you (had hard time at making a working install on this machine). If really needed, I can switch to work on an other laptop, and go for destructive tests. You can find some hardware infos about the config there, setup, etc: http://paste.ubuntu.com/8478288/ + --- + ApportVersion: 2.14.7-0ubuntu2 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: kick 3322 F pulseaudio + /dev/snd/controlC2: kick 3322 F pulseaudio + /dev/snd/controlC1: kick 3322 F pulseaudio + CurrentDesktop: Unity + DistroRelease: Ubuntu 14.10 + HibernationDevice: RESUME=UUID=46a8dc48-0696-4cc1-9ba5-6718ccae8802 + InstallationDate: Installed on 2014-10-01 (0 days ago) + InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140923) + MachineType: Micro-Star International Co., Ltd. GS60 2PE + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-17-generic root=UUID=71fadb93-5ab3-4fab-98d7-e558816e33a0 ro quiet splash blacklist=nouveau + ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3 + RelatedPackageVersions: + linux-restricted-modules-3.16.0-17-generic N/A + linux-backports-modules-3.16.0-17-generic N/A + linux-firmware 1.134 + Tags: utopic + Uname: Linux 3.16.0-17-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 08/16/2014 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: E16H2IMS.10B + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: MS-16H2 + dmi.board.vendor: Micro-Star International Co., Ltd. + dmi.board.version: REV:0.B + dmi.chassis.asset.tag: To Be Filled By O.E.M. + dmi.chassis.type: 3 + dmi.chassis.vendor: To Be Filled By O.E.M. + dmi.chassis.version: To Be Filled By O.E.M. + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16H2IMS.10B:bd08/16/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS602PE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16H2:rvrREV0.B:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: + dmi.product.name: GS60 2PE + dmi.product.version: REV:1.0 + dmi.sys.vendor: Micro-Star International Co., Ltd. ** Attachment added: AlsaInfo.txt https://bugs.launchpad.net/bugs/1376661/+attachment/468/+files/AlsaInfo.txt -- 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/1376661 Title: Strange behaviour of ahci driver (intel 82801 Mobile SATA Controller) Status in “linux” package in Ubuntu: Incomplete Bug description: Hi, I have a MSI GS60E Ghost Pro laptop. It is quite complex: 2 SSD in raid 0 (intel Raid) 1 HDD standard SATA 2 Gpus (intel and nvidia) I was trying to upgrade my trusty to utopic. On trusty if I remember well there was no way to have a functionnal intel raid disks. I had to delete the raid an go to 2 separate disks to take advantage of the SSD (involved reinstalling secondary OS used for gaming). Legacy boot: On utopic, I can now use it but the name of the device is still strange
[Kernel-packages] [Bug 1376661] BootDmesg.txt
apport information ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/1376661/+attachment/469/+files/BootDmesg.txt -- 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/1376661 Title: Strange behaviour of ahci driver (intel 82801 Mobile SATA Controller) Status in “linux” package in Ubuntu: Incomplete Bug description: Hi, I have a MSI GS60E Ghost Pro laptop. It is quite complex: 2 SSD in raid 0 (intel Raid) 1 HDD standard SATA 2 Gpus (intel and nvidia) I was trying to upgrade my trusty to utopic. On trusty if I remember well there was no way to have a functionnal intel raid disks. I had to delete the raid an go to 2 separate disks to take advantage of the SSD (involved reinstalling secondary OS used for gaming). Legacy boot: On utopic, I can now use it but the name of the device is still strange (don't know if it is expected, but on other scsi harware I had I always had standard names /dev/sdx...): /dev/mapper/isw_ihbcddegh_SSD, where SSD is the name given at raid creation of the volume. Despite of this device I still have access to bare device /dev/sda, /dev/sdb, with the added bonus of being able to destroy the raid on it if we let the default /dev/sda for grub install of utopic desktop (destroyed at the end of install). At install time we see /dev/mapper/isw_ /dev/sda /dev/sdb and /dev/sdc, but it is readable on legacy installer even if not ideal. UEFI boot: If we boot on UEFI, it is more complex, as grub is not able to find the windows bootmanager for unknown reason (maybe not related). Don't know if I need to put it somewhere else, but at the install selection of disks and partitions, it is also a bit confusing as it show two devices for the raid /dev/mapper/isw_ each with the copy of the partitions (split the raid) plus bare devices, /dev/sda, /dev/sdb. I don't remember, if I saw partitions on the bare devices equaly. I can make some undestructive tests for you (had hard time at making a working install on this machine). If really needed, I can switch to work on an other laptop, and go for destructive tests. You can find some hardware infos about the config there, setup, etc: http://paste.ubuntu.com/8478288/ --- ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kick 3322 F pulseaudio /dev/snd/controlC2: kick 3322 F pulseaudio /dev/snd/controlC1: kick 3322 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=46a8dc48-0696-4cc1-9ba5-6718ccae8802 InstallationDate: Installed on 2014-10-01 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140923) MachineType: Micro-Star International Co., Ltd. GS60 2PE Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-17-generic root=UUID=71fadb93-5ab3-4fab-98d7-e558816e33a0 ro quiet splash blacklist=nouveau ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3 RelatedPackageVersions: linux-restricted-modules-3.16.0-17-generic N/A linux-backports-modules-3.16.0-17-generic N/A linux-firmware 1.134 Tags: utopic Uname: Linux 3.16.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/16/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16H2IMS.10B dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-16H2 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.B dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16H2IMS.10B:bd08/16/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS602PE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16H2:rvrREV0.B:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GS60 2PE dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1376661/+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 1376661] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/1376661/+attachment/477/+files/ProcInterrupts.txt -- 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/1376661 Title: Strange behaviour of ahci driver (intel 82801 Mobile SATA Controller) Status in “linux” package in Ubuntu: Incomplete Bug description: Hi, I have a MSI GS60E Ghost Pro laptop. It is quite complex: 2 SSD in raid 0 (intel Raid) 1 HDD standard SATA 2 Gpus (intel and nvidia) I was trying to upgrade my trusty to utopic. On trusty if I remember well there was no way to have a functionnal intel raid disks. I had to delete the raid an go to 2 separate disks to take advantage of the SSD (involved reinstalling secondary OS used for gaming). Legacy boot: On utopic, I can now use it but the name of the device is still strange (don't know if it is expected, but on other scsi harware I had I always had standard names /dev/sdx...): /dev/mapper/isw_ihbcddegh_SSD, where SSD is the name given at raid creation of the volume. Despite of this device I still have access to bare device /dev/sda, /dev/sdb, with the added bonus of being able to destroy the raid on it if we let the default /dev/sda for grub install of utopic desktop (destroyed at the end of install). At install time we see /dev/mapper/isw_ /dev/sda /dev/sdb and /dev/sdc, but it is readable on legacy installer even if not ideal. UEFI boot: If we boot on UEFI, it is more complex, as grub is not able to find the windows bootmanager for unknown reason (maybe not related). Don't know if I need to put it somewhere else, but at the install selection of disks and partitions, it is also a bit confusing as it show two devices for the raid /dev/mapper/isw_ each with the copy of the partitions (split the raid) plus bare devices, /dev/sda, /dev/sdb. I don't remember, if I saw partitions on the bare devices equaly. I can make some undestructive tests for you (had hard time at making a working install on this machine). If really needed, I can switch to work on an other laptop, and go for destructive tests. You can find some hardware infos about the config there, setup, etc: http://paste.ubuntu.com/8478288/ --- ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kick 3322 F pulseaudio /dev/snd/controlC2: kick 3322 F pulseaudio /dev/snd/controlC1: kick 3322 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=46a8dc48-0696-4cc1-9ba5-6718ccae8802 InstallationDate: Installed on 2014-10-01 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140923) MachineType: Micro-Star International Co., Ltd. GS60 2PE Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-17-generic root=UUID=71fadb93-5ab3-4fab-98d7-e558816e33a0 ro quiet splash blacklist=nouveau ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3 RelatedPackageVersions: linux-restricted-modules-3.16.0-17-generic N/A linux-backports-modules-3.16.0-17-generic N/A linux-firmware 1.134 Tags: utopic Uname: Linux 3.16.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/16/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16H2IMS.10B dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-16H2 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.B dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16H2IMS.10B:bd08/16/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS602PE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16H2:rvrREV0.B:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GS60 2PE dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1376661/+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 1376661] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/1376661/+attachment/474/+files/Lsusb.txt -- 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/1376661 Title: Strange behaviour of ahci driver (intel 82801 Mobile SATA Controller) Status in “linux” package in Ubuntu: Incomplete Bug description: Hi, I have a MSI GS60E Ghost Pro laptop. It is quite complex: 2 SSD in raid 0 (intel Raid) 1 HDD standard SATA 2 Gpus (intel and nvidia) I was trying to upgrade my trusty to utopic. On trusty if I remember well there was no way to have a functionnal intel raid disks. I had to delete the raid an go to 2 separate disks to take advantage of the SSD (involved reinstalling secondary OS used for gaming). Legacy boot: On utopic, I can now use it but the name of the device is still strange (don't know if it is expected, but on other scsi harware I had I always had standard names /dev/sdx...): /dev/mapper/isw_ihbcddegh_SSD, where SSD is the name given at raid creation of the volume. Despite of this device I still have access to bare device /dev/sda, /dev/sdb, with the added bonus of being able to destroy the raid on it if we let the default /dev/sda for grub install of utopic desktop (destroyed at the end of install). At install time we see /dev/mapper/isw_ /dev/sda /dev/sdb and /dev/sdc, but it is readable on legacy installer even if not ideal. UEFI boot: If we boot on UEFI, it is more complex, as grub is not able to find the windows bootmanager for unknown reason (maybe not related). Don't know if I need to put it somewhere else, but at the install selection of disks and partitions, it is also a bit confusing as it show two devices for the raid /dev/mapper/isw_ each with the copy of the partitions (split the raid) plus bare devices, /dev/sda, /dev/sdb. I don't remember, if I saw partitions on the bare devices equaly. I can make some undestructive tests for you (had hard time at making a working install on this machine). If really needed, I can switch to work on an other laptop, and go for destructive tests. You can find some hardware infos about the config there, setup, etc: http://paste.ubuntu.com/8478288/ --- ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kick 3322 F pulseaudio /dev/snd/controlC2: kick 3322 F pulseaudio /dev/snd/controlC1: kick 3322 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=46a8dc48-0696-4cc1-9ba5-6718ccae8802 InstallationDate: Installed on 2014-10-01 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140923) MachineType: Micro-Star International Co., Ltd. GS60 2PE Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-17-generic root=UUID=71fadb93-5ab3-4fab-98d7-e558816e33a0 ro quiet splash blacklist=nouveau ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3 RelatedPackageVersions: linux-restricted-modules-3.16.0-17-generic N/A linux-backports-modules-3.16.0-17-generic N/A linux-firmware 1.134 Tags: utopic Uname: Linux 3.16.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/16/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16H2IMS.10B dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-16H2 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.B dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16H2IMS.10B:bd08/16/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS602PE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16H2:rvrREV0.B:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GS60 2PE dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1376661/+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 1376661] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1376661/+attachment/481/+files/UdevDb.txt -- 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/1376661 Title: Strange behaviour of ahci driver (intel 82801 Mobile SATA Controller) Status in “linux” package in Ubuntu: Incomplete Bug description: Hi, I have a MSI GS60E Ghost Pro laptop. It is quite complex: 2 SSD in raid 0 (intel Raid) 1 HDD standard SATA 2 Gpus (intel and nvidia) I was trying to upgrade my trusty to utopic. On trusty if I remember well there was no way to have a functionnal intel raid disks. I had to delete the raid an go to 2 separate disks to take advantage of the SSD (involved reinstalling secondary OS used for gaming). Legacy boot: On utopic, I can now use it but the name of the device is still strange (don't know if it is expected, but on other scsi harware I had I always had standard names /dev/sdx...): /dev/mapper/isw_ihbcddegh_SSD, where SSD is the name given at raid creation of the volume. Despite of this device I still have access to bare device /dev/sda, /dev/sdb, with the added bonus of being able to destroy the raid on it if we let the default /dev/sda for grub install of utopic desktop (destroyed at the end of install). At install time we see /dev/mapper/isw_ /dev/sda /dev/sdb and /dev/sdc, but it is readable on legacy installer even if not ideal. UEFI boot: If we boot on UEFI, it is more complex, as grub is not able to find the windows bootmanager for unknown reason (maybe not related). Don't know if I need to put it somewhere else, but at the install selection of disks and partitions, it is also a bit confusing as it show two devices for the raid /dev/mapper/isw_ each with the copy of the partitions (split the raid) plus bare devices, /dev/sda, /dev/sdb. I don't remember, if I saw partitions on the bare devices equaly. I can make some undestructive tests for you (had hard time at making a working install on this machine). If really needed, I can switch to work on an other laptop, and go for destructive tests. You can find some hardware infos about the config there, setup, etc: http://paste.ubuntu.com/8478288/ --- ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kick 3322 F pulseaudio /dev/snd/controlC2: kick 3322 F pulseaudio /dev/snd/controlC1: kick 3322 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=46a8dc48-0696-4cc1-9ba5-6718ccae8802 InstallationDate: Installed on 2014-10-01 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140923) MachineType: Micro-Star International Co., Ltd. GS60 2PE Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-17-generic root=UUID=71fadb93-5ab3-4fab-98d7-e558816e33a0 ro quiet splash blacklist=nouveau ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3 RelatedPackageVersions: linux-restricted-modules-3.16.0-17-generic N/A linux-backports-modules-3.16.0-17-generic N/A linux-firmware 1.134 Tags: utopic Uname: Linux 3.16.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/16/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16H2IMS.10B dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-16H2 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.B dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16H2IMS.10B:bd08/16/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS602PE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16H2:rvrREV0.B:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GS60 2PE dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1376661/+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 1376661] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/1376661/+attachment/482/+files/UdevLog.txt -- 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/1376661 Title: Strange behaviour of ahci driver (intel 82801 Mobile SATA Controller) Status in “linux” package in Ubuntu: Incomplete Bug description: Hi, I have a MSI GS60E Ghost Pro laptop. It is quite complex: 2 SSD in raid 0 (intel Raid) 1 HDD standard SATA 2 Gpus (intel and nvidia) I was trying to upgrade my trusty to utopic. On trusty if I remember well there was no way to have a functionnal intel raid disks. I had to delete the raid an go to 2 separate disks to take advantage of the SSD (involved reinstalling secondary OS used for gaming). Legacy boot: On utopic, I can now use it but the name of the device is still strange (don't know if it is expected, but on other scsi harware I had I always had standard names /dev/sdx...): /dev/mapper/isw_ihbcddegh_SSD, where SSD is the name given at raid creation of the volume. Despite of this device I still have access to bare device /dev/sda, /dev/sdb, with the added bonus of being able to destroy the raid on it if we let the default /dev/sda for grub install of utopic desktop (destroyed at the end of install). At install time we see /dev/mapper/isw_ /dev/sda /dev/sdb and /dev/sdc, but it is readable on legacy installer even if not ideal. UEFI boot: If we boot on UEFI, it is more complex, as grub is not able to find the windows bootmanager for unknown reason (maybe not related). Don't know if I need to put it somewhere else, but at the install selection of disks and partitions, it is also a bit confusing as it show two devices for the raid /dev/mapper/isw_ each with the copy of the partitions (split the raid) plus bare devices, /dev/sda, /dev/sdb. I don't remember, if I saw partitions on the bare devices equaly. I can make some undestructive tests for you (had hard time at making a working install on this machine). If really needed, I can switch to work on an other laptop, and go for destructive tests. You can find some hardware infos about the config there, setup, etc: http://paste.ubuntu.com/8478288/ --- ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kick 3322 F pulseaudio /dev/snd/controlC2: kick 3322 F pulseaudio /dev/snd/controlC1: kick 3322 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=46a8dc48-0696-4cc1-9ba5-6718ccae8802 InstallationDate: Installed on 2014-10-01 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140923) MachineType: Micro-Star International Co., Ltd. GS60 2PE Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-17-generic root=UUID=71fadb93-5ab3-4fab-98d7-e558816e33a0 ro quiet splash blacklist=nouveau ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3 RelatedPackageVersions: linux-restricted-modules-3.16.0-17-generic N/A linux-backports-modules-3.16.0-17-generic N/A linux-firmware 1.134 Tags: utopic Uname: Linux 3.16.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/16/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16H2IMS.10B dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-16H2 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.B dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16H2IMS.10B:bd08/16/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS602PE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16H2:rvrREV0.B:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GS60 2PE dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1376661/+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 1376661] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/1376661/+attachment/471/+files/CurrentDmesg.txt -- 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/1376661 Title: Strange behaviour of ahci driver (intel 82801 Mobile SATA Controller) Status in “linux” package in Ubuntu: Incomplete Bug description: Hi, I have a MSI GS60E Ghost Pro laptop. It is quite complex: 2 SSD in raid 0 (intel Raid) 1 HDD standard SATA 2 Gpus (intel and nvidia) I was trying to upgrade my trusty to utopic. On trusty if I remember well there was no way to have a functionnal intel raid disks. I had to delete the raid an go to 2 separate disks to take advantage of the SSD (involved reinstalling secondary OS used for gaming). Legacy boot: On utopic, I can now use it but the name of the device is still strange (don't know if it is expected, but on other scsi harware I had I always had standard names /dev/sdx...): /dev/mapper/isw_ihbcddegh_SSD, where SSD is the name given at raid creation of the volume. Despite of this device I still have access to bare device /dev/sda, /dev/sdb, with the added bonus of being able to destroy the raid on it if we let the default /dev/sda for grub install of utopic desktop (destroyed at the end of install). At install time we see /dev/mapper/isw_ /dev/sda /dev/sdb and /dev/sdc, but it is readable on legacy installer even if not ideal. UEFI boot: If we boot on UEFI, it is more complex, as grub is not able to find the windows bootmanager for unknown reason (maybe not related). Don't know if I need to put it somewhere else, but at the install selection of disks and partitions, it is also a bit confusing as it show two devices for the raid /dev/mapper/isw_ each with the copy of the partitions (split the raid) plus bare devices, /dev/sda, /dev/sdb. I don't remember, if I saw partitions on the bare devices equaly. I can make some undestructive tests for you (had hard time at making a working install on this machine). If really needed, I can switch to work on an other laptop, and go for destructive tests. You can find some hardware infos about the config there, setup, etc: http://paste.ubuntu.com/8478288/ --- ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kick 3322 F pulseaudio /dev/snd/controlC2: kick 3322 F pulseaudio /dev/snd/controlC1: kick 3322 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=46a8dc48-0696-4cc1-9ba5-6718ccae8802 InstallationDate: Installed on 2014-10-01 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140923) MachineType: Micro-Star International Co., Ltd. GS60 2PE Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-17-generic root=UUID=71fadb93-5ab3-4fab-98d7-e558816e33a0 ro quiet splash blacklist=nouveau ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3 RelatedPackageVersions: linux-restricted-modules-3.16.0-17-generic N/A linux-backports-modules-3.16.0-17-generic N/A linux-firmware 1.134 Tags: utopic Uname: Linux 3.16.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/16/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16H2IMS.10B dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-16H2 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.B dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16H2IMS.10B:bd08/16/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS602PE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16H2:rvrREV0.B:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GS60 2PE dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1376661/+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 1376661] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1376661/+attachment/475/+files/ProcCpuinfo.txt -- 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/1376661 Title: Strange behaviour of ahci driver (intel 82801 Mobile SATA Controller) Status in “linux” package in Ubuntu: Incomplete Bug description: Hi, I have a MSI GS60E Ghost Pro laptop. It is quite complex: 2 SSD in raid 0 (intel Raid) 1 HDD standard SATA 2 Gpus (intel and nvidia) I was trying to upgrade my trusty to utopic. On trusty if I remember well there was no way to have a functionnal intel raid disks. I had to delete the raid an go to 2 separate disks to take advantage of the SSD (involved reinstalling secondary OS used for gaming). Legacy boot: On utopic, I can now use it but the name of the device is still strange (don't know if it is expected, but on other scsi harware I had I always had standard names /dev/sdx...): /dev/mapper/isw_ihbcddegh_SSD, where SSD is the name given at raid creation of the volume. Despite of this device I still have access to bare device /dev/sda, /dev/sdb, with the added bonus of being able to destroy the raid on it if we let the default /dev/sda for grub install of utopic desktop (destroyed at the end of install). At install time we see /dev/mapper/isw_ /dev/sda /dev/sdb and /dev/sdc, but it is readable on legacy installer even if not ideal. UEFI boot: If we boot on UEFI, it is more complex, as grub is not able to find the windows bootmanager for unknown reason (maybe not related). Don't know if I need to put it somewhere else, but at the install selection of disks and partitions, it is also a bit confusing as it show two devices for the raid /dev/mapper/isw_ each with the copy of the partitions (split the raid) plus bare devices, /dev/sda, /dev/sdb. I don't remember, if I saw partitions on the bare devices equaly. I can make some undestructive tests for you (had hard time at making a working install on this machine). If really needed, I can switch to work on an other laptop, and go for destructive tests. You can find some hardware infos about the config there, setup, etc: http://paste.ubuntu.com/8478288/ --- ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kick 3322 F pulseaudio /dev/snd/controlC2: kick 3322 F pulseaudio /dev/snd/controlC1: kick 3322 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=46a8dc48-0696-4cc1-9ba5-6718ccae8802 InstallationDate: Installed on 2014-10-01 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140923) MachineType: Micro-Star International Co., Ltd. GS60 2PE Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-17-generic root=UUID=71fadb93-5ab3-4fab-98d7-e558816e33a0 ro quiet splash blacklist=nouveau ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3 RelatedPackageVersions: linux-restricted-modules-3.16.0-17-generic N/A linux-backports-modules-3.16.0-17-generic N/A linux-firmware 1.134 Tags: utopic Uname: Linux 3.16.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/16/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16H2IMS.10B dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-16H2 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.B dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16H2IMS.10B:bd08/16/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS602PE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16H2:rvrREV0.B:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GS60 2PE dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1376661/+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 1376661] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/1376661/+attachment/473/+files/Lspci.txt -- 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/1376661 Title: Strange behaviour of ahci driver (intel 82801 Mobile SATA Controller) Status in “linux” package in Ubuntu: Incomplete Bug description: Hi, I have a MSI GS60E Ghost Pro laptop. It is quite complex: 2 SSD in raid 0 (intel Raid) 1 HDD standard SATA 2 Gpus (intel and nvidia) I was trying to upgrade my trusty to utopic. On trusty if I remember well there was no way to have a functionnal intel raid disks. I had to delete the raid an go to 2 separate disks to take advantage of the SSD (involved reinstalling secondary OS used for gaming). Legacy boot: On utopic, I can now use it but the name of the device is still strange (don't know if it is expected, but on other scsi harware I had I always had standard names /dev/sdx...): /dev/mapper/isw_ihbcddegh_SSD, where SSD is the name given at raid creation of the volume. Despite of this device I still have access to bare device /dev/sda, /dev/sdb, with the added bonus of being able to destroy the raid on it if we let the default /dev/sda for grub install of utopic desktop (destroyed at the end of install). At install time we see /dev/mapper/isw_ /dev/sda /dev/sdb and /dev/sdc, but it is readable on legacy installer even if not ideal. UEFI boot: If we boot on UEFI, it is more complex, as grub is not able to find the windows bootmanager for unknown reason (maybe not related). Don't know if I need to put it somewhere else, but at the install selection of disks and partitions, it is also a bit confusing as it show two devices for the raid /dev/mapper/isw_ each with the copy of the partitions (split the raid) plus bare devices, /dev/sda, /dev/sdb. I don't remember, if I saw partitions on the bare devices equaly. I can make some undestructive tests for you (had hard time at making a working install on this machine). If really needed, I can switch to work on an other laptop, and go for destructive tests. You can find some hardware infos about the config there, setup, etc: http://paste.ubuntu.com/8478288/ --- ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kick 3322 F pulseaudio /dev/snd/controlC2: kick 3322 F pulseaudio /dev/snd/controlC1: kick 3322 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=46a8dc48-0696-4cc1-9ba5-6718ccae8802 InstallationDate: Installed on 2014-10-01 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140923) MachineType: Micro-Star International Co., Ltd. GS60 2PE Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-17-generic root=UUID=71fadb93-5ab3-4fab-98d7-e558816e33a0 ro quiet splash blacklist=nouveau ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3 RelatedPackageVersions: linux-restricted-modules-3.16.0-17-generic N/A linux-backports-modules-3.16.0-17-generic N/A linux-firmware 1.134 Tags: utopic Uname: Linux 3.16.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/16/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16H2IMS.10B dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-16H2 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.B dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16H2IMS.10B:bd08/16/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS602PE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16H2:rvrREV0.B:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GS60 2PE dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1376661/+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 1376661] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/1376661/+attachment/478/+files/ProcModules.txt -- 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/1376661 Title: Strange behaviour of ahci driver (intel 82801 Mobile SATA Controller) Status in “linux” package in Ubuntu: Incomplete Bug description: Hi, I have a MSI GS60E Ghost Pro laptop. It is quite complex: 2 SSD in raid 0 (intel Raid) 1 HDD standard SATA 2 Gpus (intel and nvidia) I was trying to upgrade my trusty to utopic. On trusty if I remember well there was no way to have a functionnal intel raid disks. I had to delete the raid an go to 2 separate disks to take advantage of the SSD (involved reinstalling secondary OS used for gaming). Legacy boot: On utopic, I can now use it but the name of the device is still strange (don't know if it is expected, but on other scsi harware I had I always had standard names /dev/sdx...): /dev/mapper/isw_ihbcddegh_SSD, where SSD is the name given at raid creation of the volume. Despite of this device I still have access to bare device /dev/sda, /dev/sdb, with the added bonus of being able to destroy the raid on it if we let the default /dev/sda for grub install of utopic desktop (destroyed at the end of install). At install time we see /dev/mapper/isw_ /dev/sda /dev/sdb and /dev/sdc, but it is readable on legacy installer even if not ideal. UEFI boot: If we boot on UEFI, it is more complex, as grub is not able to find the windows bootmanager for unknown reason (maybe not related). Don't know if I need to put it somewhere else, but at the install selection of disks and partitions, it is also a bit confusing as it show two devices for the raid /dev/mapper/isw_ each with the copy of the partitions (split the raid) plus bare devices, /dev/sda, /dev/sdb. I don't remember, if I saw partitions on the bare devices equaly. I can make some undestructive tests for you (had hard time at making a working install on this machine). If really needed, I can switch to work on an other laptop, and go for destructive tests. You can find some hardware infos about the config there, setup, etc: http://paste.ubuntu.com/8478288/ --- ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kick 3322 F pulseaudio /dev/snd/controlC2: kick 3322 F pulseaudio /dev/snd/controlC1: kick 3322 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=46a8dc48-0696-4cc1-9ba5-6718ccae8802 InstallationDate: Installed on 2014-10-01 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140923) MachineType: Micro-Star International Co., Ltd. GS60 2PE Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-17-generic root=UUID=71fadb93-5ab3-4fab-98d7-e558816e33a0 ro quiet splash blacklist=nouveau ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3 RelatedPackageVersions: linux-restricted-modules-3.16.0-17-generic N/A linux-backports-modules-3.16.0-17-generic N/A linux-firmware 1.134 Tags: utopic Uname: Linux 3.16.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/16/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16H2IMS.10B dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-16H2 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.B dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16H2IMS.10B:bd08/16/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS602PE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16H2:rvrREV0.B:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GS60 2PE dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1376661/+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 1376661] PulseList.txt
apport information ** Attachment added: PulseList.txt https://bugs.launchpad.net/bugs/1376661/+attachment/479/+files/PulseList.txt -- 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/1376661 Title: Strange behaviour of ahci driver (intel 82801 Mobile SATA Controller) Status in “linux” package in Ubuntu: Incomplete Bug description: Hi, I have a MSI GS60E Ghost Pro laptop. It is quite complex: 2 SSD in raid 0 (intel Raid) 1 HDD standard SATA 2 Gpus (intel and nvidia) I was trying to upgrade my trusty to utopic. On trusty if I remember well there was no way to have a functionnal intel raid disks. I had to delete the raid an go to 2 separate disks to take advantage of the SSD (involved reinstalling secondary OS used for gaming). Legacy boot: On utopic, I can now use it but the name of the device is still strange (don't know if it is expected, but on other scsi harware I had I always had standard names /dev/sdx...): /dev/mapper/isw_ihbcddegh_SSD, where SSD is the name given at raid creation of the volume. Despite of this device I still have access to bare device /dev/sda, /dev/sdb, with the added bonus of being able to destroy the raid on it if we let the default /dev/sda for grub install of utopic desktop (destroyed at the end of install). At install time we see /dev/mapper/isw_ /dev/sda /dev/sdb and /dev/sdc, but it is readable on legacy installer even if not ideal. UEFI boot: If we boot on UEFI, it is more complex, as grub is not able to find the windows bootmanager for unknown reason (maybe not related). Don't know if I need to put it somewhere else, but at the install selection of disks and partitions, it is also a bit confusing as it show two devices for the raid /dev/mapper/isw_ each with the copy of the partitions (split the raid) plus bare devices, /dev/sda, /dev/sdb. I don't remember, if I saw partitions on the bare devices equaly. I can make some undestructive tests for you (had hard time at making a working install on this machine). If really needed, I can switch to work on an other laptop, and go for destructive tests. You can find some hardware infos about the config there, setup, etc: http://paste.ubuntu.com/8478288/ --- ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kick 3322 F pulseaudio /dev/snd/controlC2: kick 3322 F pulseaudio /dev/snd/controlC1: kick 3322 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=46a8dc48-0696-4cc1-9ba5-6718ccae8802 InstallationDate: Installed on 2014-10-01 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140923) MachineType: Micro-Star International Co., Ltd. GS60 2PE Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-17-generic root=UUID=71fadb93-5ab3-4fab-98d7-e558816e33a0 ro quiet splash blacklist=nouveau ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3 RelatedPackageVersions: linux-restricted-modules-3.16.0-17-generic N/A linux-backports-modules-3.16.0-17-generic N/A linux-firmware 1.134 Tags: utopic Uname: Linux 3.16.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/16/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16H2IMS.10B dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-16H2 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.B dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16H2IMS.10B:bd08/16/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS602PE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16H2:rvrREV0.B:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GS60 2PE dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1376661/+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 1376661] CRDA.txt
apport information ** Attachment added: CRDA.txt https://bugs.launchpad.net/bugs/1376661/+attachment/470/+files/CRDA.txt -- 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/1376661 Title: Strange behaviour of ahci driver (intel 82801 Mobile SATA Controller) Status in “linux” package in Ubuntu: Incomplete Bug description: Hi, I have a MSI GS60E Ghost Pro laptop. It is quite complex: 2 SSD in raid 0 (intel Raid) 1 HDD standard SATA 2 Gpus (intel and nvidia) I was trying to upgrade my trusty to utopic. On trusty if I remember well there was no way to have a functionnal intel raid disks. I had to delete the raid an go to 2 separate disks to take advantage of the SSD (involved reinstalling secondary OS used for gaming). Legacy boot: On utopic, I can now use it but the name of the device is still strange (don't know if it is expected, but on other scsi harware I had I always had standard names /dev/sdx...): /dev/mapper/isw_ihbcddegh_SSD, where SSD is the name given at raid creation of the volume. Despite of this device I still have access to bare device /dev/sda, /dev/sdb, with the added bonus of being able to destroy the raid on it if we let the default /dev/sda for grub install of utopic desktop (destroyed at the end of install). At install time we see /dev/mapper/isw_ /dev/sda /dev/sdb and /dev/sdc, but it is readable on legacy installer even if not ideal. UEFI boot: If we boot on UEFI, it is more complex, as grub is not able to find the windows bootmanager for unknown reason (maybe not related). Don't know if I need to put it somewhere else, but at the install selection of disks and partitions, it is also a bit confusing as it show two devices for the raid /dev/mapper/isw_ each with the copy of the partitions (split the raid) plus bare devices, /dev/sda, /dev/sdb. I don't remember, if I saw partitions on the bare devices equaly. I can make some undestructive tests for you (had hard time at making a working install on this machine). If really needed, I can switch to work on an other laptop, and go for destructive tests. You can find some hardware infos about the config there, setup, etc: http://paste.ubuntu.com/8478288/ --- ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kick 3322 F pulseaudio /dev/snd/controlC2: kick 3322 F pulseaudio /dev/snd/controlC1: kick 3322 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=46a8dc48-0696-4cc1-9ba5-6718ccae8802 InstallationDate: Installed on 2014-10-01 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140923) MachineType: Micro-Star International Co., Ltd. GS60 2PE Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-17-generic root=UUID=71fadb93-5ab3-4fab-98d7-e558816e33a0 ro quiet splash blacklist=nouveau ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3 RelatedPackageVersions: linux-restricted-modules-3.16.0-17-generic N/A linux-backports-modules-3.16.0-17-generic N/A linux-firmware 1.134 Tags: utopic Uname: Linux 3.16.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/16/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16H2IMS.10B dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-16H2 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.B dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16H2IMS.10B:bd08/16/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS602PE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16H2:rvrREV0.B:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GS60 2PE dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1376661/+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 1359146] Re: Kernel crash when mounting bcache on a vm with virtio
The virtual machine hangs some seconds after mount command of bcache device. -- 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/1359146 Title: Kernel crash when mounting bcache on a vm with virtio Status in “linux” package in Ubuntu: Confirmed Bug description: bcache used in a virtual machine: If you create a bcache device with caching device and backing device on virtio disks, it will let you do your work until you mount it where it crashes the virtual machine (virtual machine is utopic, host is trusty). For example: if your backing device is /dev/vdb, and your caching device is /dev/vdc: sudo make-bcache -B /dev/vdc -C /dev/vdb --writeback is ok mkfs.ext4 /dev/bcache0 -L bcache-test is ok but mount /dev/bcache0 /media/bcache make it crash, if I remember well one time I had a few seconds before crash, but I don't have any log files. qemu-system-x86 is version 2.0.0+dfsg-2ubuntu1.2 Re-installing, and using IDE virtual interface seems to create and mount the bcache device is ok. After bcache created an mounted successfully with IDE interfaces, switching to SATA, SCSI, and USB with booting and mounting seemed ok. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359146/+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 1359146] Re: Kernel crash when mounting bcache on a vm with virtio
I've tested with upstream kernel, and I've got also an hang of the virtual machine. kernel tested is : linux-image-3.17.0-031700rc1 -- 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/1359146 Title: Kernel crash when mounting bcache on a vm with virtio Status in “linux” package in Ubuntu: Confirmed Bug description: bcache used in a virtual machine: If you create a bcache device with caching device and backing device on virtio disks, it will let you do your work until you mount it where it crashes the virtual machine (virtual machine is utopic, host is trusty). For example: if your backing device is /dev/vdb, and your caching device is /dev/vdc: sudo make-bcache -B /dev/vdc -C /dev/vdb --writeback is ok mkfs.ext4 /dev/bcache0 -L bcache-test is ok but mount /dev/bcache0 /media/bcache make it crash, if I remember well one time I had a few seconds before crash, but I don't have any log files. qemu-system-x86 is version 2.0.0+dfsg-2ubuntu1.2 Re-installing, and using IDE virtual interface seems to create and mount the bcache device is ok. After bcache created an mounted successfully with IDE interfaces, switching to SATA, SCSI, and USB with booting and mounting seemed ok. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359146/+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 1359146] Re: Kernel crash when mounting bcache on a vm with virtio
At boot ime after crash I got: http://paste.ubuntu.com/8106758/ trace begins at line 466 -- 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/1359146 Title: Kernel crash when mounting bcache on a vm with virtio Status in “linux” package in Ubuntu: Confirmed Bug description: bcache used in a virtual machine: If you create a bcache device with caching device and backing device on virtio disks, it will let you do your work until you mount it where it crashes the virtual machine (virtual machine is utopic, host is trusty). For example: if your backing device is /dev/vdb, and your caching device is /dev/vdc: sudo make-bcache -B /dev/vdc -C /dev/vdb --writeback is ok mkfs.ext4 /dev/bcache0 -L bcache-test is ok but mount /dev/bcache0 /media/bcache make it crash, if I remember well one time I had a few seconds before crash, but I don't have any log files. qemu-system-x86 is version 2.0.0+dfsg-2ubuntu1.2 Re-installing, and using IDE virtual interface seems to create and mount the bcache device is ok. After bcache created an mounted successfully with IDE interfaces, switching to SATA, SCSI, and USB with booting and mounting seemed ok. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359146/+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 1359146] [NEW] Kernel crash when mounting bcache on a vm with virtio
Public bug reported: bcache used in a virtual machine: If you create a bcache device with caching device and backing device on virtio disks, it will let you do your work until you mount it where it crashes the virtual machine (virtual machine is utopic, host is trusty). For example: if your backing device is /dev/vdb, and your caching device is /dev/vdc: sudo make-bcache -B /dev/vdc -C /dev/vdb --writeback is ok mkfs.ext4 /dev/bcache0 -L bcache-test is ok but mount /dev/bcache0 /media/bcache make it crash, if I remember well one time I had a few seconds before crash. qemu-system-x86 is version 2.0.0+dfsg-2ubuntu1.2 Re-installing, and using IDE virtual interface seems to create and mount the bcache device is ok. After bcache created an mounted successfully with IDE interfaces, switching to SATA, SCSI, and USB with booting and mounting seemed ok. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Description changed: If you create a bcache device with caching device and backing device on virtio disks, it will let you do your work until you mount it where it crashes the virtual machine (virtual machine is utopic, host is trusty). For example: if your backing device is /dev/vdb, and your caching device is /dev/vdc: sudo make-bcache -B /dev/vdc -C /dev/vdb --writeback is ok - mkfs.ext4 /dev/bcache0 -L bcache-test + mkfs.ext4 /dev/bcache0 -L bcache-test is ok but mount /dev/bcache0 /media/bcache make it crash, if I remember well one time I had a few seconds before crash. qemu-system-x86 is version 2.0.0+dfsg-2ubuntu1.2 + + Re-installing, and using IDE virtual interface seems to create and mount + the bcache device is ok. + + After bcache created an mounted successfully with IDE interfaces, + switching to SATA, SCSI, and USB with booting and mounting seemed ok. ** Description changed: + bcache used in a virtual machine: + If you create a bcache device with caching device and backing device on virtio disks, it will let you do your work until you mount it where it crashes the virtual machine (virtual machine is utopic, host is trusty). For example: if your backing device is /dev/vdb, and your caching device is /dev/vdc: sudo make-bcache -B /dev/vdc -C /dev/vdb --writeback is ok mkfs.ext4 /dev/bcache0 -L bcache-test is ok but mount /dev/bcache0 /media/bcache make it crash, if I remember well one time I had a few seconds before crash. qemu-system-x86 is version 2.0.0+dfsg-2ubuntu1.2 Re-installing, and using IDE virtual interface seems to create and mount the bcache device is ok. After bcache created an mounted successfully with IDE interfaces, switching to SATA, SCSI, and USB with booting and mounting seemed ok. -- 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/1359146 Title: Kernel crash when mounting bcache on a vm with virtio Status in “linux” package in Ubuntu: New Bug description: bcache used in a virtual machine: If you create a bcache device with caching device and backing device on virtio disks, it will let you do your work until you mount it where it crashes the virtual machine (virtual machine is utopic, host is trusty). For example: if your backing device is /dev/vdb, and your caching device is /dev/vdc: sudo make-bcache -B /dev/vdc -C /dev/vdb --writeback is ok mkfs.ext4 /dev/bcache0 -L bcache-test is ok but mount /dev/bcache0 /media/bcache make it crash, if I remember well one time I had a few seconds before crash. qemu-system-x86 is version 2.0.0+dfsg-2ubuntu1.2 Re-installing, and using IDE virtual interface seems to create and mount the bcache device is ok. After bcache created an mounted successfully with IDE interfaces, switching to SATA, SCSI, and USB with booting and mounting seemed ok. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359146/+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 1359146] Re: Kernel crash when mounting bcache on a vm with virtio
** Description changed: bcache used in a virtual machine: If you create a bcache device with caching device and backing device on virtio disks, it will let you do your work until you mount it where it crashes the virtual machine (virtual machine is utopic, host is trusty). For example: if your backing device is /dev/vdb, and your caching device is /dev/vdc: sudo make-bcache -B /dev/vdc -C /dev/vdb --writeback is ok mkfs.ext4 /dev/bcache0 -L bcache-test is ok but mount /dev/bcache0 /media/bcache make it crash, if I remember well one time I had a few seconds before - crash. + crash, but I don't have any log files. qemu-system-x86 is version 2.0.0+dfsg-2ubuntu1.2 Re-installing, and using IDE virtual interface seems to create and mount the bcache device is ok. After bcache created an mounted successfully with IDE interfaces, switching to SATA, SCSI, and USB with booting and mounting seemed ok. ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- 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/1359146 Title: Kernel crash when mounting bcache on a vm with virtio Status in “linux” package in Ubuntu: Confirmed Bug description: bcache used in a virtual machine: If you create a bcache device with caching device and backing device on virtio disks, it will let you do your work until you mount it where it crashes the virtual machine (virtual machine is utopic, host is trusty). For example: if your backing device is /dev/vdb, and your caching device is /dev/vdc: sudo make-bcache -B /dev/vdc -C /dev/vdb --writeback is ok mkfs.ext4 /dev/bcache0 -L bcache-test is ok but mount /dev/bcache0 /media/bcache make it crash, if I remember well one time I had a few seconds before crash, but I don't have any log files. qemu-system-x86 is version 2.0.0+dfsg-2ubuntu1.2 Re-installing, and using IDE virtual interface seems to create and mount the bcache device is ok. After bcache created an mounted successfully with IDE interfaces, switching to SATA, SCSI, and USB with booting and mounting seemed ok. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359146/+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
Re: [Kernel-packages] [Bug 1359146] Re: Kernel crash when mounting bcache on a vm with virtio
I'll try upstream kernel, and I will try previous release. Only utopic kernel releases, or also trusty ones? Le 20/08/2014 18:07, Joseph Salisbury a écrit : Also, was there a prior release that did not exhibit this bug? -- 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/1359146 Title: Kernel crash when mounting bcache on a vm with virtio Status in “linux” package in Ubuntu: Confirmed Bug description: bcache used in a virtual machine: If you create a bcache device with caching device and backing device on virtio disks, it will let you do your work until you mount it where it crashes the virtual machine (virtual machine is utopic, host is trusty). For example: if your backing device is /dev/vdb, and your caching device is /dev/vdc: sudo make-bcache -B /dev/vdc -C /dev/vdb --writeback is ok mkfs.ext4 /dev/bcache0 -L bcache-test is ok but mount /dev/bcache0 /media/bcache make it crash, if I remember well one time I had a few seconds before crash, but I don't have any log files. qemu-system-x86 is version 2.0.0+dfsg-2ubuntu1.2 Re-installing, and using IDE virtual interface seems to create and mount the bcache device is ok. After bcache created an mounted successfully with IDE interfaces, switching to SATA, SCSI, and USB with booting and mounting seemed ok. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359146/+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
