date:20171210

Re: [Kernel-packages] [Bug 1698700] Re: hibmc driver does not include "pci:" prefix in bus ID

2017-12-10 Thread Daniel Axtens

Hi Fred,

I will have a look soon and update you.

Regards,
Daniel

On Mon, Dec 11, 2017 at 6:00 PM, Fred Kimmy
 wrote:
> this  patch will solve commit #10 bug, please merge this patch.
>
> thank you
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1698700
>
> Title:
>   hibmc driver does not include "pci:" prefix in bus ID
>
> Status in linux package in Ubuntu:
>   Incomplete
> Status in linux source package in Zesty:
>   Fix Released
> Status in linux source package in Artful:
>   Incomplete
>
> Bug description:
>   SRU Justification
>
>   [Impact]
>   On the HiSilicon D05 (arm64) board, X crashes when started. [0]
>
>   [Fix]
>   The crash is attributable to the bus ID that the hibmc driver reports for 
> the hibmc graphics card on the board. In particular, the bus id is missing 
> the "pci:" prefix that most other cards provide: [1]
>   - The busid reported on the arm64 system is "0007:a1:00.0"
>   - The busid reported on a amd64 system is "pci::00:02.0"
>
>   X tests for this prefix. A missing prefix for PCI cards leads to an
>   Xorg crash.
>
>   Fix this by using the set_pci_busid function from the DRM core.
>
>   [Testcase]
>   Successfully tested on a D05 board. [2]
>
>   [Regression Potential]
>   Changes are limited to the hibmc driver, so any regression should also be 
> limited to that driver.
>
>   [Notes]
>   I submitted the patch upstream. However, upstream is refactoring the drm 
> core, and set_busid is going away. That does fix this issue but the 
> regression potential of the refactor is enormous, so this seems like the 
> wiser approach. [3]
>
>   [0]: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991
>   [1]: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/comments/16
>   [2]: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/comments/29
>   [3]: https://www.spinics.net/lists/dri-devel/msg143831.html
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1698700/+subscriptions

-- 
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/1698700

Title:
  hibmc driver does not include "pci:" prefix in bus ID

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Zesty:
  Fix Released
Status in linux source package in Artful:
  Incomplete

Bug description:
  SRU Justification

  [Impact]
  On the HiSilicon D05 (arm64) board, X crashes when started. [0]

  [Fix]
  The crash is attributable to the bus ID that the hibmc driver reports for the 
hibmc graphics card on the board. In particular, the bus id is missing the 
"pci:" prefix that most other cards provide: [1]
  - The busid reported on the arm64 system is "0007:a1:00.0"
  - The busid reported on a amd64 system is "pci::00:02.0"

  X tests for this prefix. A missing prefix for PCI cards leads to an
  Xorg crash.

  Fix this by using the set_pci_busid function from the DRM core.

  [Testcase]
  Successfully tested on a D05 board. [2]

  [Regression Potential]
  Changes are limited to the hibmc driver, so any regression should also be 
limited to that driver.

  [Notes]
  I submitted the patch upstream. However, upstream is refactoring the drm 
core, and set_busid is going away. That does fix this issue but the regression 
potential of the refactor is enormous, so this seems like the wiser approach. 
[3]

  [0]: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991
  [1]: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/comments/16
  [2]: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/comments/29
  [3]: https://www.spinics.net/lists/dri-devel/msg143831.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1698700/+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 1698700] Re: hibmc driver does not include "pci:" prefix in bus ID

2017-12-10 Thread Fred Kimmy

this  patch will solve commit #10 bug, please merge this patch.

thank you

-- 
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/1698700

Title:
  hibmc driver does not include "pci:" prefix in bus ID

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Zesty:
  Fix Released
Status in linux source package in Artful:
  Incomplete

Bug description:
  SRU Justification

  [Impact]
  On the HiSilicon D05 (arm64) board, X crashes when started. [0]

  [Fix]
  The crash is attributable to the bus ID that the hibmc driver reports for the 
hibmc graphics card on the board. In particular, the bus id is missing the 
"pci:" prefix that most other cards provide: [1]
  - The busid reported on the arm64 system is "0007:a1:00.0"
  - The busid reported on a amd64 system is "pci::00:02.0"

  X tests for this prefix. A missing prefix for PCI cards leads to an
  Xorg crash.

  Fix this by using the set_pci_busid function from the DRM core.

  [Testcase]
  Successfully tested on a D05 board. [2]

  [Regression Potential]
  Changes are limited to the hibmc driver, so any regression should also be 
limited to that driver.

  [Notes]
  I submitted the patch upstream. However, upstream is refactoring the drm 
core, and set_busid is going away. That does fix this issue but the regression 
potential of the refactor is enormous, so this seems like the wiser approach. 
[3]

  [0]: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991
  [1]: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/comments/16
  [2]: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/comments/29
  [3]: https://www.spinics.net/lists/dri-devel/msg143831.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1698700/+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 1715609] Re: kernel warning: skb_warn_bad_offload

2017-12-10 Thread Kevin Carter

I'm still seeing this in the latest 4.10, 4.11, 4.13 and 4.15 (from
mainline).


Dec 10 23:09:05 infra1 kernel: [  571.226805] RIP: 
0010:skb_warn_bad_offload+0xb7/0xf0
Dec 10 23:09:05 infra1 kernel: [  571.226810] FS:  () 
GS:97c25eb8() knlGS:
Dec 10 23:09:05 infra1 kernel: [  571.226818]  ipt_do_table+0x2eb/0x5f0 
[ip_tables]
Dec 10 23:09:05 infra1 kernel: [  571.226829]  nf_hook_slow+0x42/0xb0
Dec 10 23:09:05 infra1 kernel: [  571.226849]  ? 
br_dev_queue_push_xmit+0x140/0x140 [bridge]
Dec 10 23:09:05 infra1 kernel: [  571.226866]  
br_handle_frame_finish+0x2a4/0x540 [bridge]
Dec 10 23:09:05 infra1 kernel: [  571.226881]  ? iptable_nat_ipv4_in+0x15/0x20 
[iptable_nat]
Dec 10 23:09:05 infra1 kernel: [  571.226895]  __netif_receive_skb+0x18/0x60
Dec 10 23:09:05 infra1 kernel: [  571.226906]  common_interrupt+0x93/0x93
Dec 10 23:09:05 infra1 kernel: [  571.226912] R10: bc4f00cf3e40 R11: 
012b R12: 97c25eba4e30
Dec 10 23:09:05 infra1 kernel: [  571.226921]  secondary_startup_64+0xa5/0xa5

Dec 10 23:09:15 infra1 kernel: [  582.507590] CPU: 0 PID: 20250 Comm: apache2 
Tainted: GW   4.14.5-041405-generic #201712101332   

   
Dec 10 23:09:15 infra1 kernel: [  582.507595] RBP: 97c25ea036e0 R08: 
0001 R09: 0c10  


Dec 10 23:09:15 infra1 kernel: [  582.507599] Call Trace:   


 
Dec 10 23:09:15 infra1 kernel: [  582.507610]  iptable_mangle_hook+0x37/0x110 
[iptable_mangle]

   
Dec 10 23:09:15 infra1 kernel: [  582.507622]  br_forward_finish+0x9d/0xb0 
[bridge]

  
Dec 10 23:09:15 infra1 kernel: [  582.507631]  br_nf_forward_ip+0x30c/0x430 
[br_netfilter]  

 
Dec 10 23:09:15 infra1 kernel: [  582.507641]  br_forward+0x97/0xa0 [bridge]


 
Dec 10 23:09:15 infra1 kernel: [  582.507650]  ? br_pass_frame_up+0x150/0x150 
[bridge]

   
Dec 10 23:09:15 infra1 kernel: [  582.507659]  br_handle_frame+0x1ec/0x300 
[bridge]

  
Dec 10 23:09:15 infra1 kernel: [  582.507667]  net_rx_action+0x13b/0x380


 
Dec 10 23:09:15 infra1 kernel: [  582.507678]  ip_finish_output2+0x172/0x3a0


 
Dec 10 23:09:15 infra1 kernel: [  582.507684]  ip_local_out+0x35/0x40   


 
Dec 10 23:09:15 infra1 kernel: [  582.507692]  tcp_sendmsg_locked+0xb4c/0xe90   


 
Dec 10 23:09:15 infra1 kernel: [  582.507699]  do_iter_write+0x86/0x190 


 
Dec 10 23:09:15 infra1 kernel: [  582.507708]  do_syscall_64+0x61/0x120 


 
Dec 10 23:09:15 infra1 kernel: [  582.507712] RBP: 7f906c1800b0 R08:

