From: "Diego Calleja García" <diegocg@teleline.es>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.70-mm9
Date: Sun, 15 Jun 2003 03:14:21 +0200 [thread overview]
Message-ID: <20030615031421.1ed6640a.diegocg@teleline.es> (raw)
In-Reply-To: <20030613013337.1a6789d9.akpm@digeo.com>
On Fri, 13 Jun 2003 01:33:37 -0700
Andrew Morton <akpm@digeo.com> wrote:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.5/2.5.70/2.5.70-mm9/
I had the following messages: (ide, ext3 without any option, SMP, AS, JBD
debugging enabled):
VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci00:07.1
ide0: BM-DMA at 0xd000-0xd007, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xd008-0xd00f, BIOS settings: hdc:DMA, hdd:DMA
hda: Maxtor 6Y060L0, ATA DISK drive
anticipatory scheduling elevator
[...]
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
[...]
EXT3 FS 2.4-0.9.16, 02 Dec 2001 on hda5, internal journal
[...]
__mark_inode_dirty: this cannot happen
__mark_inode_dirty: this cannot happen
__mark_inode_dirty: this cannot happen
__mark_inode_dirty: this cannot happen
PPP: VJ decompression error
PPP: VJ decompression error
PPP: VJ decompression error
__mark_inode_dirty: this cannot happen
__mark_inode_dirty: this cannot happen
__mark_inode_dirty: this cannot happen
__mark_inode_dirty: this cannot happen
__mark_inode_dirty: this cannot happen
__mark_inode_dirty: this cannot happen
invalid via82xx_cur_ptr, using last valid pointer
invalid via82xx_cur_ptr, using last valid pointer
invalid via82xx_cur_ptr, using last valid pointer
PPP: VJ decompression error
next prev parent reply other threads:[~2003-06-15 1:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-13 8:33 2.5.70-mm9 Andrew Morton
2003-06-13 9:17 ` 2.5.70-mm9 Andrew Morton
2003-06-13 10:50 ` Bug in 2.5.70-mm9: df: `/': Value too large for defined data type Thomas Schlichter
2003-06-13 20:09 ` Andrew Morton
2003-06-13 17:57 ` 2.5.70-mm9 Brandon Low
2003-06-14 7:51 ` 2.5.70-mm9 Mingming Cao
2003-06-14 8:01 ` 2.5.70-mm9 Andrew Morton
2003-06-15 0:41 ` 2.5.70-mm9 Mingming Cao
2003-06-15 4:14 ` 2.5.70-mm9 Nick Piggin
2003-06-16 16:25 ` 2.5.70-mm9 Mingming Cao
2003-06-15 6:20 ` 2.5.70-mm9 Andrew Morton
2003-06-16 15:59 ` 2.5.70-mm9 Mingming Cao
2003-06-18 7:13 ` 2.5.70-mm9 Mingming Cao
2003-06-18 7:38 ` 2.5.70-mm9 Andrew Morton
2003-06-18 13:54 ` 2.5.70-mm9 James Bottomley
2003-06-15 1:14 ` Diego Calleja García [this message]
2003-06-15 7:58 ` 2.5.70-mm9 Felipe Alfaro Solana
2003-06-15 11:22 ` 2.5.70-mm9 Diego Calleja García
2003-06-13 22:21 2.5.70-mm9 Shane Shrybman
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=20030615031421.1ed6640a.diegocg@teleline.es \
--to=diegocg@teleline.es \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).