On 11/15/14, Dominik Zajac wrote:
> Hi,
>
> I am trying to change the default keymap for my keyboard therefore I
> added the following options to my kernel configuration which leads to
> the error bellow.
>
> Added options:
>
> options KBD_INSTALL_CDEV
>
> options UKBD_DFLT_KEYMAP
>
>
On Sat, Nov 15, 2014 at 09:44:18PM -0800, Adrian Chadd wrote:
> On 15 November 2014 21:41, Steve Kargl
> wrote:
> > On Thu, Nov 13, 2014 at 01:22:06PM -0800, Steve Kargl wrote:
> >> On Thu, Nov 13, 2014 at 09:34:07PM +0100, Hans Petter Selasky wrote:
> >> > On 11/13/14 19:15, Steve Kargl wrote:
>
In init(8), one finds under DIAGNOSISTICS
"some processes would not die; ps axl advised."
So, just how is one to actually run 'ps axl advised' as
the message appears as init(8) is killing off the system?
--
Steve
___
freebsd-current@freebsd.org mai
> On 16 Nov 2014, at 17:51, Steve Kargl
> wrote:
>
> Is there a 'random: device_detach():' missing between the 'umass0'
> and 'da0' messages in the last 4 lines.
No. At attach time, the RNG grabs some probe entropy. At detach time it does
nothing.
M
--
Mark R V Murray
_
On Sun, 2014-11-16 at 18:17 +, Mark R V Murray wrote:
> > On 16 Nov 2014, at 17:51, Steve Kargl
> > wrote:
> >
> > Is there a 'random: device_detach():' missing between the 'umass0'
> > and 'da0' messages in the last 4 lines.
>
> No. At attach time, the RNG grabs some probe entropy. At deta
On 2014-11-16 13:07, Steve Kargl wrote:
> In init(8), one finds under DIAGNOSISTICS
>
>"some processes would not die; ps axl advised."
>
> So, just how is one to actually run 'ps axl advised' as
> the message appears as init(8) is killing off the system?
>
In this case 'advised' is not a li
> On 16 Nov 2014, at 18:21, Ian Lepore wrote:
>
> On Sun, 2014-11-16 at 18:17 +, Mark R V Murray wrote:
>>> On 16 Nov 2014, at 17:51, Steve Kargl
>>> wrote:
>>>
>>> Is there a 'random: device_detach():' missing between the 'umass0'
>>> and 'da0' messages in the last 4 lines.
>>
>> No. At
On Sun, 2014-11-16 at 18:23 +, Mark R V Murray wrote:
> > On 16 Nov 2014, at 18:21, Ian Lepore wrote:
> >
> > On Sun, 2014-11-16 at 18:17 +, Mark R V Murray wrote:
> >>> On 16 Nov 2014, at 17:51, Steve Kargl
> >>> wrote:
> >>>
> >>> Is there a 'random: device_detach():' missing between
> On 16 Nov 2014, at 18:31, Ian Lepore wrote:
>
> The point I'm trying to make here is that you trimmed away the important
> part of the prior messages and replied only to the part where Steve's
> debugging efforts were somewhat speculating. The non-speculative part
> was where he bisected the
On Sun, Nov 16, 2014 at 01:23:00PM -0500, Allan Jude wrote:
> On 2014-11-16 13:07, Steve Kargl wrote:
> > In init(8), one finds under DIAGNOSISTICS
> >
> >"some processes would not die; ps axl advised."
> >
> > So, just how is one to actually run 'ps axl advised' as
> > the message appears as
On Sun, Nov 16, 2014 at 06:34:42PM +, Mark R V Murray wrote:
>
> > On 16 Nov 2014, at 18:31, Ian Lepore wrote:
> >
> > The point I'm trying to make here is that you trimmed away the important
> > part of the prior messages and replied only to the part where Steve's
> > debugging efforts were
> On 16 Nov 2014, at 18:51, Steve Kargl
> wrote:
>
>>
>> I?m sorry my commit caused the problem.
>>
>
> Nothing to be sorry about. This is -current after all.
Thanks :-)
>> I?m also trying to find out why, but I don?t know enough about USB or
>> mass-storage devices to know why, so this m
On Sun, Nov 16, 2014 at 06:55:53PM +, Mark R V Murray wrote:
>
> > On 16 Nov 2014, at 18:51, Steve Kargl
> > wrote:
> >
> > If you have not read the entire thread, once the laptop keyboard and
> > video output lock up, I can ssh into the laptop. If I run usbconfig,
> > it hangs, ^T tells m
On 11/16/14 20:03, Steve Kargl wrote:
On Sun, Nov 16, 2014 at 06:55:53PM +, Mark R V Murray wrote:
On 16 Nov 2014, at 18:51, Steve Kargl wrote:
If you have not read the entire thread, once the laptop keyboard and
video output lock up, I can ssh into the laptop. If I run usbconfig,
it ha
On Sun, Nov 16, 2014 at 08:16:36PM +0100, Hans Petter Selasky wrote:
> On 11/16/14 20:03, Steve Kargl wrote:
> > On Sun, Nov 16, 2014 at 06:55:53PM +, Mark R V Murray wrote:
> >>
> >>> On 16 Nov 2014, at 18:51, Steve Kargl
> >>> wrote:
> >>>
> >>> If you have not read the entire thread, once
On 11/16/14 20:29, Steve Kargl wrote:
On Sun, Nov 16, 2014 at 08:16:36PM +0100, Hans Petter Selasky wrote:
On 11/16/14 20:03, Steve Kargl wrote:
On Sun, Nov 16, 2014 at 06:55:53PM +, Mark R V Murray wrote:
On 16 Nov 2014, at 18:51, Steve Kargl wrote:
If you have not read the entire thr
On Nov 16, 2014 10:07 AM, "Steve Kargl"
wrote:
>
> In init(8), one finds under DIAGNOSISTICS
>
>"some processes would not die; ps axl advised."
>
> So, just how is one to actually run 'ps axl advised' as
> the message appears as init(8) is killing off the system?
"shutdown now" will drop you
Its usually something like stalled IO
On 16/11/2014 18:07, Steve Kargl wrote:
In init(8), one finds under DIAGNOSISTICS
"some processes would not die; ps axl advised."
So, just how is one to actually run 'ps axl advised' as
the message appears as init(8) is killing off the system?
_
On Sun, Nov 16, 2014 at 11:41:03AM -0800, Freddie Cash wrote:
> On Nov 16, 2014 10:07 AM, "Steve Kargl"
> wrote:
> >
> > In init(8), one finds under DIAGNOSISTICS
> >
> >"some processes would not die; ps axl advised."
> >
> > So, just how is one to actually run 'ps axl advised' as
> > the mess
On Sun, Nov 16, 2014 at 12:37 PM, Steve Kargl <
s...@troutmask.apl.washington.edu> wrote:
> On Sun, Nov 16, 2014 at 01:23:00PM -0500, Allan Jude wrote:
> > On 2014-11-16 13:07, Steve Kargl wrote:
> > > In init(8), one finds under DIAGNOSISTICS
> > >
> > >"some processes would not die; ps axl a
... or since you can ssh into the thing, try as root:
procstat -ka
-adrian
On 16 November 2014 11:33, Hans Petter Selasky wrote:
> On 11/16/14 20:29, Steve Kargl wrote:
>>
>> On Sun, Nov 16, 2014 at 08:16:36PM +0100, Hans Petter Selasky wrote:
>>>
>>> On 11/16/14 20:03, Steve Kargl wrote:
>
On Sun, Nov 16, 2014 at 04:34:38PM -0800, Adrian Chadd wrote:
> ... or since you can ssh into the thing, try as root:
>
> procstat -ka
>
I'll try that tomorrow. But, I now know that this is
related to using hal from ports. If I comment out both
enable_dbus and enable_hal in /etc/rc.conf, the
On Sun, Nov 16, 2014 at 08:33:15PM +0100, Hans Petter Selasky wrote:
>
> thread apply all bt
>
> That will give you the backtrace of all threads. Grep for usbconfig, and
> figure out which line is causing the problem in the kernel. Then look at
> the USB explore threads and see where they are s
Steve Kargl writes:
> I'll try that tomorrow. But, I now know that this is related to using
> hal from ports. If I comment out both enable_dbus and enable_hal in
> /etc/rc.conf, the system works as I would expect (ie., usb now works
> for unplugging devices!). I further suspect that the problem
Dag-Erling Smørgrav writes:
> Steve Kargl writes:
> > I'll try that tomorrow. But, I now know that this is related to using
> > hal from ports. If I comment out both enable_dbus and enable_hal in
> > /etc/rc.conf, the system works as I would expect (ie., usb now works
> > for unplugging devices
25 matches
Mail list logo