[Kernel-packages] [Bug 1722859] Re: wireless not working trace in dmesg

2017-12-10 Thread Launchpad Bug Tracker

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

** Changed in: linux (Ubuntu)
   Status: Incomplete => Expired

-- 
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/1722859

Title:
  wireless not working trace in dmesg

Status in linux package in Ubuntu:
  Expired

Bug description:
  My wireless seems to have stopped working (at least working well).

  
  [   27.950002] [ cut here ]
  [   27.950030] WARNING: CPU: 1 PID: 148 at 
/build/linux-z2ccW0/linux-4.4.0/net/mac80211/driver-ops.c:175 
drv_conf_tx+0x1c8/0x1e0 [mac80211]()
  [   27.950032] wlan2: invalid CW_min/CW_max: 0/0
  [   27.950034] Modules linked in: drbg ansi_cprng binfmt_misc veth 
ip6table_filter xt_CHECKSUM iptable_mangle xt_tcpudp ip6t_MASQUERADE 
nf_nat_masquerade_ipv6 ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 
nf_nat_ipv6 ip6_tables ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_comment 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack 
bridge stp llc iptable_filter ip_tables x_tables ipmi_msghandler zfs(PO) 
zunicode(PO) zcommon(PO) znvpair(PO) spl(O) zavl(PO) uvcvideo videobuf2_vmalloc 
videobuf2_memops videobuf2_v4l2 videobuf2_core v4l2_common intel_rapl 
snd_seq_midi videodev x86_pkg_temp_thermal snd_seq_midi_event intel_powerclamp 
media coretemp snd_hda_codec_hdmi crct10dif_pclmul crc32_pclmul snd_rawmidi 
snd_hda_codec_realtek ghash_clmulni_intel cryptd snd_hda_codec_generic arc4 
snd_hda_intel
  [   27.950080]  iwldvm snd_seq snd_hda_codec mac80211 input_leds joydev 
serio_raw snd_hda_core snd_hwdep iwlwifi snd_pcm snd_seq_device rtsx_pci_ms 
cfg80211 thinkpad_acpi nvram memstick lpc_ich snd_timer shpchp mei_me mei snd 
soundcore mac_hid kvm_intel kvm irqbypass parport_pc ppdev lp parport autofs4 
rtsx_pci_sdmmc i915 psmouse i2c_algo_bit drm_kms_helper ahci libahci 
syscopyarea sysfillrect sysimgblt r8169 fb_sys_fops mii drm rtsx_pci wmi fjes 
video
  [   27.950120] CPU: 1 PID: 148 Comm: kworker/u16:5 Tainted: P   O
4.4.0-96-generic #119-Ubuntu
  [   27.950122] Hardware name: LENOVO 33672B7/33672B7, BIOS G8ET96WW (2.56 ) 
12/18/2013
  [   27.950144] Workqueue: phy0 ieee80211_iface_work [mac80211]
  [   27.950147]  0286 3f54778a458836b7 8800cffb75f0 
813fabd3
  [   27.950151]  8800cffb7638 c056d500 8800cffb7628 
810812e2
  [   27.950154]  8800cfdc4840 880193740700  
8800cfdc4840
  [   27.950157] Call Trace:
  [   27.950163]  [] dump_stack+0x63/0x90
  [   27.950168]  [] warn_slowpath_common+0x82/0xc0
  [   27.950172]  [] warn_slowpath_fmt+0x5c/0x80
  [   27.950190]  [] drv_conf_tx+0x1c8/0x1e0 [mac80211]
  [   27.950215]  [] ieee80211_sta_wmm_params+0x38b/0x3d0 
[mac80211]
  [   27.950238]  [] ieee80211_assoc_success+0x499/0xa80 
[mac80211]
  [   27.950243]  [] ? vprintk_emit+0x2d7/0x520
  [   27.950246]  [] ? vprintk_default+0x29/0x40
  [   27.950252]  [] ? printk+0x57/0x73
  [   27.950274]  [] ? __sdata_info+0x6f/0xd0 [mac80211]
  [   27.950297]  [] ieee80211_rx_mgmt_assoc_resp+0x164/0x4e0 
[mac80211]
  [   27.950319]  [] ieee80211_sta_rx_queued_mgmt+0x34e/0x670 
[mac80211]
  [   27.950324]  [] ? __local_bh_enable_ip+0x7d/0x80
  [   27.950346]  [] ? __ieee80211_tx_skb_tid_band+0x7b/0x80 
[mac80211]
  [   27.950367]  [] ? ieee80211_send_assoc+0x4af/0xbf0 
[mac80211]
  [   27.950370]  [] ? update_curr+0xe3/0x160
  [   27.950373]  [] ? dequeue_entity+0x41b/0xa80
  [   27.950376]  [] ? set_next_entity+0x9c/0xb0
  [   27.950396]  [] ieee80211_iface_work+0x2d0/0x3e0 
