[Bug 1424231] Re: A trivial program can exhaust system memory with infinite anon_vma chain.

Based on comment above by Luis, this bug is confirmed. ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed ** Changed in: juju-website Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug

[Bug 1205741] Re: The route metrics added ip route are not being inherited by route cache entries

Unfortunately in my haste to verify this, I bungled my test of -55 and managed to pull down the wrong source for -55 as well. Now that I have corrected both those mistakes, I can verify that the code for the fix is in -55 and the code for the fix functions properly. Sorry about that. **

[Bug 1205741] Re: The route metrics added ip route are not being inherited by route cache entries

** Tags removed: verification-done verification-needed-precise ** Tags added: verification-done-precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1205741 Title: The route metrics added ip route

[Bug 1205741] Re: The route metrics added ip route are not being inherited by route cache entries

I just downloaded linux-image-3.2.0-55-generic from -proposed and the bug is still in this version. I inspected the source for linux- image-3.2.0-55-generic and I see no evidence that the patches cited above have been applied. There is no implementation or invocation of inetpeer_invalidate_tree

[Bug 1205741] Re: The route metrics added ip route are not being inherited by route cache entries

** Tags added: verification-failed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1205741 Title: The route metrics added ip route are not being inherited by route cache entries To manage

[Bug 1205741] Re: The route metrics added ip route are not being inherited by route cache entries

Does the move from Incomplete to Fix Committed mean that the fix for this bug will be in -54 or we miss the window for that? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1205741 Title: The route

[Bug 1205741] Re: The route metrics added ip route are not being inherited by route cache entries

So what is the status of this bug. The 3.2.0-53 update arrived today and the fix wasn't in it. Is this bug going to be fixed or not? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1205741 Title:

Re: [Bug 1205741] Re: The route metrics added ip route are not being inherited by route cache entries

Joe, Sorry for the late response, I was on vacation. I will load it up and give it a ride. Tim Hartrick On Fri, 2013-08-16 at 18:04 +, Joseph Salisbury wrote: I built a Precise test kernel with commits 5faa5df and 55432d2 applied. The test kernel can be downloaded from: http

Re: [Bug 1205741] Re: The route metrics added ip route are not being inherited by route cache entries

Joe, This kernel fixes the problem. Thanks Tim Hartrick On Mon, 2013-08-19 at 17:29 -0600, Tim Hartrick wrote: Joe, Sorry for the late response, I was on vacation. I will load it up and give it a ride. Tim Hartrick On Fri, 2013-08-16 at 18:04 +, Joseph Salisbury wrote: I

Re: [Bug 1205741] Re: The route metrics added ip route are not being inherited by route cache entries

Joe, These three seem to be relevant. https://git.kernel.org/cgit/linux/kernel/git/stable/linux- stable.git/commit/?h=linux-3.5.yid=5faa5df1fa2024bd750089ff21dcc4191798263d https://git.kernel.org/cgit/linux/kernel/git/stable/linux-

[Bug 1205741] [NEW] The route metrics added ip route are not being inherited by route cache entries

Public bug reported: There is a bug in the the management of inet peers which prevents route metrics like initcwnd from being inherited by route cache entries. An example: $ ip route show default via 172.16.231.2 dev eth0 metric 100 172.16.231.0/24 dev eth0 proto kernel scope link src

[Bug 1205741] AlsaDevices.txt

apport information ** Attachment added: AlsaDevices.txt https://bugs.launchpad.net/bugs/1205741/+attachment/3751679/+files/AlsaDevices.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1205741

[Bug 1205741] Re: The route metrics added ip route are not being inherited by route cache entries

apport information ** Tags added: apport-collected precise ** Description changed: There is a bug in the the management of inet peers which prevents route metrics like initcwnd from being inherited by route cache entries. An example: $ ip route show default via 172.16.231.2 dev

[Bug 1205741] PciMultimedia.txt

apport information ** Attachment added: PciMultimedia.txt https://bugs.launchpad.net/bugs/1205741/+attachment/3751685/+files/PciMultimedia.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1205741] UdevLog.txt

apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/1205741/+attachment/3751690/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1205741 Title:

[Bug 1205741] ProcCpuinfo.txt

apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1205741/+attachment/3751686/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1205741

