Hurrah, I was able to get the output from a trace when the problem
described below occurs.
db> trace
Debugger(c0357efe,4,1,0,1) at Debugger+0x54
scgetc(c03c8400,2,b45afa2e,16166842,c25a6180) at scgetc+0x445
sckbdevent(c03a31e0,0,c03c8400,d1d51ccc,4e) at sckbdevent+0x1e0
atkbd_intr(c03a31e
* Nate Lawson <[EMAIL PROTECTED]> [20030109 21:34]: wrote:
> On Sat, 4 Jan 2003, Trent Nelson wrote:
> > On Fri, Jan 03, 2003 at 11:16:57AM -0800, Nate Lawson wrote:
> > > Sounds like an atkbd or syscons problem.
> > > Did you suspend the laptop and resume before this happens?
> >
> > No. How
On Fri, 10 Jan 2003, Odhiambo Washington wrote:
> When is this "unset acpi_load" done? I can provide the info rqd.
At the "booting in 10 seconds" prompt. Hit space and type it in.
-Nate
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the messag
* Nate Lawson <[EMAIL PROTECTED]> [20030109 21:34]: wrote:
> On Sat, 4 Jan 2003, Trent Nelson wrote:
> > On Fri, Jan 03, 2003 at 11:16:57AM -0800, Nate Lawson wrote:
> > > Sounds like an atkbd or syscons problem.
> > > Did you suspend the laptop and resume before this happens?
> >
> > No. How
On Sat, 4 Jan 2003, Trent Nelson wrote:
> On Fri, Jan 03, 2003 at 11:16:57AM -0800, Nate Lawson wrote:
> > Sounds like an atkbd or syscons problem.
> > Did you suspend the laptop and resume before this happens?
>
> No. However, it happened to me today shorty after I issued a sysctl
> -w h
Hi all,
On Sat, 4 Jan 2003 17:55:25 +
Trent Nelson <[EMAIL PROTECTED]> wrote:
> No. However, it happened to me today shorty after I issued a sysctl
> -w hw.acpi.cpu.economy_speed=8. (Why does it default to 4 anyway?)
It reminded me of my tiny local patch.
--- src/sys/dev/acpica/acp
On Fri, Jan 03, 2003 at 11:16:57AM -0800, Nate Lawson wrote:
> Sounds like an atkbd or syscons problem.
> Did you suspend the laptop and resume before this happens?
No. However, it happened to me today shorty after I issued a sysctl
-w hw.acpi.cpu.economy_speed=8. (Why does it default
On Fri, 3 Jan 2003, Trent Nelson wrote:
> I've experienced -current lock up in exactly the same way twice now;
> once with 5.0-RC2, and just now, with sources from 30th December.
>
> The system in question is a Sharp PC-AR50 laptop. In both instances
> the system was idle and
I've experienced -current lock up in exactly the same way twice now;
once with 5.0-RC2, and just now, with sources from 30th December.
The system in question is a Sharp PC-AR50 laptop. In both instances
the system was idle and I was editing a file in vim on ttyv0. Both
