** Changed in: linux (Ubuntu)
Status: Fix Released => Fix Committed
--
Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
https://bugs.launchpad.net/bugs/268502
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubunt
that 'fix' might be.
KeithG
--
Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
https://bugs.launchpad.net/bugs/268502
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bu
Tom ,
Thanks! I did not think that the 'fix committed' worked like that, but
was looking through the thread for a fix that someone said "worked" and
a response saying, "yes, worked for me, too".
On a whim, I added the repository
"http://ppa.launchpad.net/blueman/ppa/ubuntu karmic main" and then r
Well, I just tried the serial port. I do not think this is part of this
bug, though, as it will not allow me to select the 1234 paring number
that my serial port needs. What I did was click on the device in the BT
manager, then select the pin option and select 1234 then clicked
connect. At that tim
The latest I have tried is to uninstall "gnome-bluetooth" and install
"bluez-gnome". This allowed me to actually connect to the serial port
with the '1234' code. It now shows up in BT manager with a totally
different dialog graphics and commands, but it seems to be more robust
at least for this pai
apport information
** Tags added: apport-collected
** Description changed:
This is similar to bug 162671, but it is the VT6655 which also not
supported under similar circumstances (via has released code, but it is
only for ubuntu 9.04). It appears in the git for later kernels. I was
able
apport information
** Attachment added: "AplayDevices.txt"
http://launchpadlibrarian.net/46077548/AplayDevices.txt
--
VT6655 wireless chipset is unsupported
https://bugs.launchpad.net/bugs/559697
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
apport information
** Attachment added: "ArecordDevices.txt"
http://launchpadlibrarian.net/46077796/ArecordDevices.txt
--
VT6655 wireless chipset is unsupported
https://bugs.launchpad.net/bugs/559697
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
apport information
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/46077914/BootDmesg.txt
--
VT6655 wireless chipset is unsupported
https://bugs.launchpad.net/bugs/559697
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
apport information
** Attachment added: "Card0.Amixer.values.txt"
http://launchpadlibrarian.net/46077931/Card0.Amixer.values.txt
--
VT6655 wireless chipset is unsupported
https://bugs.launchpad.net/bugs/559697
You received this bug notification because you are a member of Ubuntu
Bugs, which
apport information
** Attachment added: "Card0.Codecs.codec97.0.ac97.0.0.regs.txt"
http://launchpadlibrarian.net/46078036/Card0.Codecs.codec97.0.ac97.0.0.regs.txt
--
VT6655 wireless chipset is unsupported
https://bugs.launchpad.net/bugs/559697
You received this bug notification because you
apport information
** Attachment added: "Lsusb.txt"
http://launchpadlibrarian.net/46078108/Lsusb.txt
--
VT6655 wireless chipset is unsupported
https://bugs.launchpad.net/bugs/559697
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
apport information
** Attachment added: "Card0.Codecs.codec97.0.ac97.0.0.txt"
http://launchpadlibrarian.net/46077966/Card0.Codecs.codec97.0.ac97.0.0.txt
--
VT6655 wireless chipset is unsupported
https://bugs.launchpad.net/bugs/559697
You received this bug notification because you are a memb
apport information
** Attachment added: "Lspci.txt"
http://launchpadlibrarian.net/46078052/Lspci.txt
--
VT6655 wireless chipset is unsupported
https://bugs.launchpad.net/bugs/559697
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
apport information
** Attachment added: "ProcModules.txt"
http://launchpadlibrarian.net/46078401/ProcModules.txt
--
VT6655 wireless chipset is unsupported
https://bugs.launchpad.net/bugs/559697
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
apport information
** Attachment added: "PciMultimedia.txt"
http://launchpadlibrarian.net/46078178/PciMultimedia.txt
--
VT6655 wireless chipset is unsupported
https://bugs.launchpad.net/bugs/559697
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
apport information
** Attachment added: "UdevLog.txt"
http://launchpadlibrarian.net/46078630/UdevLog.txt
--
VT6655 wireless chipset is unsupported
https://bugs.launchpad.net/bugs/559697
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
apport information
** Attachment added: "WifiSyslog.txt"
http://launchpadlibrarian.net/46078786/WifiSyslog.txt
--
VT6655 wireless chipset is unsupported
https://bugs.launchpad.net/bugs/559697
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
apport information
** Attachment added: "ProcCpuinfo.txt"
http://launchpadlibrarian.net/46078312/ProcCpuinfo.txt
--
VT6655 wireless chipset is unsupported
https://bugs.launchpad.net/bugs/559697
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
apport information
** Attachment added: "ProcInterrupts.txt"
http://launchpadlibrarian.net/46078376/ProcInterrupts.txt
--
VT6655 wireless chipset is unsupported
https://bugs.launchpad.net/bugs/559697
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
apport information
** Attachment added: "UdevDb.txt"
http://launchpadlibrarian.net/46078485/UdevDb.txt
--
VT6655 wireless chipset is unsupported
https://bugs.launchpad.net/bugs/559697
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Wow, it uploaded a lot of stuff... This is with the latest Ubuntu 10.04
RC after updates to make it current as of last night. THis wireless card
still doe snot show up or work. Like I said earlier, there is reference
to it in the Kernel driver git, but there does not appear to be enough
in the part
Well, this is affecting me as well on released code?!? I "killall gnome-
panel" and it works fine, but from login I get no panels except for one
login (mine). The 2 other 'users' get no panels at all. I have set them
up with a launcher icon that kills the panels and resets teh panels and
all is fin
No problem pairing a phone that can negotiate a random code, but my BT
serial with a code 1234, I cannot pair. It shows, but after I select the
1234 code, it tries to send a random code.
Please help.
KeithG
--
Bluetooth almost impossible to pair - too short timeout, pin sel fails
https
Public bug reported:
This is similar to bug 162671, but it is the VT6655 which also not
supported under similar circumstances (via has released code, but it is
only for ubuntu 9.04). It appears in the git for later kernels. I was
able to follow instructions in the other bug thread and get the vt66
Public bug reported:
Binary package hint: gnome-bluetooth
I have a BT serial port with a pin of 1234. I cannot pair to this device
with gnome-bluetooth. Every attempt results in gnome-bluetooth requiring
a 6 digit random pin. I was able to pair when I uninstalled gnome-
bluetooth and installed bl
Baptiste,
Yes, I did try this and was able to find it. If I selected fixed pin
1234, it accepts that then immediately shows me the 6 digit pin and
tells me that it failed to connect. I have found the gnome-bluetooth
package to be inconsistent with pairing and repairing. That is except
with OBEX fi
Actually on mine, it only partially works. I cannot see the list of
paired devices any more. The drop down menu "devices" does nothing. This
should be the default bluetooth manager for Ubuntu as it really works.
Now if I could get the second serial port to show up, I'd be ecstatic.
--
[karmic] bl
Problem is with udisks (previously devicekits-disks). It will *not*
automount a fat or vfat parttion as RW. This messes with samba shares
and the ability to copy pictures from a camera CFcard and erase it.
Please fix this. It should mount fat/vfat as rw for all users, not just
root.
KeithG
Just upgraded to 10.04. Now every time I reboot, there are a ton of BT
device addresses listed. Some can be deleted, but some cannot. I do not
know where to look for the config file to delete them there. Everything
seesm to work (after I uninstalled gnome bluetooth and installed
blueman), but there
Similar stuff here. Fresh instal of 10.04LTS. odd handling of DVDs . I
get this message in dmesg on each burned DVD that works fine in other
OSes and in a player: "end_request: I/O error, dev sr1, sector 9147640".
I have anotehr DVD that plays fine, but when I try to rip it to disk, it
hangs and dr
Postponing this for 18.10 would be a problem, IMO. Please include it in
18.04.x (LTS). This missing package not only does not allow a Nautilus
browse, it also breaks deja dup nfs functionality as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
Still an issue with 18.04. FWIW, it is included in the Arch version of
Gnome and gvfs-nfs works in Arch. Both in Nautilus and in DejaDup. NFS
should also be a possible means of a backup with deja-dup, but because
this module is not included in gvfs, it does not work. Waiting for this
regression to
Public bug reported:
gvfs will not allow an NFS mount.
In nautilus, one cannot mount an NFS mount using 'other locations'. If a
valid url is typed, (nfs://IP _ADDRESS/MOUNT_POINT one can never select
'connect' as it is always greyed out.
Fully up to date ubuntu 18.04. Duplicates same behavior on
Please, can't we just remove this STA driver from Ubuntu. IMO, it is not
worth the effort and it is pulling resources from other issues/bugs that
can actually be fixed. This STA driver has been a problem because
Broadcom does not want to work with open source. The resolution of
incompatibilities si
Public bug reported:
Dmesg is filled with this:
[32582.450283] [ cut here ]
[32582.450302] WARNING: CPU: 1 PID: 1154 at
/build/buildd/linux-3.13.0/drivers/gpu/drm/i915/intel_display.c:9226
intel_modeset_check_state+0x62d/0x780 [i915]()
[32582.450304] encoder's hw state do
Tried latest mainline intel kernel I could find (3.15.0-994-generic) and
same issue. This appears to be from, at least, 13.10 to current kernel.
I got this latest kernel here: http://kernel.ubuntu.com/~kernel-
ppa/mainline/ and selected this one: drm-intel-nightly from 5/30/14
I see that the bot
3.15.0-031500rc7-generic kernel has it as well.
** Tags added: bug exists upstream
** Tags removed: bug exists upstream
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
Just installed it and checked dmesg and this warning was there. I
recently got this computer and have only tried 13.10 and 14.04. THis si
after a cold boot. If I try to suspend, it appears to suspend correctly.
When I resume, it has black screen. I have done a ton of updates, so I
need to try suspe
call
modeset=0 video.allow_duplicates=1
I no longer get the message in the log. The video does not appear to be
as crisp somehow, but I can suspend and wake from the command line (tty
or terminal) I get a black screen on resume when I allow the UI to
timeout and suspend.
KeithG
--
You received
If I set modeset=1 or -1, I get the crash on resume. Black screen on all
ttys and no reconnect to network (I cannot ssh back in).
modeset = 0 will allow normal function, but no KMS.
KeithG
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I loaded 12.04 amd64 on it this morning. This appears to work correctly.
I can suspend and resume with no issues. There is no warning in the log
other than the 'duplicate interface' which does not seem to affect
anything. I have not upgraded anything, just installed xubuntu 12.04
then installed the
I have started the process. Strange that this bug has crept in and no
one has noticed. It is pretty limiting, actually.
KeithG
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1324935
Title:
[Dell
Same here. Adding the line to /etc/hosts with the .local works. The printers
are automatically detected (as expected) and auto populate the printers. I did
not have to go to the cups web interface to add them. Without the .local, it
does not work.
Has worked with every release since 11.04. This
Also does not work in 16.10. Same error:
$ smart-notifier
/usr/share/smart-notifier/smart_notifier/gui.py:23: PyGIWarning: Gtk was
imported without specifying a version first. Use gi.require_version('Gtk',
'3.0') before import to ensure that the right version gets loaded.
from gi.repository i
Same deal in 16.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1598896
Title:
Warning from smart-notifier
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts
Running 4.4.0-64 in 16.04. This is definitely a flaky wireless driver.
If I turn it off, and back on I cannot browse any ssids. If I suspend
and resume, I cannot browse any ssids. I have recently added the options
to the /etc/modprobe.d/rtl8821ae.conf file "options rtl8821ae ips=0
fwlps=0" It is im
Fix released! Awesome. Is there a link to anything that will allow me to
verify that it is fixed? Is it in the current 16.04 kernel? 16.10?
17.04? Upstream?
Thanks.
Keith
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
My experience with this driver or any broadcom wl or wl/bt card is that
it is too much trouble to deal with. I pulled both of them I had and
replaced them with Intel cards which have great support and 'just work'.
Amazon or newegg or wherever has great intel cards that work for about
$25.00. It is
Public bug reported:
Previously (12.04 - 15.04), if I edited the /etc/systemd/logind.conf
file to auto suspend the GDM login screen it worked. Now, if I edit the
2 lines to cause a suspend if the login screen (GDM) is up and no one
logs in for 15 minutes, I get unintended random suspend from an ac
Just spent some time trying to do this. Can you please give more
'recipe' type instructions. If I install the driver, I get the fully
compiled driver. If I install the source, it also compiles and installs
the 'wl' driver.
Also, the current version of 16.04 no longer has that older STA package.
It
Well, It does not work for me.
I went to the archives. I grabbed the 6.30.223.141-1 archive. Unpacked it. Put
the edited files from the patch above in the amd64 directory and built the
module. To get it to build, I had to edit the MAKEFILE to add this EXTRA_CFLAGS
"-Wno-error=date-time" as it w
May be due to edit of /etc/systemd/login.conf edited to suspend computer
if login screen is up. uncommented:
#IdleAction=suspend
#IdleActionSec=15min
and saw the behavior.
re-commented and have not seen the behavior. This edit has worked to suspend
the gdm login screen since 12.04 to 15.04. I
I'm interested in this. If you go to Broadcom, though, there is a later version
of the driver.
http://www.broadcom.com/docs/linux_sta/hybrid-v35-nodebug-pcoem-6_30_223_271.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
Public bug reported:
This package is broken. The smartmon tools use commands which are no
longer in 16.04.
Example:
/etc/smartmontools/run.d/10powersave-notify
#! /bin/sh
# Send message if /usr/lib/powersave/powersave-notify exists or exit silently
[ -x /usr/lib/powersave/powersave-notify ] ||
It is also a regression, isn't it? It appears that mail is set up, but
it is mailed to root and it is uncommon for a user to log in as root...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1646886
Tit
I get loginloop where it is trying to set the video mode but just
resets. I cannot even login to a terminal as it constantly wipes it out
and sends me to tty7. My card is:
*-display
description: VGA compatible controller
product: G71GL [Quadro FX 3500] [10DE:29D]
This package no longer works with the current smartmontools
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1598896
Title:
Warning from smart-notifier
To manage notifications about this bug go to:
ht
I do not know why this is associated with nvidia-graphis-drivers-304 as
I am running 361.42
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574127
Title:
Random suspend when working
To manage notifi
Public bug reported:
I have seen this with 15.10 and now with 16.04. Am running a fresh/clean
install 16.04LTS (not upgraded) with Nvidia driver (361.42). I have a
firefox browser open and when browsing, it will just suspend randomly. I
am typing or mous-ing and it suspends. I do have the UI set t
how about 16.04? It does not hang any more, but the message is still
repeated many times in the dmesg log:
[1.940071] [ cut here ]
[1.940109] WARNING: CPU: 1 PID: 6 at
/build/linux-Ay7j_C/linux-4.4.0/drivers/gpu/drm/drm_irq.c:1326
drm_wait_one_vblank+0x1b5/0x1c0 [
I installed 16.04 on 3 machines. One gigabyte AMD/nvidia 361.42, One
Dell Core 2 Duo/Nvidia 304.131 and one Dell Inspiron Laptop i915 with
default video driver. All 3 do this randomly. I am working along typing,
mousing, reading, etc and the computer suspends. It always resumes
correctly. I need he
I have some older hardware (Core 2 Duo 1.5) and unless I disable
tracker, the computer is unusable. CPU 100%, CPU temps up to 85C. With
it disabled, CPU idles at 47 and the old laptop is, at least, useful for
light browsing, email, etc. Using Gnome shell. I have no clue what it
is doing, but it th
I am running 32 bit 10.10 fully up to date. It appears that sound juicer
will extract music. When I put the CD in the drive with rhythmbox,
though, it crashes.
dmesg shows this:
[35518.296548] rhythmbox[4357]: segfault at 0 ip 02aa531a sp b1fe3120 error 6
in libnss_wins.so.2[2a5c000+2c7000]
[355
I have a Dell Latitude D630. With 9.10 and 10.4, Hibernate worked. With
10.10, hibernate will save the configuration and shut down, but hangs on
restart (it is very slow, though). Suspend works flawlessly. I have not
done anything weird with the install. It has a Nvidia graphics card and
I am runni
I kept seeing it and eventually built v3.8.0 and it 'appeared' to not
show the error. I thought I had found it and started another bisect
between the commits for v3.8.0 and v3.8.1, but when I tried to boot back
to v3.8.0, the error in the log showed up. It was not there previously.
Now if I reboot
Just upgraded to 15.04. I still get the error and sometimes it will not
shut down and takes a long time to reboot.
Is this just that the i915 driver is not very good or that my hardware
is not well supported?
# lspci
...
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960
Int
It failed to build for me as well. Ib jumped through lots of googling
and found a couple patches which show it to build, but it never worked
fur me. I can see ssids, but never connect.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
Grabbed all the patches from the 4 corners of the internet to have it
compile on 3.19. Compiles, Installs, shows a list of only the 2.5Ghz
ssids, but will not connect to them. I have never been able to get this
laptop to connect using the STA driver. This behavior is the same as
when I install the
Public bug reported:
new BT dongle is very flaky. If it will pair, whenever it is used to
send any data, it freezes the machine (flashing caps lock and num lock
leds). The only way to get it back is to press and hold the power
button. I have 2 other dongles which work fine. It announces itself as
The chip in the adapter is marked OVC3620. Do not know if this is
helpful or not.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/930848
Title:
USB BT dongle freezes machine
To manage notifications a
For what it is worth, this same dongle hangs a windows 7 machine as well
as a Mac.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/930848
Title:
USB BT dongle freezes machine
To manage notifications
Just loaded ubuntu 15.10 (kernel 4.2.0-18-generic) and it is still
there.
Interestingly, I have this as well:
CPU: 1 PID: 1276 Comm: Xorg Tainted: GW 4.2.0-18-generic
#22-Ubuntu.
I do not know why it is tainted as I did not install any private
modules. on the 'Software & Updates" "
Christopher,
I grabbed kernel 4.4.0-040400rc3-generic as it shows as the latest. I
installed it and get the same messages in the dmesg log. I do note that
the fans are not running so fast. I have been having problems where it
will overheat and shut down. Never had that problem with 15.04 or
earlie
ethany,
I do not really remember. Try 13.04 (and 12.04 if it is still in 13.04).
It was one of those, IIRC, that did not have it. Problem is that so much
has changed in the kernel since then. I went through a huge kernel
bisect project to then be told to report it to the kernel i915 group and
got
I still get this:
[1.968043] [ cut here ]
[1.968074] WARNING: CPU: 0 PID: 85 at
/home/kernel/COD/linux/drivers/gpu/drm/drm_irq.c:1216
drm_wait_one_vblank+0x1b5/0x1c0 [drm]()
And it is way laggy. 15.10 is unusable for me with any of these kernels
(stock, latest,
running 15.04 with the nvidia 304.131(proprietary, tested) and get a
similar result:
Inconsistency detected by ld.so: dl-version.c: 224:
_dl_check_map_versions: Assertion `needed != ((void *)0)' failed!
The binutils installed is 2.25-5ubuntu7
I get this on another machine with the nvidia 352.63
I have an Inspiron 1525 and among its many problems is low volume. Max volume
feels like half volume at best. Running 14.04 with recent kernel:
3.13.0-40-generic
$ cat /proc/asound/card0/codec* | grep Codec
Codec: Conexant ID 2c06
Codec: Silicon Image SiI1392 HDMI
Codec: SigmaTel STAC9228
$ apl
know now? If so, I need a bit more help to
do it.
KeithG
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1324935
Title:
[Dell Inspiron 1525] WARNING: CPU: 1 PID: 1154 at
/build/buildd/linux-3.13.0
I tried 12.10 and 13.04. 12.10 appears to work. Initial install of 13.04
appears to work. When I dist-upgraded 13.04 after I installed it, I got
the warning in the log. I think I have narrowed it down to this release.
I was going to respond with the kernel versions at beginning and end of
13.04, bu
Ok, I did my first bisect with 3.8.0-28.42 and it came up bad. Now I am
here:
$ git bisect bad
Bisecting: 388 revisions left to test after this (roughly 9 steps)
error: Your local changes to the following files would be overwritten by
checkout:
debian.master/changelog
Please, commit your
This is extremely confusing. 1) The kernels I am using do not appear in
that mainline map (version numbers are just not there) 2) I'd rather
just keep going with my first attempt. 3) the example on the
https://wiki.ubuntu.com/Kernel/KernelBisection apparently uses a older
version of git than in Rar
I figured it out. I was able to start over. The key is to not edit any
of the files as it bisects. The revision numbers are good enough for me
to keep track of where I am. As it is, I have done 4 or 5 bisects and am
narrowing it down.
--
You received this bug notification because you are a member
Ok, Something is going wrong. It stalled at 3.8.0-26.38. It is 'good',
but when I go and do 'git bisect good', it does some stuff and returns
and appears to have a new version to build. WHen I build it, it is the
same version 3.8.0-26.38.
--
You received this bug notification because you are a me
Please help! I am trying to follow the instructions to find this bug and am a
bit lost. I have determined that this bug is between 3.8.0-26.38 and
3.8.0-28.42. These do not 'map' to the Mainline kernel map, directly. so I am
guessing near these 2 end points. Following the Mainline instructions,
Christopher,
I Appreciate the help and apologize for being so dense. I think I get it, but
am still a bit lost with the mainline kernel. From the kernel mapping, I see
the 2 kernel versions you are referring to. I have git cloned the kernel. When
I try to tell it that I want 3.8.13.2, though, t
Poked around some more and was able to get other versions in my copy of
the mainline kernel.
this command got me some more kernel versions:
git remote set-url origin
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
now, when I 'tab' to see what is there, I get:
$ git checkou
Christopher.
I used the commit numbers and did the bisect again. Now it points to one
commit which causes the error:
8164f7af88d9ad3a757bd14f634b23997ee77f6b is the first bad commit
commit 8164f7af88d9ad3a757bd14f634b23997ee77f6b
Author: Stephen Boyd
Date: Mon Mar 18 19:44:15 2013 +0100
A
Yes. Bisecting between commits actually did that for me. My 8th pass
used commit c40e3641670eb6ebfdb71d4b0c775416ef95f4f0 which was 'good'
and was the next older commit. The next newer commit was the 9th pass
which used commit 8164f7af88d9ad3a757bd14f634b23997ee77f6b which was
'bad'. Should I cont
It seems odd as the diff shows only changes to the arm branch of the
code. the result of the lshw command are attached.
** Attachment added: "lshw"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1324935/+attachment/4141378/+files/lshw.txt
--
You received this bug notification because y
Christoper, I am not sure. My second git bisect was done using commits
as the end points and not versions. I tracked the commit numbers as
bisect did its work and it appeared that the 8th run actually built to
that commit. I have done a git pull to the commit right before this
(c40e3641670eb6ebfdb7
it turned up bad. I am going one back from that.
e651eab0af88aa7a281fe9e8c36c0846552aa7fc. and will test that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1324935
Title:
[Dell Inspiron 1525] WARNI
So far I have tested 5 back and still have the error. Isn't this what git
bisect is supposed to do? At this rate I'll be compiling for a week, one at
a time.
On Jun 28, 2014 2:55 PM, "KeithG" <1324...@bugs.launchpad.net> wrote:
> it turned up bad.
I started with commit c40e36... and worked back according to the git
log. The last 'good' build was fb72a0... The next commit breaks it.
c40e3641670eb6ebfdb71d4b0c775416ef95f4f0 bad
e651eab0af88aa7a281fe9e8c36c0846552aa7fc bad
7fb476c231bbc551ede5b4afb189d9ca5ab7406d bad
3500ed90b26a9935b943b5e2e4
I rebooted to 14.04 again and built the kernel from that commit,
installed and rebooted 14.04 and the error still shows in the log.
Previously, I was using 13.04 as the base. I guess I will continue to
buils kernels backwards from here until it goes away. Any other
suggestions? I wonder if this is
I have no clue what is going on. I have started building kernels from
v3.8.13 and back. So far all fail. I am at v3.8.7 and still have the
dmesg error. It is not clear from the ubuntu kernel to mainline map as
to which is/should be the version that I have on there which works
without error. The ver
persists in 13.10 saucy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/892768
Title:
Slow boot with ata4.00: failed command: IDENTIFY PACKET DEVICE in log.
To manage notifications about this bug go
I finished the bisect. I am running xubuntu 14.04. I pulled mainline
kernels v3.6 which worked without error and v3.7 which exhibited the
error. I then bisected between the 2. It took 14 steps and concluded
with this which makes more sense:
24929352481f085c5f85d4d4cbc919ddf106d381 is the first bad
The dmesg from this version of the kernel (different line number in the
*.c file) is attached.
Keith
** Attachment added: "dmesg output from the failed commit"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1324935/+attachment/4163777/+files/249293_dmesg.txt
--
You received this bug n
yes, it is still present. dmesg attached.
** Attachment added: "dmesg with 3,16-rc6"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1324935/+attachment/4163968/+files/dmesg-3.16_rc6.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
1 - 100 of 146 matches
Mail list logo
