found 894375 4.16.5-1
thanks
Just an update on this bug: it is still showing in the 4.16 series.
Best wishes,
Julian
On Thu, Mar 29, 2018 at 03:22:00PM +0100, Julian Gilbey wrote:
> Package: src:linux
> Version: 4.15.11-1
> Severity: normal
>
> Hello!
>
> Since upgra
Package: src:linux
Version: 4.15.11-1
Severity: normal
Hello!
Since upgrading my Debian kernel from 4.14.17-1 to 4.15.11-1
yesterday, my computer has started regularly beeping. Checking the
syslog, I see loads of entries reading:
Mar 29 00:08:14 erdos kernel: [57598.530605] do_IRQ: 0.36 No irq
Package: firmware-brcm80211
Version: 0.44
Very similar problem to bug #797779: I was unable to load the
brcmfmac43603-pcie.bin firmware sadly needed to use the wireless card
on a new MacBook Pro.
I downloaded the file from the github site, along with the .ap.bin
file (whatever that is), installed
[Resending cc'ing bug report]
On Sun, Dec 28, 2014 at 02:32:38PM +0100, Ben Hutchings wrote:
> > Hi!
> >
> > I don't know how to track down this bug, but I'm happy to help do so.
> > Also, if this is related to network-manager and not the kernel, please
> > feel free to reassign.
> >
> > I am us
Package: src:linux
Version: 3.16.5-1
Severity: normal
Hi!
I don't know how to track down this bug, but I'm happy to help do so.
Also, if this is related to network-manager and not the kernel, please
feel free to reassign.
I am using a MacBook Pro running Debian testing.
I have noticed that when
Package: nfs-common
Version: 1:1.2.8-5
Severity: minor
Tags: patch
During installation, dpkg says:
Setting up nfs-common (1:1.2.8-5) ...
Installing new version of config file /etc/init.d/nfs-common ...
Replacing config file /etc/idmapd.conf with new version
update-rc.d: warning: start and stop ac
reopen 681280
thanks
Oh dear. Even with a patched kernel, it's started doing the same
thing again. So even though this seemed to help, it's not actually
fully fixed the problem :-/
It certainly seems to be the case, though, that this problem only
appears when the computer is powered by battery;
On Tue, Oct 30, 2012 at 10:46:29AM +0100, Uwe Kleine-König wrote:
> > -eval "set -- $(getopt -n "$0" -- "f:j:s:" "$@")"
> > +if [ -z "${DEBIAN_KERNEL_DISABLE_DEBUG+set}" ]; then
> I don't know that construct, only :+, but + seems to do the same without
> me finding it in the manpage of neither bash
On Mon, Oct 29, 2012 at 11:49:37PM -0700, Jonathan Nieder wrote:
> Sounds sane. How about something like this?
Nice; one tiny suggestion:
> Index: debian/bin/test-patches
> ===
> --- debian/bin/test-patches (révision 19472)
> +++
On Wed, Oct 24, 2012 at 11:27:51PM +0100, Julian Gilbey wrote:
> > The only interesting recent sky2 patch I can find upstream is
> > v3.6-rc1~125^2~264 (sky2: Fix for interrupt handler, 2012-07-03). How
> > does a kernel with that patch applied behave?
> >
> > A
On Sat, Oct 20, 2012 at 10:50:02PM -0700, Jonathan Nieder wrote:
> Jonathan Nieder wrote:
> > Julian Gilbey wrote [regarding sky2 tx stalls]:
>
> >> I think this may be a hardware fault: I have now identified what
> >> appears to be the physical situation
On Wed, Oct 24, 2012 at 10:42:53PM +0100, Julian Gilbey wrote:
> On Sat, Oct 20, 2012 at 10:50:02PM -0700, Jonathan Nieder wrote:
> > The only interesting recent sky2 patch I can find upstream is
> > v3.6-rc1~125^2~264 (sky2: Fix for interrupt handler, 2012-07-03). How
> > do
On Sat, Oct 20, 2012 at 10:50:02PM -0700, Jonathan Nieder wrote:
> The only interesting recent sky2 patch I can find upstream is
> v3.6-rc1~125^2~264 (sky2: Fix for interrupt handler, 2012-07-03). How
> does a kernel with that patch applied behave?
>
> A 3.6.y kernel should be hitting experimenta
On Tue, Jul 17, 2012 at 08:12:10AM +0100, Julian Gilbey wrote:
> On Wed, Jul 11, 2012 at 11:16:39PM +0100, Julian Gilbey wrote:
> > I've had numerous occasions in at least the last month (from kernel
> > 3.2.19-1 or earlier - that's as far back as my logs go) when my
>
On Sun, Sep 16, 2012 at 01:33:08AM +0100, Ben Hutchings wrote:
> On Fri, 2012-09-14 at 18:48 +0100, Julian Gilbey wrote:
> > Package: src:linux
> > Version: 3.2.23-1
> > Severity: normal
> >
> > I've had four oopses today when trying to connect to an eth
On Wed, Jul 11, 2012 at 11:16:39PM +0100, Julian Gilbey wrote:
> I've had numerous occasions in at least the last month (from kernel
> 3.2.19-1 or earlier - that's as far back as my logs go) when my
> machine has given a kernel error when trying to connect to a
> Window
On Wed, Jul 11, 2012 at 11:16:39PM +0100, Julian Gilbey wrote:
> I've had numerous occasions in at least the last month (from kernel
> 3.2.19-1 or earlier - that's as far back as my logs go) when my
> machine has given a kernel error when trying to connect to a
> Window
On Sun, Aug 28, 2011 at 06:31:58PM -0500, Jonathan Nieder wrote:
> forcemerge 631187 636103
> tags 631187 + upstream
> quit
>
> Hi Julian,
>
> Julian Gilbey wrote:
>
> > ata2.00: detaching (SCSI 1:0:0:0)
> > BUG: unable to handle kernel NULL pointer de
Package: linux-image-2.6.32-trunk-amd64
Version: 2.6.32-5
Every time I boot - and I'm using crypto file systems - I get the
series of messages (copied from bootlog):
Starting early crypto disks...sda2_crypt (starting)...
Unlocking the disk /dev/sda2 (sda2_crypt)
Enter passphrase:
modprobe: FATAL
On Fri, Aug 21, 2009 at 09:42:05AM +0200, Bastian Blank wrote:
> severity 534867 wishlist
> tags 534867 wontfix
> thanks
>
> On Fri, Aug 21, 2009 at 01:52:35AM +0100, Julian Gilbey wrote:
> > > I've reopened this bug because I've just been stung by it myself.
reopen 534867
thanks
> I've reopened this bug because I've just been stung by it myself. The
> issue seems to be not so much that the package I'm trying to build
> (nvidia graphics module, see http://bugs.debian.org/510961) is using
> references to linux/* rather than asm/*, but rather that it do
According to Manoj in the logs to bug#394661, which was blocking this
bug and has since been closed, the bug was fixed in kernel-package
10.063. So I guess that all that is needed is a rebuild of the
kernels with a Build-Depends on a sufficiently recent kernel-package.
Julian
--
To UNSUBSCR
Package: linux-image-2.6.18-1-k7
Version: 2.6.18-3
Severity: serious
When configuring this kernel, I observed the following:
Running depmod.
Finding valid ramdisk creators.
Using mkinitrd.yaird to build the ramdisk.
Missing Required paramater 'Old' at
/var/lib/dpkg/info/linux-image-2.6.18-1-k7.p
23 matches
Mail list logo
