On 14/02/13(Thu) 16:22, Kent Fritz wrote:
This works for me. I just installed the latest snapshot, synced the
source, applied your patch, built and installed and it works just
fine.
Hate Gmail for patches, though.
Thanks. Hope I replied in time to make the 5.3 cut. :)
Yep, it's in
This works for me. I just installed the latest snapshot, synced the
source, applied your patch, built and installed and it works just
fine.
Hate Gmail for patches, though.
Thanks. Hope I replied in time to make the 5.3 cut. :)
Kent.
On Mon, Feb 11, 2013 at 2:34 AM, Martin Pieuchot
Hi Kent,
On 14/01/13(Mon) 10:05, Kent Fritz wrote:
On Fri, Jan 11, 2013 at 5:29 PM, Stefan Sperling s...@openbsd.org wrote:
I see. So this is happening during pms_probe() which runs before the
protocol is selected. Maybe fix it like this? I think the code should
cope with hardware that
On Fri, Jan 11, 2013 at 5:29 PM, Stefan Sperling s...@openbsd.org wrote:
I see. So this is happening during pms_probe() which runs before the
protocol is selected. Maybe fix it like this? I think the code should
cope with hardware that returns unrecognizable garbage. But I don't
know very much
On 10/01/13(Thu) 14:08, Kent Fritz wrote:
On Thu, Jan 10, 2013 at 9:26 AM, Stefan Sperling s...@openbsd.org wrote:
Can you please try to find out which protocol probe routine is
responsible for hanging the machine?
None of them. I tried as you suggested, then just #if'd out every
entry
On Fri, Jan 11, 2013 at 01:16:53PM +0100, Martin Pieuchot wrote:
On 10/01/13(Thu) 14:08, Kent Fritz wrote:
On Thu, Jan 10, 2013 at 9:26 AM, Stefan Sperling s...@openbsd.org wrote:
Can you please try to find out which protocol probe routine is
responsible for hanging the machine?
None
I dug a little deeper, and defined PCKBCDEBUG in
/usr/src/sys/dev/ic/pckbc.c, and it spews:
pckbc_cmd: lost 0xfc
Looking at pckbc_poll_cmd1, it looks like there's an infinite loop if
it doesn't get back a response it expects. What's best: specifically
handling 0xfc, or erroring out on any
On Fri, Jan 11, 2013 at 04:44:07PM -0800, Kent Fritz wrote:
I dug a little deeper, and defined PCKBCDEBUG in
/usr/src/sys/dev/ic/pckbc.c, and it spews:
pckbc_cmd: lost 0xfc
Looking at pckbc_poll_cmd1, it looks like there's an infinite loop if
it doesn't get back a response it expects.
On Wed, Jan 9, 2013 at 5:34 PM, Stefan Sperling s...@openbsd.org wrote:
Shot in the dark: Does it not hang if you disable the pms driver
via boot -c? See the boot_config(8) man page.
The RAMDISK_CD kernel doesn't have pms compiled in, and it might be
the next thing pckbd0 is trying to
On Thu, Jan 10, 2013 at 08:56:15AM -0800, Kent Fritz wrote:
On Wed, Jan 9, 2013 at 5:34 PM, Stefan Sperling s...@openbsd.org wrote:
Shot in the dark: Does it not hang if you disable the pms driver
via boot -c? See the boot_config(8) man page.
The RAMDISK_CD kernel doesn't have pms
On Thu, Jan 10, 2013 at 9:26 AM, Stefan Sperling s...@openbsd.org wrote:
Can you please try to find out which protocol probe routine is
responsible for hanging the machine?
None of them. I tried as you suggested, then just #if'd out every
entry in that structure. No change in behavior.
Install works fine, but consistently stops after printing:
wskbd0 at pckbd0: console keyboard, using wsdisplay0
Same behavior for 5.2 release, current, amd64 and i386, and another
model nT-i2847. Any hints where to poke next?
dmesg from booting bsd.rd follows. Thanks.
Kent
OpenBSD
On Wed, Jan 09, 2013 at 04:30:21PM -0800, Kent Fritz wrote:
Install works fine, but consistently stops after printing:
wskbd0 at pckbd0: console keyboard, using wsdisplay0
Same behavior for 5.2 release, current, amd64 and i386, and another
model nT-i2847. Any hints where to poke next?
Shot
13 matches
Mail list logo
