[arch-dev-public] Issues with kernel 3.6.4 on some AMD systems
Hi all, turns out there was an issue with Linux 3.6.4 on some AMD systems with more than 4GB of RAM. 3.6.5 fixed this bug. Unfortunately this was a little too late for the recent ISO image. I was wondering what was the best way to handle issues like this. One of the benefits of monthly releases is that we have more than one image available which is recent enough to install your system. Instead of aiming for the perfect, bug free system I would prefer to update the download page with a "known issues" section and a link to the last two previous install images. I think it might be saner to solve the problem this way; for example 3.6.5 might fix this issue but as the changelog is quite long its possible new bugs were introduced at the same time. In this particular case a simple workaround exists by adding "mem=3G" to your boot parameters. PS: Maybe it's worth to post a dedicated news item about this issue; I assume while not a lot of people seem to be affected most probably got hit it via regular system updates. What do you think about this? In general and for this particular problem. Greetings, Pierre -- Pierre Schmitz, https://pierre-schmitz.com
On Fri, Nov 02, 2012 at 08:06:03PM +0100, Pierre Schmitz wrote:
Hi all,
turns out there was an issue with Linux 3.6.4 on some AMD systems with more than 4GB of RAM. 3.6.5 fixed this bug. Unfortunately this was a little too late for the recent ISO image.
I was wondering what was the best way to handle issues like this. One of the benefits of monthly releases is that we have more than one image available which is recent enough to install your system. Instead of aiming for the perfect, bug free system I would prefer to update the download page with a "known issues" section and a link to the last two previous install images. I think it might be saner to solve the problem this way; for example 3.6.5 might fix this issue but as the changelog is quite long its possible new bugs were introduced at the same time.
In this particular case a simple workaround exists by adding "mem=3G" to your boot parameters.
PS: Maybe it's worth to post a dedicated news item about this issue; I assume while not a lot of people seem to be affected most probably got hit it via regular system updates.
What do you think about this? In general and for this particular problem.
Greetings,
Pierre
-- Pierre Schmitz, https://pierre-schmitz.com
Given that: - it doesn't affect everyone - there's an easy enough workaround - there's always last month's ISO - there's always next month's ISO I vote for a news post for the front page, and we just roll with it. d
- it doesn't affect everyone - there's an easy enough workaround - there's always last month's ISO - there's always next month's ISO
I vote for a news post for the front page, and we just roll with it.
d
A notice should be enough. ++
Am 02.11.2012 20:13, schrieb Dave Reisner:
Given that:
- it doesn't affect everyone - there's an easy enough workaround - there's always last month's ISO - there's always next month's ISO
I vote for a news post for the front page, and we just roll with it.
How about the idea to integrate a "known issues" section and links to previous isos on the download page. We all know noody reads the front page. :-) -- Pierre Schmitz, https://pierre-schmitz.com
On Fri, Nov 2, 2012 at 8:06 PM, Pierre Schmitz
turns out there was an issue with Linux 3.6.4 on some AMD systems with more than 4GB of RAM. 3.6.5 fixed this bug. Unfortunately this was a little too late for the recent ISO image.
I was wondering what was the best way to handle issues like this.
Maybe in this case it is not worth it, but in principle we could just push a new version (not changing anything but bumping the kernel version). -t
participants (4)
-
Dave Reisner
-
Laurent Carlier
-
Pierre Schmitz
-
Tom Gundersen