Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Brian Murphy <brian@murphy.dk>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-mips@linux-mips.org
Subject: Re: 2.5 crash on boot
Date: Tue, 01 Jul 2003 23:32:35 +0200	[thread overview]
Message-ID: <3F01FDF3.1090105@murphy.dk> (raw)
In-Reply-To: <3F01CD50.49F34BAC@broadcom.com>

Kip Walker wrote:

>This may be related to something I just found -- in pmd_populate_kernel,
>a physical address is installed in the pmd instead of a virtual
>address.  The patch I sent Ralf 30 minutes ago is attached :-)
>
>Kip
>
>  
>
Now (with the latest source) I get:

kjournald starting.  Commit interval 5 
seconds                                 
EXT3-fs: mounted filesystem with ordered data 
mode.                            
VFS: Mounted root (ext3 filesystem) 
readonly.                                  
Freeing unused kernel memory: 88k 
freed                                        
Adding 131532k swap on /dev/hda1.  Priority:-1 
extents:1                       
EXT3 FS 2.4-0.9.16, 02 Dec 2001 on hda2, internal 
journal                      
mount: Exception at [<800e5650>] 
(800e5830)                                    
mount: Exception at [<800e5650>] 
(800e5830)                                    
mount: Exception at [<800e5650>] 
(800e5830)                                    
 
The error is in __copy_user (both_aligned), closer and closer...

/Brian

WARNING: multiple messages have this Message-ID (diff)
From: Brian Murphy <brian@murphy.dk>
Cc: linux-mips@linux-mips.org
Subject: Re: 2.5 crash on boot
Date: Tue, 01 Jul 2003 23:32:35 +0200	[thread overview]
Message-ID: <3F01FDF3.1090105@murphy.dk> (raw)
Message-ID: <20030701213235.wCyVSmKerzt46-aJVpwVeBjyBLRY5LTkhy02_tIaUuI@z> (raw)
In-Reply-To: <3F01CD50.49F34BAC@broadcom.com>

Kip Walker wrote:

>This may be related to something I just found -- in pmd_populate_kernel,
>a physical address is installed in the pmd instead of a virtual
>address.  The patch I sent Ralf 30 minutes ago is attached :-)
>
>Kip
>
>  
>
Now (with the latest source) I get:

kjournald starting.  Commit interval 5 
seconds                                 
EXT3-fs: mounted filesystem with ordered data 
mode.                            
VFS: Mounted root (ext3 filesystem) 
readonly.                                  
Freeing unused kernel memory: 88k 
freed                                        
Adding 131532k swap on /dev/hda1.  Priority:-1 
extents:1                       
EXT3 FS 2.4-0.9.16, 02 Dec 2001 on hda2, internal 
journal                      
mount: Exception at [<800e5650>] 
(800e5830)                                    
mount: Exception at [<800e5650>] 
(800e5830)                                    
mount: Exception at [<800e5650>] 
(800e5830)                                    
 
The error is in __copy_user (both_aligned), closer and closer...

/Brian

  parent reply	other threads:[~2003-07-01 21:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-01 17:56 2.5 crash on boot Brian Murphy
2003-07-01 18:05 ` Kip Walker
2003-07-01 20:55   ` Brian Murphy
2003-07-02  0:46     ` Ralf Baechle
2003-07-01 21:32   ` Brian Murphy [this message]
2003-07-01 21:32     ` Brian Murphy
     [not found] ` <3F01CCAA.9050307@mac.com>
2003-07-01 20:36   ` Brian Murphy

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=3F01FDF3.1090105@murphy.dk \
    --to=brian@murphy.dk \
    --cc=linux-mips@linux-mips.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