[Bug 1851881] [NEW] package keystone 2:15.0.0-0ubuntu1.2 failed to install/upgrade: installed keystone package post-installation script subprocess returned error exit status 1
Public bug reported: Upgrading to disco from bionic it failed to install keystone. It is possible that's a configuration problem but it was working nicely on disco... So I have to further investigate... ProblemType: Package DistroRelease: Ubuntu 19.04 Package: keystone 2:15.0.0-0ubuntu1.2 ProcVersionSignature: Ubuntu 4.15.0-66.75-generic 4.15.18 Uname: Linux 4.15.0-66-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.3 Architecture: amd64 Date: Fri Nov 8 22:14:10 2019 DuplicateSignature: package:keystone:2:15.0.0-0ubuntu1.2 Setting up keystone (2:15.0.0-0ubuntu1.2) ... dpkg: error processing package keystone (--configure): installed keystone package post-installation script subprocess returned error exit status 1 ErrorMessage: installed keystone package post-installation script subprocess returned error exit status 1 PackageArchitecture: all Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.6ubuntu1.1 apt 1.8.3 SourcePackage: keystone Title: package keystone 2:15.0.0-0ubuntu1.2 failed to install/upgrade: installed keystone package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to disco on 2019-11-08 (0 days ago) modified.conffile..etc.apache2.sites-available.keystone.conf: [deleted] modified.conffile..etc.keystone.keystone-paste.ini: [modified] modified.conffile..etc.keystone.keystone.conf: [modified] mtime.conffile..etc.keystone.keystone-paste.ini: 2016-04-17T23:22:13.590595 mtime.conffile..etc.keystone.keystone.conf: 2019-10-04T11:50:57.826211 mtime.conffile..etc.keystone.keystone.policy.yaml: 2019-09-18T11:08:09 upstart.keystone.override: manual ** Affects: keystone (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package disco uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851881 Title: package keystone 2:15.0.0-0ubuntu1.2 failed to install/upgrade: installed keystone package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keystone/+bug/1851881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846950] [NEW] package tftpd 0.17-18ubuntu3 failed to install/upgrade: instalado tftpd paquete post-installation guión el subproceso devolvió un error con estado de salida 127
Public bug reported: It failed while upgrading to bionic from xenial. Sorry I don't have much information... ProblemType: Package DistroRelease: Ubuntu 18.04 Package: tftpd 0.17-18ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-159.187-generic 4.4.185 Uname: Linux 4.4.0-159-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Sun Oct 6 15:32:12 2019 ErrorMessage: instalado tftpd paquete post-installation guión el subproceso devolvió un error con estado de salida 127 Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12 SourcePackage: netkit-tftp Title: package tftpd 0.17-18ubuntu3 failed to install/upgrade: instalado tftpd paquete post-installation guión el subproceso devolvió un error con estado de salida 127 UpgradeStatus: Upgraded to bionic on 2019-10-06 (0 days ago) ** Affects: netkit-tftp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846950 Title: package tftpd 0.17-18ubuntu3 failed to install/upgrade: instalado tftpd paquete post-installation guión el subproceso devolvió un error con estado de salida 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netkit-tftp/+bug/1846950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790387] [NEW] package xserver-xorg-video-radeon (not installed) failed to install/upgrade: intentando sobreescribir `/usr/share/X11/xorg.conf.d/10-radeon.conf', que está también en el paquete xs
Public bug reported: With Ubuntu 4.15.0-XX-generic I cannot boot the GPU. I can trick the card but when I boot it I think I can only get mesa support. And only 1 of 2 monitors available. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: xserver-xorg-video-radeon (not installed) ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Aug 27 12:42:30 2018 DistUpgraded: 2018-05-25 16:33:13,549 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: anbox, 1, 4.15.0-32-generic, x86_64: installedError! Could not locate dkms.conf file. File: does not exist. anbox, 1, 4.15.0-33-generic, x86_64: installed DpkgLog: ErrorMessage: intentando sobreescribir `/usr/share/X11/xorg.conf.d/10-radeon.conf', que está también en el paquete xserver-xorg-video-ati 1:18.0.99+git1808041657.740f085~b~padoka0 GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn XT [Radeon HD 7870 GHz Edition] [1002:6818] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Pitcairn XT [Radeon HD 7870 GHz Edition] [1043:0432] MachineType: Hewlett-Packard HP Z800 Workstation ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic root=UUID=892181ef-9502-4f64-9219-6e11543fc8a8 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 Renderer: Software SourcePackage: xserver-xorg-video-ati Title: package xserver-xorg-video-radeon (not installed) failed to install/upgrade: intentando sobreescribir `/usr/share/X11/xorg.conf.d/10-radeon.conf', que está también en el paquete xserver-xorg-video-ati 1:18.0.99+git1808041657.740f085~b~padoka0 UpgradeStatus: Upgraded to bionic on 2018-05-25 (100 days ago) dmi.bios.date: 03/05/2018 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786G5 v03.61 dmi.board.asset.tag: CZC2460MMG dmi.board.name: 0AECh dmi.board.vendor: Hewlett-Packard dmi.board.version: D dmi.chassis.asset.tag: CZC2460MMG dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786G5v03.61:bd03/05/2018:svnHewlett-Packard:pnHPZ800Workstation:pvr:rvnHewlett-Packard:rn0AECh:rvrD:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53335X dmi.product.name: HP Z800 Workstation dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.7-0~b~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.7-0~b~padoka0 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15+git1803090733.ac8f7b~oibaf~a ** Affects: xserver-xorg-video-ati (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790387 Title: package xserver-xorg-video-radeon (not installed) failed to install/upgrade: intentando sobreescribir `/usr/share/X11/xorg.conf.d/10-radeon.conf', que está también en el paquete xserver-xorg-video-ati 1:18.0.99+git1808041657.740f085~b~padoka0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1790387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1714989] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64() [Global App Menu specific?]
Hi Marco, Good. I will give it a try. But since the whole screen get freezed I don't know if I will able catch anything. Best regards, On 21/11/17 17:08, Marco Trevisan (Treviño) wrote: > GadLinux, not so hard now... We've added tools in gnome-shell to show > this in the journal. > > Or just follow this https://is.gd/wiki_gnome_shell_crash_debug to see > what's crashing. > > Anyway, the fix for the issue of GS is in gnome, will be released in > next point release. > > ** Summary changed: > > - gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from > st_label_set_text() from ffi_call_unix64() [Global App Menu specific?] > + gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from > st_label_set_text() from ffi_call_unix64() > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714989 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1714989/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1714989] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64() [Global App Menu specific?]
Hi, Yes, but's quite difficult for normal user know what's the plugin that's behaving wrong. Best regards, On 17/11/17 22:40, Marco Trevisan (Treviño) wrote: > Thanks for all these reports... > > Unfortunately all these issues are unrelated to the shell itself, but I > please you guys to report these crashes to the extensions authors (as I > already did in various cases, proposing fixes too). > > In fact, what I suspect might have changed is the way gjs (or new mozjs) > handles the destruction of the actors (as js elements)... Or the shell > itself might destroy the extension actors at its request. > > When this happens, the extensions should block all the async operations > that are happening, so as a generic rule I guess they should connect to > the extension actor "destroy" signal and stop all the async operations > there. > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714989 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64() [Global App Menu specific?] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1714989/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1637774] Re: gqrx-sdr crashes on startup
Affects me also... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1637774 Title: gqrx-sdr crashes on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gqrx-sdr/+bug/1637774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1400470] Re: cannot download photos using shotwell via usb
The situation got worse with 17.04 ubuntu. The unmount trick doesn't work anymore and the camera/phone is left in strange status. I get "Can't lock camera. Unspecified error (-1)" If I unmount. I had to kill the gvfs process to be able access. After killing /usr/lib/gvfs/gvfsd-mtp I got it working. but that's not the solution. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1400470 Title: cannot download photos using shotwell via usb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1400470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1501240] Re: Serialport doens't work correctly after ubuntu update?
*** This bug is a duplicate of bug 1501345 *** https://bugs.launchpad.net/bugs/1501345 Here they say it's fixed in 3.13.0-66 https://github.com/pyserial/pyserial/issues/17 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1501240 Title: Serialport doens't work correctly after ubuntu update? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1501240/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1329719] Re: cloud-init does not bring up all bridge interfaces created with openvswitch
It seems it's related to this but also: https://bugs.launchpad.net/cloud-init/+bug/1345433 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1329719 Title: cloud-init does not bring up all bridge interfaces created with openvswitch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1329719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1329719] Re: cloud-init does not bring up all bridge interfaces created with openvswitch
It seems it's related to this but also: https://bugs.launchpad.net/cloud-init/+bug/1345433 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1329719 Title: cloud-init does not bring up all bridge interfaces created with openvswitch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1329719/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1336555] Re: [SRU] ovs-vswitchd crashed with SIGSEGV in nl_attr_get_size()
What's version with patch applied. I want to test. Latest? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1336555 Title: [SRU] ovs-vswitchd crashed with SIGSEGV in nl_attr_get_size() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1336555/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1336555] Re: [SRU] ovs-vswitchd crashed with SIGSEGV in nl_attr_get_size()
What's version with patch applied. I want to test. Latest? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1336555 Title: [SRU] ovs-vswitchd crashed with SIGSEGV in nl_attr_get_size() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1336555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1336555] Re: ovs-vswitchd crashed with SIGSEGV in nl_attr_get_size()
Yes I use openvswitch for everything. I tried to mix br-utils with openvswitch and gave me no goood results. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1336555 Title: ovs-vswitchd crashed with SIGSEGV in nl_attr_get_size() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1336555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1336555] Re: ovs-vswitchd crashed with SIGSEGV in nl_attr_get_size()
Yes I use openvswitch for everything. I tried to mix br-utils with openvswitch and gave me no goood results. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1336555 Title: ovs-vswitchd crashed with SIGSEGV in nl_attr_get_size() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1336555/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1336555] Re: ovs-vswitchd segfault every 2 days
I'm still seeing the problem with new kernels. It breaks my ceph installation badly. [1368555.197934] [ cut here ] [1368555.197945] WARNING: CPU: 3 PID: 4400 at /build/buildd/linux-3.13.0/fs/proc/generic.c:511 remove_proc_entry+0x139/0x1b0() [1368555.197947] name 'fs/nfsfs' [1368555.197949] Modules linked in: gspca_ov534 nls_iso8859_1 usb_storage xt_TCPMSS xt_tcpmss arc4 ppp_mppe ppp_async crc_ccitt vhost_net vhost macvtap macvlan nf_conntrack_ipv6 nf_defrag_ipv6 xt_mac xt_physdev xt_multiport pci_stub vboxpci(OX) vboxnetadp(OX) vboxnetflt(OX) vboxdrv(OX) xt_conntrack ipt_REJECT veth ip6table_filter ip6_tables ebtable_nat ebtables xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables nbd ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi rfcomm rbd libceph openvswitch gre vxlan ip_tunnel binfmt_misc nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache dm_crypt xfs snd_usb_audio snd_usbmidi_lib fglrx(POX) kvm_amd kvm gspca_main videodev wacom serio_raw dm_multipath scsi_dh joydev edac_core edac_mce_amd k10temp snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel btusb snd_hda _codec snd_hwdep snd_pcm bluetooth snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer snd soundcore sp5100_tco amd_iommu_v2 i2c_piix4 asus_atk0110 mac_hid parport_pc ppdev lp parport btrfs libcrc32c raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear dm_mirror dm_region_hash dm_log hid_generic hid_logitech_dj usbhid hid pata_acpi psmouse pata_atiixp ahci e1000e pata_marvell libahci firewire_ohci ptp firewire_core pps_core r8169 crc_itu_t mii floppy wmi [last unloaded: gspca_ov534] [1368555.198044] CPU: 3 PID: 4400 Comm: kworker/u12:1 Tainted: PW OX 3.13.0-37-generic #64-Ubuntu [1368555.198046] Hardware name: System manufacturer System Product Name/M4A79T Deluxe, BIOS 350305/06/2011 [1368555.198051] Workqueue: netns cleanup_net [1368555.198053] 0009 880119017c80 8171ed09 880119017cc8 [1368555.198057] 880119017cb8 8106773d 0005 [1368555.198060] a06e48a8 880323019ab0 0180 880119017d18 [1368555.198063] Call Trace: [1368555.198070] [8171ed09] dump_stack+0x45/0x56 [1368555.198074] [8106773d] warn_slowpath_common+0x7d/0xa0 [1368555.198079] [810677ac] warn_slowpath_fmt+0x4c/0x50 [1368555.198084] [81229839] remove_proc_entry+0x139/0x1b0 [1368555.198103] [a06c44e2] nfs_fs_proc_net_exit+0x62/0x70 [nfs] [1368555.198115] [a06ca5b2] nfs_net_exit+0x12/0x20 [nfs] [1368555.198118] [8161b409] ops_exit_list.isra.1+0x39/0x60 [1368555.198122] [8161bc90] cleanup_net+0x110/0x250 [1368555.198126] [810839c2] process_one_work+0x182/0x450 [1368555.198130] [810847b1] worker_thread+0x121/0x410 [1368555.198133] [81084690] ? rescuer_thread+0x430/0x430 [1368555.198137] [8108b492] kthread+0xd2/0xf0 [1368555.198140] [8108b3c0] ? kthread_create_on_node+0x1c0/0x1c0 [1368555.198143] [8172f77c] ret_from_fork+0x7c/0xb0 [1368555.198146] [8108b3c0] ? kthread_create_on_node+0x1c0/0x1c0 [1368555.198148] ---[ end trace 007872efa0f6c8f7 ]--- [1372797.021226] libceph: osd0 172.16.0.119:6800 socket closed (con state OPEN) [1373904.941772] libceph: osd2 172.16.0.119:6805 socket closed (con state OPEN) [1374022.647670] [ cut here ] [1374022.647691] WARNING: CPU: 1 PID: 17323 at /build/buildd/linux-3.13.0/fs/proc/generic.c:511 remove_proc_entry+0x139/0x1b0() [1374022.647696] name 'fs/nfsfs' [1374022.647700] Modules linked in: gspca_ov534 nls_iso8859_1 usb_storage xt_TCPMSS xt_tcpmss arc4 ppp_mppe ppp_async crc_ccitt vhost_net vhost macvtap macvlan nf_conntrack_ipv6 nf_defrag_ipv6 xt_mac xt_physdev xt_multiport pci_stub vboxpci(OX) vboxnetadp(OX) vboxnetflt(OX) vboxdrv(OX) xt_conntrack ipt_REJECT veth ip6table_filter ip6_tables ebtable_nat ebtables xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables nbd ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi rfcomm rbd libceph openvswitch gre vxlan ip_tunnel binfmt_misc nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache dm_crypt xfs snd_usb_audio snd_usbmidi_lib fglrx(POX) kvm_amd kvm gspca_main videodev wacom serio_raw dm_multipath scsi_dh joydev edac_core edac_mce_amd k10temp snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel btusb snd_hda _codec snd_hwdep snd_pcm bluetooth snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi
[Bug 1336555] Re: ovs-vswitchd segfault every 2 days
I'm still seeing the problem with new kernels. It breaks my ceph installation badly. [1368555.197934] [ cut here ] [1368555.197945] WARNING: CPU: 3 PID: 4400 at /build/buildd/linux-3.13.0/fs/proc/generic.c:511 remove_proc_entry+0x139/0x1b0() [1368555.197947] name 'fs/nfsfs' [1368555.197949] Modules linked in: gspca_ov534 nls_iso8859_1 usb_storage xt_TCPMSS xt_tcpmss arc4 ppp_mppe ppp_async crc_ccitt vhost_net vhost macvtap macvlan nf_conntrack_ipv6 nf_defrag_ipv6 xt_mac xt_physdev xt_multiport pci_stub vboxpci(OX) vboxnetadp(OX) vboxnetflt(OX) vboxdrv(OX) xt_conntrack ipt_REJECT veth ip6table_filter ip6_tables ebtable_nat ebtables xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables nbd ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi rfcomm rbd libceph openvswitch gre vxlan ip_tunnel binfmt_misc nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache dm_crypt xfs snd_usb_audio snd_usbmidi_lib fglrx(POX) kvm_amd kvm gspca_main videodev wacom serio_raw dm_multipath scsi_dh joydev edac_core edac_mce_amd k10temp snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel btusb snd_hda _codec snd_hwdep snd_pcm bluetooth snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer snd soundcore sp5100_tco amd_iommu_v2 i2c_piix4 asus_atk0110 mac_hid parport_pc ppdev lp parport btrfs libcrc32c raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear dm_mirror dm_region_hash dm_log hid_generic hid_logitech_dj usbhid hid pata_acpi psmouse pata_atiixp ahci e1000e pata_marvell libahci firewire_ohci ptp firewire_core pps_core r8169 crc_itu_t mii floppy wmi [last unloaded: gspca_ov534] [1368555.198044] CPU: 3 PID: 4400 Comm: kworker/u12:1 Tainted: PW OX 3.13.0-37-generic #64-Ubuntu [1368555.198046] Hardware name: System manufacturer System Product Name/M4A79T Deluxe, BIOS 350305/06/2011 [1368555.198051] Workqueue: netns cleanup_net [1368555.198053] 0009 880119017c80 8171ed09 880119017cc8 [1368555.198057] 880119017cb8 8106773d 0005 [1368555.198060] a06e48a8 880323019ab0 0180 880119017d18 [1368555.198063] Call Trace: [1368555.198070] [8171ed09] dump_stack+0x45/0x56 [1368555.198074] [8106773d] warn_slowpath_common+0x7d/0xa0 [1368555.198079] [810677ac] warn_slowpath_fmt+0x4c/0x50 [1368555.198084] [81229839] remove_proc_entry+0x139/0x1b0 [1368555.198103] [a06c44e2] nfs_fs_proc_net_exit+0x62/0x70 [nfs] [1368555.198115] [a06ca5b2] nfs_net_exit+0x12/0x20 [nfs] [1368555.198118] [8161b409] ops_exit_list.isra.1+0x39/0x60 [1368555.198122] [8161bc90] cleanup_net+0x110/0x250 [1368555.198126] [810839c2] process_one_work+0x182/0x450 [1368555.198130] [810847b1] worker_thread+0x121/0x410 [1368555.198133] [81084690] ? rescuer_thread+0x430/0x430 [1368555.198137] [8108b492] kthread+0xd2/0xf0 [1368555.198140] [8108b3c0] ? kthread_create_on_node+0x1c0/0x1c0 [1368555.198143] [8172f77c] ret_from_fork+0x7c/0xb0 [1368555.198146] [8108b3c0] ? kthread_create_on_node+0x1c0/0x1c0 [1368555.198148] ---[ end trace 007872efa0f6c8f7 ]--- [1372797.021226] libceph: osd0 172.16.0.119:6800 socket closed (con state OPEN) [1373904.941772] libceph: osd2 172.16.0.119:6805 socket closed (con state OPEN) [1374022.647670] [ cut here ] [1374022.647691] WARNING: CPU: 1 PID: 17323 at /build/buildd/linux-3.13.0/fs/proc/generic.c:511 remove_proc_entry+0x139/0x1b0() [1374022.647696] name 'fs/nfsfs' [1374022.647700] Modules linked in: gspca_ov534 nls_iso8859_1 usb_storage xt_TCPMSS xt_tcpmss arc4 ppp_mppe ppp_async crc_ccitt vhost_net vhost macvtap macvlan nf_conntrack_ipv6 nf_defrag_ipv6 xt_mac xt_physdev xt_multiport pci_stub vboxpci(OX) vboxnetadp(OX) vboxnetflt(OX) vboxdrv(OX) xt_conntrack ipt_REJECT veth ip6table_filter ip6_tables ebtable_nat ebtables xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables nbd ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi rfcomm rbd libceph openvswitch gre vxlan ip_tunnel binfmt_misc nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache dm_crypt xfs snd_usb_audio snd_usbmidi_lib fglrx(POX) kvm_amd kvm gspca_main videodev wacom serio_raw dm_multipath scsi_dh joydev edac_core edac_mce_amd k10temp snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel btusb snd_hda _codec snd_hwdep snd_pcm bluetooth snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi
[Bug 1376245] Re: remove_proc_entry+0x139/0x1b0() -- name 'fs/nfsfs'
You can see several kernel panics here. Lots of them until massive down and hangs. ** Attachment added: Kernel Panic and crash. Massive down. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1376245/+attachment/4238894/+files/kernelpanic.dmesg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1376245 Title: remove_proc_entry+0x139/0x1b0() -- name 'fs/nfsfs' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1376245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1376245] Re: remove_proc_entry+0x139/0x1b0() -- name 'fs/nfsfs'
I must add that I'm using kvm-qemu for virtualization. Maybe this also triggers the bug. Just in case you need to know. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1376245 Title: remove_proc_entry+0x139/0x1b0() -- name 'fs/nfsfs' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1376245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1376245] Re: remove_proc_entry+0x139/0x1b0() -- name 'fs/nfsfs'
Hi, for me happening in Linux red-compute 3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:28:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux. It seems this has something related to openvswitch that seems to trigger the error more often. But every bootup I have this on my log: [ 437.773703] ip6_tables: (C) 2000-2006 Netfilter Core Team [ 458.240318] [ cut here ] [ 458.240326] WARNING: CPU: 0 PID: 157 at /build/buildd/linux-3.13.0/fs/proc/generic.c:522 remove_proc_entry+0x19f/0x1b0() [ 458.240328] remove_proc_entry: removing non-empty directory 'fs/nfsfs', leaking at least 'volumes' [ 458.240330] Modules linked in: ip6table_filter ip6_tables ebtable_nat ebtables veth xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables nbd ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi rfcomm rbd libceph nfsd auth_rpcgss openvswitch gre vxlan ip_tunnel binfmt_misc nfs_acl nfs lockd sunrpc fscache dm_crypt xfs snd_usb_audio snd_usbmidi_lib fglrx(POX) gspca_ov534 gspca_main videodev wacom joydev kvm_amd kvm dm_multipath scsi_dh serio_raw edac_core edac_mce_amd k10temp snd_hda_codec_hdmi btusb snd_hda_codec_realtek bluetooth snd_hda_intel snd_hda_codec snd_seq_midi snd_seq_midi_event snd_hwdep snd_pcm snd_rawmidi snd_seq snd_page_alloc snd_seq_device snd_timer snd soundcore sp5100_tco i2c_piix4 amd_iommu_v2 asus_atk0110 mac_hid parport_pc ppdev lp parport btrfs libcrc32c raid10 raid456 async_raid 6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear dm_mirror dm_region_hash dm_log hid_generic hid_logitech_dj usbhid hid pata_acpi psmouse pata_atiixp pata_marvell e1000e firewire_ohci ahci libahci firewire_core ptp floppy pps_core crc_itu_t r8169 mii wmi [ 458.240393] CPU: 0 PID: 157 Comm: kworker/u12:8 Tainted: P OX 3.13.0-37-generic #64-Ubuntu [ 458.240395] Hardware name: System manufacturer System Product Name/M4A79T Deluxe, BIOS 350305/06/2011 [ 458.240398] Workqueue: netns cleanup_net [ 458.240400] 0009 88031964bc80 8171ed09 88031964bcc8 [ 458.240403] 88031964bcb8 8106773d 88031d22cc80 0005 [ 458.240405] a0ffb8a8 8800cfb60130 88031d22ccf5 88031964bd18 [ 458.240408] Call Trace: [ 458.240412] [8171ed09] dump_stack+0x45/0x56 [ 458.240415] [8106773d] warn_slowpath_common+0x7d/0xa0 [ 458.240419] [810677ac] warn_slowpath_fmt+0x4c/0x50 [ 458.240421] [8122989f] remove_proc_entry+0x19f/0x1b0 [ 458.240434] [a0fdb4e2] nfs_fs_proc_net_exit+0x62/0x70 [nfs] [ 458.240443] [a0fe15b2] nfs_net_exit+0x12/0x20 [nfs] [ 458.240445] [8161b409] ops_exit_list.isra.1+0x39/0x60 [ 458.240447] [8161bc90] cleanup_net+0x110/0x250 [ 458.240450] [810839c2] process_one_work+0x182/0x450 [ 458.240453] [810847b1] worker_thread+0x121/0x410 [ 458.240455] [81084690] ? rescuer_thread+0x430/0x430 [ 458.240458] [8108b492] kthread+0xd2/0xf0 [ 458.240460] [8108b3c0] ? kthread_create_on_node+0x1c0/0x1c0 [ 458.240462] [8172f77c] ret_from_fork+0x7c/0xb0 [ 458.240465] [8108b3c0] ? kthread_create_on_node+0x1c0/0x1c0 [ 458.240466] ---[ end trace deb7a3367698c9e6 ]--- [ 458.750935] IPv6: ADDRCONF(NETDEV_UP): virbr0: link is not ready [ 463.179724] init: plymouth-upstart-bridge main process ended, respawning I will attach also logs of several kernel panics that I think may be related. Older kernel of the same series used to have this problem less often. I mean 3.13.0-2X? Don't remember. Anyway this bug should be marked as critical since it affects normal ops. And can cause dataloss and network downs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1376245 Title: remove_proc_entry+0x139/0x1b0() -- name 'fs/nfsfs' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1376245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1336555] Re: ovs-vswitchd segfault every 2 days
After updating kernel in ubuntu 14.04 I found this again. But this time with kernel panic. ct 12 00:56:30 red-compute kernel: [ 2139.850867] ovs-vswitchd[19280]: segfault at 0 ip 00459340 sp 7fff2d88c3e8 error 4 in ovs-vswitchd[40+133000] Oct 12 00:56:31 red-compute ovs-vswitchd: ovs|00010|daemon(monitor)|ERR|7 crashes: pid 19280 died, killed (Segmentation fault), core dumped, restarting Oct 12 00:57:01 red-compute CRON[19736]: (root) CMD (if [ -x /usr/share/mdadm/checkarray ] [ $(date +%d) -le 7 ]; then /usr/share/mdadm/checkarray --cron --all --idle --quiet; fi) Oct 12 00:58:28 red-compute ovsdb-client: ovs|1|fatal_signal|WARN|terminating with signal 15 (Terminated) Oct 12 00:58:34 red-compute kernel: [ 2264.419340] init: neutron-plugin-openvswitch-agent main process (14411) killed by KILL signal Oct 12 00:58:56 red-compute kernel: [ 2286.159789] INFO: task jbd2/rbd1-8:10184 blocked for more than 120 seconds. Oct 12 00:58:56 red-compute kernel: [ 2286.159802] Tainted: PW OX 3.13.0-37-generic #64-Ubuntu Oct 12 00:58:56 red-compute kernel: [ 2286.159807] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. Oct 12 00:58:56 red-compute kernel: [ 2286.159812] jbd2/rbd1-8 D 88032fc54480 0 10184 2 0x Oct 12 00:58:56 red-compute kernel: [ 2286.159822] 88029baadbc8 0046 8802d1ac8000 88029baadfd8 Oct 12 00:58:56 red-compute kernel: [ 2286.159832] 00014480 00014480 8802d1ac8000 88032fc54d18 Oct 12 00:58:56 red-compute kernel: [ 2286.159840] 88032ffb1020 0002 811ee820 88029baadc40 Oct 12 00:58:56 red-compute kernel: [ 2286.159847] Call Trace: Oct 12 00:58:56 red-compute kernel: [ 2286.159864] [811ee820] ? generic_block_bmap+0x50/0x50 Oct 12 00:58:56 red-compute kernel: [ 2286.159875] [8172344d] io_schedule+0x9d/0x140 Oct 12 00:58:56 red-compute kernel: [ 2286.159884] [811ee82e] sleep_on_buffer+0xe/0x20 Oct 12 00:58:56 red-compute kernel: [ 2286.159892] [817238d2] __wait_on_bit+0x62/0x90 Oct 12 00:58:56 red-compute kernel: [ 2286.159899] [811ee820] ? generic_block_bmap+0x50/0x50 Oct 12 00:58:56 red-compute kernel: [ 2286.159907] [81723977] out_of_line_wait_on_bit+0x77/0x90 Oct 12 00:58:56 red-compute kernel: [ 2286.159916] [810ab010] ? autoremove_wake_function+0x40/0x40 Oct 12 00:58:56 red-compute kernel: [ 2286.159924] [811efb5a] __wait_on_buffer+0x2a/0x30 Oct 12 00:58:56 red-compute kernel: [ 2286.159933] [812888f0] jbd2_journal_commit_transaction+0xee0/0x1a70 Oct 12 00:58:56 red-compute kernel: [ 2286.159943] [810754ff] ? try_to_del_timer_sync+0x4f/0x70 Oct 12 00:58:56 red-compute kernel: [ 2286.159951] [8128d4ad] kjournald2+0xbd/0x250 Oct 12 00:58:56 red-compute kernel: [ 2286.159959] [810aafd0] ? prepare_to_wait_event+0x100/0x100 Oct 12 00:58:56 red-compute kernel: [ 2286.159967] [8128d3f0] ? commit_timeout+0x10/0x10 Oct 12 00:58:56 red-compute kernel: [ 2286.159974] [8108b492] kthread+0xd2/0xf0 Oct 12 00:58:56 red-compute kernel: [ 2286.159981] [8108b3c0] ? kthread_create_on_node+0x1c0/0x1c0 Oct 12 00:58:56 red-compute kernel: [ 2286.159988] [8172f77c] ret_from_fork+0x7c/0xb0 Oct 12 00:58:56 red-compute kernel: [ 2286.159995] [8108b3c0] ? kthread_create_on_node+0x1c0/0x1c0 Oct 12 00:58:56 red-compute kernel: [ 2286.160016] INFO: task init:10493 blocked for more than 120 seconds. Oct 12 00:58:56 red-compute kernel: [ 2286.160022] Tainted: PW OX 3.13.0-37-generic #64-Ubuntu Oct 12 00:58:56 red-compute kernel: [ 2286.160025] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. Oct 12 00:58:56 red-compute kernel: [ 2286.160028] initD 88032fc94480 0 10493 10443 0x Oct 12 00:58:56 red-compute kernel: [ 2286.160036] 8802eae2da28 0082 8802b37a3000 8802eae2dfd8 Oct 12 00:58:56 red-compute kernel: [ 2286.160043] 00014480 00014480 8802b37a3000 88032fc94d18 Oct 12 00:58:56 red-compute kernel: [ 2286.160050] 88032ffb7908 0002 812851c0 8802eae2daa0 Oct 12 00:58:56 red-compute kernel: [ 2286.160057] Call Trace: Oct 12 00:58:56 red-compute kernel: [ 2286.160066] [812851c0] ? start_this_handle+0x590/0x590 Oct 12 00:58:56 red-compute kernel: [ 2286.160074] [8172344d] io_schedule+0x9d/0x140 Oct 12 00:58:56 red-compute kernel: [ 2286.160081] [812851ce] sleep_on_shadow_bh+0xe/0x20 Oct 12 00:58:56 red-compute kernel: [ 2286.160088] [817238d2] __wait_on_bit+0x62/0x90 Oct 12 00:58:56 red-compute kernel: [ 2286.160095] [812851c0] ? start_this_handle+0x590/0x590 Oct 12 00:58:56 red-compute kernel: [ 2286.160103] [81723977] out_of_line_wait_on_bit+0x77/0x90 Oct 12 00:58:56 red-compute kernel: [
[Bug 1336555] Re: ovs-vswitchd segfault every 2 days
ovs-vsctl (Open vSwitch) 2.0.2 Compiled Aug 15 2014 14:31:02 I did: apport-collect 1336555 Package openvswitch not installed and no hook available, ignoring But no luck. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1336555 Title: ovs-vswitchd segfault every 2 days To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1336555/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1336555] Re: ovs-vswitchd segfault every 2 days
After updating kernel in ubuntu 14.04 I found this again. But this time with kernel panic. ct 12 00:56:30 red-compute kernel: [ 2139.850867] ovs-vswitchd[19280]: segfault at 0 ip 00459340 sp 7fff2d88c3e8 error 4 in ovs-vswitchd[40+133000] Oct 12 00:56:31 red-compute ovs-vswitchd: ovs|00010|daemon(monitor)|ERR|7 crashes: pid 19280 died, killed (Segmentation fault), core dumped, restarting Oct 12 00:57:01 red-compute CRON[19736]: (root) CMD (if [ -x /usr/share/mdadm/checkarray ] [ $(date +%d) -le 7 ]; then /usr/share/mdadm/checkarray --cron --all --idle --quiet; fi) Oct 12 00:58:28 red-compute ovsdb-client: ovs|1|fatal_signal|WARN|terminating with signal 15 (Terminated) Oct 12 00:58:34 red-compute kernel: [ 2264.419340] init: neutron-plugin-openvswitch-agent main process (14411) killed by KILL signal Oct 12 00:58:56 red-compute kernel: [ 2286.159789] INFO: task jbd2/rbd1-8:10184 blocked for more than 120 seconds. Oct 12 00:58:56 red-compute kernel: [ 2286.159802] Tainted: PW OX 3.13.0-37-generic #64-Ubuntu Oct 12 00:58:56 red-compute kernel: [ 2286.159807] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. Oct 12 00:58:56 red-compute kernel: [ 2286.159812] jbd2/rbd1-8 D 88032fc54480 0 10184 2 0x Oct 12 00:58:56 red-compute kernel: [ 2286.159822] 88029baadbc8 0046 8802d1ac8000 88029baadfd8 Oct 12 00:58:56 red-compute kernel: [ 2286.159832] 00014480 00014480 8802d1ac8000 88032fc54d18 Oct 12 00:58:56 red-compute kernel: [ 2286.159840] 88032ffb1020 0002 811ee820 88029baadc40 Oct 12 00:58:56 red-compute kernel: [ 2286.159847] Call Trace: Oct 12 00:58:56 red-compute kernel: [ 2286.159864] [811ee820] ? generic_block_bmap+0x50/0x50 Oct 12 00:58:56 red-compute kernel: [ 2286.159875] [8172344d] io_schedule+0x9d/0x140 Oct 12 00:58:56 red-compute kernel: [ 2286.159884] [811ee82e] sleep_on_buffer+0xe/0x20 Oct 12 00:58:56 red-compute kernel: [ 2286.159892] [817238d2] __wait_on_bit+0x62/0x90 Oct 12 00:58:56 red-compute kernel: [ 2286.159899] [811ee820] ? generic_block_bmap+0x50/0x50 Oct 12 00:58:56 red-compute kernel: [ 2286.159907] [81723977] out_of_line_wait_on_bit+0x77/0x90 Oct 12 00:58:56 red-compute kernel: [ 2286.159916] [810ab010] ? autoremove_wake_function+0x40/0x40 Oct 12 00:58:56 red-compute kernel: [ 2286.159924] [811efb5a] __wait_on_buffer+0x2a/0x30 Oct 12 00:58:56 red-compute kernel: [ 2286.159933] [812888f0] jbd2_journal_commit_transaction+0xee0/0x1a70 Oct 12 00:58:56 red-compute kernel: [ 2286.159943] [810754ff] ? try_to_del_timer_sync+0x4f/0x70 Oct 12 00:58:56 red-compute kernel: [ 2286.159951] [8128d4ad] kjournald2+0xbd/0x250 Oct 12 00:58:56 red-compute kernel: [ 2286.159959] [810aafd0] ? prepare_to_wait_event+0x100/0x100 Oct 12 00:58:56 red-compute kernel: [ 2286.159967] [8128d3f0] ? commit_timeout+0x10/0x10 Oct 12 00:58:56 red-compute kernel: [ 2286.159974] [8108b492] kthread+0xd2/0xf0 Oct 12 00:58:56 red-compute kernel: [ 2286.159981] [8108b3c0] ? kthread_create_on_node+0x1c0/0x1c0 Oct 12 00:58:56 red-compute kernel: [ 2286.159988] [8172f77c] ret_from_fork+0x7c/0xb0 Oct 12 00:58:56 red-compute kernel: [ 2286.159995] [8108b3c0] ? kthread_create_on_node+0x1c0/0x1c0 Oct 12 00:58:56 red-compute kernel: [ 2286.160016] INFO: task init:10493 blocked for more than 120 seconds. Oct 12 00:58:56 red-compute kernel: [ 2286.160022] Tainted: PW OX 3.13.0-37-generic #64-Ubuntu Oct 12 00:58:56 red-compute kernel: [ 2286.160025] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. Oct 12 00:58:56 red-compute kernel: [ 2286.160028] initD 88032fc94480 0 10493 10443 0x Oct 12 00:58:56 red-compute kernel: [ 2286.160036] 8802eae2da28 0082 8802b37a3000 8802eae2dfd8 Oct 12 00:58:56 red-compute kernel: [ 2286.160043] 00014480 00014480 8802b37a3000 88032fc94d18 Oct 12 00:58:56 red-compute kernel: [ 2286.160050] 88032ffb7908 0002 812851c0 8802eae2daa0 Oct 12 00:58:56 red-compute kernel: [ 2286.160057] Call Trace: Oct 12 00:58:56 red-compute kernel: [ 2286.160066] [812851c0] ? start_this_handle+0x590/0x590 Oct 12 00:58:56 red-compute kernel: [ 2286.160074] [8172344d] io_schedule+0x9d/0x140 Oct 12 00:58:56 red-compute kernel: [ 2286.160081] [812851ce] sleep_on_shadow_bh+0xe/0x20 Oct 12 00:58:56 red-compute kernel: [ 2286.160088] [817238d2] __wait_on_bit+0x62/0x90 Oct 12 00:58:56 red-compute kernel: [ 2286.160095] [812851c0] ? start_this_handle+0x590/0x590 Oct 12 00:58:56 red-compute kernel: [ 2286.160103] [81723977] out_of_line_wait_on_bit+0x77/0x90 Oct 12 00:58:56 red-compute kernel: [
[Bug 1336555] Re: ovs-vswitchd segfault every 2 days
ovs-vsctl (Open vSwitch) 2.0.2 Compiled Aug 15 2014 14:31:02 I did: apport-collect 1336555 Package openvswitch not installed and no hook available, ignoring But no luck. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1336555 Title: ovs-vswitchd segfault every 2 days To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1336555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1249358] Re: PS3 Eye showing with lsusb, but not mounted or available now to Cheese, Skype, etc., .
Hi I have exactly the same problem . I discovered that under my USB port multiplier it shows as 1415:2000 and it's recognized: [262724.745858] usb 1-5.3.1: new high-speed USB device number 22 using ehci-pci [262724.845230] usb 1-5.3.1: New USB device found, idVendor=1415, idProduct=2000 [262724.845234] usb 1-5.3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [262724.845236] usb 1-5.3.1: Product: USB Camera-B3.04.06.1 [262724.845238] usb 1-5.3.1: Manufacturer: OmniVision Technologies, Inc. [262724.845442] gspca_main: ov534-2.14.0 probing 1415:2000 And it works. But directly attached to the computer does not 1415:4000, and does not work: 262792.471160] usb 1-5.3: USB disconnect, device number 21 [262792.471165] usb 1-5.3.1: USB disconnect, device number 22 [262819.083096] usb 1-1: new high-speed USB device number 23 using ehci-pci [262819.220451] usb 1-1: New USB device found, idVendor=1415, idProduct=4000 [262819.220456] usb 1-1: New USB device strings: Mfr=10, Product=11, SerialNumber=0 [262819.220458] usb 1-1: Product: USB 2.0 HUB [262819.220460] usb 1-1: Manufacturer: SONY [262819.220856] hub 1-1:1.0: USB hub found [262819.221520] hub 1-1:1.0: 1 port detected How can this be? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1249358 Title: PS3 Eye showing with lsusb, but not mounted or available now to Cheese, Skype, etc.,. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gspca/+bug/1249358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1359815] Re: virt-manager crashed with SIGSEGV in _pygi_argument_from_object()
Confirming, here with 14.10 utopic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1359815 Title: virt-manager crashed with SIGSEGV in _pygi_argument_from_object() To manage notifications about this bug go to: https://bugs.launchpad.net/virt-manager/+bug/1359815/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1283218] Re: fail to start
This also happens to me. Do it requires EHCache? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1283218 Title: fail to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/red5/+bug/1283218/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1283218] Re: fail to start
I installed by hand ehcache-2.7.2.jar to red5/lib and it worked. Now I have another problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1283218 Title: fail to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/red5/+bug/1283218/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1336555] Re: ovs-vswitchd segfault every 2 days
Hi Nooope, I had to restart the computer and I think I don't have it. It didn't hapened for a while. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1336555 Title: ovs-vswitchd segfault every 2 days To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1336555/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1336555] Re: ovs-vswitchd segfault every 2 days
Hi Nooope, I had to restart the computer and I think I don't have it. It didn't hapened for a while. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1336555 Title: ovs-vswitchd segfault every 2 days To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1336555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1329719] Re: cloud-init does not bring up all bridge interfaces created with openvswitch
This is a problem when installing metal with mass. This is related to this https://bugs.launchpad.net/juju-core/+bug/1271144 but not resolved. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1329719 Title: cloud-init does not bring up all bridge interfaces created with openvswitch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1329719/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1329719] Re: cloud-init does not bring up all bridge interfaces created with openvswitch
This is a problem when installing metal with mass. This is related to this https://bugs.launchpad.net/juju-core/+bug/1271144 but not resolved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1329719 Title: cloud-init does not bring up all bridge interfaces created with openvswitch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1329719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1336555] Re: ovs-vswitchd segfault every 2 days
Hi, Is there a way I can get a core from this process? I suppose that leaving ulimit -c unlimited is not enough. And I don't know where it will be left. But I can try. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1336555 Title: ovs-vswitchd segfault every 2 days To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1336555/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1336555] Re: ovs-vswitchd segfault every 2 days
To make it happen more ofter, is needed a lot of transfer connections through the network node. I have GB eth with two interfaces on each host to make it happen. But only 4-5 vmachines on the cloud. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1336555 Title: ovs-vswitchd segfault every 2 days To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1336555/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1336555] Re: ovs-vswitchd segfault every 2 days
Hi, Is there a way I can get a core from this process? I suppose that leaving ulimit -c unlimited is not enough. And I don't know where it will be left. But I can try. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1336555 Title: ovs-vswitchd segfault every 2 days To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1336555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1336555] Re: ovs-vswitchd segfault every 2 days
To make it happen more ofter, is needed a lot of transfer connections through the network node. I have GB eth with two interfaces on each host to make it happen. But only 4-5 vmachines on the cloud. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1336555 Title: ovs-vswitchd segfault every 2 days To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1336555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1336555] [NEW] ovs-vswitchd segfault every 2 days
Public bug reported: Hi I find that every 2 days or so I loose part of my cluster. It seems that openvswitch is crashing... The only message left on syslog is as follows: syslog:Jul 1 22:52:32 blue-compute kernel: [530482.190688] ovs- vswitchd[1935]: segfault at 0 ip 00459110 sp 7fff85804758 error 4 in ovs-vswitchd[40+133000] And this is the last message. I'm unable to reboot gracefully. I have to reset. (This can be because ceph not giving up also). And I can see a lot of traffic going around in the network. There so much traffic that some lowend routers/switches fail. Can be because another problem (machines stalled because the ovs fault and others trying to connect. Maybe it fails because much traffic). But I tell this for completeness. Now some info: Linux version 3.13.0-30-generic (buildd@allspice) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #54-Ubu ntu SMP Mon Jun 9 22:45:01 UTC 2014 (Ubuntu 3.13.0-30.54-generic 3.13.11.2) vendor_id : AuthenticAMD cpu family : 16 model : 4 model name : AMD Phenom(tm) II X4 810 Processor Ubuntu 14.04 LTS (server). ovs-vsctl --version ovs-vsctl (Open vSwitch) 2.0.1 Compiled Feb 23 2014 14:42:32 I can attach full logs but I think there's nothing useful because only one line referring the problem. NOTE: restarting ovs does not solve the problem. ** Affects: openvswitch (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1336555 Title: ovs-vswitchd segfault every 2 days To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1336555/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1336555] [NEW] ovs-vswitchd segfault every 2 days
Public bug reported: Hi I find that every 2 days or so I loose part of my cluster. It seems that openvswitch is crashing... The only message left on syslog is as follows: syslog:Jul 1 22:52:32 blue-compute kernel: [530482.190688] ovs- vswitchd[1935]: segfault at 0 ip 00459110 sp 7fff85804758 error 4 in ovs-vswitchd[40+133000] And this is the last message. I'm unable to reboot gracefully. I have to reset. (This can be because ceph not giving up also). And I can see a lot of traffic going around in the network. There so much traffic that some lowend routers/switches fail. Can be because another problem (machines stalled because the ovs fault and others trying to connect. Maybe it fails because much traffic). But I tell this for completeness. Now some info: Linux version 3.13.0-30-generic (buildd@allspice) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #54-Ubu ntu SMP Mon Jun 9 22:45:01 UTC 2014 (Ubuntu 3.13.0-30.54-generic 3.13.11.2) vendor_id : AuthenticAMD cpu family : 16 model : 4 model name : AMD Phenom(tm) II X4 810 Processor Ubuntu 14.04 LTS (server). ovs-vsctl --version ovs-vsctl (Open vSwitch) 2.0.1 Compiled Feb 23 2014 14:42:32 I can attach full logs but I think there's nothing useful because only one line referring the problem. NOTE: restarting ovs does not solve the problem. ** Affects: openvswitch (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1336555 Title: ovs-vswitchd segfault every 2 days To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1336555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1084028] Re: openvswitch based interfaces not started in time during boot
I will open another bug... sorry -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1084028 Title: openvswitch based interfaces not started in time during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1084028/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1084028] Re: openvswitch based interfaces not started in time during boot
root@red-compute:~# ovs-vsctl show 8d08d8e4-49f2-4243-b1db-7641984a8530 Bridge br-ex Port br-ex Interface br-ex type: internal Bridge br-int Port eth1 Interface eth1 Port br-int Interface br-int type: internal ovs_version: 2.0.1 root@red-compute:~# cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet manual up ifconfig $IFACE 0.0.0.0 up up ip link set $IFACE promisc on down ip link set $IFACE promisc off down ifconfig $IFACE down auto eth1 iface eth1 inet manual up ifconfig $IFACE 0.0.0.0 up down ifconfig $IFACE down auto br-int iface br-int inet dhcp And when I boot up, cloudinit does not find the interfaces so no network is up. I have to take an screenshot of the issue. The problem is that rbd storage is not boot up because cloudinit does not find the interfaces to connect to the intranet (because it's a bridge), and all the system becomes a nightmare. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1084028 Title: openvswitch based interfaces not started in time during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1084028/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1329719] [NEW] cloud-init does not bring up all bridge interfaces created with openvswitch
Public bug reported: Hi, In my systems (all of them where I have openstack), I found that cloud- init does not perform well. Mainly because the bridges I have were created with ovs. Since they are not ready at boot time it seems that the system got stalled for a few mins. And after boot not all services recover. For example rbdmap is not called again after the net is up. It may be the order where the things are done. Or maybe something worse. The problem is that cloud-init stalls for 2 mins on boot. RBD doesn't run because cloud-init starts in nonet mode. And the whole system becomes broken. It's curious that ceph-osd are re-run after net is up. So some scripts are relaunched. In fact two times. So they start to work well. But some others no. root@red-compute:~# ovs-vsctl show 8d08d8e4-49f2-4243-b1db-7641984a8530 Bridge br-ex Port br-ex Interface br-ex type: internal Bridge br-int Port eth1 Interface eth1 Port br-int Interface br-int type: internal ovs_version: 2.0.1 root@red-compute:~# cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet manual up ifconfig $IFACE 0.0.0.0 up up ip link set $IFACE promisc on down ip link set $IFACE promisc off down ifconfig $IFACE down auto eth1 iface eth1 inet manual up ifconfig $IFACE 0.0.0.0 up down ifconfig $IFACE down auto br-int iface br-int inet dhcp And when I boot up, cloudinit does not find the interfaces so no network is up. I have to take an screenshot of the issue. The problem is that rbd storage is not boot up because cloudinit does not find the interfaces to connect to the intranet (because it's a bridge), and all the system becomes a nightmare. ** Affects: openvswitch (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1329719 Title: cloud-init does not bring up all bridge interfaces created with openvswitch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1329719/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1084028] Re: openvswitch based interfaces not started in time during boot
I will open another bug... sorry -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1084028 Title: openvswitch based interfaces not started in time during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1084028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1084028] Re: openvswitch based interfaces not started in time during boot
root@red-compute:~# ovs-vsctl show 8d08d8e4-49f2-4243-b1db-7641984a8530 Bridge br-ex Port br-ex Interface br-ex type: internal Bridge br-int Port eth1 Interface eth1 Port br-int Interface br-int type: internal ovs_version: 2.0.1 root@red-compute:~# cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet manual up ifconfig $IFACE 0.0.0.0 up up ip link set $IFACE promisc on down ip link set $IFACE promisc off down ifconfig $IFACE down auto eth1 iface eth1 inet manual up ifconfig $IFACE 0.0.0.0 up down ifconfig $IFACE down auto br-int iface br-int inet dhcp And when I boot up, cloudinit does not find the interfaces so no network is up. I have to take an screenshot of the issue. The problem is that rbd storage is not boot up because cloudinit does not find the interfaces to connect to the intranet (because it's a bridge), and all the system becomes a nightmare. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1084028 Title: openvswitch based interfaces not started in time during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1084028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1329719] [NEW] cloud-init does not bring up all bridge interfaces created with openvswitch
Public bug reported: Hi, In my systems (all of them where I have openstack), I found that cloud- init does not perform well. Mainly because the bridges I have were created with ovs. Since they are not ready at boot time it seems that the system got stalled for a few mins. And after boot not all services recover. For example rbdmap is not called again after the net is up. It may be the order where the things are done. Or maybe something worse. The problem is that cloud-init stalls for 2 mins on boot. RBD doesn't run because cloud-init starts in nonet mode. And the whole system becomes broken. It's curious that ceph-osd are re-run after net is up. So some scripts are relaunched. In fact two times. So they start to work well. But some others no. root@red-compute:~# ovs-vsctl show 8d08d8e4-49f2-4243-b1db-7641984a8530 Bridge br-ex Port br-ex Interface br-ex type: internal Bridge br-int Port eth1 Interface eth1 Port br-int Interface br-int type: internal ovs_version: 2.0.1 root@red-compute:~# cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet manual up ifconfig $IFACE 0.0.0.0 up up ip link set $IFACE promisc on down ip link set $IFACE promisc off down ifconfig $IFACE down auto eth1 iface eth1 inet manual up ifconfig $IFACE 0.0.0.0 up down ifconfig $IFACE down auto br-int iface br-int inet dhcp And when I boot up, cloudinit does not find the interfaces so no network is up. I have to take an screenshot of the issue. The problem is that rbd storage is not boot up because cloudinit does not find the interfaces to connect to the intranet (because it's a bridge), and all the system becomes a nightmare. ** Affects: openvswitch (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1329719 Title: cloud-init does not bring up all bridge interfaces created with openvswitch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1329719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1084028] Re: openvswitch based interfaces not started in time during boot
You should reopen it since it happens in trusty tahr to me. Someone can try it in this version of ubuntu, please? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1084028 Title: openvswitch based interfaces not started in time during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1084028/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1084028] Re: openvswitch based interfaces not started in time during boot
You should reopen it since it happens in trusty tahr to me. Someone can try it in this version of ubuntu, please? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1084028 Title: openvswitch based interfaces not started in time during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1084028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295070] CRDA.txt
apport information ** Attachment added: CRDA.txt https://bugs.launchpad.net/bugs/1295070/+attachment/4033650/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295070 Title: PS3 Camera driver does not work. Micro is not found. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1295070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295070] [NEW] PS3 Camera driver does not work. Micro is not found.
Public bug reported: I cannot make PS3 camera work. The camera is working but microphone is not wokring If I try to set the volume with alsamixer I get alsamixer no se pueden cargar los controles del mezclador: Argumento inválido Cannot load mixer controls: Argument invalid I also cannot set the volume from pulse. I suppose that's an alsa problem. I don't know if this has something to do. But I just post in case of: Mar 19 16:23:46 red1 pulseaudio[4679]: [pulseaudio] alsa-util.c: Unable to load mixer: Argumento inválido Mar 19 16:23:46 red1 kernel: [ 28.633185] cannot get current value for control 2 ch 1: err = -22 This is trusty thar. uname -a Linux red1 3.13.0-18-generic #38-Ubuntu SMP Mon Mar 17 21:40:06 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux I will attach the rest after the bug is created. --- ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0c: gad9023 F...m pulseaudio DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=5b28f9e9-67cf-4b45-ab59-9bfd7e391f28 MachineType: System manufacturer System Product Name NonfreeKernelModules: fglrx Package: linux (not installed) ProcEnviron: LANGUAGE=es_ES:es_SV:en TERM=xterm PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-18-generic root=UUID=225aabc5-9098-412c-9cf1-4b06f8ec4c80 ro quiet splash elevator=deadline nomdmonddf nomdmonisw vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-18-generic N/A linux-backports-modules-3.13.0-18-generic N/A linux-firmware 1.126 RfKill: Tags: trusty Uname: Linux 3.13.0-18-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-02-09 (38 days ago) UserGroups: lp lpadmin _MarkForUpload: True dmi.bios.date: 05/06/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3503 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A79T Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3503:bd05/06/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A79TDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected trusty ** Tags added: apport-collected trusty ** Description changed: I cannot make PS3 camera work. The camera is working but microphone is not wokring If I try to set the volume with alsamixer I get alsamixer no se pueden cargar los controles del mezclador: Argumento inválido Cannot load mixer controls: Argument invalid I also cannot set the volume from pulse. I suppose that's an alsa problem. I don't know if this has something to do. But I just post in case of: Mar 19 16:23:46 red1 pulseaudio[4679]: [pulseaudio] alsa-util.c: Unable to load mixer: Argumento inválido Mar 19 16:23:46 red1 kernel: [ 28.633185] cannot get current value for control 2 ch 1: err = -22 This is trusty thar. uname -a Linux red1 3.13.0-18-generic #38-Ubuntu SMP Mon Mar 17 21:40:06 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux I will attach the rest after the bug is created. + --- + ApportVersion: 2.13.3-0ubuntu1 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/pcmC2D0c: gad9023 F...m pulseaudio + DistroRelease: Ubuntu 14.04 + HibernationDevice: RESUME=UUID=5b28f9e9-67cf-4b45-ab59-9bfd7e391f28 + MachineType: System manufacturer System Product Name + NonfreeKernelModules: fglrx + Package: linux (not installed) + ProcEnviron: + LANGUAGE=es_ES:es_SV:en + TERM=xterm + PATH=(custom, no user) + LANG=es_ES.UTF-8 + SHELL=/bin/bash + ProcFB: + + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-18-generic root=UUID=225aabc5-9098-412c-9cf1-4b06f8ec4c80 ro quiet splash elevator=deadline nomdmonddf nomdmonisw vt.handoff=7 + ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 + PulseList: + Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied + No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-3.13.0-18-generic N/A + linux-backports-modules-3.13.0-18-generic N/A + linux-firmware 1.126 + RfKill: + + Tags: trusty + Uname: Linux
[Bug 1295070] AlsaInfo.txt
apport information ** Attachment added: AlsaInfo.txt https://bugs.launchpad.net/bugs/1295070/+attachment/4033648/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295070 Title: PS3 Camera driver does not work. Micro is not found. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1295070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295070] BootDmesg.txt
apport information ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/1295070/+attachment/4033649/+files/BootDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295070 Title: PS3 Camera driver does not work. Micro is not found. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1295070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295070] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/1295070/+attachment/4033659/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295070 Title: PS3 Camera driver does not work. Micro is not found. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1295070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295070] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/1295070/+attachment/4033657/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295070 Title: PS3 Camera driver does not work. Micro is not found. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1295070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295070] IwConfig.txt
apport information ** Attachment added: IwConfig.txt https://bugs.launchpad.net/bugs/1295070/+attachment/4033652/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295070 Title: PS3 Camera driver does not work. Micro is not found. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1295070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295070] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1295070/+attachment/4033658/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295070 Title: PS3 Camera driver does not work. Micro is not found. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1295070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295070] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/1295070/+attachment/4033654/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295070 Title: PS3 Camera driver does not work. Micro is not found. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1295070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295070] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1295070/+attachment/4033655/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295070 Title: PS3 Camera driver does not work. Micro is not found. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1295070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295070] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/1295070/+attachment/4033653/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295070 Title: PS3 Camera driver does not work. Micro is not found. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1295070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295070] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/1295070/+attachment/4033656/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295070 Title: PS3 Camera driver does not work. Micro is not found. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1295070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295070] WifiSyslog.txt
apport information ** Attachment added: WifiSyslog.txt https://bugs.launchpad.net/bugs/1295070/+attachment/4033660/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295070 Title: PS3 Camera driver does not work. Micro is not found. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1295070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295070] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/1295070/+attachment/4033651/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295070 Title: PS3 Camera driver does not work. Micro is not found. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1295070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295070] Re: PS3 Camera driver does not work. Micro is not found.
What bot? Because it broke my system. I installed updates and now I cannot even have sound... :D -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295070 Title: PS3 Camera driver does not work. Micro is not found. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1295070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1255516] Re: Network access broken to some hosts after some usage...
It seems macvtap driver works better. I had no more problems since I use it instead the normal bridge tools. Someone should take a look to this problem since macvtap has it's own problems, like host is not seeing hosted machine. I had to do the KVM subnet trick to enable a subnet for communications between host and vm. At least network gone no down anyway. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1255516 Title: Network access broken to some hosts after some usage... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netbase/+bug/1255516/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1286039] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/1286039/+attachment/4000588/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1286039 Title: X and possibly kernel crashes on overlay screen fglrx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1286039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1286039] BootLog.txt
apport information ** Attachment added: BootLog.txt https://bugs.launchpad.net/bugs/1286039/+attachment/4000584/+files/BootLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1286039 Title: X and possibly kernel crashes on overlay screen fglrx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1286039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1286039] DpkgLog.txt
apport information ** Attachment added: DpkgLog.txt https://bugs.launchpad.net/bugs/1286039/+attachment/4000586/+files/DpkgLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1286039 Title: X and possibly kernel crashes on overlay screen fglrx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1286039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1286039] GconfCompiz.txt
apport information ** Attachment added: GconfCompiz.txt https://bugs.launchpad.net/bugs/1286039/+attachment/4000587/+files/GconfCompiz.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1286039 Title: X and possibly kernel crashes on overlay screen fglrx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1286039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1286039] MonitorsUser.xml.txt
apport information ** Attachment added: MonitorsUser.xml.txt https://bugs.launchpad.net/bugs/1286039/+attachment/4000590/+files/MonitorsUser.xml.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1286039 Title: X and possibly kernel crashes on overlay screen fglrx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1286039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1286039] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/1286039/+attachment/4000585/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1286039 Title: X and possibly kernel crashes on overlay screen fglrx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1286039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1286039] [NEW] X and possibly kernel crashes on overlay screen fglrx
Public bug reported: Hi, X is crashing whenever you use XV overlays. I also noticed that this happens with skype and gucview. [ 35503.966] (EE) [ 35503.966] (EE) Backtrace: [ 35503.968] (EE) 0: /usr/bin/X (xorg_backtrace+0x48) [0x7ff31f324958] [ 35503.968] (EE) 1: /usr/bin/X (0x7ff31f17c000+0x1ac649) [0x7ff31f328649] [ 35503.968] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7ff31e279000+0x10330) [0x7ff31e289330] [ 35503.968] (EE) 3: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so (xdl_xs115_atiddxPixmapIsTypeOf+0x25) [0x7ff31ab9aaf5] [ 35503.968] (EE) 4: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so (atiddxPixmapIsTypeOf+0xd) [0x7ff31a9b446d] [ 35503.969] (EE) 5: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/amdxmm.so (X740XvPutImage+0x197) [0x7ff317a97957] [ 35503.969] (EE) 6: /usr/bin/X (0x7ff31f17c000+0xaca5d) [0x7ff31f228a5d] [ 35503.969] (EE) 7: /usr/bin/X (0x7ff31f17c000+0xf2def) [0x7ff31f26edef] [ 35503.969] (EE) 8: /usr/bin/X (0x7ff31f17c000+0x55a9e) [0x7ff31f1d1a9e] [ 35503.969] (EE) 9: /usr/bin/X (0x7ff31f17c000+0x5989a) [0x7ff31f1d589a] [ 35503.969] (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0x7ff31ccb6ed5] [ 35503.969] (EE) 11: /usr/bin/X (0x7ff31f17c000+0x44e7e) [0x7ff31f1c0e7e] [ 35503.969] (EE) [ 35503.969] (EE) Segmentation fault at address 0x47 [ 35503.969] (EE) Fatal server error: [ 35503.969] (EE) Caught signal 11 (Segmentation fault). Server aborting [ 35503.969] (EE) [ 35503.969] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 35503.969] (EE) Please also check the log file at /var/log/Xorg.0.log for additional information. [ 35503.969] (EE) [ 35503.969] (II) AIGLX: Suspending AIGLX clients for VT switch [ 35503.971] (II) fglrx(0): Backup framebuffer data. [ 35504.033] (II) fglrx(0): Backup complete. [ 35504.682] (EE) Server terminated with error (1). Closing log file. (END) - Card X11 - [22.757] X Protocol Version 11, Revision 0 [22.757] Build Operating System: Linux 3.2.0-58-generic x86_64 Ubuntu [22.757] Current Operating System: Linux red1 3.13.0-11-generic #31-Ubuntu SMP Wed Feb 19 19:57:21 UTC 2014 x86_64 [22.757] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.13.0-11-generic root=UUID=225aabc5-9098-412c-9cf1-4b06f8ec4c80 ro quiet splash elevator=deadline nomdmonddf nomdmonisw vt.handoff=7 [22.757] Build Date: 13 February 2014 03:27:21PM [22.757] xorg-server 2:1.15.0-1ubuntu6 (For technical support please see http://www.ubuntu.com/support) [22.757] Current version of pixman: 0.30.2 [22.757]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [22.757] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [22.757] (==) Log file: /var/log/Xorg.0.log, Time: Fri Feb 28 00:16:58 2014 [22.761] (==) Using config file: /etc/X11/xorg.conf [22.761] (==) Using system config directory /usr/share/X11/xorg.conf.d [22.767] (==) ServerLayout amdcccle Layout [22.767] (**) |--Screen amdcccle-Screen[6]-0 (0) [22.767] (**) | |--Monitor default monitor [22.767] (**) | |--Device amdcccle-Device[6]-0 --- lspci 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD790 Host Bridge 00:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RX780/RD790 PCI to PCI bridge (external gfx0 port A) 00:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD790 PCI to PCI bridge (PCI express gpp port C) 00:07.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RX780/RD790 PCI to PCI bridge (PCI express gpp port D) 00:0a.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD790 PCI to PCI bridge (PCI express gpp port F) 00:0b.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD790 PCI to PCI bridge (external gfx1 port A) 00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] 00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller 00:12.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB OHCI1 Controller 00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller 00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller 00:13.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB OHCI1 Controller 00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller (rev 3a) 00:14.1 IDE interface: Advanced Micro Devices, Inc.
[Bug 1286039] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/1286039/+attachment/4000589/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1286039 Title: X and possibly kernel crashes on overlay screen fglrx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1286039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1286039] BootDmesg.txt
apport information ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/1286039/+attachment/4000583/+files/BootDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1286039 Title: X and possibly kernel crashes on overlay screen fglrx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1286039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1286039] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1286039/+attachment/4000592/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1286039 Title: X and possibly kernel crashes on overlay screen fglrx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1286039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1286039] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/1286039/+attachment/4000596/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1286039 Title: X and possibly kernel crashes on overlay screen fglrx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1286039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1286039] XorgConf.txt
apport information ** Attachment added: XorgConf.txt https://bugs.launchpad.net/bugs/1286039/+attachment/4000598/+files/XorgConf.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1286039 Title: X and possibly kernel crashes on overlay screen fglrx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1286039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1286039] Xrandr.txt
apport information ** Attachment added: Xrandr.txt https://bugs.launchpad.net/bugs/1286039/+attachment/4000601/+files/Xrandr.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1286039 Title: X and possibly kernel crashes on overlay screen fglrx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1286039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1286039] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/1286039/+attachment/4000594/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1286039 Title: X and possibly kernel crashes on overlay screen fglrx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1286039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1286039] UnitySupportTest.txt
apport information ** Attachment added: UnitySupportTest.txt https://bugs.launchpad.net/bugs/1286039/+attachment/4000597/+files/UnitySupportTest.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1286039 Title: X and possibly kernel crashes on overlay screen fglrx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1286039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1286039] xserver.outputs.txt
apport information ** Attachment added: xserver.outputs.txt https://bugs.launchpad.net/bugs/1286039/+attachment/4000603/+files/xserver.outputs.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1286039 Title: X and possibly kernel crashes on overlay screen fglrx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1286039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1286039] XorgLogOld.txt
apport information ** Attachment added: XorgLogOld.txt https://bugs.launchpad.net/bugs/1286039/+attachment/4000600/+files/XorgLogOld.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1286039 Title: X and possibly kernel crashes on overlay screen fglrx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1286039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1286039] XorgLog.txt
apport information ** Attachment added: XorgLog.txt https://bugs.launchpad.net/bugs/1286039/+attachment/4000599/+files/XorgLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1286039 Title: X and possibly kernel crashes on overlay screen fglrx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1286039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1286039] xdpyinfo.txt
apport information ** Attachment added: xdpyinfo.txt https://bugs.launchpad.net/bugs/1286039/+attachment/4000602/+files/xdpyinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1286039 Title: X and possibly kernel crashes on overlay screen fglrx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1286039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1286039] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1286039/+attachment/4000595/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1286039 Title: X and possibly kernel crashes on overlay screen fglrx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1286039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1286039] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/1286039/+attachment/4000593/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1286039 Title: X and possibly kernel crashes on overlay screen fglrx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1286039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1286039] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1286039/+attachment/4000591/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1286039 Title: X and possibly kernel crashes on overlay screen fglrx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1286039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1272890] [NEW] Connection error in iscsi targets
Public bug reported: Hi, It seems that my open-iscsi/tgt installation is not relliable. I'm receiving this over logs: Jan 26 13:06:27 blue-compute iscsid: Kernel reported iSCSI connection 1:0 error (1019 - ISCSI_ERR_XMIT_FAILED: Transmission of iSCSI packet failed) state (2) Jan 26 13:06:27 blue-compute iscsid: Kernel reported iSCSI connection 3:0 error (1019 - ISCSI_ERR_XMIT_FAILED: Transmission of iSCSI packet failed) state (2) Jan 26 13:06:27 blue-compute iscsid: Kernel reported iSCSI connection 2:0 error (1019 - ISCSI_ERR_XMIT_FAILED: Transmission of iSCSI packet failed) state (2) Jan 26 13:06:44 blue-compute iscsid: Connection1:0 to [target: iqn.2010-10.org.openstack:volume-73d6b50b-a5e8-497a-98f2-e1c31645eb71, portal: 172.16.0.119,3260] through [iface: default] is shutdown. Jan 26 13:06:44 blue-compute iscsid: Connection2:0 to [target: iqn.2010-10.org.openstack:volume-8b078749-527b-4936-abc3-e642b7e11929, portal: 172.16.0.119,3260] through [iface: default] is shutdown. Jan 26 13:06:44 blue-compute iscsid: Connection3:0 to [target: iqn.2010-10.org.openstack:volume-d38a950e-326c-4e81-9245-840d826f3e41, portal: 172.16.0.119,3260] through [iface: default] is shutdown. A lot of times when rebooting iscsid. But while connected: Jan 26 13:04:34 blue-compute iscsid: semop down failed 22 Jan 26 13:04:34 blue-compute iscsid: semop down failed 22 Jan 26 13:04:35 blue-compute kernel: [230627.635286] connection7:0: detected conn error (1019) Jan 26 13:04:35 blue-compute iscsid: semop down failed 22 Jan 26 13:04:36 blue-compute kernel: [230629.139162] connection1:0: detected conn error (1019) Jan 26 13:04:36 blue-compute kernel: [230629.139199] connection2:0: detected conn error (1019) Jan 26 13:04:37 blue-compute iscsid: semop down failed 22 Jan 26 13:04:37 blue-compute iscsid: semop down failed 22 Jan 26 13:04:38 blue-compute kernel: [230630.642895] connection7:0: detected conn error (1019) Jan 26 13:04:38 blue-compute iscsid: semop down failed 22 Jan 26 13:04:39 blue-compute kernel: [230632.146789] connection1:0: detected conn error (1019) Jan 26 13:04:39 blue-compute kernel: [230632.146828] connection2:0: detected conn error (1019) So something is going wrong here. 172.16.0.119 is the same host where iscsi/tgt is installed and contains targets. I mean, everything is in the same machine. So no network problems should be here. Cannot find any solution to this so suppose that's a bug. The software installed is ii open-iscsi 2.0.873-3ubuntu7 amd64High performance, transport independent iSCSI implementation i tgt 1:1.0.38-0ubuntu1 amd64 Linux SCSI target user-space tools Ubuntu saucy. Linux blue-compute 3.11.0-12-generic #19-Ubuntu SMP Wed Oct 9 16:20:46 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Best regards, ** Affects: open-iscsi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1272890 Title: Connection error in iscsi targets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1272890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 993922] Re: 1415:2000 PS Eye driver not working
As far I can tell. The driver didn't improved. The problem is that I'm not a good tester because I discovered that my computer does something wierd with USB. It seems something related to bandwidth. So in the computer where I used to test this driver the camera only works in low resolution. It seems to work well in another computer but maybe someone else can try. The driver seems to work. But I cannot tell until what extent. I'm not able to tell if it works at higher resolutions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/993922 Title: 1415:2000 PS Eye driver not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/993922/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 950413] Re: 0a5c:201e [Lenovo ThinkPad X41] Bluetooth connections stalling
Hi Christopher, will try to do it but since I don't use this keyboard all time it will take me time to do it. Cause I have to switch environment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/950413 Title: 0a5c:201e [Lenovo ThinkPad X41] Bluetooth connections stalling To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/950413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 950413] Re: 0a5c:201e [Lenovo ThinkPad X41] Bluetooth connections stalling
I can confirm with latest kernel has same bug. [116176.608967] hid-generic 0005:046D:B309.003F: input,hidraw2: BLUETOOTH HID v1.1b Mouse [Logitech diNovo Edge] on 00:10:60:af:02:19 [116221.665226] Bluetooth: hci0 link tx timeout [116221.665239] Bluetooth: hci0 killing stalled connection 00:07:61:73:4f:76 [116223.100435] hid-generic 0005:046D:B309.0040: unknown main item tag 0x0 [116228.104906] input: Logitech diNovo Edge as /devices/pci:00/:00:12.0/usb3/3-3/3-3:1.0/bluetooth/hci0/hci0:7/input76 [116228.105262] hid-generic 0005:046D:B309.0040: input,hidraw2: BLUETOOTH HID v1.1b Mouse [Logitech diNovo Edge] on 00:10:60:af:02:19 Not the same model, but same problem. Linux red1 3.11.0-15-generic #23-Ubuntu SMP Mon Dec 9 18:17:04 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux g -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/950413 Title: 0a5c:201e [Lenovo ThinkPad X41] Bluetooth connections stalling To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/950413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1242587] Re: Kernel error while writing to iscsi ext4 filesystem
This seems to be resolved in recent kernels. Thank you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1242587 Title: Kernel error while writing to iscsi ext4 filesystem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1242587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1255516] Re: Network access broken to some hosts after some usage...
I'm having less problems with macvtap driver. It seems that brctl bridges has some kind of problems. I migrated everything from brctl to macvtap and now it's working without problems. I had to add a new interface to let host and virtualization communicate but that's all. I'm pretty sure that there is a problem on this driver. I have another machine with precise ubuntu and had much less problems. I wanted to update but now I don't think it's a good idea. Since it will be installed as a Compute node of Openstack cloud. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1255516 Title: Network access broken to some hosts after some usage... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netbase/+bug/1255516/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1255516] Re: Network access broken to some hosts after some usage...
Hi, I'm not sure if this is ubuntu only. I suspect that's kernel problem. Or driver problem but I can't diagnose. What do you need? I realized that I was using a bridge done with brctl and the added this bridge to an ovs bridge. It caused the system to fail faster... Few seconds... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1255516 Title: Network access broken to some hosts after some usage... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netbase/+bug/1255516/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1255516] Re: Network access broken to some hosts after some usage...
I've switched to macvtap and trying to see if it works better... For now looks like it's working, thought I've found another possible bug that I will test before reporting. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1255516 Title: Network access broken to some hosts after some usage... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/core-network/+bug/1255516/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 997978] Re: KVM images lose connectivity with bridged network
I have to clarify that I'm not sure that this has something to do with KVM, QEMU and the like. I think is more a problem of the linux bridge driver since It fails even if you don't have any vm running. Yes, it takes more time to fail but this can be because not enough traffic to make it fail. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/997978 Title: KVM images lose connectivity with bridged network To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/997978/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 997978] Re: KVM images lose connectivity with bridged network
I have to clarify that I'm not sure that this has something to do with KVM, QEMU and the like. I think is more a problem of the linux bridge driver since It fails even if you don't have any vm running. Yes, it takes more time to fail but this can be because not enough traffic to make it fail. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/997978 Title: KVM images lose connectivity with bridged network To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/997978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 997978] Re: KVM images lose connectivity with bridged network
I've found this problem in my saucy installation. I just opened a bug cause I'm not sure if it's related. https://bugs.launchpad.net/ubuntu/+source/core-network/+bug/1255516 My problem is actually worse since host machine cannot get access to other machines on the network. Not even virtual machines but hardware machines, routers, NAS, and so on. The only way to recover from this situation is to ifdown ifup the bridge. Then it recovers until it happens again. When I remove the bridge no problems. But I was not able to test it since I need the bridge up. I'm investigating macvtap instead of bridge... -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/997978 Title: KVM images lose connectivity with bridged network To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/997978/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1255516] [NEW] Network access broken when interface is configured with dhcp
Public bug reported: Hi, I'm suffering something that's strange. I think it's related to dhcp but really don't know. I configured my server to use dhcp so it can receive dns updates and ip on each boot. Among using PXE with maas for booting. The problem is that I found that it looses network access from time to time. The only way to recover the network is by doing ifdown br0 ifup br0. Since this is a virtualization server everytime I do this, the virtual machines loose also the network so I have to restart each one. I tried to change to another switch/router because I suspected that link is broken from time to time and this caused dhcpd to rerun, broking the configuration given at boot. It made no change. I changed the interface to which br0 is bridged from eth0 (internal asus motherboard link) to eth2 (intel PRO card pci/e). It made no change. So I'm lost on what's the problem. I've just changed the configuration to static ip and it seems to work now, but I have to test it more, and with heavy load. This is old log, with eth0 in place Nov 26 05:29:11 red1 kernel: [29995.675232] br0: port 1(eth0) entered disabled state Nov 26 05:29:11 red1 avahi-daemon[1508]: Interface br0.IPv6 no longer relevant for mDNS. Nov 26 05:29:11 red1 avahi-daemon[1508]: Leaving mDNS multicast group on interface br0.IPv6 with address fe80::224:8cff:fe3b:c700. Nov 26 05:29:11 red1 avahi-daemon[1508]: Withdrawing address record for fe80::224:8cff:fe3b:c700 on br0. Nov 26 05:29:11 red1 charon: 02[KNL] fe80::224:8cff:fe3b:c700 disappeared from br0 Nov 26 05:29:11 red1 charon: 02[KNL] interface eth0 deactivated Nov 26 05:29:11 red1 charon: 02[KNL] interface eth0 deleted Nov 26 05:29:11 red1 kernel: [29995.723958] device eth0 left promiscuous mode Nov 26 05:29:11 red1 kernel: [29995.723971] br0: port 1(eth0) entered disabled state Nov 26 05:29:11 red1 kernel: [29995.730646] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready Nov 26 05:29:11 red1 charon: 02[KNL] interface vnet1 deleted Nov 26 05:29:11 red1 charon: 02[KNL] interface vnet0 deleted Nov 26 05:29:11 red1 charon: 02[KNL] interface br0 deleted Nov 26 05:29:11 red1 avahi-daemon[1508]: Withdrawing workstation service for br0. Nov 26 05:29:11 red1 kernel: [29995.732532] device vnet1 left promiscuous mode Nov 26 05:29:11 red1 kernel: [29995.732546] br0: port 3(vnet1) entered disabled state Nov 26 05:29:11 red1 kernel: [29995.733670] device vnet0 left promiscuous mode Nov 26 05:29:11 red1 kernel: [29995.733680] br0: port 2(vnet0) entered disabled state Nov 26 05:29:11 red1 kernel: [29995.734800] device br0 left promiscuous mode Nov 26 05:29:11 red1 NetworkManager[3392]:SCPlugin-Ifupdown: devices removed (path: /sys/devices/virtual/net/br0, iface: br0) Nov 26 05:29:12 red1 kernel: [29995.793763] device eth0 entered promiscuous mode Nov 26 05:29:12 red1 charon: 02[KNL] interface eth0 activated Nov 26 05:29:12 red1 kernel: [29995.804671] r8169 :05:00.0 eth0: link down Nov 26 05:29:12 red1 kernel: [29995.804688] r8169 :05:00.0 eth0: link down Nov 26 05:29:12 red1 kernel: [29995.805141] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready : Any idea on what can it be? ** Affects: core-network (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1255516 Title: Network access broken when interface is configured with dhcp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/core-network/+bug/1255516/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1255516] Re: Network access broken to some hosts after some usage...
This is last log of faillure: [20173.368191] qbrd915d7fa-eb: port 2(tapd915d7fa-eb) entered disabled state [20173.372029] device tapd915d7fa-eb left promiscuous mode [20173.372035] qbrd915d7fa-eb: port 2(tapd915d7fa-eb) entered disabled state [20174.564351] type=1400 audit(1385569885.340:100): apparmor=STATUS operation=profile_remove parent=9268 profile=unconfined name=libvirt-d522bc4a-8a7a-4530-963a-d706361d9cf6 pid=9269 comm=apparmor_parser [20189.388200] type=1400 audit(1385569900.148:101): apparmor=STATUS operation=profile_load parent=9297 profile=unconfined name=libvirt-d522bc4a-8a7a-4530-963a-d706361d9cf6 pid=9298 comm=apparmor_parser [20189.506371] device tapd915d7fa-eb entered promiscuous mode [20189.536371] qbrd915d7fa-eb: port 2(tapd915d7fa-eb) entered forwarding state [20189.536403] qbrd915d7fa-eb: port 2(tapd915d7fa-eb) entered forwarding state [20191.932260] kvm [9491]: vcpu0 unhandled rdmsr: 0xc001100d [20191.932277] kvm [9491]: vcpu0 unhandled rdmsr: 0xc0010112 [20192.086417] kvm [9491]: vcpu0 unhandled rdmsr: 0xc0010001 [22254.219798] init: neutron-metadata-agent main process (3190) killed by TERM signal [22254.289118] init: neutron-plugin-openvswitch-agent main process (3198) killed by TERM signal [22633.070206] qbrd915d7fa-eb: port 2(tapd915d7fa-eb) entered disabled state [22633.071270] device tapd915d7fa-eb left promiscuous mode [22633.071274] qbrd915d7fa-eb: port 2(tapd915d7fa-eb) entered disabled state [22634.156716] type=1400 audit(1385572341.864:102): apparmor=STATUS operation=profile_remove parent=16946 profile=unconfined name=libvirt-d522bc4a-8a7a-4530-963a-d706361d9cf6 pid=16947 comm=apparmor_parser [22716.762951] br0: port 3(vnet1) entered disabled state [22716.763058] br0: port 2(vnet0) entered disabled state [22716.763092] br0: port 1(eth2) entered disabled state [22716.874182] device eth2 left promiscuous mode [22716.874195] br0: port 1(eth2) entered disabled state [22716.879092] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready [22716.881038] device vnet1 left promiscuous mode [22716.881050] br0: port 3(vnet1) entered disabled state [22716.881973] device vnet0 left promiscuous mode [22716.881985] br0: port 2(vnet0) entered disabled state [22716.883144] device br0 left promiscuous mode [22716.942674] device eth2 entered promiscuous mode [22717.024067] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready [22717.024080] 8021q: adding VLAN 0 to HW filter on device eth2 [22717.036589] br0: port 1(eth2) entered forwarding state [22717.036678] br0: port 1(eth2) entered forwarding state [22717.772845] br0: port 1(eth2) entered disabled state [22718.702856] e1000e: eth2 NIC Link is Up 100 Mbps Full Duplex, Flow Control: None [22718.703174] IPv6: ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready [22718.703290] br0: port 1(eth2) entered forwarding state [22718.703373] br0: port 1(eth2) entered forwarding state -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1255516 Title: Network access broken to some hosts after some usage... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/core-network/+bug/1255516/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1255516] Re: Network access broken when interface is configured with dhcp
Hi, The DHCP issue has nothing to do with this. I have just done static ip config as I said and found that I'm loosing connection over time. Strange thing is that I do not loose connection to hosts if I maintain a ping on an open terminal. But if I stop ping, connection is lost after a while. ** Summary changed: - Network access broken when interface is configured with dhcp + Network access broken to some hosts after some usage... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1255516 Title: Network access broken to some hosts after some usage... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/core-network/+bug/1255516/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1255516] Re: Network access broken to some hosts after some usage...
I'm really lost with this. root@red1:~# ping controller PING jb4ja.cloud.level2crm.com (172.16.0.115) 56(84) bytes of data. 64 bytes from jb4ja.cloud.level2crm.com (172.16.0.115): icmp_seq=1 ttl=64 time=0.624 ms 64 bytes from jb4ja.cloud.level2crm.com (172.16.0.115): icmp_seq=2 ttl=64 time=0.339 ms ^C --- jb4ja.cloud.level2crm.com ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1002ms rtt min/avg/max/mdev = 0.339/0.481/0.624/0.144 ms And After a while root@red1:~# ping controller PING jb4ja.cloud.level2crm.com (172.16.0.115) 56(84) bytes of data. From red1 (172.16.0.100) icmp_seq=1 Destination Host Unreachable From red1 (172.16.0.100) icmp_seq=2 Destination Host Unreachable From red1 (172.16.0.100) icmp_seq=3 Destination Host Unreachable -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1255516 Title: Network access broken to some hosts after some usage... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/core-network/+bug/1255516/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1255516] Re: Network access broken to some hosts after some usage...
It seems that system has same problem if I reboot the machine. This is the current log on boot. ** Attachment added: Dmesg output after boot https://bugs.launchpad.net/ubuntu/+source/core-network/+bug/1255516/+attachment/3918435/+files/dmesg-report -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1255516 Title: Network access broken to some hosts after some usage... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/core-network/+bug/1255516/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1255516] Re: Network access broken to some hosts after some usage...
It seems that system has same problem if I reboot the machine. This is the current log on boot. ** Attachment added: Dmesg output after boot https://bugs.launchpad.net/ubuntu/+source/core-network/+bug/1255516/+attachment/3918436/+files/dmesg-report -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1255516 Title: Network access broken to some hosts after some usage... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/core-network/+bug/1255516/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
