I can confirm that it works on my system now.
On Jul 29, 2013 11:34 PM, "Robert Millan" wrote:
> 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 issue
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
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
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
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
[...] 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
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
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
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
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
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
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
12 matches
Mail list logo