[Bug 1205741] UdevDb.txt

apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1205741/+attachment/3751689/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1205741 Title: The

[Bug 1205741] ProcInterrupts.txt

apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/1205741/+attachment/3751687/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1205741] Card0.Codecs.codec97.0.ac97.0.0.regs.txt

apport information ** Attachment added: Card0.Codecs.codec97.0.ac97.0.0.regs.txt https://bugs.launchpad.net/bugs/1205741/+attachment/3751682/+files/Card0.Codecs.codec97.0.ac97.0.0.regs.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1205741] ProcModules.txt

apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/1205741/+attachment/3751688/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1205741

[Bug 1205741] WifiSyslog.txt

apport information ** Attachment added: WifiSyslog.txt https://bugs.launchpad.net/bugs/1205741/+attachment/3751691/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which

[Bug 1205741] BootDmesg.txt

apport information ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/1205741/+attachment/3751680/+files/BootDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1205741

[Bug 1205741] Card0.Codecs.codec97.0.ac97.0.0.txt

apport information ** Attachment added: Card0.Codecs.codec97.0.ac97.0.0.txt https://bugs.launchpad.net/bugs/1205741/+attachment/3751681/+files/Card0.Codecs.codec97.0.ac97.0.0.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1205741] Lspci.txt

apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/1205741/+attachment/3751684/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1205741 Title: The

[Bug 1205741] CurrentDmesg.txt

apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/1205741/+attachment/3751683/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1205741

[Bug 882340] Re: Invalid physical address encountered during vmcore_init.

Christoper, The report was made again the natty 2.6.38-8 kernel. It was subsequently reproduced on upstream kernels out to 3.2. As I noted in my previous comment, I worked with the upstream developers to create a patch that works on the 2.6.38 kernel as well as newer kernels (see previous

[Bug 882340] Re: Invalid physical address encountered during vmcore_init.

If the patch has been applied to the 2.6.38 natty line, the 2.6.32 lucid line and the 3.2.0 precise line, then all the releases that we use have been fixed. If all those releases have been fixed then from my perspective the bug can be closed. Of course the 3.0.0 oneric line also had the bug. --

[Bug 882340] Re: Invalid physical address encountered during vmcore_init.

Christopher, I worked with the upstream developers back in November to generate a patch for this. The original commit was from Tejun Heo a855b84c3d8c73220d4d3cd392a7bee7c83de70e It was merged into the 3.2 tree at 9b5a4d4f65e260a109eaeea8bbc8062a7c58b55e -- You received this bug notification

[Bug 882322] Re: The crashkernel size can't be = 512M

I am curious to know whether this problem and 882340 have any chance of getting fixed in a future natty update. If not, what is the chance that they ever get fixed? We would very much like to use kexec/kdump on our largish servers (48GB) but we can't as long as they bugs are in the way. -- You

[Bug 882340] Re: Invalid physical address encountered during vmcore_init.

I installed linux- image-3.1.0-030100rc10-generic_3.1.0-030100rc10.201110200610_amd64.deb and got essentially the same result. [ 73.637287] SysRq : Trigger a crash [ 73.640783] BUG: unable to handle kernel NULL pointer dereference at (null) [ 73.648611] IP: [813aa2b6]

[Bug 882322] [NEW] The crashkernel size can't be = 512M

Public bug reported: For 2.6.38-8-server and 2.6.38-10-server running on Dell R710s and R610s with 50GB of memory it isn't possible to create a crashkernel area of 512M or larger. The limit is actually less than 512M but I haven't bothered to do a binary search between 384M and 512M to

[Bug 882322] Re: The crashkernel size can't be = 512M

-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/882322 Title: The crashkernel size can't be = 512M To manage notifications about this bug go to:

[Bug 882340] [NEW] Invalid physical address encountered during vmcore_init.

Public bug reported: For 2.6.38-8-server and 2.6.38-10-server running on Dell R610s and R710s with 50GB of memory we see consistent failure of vmcore_init because of an invalid physical address. The invalid address is always the same, db74. Below is the dmesg of the event. The

[Bug 882340] Re: Invalid physical address encountered during vmcore_init.

-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/882340 Title: Invalid physical address encountered during vmcore_init. To manage notifications about this bug go to: