PPC Radeon Xserver bug? (Was Re: Debian Sparc4 mounts root as read-only)

[Daniel Smith]

This is a _good thing_ (tm). Would you really like your
system to fsck a *live* *writable* file system.

More importantly, what does mount(1) say?
Mine sez

[root at fuji drs]# mount
/dev/sda1 on / type ext2 (rw,errors=remount-ro,errors=remount-ro)
proc on /proc type proc (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/sda2 on /mnt type ext2 (rw)

ie Once you've fsck'ed the / fs, it will remount rw.

Just so you know it's not a SPARCism

drs at kobe:~$ mount
/dev/hdb10 on / type ext2 (rw,errors=remount-ro)
proc on /proc type proc (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/hdb12 on /usr type ext3 (rw)
/dev/hdb13 on /var type ext3 (rw)

drs at kobe:~$ dmesg | grep VFS
VFS: Diskquotas version dquot_6.4.0 initialized
VFS: Mounted root (ext3 filesystem) readonly.

Which is my Dual G4

(Maybe it's an endian conspiracy !)

Speaking of which, Am I the only one who thinks

(II) RADEON(0): Hitachi CM722: Using hsync range of 31.00-115.00 kHz
(II) RADEON(0): Hitachi CM722: Using vrefresh range of 50.00-160.00 Hz
(II) RADEON(0): Clock range: 8403.06 to -1237165.64 MHz
(II) RADEON(0): Not using mode "1280x1024" (bad mode clock/interlace/doublescan)

means I've found an off by one/miscast etc bug in the ppc radeon server?

I don't have the source to trawl through atm (bleah, dialup!)

Daniel

On Wed, Mar 27, 2002 at 10:20:41AM +1100 or thereabouts, Antti.Roppola at brs.gov.au wrote:
> Some time in the recent past, my Sparc4 has started
> mounting root as read-only. /tmp and /var seem OK.
> 
> dmesg says:
> VFS: Mounted root (ext2 filesystem) readonly.
> 
> fstab says:
> /dev/sda1	/		ext2	defaults,errors=remount-ro	0	1
> 
> I tried "mount / -o remount,rw", but to no (discernable)
> effect. When I display the partition table in fdisk, I notice
> that Flag is set as "u" on root, but not swap. I can use
> cat & echo to create and append to files, but not vi.
> 
> Anyone have any ideas on what is going on? It seems a reasonably
> common problem (trolling Google), but I haven't yet found a fix.
> 
> TIA,
> 
> Antti
>