-33 from proposed does boot.
However, while installing that I noticed that the dpkg status on my -32 was
listed as iF (probably from a previous full disk?)
When it installed -33 it regenerated the initramfs for -32 as well and -32 now
works.
Marked invalid.
** Changed in: linux (Ubuntu)
** Attachment added: "screenshot of boot oops"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787807/+attachment/5177502/+files/bootoops-32.jpg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launch
Public bug reported:
4.15.0-32 is failing to boot on this core2 laptop, 4.15.0-30 (and
earlier) is fine.
(I'll attach the screenshot of the panic in a second)
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-30-generic 4.15.0-30.32
ProcVersionSignature: Ubuntu 4.15.0-30.3
the 4.2.0 initrd's are pretty sparse, the recent ones seem to have a
full set of modules and firmware (e.g. 18MB of drivers/net)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1692208
Titl
Public bug reported:
My initrd in recent kernels is 4x larger than in slightly older kernels,
making /boot just large enough. It seems unlikely this growth is
intended:
-rw-r--r-- 1 root root 44052519 May 13 12:29 initrd.img-4.10.0-19-generic
-rw-r--r-- 1 root root 44050984 May 13 12:28 initrd.i
Public bug reported:
Full backtrace below.
Not seen this one before (machine has been running fine for many years),
so I guess it's Zesty kernel issue. Hit it while running a heavily busy
Firefox.
Apr 2 17:52:16 davros kernel: [17739.294897] [ cut here
]
Apr 2 17:52:
I can confirm this is fixed in 4.4.0-4, except that is by the
WARN_ON(!connector_state->crtc) warn/backtrace.
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
No, not needed on earlier than xenial (utopic worked fine) - someone
should probably look at the oops though that backtrace that I still see
in the logs - but it's only a low, since everything apparently works.
--
You received this bug notification because you are a member of Kernel
Packages, whi
The 4.4.0-999-generic daily (201512120150) seems to work.
Although there's a whole bunch of slowpath warnings in the logs.
(I say seems to work - I'm running it now in KDE apparently OK; on the first
boot the desktop didn't complete starting up but ti wasn't obvious why, X was
still responsive ju
Public bug reported:
This laptop works with 4.2.0-19 and fails with 4.3.0-2.
At boot (before X) the display is corrupt - with the entire screen
shifted halfway across the screen with the kernel boot text mostly
readable, just shifted over (and some crud at the top). X doesn't
start. Returning t
Critical: It wont boot any more, and it's a regression on LTS.
** Changed in: linux (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1450504
Ti
There's a report of this panicing (looks audit related):
See
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450504
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1444141
Title:
Joseph: Thanks for that kernel build, I can confirm that fixes it.
Linux davros 3.19.0-10-generic #10~lp1432405v1 SMP Mon Mar 23 18:54:51
UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubu
Marked as triaged; see upstream bug report; the backtrace and error is the same
and the time of the report is about right.
It looks like we need.
drm/i915: Push vblank enable/disable past encoder->enable/disable
** Bug watch added: freedesktop.org Bugzilla #89108
https://bugs.freedesktop.o
4.0-rc4-vivid works fine
** Tags added: kernel-fixed-upstream
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1432405
Title:
[Toshiba Equium A100-306] WARNING: CPU: 0 PID: 968 at
/buil
To answer the 1st part of the question; 3.16.0-28 from Utopic worked
fine (indeed the machine has been running Ubuntu for over 5 years
upgrading all the way and hasn't hit this). I'll try latest upstream.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Public bug reported:
Noticed during boot of vivid after upgrade:
[ 54.762967] [ cut here ]
[ 54.763009] WARNING: CPU: 1 PID: 968 at
/build/buildd/linux-3.19.0/drivers/gpu/drm/drm_irq.c:1121
drm_wait_one_vblank+0x170/0x180 [drm]()
[ 54.763012] vblank not available o
Joseph:
I'm seeing an identical backtrace on one of my dads machines after upgrade to
a recent kernel; it's intermittent perhaps 1/4 ish boots
3.13.0-32-generic, so I say not fixed:
Jul 22 17:58:13 thedr kernel: [ 16.146863] fb: conflicting fb hw usage
inteldrmfb vs VESA VGA - removing gene
roots: Pulse would have been issuing some ioctl or open on the sound
device that sohuld have worked but because the kernel driver of it was
screwed up that's what triggered the crash.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux i
it's a kernel panic; however nasty pulseaudio is to the kernel it shouldn't
panic.
Unfortunately looking at that picture I think it's actually a picture of
something graphics driver related but I'm not sure and it's not the first oops
** Package changed: pulseaudio (Ubuntu) => linux (Ubuntu)
--
Hi Shengliang,
I'm setting this as 'triaged' since you seem to have a grip on the problem.
I don't know much about the internals of atkbd; for review probably the best
thing is to mail upstream;
scripts/get_maintainer.pl -f drivers/input/keyboard/atkbd.c
says:
Dmitry Torokhov (maintainer:INP
Sehngliang: It sounds like you understand this bug - so should we set it
to 'triaged'? Do you believe your patch is safe for other machines?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1
So while I know very little about touchpads, the other bug seemed to be asking
for some chunks of data; so
if all of you who are affected could post (as one comment):
1) The exact model of laptop
2) dmesg | egrep -i 'psmouse|input|elan|synapt'
3) xinput list
4) Then using the id from t
Jochen: Please open a separate bug for your Acer; this one mostly seems
to be pretty specific to this hardware.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1093217
Title:
8086:0166 [L
Triaged: Points to upstream fixes
Low: Timeouts after annoying but not geological time.
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Kernel
Packag
Hi,
You don't say what happens when your computer doesn't boot:
- please describe at what stage it stops - what's visible on the screen?
- does it work if you boot it in recovery mode?
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug not
Setting to medium as per the related bug.
Lets collect the log files and see where we go.
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launc
lightweight/nocobrainless: Hmm given that the fix in this bug fixes
something for some group of people, but you're still having issues,
please open separate bugs for them.
Add a comment here with the new bug number, and in your new bug add a
comment saying you think it might be related to this one
I'd like to suggest something;
It should be possible to build a ppa'd kernel with just that change
reverted, then that kernel could be used to see if other apparently similar
bugs (like bug 1243904) are actually the same issue without other users having
to do the same bisect (especially if th
Joonas: Thanks for doing that, technically by the ubuntu lp rules we
should have a separate bug for your separate failure on different
hardware - but I agree it's probably the same problem, so create the bug
anyway, and add a comment giving this bug number, and also add a comment
here giving the bu
I don't recall ever seeing an ISO respin.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1241871
Title:
8086:0166 [ASUS ZENBOOK UX32VD] 13.10 kernels (3.11.x) Fail to light
Status in Th
This has 'gone away' on trusty but not saucy; I think it's the X server update,
but can't be sure.
Looking at the debug I sent upstream I'm wondering if the problem is the X
server stopping the VT change happening
as the 1st problem, and then things going down hill from there.
--
You received t
Nougieryann: if this fix has fixed it then no, you don't need to submit
a separate bug.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1241822
Title:
RAID 5 not available after upgrade f
Also fails in set I built from drm-next, so I've reported it upstream in
the spice/qxl bug tracker and added the link here
** Bug watch added: freedesktop.org Bugzilla #71365
https://bugs.freedesktop.org/show_bug.cgi?id=71365
** Also affects: linux via
https://bugs.freedesktop.org/show_bug
Today's drm-next kernel also fails; linux-
headers-3.12.0-996_3.12.0-996.201311070425_all.deb
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1247906
Title:
Repeatable oops qxl_enc_commit
Linux trusty 3.12.0-1-generic #3-Ubuntu SMP Tue Oct 29 18:41:32 UTC 2013 x86_64
x86_64 x86_64 GNU/Linux
corrupted console on 1st c-a-f1, oops on c-a-f3 (even via grub menu)
Linux trusty 3.10.0-031000-generic #201306301935 SMP Sun Jun 30 23:36:16 UTC
2013 x86_64 x86_64 x86_64 GNU/Linux
got oo
Answer to 1st question 1st;
I've got this on both a saucy and a trusty guest, so not new in Trusty, but
Raring doesn't seem to exhibit it
Linux saucy 3.12.0-031200-generic #201311031935 SMP Mon Nov 4 00:36:54 UTC 2013
x86_64 x86_64 x86_64 GNU/Linux
still oopsing - slightly different backtrace a
Hi,
OK, I've flipped this to 'linux' - I think it's much more likely than it
being ibus.
You'll be asked to do some commands to report some more logs.
Set to importance High: Important device (internal keyboard) doesn't
work.
** Package changed: ibus (Ubuntu) => linux (Ubuntu)
** Changed in:
Public bug reported:
I've got an Ubuntu Trusty guest running under a Fedora 20-pre-beta, the
guest oops reliably.
To repeat:
Setup KVM with the guest configured with QXL graphics,
Install openssh-server in the guest
Boot it and then send a ctrl-alt-f1
Problem 1 : Corrupt graphics
Christopher:
Please carefully read the upstream bug that Gabriel has referenced, it
includes a fix that he references in #10
I don't see how this bug with a specified upstream fix is an 'unhelpful "catch
all"', given it's got an upstream fix I'd say it's pretty
close to triaged if Gabriel conf
Hi Gabriel,
I'm just putting this back to Confirmed/Medium.
Lets ignore your comment #13 - this bug isn't about other problems;
but can you confirm the current kernel-ppa fixes this bug.
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Sta
Hi Gabriel,
SO hopefully you should mainline builds pick this up in the kernel-ppa; it
would be good to know.
I don't think it's possible to fix the install ISO?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://
This isn't minicom's problem - most likely kernel (or possibly udev?)
** Package changed: minicom (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1243607
Title:
Siddu: Hmm your description on there seems to be different; my
understanding of the bug reported here was that it happened every/most
times during boot, your comment on the upstream bug talks about
occasional infinite loops - are we talking about the same bug here?
--
You received this bug notifi
13.10 still uses kernel 3.11
The upstream comment says they believe it's fixed in kernel 3.12-rc2, so can
some of you try the latest kernel by using the
instructions in comment #27 from Christopher.
--
You received this bug notification because you are a member of Kernel
Packages, which is subs
Nouguieryann: Can you please submit a separate bug which will capture
your logs, put a comment on it mentioning this bug number, and put a
comment on here mentioning the new bug number you get.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
High: A problem with an essential hardware component / Has a severe
impact on a small portion of Ubuntu users
this looks the same as bug 102973 which is duped to bug 220493 but I'm
not entirely sure it's the same.
** Changed in: linux (Ubuntu)
Importance: Undecided => High
--
You received th
I can see in the new kernels there is a config called CONFIG_MD_RAID456
- is this a case tha t the 6 got added somewhere?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1241822
Title:
RA
Gabriel: Can you give us log files from your system, if you can't do it
with current then go with the previous working version and include at
least a dmesg and /var/log/Xorg.0.log so at least we have something to
reference and please state full details of the hardware you see htis on.
--
You rec
David: Please run
sudo dbus-monitor --system
in a shell on the machine in the live environment and paste the output when you
insert a cd.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/65
David Balažic :
Can you just confirm the latest stuff you tried - does this bug happen on an
installed system?
Alberto: IMHO this isn't a hundredpapercut job unless it can be nailed
down more as to how to repeat it
--
You received this bug notification because you are a member of Kernel
Packa
OK, let me ask:
1) What makes people think it's a kernel bug? The kernel is detecting the CD
drives in the bootdmesg, and if I read the bug correctly it mounts them if told
to.
2) Does this issue happen in an installed system; i.e. if you install (I think
you could probably install to a thumb
Triaged: Just a config change and reporter states what they want, seems
reasonable if it works
Low: It's just something new, not apparently a regression
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
--
You receiv
Hi TJ,
Could you file a separate bug on this (so that we can catch all your hardware
info etc) and add a comment here stating the bug number.
Thanks, Dave
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.la
TJ: Plus can you confirm where you got that kernel from - the current
version on my just-updated saucy box is 3.11.0-8
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1205827
Title:
Regre
Well, the question is, is it still there; on Saucy (3.11.0-4-generic #9):
# grep -i taint /var/log/kern.log
Aug 26 11:34:52 major vmunix: [0.903410] crc_itu_t: module verification
failed: signature and/or required key missing - tainting kernel
Aug 27 11:55:01 major vmunix: [0.903210] crc_i
Works in 3.11.0-2generic #5
** Changed in: linux (Ubuntu Saucy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1205827
Title:
Regression: US
All good - thanks!
Linux major 3.11.0-2-generic #5-Ubuntu SMP Mon Aug 12 16:09:51 UTC 2013
x86_64 x86_64 x86_64 GNU/Linux
Dave
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1205827
Titl
Tim: This still affects 3.11.0-1-generic (3.11.0-1.4)
Put back to triaged.
** Changed in: linux (Ubuntu Saucy)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.
Thank you Emil; that seems to do the trick!
I built a modified 3.11 from the daily with that in and it seems to work.
Dave
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1205827
Title:
Logs not needed; this is observation from source tree; (on both 3.10.0-6
and current dailies)
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bu
Public bug reported:
I was doing a kernel config and noticed there are a bunch of ARM/non-x86
only drivers being built on x86 - they're just increasing build time and
taking up space in /lib/modules; spotted so far:
- Exynos random number generator:
./kernel/drivers/char/hw_random/exynos-rng.
Tested upstream Linux major 3.11.0-999-generic #201308030433
bug still exists.
(Removed needs-upstream and set to triaged)
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to l
>From your logs; this looks relevant to an unhappy bluetooth adapter:
[ 8521.365815] WARNING: at /build/buildd/linux-3.8.0/fs/sysfs/dir.c:536
sysfs_add_one+0xd4/0x100()
[ 8521.365820] Hardware name: MM061
[ 8521.365823] sysfs: cannot create duplicate filename
'/devices
Public bug reported:
A Kingston 16GB DataTraveler G2 stick is timing out on 3.10.06-generic #17
If I reboot back to 3.10.04-generic #13 this works
It also works in another machine running OpenSLES
[2.687510] scsi 8:0:0:0: Direct-Access Kingston DataTraveler G2 1.00
PQ: 0 ANSI: 2
[2.
OK, so can you just confirm exactly which version you tested that worked;
ideally if you can add
the tag explaining this as per:
https://wiki.ubuntu.com/Kernel/BugTriage/Responses#Please_Test_Latest_Upstream
Dave
--
You received this bug notification because you are a member of Kernel
Packages,
Hi,
I know there are lots of EFI fixes that are going in for people; so what's
the newest kernel you've tried; I'd try the newest
thing that you can; try the instructions at:
https://wiki.ubuntu.com/Kernel/BugTriage/Responses#Please_Test_Latest_Upstream
to get the latest.
Dave
--
You received
67 matches
Mail list logo
