Oh... try removing the speakup patch... it reorders initialization of
serio which might be it... so put:
in the ebuild (under the use ultra1 || UNIPATCH_EXCLUDE=... line).
On Wed, 2004-12-01 at 18:31 -0800, Jeremy Huddleston wrote:
> On Wed, 2004-12-01 at 14:09 -0900, Leif Sawyer wrote:
> > Jeremy Huddleston writes:
> > > Can you try d-s-2.6.7 to see if your keyboard works there?
> > > I'm helping dsd with g-d-s now for sparc related goodies,
> > > and I want to squash these annoying bugs, but unfortunately,
> > > I can't reproduce the keyboard bug...
> > yikes..
> > emerge and build of 2.6.7-r16
> > boot:
> > Console: switching to colour frome buffer device 160x64
> > zs2 at 0x000001fff100000f (irq = 12,7e8) is a SunZilog
> > bad: scheduling while atomic!
> > Call Trace:
> > [000000000052d648] sunkbd_initialize+0x1a8/0x1e0
> > [000000000052d910] sunkbd_connect+0x130/0x220
> > [000000000052da94] serio_find_dev+0x54/0x80
> > [000000000052df78] serio_register_port+0x18/0x40
> > [00000000006f4794] sunzilog_init_kbdms+0x134/0x180
> > [0000000000......] sunzilog_init_hw
> > [0000000000......] sunzilog_ports_init
> > [0000000000......] sunzilog_init
> > [0000000000......] do_init_calls
> > [0000000000......] init
> > [0000000000......] kernel_thread
> > [0000000000......] rest_init
> > zs3 at 0x000001fff1000000 (irq = 12,7e8) is a SunZilog
> Again, this is a known issue but apparently everyone experiencing it is
> unwilling to find the solution... see this message from last week:
> On Fri, 2004-11-26 at 16:11 -0800, Jeremy Huddleston wrote:
> > On Fri, 2004-11-26 at 23:45 +0000, Ciaran McCreesh wrote:
> > > d-s-2.6.7 works. g-d-s-2.6.7 doesn't, hence why I moan about the
> > > patchset so much :) Unfortunately I don't have access to the box
> that I
> > > could trigger that on any more...
> > >
> > Ok, that's actually good news... So if someone can trigger the
> > bug in the g-d-s-2.6.7-r15 kernel, then try adding this to the
> > gentoo-dev-sources-2.6.7-r15 ebuild and re-emerging/compiling the
> > kernel... This will exclude all the non-sparc patches...
> > UNIPATCH_EXCLUDE="1100_ip_tables.patch 1105_CAN-2004-0497.patch
> > 1110_proc.patch 1115_net_eql.patch 1120-CAN-2004-0415.patch
> > 1125-proc_pid_cmdline-race-fix.patch 1130_nfs-fix.patch
> > 1135_netfilter-dos-fix.patch 1140_CAN-2004-0814.patch
> > 1145_smbfs-dos.patch 1310_k8_cardbus_io.patch
> > 1315_alpha-sysctl-uac.patch 1320_x86_64-2.6.7-2.patch
> > 1321_x86_64-noiommu.patch 1325_iptables-headers.patch
> > 1900_ulogd_timestamp.patch 2115_fa311-mac-address-fix.patch
> > 2700_ppc-pegasos-2.6.6.patch 2905_mouse_click_fix.patch
> > 2910_wacom_fix.patch 4505_bootsplash-3.1.4-sp-0.1-2.6.7.patch
> > 4705_squashfs-2.0.patch 4715_supermount-2.0.4-2.6.7.patch
> > 4905_speakup-20040618.patch"
> > Test that out, slowly remove them until you find the culprit...
> > I am suspicious of 2905_mouse_click_fix.patch as it's the only one
> > touches the input code, so try re-adding that one first to see if it
> > rebreaks the keyboard.
> > --Jeremy
Jeremy Huddleston <firstname.lastname@example.org>