[Kernel-packages] [Bug 1802480] Re: Crash when using IPsec VTI interfaces on 4.15 and 4.18.

2019-03-27 Thread Jean-Philippe Menil
The fix is available in commit:
commit 0152eee6fc3b84298bb6a79961961734e8afa5b8
Author: Steffen Klassert 
Date:   Thu Nov 22 07:26:24 2018 +0100

xfrm: Fix NULL pointer dereference in xfrm_input when skb_dst_force clea
rs the dst_entry.

Could be nice to backport this one.

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

Title:
  Crash when using IPsec VTI interfaces on 4.15 and 4.18.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hey!

  After upgrading a few VPN to 4.15.0-38.41 (either Xenial or Bionic),
  we get random crashes. This also happens with the 4.18 in bionic-
  proposed. These crashes didn't happen with 4.4 from Xenial. Here is a
  stack trace:

  [   31.154360] BUG: unable to handle kernel NULL pointer dereference at 
0038
  [   31.162233] PGD 0 P4D 0
  [   31.164786] Oops:  [#1] SMP PTI
  [   31.168291] CPU: 5 PID: 42 Comm: ksoftirqd/5 Not tainted 4.18.0-11-generic 
#12~18.04.1-Ubuntu
  [   31.176854] Hardware name: Supermicro Super Server/X10SDV-4C-7TP4F, BIOS 
1.0b 11/21/2016
  [   31.184980] RIP: 0010:vti_rcv_cb+0xb9/0x1a0 [ip_vti]
  [   31.189962] Code: 8b 44 24 70 0f c8 89 87 b4 00 00 00 48 8b 86 20 05 00 00 
8b 80 f8 14 00 00 85 c0 75 05 48 85 d2 74 0e 48 8b 43 58 48 83 e0 fe  40 38 
04 74 7d 44 89 b3 b4 00 00 00 49 8b 44 24 20 48 39 86 20
  [   31.208916] RSP: 0018:bc61832e3920 EFLAGS: 00010246
  [   31.214160] RAX:  RBX: 9a3504964a00 RCX: 
0002
  [   31.221328] RDX: 9a351add4080 RSI: 9a351aa08000 RDI: 
9a3504964a00
  [   31.228485] RBP: bc61832e3940 R08: 0004 R09: 
c0aa612b
  [   31.235643] R10: 0008f09b99881884 R11: 1884bd4e2d6b1fac R12: 
9a3507b31900
  [   31.242803] R13: 9a3507b31000 R14:  R15: 
9a3504964a00
  [   31.249964] FS:  () GS:9a35bfd4() 
knlGS:
  [   31.258077] CS:  0010 DS:  ES:  CR0: 80050033
  [   31.263848] CR2: 0038 CR3: 00041a40a003 CR4: 
003606e0
  [   31.271004] DR0:  DR1:  DR2: 

  [   31.278163] DR3:  DR6: fffe0ff0 DR7: 
0400
  [   31.285320] Call Trace:
  [   31.287789]  xfrm4_rcv_cb+0x4a/0x70
  [   31.291297]  xfrm_input+0x58f/0x8f0
  [   31.294807]  vti_input+0xaa/0x110 [ip_vti]
  [   31.298926]  vti_rcv+0x33/0x3c [ip_vti]
  [   31.302783]  xfrm4_esp_rcv+0x39/0x50
  [   31.306375]  ip_local_deliver_finish+0x62/0x200
  [   31.310923]  ip_local_deliver+0xdf/0xf0
  [   31.314775]  ? ip_rcv_finish+0x420/0x420
  [   31.318718]  ip_rcv_finish+0x126/0x420
  [   31.322486]  ip_rcv+0x28f/0x360
  [   31.325655]  ? inet_del_offload+0x40/0x40
  [   31.329686]  __netif_receive_skb_core+0x48c/0xb70
  [   31.334413]  ? kmem_cache_alloc+0xb4/0x1d0
  [   31.338532]  ? __build_skb+0x2b/0xf0
  [   31.342128]  __netif_receive_skb+0x18/0x60
  [   31.346244]  ? __netif_receive_skb+0x18/0x60
  [   31.350536]  netif_receive_skb_internal+0x45/0xe0
  [   31.355263]  napi_gro_receive+0xc5/0xf0
  [   31.359141]  mlx5e_handle_rx_cqe+0x1b2/0x5d0 [mlx5_core]
  [   31.364476]  ? skb_release_all+0x24/0x30
  [   31.368430]  mlx5e_poll_rx_cq+0xd3/0x990 [mlx5_core]
  [   31.373432]  mlx5e_napi_poll+0x9b/0xc60 [mlx5_core]
  [   31.378333]  ? __switch_to_asm+0x34/0x70
  [   31.382270]  ? __switch_to_asm+0x40/0x70
  [   31.386214]  ? __switch_to_asm+0x34/0x70
  [   31.391056]  ? __switch_to_asm+0x40/0x70
  [   31.395905]  ? __switch_to_asm+0x34/0x70
  [   31.400743]  net_rx_action+0x140/0x3a0
  [   31.405379]  ? __switch_to+0xad/0x500
  [   31.409887]  __do_softirq+0xe4/0x2bb
  [   31.414448]  run_ksoftirqd+0x2b/0x40
  [   31.418862]  smpboot_thread_fn+0xfc/0x170
  [   31.423700]  kthread+0x121/0x140
  [   31.427701]  ? sort_range+0x30/0x30
  [   31.432040]  ? kthread_create_worker_on_cpu+0x70/0x70
  [   31.437816]  ret_from_fork+0x35/0x40
  [   31.442219] Modules linked in: esp6 authenc echainiv xfrm6_mode_tunnel 
xfrm4_mode_tunnel xfrm_user xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 
af_key xfrm_algo ip_vti ip_tunnel ip6_vti ip6_tunnel tunnel6 8021q garp mrp stp 
llc bonding ipt_REJECT nf_reject_ipv4 nfnetlink_log n
  fnetlink xt_NFLOG xt_hl xt_limit xt_nat xt_TCPMSS xt_HL xt_comment xt_tcpudp 
xt_multiport xt_conntrack iptable_filter iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 nf_nat xt_connmark xt_mark iptable_mangle xt_CT 
nf_conntrack xt_addrtype iptable_raw bpfilter ipmi_ssif gpio_
  ich intel_rapl sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp 
kvm_intel kvm irqbypass intel_cstate intel_rapl_perf input_leds joydev mei_me 
intel_pch_thermal ioatdma mei lpc_ich ipmi_si ipmi_devintf ipmi_msghandler 
acpi_pad mac_hid sch_fq_codel
  [   31.519488]  ib_iser rdma_cm iw_cm ib_cm iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi ip_tables 

[Kernel-packages] [Bug 1600371] Re: Gnome freezes for some seconds on simultaneous touch and stylus input (palm rejection fails)

2016-07-27 Thread Jean-Philippe Bernardy
** Package changed: linux (Ubuntu) => gnome-shell (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/1600371

Title:
  Gnome freezes for some seconds on simultaneous touch and stylus input
  (palm rejection fails)

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  My notebook (Lenovo Yoga S1) has a capacitive touch screen as well as
  an inductive screen for styluses. When I rest my palm on the screen
  and then hover my stylus above the screen so that the stylus is
  recognized and the mouse pointer follows it, and then move the stylus
  around Gnome seems to freeze for some seconds. The duration of the
  freeze is proportional to the time the notebook received simultaneous
  input from the two methods.

  "Freeze" means that the screen is not updated. Keyboard inputs that I
  make during the freeze would be executed after the freezing stops.

  I do not need to touch the screen with the stylus for the bug to
  occur. The bug occurs also when I actually touch the screen with the
  stylus.

  What I expect to happen (and what actually happens in all stylus-
  supporting tablets, running with Android or Windows) is that the input
  from the touch screen is rejected as long as the stylus is hovering
  above the screen.

  I'm running Ubuntu Gnome 16.04 (non-LTS) with the latest packages. The
  problem was present in 15.10 as well.

  I attach a script as a workaround solution.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  timeshifter   1787 F pulseaudio
   /dev/snd/controlC0:  timeshifter   1787 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=87cca434-274f-4464-9598-97fd7a1338fe
  InstallationDate: Installed on 2016-03-19 (111 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: LENOVO 20C0003SFR
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/zsh
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic 
root=UUID=e52c99ea-9646-4e8a-b8ad-c47b175ac5a3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.1
  Tags:  xenial
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-07-02 (6 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare scanner sudo vboxusers 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/29/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: B0ET33WW (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C0003SFR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrB0ET33WW(1.20):bd04/29/2016:svnLENOVO:pn20C0003SFR:pvrThinkPadS1Yoga:rvnLENOVO:rn20C0003SFR:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20C0003SFR
  dmi.product.version: ThinkPad S1 Yoga
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1600371/+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 1600371] Re: Gnome freezes for some seconds on simultaneous touch and stylus input (palm rejection fails)

2016-07-23 Thread Jean-Philippe Bernardy
The bug does not appear with a TWM session nor with a LXDE session. Thus
I think that we can safely conclude that this is in fact not a kernel
bug.

In my case it occurs only with gnome-shell.

** Tags removed: kernel-bug-exists-upstream

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

Title:
  Gnome freezes for some seconds on simultaneous touch and stylus input
  (palm rejection fails)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My notebook (Lenovo Yoga S1) has a capacitive touch screen as well as
  an inductive screen for styluses. When I rest my palm on the screen
  and then hover my stylus above the screen so that the stylus is
  recognized and the mouse pointer follows it, and then move the stylus
  around Gnome seems to freeze for some seconds. The duration of the
  freeze is proportional to the time the notebook received simultaneous
  input from the two methods.

  "Freeze" means that the screen is not updated. Keyboard inputs that I
  make during the freeze would be executed after the freezing stops.

  I do not need to touch the screen with the stylus for the bug to
  occur. The bug occurs also when I actually touch the screen with the
  stylus.

  What I expect to happen (and what actually happens in all stylus-
  supporting tablets, running with Android or Windows) is that the input
  from the touch screen is rejected as long as the stylus is hovering
  above the screen.

  I'm running Ubuntu Gnome 16.04 (non-LTS) with the latest packages. The
  problem was present in 15.10 as well.

  I attach a script as a workaround solution.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  timeshifter   1787 F pulseaudio
   /dev/snd/controlC0:  timeshifter   1787 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=87cca434-274f-4464-9598-97fd7a1338fe
  InstallationDate: Installed on 2016-03-19 (111 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: LENOVO 20C0003SFR
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/zsh
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic 
root=UUID=e52c99ea-9646-4e8a-b8ad-c47b175ac5a3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.1
  Tags:  xenial
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-07-02 (6 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare scanner sudo vboxusers 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/29/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: B0ET33WW (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C0003SFR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrB0ET33WW(1.20):bd04/29/2016:svnLENOVO:pn20C0003SFR:pvrThinkPadS1Yoga:rvnLENOVO:rn20C0003SFR:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20C0003SFR
  dmi.product.version: ThinkPad S1 Yoga
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1600371/+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 1600371] Re: Gnome freezes for some seconds on simultaneous touch and stylus input (palm rejection fails)

2016-07-19 Thread Jean-Philippe Bernardy
I could reproduce the bug with v4.7-rc7


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

** Tags added: kernel-bug-exists-upstream

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

Title:
  Gnome freezes for some seconds on simultaneous touch and stylus input
  (palm rejection fails)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My notebook (Lenovo Yoga S1) has a capacitive touch screen as well as
  an inductive screen for styluses. When I rest my palm on the screen
  and then hover my stylus above the screen so that the stylus is
  recognized and the mouse pointer follows it, and then move the stylus
  around Gnome seems to freeze for some seconds. The duration of the
  freeze is proportional to the time the notebook received simultaneous
  input from the two methods.

  "Freeze" means that the screen is not updated. Keyboard inputs that I
  make during the freeze would be executed after the freezing stops.

  I do not need to touch the screen with the stylus for the bug to
  occur. The bug occurs also when I actually touch the screen with the
  stylus.

  What I expect to happen (and what actually happens in all stylus-
  supporting tablets, running with Android or Windows) is that the input
  from the touch screen is rejected as long as the stylus is hovering
  above the screen.

  I'm running Ubuntu Gnome 16.04 (non-LTS) with the latest packages. The
  problem was present in 15.10 as well.

  I attach a script as a workaround solution.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  timeshifter   1787 F pulseaudio
   /dev/snd/controlC0:  timeshifter   1787 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=87cca434-274f-4464-9598-97fd7a1338fe
  InstallationDate: Installed on 2016-03-19 (111 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: LENOVO 20C0003SFR
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/zsh
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic 
root=UUID=e52c99ea-9646-4e8a-b8ad-c47b175ac5a3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.1
  Tags:  xenial
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-07-02 (6 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare scanner sudo vboxusers 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/29/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: B0ET33WW (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C0003SFR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrB0ET33WW(1.20):bd04/29/2016:svnLENOVO:pn20C0003SFR:pvrThinkPadS1Yoga:rvnLENOVO:rn20C0003SFR:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20C0003SFR
  dmi.product.version: ThinkPad S1 Yoga
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1600371/+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 1374965] Re: nvidia-setting crashes on startup

2014-12-20 Thread Jean-Philippe Orsini
Since the upgrade to nvidia 331.89, I no more reproduce the issue.

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

Title:
  nvidia-setting crashes on startup

Status in nvidia-settings package in Ubuntu:
  Confirmed

Bug description:
  nvidia-settings 
  *** Error in `nvidia-settings': free(): invalid pointer: 0x7fd8a5b0f623 
***
  Aborted

  NVidia card: Asus GeForce GT 730 - 2 Go (DDR3)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-settings 331.20-0ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Sep 28 14:35:00 2014
  InstallationDate: Installed on 2011-04-28 (1248 days ago)
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
  SourcePackage: nvidia-settings
  UpgradeStatus: Upgraded to trusty on 2014-04-17 (163 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1374965/+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 1374965] [NEW] nvidia-setting crashes on startup

2014-09-28 Thread Jean-Philippe Orsini
Public bug reported:

nvidia-settings 
*** Error in `nvidia-settings': free(): invalid pointer: 0x7fd8a5b0f623 ***
Aborted

NVidia card: Asus GeForce GT 730 - 2 Go (DDR3)

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: nvidia-settings 331.20-0ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
Uname: Linux 3.13.0-36-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.4
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Sep 28 14:35:00 2014
InstallationDate: Installed on 2011-04-28 (1248 days ago)
InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
SourcePackage: nvidia-settings
UpgradeStatus: Upgraded to trusty on 2014-04-17 (163 days ago)

** Affects: nvidia-settings (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty

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

Title:
  nvidia-setting crashes on startup

Status in “nvidia-settings” package in Ubuntu:
  New

Bug description:
  nvidia-settings 
  *** Error in `nvidia-settings': free(): invalid pointer: 0x7fd8a5b0f623 
***
  Aborted

  NVidia card: Asus GeForce GT 730 - 2 Go (DDR3)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-settings 331.20-0ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Sep 28 14:35:00 2014
  InstallationDate: Installed on 2011-04-28 (1248 days ago)
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
  SourcePackage: nvidia-settings
  UpgradeStatus: Upgraded to trusty on 2014-04-17 (163 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1374965/+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 1327741] Re: Kernel panic on driver rtl8821ae

2014-08-12 Thread Jean-Philippe Guérard
This issue also affects the latest Xubuntu installation image
(xubuntu-14.04.1-desktop-amd64.iso), which is not installable on an Asus
M11AD.

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

Title:
  Kernel panic on driver rtl8821ae

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Since kernel version 3.13.0-27, my Asus VM40B goes into kernel panic
  during boot, seemingly due to an error with the WiFi driver,
  rtl8821ae. The attached screenshot of the screen (I have no idea how
  to otherwise capture the output of a kernel panic) shows the error
  with kernel version 3.13.0-29, but it happens exactly the same with
  -27.

  WORKAROUND: Disabling the WiFi card or using version 3.13.0-24 does
  not cause any problem.

  Please bear in mind, while reading the generated report, that I have
  disabled the WiFi card to be able to boot with kernel -29.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1327741/+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 1320070] Re: Realtek Wifi card RTL8723BE drops connection with MSI enabled

2014-06-08 Thread Jean-Philippe
I'm having the same problem with my Lenovo Flex 2 with the same
rtl8723be wireless card.

Kernel :
3.13.0-29-generic #52-Ubuntu SMP Wed May 28 12:42:47 UTC 2014 x86_64 x86_64 
x86_64 GNU/Linux

gets the card to work.  Internet works for extended periods of time, but
will require the occasional reboot to get it back working.  I tried
upgrading to the v.3.15-rc8 I would break.  I would get notification
that it connected to the WiFi (DNS and all) but would never get any
internet connection.

Reverted back to kernel above and back in a working state - till my next
reboot.  Not sure if this information helps at all.

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

Title:
  Realtek Wifi card RTL8723BE drops connection with MSI enabled

Status in “linux” package in Ubuntu:
  In Progress
Status in “linux” source package in Trusty:
  Fix Released
Status in “linux” source package in Utopic:
  In Progress

Bug description:
  As my testing result with ThinkPad E540 and other users' report[1],
  RTL8723BE drops connection with MSI enabled, need to backport
  329d6e299f92a591acb3a80f6d597a5f9dce7e6d rtlwifi: rtl8723be: disable
  MSI interrupts mode

  [1] https://bugs.launchpad.net/bugs/1240940

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1320070/+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 889664] Re: No network access with Trendnet TU2-ET100

2013-08-19 Thread Jean-Philippe Guérard
As I already reported, this bug has been fixed in kernel 3.2. This
driver is working correctly with the current ubuntu kernels. HTH.

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

Title:
  No network access with Trendnet TU2-ET100

Status in The Linux Kernel:
  Invalid
Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I'm trying to use a USB Network adapter, Trendnet TU2-ET100 (AX88772).
  This adapter is managed by the asix.ko kernel module.

  When I boot with the adapter plugged-in, the adapter seems to
  configure cleanly, but I get no network access.

  This used to work with older version of Ubuntu (9.04 if I am not
  mistaken).

  I've been able to use this adapter using hot plug. But when the
  adapter is plugged during boot, there seems to be no way to get a
  connexion.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: linux-image-3.0.0-13-generic-pae 3.0.0-13.22
  ProcVersionSignature: Ubuntu 3.0.0-13.22-generic-pae 3.0.6
  Uname: Linux 3.0.0-13-generic-pae i686
  NonfreeKernelModules: raid10 raid456 async_raid6_recov async_pq raid6_pq 
async_xor xor async_memcpy async_tx raid0 multipath linear raid1 usbhid hid 
forcedeth sata_nv pata_amd
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: aplay: device_list:240: no soundcards found...
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  ArecordDevices: arecord: device_list:240: no soundcards found...
  CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type
  Date: Sun Nov 13 01:02:42 2011
  HibernationDevice: RESUME=UUID=c80d4976-a06e-4865-a8d8-ae43aa14384a
  InstallationMedia: Xubuntu 11.04 Natty Narwhal - Release i386 (20110426.1)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 002: ID 1e54:2030 TypeMatrix 2030 USB Keyboard
   Bus 002 Device 003: ID 046d:c046 Logitech, Inc. RX1000 Laser Mouse
   Bus 001 Device 004: ID 0b95:7720 ASIX Electronics Corp. AX88772
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=fr_FR:fr_CA:fr_CH:en_US:en
   PATH=(custom, user)
   LANG=fr_FR.UTF-8
   LC_MESSAGES=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: root=UUID=c21f66e9-61cc-4cb6-98b6-a72131afb6b1 ro quiet 
splash
  RelatedPackageVersions:
   linux-restricted-modules-3.0.0-13-generic-pae N/A
   linux-backports-modules-3.0.0-13-generic-pae  N/A
   linux-firmware1.60
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to oneiric on 2011-10-15 (28 days ago)
  dmi.bios.date: 02/05/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS M2NPV-VM ACPI BIOS Revision 1301
  dmi.board.name: M2NPV-VM
  dmi.board.vendor: ASUSTek Computer INC.
  dmi.board.version: 1.xx
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2NPV-VMACPIBIOSRevision1301:bd02/05/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTekComputerINC.:rnM2NPV-VM:rvr1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/889664/+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