- openSUSE Bugs

[Bug 193280] Novell SLED10 : Active Directory change password "Segmentation fault"
by bugzilla_noreply＠novell.com 12 Sep '06

12 Sep '06

https://bugzilla.novell.com/show_bug.cgi?id=193280 gd(a)suse.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Info Provider|adanieli(a)arpa.veneto.it | Resolution| |WORKSFORME ------- Comment #14 from gd(a)suse.de 2006-09-12 11:29 MST ------- No feedback for months. Closing this. Reopen when you see this happening again. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 0

[Bug 196308] SMB won't connect to a Vista 5384 machine
by bugzilla_noreply＠novell.com 12 Sep '06

12 Sep '06

https://bugzilla.novell.com/show_bug.cgi?id=196308 gd(a)suse.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |LATER ------- Comment #9 from gd(a)suse.de 2006-09-12 11:27 MST ------- Well work on this later. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 0

[Bug 201756] pam_winbind.so uses openlog()
by bugzilla_noreply＠novell.com 12 Sep '06

12 Sep '06

https://bugzilla.novell.com/show_bug.cgi?id=201756 gd(a)suse.de changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|samba-maintainers(a)SuSE.de |gd(a)suse.de Status|NEW |ASSIGNED -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 0

[Bug 168834] NVIDIA's glx does not work for big twinview / Xinerama displays on some 6200
by bugzilla_noreply＠novell.com 12 Sep '06

12 Sep '06

https://bugzilla.novell.com/show_bug.cgi?id=168834 mhopf(a)novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED ------- Comment #19 from mhopf(a)novell.com 2006-09-12 11:17 MST ------- Created an attachment (id=98478) --> (https://bugzilla.novell.com/attachment.cgi?id=98478&action=view) triarray.c Source of simple test program that exhibits the issue. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 0

[Bug 168834] NVIDIA's glx does not work for big twinview / Xinerama displays on some 6200
by bugzilla_noreply＠novell.com 12 Sep '06

12 Sep '06

https://bugzilla.novell.com/show_bug.cgi?id=168834 ------- Comment #18 from mhopf(a)novell.com 2006-09-12 11:16 MST ------- glxgears triggers the issue. Also find triarray.c attached. Compile with gcc -o triarray triarray.c -lglut Call triarray 1500 Correction to comment #15: it is not double buffering that triggers the bug, but the use of glClear(GL_COLOR_BUFFER_BIT). If I disable the call in run(), the display remains calm. If I enable it, the issue pops up, in single *and* in double buffering mode. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 0

[Bug 201756] pam_winbind.so uses openlog()
by bugzilla_noreply＠novell.com 12 Sep '06

12 Sep '06

https://bugzilla.novell.com/show_bug.cgi?id=201756 ------- Comment #1 from gd(a)suse.de 2006-09-12 11:16 MST ------- Created an attachment (id=98477) --> (https://bugzilla.novell.com/attachment.cgi?id=98477&action=view) remove openlog/closelog -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 0

[Bug 192199] Intel Pro gigabit fiber nic fails to communicate
by bugzilla_noreply＠novell.com 12 Sep '06

12 Sep '06

https://bugzilla.novell.com/show_bug.cgi?id=192199 ------- Comment #15 from john.ronciak(a)intel.com 2006-09-12 11:15 MST ------- I updated 161679 which is this same issue with this information yesterday. The questions in that bug still apply. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 0

[Bug 192199] Intel Pro gigabit fiber nic fails to communicate
by bugzilla_noreply＠novell.com 12 Sep '06

12 Sep '06

https://bugzilla.novell.com/show_bug.cgi?id=192199 tony(a)mail.applog.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|tony(a)mail.applog.com | ------- Comment #14 from tony(a)mail.applog.com 2006-09-12 10:59 MST ------- Got this email from the kernel list.... it apparently fixes the the problem with the intel nic... however I do not know how or if I should apply it. Will there be a kernel update that has the patch soon? Here is the message from auke-jan.h.kok(a)intel.com Commit 581d708eb47cccb5f41bc0817e50c9b004011ba8 (oct. 5 2005) introduced partial Multiqueue support for e1000 which broke macro smartness in setting up head/tail registers for 82542 rev3 chipsets, making these adapters completely non-working since 2.6.15. This commit sets the proper head and tail registers for read and write descriptor rings. Ths fix was tested on an 82542 rev3 NIC and newer NICs. Signed-off-by: Auke Kok <auke-jan.h.kok(a)intel.com> diff --git a/drivers/net/e1000/e1000_main.c b/drivers/net/e1000/e1000_main.c index 726f43d..98ef9f8 100644 --- a/drivers/net/e1000/e1000_main.c +++ b/drivers/net/e1000/e1000_main.c @@ -1433,8 +1433,8 @@ e1000_configure_tx(struct e1000_adapter E1000_WRITE_REG(hw, TDBAL, (tdba & 0x00000000ffffffffULL)); E1000_WRITE_REG(hw, TDT, 0); E1000_WRITE_REG(hw, TDH, 0); - adapter->tx_ring[0].tdh = E1000_TDH; - adapter->tx_ring[0].tdt = E1000_TDT; + adapter->tx_ring[0].tdh = ((hw->mac_type >= e1000_82543) ? E1000_TDH : E1000_82542_TDH); + adapter->tx_ring[0].tdt = ((hw->mac_type >= e1000_82543) ? E1000_TDT : E1000_82542_TDT); break; } @@ -1840,8 +1840,8 @@ #endif E1000_WRITE_REG(hw, RDBAL, (rdba & 0x00000000ffffffffULL)); E1000_WRITE_REG(hw, RDT, 0); E1000_WRITE_REG(hw, RDH, 0); - adapter->rx_ring[0].rdh = E1000_RDH; - adapter->rx_ring[0].rdt = E1000_RDT; + adapter->rx_ring[0].rdh = ((hw->mac_type >= e1000_82543) ? E1000_RDH : E1000_82542_RDH); + adapter->rx_ring[0].rdt = ((hw->mac_type >= e1000_82543) ? E1000_RDT : E1000_82542_RDT); break; } -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 0

[Bug 171517] APIC problems on Asus M2N-SLI Deluxe (chipset nForce 570; socket AM2) machine hangs at early boot time
by bugzilla_noreply＠novell.com 12 Sep '06

12 Sep '06

https://bugzilla.novell.com/show_bug.cgi?id=171517 ------- Comment #8 from user72(a)go2.pl 2006-09-12 10:54 MST ------- Kernel version is 2.6.18-rc5-git6-2-default. commands: "rmmod asus_acpi" and "modprobe asus_acpi" - both give no errors. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 0

[Bug 171517] APIC problems on Asus M2N-SLI Deluxe (chipset nForce 570; socket AM2) machine hangs at early boot time
by bugzilla_noreply＠novell.com 12 Sep '06

12 Sep '06

https://bugzilla.novell.com/show_bug.cgi?id=171517 ------- Comment #7 from user72(a)go2.pl 2006-09-12 10:50 MST ------- Created an attachment (id=98470) --> (https://bugzilla.novell.com/attachment.cgi?id=98470&action=view) Acpidump -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 0