** Tags added: verification-done-maverick
** Tags added: verification-done-natty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/946928
Title:
sysfs: can not remove 'bsg', no directory
To manage
This bug is awaiting verification that the kernel for Oneiric in
-proposed solves the problem ( 3.0.0-18.31). Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-oneiric' to 'verification-done-oneiric'.
If verification is not
** Changed in: kernel-sru-workflow/verification-testing
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/967068
Title:
linux-lts-backport-maverick:
** Changed in: kernel-sru-workflow/verification-testing
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/965065
Title:
linux: 2.6.35-32.68 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/965346
Title:
linux: 2.6.38-14.58 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/968717
Title:
linux-lts-backport-oneiric:
** Changed in: kernel-sru-workflow/verification-testing
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/967823
Title:
linux-lts-backport-natty:
This bug is awaiting verification that the kernel for Lucid in -proposed
solves the problem (2.6.32-41.88). Please test the kernel and update
this bug with the results. If the problem is solved, change the tag
'verification-needed-lucid' to 'verification-done-lucid'.
If verification is not done
This bug is awaiting verification that the kernel for Oneiric in
-proposed solves the problem (3.0.0-18.31). Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-oneiric' to 'verification-done-oneiric'.
If verification is not
This bug is awaiting verification that the kernel for Oneiric in
-proposed solves the problem ( 3.0.0-18.31). Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-oneiric' to 'verification-done-oneiric'.
If verification is not
This bug is awaiting verification that the kernel for Oneiric in
-proposed solves the problem (3.0.0-18.31). Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-oneiric' to 'verification-done-oneiric'.
If verification is not
This bug is awaiting verification that the kernel for Oneiric in
-proposed solves the problem ( 3.0.0-17.30). Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-oneiric' to 'verification-done-oneiric'.
If verification is not
This bug is awaiting verification that the kernel for Oneiric in
-proposed solves the problem ( 3.0.0-17.30). Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-oneiric' to 'verification-done-oneiric'.
If verification is not
This bug is awaiting verification that the kernel for Oneiric in
-proposed solves the problem ( 3.0.0-17.30). Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-oneiric' to 'verification-done-oneiric'.
If verification is not
This bug is awaiting verification that the kernel for Oneiric in
-proposed solves the problem ( 3.0.0-17.30). Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-oneiric' to 'verification-done-oneiric'.
If verification is not
This bug is awaiting verification that the kernel for Oneiric in
-proposed solves the problem ( 3.0.0-17.30). Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-oneiric' to 'verification-done-oneiric'.
If verification is not
This bug is awaiting verification that the kernel for Oneiric in
-proposed solves the problem ( 3.0.0-17.30). Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-oneiric' to 'verification-done-oneiric'.
If verification is not
As Tim referred in comment #6, this patch is queued for stable so its
safe to assume verification-done.
** Tags removed: verification-needed-oneiric
** Tags added: verification-done-oneiric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This bug is awaiting verification that the kernel for Oneiric in
-proposed solves the problem ( 3.0.0-17.30). Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-oneiric' to 'verification-done-oneiric'.
If verification is not
Well, these are not good news.
Anyway, there's another thing I would like to suggest. Can you try to
add acpi_apic_instance=2 to your kernel? (See
https://wiki.ubuntu.com/Kernel/KernelBootParameters for details on how
to do this).
I'm not sure if this will actually have any impact, but it may
The commit for this issue came in via a stable upstream release (commit
5a50a7c32d630d6cdb13d69afabb0cc81b2f379c) . As such it is can be tagged
as verified.
** Tags removed: verification-needed-oneiric
** Tags added: verification-done-oneiric
--
You received this bug notification because you
** Changed in: kernel-sru-workflow/verification-testing
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/950573
Title:
linux-lts-backport-oneiric:
** Changed in: kernel-sru-workflow/verification-testing
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/949882
Title:
linux: 3.0.0-17.30 -proposed tracker
This patch has hit mainline, with commit
fe316bf2d5847bc5dd975668671a7b1067603bc7.
It may be a good idea to also take a look at commit
9f53d2fe815b4011ff930a7b6db98385d45faa68.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 914319 ***
https://bugs.launchpad.net/bugs/914319
** This bug has been marked a duplicate of bug 914319
NULL pointer dereference at sd_revalidate_disk+0x30/0x2a0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I have uploaded a test kernel with the referred patch reverted. Could
you please check if this problem persists? You can download the new
kernel here:
http://people.canonical.com/~henrix/lp956479/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I have the same problem and yes, with a powered usb hub the problem goes
away.
--
usb interface with wireless keyboard/mouse and usb1.1
https://bugs.launchpad.net/bugs/588082
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Perhaps a duplicate of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/588082 ?
--
USB Wireless keyboard and mouse blocks unexpectedly
https://bugs.launchpad.net/bugs/598883
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
This bug still exists. I can confirm it on Lucid
Linux kila-desktop 2.6.32-25-generic #44-Ubuntu SMP Fri Sep 17 20:26:08 UTC
2010 i686 GNU/Linux
--
problem with key repeat, extra key up events
https://bugs.launchpad.net/bugs/403339
You received this bug notification because you are a member of
Hi Frediano, just to let you know the kernel containing the patch you
were waiting has been released into the -proposed pocket. If you would
like to give it a try before its actually released (should happen in ~2
weeks time), you can follow the instructions in
No SRUs to verify, moving to testing.
** Changed in: kernel-sru-workflow/verification-testing
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1027821
Title:
No SRUs to verify, moving to testing
** Changed in: kernel-sru-workflow/verification-testing
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1029786
Title:
This bug is awaiting verification that the kernel for Oneiric in
-proposed solves the problem (3.0.0-24.40). Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-oneiric' to 'verification-done-oneiric'.
If verification is not
This bug is awaiting verification that the kernel for Oneiric in
-proposed solves the problem (3.0.0-24.40). Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-oneiric' to 'verification-done-oneiric'.
If verification is not
This bug is awaiting verification that the kernel for Oneiric in
-proposed solves the problem (3.0.0-24.40). Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-oneiric' to 'verification-done-oneiric'.
If verification is not
This bug is awaiting verification that the kernel for Oneiric in
-proposed solves the problem (3.0.0-24.40). Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-oneiric' to 'verification-done-oneiric'.
If verification is not
This bug is awaiting verification that the kernel for Precise in
-proposed solves the problem (3.2.0-29.46). Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-precise' to 'verification-done-precise'.
If verification is not
This bug is awaiting verification that the kernel for Precise in
-proposed solves the problem (3.2.0-29.46). Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-precise' to 'verification-done-precise'.
If verification is not
This bug is awaiting verification that the kernel for Precise in
-proposed solves the problem (3.2.0-29.46). Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-precise' to 'verification-done-precise'.
If verification is not
This bug is awaiting verification that the kernel for Precise in
-proposed solves the problem (3.2.0-29.46). Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-precise' to 'verification-done-precise'.
If verification is not
This bug is awaiting verification that the kernel for Precise in
-proposed solves the problem (3.2.0-29.46). Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-precise' to 'verification-done-precise'.
If verification is not
This bug is awaiting verification that the kernel for Precise in
-proposed solves the problem (3.2.0-29.46). Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-precise' to 'verification-done-precise'.
If verification is not
This bug is awaiting verification that the kernel for Precise in
-proposed solves the problem (3.2.0-29.46). Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-precise' to 'verification-done-precise'.
If verification is not
No SRUs to verify, moving to testing.
** Changed in: kernel-sru-workflow/verification-testing
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1028834
Title:
This bug is awaiting verification that the kernel for Precise in
-proposed solves the problem (3.2.0-29.46). Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-precise' to 'verification-done-precise'.
If verification is not
This bug is awaiting verification that the kernel for Lucid in -proposed
solves the problem (2.6.32-42.95). Please test the kernel and update
this bug with the results. If the problem is solved, change the tag
'verification-needed-lucid' to 'verification-done-lucid'.
If verification is not done
This bug is awaiting verification that the kernel for Precise in
-proposed solves the problem (3.2.0-29.46). Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-precise' to 'verification-done-precise'.
If verification is not
I've executed the test case on a Lucid system. Here's the output for the
2.6.32-41.94 kernel:
# uname -a
Linux lucid 2.6.32-41-generic #94-Ubuntu SMP Fri Jul 6 16:51:39 UTC 2012 i686
GNU/Linux
# ./leap_seconds
now: 1343779191:18314044 diff: 0:275081 rem: 0:0
now: 1343779191:518753118 diff:
SRUs verified, moving to testing.
** Changed in: kernel-sru-workflow/verification-testing
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1027831
Title:
Setting bug state as fix commited as per previous comment.
** Changed in: linux (Ubuntu)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1023889
Title:
BUG:
Hi Cristian,
This may be a wild guess, but there's a fix on upstream kernel (commit
d663d181b9e92d80c2455e460e932d34e7a2a7ae sky2: Fix for interrupt
handler), which fixes interrupt handling on Yukon-2 chip. I took a
look at your logs and I can see a single IRQ 44 occurring. So it may be
worth
I've just realised that the kernel in the -proposed pocket also includes
a fix for the sky2 device driver: upstreams commit
5ff0feac88ced864f44adb145142269196fa79d9 sky2: fix checksum bit
management on some chips. So, if the test kernel I referred in
previous comment fixes the issue, you would
Hi Lars, thank you for testing. I'll tag the bug as verified (you just
click the 'Edit tags' button on the top, after the Bug Description).
** Tags removed: verification-needed-precise
** Tags added: verification-done-precise
--
You received this bug notification because you are a member of
Ok, so two questions:
1) What exactly do you mean by not working? If you run 'ifconfig -a' on a
console, do you see your interface? Can you paste the output of this command?
2) Has this network card ever worked with an older version of the kernel? Can
you remember the last kernel version where
So, between kernel 3.2.0-23.36 and 3.2.0-24.39 there is a single commit
that directly affects the sky2 driver (Upstream commit
2240eb4ae3dc4acff20d1a8947c441c451513e37 sky2: dont overwrite settings
for PHY Quick link). Before building another test kernel reverting
this commit, it would great if
Hi Chris,
Would you be able to check if the kernel on -proposed is Ok, so that we
can close this bug? See previous comment for how to enable -proposed.
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
As this fix came from stable updates, and it has already been verified
on Precise, I'm tagging it as verified in Oneiric as well.
** Tags removed: verification-needed-oneiric
** Tags added: verification-done-oneiric
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Thank you for this information, and for opening an upstream bug. One
thing I just noticed is that the last kernel known to work is a PAE
kernel (32 bits), while the first one known to fail is a 64 bits kernel.
Any chances of trying a recent 32 bits kernel to check whether it still
works?
--
You
So, there are still some issues with the asix driver but it looks like
these are different from the original bug report. Do we all agree with
this? If so, I would propose to open a new bug report. Can anyone (the
original reporter, maybe) confirm the original issue is solve with the
kernel
Adam, you can check https://wiki.ubuntu.com/Testing/EnableProposed for
instructions on how to use the -proposed pocket. After enabling the
-proposed pocket, you don't need to manually download the kernel -- just
run apt-get in a console, for example.
--
You received this bug notification
Adam, thanks a lot for testing and verifying that the new kernel solves
the original issue.
David, Ming: do we all agree that we're now dealing with a different
issue? If so, could you please open a new bug?
Thank you all!
--
You received this bug notification because you are a member of
** Tags removed: verification-needed-oneiric
** Tags added: verification-done-oneiric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/999755
Title:
Kernel crash in rb_next doing ohai loops
To manage
Tagged as verified in Oneiric as per comment #46 and IRC chat.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/999755
Title:
Kernel crash in rb_next doing ohai loops
To manage notifications about
So, to summarise: we have a 3.5.0 kernel that fails on 64-bits, but its
Ok for 32-bits. I took a look at the kernel logs, and something that
caught my attention was the following errors/warnings:
[0.00] ACPI Warning: 32/64 FACS address mismatch in FADT - two FACS
tables!
All verified, moving to testing.
** Changed in: kernel-sru-workflow/verification-testing
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1029507
Title:
All verified, moving to testing.
** Changed in: kernel-sru-workflow/verification-testing
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1027841
Title:
** Also affects: linux (Ubuntu Oneiric)
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/1067266
Title:
linux: 3.0.0-27.44 -proposed tracker
To manage
** Also affects: linux (Ubuntu Lucid)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: In Progress = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux (Ubuntu)
Status: In Progress = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067266
Title:
linux: 3.0.0-27.44 -proposed tracker
To manage notifications about
: Undecided
Assignee: Canonical Hardware Certification (canonical-hw-cert)
Status: New
** Affects: kernel-sru-workflow/prepare-package
Importance: Undecided
Assignee: Luis Henriques (henrix)
Status: In Progress
** Affects: kernel-sru-workflow/prepare-package-lbm
** Changed in: linux (Ubuntu)
Status: In Progress = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067666
Title:
linux: 3.2.0-33.52 -proposed tracker
To manage notifications about
*** This bug is a duplicate of bug 1066595 ***
https://bugs.launchpad.net/bugs/1066595
This is a duplicate of bug #1066595, which has already been queued for
next release cycle.
** This bug has been marked a duplicate of bug 1066595
kernel upgrade breaks triple monitor setup
--
You
: Undecided
Assignee: Canonical Hardware Certification (canonical-hw-cert)
Status: New
** Affects: kernel-sru-workflow/prepare-package
Importance: Undecided
Assignee: Luis Henriques (henrix)
Status: In Progress
** Affects: kernel-sru-workflow/prepare-package-lbm
** Changed in: linux (Ubuntu)
Status: In Progress = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1068224
Title:
linux: 3.5.0-18.29 -proposed tracker
To manage notifications about
** Changed in: kernel-sru-workflow/prepare-package
Status: New = In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team (canonical-kernel-team) = Luis Henriques
(henrix)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status
Hi Andreas,
I've built a test kernel containing the referred commit, and uploaded it
here:
http://people.canonical.com/~henrix/lp1065475
(there's a 32 and a 64 bits version)
Could you please install it in your system and see if it solves the
problem?
--
You received this bug notification
** Changed in: linux (Ubuntu)
Status: Confirmed = Triaged
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Luis Henriques (henrix)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
** Changed in: linux (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1052933
Title:
Kernel oops -- IP: [f85ba9e0] ttm_bo_mem_put+0x20/0x30 [ttm]
I believe this should be solved in current Precise kernel (3.2.0-32.51),
after commit:
2d35d73b032ce99701b059023e422a719ed8bab9 drm/radeon: rework pll
selection (v3)
(upstream commit 985f61f7ee647ad570c05eab0b74915da2ac8e19)
Could you please try to update your kernel and verify if you still
You're absolutely right! Sorry, I completely missed the point. Thanks
for the correction.
Anyway, the fix (the revert) is already queued for the next kernel.
This kernel should be out in ~3 weeks, but by the end of this week (or
beginning of next week) you should be able to use it if you enable
: Undecided
Assignee: Canonical Hardware Certification (canonical-hw-cert)
Status: Invalid
** Affects: kernel-sru-workflow/prepare-package
Importance: Undecided
Assignee: Luis Henriques (henrix)
Status: In Progress
** Affects: kernel-sru-workflow/prepare-package-lbm
: Undecided
Assignee: Canonical Hardware Certification (canonical-hw-cert)
Status: New
** Affects: kernel-sru-workflow/prepare-package
Importance: Undecided
Assignee: Luis Henriques (henrix)
Status: In Progress
** Affects: kernel-sru-workflow/prepare-package-lbm
Thanks a lot. So, we have pretty much finish the bisect but the faulty
commit (10feec8db921f3cd754f0f496e2fbf43763b1ccb) doesn't seem to
contain anything particularly suspicious. I'll need to spend a little
bit more time looking at that, but at this point there are two
possibilities:
1) The
I've managed to reproduce the issue and the patched kernel solves the
issue.
The patch has already been submitted (and accepted) upstreams:
https://lkml.org/lkml/2012/6/20/686
** Changed in: linux (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you
** Description changed:
+ == SRU Justification ==
+
+ A NULL pointer will be triggered by ocfs2_fallocate() as it will
+ invoke __ocfs2_change_file_space() with a NULL as the file argument.
+ This may result in filesystem corruption.
+
+ == Fix ==
+
+ This patch has already been submitted
Assignee: Canonical Hardware Certification (canonical-hw-cert)
Status: Invalid
** Affects: kernel-sru-workflow/prepare-package
Importance: Undecided
Assignee: Luis Henriques (henrix)
Status: In Progress
** Affects: kernel-sru-workflow/prepare-package-lbm
Assignee: Canonical Hardware Certification (canonical-hw-cert)
Status: New
** Affects: kernel-sru-workflow/prepare-package
Importance: Undecided
Assignee: Luis Henriques (henrix)
Status: In Progress
** Affects: kernel-sru-workflow/prepare-package-lbm
Importance
** Affects: kernel-sru-workflow/certification-testing
Importance: Undecided
Assignee: Canonical Hardware Certification (canonical-hw-cert)
Status: Invalid
** Affects: kernel-sru-workflow/prepare-package
Importance: Undecided
Assignee: Luis Henriques (henrix)
Status
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New = In Progress
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) = Luis Henriques
(henrix)
--
You received this bug notification because you are a member
** Changed in: kernel-sru-workflow/prepare-package-lrm
Status: New = In Progress
** Changed in: kernel-sru-workflow/prepare-package-lrm
Assignee: Canonical Kernel Team (canonical-kernel-team) = Luis Henriques
(henrix)
** Changed in: kernel-sru-workflow/prepare-package-lum
Assignee: Canonical Hardware Certification (canonical-hw-cert)
Status: New
** Affects: kernel-sru-workflow/prepare-package
Importance: Undecided
Assignee: Luis Henriques (henrix)
Status: In Progress
** Affects: kernel-sru-workflow/prepare-package-lbm
Hi Chris,
I'm sorry -- I've done a clean-up on my home and accidentally deleted
the kernel. I'll build another one and post a new link here. Thanks for
you help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sorry for the delay (again...)
What you described in your last comments makes me think this is not a kernel
issue, but some issue in your initrd. And you're photo in comment #33 actually
points this way: the first line points to an issue on the init script.
Could you please attach your init
Chris, I've uploaded a kernel into:
http://people.canonical.com/~henrix/lp1010281/
This test kernel contains the patch referred above in comment #2. If
this fixes your issue, it would be great if you could attach to the bug
report:
- The output of the command 'usb-devices' (you can run it on
Thanks. Still nothing there... your script seems to be sane. Would you
mind trying to boot again the kernel in comment #33 (kernel v3, I
believe) but removing the arguments 'quiet' and 'splash'? Maybe the
output contains some more hints...
--
You received this bug notification because you are
** Changed in: kernel-sru-workflow/prepare-package
Status: New = In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team (canonical-kernel-team) = Luis Henriques
(henrix)
--
You received this bug notification because you are a member of Ubuntu
Assignee: Canonical Hardware Certification (canonical-hw-cert)
Status: Invalid
** Affects: kernel-sru-workflow/prepare-package
Importance: Undecided
Assignee: Luis Henriques (henrix)
Status: In Progress
** Affects: kernel-sru-workflow/prepare-package-lbm
Hi Hossein,
Sorry for taking so long coming back to you. I was able to reproduce
this issue (got a laptop with similar wireless card), and I believe I
found the commit that fixes it:
2655e314c4b204966008689eaf3e87ba1f38d55c iwlwifi: trace debug messages
Aparentely, the issue is caused by an
** Changed in: linux (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1035889
Title:
iwlwifi causes total system freeze on certain WiFi speeds
To manage
Public bug reported:
This bug is for tracking the 2.6.38-16.67 upload package. This bug will
contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
101 - 200 of 3244 matches
Mail list logo
