Linux v2.6.18-rc5
In-Reply-To: <[email protected]>
Quoted 10 lines · Andrew Morton
Quoted 1 line
Linux 2.6.18-rc5 is out there now
(Reporters Bcc'ed: please provide updates)
Serious-looking regressions include:
<...>
From: Chuck Ebbert <[email protected]>
Subject: PCI: Cannot allocate resource region 7 of bridge 0000:00:04.0
Also happens on 2.6.16.28 and 2.6.17.11, so not a regression.
Quoted 4 lines
From: "Beschorner Daniel" <[email protected]>
Subject:fctnl(F_SETSIG)no longer works in 2.6.17, does in 2.6.16.(I think we fixed this?)
Fixed by this -rc5 patch:
Trond Myklebust:
fcntl(F_SETSIG) fix
Signature · 1 line
Chuck
Quoted 4 lines · On Mon, 28 Aug 2006 05:50:07 -0400 Chuck Ebbert <[email protected]>…
Quoted 2 lines
From: Chuck Ebbert <[email protected]>
Subject: PCI: Cannot allocate resource region 7 of bridge 0000:00:04.0Also happens on 2.6.16.28 and 2.6.17.11, so not a regression.
Well it's not a post-2.6.17 regression. But it's something which quite a few people have been reporting in recent months. I don't _think_ it's associated with any consistent runtime failures, but otoh I don't think we know what caused it.
Quoted 6 lines · Andrew Morton
Quoted 3 lines · On Mon, 28 Aug 2006 05:50:07 -0400 Chuck Ebbert <[email protected]>…
Quoted 2 lines
From: Chuck Ebbert <[email protected]>
Subject: PCI: Cannot allocate resource region 7 of bridge 0000:00:04.0
Quoted 6 lines
Quoted 1 line
Also happens on 2.6.16.28 and 2.6.17.11, so not a regression.
Well it's not a post-2.6.17 regression. But it's something which quite a few people have been reporting in recent months. I don't _think_ it's associated with any consistent runtime failures, but otoh I don't think we know what caused it.
in itself this can just happen (bios issue, but if the bars are unused no big deal)... the kernel has gotten more verbose afaik though.
It CAN cause real issues so I'm not saying there's no problem or no regression, it's just that the printk alone isn't serious.