public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kasper Sandberg <lkml@metanurb.dk>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.15-rc4
Date: Thu, 01 Dec 2005 19:57:53 +0100	[thread overview]
Message-ID: <1133463473.16820.3.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.64.0512010759571.3099@g5.osdl.org>

On Thu, 2005-12-01 at 08:05 -0800, Linus Torvalds wrote:
> 
> On Thu, 1 Dec 2005, Kasper Sandberg wrote:
> >
> > On Wed, 2005-11-30 at 22:40 -0800, Linus Torvalds wrote:
> > <snip>
> > > 
> > > 		Linus
> > > 
> > > [ Btw, some drivers will now complain loudly about their nasty mis-use of 
> > >   page remapping, and that migh look scary, but it should all be good, and 
> > >   we'd love to see the detailed output of dmesg on such machines. ]
> > > 
> > 
> > this is the ati proprietary driver on x86 laptop.
> > 
> > Backtrace:
> >  [<b013d88d>] bad_page+0x7d/0xc0
> >  [<b013e124>] free_hot_cold_page+0x44/0x100
> >  [<b0148c2c>] zap_pte_range+0xfc/0x220
> >  [<b0148e3c>] unmap_page_range+0xec/0x110
> >  [<b0148f21>] unmap_vmas+0xc1/0x1e0
> >  [<b014cc45>] unmap_region+0x85/0x110
> >  [<b014cf39>] do_munmap+0xd9/0x120
> >  [<b014cfc7>] sys_munmap+0x47/0x70
> >  [<b0102f1b>] sysenter_past_esp+0x54/0x75
> > Trying to fix it up, but a reboot is needed
> 
> It _should_ have said something before this too. In particular, I'd have 
> expected a message like
> 
> 	X.org does an incomplete pfn remapping
> 	Backtrace:
> 	 ....
> 
> when the thing started up. Oh, and _just_ before that trace, I'd have 
> expected a
> 
> 	Bad page state at ....
> 	flags: .....
> 
> which is also something I'd like to see.
> 
> Oh, and that "Trying to fix it up, but a reboot is needed" message should 
> be harmless. We share the same "bad_page()" function with all the 
> problems, even though the PageReserved() one should really be harmless 
> apart from being scary-noisy. So please keep running, if only to verify 
> that I'm not full of crap about that.
> 
> (I can silence the nasty warnings easily enough, but I wanted people who 
> triggered the new code-paths to be aware of it and report to me what 
> drivers to it, so they are _really_ noisy right now).
im not sure its a good idea to silence this, because this seems to be a
genuine error, the ati proprietary driver is not working.. if i try to
use 3d, it will display this message again, and the process trying to
use 3d will freeze, and become unkillable.

> 
> 		Thanks,
> 
> 				Linus
> 


  reply	other threads:[~2005-12-01 18:57 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-01  6:40 Linux 2.6.15-rc4 Linus Torvalds
2005-12-01 12:18 ` Ralf Hildebrandt
2005-12-01 21:11   ` Terence Ripperda
2005-12-01 23:11     ` Linus Torvalds
2005-12-02 18:02       ` Terence Ripperda
2005-12-03  0:22         ` Greg KH
     [not found]           ` <6f6293f10512031726n10ea87e6s44be5dffbd512bb5@mail.gmail.com>
2005-12-04  1:34             ` Linus Torvalds
2005-12-01 14:05 ` Kasper Sandberg
2005-12-01 16:05   ` Linus Torvalds
2005-12-01 18:57     ` Kasper Sandberg [this message]
2005-12-01 19:04       ` Linus Torvalds
2005-12-01 22:57         ` Kasper Sandberg
     [not found]     ` <6f6293f10512011112m6e50fe0ejf0aa5ba9d09dca1e@mail.gmail.com>
2005-12-01 19:34       ` Linus Torvalds
2005-12-01 21:41         ` Eyal Lebedinsky
2005-12-01 21:53           ` Linus Torvalds
2005-12-01 23:37             ` Grant Coady
2005-12-02 11:45               ` Mauro Carvalho Chehab
2005-12-02 17:41                 ` Grant Coady
2005-12-02 17:48                   ` Michael Krufky
2005-12-02 19:37                     ` Pauline Middelink
2005-12-02 20:19                       ` Grant Coady
2005-12-02 20:32                         ` Richard Mittendorfer
2005-12-04 15:50                     ` Adrian Bunk
  -- strict thread matches above, loose matches on Subject: below --
2005-12-04  3:00 Paul Blazejowski
2005-12-04 14:12 Subodh Shrivastava
2005-12-05 15:51 ` Mark Lord

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1133463473.16820.3.camel@localhost \
    --to=lkml@metanurb.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox