Re: Do 8042/kb_ps2 keyboard devices work under wheezy kernels?
Hello Mark, On Sat, Oct 03, 2015 at 10:32:38AM +, Mark Morgan Lloyd wrote: > For the sake of anybody who does happen to have time, where are you getting > your .iso image and what if any mirror are you selecting during > installation? if you can consider netbooting, maybe https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757787 may help to get a working wheezy installation - that was my last installation (when I still hoped debian will fix the arch). > I had no end of problems about 18 months ago trying to find a SPARC/Linux > later than Lenny which was even half-way reliable, and that was a large part > of our eventual decision to abandon the architecture. What Hardware are you running ? The wheezy kernel seems not to be so bad on my Enterprise/Fire class systems. Greetings Hermann -- Netzwerkadministration/Zentrale Dienste, Interdiziplinaeres Zentrum fuer wissenschaftliches Rechnen der Universitaet Heidelberg IWR; INF 368; 69120 Heidelberg; Tel: (06221)54-8236 Fax: -5224 Email: hermann.la...@iwr.uni-heidelberg.de
Re: Do 8042/kb_ps2 keyboard devices work under wheezy kernels?
Hermann Lauer wrote: Hello Mark, On Sat, Oct 03, 2015 at 10:32:38AM +, Mark Morgan Lloyd wrote: For the sake of anybody who does happen to have time, where are you getting your .iso image and what if any mirror are you selecting during installation? if you can consider netbooting, maybe https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757787 may help to get a working wheezy installation - that was my last installation (when I still hoped debian will fix the arch). Thanks, noted but I'm not optimistic that my workload permits much investigation particularly since the machine most likely to help is now defunct. I had no end of problems about 18 months ago trying to find a SPARC/Linux later than Lenny which was even half-way reliable, and that was a large part of our eventual decision to abandon the architecture. What Hardware are you running ? The wheezy kernel seems not to be so bad on my Enterprise/Fire class systems. At the time, V880. But was prepared to try various other systems in the hope of finding something that would install. The impression I got was that the developers were doing dist-upgrades etc., but were rarely checking the CD image. The bug you cite would appear to stem from the same shortcoming. -- Mark Morgan Lloyd markMLl .AT. telemetry.co .DOT. uk [Opinions above are the author's, not those of his employers or colleagues]
Re: Do 8042/kb_ps2 keyboard devices work under wheezy kernels?
Hermann Lauer wrote: On Mon, Oct 05, 2015 at 08:46:32AM +, Mark Morgan Lloyd wrote: At the time, V880. But was prepared to try various other systems in the hope of finding something that would install. Just checked - on V880 here a vanilla 3.12.6 is running. If you like to get that as a deb, just ask. We ended up putting running Solaris 10 on it for a year, and it will probably be retired with OpenSXCE. The impression I got was that the developers were doing dist-upgrades etc., but were rarely checking the CD image. The bug you cite would appear to stem from the same shortcoming. On the diverging netboot vs. di kernel module iussue on the ftp servers I proposed a check to help keeping the right di kernel modules - but the maintainer didn't like or postponed that idea (stumbled over this on amd64, too). I've seen this sort of thing on Gentoo as well. -- Mark Morgan Lloyd markMLl .AT. telemetry.co .DOT. uk [Opinions above are the author's, not those of his employers or colleagues]
Re: Do 8042/kb_ps2 keyboard devices work under wheezy kernels?
On Mon, Oct 05, 2015 at 08:46:32AM +, Mark Morgan Lloyd wrote: > At the time, V880. But was prepared to try various other systems in the hope > of finding something that would install. Just checked - on V880 here a vanilla 3.12.6 is running. If you like to get that as a deb, just ask. > The impression I got was that the developers were doing dist-upgrades etc., > but were rarely checking the CD image. The bug you cite would appear to stem > from the same shortcoming. On the diverging netboot vs. di kernel module iussue on the ftp servers I proposed a check to help keeping the right di kernel modules - but the maintainer didn't like or postponed that idea (stumbled over this on amd64, too). Greetings Hermann -- Netzwerkadministration/Zentrale Dienste, Interdiziplinaeres Zentrum fuer wissenschaftliches Rechnen der Universitaet Heidelberg IWR; INF 368; 69120 Heidelberg; Tel: (06221)54-8236 Fax: -5224 Email: hermann.la...@iwr.uni-heidelberg.de
Re: Do 8042/kb_ps2 keyboard devices work under wheezy kernels?
Mark Cave-Ayland wrote:
Hi all,
I'm currently working on a patchset to fix up the various OpenBIOS
properties to enable detection of the PS/2 keyboard in QEMU. After a
couple of days work I have a prototype patch which fixes us the various
device tree properties to match those close to real hardware - which
works fine on all of my non-Linux images but fails when trying to boot a
Debian wheezy kernel.
Here is the panic I get when I try and boot the kernel:
[ 17.184211] Unable to handle kernel NULL pointer dereference
[ 17.184776] tsk->{mm,active_mm}->context =
[ 17.185438] tsk->{mm,active_mm}->pgd = f89f6550
[ 17.185964] \|/ \|/
[ 17.185979] "@'/ .. \`@"
[ 17.185990] /_| \__/ |_\
[ 17.186001] \__U_/
[ 17.187411] swapper(1): Oops [#1]
I think we've all seen plenty of this sort of thing over the years.
I'm afraid that it's very unlikely that I can spare time to trawl
through surviving machines trying to find one with the right kind of
hardware: the most likely machine went down with a Psycho failure years ago.
For the sake of anybody who does happen to have time, where are you
getting your .iso image and what if any mirror are you selecting during
installation?
I had no end of problems about 18 months ago trying to find a
SPARC/Linux later than Lenny which was even half-way reliable, and that
was a large part of our eventual decision to abandon the architecture.
--
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk
[Opinions above are the author's, not those of his employers or colleagues]
Do 8042/kb_ps2 keyboard devices work under wheezy kernels?
Hi all,
I'm currently working on a patchset to fix up the various OpenBIOS
properties to enable detection of the PS/2 keyboard in QEMU. After a
couple of days work I have a prototype patch which fixes us the various
device tree properties to match those close to real hardware - which
works fine on all of my non-Linux images but fails when trying to boot a
Debian wheezy kernel.
Here is the panic I get when I try and boot the kernel:
[ 17.184211] Unable to handle kernel NULL pointer dereference
[ 17.184776] tsk->{mm,active_mm}->context =
[ 17.185438] tsk->{mm,active_mm}->pgd = f89f6550
[ 17.185964] \|/ \|/
[ 17.185979] "@'/ .. \`@"
[ 17.185990] /_| \__/ |_\
[ 17.186001] \__U_/
[ 17.187411] swapper(1): Oops [#1]
[ 17.188086] TSTATE: 004480001605 TPC: 00812788 TNPC:
0081278c Y: Not tainted
[ 17.189643] TPC:
[ 17.190247] g0: g1: 009563e8 g2:
g3: 00992cf8
[ 17.191080] g4: f8000703b6e0 g5: g6:
f8000704 g7:
[ 17.191911] o0: 008fd5c0 o1: f8000722e800 o2:
8000 o3: 0002
[ 17.192738] o4: f800070436b0 o5: sp:
f80007042ee1 ret_pc: 00812764
[ 17.193693] RPC:
[ 17.194223] l0: 008e8800 l1: 008fd400 l2:
f800 l3: 00a83bf0
[ 17.195069] l4: f8000726b748 l5: l6:
0097cfa0 l7: 0008
[ 17.195889] i0: f8000722e800 i1: 008e9000 i2:
008fd400 i3: 008e9000
[ 17.196714] i4: f80007296980 i5: i6:
f80007042f91 i7: 006a3d8c
[ 17.197645] I7:
[ 17.198208] Call Trace:
[ 17.198643] [006a3d8c] platform_drv_probe+0xc/0x20
[ 17.199200] [006a2890] really_probe+0x50/0x180
[ 17.199682] [006a0ff4] bus_for_each_drv+0x54/0xa0
[ 17.200178] [006a2a40] device_attach+0x80/0xc0
[ 17.200654] [006a1f98] bus_probe_device+0x78/0xc0
[ 17.201233] [0069fcf8] device_add+0x498/0x600
[ 17.201715] [006a4440] platform_device_add.part.4+0x100/0x240
[ 17.202297] [006a498c] platform_create_bundle+0xcc/0x160
[ 17.202938] [009cd5f4] i8042_init+0x174/0x1d8
[ 17.203420] [00426ba8] do_one_initcall+0xe8/0x160
[ 17.203923] [009b08f0] kernel_init+0xd8/0x168
[ 17.204396] [0042b270] kernel_thread+0x30/0x60
[ 17.204965] [00801f20] rest_init+0x10/0x70
[ 17.205590] Disabling lock debugging due to kernel taint
[ 17.206269] Caller[006a3d8c]: platform_drv_probe+0xc/0x20
[ 17.206875] Caller[006a2890]: really_probe+0x50/0x180
[ 17.207394] Caller[006a0ff4]: bus_for_each_drv+0x54/0xa0
[ 17.207929] Caller[006a2a40]: device_attach+0x80/0xc0
[ 17.208443] Caller[006a1f98]: bus_probe_device+0x78/0xc0
[ 17.208977] Caller[0069fcf8]: device_add+0x498/0x600
[ 17.209568] Caller[006a4440]:
platform_device_add.part.4+0x100/0x240
[ 17.210185] Caller[006a498c]: platform_create_bundle+0xcc/0x160
[ 17.210763] Caller[009cd5f4]: i8042_init+0x174/0x1d8
[ 17.211270] Caller[00426ba8]: do_one_initcall+0xe8/0x160
[ 17.211804] Caller[009b08f0]: kernel_init+0xd8/0x168
[ 17.212312] Caller[0042b270]: kernel_thread+0x30/0x60
[ 17.212826] Caller[00801f20]: rest_init+0x10/0x70
[ 17.213420] Instruction DUMP: 350023f5 901221c0 370023a4
9210001d a21461f0 a01420d0 4467 b2166078
[ 17.215328] Kernel panic - not syncing: Attempted to kill init!
[ 17.215923] Call Trace:
[ 17.216219] [0046711c] do_exit+0x79c/0x7c0
[ 17.216675] [00427c3c] die_if_kernel+0x17c/0x300
[ 17.217265] [00818ac8] unhandled_fault+0x84/0x9c
[ 17.217766] [00819290] do_sparc64_fault+0x7b0/0x8e0
[ 17.218273] [00407880] sparc64_realfault_common+0x10/0x20
[ 17.218881] [00812788] sparc_i8042_probe+0x34/0x134
[ 17.219393] [006a3d8c] platform_drv_probe+0xc/0x20
[ 17.219893] [006a2890] really_probe+0x50/0x180
[ 17.220368] [006a0ff4] bus_for_each_drv+0x54/0xa0
[ 17.220856] [006a2a40] device_attach+0x80/0xc0
[ 17.221428] [006a1f98] bus_probe_device+0x78/0xc0
[ 17.221934] [0069fcf8] device_add+0x498/0x600
[ 17.222402] [006a4440] platform_device_add.part.4+0x100/0x240
[ 17.222968] [006a498c] platform_create_bundle+0xcc/0x160
[ 17.223539] [009cd5f4] i8042_init+0x174/0x1d8
[ 17.224088] [00426ba8] do_one_initcall+0xe8/0x160
[ 17.225484] Press Stop-A (L1-A) to return to the boot prom
The problem seems to be related to the platform-specific parts of the
8042
