| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Thu, 07 Jan 2010 10:51:24 +0000 From: Richard Purdie <rpurdie@...ys.net> To: Arnd Hannemann <hannemann@...s.rwth-aachen.de>, Daniel Mack <daniel@...aq.de> Cc: LKML <linux-kernel@...r.kernel.org>, linux-geode@...ts.infradead.org Subject: Re: 2.6.33-rc3 regression: leds_alix2: can't allocate I/O for GPIO On Thu, 2010-01-07 at 11:26 +0100, Arnd Hannemann wrote: > with 2.6.33-rc3 the LEDs are not working anymore on my Geode embedded board: > If I remember correctly this was working fine with 2.6.32, but certainly with 2.6.31 > > relevant dmesg output of 2.6.33-rc3: > > [ 0.709643] cs5535_gpio: base=0x6100 mask=0xb003c66 major=253 > > [ 2.207947] leds_alix2: system is recognized as "PC Engines ALIX.2 v0.99h" > [ 2.228678] leds_alix2: can't allocate I/O for GPIO > > > For reference dmesg of 2.6.31.3: > > [ 0.611953] cs5535_gpio: base=0x6100 mask=0xb003c66 major=253 > > [ 2.379114] leds_alix2: system is recognized as "PC Engines ALIX.2" > [ 2.399097] Registered led device: alix:1 > [ 2.411404] Registered led device: alix:2 > [ 2.423720] Registered led device: alix:3 Its likely to be commit 7f131cf3ed96c969d7b092bf629e25c3df50901e. It looks like the request_region() call is failing. Daniel, any idea why? Cheers, Richard -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists