Re: [SATA] sata-via : bug?(Closed No Bug)

[Jayant Roplekar]

This turns out to be a motheboard/bios  issue + my lack of careful thinking. 
 And the driver seems to work ok  so far.  Sorry for the false alarm..

Jay Roplekar
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [SATA] sata-via : bug?(Closed No Bug)

[Jayant Roplekar]

This turns out to be a motheboard/bios  issue + my lack of careful thinking. 
 And the driver seems to work ok  so far.  Sorry for the false alarm..

Jay Roplekar
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [SATA] sata-via : bug?

[Jayant Roplekar]

Any modes in the bios for the SATA ports?  Maybe it is in a mode not
supported by linux.  I know the ICH5 only wanted to work for me in
native (enhanced?) mode, not compatible (emulating PATA) mode.  Maybe
via does something similar.  I am puzzles by the UDMA/133 message which
makes no sense for SATA which should be 150 or 300 not 133.

Len Sorensen
Len,
Thanks for the suggestion but I do not have any option of turning any modes 
on in the BIOS.
At this point I am thinking/hoping that  this is quirk introduced by mobo 
that is triggering this behavior in the driver that can be fixed by somebody 
easily. Although I do not have the skill set to device a solution.

Jay
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [SATA] sata-via : bug?

[Jayant Roplekar]

Any modes in the bios for the SATA ports?  Maybe it is in a mode not
supported by linux.  I know the ICH5 only wanted to work for me in
native (enhanced?) mode, not compatible (emulating PATA) mode.  Maybe
via does something similar.  I am puzzles by the UDMA/133 message which
makes no sense for SATA which should be 150 or 300 not 133.

Len Sorensen
Len,
Thanks for the suggestion but I do not have any option of turning any modes 
on in the BIOS.
At this point I am thinking/hoping that  this is quirk introduced by mobo 
that is triggering this behavior in the driver that can be fixed by somebody 
easily. Although I do not have the skill set to device a solution.

Jay
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Kernel bug: mm/rmap.c:483 and related {now 2.6.8}

[Jayant Roplekar]

I had reported a week ago that with  a custom 2.6.10 (tainted with 
ndiswrapper
a windows driver loader) I got error above and that I could not reproduce it
after Hugh Dickins patch to 2.6.10.  Now I have sudden rash of similar 
errors
and lock ups with 2.6.8.1-10mdk  (my daily use kernel)  in the last couple 
of
days.  This *does not* use Hugh's patch.  I ran  memtest overnight with 19
passes and no errors.   I am enclosing all the lines from /var/log/messages 
apparently
related  to mm  errors [ I am a kernel newbie] .  Thanks,

Jay
P.S. This is 250 lines post, you can jump to  commentary  by searching for 

 As a recap:
I  have VIA motherboard and a matrox AGP card.  Following might be relevant
CONFIG_AGP_VIA=m
CONFIG_DRM=y
CONFIG_DRM_MGA=m

 Following message appears three times in syslog at (Jan 29 08:27:03 )
  and at  (Jan 29 08:27:08)  with identical  addresses  and
  then the machine was rebooted
Jan 29 08:25:02 localhost kernel: Bad page state at prep_new_page (in 
process
'X', page c1251ae0)
Jan 29 08:25:02 localhost kernel: flags:0x2004 mapping:6a00 
mapcount:0
count:0
Jan 29 08:25:02 localhost kernel: Backtrace:
Jan 29 08:25:02 localhost kernel:  [dump_stack+30/32] dump_stack+0x1e/0x20
Jan 29 08:25:02 localhost kernel:  [] dump_stack+0x1e/0x20
Jan 29 08:25:02 localhost kernel:  [bad_page+108/160] bad_page+0x6c/0xa0
Jan 29 08:25:02 localhost kernel:  [] bad_page+0x6c/0xa0
Jan 29 08:25:02 localhost kernel:  [prep_new_page+40/112]
prep_new_page+0x28/0x70
Jan 29 08:25:02 localhost kernel:  [] prep_new_page+0x28/0x70
Jan 29 08:25:02 localhost kernel:  [buffered_rmqueue+216/384]
buffered_rmqueue+0xd8/0x180
Jan 29 08:25:02 localhost kernel:  [] buffered_rmqueue+0xd8/0x180
Jan 29 08:25:02 localhost kernel:  [__alloc_pages+161/752]
__alloc_pages+0xa1/0x2f0
Jan 29 08:25:02 localhost kernel:  [] __alloc_pages+0xa1/0x2f0
Jan 29 08:25:02 localhost kernel:  [do_anonymous_page+102/368]
do_anonymous_page+0x66/0x170
Jan 29 08:25:02 localhost kernel:  [] do_anonymous_page+0x66/0x170
Jan 29 08:25:03 localhost kernel:  [do_no_page+95/816] do_no_page+0x5f/0x330
Jan 29 08:25:03 localhost kernel:  [] do_no_page+0x5f/0x330
Jan 29 08:25:03 localhost kernel:  [handle_mm_fault+341/416]
handle_mm_fault+0x155/0x1a0
Jan 29 08:25:03 localhost kernel:  [] handle_mm_fault+0x155/0x1a0
Jan 29 08:25:03 localhost kernel:  [do_page_fault+396/1456]
do_page_fault+0x18c/0x5b0
Jan 29 08:25:03 localhost kernel:  [] do_page_fault+0x18c/0x5b0
Jan 29 08:25:03 localhost kernel:  [error_code+45/56] error_code+0x2d/0x38
Jan 29 08:25:03 localhost kernel:  [] error_code+0x2d/0x38
Jan 29 08:25:03 localhost kernel: Trying to fix it up, but a reboot is 
needed

 After the reboot there were no issues. On the next boot half an hour
  after the boot following stuff appears in the log
Jan 30 08:33:38 localhost kernel: [ cut here ]
Jan 30 08:33:38 localhost kernel: kernel BUG at mm/rmap.c:407!
Jan 30 08:33:38 localhost kernel: invalid operand:  [#1]
Jan 30 08:33:38 localhost kernel: Modules linked in: sd_mod usb-storage
scsi_mod mga md5 ipv6 snd-seq-oss snd-seq-midi-event snd-seq snd-pcm-oss
snd-mixer-oss snd-via82xx snd-ac97-codec snd-pcm snd-timer snd-page-alloc
gameport snd-mpu401-uart snd-rawmidi snd-seq-device snd soundcore af_packet
fealnx mii eth1394 ide-cd cdrom ohci1394 ieee1394 loop ntfs nls_iso8859-1
nls_cp437 vfat fat ndiswrapper via-agp agpgart uhci-hcd usbcore genrtc ext3
jbd
Jan 30 08:33:38 localhost kernel: CPU:0
Jan 30 08:33:38 localhost kernel: EIP:0060:[page_remove_rmap+68/112]
Not tainted VLI
Jan 30 08:33:38 localhost kernel: EIP:0060:[]Not tainted 
VLI
Jan 30 08:33:38 localhost kernel: EFLAGS: 00010246   (2.6.8.1-10mdk)
Jan 30 08:33:38 localhost kernel: EIP is at page_remove_rmap+0x44/0x70
Jan 30 08:33:38 localhost kernel: eax:    ebx: 00104000   ecx:
c039f1d0   edx: c1327000
Jan 30 08:33:38 localhost kernel: esi: cda49530   edi: 0032b000   ebp:
cd02bb78   esp: cd02bb78
Jan 30 08:33:38 localhost kernel: ds: 007b   es: 007b   ss: 0068
Jan 30 08:33:38 localhost kernel: Process net_applet (pid: 5428,
threadinfo=cd02a000 task=d125da30)
Jan 30 08:33:38 localhost kernel: Stack: cd02bba4 c014718a c1327000 0080
0080 cfbd8ec0 19380045 c1327000
Jan 30 08:33:38 localhost kernel:08c48000 ce93b08c 08b73000 cd02bbd4
c0147332 c039f1d0 ce93b088 08848000
Jan 30 08:33:38 localhost kernel:0032b000   c039f1d0
08848000 ce93b08c 08b73000 cd02bbfc
Jan 30 08:33:38 localhost kernel: Call Trace:
Jan 30 08:33:38 localhost kernel:  [show_stack+127/160] show_stack+0x7f/0xa0
Jan 30 08:33:38 localhost kernel:  [] show_stack+0x7f/0xa0
Jan 30 08:33:38 localhost kernel:  [show_registers+342/464]
show_registers+0x156/0x1d0
Jan 30 08:33:38 localhost kernel:  [] show_registers+0x156/0x1d0
Jan 30 08:33:38 localhost kernel:  [die+102/208] die+0x66/0xd0
Jan 30 08:33:38 localhost kernel:  [] die+0x66/0xd0
Jan 30 08:33:38 localhost kernel: