Package: kfreebsd-image-9.1-1-amd64
Version: 9.1-3
Severity: important
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
After upgrading a headless wheezy to jessie and after the reboot attaching
a USB keyboard.
* Wha
Hi!
On Mon, 2013-07-29 at 07:45:30 +0200, Petr Salinger wrote:
> Ideally whole set [1] of 9.1 based packages should migrate into
> testing before upload of a corresponding 9.2 package into sid.
> Especially lag of ufsutils (still 8.2) worries me.
I was planning on working on ufsutils, and I can d
2013/7/29 Steven Chamberlain :
> Some code appears to have
> possibly hardcoded a value of 100. And even NetBSD seems to have
> chosen that value. So I think we should simply change GNU/kFreeBSD to
> use 100 in the kernel.
>
> I don't foresee any breakage from such a change. This is only relevan
2013/7/29 Lars Lansink :
>* What led up to the situation?
> After upgrading a headless wheezy to jessie and after the reboot
> attaching a USB keyboard.
>* What exactly did you do (or not do) that was effective (or
> ineffective)?
> Powered down the system, attached keyboard
Control: severity -1 grave
I think a panic during a fairly typical usecase like this deserves
severity 'grave'; we would not want 9.1 to migrate to testing if this
bug could hurt more users.
Lars, please try to show us a stack trace of the panic if possible.
Even a photograph of it on-screen may
Processing control commands:
> severity -1 grave
Bug #718250 [kfreebsd-image-9.1-1-amd64] kfreebsd-image-9.1-1-amd64: attaching
USB keyboard makes system reboot
Severity set to 'grave' from 'important'
--
718250: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718250
Debian Bug Tracking System
Hi all!
Steven Chamberlain writes:
> I think a panic during a fairly typical usecase like this deserves
> severity 'grave'; we would not want 9.1 to migrate to testing if this
> bug could hurt more users.
>
> Lars, please try to show us a stack trace of the panic if possible.
> Even a photograph
Hi!
On 29/07/13 19:00, Christoph Egger wrote:
> [...] IIRC it happens to me both, on the 9.1 and the
> 10 kernel but only recently.
It could be due to GCC-4.8 and/or use of -O2 compiler optimisations,
which were enabled only in the most recent upload of each.
> Any other suggestions on how one w
[...] IIRC it happens to me both, on the 9.1 and the
10 kernel but only recently.
It could be due to GCC-4.8 and/or use of -O2 compiler optimisations,
which were enabled only in the most recent upload of each.
Perfect guess!
I have been able to confirm crash also on my PC,
usually with only P
On 29/07/13 20:38, Petr Salinger wrote:
> Please do upload from just created glibc-bsd/kfreebsd-9.1/
> The fix
> http://security.FreeBSD.org/patches/SA-13:08/nfsserver.patch
> for kfreebsd-9: CVE-2013-4851: nfsserver applies wrong credentials
> is not yet included.
Meanwhile I have added that t
2013/7/29 Steven Chamberlain :
> Meanwhile I have added that to the new trunk/kfreebsd-9.1/
>
> Robert: I think we're ready for an upload of this to stable. We can
> try to tackle GCC issues another time, even after this has migrated.
Ack. I was already running dput when you guys fixed this. Oh
2013/7/29 Robert Millan :
> 2013/7/29 Steven Chamberlain :
>> Meanwhile I have added that to the new trunk/kfreebsd-9.1/
>>
>> Robert: I think we're ready for an upload of this to stable. We can
>> try to tackle GCC issues another time, even after this has migrated.
>
> Ack. I was already runnin
On 07/09/12 17:29, Moritz Muehlenhoff wrote:
> What about keeping autoconfig enabled and documenting the potential danger in
> README.Debian (or somewhere similar), so that anyone concerned can disable
> it locally?
It looks like we have a bigger problem than this:
I was going to simply write in
On 29/07/13 22:40, Steven Chamberlain wrote:
> # ifconfig xn0 ifdisabled
> ifconfig: ioctl(SIOCGIFINFO_IN6): Invalid argument
> # ifconfig xn0 -accept_rtadv
> ifconfig: ioctl(SIOCGIFINFO_IN6): Invalid argument
Argh, that needs to be:
# ifconfig xn0 inet6 ifdisabled
# ifconfig xn0 inet6 -accept_rt
Your message dated Tue, 30 Jul 2013 00:04:12 +
with message-id
and subject line Bug#717958: fixed in kfreebsd-9 9.1-4
has caused the Debian Bug report #717958,
regarding kfreebsd-9: CVE-2013-4851: nfsserver applies wrong credentials
to be marked as done.
This means that you claim that the pro
Your message dated Tue, 30 Jul 2013 00:04:12 +
with message-id
and subject line Bug#718250: fixed in kfreebsd-9 9.1-4
has caused the Debian Bug report #718250,
regarding kfreebsd-image-9.1-1-amd64: attaching USB keyboard makes system reboot
to be marked as done.
This means that you claim that
kfreebsd-9_9.1-4_kfreebsd-amd64.changes uploaded successfully to localhost
along with the files:
kfreebsd-9_9.1-4.dsc
kfreebsd-9_9.1-4.debian.tar.gz
kfreebsd-source-9.1_9.1-4_all.deb
kfreebsd-headers-9.1-1_9.1-4_kfreebsd-amd64.deb
kfreebsd-image-9.1-1-amd64_9.1-4_kfreebsd-amd64.deb
kfre
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Mon, 29 Jul 2013 23:38:05 +0200
Source: kfreebsd-9
Binary: kfreebsd-source-9.1 kfreebsd-headers-9.1-1 kfreebsd-image-9.1-1-686-smp
kfreebsd-image-9-686-smp kfreebsd-headers-9.1-1-686-smp
kfreebsd-headers-9-686-smp kfree
On 29/07/13 13:30, Steven Chamberlain wrote:
> Probably we just need to add some text explaining CVE-2012-5365,
> CVE-2012-5363 and CVE-2011-2393, and that would be good enough to call
> them all 'fixed in wheezy'. We'd need to send a final debdiff
> containing all this. I'll try and draft someth
I performed yet another "USB plug test", this time on 9.2 kernel.
"gcc-4.8 -O2" compiled kernel (aka 9.2~svn253470-1 in experimental)
crashes too.
"gcc-4.8 -O1" compiled kernel survives.
I will update SVN for 9.2 and 10 kernels to use "gcc-4.8 -O1".
IMO, the 9.1 should stay at "gcc-4.6 -O1", a
20 matches
Mail list logo