[mac80211]
  [   27.950401]  [] process_one_work+0x165/0x480
  [   27.950404]  [] worker_thread+0x4b/0x4c0
  [   27.950408]  [] ? process_one_work+0x480/0x480
  [   27.950410]  [] kthread+0xe5/0x100
  [   27.950414]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [   27.950419]  [] ret_from_fork+0x3f/0x70
  [   27.950422]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [   27.950424] ---[ end trace 5b2b342ed228f884 ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-96-generic 4.4.0-96.119
  ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
  Uname: Linux 4.4.0-96-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  smoser 5514 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Oct 11 12:17:47 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-05-23 (1237 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 33672B7
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-96-generic.efi.signed 
root=UUID=19ac97d5-6973-4193-9a09-2e6bbfa38262 ro quiet splash vt.handoff=7
  RelatedPackageVersions:

[Kernel-packages] [Bug 1722781] Re: package linux-image-4.4.0-97-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

2017-12-10 Thread Launchpad Bug Tracker

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

** Changed in: linux (Ubuntu)
   Status: Incomplete => Expired

-- 
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/1722781

Title:
  package linux-image-4.4.0-97-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  Expired

Bug description:
  Automatic upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-97-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
  Uname: Linux 4.4.0-96-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dave   2721 F pulseaudio
   /dev/snd/controlC0:  dave   2721 F pulseaudio
  Date: Wed Oct 11 07:38:16 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=f9dbed43-e50f-4acd-a227-55c6c68231f2
  InstallationDate: Installed on 2016-01-10 (639 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: ASUS All Series
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-96-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.12
  SourcePackage: linux
  Title: package linux-image-4.4.0-97-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: Upgraded to xenial on 2016-04-25 (533 days ago)
  dmi.bios.date: 05/29/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1008
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-PRO(Wi-Fi ac)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  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.:bvr1008:bd05/29/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO(Wi-Fiac):rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1722781/+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 1722880] Re: package linux-image-4.10.0-37-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

2017-12-10 Thread Launchpad Bug Tracker

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

** Changed in: linux (Ubuntu)
   Status: Incomplete => Expired

-- 
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/1722880

Title:
  package linux-image-4.10.0-37-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  Expired

Bug description:
  I can not get any updates or apps to load

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-37-generic (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  manstown   1522 F pulseaudio
   /dev/snd/controlC0:  manstown   1522 F pulseaudio
   /dev/snd/controlC1:  manstown   1522 F pulseaudio
  Date: Tue Oct 10 13:51:50 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  InstallationDate: Installed on 2017-06-01 (131 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: Hewlett-Packard HP EliteDesk 800 G1 SFF
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic.efi.signed 
root=UUID=1ab0ac07-cdf5-42bf-b2ba-665b41c3a147 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-4.10.0-37-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L01 v02.21
  dmi.board.asset.tag: MXL418062G
  dmi.board.name: 1998
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: MXL418062G
  dmi.chassis.type: 4
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL01v02.21:bd12/17/2013:svnHewlett-Packard:pnHPEliteDesk800G1SFF:pvr:rvnHewlett-Packard:rn1998:rvr:cvnHewlett-Packard:ct4:cvr:
  dmi.product.name: HP EliteDesk 800 G1 SFF
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1722880/+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 480046] what a place

2017-12-10 Thread Peppone

*** This bug is a duplicate of bug 289718 ***
https://bugs.launchpad.net/bugs/289718

I've visited a wonderful place recently , it amazed me ! Just  seem here
http://www.activetechnology.ie/wp-
content/uploads/2014/01/negx.php?UE80ODAwNDZAYnVncy5sYXVuY2hwYWQubmV0

-- 
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/480046

Title:
  package linux-image-generic 2.6.24.25.27 failed to install/upgrade:
  problemi con le dipendenze - lasciato non configurato

Status in linux package in Ubuntu:
  New

Bug description:
  package linux-image-generic 2.6.24.25.27 failed to install/upgrade:
  problemi con le dipendenze - lasciato non configurato

  ProblemType: Package
  Architecture: amd64
  Date: Tue Nov 10 15:53:50 2009
  DistroRelease: Ubuntu 8.04
  ErrorMessage: problemi con le dipendenze - lasciato non configurato
  NonfreeKernelModules: fglrx
  Package: linux-image-generic 2.6.24.25.27
  PackageArchitecture: amd64
  SourcePackage: linux-meta
  Title: package linux-image-generic 2.6.24.25.27 failed to install/upgrade: 
problemi con le dipendenze - lasciato non configurato
  Uname: Linux 2.6.24-25-generic x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/480046/+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 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]

2017-12-10 Thread nsklaus

i'm using ubuntu 17.10 (single boot) on a macbookpro early 2015 (12,1 model).
i have the apple airpods. they work fantastic with my android phone.

on linux though, it's another story. "it works" but the result is awful. 
useless.
first, there's lot of time it is not able to connect. it fails. then i retry 5, 
6 times and then it connects. when it works: audio is skipping, making long 
pauses, choppy sound most of the time. and i must stay close to the laptop or 
signal is lost.

- using bluetooth headset on osx and android (both unixes) is a really
good experience. they both perform really well.

- using bluetooth headset on linux with pulseaudio is a terrible
experience.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/405294

Title:
  A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in
  audio stream"]

Status in PulseAudio:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped
  working properly. It was working fine in Jaunty.

  My headphones are detected and configured by pulse, but the audio
  skips as if it's spending half of each second paused. Music is
  buffered so that after I click stop on rhythmbox (or whatever--it
  happens with whatever player I use) the audio continues until it's
  caught up.

  syslog is full of the following lines:
  Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal 
latency to 1.00 ms
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
15128 us (= 2668 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36586 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
35593 us (= 6276 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36597 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32601 us (= 5748 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32589 us (= 5748 bytes) in audio stream

  This is with
  bluez 4.45-0ubuntu4
  pulseaudio1:0.9.15-4ubuntu2 0

  pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev
  didn't help.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/405294/+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 1576815] Re: No wireless access for BCM 43162 [14e4:43ae] rev 02

2017-12-10 Thread Povilas Brilius

@chobot (xsobotkaj) that worked in Lenovo E565 case as well, the
replaced BCM943162ZP WIFI card to Intel 7260NGW Dual Band Wireless-AC
was recognized by iwlwifi drivers, thanks for the advice.

-- 
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/1576815

Title:
  No wireless access for BCM 43162 [14e4:43ae] rev 02

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I would like to report missing driver for Broadcom wlan identified as BCM 
43162 [14e4:43ae] rev 02.  Bug was reported in past here
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1432869

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: 
boot/vmlinuz-4.4.0-21-generic]
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chobot 1406 F pulseaudio
   /dev/snd/controlC0:  chobot 1406 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Apr 29 20:11:16 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (7 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  MachineType: LENOVO 80N6
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=e86ca941-78f4-4c7f-89f0-845a49b61a7d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/21/2015
  dmi.bios.vendor: Lenovo
  dmi.bios.version: BDCN61WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo Yoga 500-15IBD
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 500-15IBD
  dmi.modalias: 
dmi:bvnLenovo:bvrBDCN61WW:bd07/21/2015:svnLENOVO:pn80N6:pvrLenovoYoga500-15IBD:rvnLENOVO:rnLenovoYoga500-15IBD:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYoga500-15IBD:
  dmi.product.name: 80N6
  dmi.product.version: Lenovo Yoga 500-15IBD
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1576815/+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 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2017-12-10 Thread Alberto Salvia Novella

I wonder where's the guy who used to discover the critical bugs during
beta release...

Wait, it's me! Happily writing from Manjaro KDE 

DM!

-- 
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/1734147

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Confirmed

Bug description:
  Hi all,

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

   UPDATE (01/12/2017) 

  LENOVO machines affected so far (please add your affected model to
  this list):

  Lenovo Y50-70
  Lenovo G40-30
  Lenovo U31-70
  Lenovo G50-70
  Lenovo Z50-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo G50-80
  Lenovo S20-30
  Lenovo Yoga 2 11" - 20332
  Lenovo B40-70

  ---

  Temporary workaround:
  https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t
  -Save-Settings-Or-Exit/m-p/3853208#M157885

  ---

  result from apport-collect 1734147:

  ---

  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tob1608 F pulseaudio
   /dev/snd/controlC0:  tob1608 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-10-22 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20378
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  Tags:  artful wayland-session
  Uname: Linux 4.13.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/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ECN43WW(V3.03)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo Y50-70
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20378
  dmi.product.version: Lenovo Y50-70
  dmi.sys.vendor: LENOVO

  ---

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+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 219057] Re: Bluetooth does not coexist with WiFi

2017-12-10 Thread Aaahh Ahh

bUmP

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/219057

Title:
  Bluetooth does not coexist with WiFi

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  On my system bluetooth and wifi are unusable together. I have a built-
  in CSR-based bluetooth module in my laptop, and an Atheros wifi. Wifi
  transfers slow to a halt whenever there is BT traffic.

  For example, if I play a music file from another machine through the
  network using a BT headset, only the first few seconds of the file
  will play until the player runs out of buffered data. No further data
  is downloaded. Web pages also do not download, and I even lose
  connection to AP from time to time.

  At the same time, it looks like AFH is trying to work. If I monitor
  the value returned by 'hcitool afh', it changes. But this seems to
  have little effect on connection quality.

  Is this a problem with my hardware, or the AFH implementation? Is
  there a way to force bluetooth to not use the channels in use by WiFi?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/219057/+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 1737428] Re: VRF support to solve routing problems associated with multi-homing

2017-12-10 Thread Dmitrii Shcherbakov

** Description changed:

  Problem description:
  
  * a host is multi-homed if it has multiple network interfaces with L3
  addresses configured (physical or virtual interfaces, natural to
  OpenStack regardless of IPv4/IPv6 and IPv6 in general);
  
  * if all hosts that need to participate in L3 communication are located
  on the same L2 network there is no need for a routing device to be
  present. ARP/NDP and auto-created directly connected routes are enough;
  
  * multi-homing with hosts located on different L2 networks requires more 
intelligent routing:
-   - "directly connected" routes are no longer enough to talk to all relevant 
hosts in the same network space;
-   - a default gateway in the main routing table may not be the correct 
routing device that knows where to forward traffic (management network traffic 
goes to a management switch and router, other traffic goes to L3 ToR switch but 
may go via different bonds);
-   - even if a default gateway knows where to forward traffic, it may not be 
the intended physical path (storage replication traffic must go through a 
specific outgoing interface, not the same interface as storage access traffic 
although both interfaces are connected to the same ToR);
-   - there is no longer a single "default gateway" as applications need either 
per-logical-direction routers or to become routers themselves (if destination 
== X, forward to next-hop Y). Leaf-spine architecture is a good example of how 
multiple L2 networks force you to use spaces that have VLANs in different 
switch fabrics => one or more hops between hosts with interfaces associated 
with the same network space;
-   - while network spaces implicitly require L3 reachability between each host 
that has a NIC associated with a network space, the current definition does not 
mention routing infrastructure required for that. For a single L2 this problem 
is hidden by directly connected routes, for multi-L2, no solution is provided 
or discussed;
+   - "directly connected" routes are no longer enough to talk to all relevant 
hosts in the same network space;
+   - a default gateway in the main routing table may not be the correct 
routing device that knows where to forward traffic (management network traffic 
goes to a management switch and router, other traffic goes to L3 ToR switch but 
may go via different bonds);
+   - even if a default gateway knows where to forward traffic, it may not be 
the intended physical path (storage replication traffic must go through a 
specific outgoing interface, not the same interface as storage access traffic 
although both interfaces are connected to the same ToR);
+   - there is no longer a single "default gateway" as applications need either 
per-logical-direction routers or to become routers themselves (if destination 
== X, forward to next-hop Y). Leaf-spine architecture is a good example of how 
multiple L2 networks force you to use spaces that have VLANs in different 
switch fabrics => one or more hops between hosts with interfaces associated 
with the same network space;
+   - while network spaces implicitly require L3 reachability between each host 
that has a NIC associated with a network space, the current definition does not 
mention routing infrastructure required for that. For a single L2 this problem 
is hidden by directly connected routes, for multi-L2, no solution is provided 
or discussed;
  
  * existing solutions to multi-homing require routing table management on
  a given host: complex static routing rules, dynamic routing (e.g.
  running an OSPF or BGP daemon on a host);
  
  * using static routes is rigid and requires network planning (i.e.
  working with network engineers which may have varying degrees of
  experience, doing VLSM planning etc.);
  
  * using dynamic routing requires a broader integration into an
  organization's L3 network infrastructure. Routing can be implemented
  differently across different organizations and it is a security and
  operational burden to integrate with a company's routing infrastructure.
  
  Summary: a mechanism is needed to associate an interface with a
  forwarding table (FIB) which has its own default gateway and make an
  application with a listen(2)ing socket(2) return connected sockets
  associated with different FIBs. In other words, applications need to
  implicitly get source/destination-based routing capabilities without the
  need to use static routing schemes or dynamic routing and with minimum
  or no modifications to the applications themselves.
  
  Goals:
  
  * avoid turning individual hosts into routers;
  * avoid complex static rules;
  * better support multi-fabric deployments with minimum effort (Juju, charms, 
MAAS, applications, network infrastructure);
  * reduce operational complexity (custom L3 infrastructure integration for 
each deployment);
  * reduce delivery risks (L3 infrastructure, L3 department responsiveness 
varies);
  * avoid any form of L2 stretching at the

[Kernel-packages] [Bug 1737428] Missing required logs.

2017-12-10 Thread Ubuntu Kernel Bot

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1737428

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
   Status: New => Incomplete

-- 
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/1737428

Title:
  VRF support to solve routing problems associated with multi-homing

Status in juju:
  New
Status in MAAS:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Problem description:

  * a host is multi-homed if it has multiple network interfaces with L3
  addresses configured (physical or virtual interfaces, natural to
  OpenStack regardless of IPv4/IPv6 and IPv6 in general);

  * if all hosts that need to participate in L3 communication are
  located on the same L2 network there is no need for a routing device
  to be present. ARP/NDP and auto-created directly connected routes are
  enough;

  * multi-homing with hosts located on different L2 networks requires more 
intelligent routing:
- "directly connected" routes are no longer enough to talk to all relevant 
hosts in the same network space;
- a default gateway in the main routing table may not be the correct 
routing device that knows where to forward traffic (management network traffic 
goes to a management switch and router, other traffic goes to L3 ToR switch but 
may go via different bonds);
- even if a default gateway knows where to forward traffic, it may not be 
the intended physical path (storage replication traffic must go through a 
specific outgoing interface, not the same interface as storage access traffic 
although both interfaces are connected to the same ToR);
- there is no longer a single "default gateway" as applications need either 
per-logical-direction routers or to become routers themselves (if destination 
== X, forward to next-hop Y). Leaf-spine architecture is a good example of how 
multiple L2 networks force you to use spaces that have VLANs in different 
switch fabrics => one or more hops between hosts with interfaces associated 
with the same network space;
- while network spaces implicitly require L3 reachability between each host 
that has a NIC associated with a network space, the current definition does not 
mention routing infrastructure required for that. For a single L2 this problem 
is hidden by directly connected routes, for multi-L2, no solution is provided 
or discussed;

  * existing solutions to multi-homing require routing table management
  on a given host: complex static routing rules, dynamic routing (e.g.
  running an OSPF or BGP daemon on a host);

  * using static routes is rigid and requires network planning (i.e.
  working with network engineers which may have varying degrees of
  experience, doing VLSM planning etc.);

  * using dynamic routing requires a broader integration into an
  organization's L3 network infrastructure. Routing can be implemented
  differently across different organizations and it is a security and
  operational burden to integrate with a company's routing
  infrastructure.

  Summary: a mechanism is needed to associate an interface with a
  forwarding table (FIB) which has its own default gateway and make an
  application with a listen(2)ing socket(2) return connected sockets
  associated with different FIBs. In other words, applications need to
  implicitly get source/destination-based routing capabilities without
  the need to use static routing schemes or dynamic routing and with
  minimum or no modifications to the applications themselves.

  Goals:

  * avoid turning individual hosts into routers;
  * avoid complex static rules;
  * better support multi-fabric deployments with minimum effort (Juju, charms, 
MAAS, applications, network infrastructure);
  * reduce operational complexity (custom L3 infrastructure integration for 
each deployment);
  * reduce delivery risks (L3 infrastructure, L3 department responsiveness 
varies);
  * avoid any form of L2 stretching at the infrastructure level - this is 
inefficient for various reasons.

  NOTE: https://cumulusnetworks.com/blog/vrf-for-linux/ - I recommend to
  read this post to understand suggestions below.

  How to solve it?

  What does it mean for Juju to support VRF devices?

  * enslave certain devices on provisioning based on network space information 
(physical NICs, VLAN devices, bonds AND bridges created for containers must be 
considered) - VRF devices logically enslave devices similar to bridges but work

[Kernel-packages] [Bug 1737428] Re: VRF support to solve routing problems associated with multi-homing

2017-12-10 Thread Dmitrii Shcherbakov

For Ubuntu kernel this is a backport request.

-- 
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/1737428

Title:
  VRF support to solve routing problems associated with multi-homing

Status in juju:
  New
Status in MAAS:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Problem description:

  * a host is multi-homed if it has multiple network interfaces with L3
  addresses configured (physical or virtual interfaces, natural to
  OpenStack regardless of IPv4/IPv6 and IPv6 in general);

  * if all hosts that need to participate in L3 communication are
  located on the same L2 network there is no need for a routing device
  to be present. ARP/NDP and auto-created directly connected routes are
  enough;

  * multi-homing with hosts located on different L2 networks requires more 
intelligent routing:
- "directly connected" routes are no longer enough to talk to all relevant 
hosts in the same network space;
- a default gateway in the main routing table may not be the correct 
routing device that knows where to forward traffic (management network traffic 
goes to a management switch and router, other traffic goes to L3 ToR switch but 
may go via different bonds);
- even if a default gateway knows where to forward traffic, it may not be 
the intended physical path (storage replication traffic must go through a 
specific outgoing interface, not the same interface as storage access traffic 
although both interfaces are connected to the same ToR);
- there is no longer a single "default gateway" as applications need either 
per-logical-direction routers or to become routers themselves (if destination 
== X, forward to next-hop Y). Leaf-spine architecture is a good example of how 
multiple L2 networks force you to use spaces that have VLANs in different 
switch fabrics => one or more hops between hosts with interfaces associated 
with the same network space;
- while network spaces implicitly require L3 reachability between each host 
that has a NIC associated with a network space, the current definition does not 
mention routing infrastructure required for that. For a single L2 this problem 
is hidden by directly connected routes, for multi-L2, no solution is provided 
or discussed;

  * existing solutions to multi-homing require routing table management
  on a given host: complex static routing rules, dynamic routing (e.g.
  running an OSPF or BGP daemon on a host);

  * using static routes is rigid and requires network planning (i.e.
  working with network engineers which may have varying degrees of
  experience, doing VLSM planning etc.);

  * using dynamic routing requires a broader integration into an
  organization's L3 network infrastructure. Routing can be implemented
  differently across different organizations and it is a security and
  operational burden to integrate with a company's routing
  infrastructure.

  Summary: a mechanism is needed to associate an interface with a
  forwarding table (FIB) which has its own default gateway and make an
  application with a listen(2)ing socket(2) return connected sockets
  associated with different FIBs. In other words, applications need to
  implicitly get source/destination-based routing capabilities without
  the need to use static routing schemes or dynamic routing and with
  minimum or no modifications to the applications themselves.

  Goals:

  * avoid turning individual hosts into routers;
  * avoid complex static rules;
  * better support multi-fabric deployments with minimum effort (Juju, charms, 
MAAS, applications, network infrastructure);
  * reduce operational complexity (custom L3 infrastructure integration for 
each deployment);
  * reduce delivery risks (L3 infrastructure, L3 department responsiveness 
varies);
  * avoid any form of L2 stretching at the infrastructure level - this is 
inefficient for various reasons.

  NOTE: https://cumulusnetworks.com/blog/vrf-for-linux/ - I recommend to
  read this post to understand suggestions below.

  How to solve it?

  What does it mean for Juju to support VRF devices?

  * enslave certain devices on provisioning based on network space information 
(physical NICs, VLAN devices, bonds AND bridges created for containers must be 
considered) - VRF devices logically enslave devices similar to bridges but work 
differently (on L3, not L2);
  * the above is per network namespace so it will work equally well in a LXD 
container;

  Conceptually:

  # echo 'net.ipv4.tcp_l3mdev_accept = 1' >> /etc/sysctl.conf
  # echo 'net.ipv4.udp_l3mdev_accept = 1' >> /etc/sysctl.conf
  # sysctl -p

  # ip link add mgmt type vrf table 1 && ip link set dev mgmt up
  # ip link add pub type vrf table 2 && ip link set dev pub up

  # ip link set mgmtbr0 master management
  # ip link set pubbr0 master public

  # make your services use INADDR_ANY for listening sockets in charms if
  not done

[Kernel-packages] [Bug 1737428] [NEW] VRF support to solve routing problems associated with multi-homing

2017-12-10 Thread Dmitrii Shcherbakov

Public bug reported:

Problem description:

* a host is multi-homed if it has multiple network interfaces with L3
addresses configured (physical or virtual interfaces, natural to
OpenStack regardless of IPv4/IPv6 and IPv6 in general);

* if all hosts that need to participate in L3 communication are located
on the same L2 network there is no need for a routing device to be
present. ARP/NDP and auto-created directly connected routes are enough;

* multi-homing with hosts located on different L2 networks requires more 
intelligent routing:
  - "directly connected" routes are no longer enough to talk to all relevant 
hosts in the same network space;
  - a default gateway in the main routing table may not be the correct routing 
device that knows where to forward traffic (management network traffic goes to 
a management switch and router, other traffic goes to L3 ToR switch but may go 
via different bonds);
  - even if a default gateway knows where to forward traffic, it may not be the 
intended physical path (storage replication traffic must go through a specific 
outgoing interface, not the same interface as storage access traffic although 
both interfaces are connected to the same ToR);
  - there is no longer a single "default gateway" as applications need either 
per-logical-direction routers or to become routers themselves (if destination 
== X, forward to next-hop Y). Leaf-spine architecture is a good example of how 
multiple L2 networks force you to use spaces that have VLANs in different 
switch fabrics => one or more hops between hosts with interfaces associated 
with the same network space;
  - while network spaces implicitly require L3 reachability between each host 
that has a NIC associated with a network space, the current definition does not 
mention routing infrastructure required for that. For a single L2 this problem 
is hidden by directly connected routes, for multi-L2, no solution is provided 
or discussed;

* existing solutions to multi-homing require routing table management on
a given host: complex static routing rules, dynamic routing (e.g.
running an OSPF or BGP daemon on a host);

* using static routes is rigid and requires network planning (i.e.
working with network engineers which may have varying degrees of
experience, doing VLSM planning etc.);

* using dynamic routing requires a broader integration into an
organization's L3 network infrastructure. Routing can be implemented
differently across different organizations and it is a security and
operational burden to integrate with a company's routing infrastructure.

Summary: a mechanism is needed to associate an interface with a
forwarding table (FIB) which has its own default gateway and make an
application with a listen(2)ing socket(2) return connected sockets
associated with different FIBs. In other words, applications need to
implicitly get source/destination-based routing capabilities without the
need to use static routing schemes or dynamic routing and with minimum
or no modifications to the applications themselves.

Goals:

* avoid turning individual hosts into routers;
* avoid complex static rules;
* better support multi-fabric deployments with minimum effort (Juju, charms, 
MAAS, applications, network infrastructure);
* reduce operational complexity (custom L3 infrastructure integration for each 
deployment);
* reduce delivery risks (L3 infrastructure, L3 department responsiveness 
varies);
* avoid any form of L2 stretching at the infrastructure level - this is 
inefficient for various reasons.

NOTE: https://cumulusnetworks.com/blog/vrf-for-linux/ - I recommend to
read this post to understand suggestions below.

How to solve it?

What does it mean for Juju to support VRF devices?

* enslave certain devices on provisioning based on network space information 
(physical NICs, VLAN devices, bonds AND bridges created for containers must be 
considered) - VRF devices logically enslave devices similar to bridges but work 
differently (on L3, not L2);
* the above is per network namespace so it will work equally well in a LXD 
container;

Conceptually:

# echo 'net.ipv4.tcp_l3mdev_accept = 1' >> /etc/sysctl.conf
# echo 'net.ipv4.udp_l3mdev_accept = 1' >> /etc/sysctl.conf
# sysctl -p

# ip link add mgmt type vrf table 1 && ip link set dev mgmt up
# ip link add pub type vrf table 2 && ip link set dev pub up

# ip link set mgmtbr0 master management
# ip link set pubbr0 master public

# make your services use INADDR_ANY for listening sockets in charms if
not done already (use 0.0.0.0)

charm-related:

* (no-op) services with listening sockets on INADDR_ANY will not need
any modifications either on the charm side or at the application level -
this is the cheapest way to solve multi-homing problems;

* (later) a more advanced functionality for applications that do not use
INADDR_ANY but bind a listening socket to a specific address - this
requires `ip vrf exec` functionality in iproute2 or application
modifications.

Notes:

* Let's

[Kernel-packages] [Bug 1716301] Re: wifi driver: mt7601u not work on 16.04

2017-12-10 Thread Thomas P.

Unfortunately the workaround from the previous post did not work for me.
Do still get the same error.

-- 
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/1716301

Title:
  wifi driver: mt7601u not work on 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in usb-modeswitch-data package in Ubuntu:
  Confirmed

Bug description:
  In the beginning, when the adapter is pluged in, it's mounted as a disk 
including driver files for Windows, and
  $> lsusb
  Bus 003 Device 010: ID 148f:2878 Ralink Technology, Corp.

  after eject the disk,
  $> lsusb
  Bus 003 Device 011: ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless 
Adapter

  I tried following 3 drivers:
  1) the default mt7601u included in the kernel: 4.4.0-91-generic
  after eject the disk,
  $> lsmod|grep mt
  mt7601u 102400 0
  mac80211 737280 1 mt7601u
  cfg80211 565248 2 mac80211,mt7601u
  binfmt_misc 20480 1
  $> modinfo mt7601u
  filename: 
/lib/modules/4.4.0-91-generic/kernel/drivers/net/wireless/mediatek/mt7601u/mt7601u.ko
  srcversion: E8B632D369E0C2A9F1CF7D8
  alias: usb:v7392p7710d*dc*dsc*dp*ic*isc*ip*in*
  ..
  depends: mac80211,cfg80211
  intree: Y
  vermagic: 4.4.0-91-generic SMP mod_unload modversions

  $> dmesg
  // begin
  [ 4581.094119] usb 3-4: USB disconnect, device number 6
  [ 4584.872751] usb 3-4: new high-speed USB device number 7 using xhci_hcd
  [ 4585.001408] usb 3-4: New USB device found, idVendor=148f, idProduct=2878
  [ 4585.001413] usb 3-4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [ 4585.001416] usb 3-4: Product: Љ
  [ 4585.001418] usb 3-4: Manufacturer: Љ
  [ 4585.001753] usb-storage 3-4:1.0: USB Mass Storage device detected
  [ 4585.001873] scsi host6: usb-storage 3-4:1.0
  [ 4586.001122] scsi 6:0:0:0: CD-ROM MediaTek Flash autorun 0.01 PQ: 0 ANSI: 0 
CCS
  [ 4586.001978] sr 6:0:0:0: [sr0] scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda 
tray
  [ 4586.002529] sr 6:0:0:0: Attached scsi CD-ROM sr0
  [ 4586.002716] sr 6:0:0:0: Attached scsi generic sg1 type 5
  [ 4619.658385] ISO 9660 Extensions: Microsoft Joliet Level 3
  [ 4619.691737] ISOFS: changing to secondary root
  [ 4691.563347] usb 3-4: USB disconnect, device number 7
  [ 4693.638315] usb 3-4: new high-speed USB device number 8 using xhci_hcd
  [ 4693.766896] usb 3-4: New USB device found, idVendor=148f, idProduct=2878
  [ 4693.766901] usb 3-4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [ 4693.766903] usb 3-4: Product: Љ
  [ 4693.766905] usb 3-4: Manufacturer: Љ
  [ 4693.767338] usb-storage 3-4:1.0: USB Mass Storage device detected
  [ 4693.768063] scsi host7: usb-storage 3-4:1.0
  [ 4694.766737] scsi 7:0:0:0: CD-ROM MediaTek Flash autorun 0.01 PQ: 0 ANSI: 0 
CCS
  [ 4694.767423] sr 7:0:0:0: [sr0] scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda 
tray
  [ 4694.767908] sr 7:0:0:0: Attached scsi CD-ROM sr0
  [ 4694.768147] sr 7:0:0:0: Attached scsi generic sg1 type 5
  [ 4728.418255] ISO 9660 Extensions: Microsoft Joliet Level 3
  [ 4728.427856] ISOFS: changing to secondary root
  [ 4733.824182] sr 7:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_OK
  [ 4733.824190] sr 7:0:0:0: [sr0] tag#0 CDB: Start/Stop Unit 1b 00 00 00 02 00
  [ 4733.824218] usb 3-4: USB disconnect, device number 8
  [ 4733.824281] sr 7:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_OK
  [ 4733.824291] sr 7:0:0:0: [sr0] tag#0 CDB: Prevent/Allow Medium Removal 1e 
00 00 00 00 00
  [ 4734.099901] usb 3-4: new high-speed USB device number 9 using xhci_hcd
  [ 4734.238749] usb 3-4: New USB device found, idVendor=148f, idProduct=7601
  [ 4734.238754] usb 3-4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [ 4734.238757] usb 3-4: Product: 802.11 n WLAN
  [ 4734.238772] usb 3-4: Manufacturer: MediaTek
  [ 4734.238775] usb 3-4: SerialNumber: 1.0
  [ 4735.432096] usb 3-4: reset high-speed USB device number 9 using xhci_hcd
  [ 4735.562543] mt7601u 3-4:1.0: ASIC revision: 76010001 MAC revision: 76010500
  [ 4735.563089] mt7601u 3-4:1.0: Firmware Version: 0.1.00 Build: 7640 Build 
time: 201302052146
  [ 4739.011624] mt7601u 3-4:1.0: Vendor request req:07 off:09a8 failed:-110
  [ 4742.131399] mt7601u 3-4:1.0: Vendor request req:02 off:09a8 failed:-110
  [ 4745.251254] mt7601u 3-4:1.0: Vendor request req:07 off:0734 failed:-110
  [ 4748.371056] mt7601u 3-4:1.0: Vendor request req:42 off:0230 failed:-110
  [ 4751.490880] mt7601u 3-4:1.0: Vendor request req:07 off:0080 failed:-110
  [ 4754.610694] mt7601u 3-4:1.0: Vendor request req:02 off:0080 failed:-110
  [ 4757.730501] mt7601u 3-4:1.0: Vendor request req:02 off:0080 failed:-110
  [ 4757.730548] mt7601u: probe of 3-4:1.0 failed with error -110
  [ 4757.730870] usbcore: registered new interface driver mt7601u
  // end 

  $> sudo ifconfig -a // do not list any new

[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2017-12-10 Thread Hernan de Soto

I just installed Ubuntu 17.10 on my Lenovo G50-80, and after intallation I 
restarted and didn't see grub, so I wasn't able to load Windows, I tried Boot 
Repair and it said that I wasn't on a EFI session or something... I went to the 
BIOS, changed it back to UEFI, saved, booted,  still the same problem.
Back to BIOS and I don't see any of the changes I made! I even have an Admin 
password on the BIOS, I removed the password so to access BIOS directly, save 
BIOS settings, restart... and admin password is asked again.
I found this thread and I find it very disturbing that Ubuntu is doing this to 
my machine, very distrubing and upset.
Does anyone knows what's causing this?

Thanks!

-- 
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/1734147

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Confirmed

Bug description:
  Hi all,

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

   UPDATE (01/12/2017) 

  LENOVO machines affected so far (please add your affected model to
  this list):

  Lenovo Y50-70
  Lenovo G40-30
  Lenovo U31-70
  Lenovo G50-70
  Lenovo Z50-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo G50-80
  Lenovo S20-30
  Lenovo Yoga 2 11" - 20332
  Lenovo B40-70

  ---

  Temporary workaround:
  https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t
  -Save-Settings-Or-Exit/m-p/3853208#M157885

  ---

  result from apport-collect 1734147:

  ---

  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tob1608 F pulseaudio
   /dev/snd/controlC0:  tob1608 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-10-22 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20378
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  Tags:  artful wayland-session
  Uname: Linux 4.13.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/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ECN43WW(V3.03)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo Y50-70
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20378
  dmi.product.version: Lenovo Y50-70
  dmi.sys.vendor: LENOVO

  ---

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+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 1725762] Re: Errors starting from live DVD Dell New I7 15 XPS

2017-12-10 Thread Norbert

Many users are affected with this bug - see search results on AskUbuntu
https://askubuntu.com/search?q=tsc_deadline+errata+0x52+is%3Aquestion

All they have problems with intel-microcode:
1. https://askubuntu.com/questions/975297/17-10-will-not-shut-down-or-suspend

Acer Aspire F5,

kernel: [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please
update microcode to version: 0x52 (or later)

2. https://askubuntu.com/questions/984043/unable-to-make-changes-in-
bios-after-17-10-installation

HP Envy x360 u000

[0:00] [Firmware Bug]: TSC_DEADLINE disabled due to Errata;
please update microcode to version: 0x52 (or later)

3. https://askubuntu.com/questions/984970/best-approach-for-dealing-
with-system-bugs

[Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update
microcode to version: 0x52 (or later)

4. https://askubuntu.com/questions/948858/ubuntu-stuck-at-busybox-
firmware-bug-tsc-deadline-disabled-due-to-errata-p

[0:00] [Firmware Bug]: TSC_DEADLINE disabled due to Errata;
please update microcode to version: 0x52 (or later)

5. https://askubuntu.com/questions/976570/how-to-fix-this-bug

Intel(R) Core(TM) i7-7920HQ CPU @ 3.10GHz

[0.00] [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please
update microcode to version: 0x52 (or later)

6. https://askubuntu.com/questions/984720/firmware-bug-tsc-deadline-
disabled-due-to-errata-please-update-microcode-to

Intel(R) Core(TM) i5-7300HQ CPU @ 2.50GHz, 2501 MHz, 4 core(s), 4
thread(s)

[Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update
microcode to version: 0x52 (or later)

7. https://askubuntu.com/questions/966432/ubuntu-17-10-boot-problem

[0:00] [Firmware Bug]: TSC_DEADLINE disabled due to Errata;
please update microcode to version: 0x52 (or later)


Please update intel-microcode on all supported distros to the latest version 
from Debian or somewhere upstream.

** Summary changed:

- Errors starting from live DVD Dell New I7 15 XPS
+ [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode 
to version: 0x52 (or later) - Errors starting from live DVD Dell New I7 15 XPS

** Changed in: intel-microcode (Ubuntu)
   Status: New => Confirmed

** Tags removed: bot-comment
** Tags added: bionic xenial zesty

-- 
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/1725762

Title:
  [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update
  microcode to version: 0x52 (or later) - Errors starting from live DVD
  Dell New I7 15 XPS

Status in intel-microcode package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10 64Bit Loading on New Dell XPS 15 I7 - Screenshot
  attached. Tested on another PC and it loaded fine.

  When booting from a Ubuntu 17.10 Live (Installed on USB with Etcher) I
  get the following:

  [Firmware Bug} TSC_Deadline disabled due to Errata - Please update Mirocode 
to version 0x52 Or Later
  ACPI Error \_.PCIO.XHC_.RHUB.HS11 Namespace Lookup Error

  ACPI Error 1 table load failiures.

  USB USB2-Port: Cannot enable

  Watchdog: BUG: soft lockup - CPU#6 stuck for 22s PlymouthD 283

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1725762/+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 1725762] Re: Errors starting from live DVD Dell New I7 15 XPS

2017-12-10 Thread Norbert

** Also affects: intel-microcode (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/1725762

Title:
  [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update
  microcode to version: 0x52 (or later) - Errors starting from live DVD
  Dell New I7 15 XPS

Status in intel-microcode package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10 64Bit Loading on New Dell XPS 15 I7 - Screenshot
  attached. Tested on another PC and it loaded fine.

  When booting from a Ubuntu 17.10 Live (Installed on USB with Etcher) I
  get the following:

  [Firmware Bug} TSC_Deadline disabled due to Errata - Please update Mirocode 
to version 0x52 Or Later
  ACPI Error \_.PCIO.XHC_.RHUB.HS11 Namespace Lookup Error

  ACPI Error 1 table load failiures.

  USB USB2-Port: Cannot enable

  Watchdog: BUG: soft lockup - CPU#6 stuck for 22s PlymouthD 283

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1725762/+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 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2017-12-10 Thread kevh

Same problem here. Lenovo Ideapad Flex 10. Came with windows 8 installed and 
updated to windows 10. Had Ubuntu 14.04 installed as dual boot and had each 
release of Ubuntu updated since 14.04.
I was dual booting using legacy for Ubuntu and UEFI for occasional access to 
windows 10. Only recent change has been upgrade to version 17.10. I can no 
longer save changes to the boot order in the BIOS. I cannot therefore boot from 
USB and am not able to boot into windows.
We need an explanation of what has has happened during the upgrade and whether 
or not there is a viable solution or workaround.
The trigger for this problem arising was clearly the upgrade from 17.04 to 
17.10. Given that, my expectation is that Canonical will take responsibility 
for finding the root cause and giving us some alternative solutions / 
workarounds.

-- 
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/1734147

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Confirmed

Bug description:
  Hi all,

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

   UPDATE (01/12/2017) 

  LENOVO machines affected so far (please add your affected model to
  this list):

  Lenovo Y50-70
  Lenovo G40-30
  Lenovo U31-70
  Lenovo G50-70
  Lenovo Z50-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo G50-80
  Lenovo S20-30
  Lenovo Yoga 2 11" - 20332
  Lenovo B40-70

  ---

  Temporary workaround:
  https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t
  -Save-Settings-Or-Exit/m-p/3853208#M157885

  ---

  result from apport-collect 1734147:

  ---

  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tob1608 F pulseaudio
   /dev/snd/controlC0:  tob1608 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-10-22 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20378
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  Tags:  artful wayland-session
  Uname: Linux 4.13.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/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ECN43WW(V3.03)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo Y50-70
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20378
  dmi.product.version: Lenovo Y50-70
  dmi.sys.vendor: LENOVO

  ---

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+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 405525] better than ever

2017-12-10 Thread heinrich

I feel wonderful , just better  than previously and all that thanks to
an excellent book I've read recently !  you are going to also read it
here
http://www.angelesruiz.org/agtgx.php?UE80MDU1MjVAYnVncy5sYXVuY2hwYWQubmV0

-- 
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/405525

Title:
  [Hewlett-Packard HP Pavilion ze2000 (EC205UA#ABA)] suspend/resume
  failure

Status in linux package in Ubuntu:
  Expired

Bug description:
  Under 8.10 suspend worked pretty much flawlessly. Installed Karmic as
  9.04 my sound card would not work for some reason. may end up going
  back to 8.10 as My vid card is not supported anymore by ATI after that
  version. but that is not here nor there. tried to wake up my laptop
  like normal. system stayed at black screen. backlight sis not come on.
  I know this is alpha and I am not mad but I am reporting this so the
  developers know it. I have no idea what caused the problem but
  hopefully the bug catcher included stuff to help trace it. If not
  please delete this bug as I have no other Idea what could have caused
  it.

  Thanks for making a great product. I have used Ubuntu since 6.06 and
  have watched it get better and better every release (with exception to
  9.04) ;)

  thanks again guys.

  ProblemType: KernelOops
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  Architecture: i386
  Date: Mon Jul 27 17:10:03 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=3a408910-86e2-46ec-a784-90545d8f3f2c
  InterpreterPath: /usr/bin/python2.6
  MachineType: Hewlett-Packard HP Pavilion ze2000 (EC205UA#ABA)
  Package: linux-image-2.6.31-4-generic 2.6.31-4.22
  ProcCmdLine: root=UUID=fe6d390e-5c59-40db-98f8-09dbdbd0b864 ro vga=792
  ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
  ProcEnviron: PATH=(custom, no user)
  ProcVersionSignature: Ubuntu 2.6.31-4.22-generic
  RelatedPackageVersions: linux-backports-modules-2.6.31-4-generic N/A
  SourcePackage: linux
  Tags: resume suspend
  Title: [Hewlett-Packard HP Pavilion ze2000 (EC205UA#ABA)] suspend/resume 
failure
  Uname: Linux 2.6.31-4-generic i686
  UserGroups:
   
  dmi.bios.date: 02/24/2006
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.24
  dmi.board.name: 3096
  dmi.board.vendor: Quanta
  dmi.board.version: 47.0E
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.24:bd02/24/2006:svnHewlett-Packard:pnHPPavilionze2000(EC205UA#ABA):pvrRev1:rvnQuanta:rn3096:rvr47.0E:cvnQuanta:ct10:cvrN/A:
  dmi.product.name: HP Pavilion ze2000 (EC205UA#ABA)
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/405525/+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 1554613] Re: Screen flickers on XPS 13 9350/9550 (Intel Skylake/Broadwell GPU)

2017-12-10 Thread Gustavo L

Flickering still going on my Dell Inspiron N4050

Linux N4050 4.10.0-42-generic #46~16.04.1-Ubuntu SMP Mon Dec 4 15:57:59
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux


LSB Version:
core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:printing-9.20160110ubuntu0.2-amd64:printing-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
Distributor ID: Ubuntu
Description:Ubuntu 16.04.3 LTS
Release:16.04
Codename:   xenial


  *-display   
   description: VGA compatible controller
   product: 2nd Generation Core Processor Family Integrated Graphics 
Controller
   vendor: Intel Corporation
   physical id: 2
   bus info: pci@:00:02.0
   version: 09
   width: 64 bits
   clock: 33MHz
   capabilities: msi pm vga_controller bus_master cap_list rom
   configuration: driver=i915 latency=0
   resources: irq:27 memory:f680-f6bf memory:e000-efff 
ioport:f000(size=64) memory:c-d

-- 
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/1554613

Title:
  Screen flickers on XPS 13 9350/9550 (Intel Skylake/Broadwell GPU)

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  *** Temporary workaround ***
  Install Kernel from the following location:
  - http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety/

  OR
  Perform the following:
  - $ apt-add-repository "deb 
http://ppa.launchpad.net/canonical-kernel-team/ppa/ubuntu yakkety main"
  - $ echo -en "Package: *\nPin: release 
o=LP-PPA-canonical-kernel-team-ppa\nPin-Priority: -1\n" >> 
/etc/apt/preferences.d/canonical-kernel-team-ubuntu-ppa-yakkety
  - $ apt update
  - $ apt install linux-image-extra-4.6.0-6-generic 
linux-headers-4.6.0-6-generic linux-tools-4.6.0-6-generic
  ```
  There was a typo in instructions (/etc/preferences.d should have been 
/etc/apt/preferences.d).
  As result you might have upgraded Linux META packages and therefor you won't 
receive proper upgrades of Xenial native Linux packages (hoping they will ever 
contain the fix).
  I suggest you move 
/etc/preferences.d/canonical-kernel-team-ubuntu-ppa-yakkety to 
/etc/apt/preferences.d/ and downgrade related packages:
  $ apt update
  $ apt install linux-headers-generic/xenial-updates 
linux-tools-generic/xenial-updates linux-image-generic/xenial-updates
  ```
  ***

  Please inspect duplicate reports for more details:
  Bug #1522922
  Bug #1535048
  Bug #1552304
  Bug #1555158
  Bug #1561729
  Bug #1565234
  Bug #1568599
  Bug #1573392

  does not affect 4.4.0-8
  affects 4.4.0-9 to 4.4.0-22

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.11.12
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tbonfort   1498 F pulseaudio
  CurrentDesktop: KDE
  Date: Tue Mar  8 09:57:12 2016
  HibernationDevice: RESUME=UUID=3248e0d7-0dac-4ccc-8982-b5ac5ce6ed5e
  InstallationDate: Installed on 2016-01-07 (61 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia
   Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic 
root=UUID=757547b8-d0e4-4eb8-8afd-920b743f99a4 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-8-generic N/A
   linux-backports-modules-4.4.0-8-generic  N/A
   linux-firmware   1.156
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-02-28 (9 days ago)
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 07TYC2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1554613/+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 1730862] Re: package linux-image-extra-4.13.0-17-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/4.13.0-17-generic/kernel/drivers/net/wireless/in

2017-12-10 Thread Stickles01

Having the same issues with 4.13.0-19, can't upgrade anything, or
downgrade anything.

-- 
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/1730862

Title:
  package linux-image-extra-4.13.0-17-generic (not installed) failed to
  install/upgrade: unable to open
  
'/lib/modules/4.13.0-17-generic/kernel/drivers/net/wireless/intersil/hostap/hostap.ko
  .dpkg-new': Operation not permitted

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I ran software update and agreed to report several system probblems
  when prompted.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: linux-image-extra-4.13.0-17-generic (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  doc4488 F pulseaudio
   /dev/snd/controlC1:  doc4488 F pulseaudio
  Date: Tue Nov  7 22:40:02 2017
  DuplicateSignature:
   package:linux-image-extra-4.13.0-17-generic:(not installed)
   Unpacking linux-image-extra-4.13.0-17-generic (4.13.0-17.20) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-2jmHF3/09-linux-image-extra-4.13.0-17-generic_4.13.0-17.20_amd64.deb
 (--unpack):
unable to open 
'/lib/modules/4.13.0-17-generic/kernel/drivers/net/wireless/intersil/hostap/hostap.ko.dpkg-new':
 Operation not permitted
  ErrorMessage: unable to open 
'/lib/modules/4.13.0-17-generic/kernel/drivers/net/wireless/intersil/hostap/hostap.ko.dpkg-new':
 Operation not permitted
  HibernationDevice: RESUME=UUID=559dcc83-cf81-43b6-b17c-e024ec829072
  InstallationDate: Installed on 2016-01-18 (659 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: EVGA 122-CK-NF68
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=74393e40-c217-40dd-a9ff-e8fb9b6e4983 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu7
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-extra-4.13.0-17-generic (not installed) failed to 
install/upgrade: unable to open 
'/lib/modules/4.13.0-17-generic/kernel/drivers/net/wireless/intersil/hostap/hostap.ko.dpkg-new':
 Operation not permitted
  UpgradeStatus: Upgraded to artful on 2017-10-23 (16 days ago)
  dmi.bios.date: 01/22/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: 122-CK-NF68
  dmi.board.vendor: EVGA
  dmi.board.version: 2
  dmi.chassis.type: 3
  dmi.chassis.vendor: EVGA
  dmi.chassis.version: 122-CK-NF68
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd01/22/2008:svnEVGA:pn122-CK-NF68:pvr2:rvnEVGA:rn122-CK-NF68:rvr2:cvnEVGA:ct3:cvr122-CK-NF68:
  dmi.product.name: 122-CK-NF68
  dmi.product.version: 2
  dmi.sys.vendor: EVGA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730862/+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 1698700] Re: hibmc driver does not include "pci:" prefix in bus ID

[Kernel-packages] [Bug 1698700] Re: hibmc driver does not include "pci:" prefix in bus ID

[Kernel-packages] [Bug 1715609] Re: kernel warning: skb_warn_bad_offload

[Kernel-packages] [Bug 1722859] Re: wireless not working trace in dmesg

[Kernel-packages] [Bug 1722781] Re: package linux-image-4.4.0-97-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

[Kernel-packages] [Bug 1722880] Re: package linux-image-4.10.0-37-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

[Kernel-packages] [Bug 480046] what a place

[Kernel-packages] [Bug 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]

[Kernel-packages] [Bug 1576815] Re: No wireless access for BCM 43162 [14e4:43ae] rev 02

[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[Kernel-packages] [Bug 219057] Re: Bluetooth does not coexist with WiFi

[Kernel-packages] [Bug 1737428] Re: VRF support to solve routing problems associated with multi-homing

[Kernel-packages] [Bug 1737428] Missing required logs.

[Kernel-packages] [Bug 1737428] Re: VRF support to solve routing problems associated with multi-homing

[Kernel-packages] [Bug 1737428] [NEW] VRF support to solve routing problems associated with multi-homing

[Kernel-packages] [Bug 1716301] Re: wifi driver: mt7601u not work on 16.04

[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[Kernel-packages] [Bug 1725762] Re: Errors starting from live DVD Dell New I7 15 XPS

[Kernel-packages] [Bug 1725762] Re: Errors starting from live DVD Dell New I7 15 XPS

[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[Kernel-packages] [Bug 405525] better than ever

[Kernel-packages] [Bug 1554613] Re: Screen flickers on XPS 13 9350/9550 (Intel Skylake/Broadwell GPU)

[Kernel-packages] [Bug 1730862] Re: package linux-image-extra-4.13.0-17-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/4.13.0-17-generic/kernel/drivers/net/wireless/in

23 matches

Site Navigation

Mail list logo

Footer information